244
Fig. 17. Distributed concept
Fig. 18. Distributed concept
Fig. 19. Distributed concept
Fig. 20. Conclusions to resume the discussion
2 CONCLUSIONS
It appears feasible to minimise the number of alerts
especially those on a high priority.
The conceptual design supports the
implementation of “Function Alerts” and “System
Alerts” and the capability of navigational system
level modules to acknowledge “Function Alerts”.
Easily manageable alert related communication
will be supported by this concept.
This presentation is a condensed version of an
Alert Management concept based as a full version
on different series of slides dealing with topics
like “State Monitoring”, “Alert State Transitions”,
“Alert Announcement State Transitions”, “Escala-
tion
Strategy” (to handle unacknowledged alerts),
“Deescalation Strategy” (to minimise the number of
high priority alerts) and “Consistency of Alert
Presentation within a Navigational System”.
German workgroups deal successfully with these
series of slides as a “starting point” whenever
they plan to recommence discussions on related
matters.
Additionally the slides are applied as a “toolbox”
useful to align the picture of an Alert Management
Structure in the mind’s eye of each member of a
working group during discussions.
These series of slides are especially suited to
mediate between the generic requirements laid down
in the Performance Standards and the “Operational
and Performance Requirements” to be implemented
in IEC’s International Standards.