10. Appendix
10-7
These cannot be null fields.
2) The sequential message identifier relates all sentences that belong to a group of multiple
sentences (i.e.message). Multiple sentences with the same sequential message identifier,
make up onemessage.
3) Contains the number of alert entries transported within this sentence.
4) Alert entry 0 – n: Each alert entry consists of four fields:
• Manufacturer Identifier (see ALF Manufacturer Identifier)
• Alert Identifier (see ALF Alert Identifier)
• Alert instance (see ALF Alert instance)
• Revision Counter (see ALF Revision Counter)
Each entry identifies a certain alert with a certain state. It is not allowed that an alert entry is
split between two ALC sentences.
8) 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>
1 2 3 4 5 6 7 8 9 10 11 12 13
1: Total number of ALF sentences for this message, 1 to 2 1)
2: Sentence number, 1 to 2 1)
3: Sequential message identifier, 0 to 9 2)
4: Time of last change 3)
5: Alert category, A, B or C 4)
6: Alert priority, E, A, W or C 5)
7: Alert state, A, S, N, O, U or V 6)
8: Manufacturer mnemonic code 7)
9: Alert identifier 8)
10: Alert instance, 1 to 999999 9)
11: Revision counter, 1 to 99 10)
12: Escalation counter, 0 to 9 11)
13: Alert text 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.
2) The sequential message identifier relates all sentences that belong to a group of multiple
sentences (i.e. message). Multiple sentences with the same sequential message identifier,
make up one message.
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 Table 5 Field type summary. Receiver is allowed to ignore
content of this field. If the receiver does not ignore this field it should support all alternatives
defined in Table 5 Field type summary.
4) The alert category is in compliance with the category definition as described in INS
Performance Standard (IMO MSC.252(83)) and Bridge Alert Management Performance
To Next Page
Loading...
Need help?
General
