JRC JFE-700, Инструкция по эксплуатации

Страница: 92 / 100

10. Appendix
10-8
Standard (IMO MSC.302(87)):
A, Category A: Alerts where information at operator unit directly assigned to the function
generating the alert is necessary, as decision support for the evaluation of the
alert-related condition, e.g. graphical information of danger of collision or
graphical information of danger of grounding.
B, Category B: Alerts where no additional information for decision support is necessary
besides the information which can be presented using alert source and alert
description text.
C, Category C: Alerts that cannot be acknowledged on the bridge but for which information is
required about the status and treatment of the alerts, e.g., certain alerts from
the engine.
5) Alert priority: Emergency Alarm: E, for use with Bridge alert management
Alarm: A
Warning: W
Caution: C
6) The alert state transition is defined in IEC 61924-2:2012, Annex J
active – unacknowledged: V
active – silenced: S
active – acknowledged or active: A
active – responsibility transferred: O
rectified – unacknowledged: U
normal: N
7) Used for proprietary alerts defined by the manufacturer. For standardized alerts this should
be a null field.
8) The alert identifier is unique within a single alert source. The alert identifier is a variable
length integer field of maximum a 7-digit integer. It identifies the type of the alert, e.g. a “lost
target” alert. Standardized alerts use unique alert identifiers described in equipment
standards. Number range 10000-9999999 is reserved for proprietary alerts. Alert Identifier
examples: “001”, “2456789”, “245”
9) The alert instance identifies the current instance of an alert to distinguish alerts of the same
type (Alert identifier) and from the same source (e.g. dangerous target). Alert instance is
maximum a 6-digit integer from 1 to 999999, the number ‘0’ indicates that this sentence is
intended for all alert instances. Except for number ‘0’, the number of alert instance can be
freely defined by the manufacturer as long as it is unique for one type of alert (alert
identifier). It is not permitted to modify the alert instance within a life cycle of a distributed
alert (from ‘active and unacknowledged’ state until ‘normal’ state is reached). It can be also
a null field, when there is only one alert of that type.
10) The revision counter is the main method to follow up-to-date status. Revision counter is
also unique for each instance of alert. Revision counter starts with 1 and the step for
increment is 1. The count resets to 1 after 99 is used. Revision counter increments on each
change of content of any field of the alert.
11) The escalation counter is presenting the number of alert escalations after time expiration
during the state active-unacknowledged. The escalation counter starts with 0 and the step
for increment is 1. The count resets to 1 after 9 is used. The alert escalation can be the
escalation from warning into warning (activation of audible signal only), the escalation from
warning to alarm or the escalation from alarm to alarm with activation of backup navigator
alarm.