Bridge alert management: UK21/N004

Adopted EU recommendation NAV-017. UK approved recommendation on the application of MSC.302(87) to Bridge Alert Management (BAM) systems.

From:
Maritime and Coastguard Agency
Published
18 July 2023
Category:
Navigation equipment
Year adopted:
2021
Reference number:
UK21/N004
Keyword:
NAV-017

Question

In MSN 1874 as amended, MSC.302(87) is included under the testing standards for some navigation equipment.

Which parts of MSC.302(87) is the navigation equipment is expected to comply with?

Recommendation

BAM-compliant equipment: BAM compliance is only relevant for equipment that is capable of issuing alerts.

To be considered BAM-compliant, equipment should include the correct application and presentation of that stated below, as applicable to the type of equipment [footnote 1].

Priorities of alerts

  • Alarms
  • Warnings
  • Cautions

Categories of alerts

[footnote 2]

  • Category A alerts
  • Category B alerts

State of alerts

  • Active - unacknowledged
  • Active - silenced
  • Active - acknowledged
  • Active - responsibility transferred
  • Rectified - unacknowledged
  • Active
  • Normal

The status of alerts shall be presented according to Table 2 of IEC 62288 (2014). If icons are used, these shall be presented as defined in Annex F of IEC 62288 (2014).

Interface

An interface according to IEC 61162-1 (2016) for reporting alerts, supporting the following messages [footnote 3] - ALF, ALC, ACN, ARC and HBT [footnote 4]

Verification of BAM compliance

Documentation to be submitted:

  • list of alerts for the equipment. The list of alerts shall include the alert identifier, title[footnote 5], description (if provided), category and priority for all alerts to be provided by the equipment. The NMEA talker ID applied for alert communication should be included.
  • list of IEC 61162-1 messages that are supported
  • user and installation manuals

Tests/checks to be carried out on the equipment:

  • Inspection of the manufacturer’s documentation (for example. alert list) to verify that alerts comply with criteria for the classification and categorization of alerts as per definitions in MSC.302(87) and IEC 62288 (2014), and that the alert title and description are appropriately formatted using simple unambiguous language providing a clear meaning.
  • Verification of the receipt and sending of ALF, ALC, ACN, ARC, HBT messages according to IEC 61162-1 (2016), including the correct use of and response to all message data fields. Ref to B.4.9.1 and B.4.9.2 for check items and examples of test documentation (tables B.4 through B.10).
  • Verification of the protocol for alert-related communication including the state diagrams as listed in module A of IEC 62923-1 (2018)
  • Alternatively, at least verification of the protocol for alert-related communication including the state diagram in Annex J of IEC 61924-2 (2012). Protocol tests are to include the following cases, as applicable to the equipment:
    • All alert categories (for example category A, category B)
    • All alert priorities (for example alarm, warning, caution)
    • All alert state transitions (V, S, A, O, U, N) Note: The remote silencing of alerts shall include verification that an audible signal starts again after 30 seconds if the alert is not acknowledged. Repeated attempts to silence the alert should not prevent the recurrence of the audible signal, but repeated silencing is allowed unless otherwise specified in the individual performance standards (for example TCS)
    • Alert instance and revision counter
    • Alert escalation of unacknowledged warnings and the correct use of the escalation counter. Note: Warnings may be escalated to warnings or alarms after a selectable time period not exceeding 5 mins.
    • Attempt to remotely acknowledge a category A alarm and warning.
  • Verification of the correct presentation of alerts in accordance with IEC 62288 (2014). Two of each of the available alerts of priority alarms, warnings and cautions to be chosen at random for the test.

Verification of the alert presentation versus the description in the list of alerts.

References

  • MSN 1874 as amended
  • The Merchant Shipping (Marine Equipment) Regulations 2016 as amended
  • MSC.302(87)

Items affected

  • UK/4.X, Navigation equipment

More information

Maritime and Coastguard Agency
Bay 2/21
Spring Place
105 Commercial Road
Southampton
SO15 1EG

Telephone: +44 (0) 203 817 2000

Email: MEQA@mcga.gov.uk

Website: www.gov.uk/mca

  1. The alerts required for a type of equipment are stated in the individual performance and testing standards. Manufacturers may define proprietary alerts in addition. The priorities and categories of alerts to be supported will hence vary for different equipment, but shall follow the criteria and definitions in MSC.302(87). ↩

  2. Ref to Annex C of IEC 61924-2 for examples of the classification of alerts defined in existing individual IMO performance standards. Individual equipment standards may require additional alerts to be provided, ref. e.g. Annex D of IEC 61174 (2015). ↩

  3. Some individual testing standards do not specify any interface for alerts, or specify an interface based on ALR and ACK. ↩

  4. As MSC.302(87) takes precedence over conflicting requirements in individual performance standards, support for ALF, ALC, CAN, ARC and HBT is considered mandatory for BAM-compliant equipment. ↩

  5. The title and description should be listed in the format and transmitted in ALF to CAM. ↩

Published 18 July 2023
Contents