NSR Marine NVR-3000, Operation And Installation Manual

Page: 94 / 105

NVR-3000 OPERATION MANUAL & INSTALLATION MANUAL
NVR-3000 OM.E 20210412-02 94
ALF - Alert sentence
$--ALF, x, x, x, hhmmss.ss, a, a, a, aaa, x.x, x.x, x.x, x,c---c*hh <CR><LF>
| | | | | | | | | | | | |
| | | | | | | | | | | | +------------------------ 13
| | | | | | | | | | | +------------------------ 12
| | | | | | | | | | +------------------------- 11
| | | | | | | | | +------------------------- 10
| | | | | | | | +-------------------------- 9
| | | | | | | +---------------------------- 8
| | | | | | +--------------------------- 7
| | | | | +----------------------- 6
| | | | +-------------------- 5
| | | +---------------------------- 4
| | +-------------------------- 3
| +----------------------- 2
+---------------------1
1.
Total number of ALF sentences for this message, 1 to 2 (see Note 1)
2.
Sentence number, 1 to 2 (see Note 1)
3.
Sequential message identifier, 0 to 9 (see Note 2)
4. Time of last change (see Note 3)
5. Alert category, A, B or C (see Note 4)
6. Alert priority, E, A, W or C (see Note 5)
7. Alert state, A, S, R, O, U or D (see Note 6)
8. Manufacturer mnemonic code (see Note 7)
9. Alert identifier (see Note 8)
10. Alert instance, 1 to 999999 (see Note 9)
11. Revision counter, 1 to 99 (see Note 10)
12. Escalation counter, 0 to 9 (see Note 11)
13. Alert text (see Note 12)
NOTE 1: The first field specifies the total number of sentences used for a message, minimum value 1. The second
field identifies the order of this sentence in the message, minimum value 1, these cannot be null fields.
When the sentence number is 2, the following Alert category, Alert priority and Alert state can be null
fields.
NOTE 2: The sequential message identifier relates all sentences that belong to a group of multiple sentences (i.e.
message). Multiple sentences (see Note 1) with the same sequential message identifier, make up one
message.
NOTE 3: Time should represent the last time the data within the alert message has changed. For example changing
the alert text by in-/decrementing a contained counter or count down should cause a revision of alert
message and a new time. Time is an optional field. The time-field is additional information about when
this happened and not used for decision making. There is no mandatory requirement for time
synchronization between the equipment. It should by either a null field (if not used) or UTC (if used).
Sender is allowed to use all alternatives defined in Alert Description Table. Receiver is allowed to
ignore content of this field. If the receiver does not ignore this field it should support all alternatives
defined in Alert Description Table.
NOTE 4: The alert category is in compliance with the category definition as described in INS Performance
Standard (MSC.252(83)) and Bridge Alert Management Performance Standard (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.