ShipCalculators.com

By ShipCalculators.com · Published

BNWAS: Bridge Navigational Watch Alarm System under SOLAS V/19-2

The Bridge Navigational Watch Alarm System (BNWAS) is the mandatory bridge-vigilance alarm under Regulation 19-2 of Chapter V of the SOLAS Convention, designed to detect officer-of-the-watch (OOW) incapacitation, sleep, sudden illness, absence and bridge desertion through a timed-reset cycle that escalates from a silent visual prompt on the bridge to an audible bridge alarm and finally to a cabin alarm in the master, chief officer and additional crew accommodations. SOLAS Regulation V/19-2 was inserted by IMO Resolution MSC.282(86) in 2009 and entered into force on 1 July 2011 for new builds, with phased retrofit through 2014 for existing passenger ships and existing cargo ships of 150 GT and above including high-speed craft. The original performance standard was IMO Resolution MSC.128(75) of 2002, revised by IMO Resolution MSC.355(92) of 2013 to refine GNSS and AIS integration, and the testing standard is IEC 62616 layered on the general radio-equipment baseline of IEC 60945 and IMO Resolution A.694(17). The function is straightforward: while the ship is at sea the OOW must reset at a bridge reset station within a master-adjustable interval Tr in the range 3 to 12 minutes; failure triggers Stage 1 visual alarm on the bridge, then approximately 15 seconds later Stage 2 audible bridge alarm, then approximately 90 seconds later Stage 3 cabin alarm in master, chief officer and designated additional crew. The active modes are Auto (always on at sea), Manual on/off (master discretion in port), and Off (only at anchor or berth). The casualty record driving the 2009 adoption includes the Pasha Bulker grounding at Newcastle on 8 June 2007 and a long line of fatigue-related casualties documented under STCW Chapter VIII watchkeeping; BNWAS interfaces with VDR, LRIT, AIS and ECDIS, AIS-SART, GMDSS, the ISM Code, MLC 2006, STCW Chapter II and the COLREGs Convention; ShipCalculators.com hosts the calculator catalogue for Tr selection and carriage-threshold determination.

Contents

Background: 1989 Marchioness + 2007 Pasha Bulker incident drivers

The case for a mandatory bridge-vigilance alarm grew from a long casualty record of fatigue-related groundings and collisions on watchkeeping bridges. The Marchioness disaster on the River Thames on 20 August 1989, in which a Thames pleasure boat was overrun by the dredger Bowbelle with 51 lives lost, exposed the watchkeeping inadequacies that recurred through the following two decades. Through the 1990s and 2000s UK MAIB, US NTSB, Australian ATSB and equivalent flag-State reports identified single-watchkeeper incapacitation as a recurring causal pattern.

The casualty most closely associated with IMO BNWAS adoption is the MV Pasha Bulker grounding at Newcastle Beach, New South Wales, on 8 June 2007. The 76,741 DWT Panamax bulk carrier waiting at anchor offshore Newcastle failed to weigh anchor and stand off as a severe east-coast low approached and was driven onto the beach. The ATSB report MAIR 243 highlighted bridge-resource shortcomings, and the casualty became a public symbol of bridge-vigilance failure as the IMO MSC finalised the 2009 amendment package. The IMO NAV Sub-Committee had placed BNWAS on its agenda through the 2000s, building on the MSC.128(75) voluntary standard of 2002. At MSC 86 in June 2009 the Committee adopted Resolution MSC.282(86) introducing new SOLAS Regulation V/19-2.

SOLAS V/19-2 carriage requirements

Regulation 19-2 of SOLAS Chapter V, inserted by MSC.282(86) and titled “Bridge Navigational Watch Alarm System (BNWAS)”, requires ships engaged on international voyages to be fitted with a BNWAS complying with the IMO performance standards. The carriage envelope under Regulation 19-2.2 covers passenger ships of any size including HSC; cargo ships of 150 GT and above and less than 500 GT including HSC; cargo ships of 500 GT and above and less than 3,000 GT including HSC; and cargo ships of 3,000 GT and above including HSC. Regulation 19-2.2.3 requires the BNWAS to be in operation whenever the ship is underway at sea. Regulation 19-2.2.4 permits flag-State exemption for ships engaged solely on domestic voyages within the territorial sea, subject to PSC scrutiny.

The 150 GT threshold for cargo ships is materially lower than the 500 GT threshold typical of other SOLAS V navigation-equipment requirements. The lower threshold captures the small-cargo and short-sea fleet most exposed to fatigue-related single-watchkeeper failure modes.

MSC.282(86) 2009 adoption + 1 July 2011 entry into force

Resolution MSC.282(86) was adopted at MSC 86 on 5 June 2009 under the SOLAS Article VIII tacit-acceptance procedure. The amendments were deemed accepted on 1 January 2011 and entered into force on 1 July 2011. The 1 July 2011 date applied immediately to new ships: any passenger ship or cargo ship of 150 GT and above (or HSC) the keel of which was laid on or after 1 July 2011 was required to be delivered with a fully-functioning BNWAS meeting MSC.128(75). The retrofit schedule for existing ships ran through 2012, 2013 and 2014. The MSC discussion identified BNWAS as a low-cost high-value intervention: per-ship retail-and-installation cost of USD 2,500 to 8,000 was modest by comparison with casualty consequences avoided.

Phased retrofit for existing ships through 2014

The retrofit timetable in V/19-2.2.2 distinguished four bands across three SOLAS-survey-anniversary cycles. Passenger ships of any size constructed before 1 July 2011 were required to be fitted not later than the first survey after 1 July 2012. Cargo ships of 3,000 GT and above: not later than first survey after 1 July 2012. Cargo ships of 500 GT and above and less than 3,000 GT: not later than first survey after 1 July 2013. Cargo ships of 150 GT and above and less than 500 GT: not later than first survey after 1 July 2014.

The phasing allowed manufacturers (Furuno, JRC, Kongsberg, Sperry, Raytheon Anschutz, Tokyo Keiki, Imtech, Saab) to scale production, operators to align installation with planned dry-docking, and the type-approval and class-survey infrastructure time to absorb the new requirement. By 1 July 2014 BNWAS became a routine PSC inspection check item.

MSC.128(75) 2002 originally + revised MSC.355(92) 2013

Resolution MSC.128(75) was adopted at MSC 75 on 20 May 2002 as a voluntary performance standard. It defined the three-stage alarm architecture, the Tr 3 to 12 minute envelope, the Auto/Manual/Off mode framework, reset-station type and number, and interfaces to ship’s power, alarm panels and cabin loudspeakers. Because MSC.128(75) was not yet linked to a SOLAS carriage mandate, voluntary uptake through the 2000s was limited.

Resolution MSC.355(92) was adopted at MSC 92 on 21 June 2013 as a substantive revision. It refined GNSS integration so the BNWAS may receive GPS-derived SOG and time inputs to determine ship-at-sea status objectively, refined AIS integration for navigation-status alignment, tightened alarm-fatigue mitigation through specification of Stage 1 visual characteristics (steady non-flashing yellow with intelligible cause-text) and Stage 2 audible characteristics (continuous tone distinguishable from other bridge alarms), clarified reset-station siting to ensure a reset cannot be triggered by accidental contact, and aligned acceptance criteria with the IEC 62616 updates of 2010. MSC.355(92) applies to all BNWAS units fitted on or after 1 July 2014.

IEC 62616 + IEC 60945 testing

IEC 62616 is the international testing and conformance standard for BNWAS, current edition IEC 62616:2010 with subsequent amendments aligning with MSC.355(92). The standard specifies test methods for each alarm stage, reset-station response time, audible-alarm sound-pressure level (typically 75 to 85 dB(A) at the listener position), visual-alarm photometric envelope, cabin-alarm interface, active-mode selection and password protection, and system self-test. The test sequence covers alarm-escalation timing (Stage 1 entry on Tr expiry, Stage 2 approximately 15 seconds later, Stage 3 approximately 90 seconds later, Stage 3 continuation until reset at the bridge), the Tr adjustment envelope, and active-mode lock-out (only the master may select Off mode, and only at anchor or berth).

IEC 60945 is the horizontal testing standard for shipborne radio and electronic-navigation equipment, defining the environmental, EMC, mechanical-shock and power-supply baseline. IEC 62616 references IEC 60945 as the foundation on which the BNWAS-specific test sequence is layered. Type-approval certificates issued under IEC 62616 by recognised classification societies (DNV, LR, ABS, BV, NK, RINA, KR, CCS, RS, IRS) are accepted by IMO Member States as evidence of compliance with MSC.128(75) or MSC.355(92).

Carriage threshold: >=150 GT cargo + passenger + HSC

The 150 GT carriage threshold brings the small-cargo and short-sea fleet within the BNWAS regime, capturing the fleet most exposed to fatigue-related single-watchkeeper failure. Below 150 GT the carriage is not mandatory under V/19-2 but flag States may impose carriage on smaller domestic-only tonnage. For passenger ships there is no lower size threshold: every SOLAS-applicable passenger ship, including small island-ferry and short-route tonnage, is required to be fitted. For HSC the requirement applies to passenger HSC and cargo HSC of 150 GT and above; HSC built to the 1994 HSC Code or 2000 HSC Code are subject to the same V/19-2 envelope by reference. The higher HSC operating speed (typically 30 to 50 knots) compresses response time available to master and chief officer after a Stage 3 alarm, and the operational risk of OOW incapacitation is correspondingly elevated.

Function: OOW vigilance monitoring via reset cycle

The BNWAS function is built around a timed-reset cycle that translates OOW vigilance into a concrete operational sequence. While the ship is at sea with BNWAS in Auto mode the system continuously monitors elapsed time since the last reset action; a reset is registered when the OOW activates a bridge reset station, resetting the counter to zero. If the OOW does not reset within Tr the system enters Stage 1; if no reset within approximately 15 seconds it enters Stage 2; if no reset within approximately 90 seconds further it enters Stage 3 cabin alarm.

The architecture embodies graduated escalation: brief inattention (Stage 1) is corrected without disturbing other crew; longer inattention (Stage 2) brings the OOW back from a brief absence (chartroom, head call); sustained inattention (Stage 3) is escalated to the master and chief officer. The system does not directly intervene in ship handling and the reset must be performed at the bridge so an alerted master can determine whether the OOW is fit to continue.

Tr reset interval: 3-12 minutes adjustable

The reset interval Tr is the principal operationally-tunable parameter. Under MSC.355(92):

Tr∈[3,12] minutes (adjustable reset interval) T_{r} \in [3, 12] \text{ minutes (adjustable reset interval)}

The 3-minute floor is the level below which the cycle becomes operationally intrusive. The 12-minute ceiling is set above the level at which the OOW could enter and exit a sleep state without triggering Stage 2. The master selects Tr by operational context: low-traffic open-ocean transits at 10 to 12 minutes; coastal approach at 5 minutes; pilotage at 3 minutes. The selection is recorded in the bridge log and is auditable on PSC inspection.

Stage 1: visual alarm on bridge

Stage 1 is triggered immediately on expiry of Tr. The alarm is visual only: a steady non-flashing yellow light at the bridge reset station and the main bridge alarm panel, with intelligible cause-text such as “BRIDGE WATCH ALARM”. Stage 1 is silent so brief inattention does not generate audible nuisance. The OOW must perform a deliberate reset within approximately 15 seconds. The IEC 62616 photometric envelope requires sufficient intensity for daylight visibility but not so intense as to compromise night-vision adaptation, with dimming control to preserve OOW night vision. The visual alarm is located at the bridge alarm panel and at each reset station so the OOW is immediately aware regardless of bridge position.

Stage 2: audible alarm on bridge ~15 sec later

Stage 2 is triggered approximately 15 seconds after Stage 1:

Tstage 1 to stage 2≈15 seconds T_{\text{stage 1 to stage 2}} \approx 15 \text{ seconds}

The alarm is audible on the bridge: a continuous tone distinguishable from other bridge alarms (ARPA collision, ECDIS chart, GPS loss-of-fix, AIS proximity, gyro fault). IEC 62616 specifies sound-pressure level (typically 75 to 85 dB(A) at the listener position) and a frequency profile intelligible against bridge ambient noise. Stage 2 runs alongside the continuing Stage 1 visual; both remain active until reset. The 15-second escalation is short by design: an OOW who has not responded to a Stage 1 visual within 15 seconds is presumptively absent, and the audible escalation brings the OOW back if a brief absence (head call, bridge pantry) is the explanation.

Stage 3: cabin alarm ~90 sec later (master, CO, additional crew)

Stage 3 is triggered approximately 90 seconds after Stage 2:

Tstage 2 to stage 3≈90 seconds T_{\text{stage 2 to stage 3}} \approx 90 \text{ seconds}

The alarm extends beyond the bridge to defined cabin loudspeakers in the master’s cabin, the chief officer’s cabin, and (where designated) additional crew cabins identified in the SMS as backup responders. The cabin tone is distinct from other shipboard alarms (general, fire, abandon-ship) so the awakened officer immediately recognises a BNWAS event. The Stage 3 mechanism is the BNWAS’s principal contribution to bridge-resource resilience: it ensures OOW incapacitation does not pass undetected through the watch period. The cabin loudspeaker must reach typically 75 dB(A) at the bunk position and is wired so loss of cabin-side power does not silence the alarm; the cabin circuit is independent of the bridge-side audible so bridge-side fault does not propagate.

Stage 3 continues until OOW resets at bridge

A defining feature is that Stage 3 continues until reset at the bridge. The cabin-side has no silencing capability; the master and chief officer must come to the bridge to perform the reset, forcing a physical bridge presence and a face-to-face check on the OOW. This is the principal behavioural design: master and chief officer cannot suppress the alarm without first verifying the OOW is fit. The reset-at-bridge requirement also addresses a defeat vector: an OOW pre-arranging relief by a non-bridge crew member cannot have the relief silence from the cabin. Forensic reconstruction after a casualty can use the VDR bridge-audio record and the BNWAS internal event log to determine how the alarm was resolved.

Reset stations: bridge wing + chartroom (multiple)

The performance standard requires multiple reset stations distributed across the bridge so the OOW can reset from any practical position. Typical layout includes the main alarm panel at the conning station, port and starboard bridge-wing reset buttons, and a chartroom reset button. Larger bridges have four to six stations; smaller bridges have two or three. The principle is that the OOW should not have to deviate substantially from a normal watchkeeping position. IEC 62616 specifies reset-action acceptance time (within 1 second of action) and audible feedback (confirming click or tone). Some vessels integrate the reset with the radar, ECDIS or conning display; where so integrated the reset must remain a deliberate user input (designated key press or screen action), preserving the deliberate-action principle.

Reset deliberate action (not solely from chair)

A central design rule is that a reset must require deliberate action; the reset must not be triggered solely by the OOW’s presence in the conning chair. This addresses a defeat scenario in which an OOW rendered unfit by sleep or incapacitation could trigger inadvertent reset by sitting motionless. Implementation is through push-button stations, motion-detector systems requiring deliberate motion across a defined sensor envelope, and console-action reset requiring a designated user input. Chair-mounted sensors are not acceptable as the sole reset trigger under MSC.355(92); a chair sensor may complement push-button reset but cannot replace it. The rule is enforceable through type-approval, and PSC inspectors verify reset stations specifically for the deliberate-action requirement.

Active modes: Auto, Manual on/off, Off

The BNWAS supports three modes. Auto is active continuously while the ship is at sea; under MSC.355(92) Auto may be triggered automatically by GNSS-derived SOG or AIS-derived ship-status. Manual on/off allows the master to switch the BNWAS on or off in defined contexts (port operations, alongside cargo work, and pilotage in some implementations); mode changes are logged. Off is permitted only at anchor or alongside; selecting Off while underway is non-compliance and a serious PSC finding. The three-mode architecture balances operational reality (continuous alarming during cargo work would be intolerable) against the safety mandate. Mode-selection controls are password-protected so only the master and (where delegated) the chief officer can change modes.

Relationship to STCW Chapter VIII rest hours

BNWAS is a technical countermeasure to OOW fatigue but not a substitute for STCW Chapter VIII watchkeeping and MLC 2006. STCW Chapter VIII requires minimum rest hours (10 hours in any 24-hour period and 77 hours in any 7-day period) with limited emergency exceptions. MLC 2006 establishes the broader hours-of-work-and-rest and minimum-manning regime. BNWAS detects the consequence of inadequate rest; the primary defence remains operator compliance with rest-hour and manning regulations. Many fatigue-related casualties are characterised by master-and-OOW pairs operating below STCW minima, often on short-sea routes. Post-2009 PSC enforcement combines BNWAS checks with rest-hour and manning checks to address the integrated risk picture.

Relationship to BRM Bridge Resource Management

Bridge Resource Management (BRM) is the operational discipline of using all bridge resources (officers, lookouts, equipment, communications) to maintain situational awareness and decision quality, required under STCW Tables A-II/1 and A-II/2. BNWAS is one technical element: it ensures an unattended bridge does not pass undetected, but does not replace cross-checking navigation, calling the master in defined circumstances, maintaining lookout, or managing pilot interaction. A well-functioning BRM team rarely triggers Stage 3 because the lookout, helmsman or pilot present alerts the OOW well before escalation. A Stage 3 event in casualty investigation is a strong indicator of BRM breakdown.

Alarm fatigue concern: ECDIS + AIS + collision-avoidance

The layered bridge-alarm population creates an alarm-fatigue concern: OOW habituation to a high-frequency alarm flow that desensitises response to genuine emergency alarms. The bridge alarm population on a modern merchant vessel includes ARPA collision, ECDIS chart (anti-grounding, route-deviation, look-ahead), AIS proximity, GNSS loss-of-fix, gyro fault, autopilot off-track, and BNWAS Stage 1 and Stage 2 alarms; aggregate rates may exceed several alarms per hour in dense traffic. The MSC.355(92) revision addressed alarm fatigue by tightening Stage 1 visual characteristics and Stage 2 audible characteristics. The 2024 IMO MSC review of bridge alarm prioritisation is examining an over-arching alarm-management framework that would prioritise safety-critical alarms (BNWAS Stage 3 chief among them).

2007 Pasha Bulker grounding catalyst

The MV Pasha Bulker grounding at Newcastle Beach on 8 June 2007 is the casualty most closely associated with the IMO BNWAS adoption discussion. The 76,741 DWT Panamax bulk carrier failed to weigh anchor and stand off as a severe east-coast low approached with sustained winds of 50 to 60 knots; the vessel dragged anchor and grounded on Newcastle’s main beach. ATSB MAIR 243 identified bridge-resource and weather-assessment failings as principal causes. While the immediate failure was not OOW sleep, the casualty became a public symbol of bridge-resource breakdown. The MSC NAV Sub-Committee analysis at MSC 86 referenced a broader casualty corpus including fatigue-related groundings reported by UK MAIB, US NTSB and Australian ATSB through the 2000s; the aggregate evidence supported a regulatory case that BNWAS would catch a meaningful fraction of fatigue-related casualties at modest cost.

2009 MSC adoption rationale

The MSC 86 adoption was justified on three grounds. Casualty cost: fatigue-related groundings and OOW sleep events had been a persistent contributor with measurable life and environmental cost. Intervention cost: per-ship cost of USD 2,500 to 8,000 (with installation typically a single day’s work) was modest relative to casualty consequences. Technical feasibility: BNWAS was a mature technology with type-approved manufacturers already supplying under voluntary MSC.128(75), requiring no new technology development. Implementation concerns about per-ship cost in fleets of small vessels were addressed by setting the threshold at 150 GT and phasing retrofit through 2014; concerns about deliberate-action and nuisance alarms were addressed in the MSC.355(92) revision.

Major manufacturers: Furuno, JRC, Kongsberg, Sperry, Raytheon Anschutz, Tokyo Keiki, Imtech, Saab

The BNWAS market is supplied by established marine-electronics manufacturers, most active also in radar, ECDIS, GNSS, AIS, VDR and IBS markets. Principal type-approved suppliers include Furuno (Japan, BR-500 standalone and integration into FAR-2xx7/3xx0 radar and FMD-3xx0 ECDIS); JRC (JBN-1000 standalone, integrated into JAN-9201/7201 ECDIS and JMR-9230 radar); Kongsberg Maritime (Norway, K-Bridge BNWAS module); Sperry Marine / Northrop Grumman (USA, VisionMaster FT); Raytheon Anschutz (Germany, Synapsis NX); Tokyo Keiki (Japan, TBR-1 on Japanese coastal and short-sea tonnage); Imtech Marine / Radio Holland (Netherlands); and Saab Transponder Tech / Saab Maritime (Sweden). Type-approval certificates are interchangeable across major flag States; operators select on installed-base familiarity, integration with existing bridge electronics, and after-sales service network. Smaller specialist suppliers (Hi-Sea, Headway, Maritec) serve niche segments, particularly the Chinese coastal and small-cargo segments.

Typical models: Furuno BR-500, JRC JBN-1000, Tokyo Keiki TBR-1

Three illustrative models bracket the typical envelope. The Furuno BR-500 is a standalone unit with master alarm panel, four reset stations, cabin loudspeaker outputs for master, chief officer and two additional cabins, GNSS interface for automatic Auto-mode triggering, and AIS interface for ship-status confirmation; type-approval by NK, DNV, LR, ABS, BV, KR; retail USD 3,500 to 5,000 installed; widely fitted on Japanese-built bulk carriers, tankers and container ships delivered between 2011 and the present. The JRC JBN-1000 has similar architecture with cabin-loudspeaker outputs scalable to 6 cabins; type-approval by NK, DNV, LR, ABS, BV, KR, CCS; retail USD 3,000 to 4,500 installed. The Tokyo Keiki TBR-1 is a cost-optimised standalone unit aimed at the small-cargo and coastal segment with 2 cabin-loudspeaker outputs; retail USD 2,500 to 3,500 installed. An increasing share of new tonnage from approximately 2015 integrates BNWAS into the IBS as a software function, fitted predominantly on cruise ships, large container ships and gas carriers.

Typical retail price: USD 2,500-8,000 installed

The retail-and-installation envelope is bounded:

Cinstalled∈[2,500,8,000] USD C_{\text{installed}} \in [2{,}500, 8{,}000] \text{ USD}

The lower end (USD 2,500 to 3,500) corresponds to small-cargo coastal vessels of 150 to 500 GT with simple bridges and two cabin-loudspeaker outputs. The middle (USD 4,000 to 5,500) corresponds to typical deep-sea bulk carriers, tankers and container ships with four reset stations and four to six cabin-loudspeaker outputs. The upper end (USD 6,500 to 8,000) corresponds to large passenger and cruise tonnage with extensive reset-station distribution, large cabin-loudspeaker counts, and IBS interfacing requiring software-side configuration and class-attended commissioning testing. The cost is materially below VDR (USD 30,000 to 80,000) and ECDIS (USD 15,000 to 50,000); cost-effectiveness was a principal element of the MSC adoption rationale.

MSC.355(92) 2013 GPS/AIS integration enhancements

The MSC.355(92) revision introduced enhancements in BNWAS integration with GNSS and AIS. The original MSC.128(75) had defined BNWAS as a self-contained alarm system with master-controlled mode selection; the 2013 revision added optional but recommended interfaces to GNSS SOG and AIS navigation status so the BNWAS could automatically determine ship-at-sea status. GNSS integration permits detection of SOG above a threshold (typically 1 to 2 knots) as an indicator the ship is underway. AIS integration permits the BNWAS to read the AIS navigation status field (under-way using engines, at anchor, moored, not under command) and align active-mode selection with AIS-broadcast status; an inconsistency is logged for PSC review. The 2013 enhancements are not retrofittable to MSC.128(75) units already fitted; most current-generation units from approximately 2015 implement both GNSS and AIS integration as standard.

2024 IMO MSC bridge alarm prioritisation review

The IMO Maritime Safety Committee in 2024 opened a structured review of bridge alarm prioritisation across the SOLAS V carriage requirements. The review, advancing through MSC 108 (May 2024) and MSC 109, addresses the cumulative bridge-alarm population accreted across BNWAS, ECDIS, ARPA, AIS, GNSS, gyro, autopilot, ECS and machinery-control domains. The objective is an over-arching alarm-management framework that prioritises safety-critical alarms (BNWAS Stage 3 chief among them, alongside ARPA collision-imminent, ECDIS anti-grounding and fire alarms), suppresses or aggregates routine information alarms, and reduces alarm-fatigue exposure. The review draws on industrial alarm-management principles in IEC 62682, IEC 61511 and ISA 18.2 adapted to the bridge environment. Expected outputs include a revised general alarm-management standard, possible amendments to IEC 62616, and possible amendments to MSC.355(92).

Autonomous + remote-control ship integration

The IMO MASS (Maritime Autonomous Surface Ships) work stream, advancing toward a non-mandatory MASS Code adoption in 2024 to 2026 and possible mandatory Code adoption in the late 2020s, intersects with BNWAS. For Degree 1 MASS (automated decision support but seafarers on board) BNWAS is unchanged. For Degree 2 MASS (remotely-controlled with seafarers on board) BNWAS may be supplemented by a remote-watchkeeping monitoring system covering remote-control-station OOW vigilance. For Degree 3 MASS (remotely-controlled without seafarers on board) BNWAS as a bridge-vigilance device becomes inapplicable to the on-board configuration and transfers to the remote-control-station environment. For Degree 4 MASS (fully autonomous) the OOW vigilance concept transforms into system-monitoring and the BNWAS framework requires replacement. Class-society interim guidance from DNV, LR, ABS and ClassNK has begun to outline BNWAS application for MASS configurations.

Class society type-approval: DNV, LR, ABS, BV, NK, RINA, KR, CCS, RS, IRS

BNWAS type-approval is issued by classification societies as recognised organisations under the IACS framework and the IMO RO Code. Principal issuers are DNV (Norway), Lloyd’s Register (LR) (UK), ABS (USA), Bureau Veritas (BV) (France), ClassNK / NK (Japan), RINA (Italy), Korean Register (KR), China Classification Society (CCS), Russian Maritime Register of Shipping (RS) and Indian Register of Shipping (IRS). A type-approval certificate confirms a specific BNWAS model has been tested against IEC 62616 and IEC 60945 and meets MSC.128(75) or MSC.355(92), identifying manufacturer, model, software revision, test laboratory, performance standard met, and validity period (typically 5 years subject to renewal). The IACS Procedural Requirement PR16 sets out the procedure including witness testing by class surveyors, documentation review and periodic renewal. Most major suppliers hold certificates from multiple class societies, allowing operators to demonstrate compliance regardless of vessel-flag.

PSC inspection: bridge test + reset stations + log

The PSC inspector’s BNWAS check covers carriage compliance against the V/19-2 threshold; type-approval certificate validity; operational mode (Auto while underway, verified at alarm-panel display and bridge log); reset-station functionality at each station; controlled Stage 1, 2, 3 demonstration in detailed inspections (alongside or at anchor with master’s permission); cabin-loudspeaker functionality in master’s, chief officer’s and designated additional crew cabins; bridge-log records of mode changes; manufacturer’s BNWAS logbook; and operator and installation manuals. Common deficiencies include reset-station push-button unserviceable, cabin-loudspeaker fault preventing Stage 3 reaching the master cabin, system in Off mode underway (a serious finding), Tr outside the 3 to 12 minute envelope, type-approval certificate missing or expired, master-only password lost, and GNSS or AIS interface fault preventing automatic Auto-mode triggering. Severe deficiencies (multiple cabin-loudspeaker failure, Off-while-underway, complete inoperative BNWAS) can lead to detention.

Tokyo MoU + Paris MoU detention codes 1316x

The Paris MOU and Tokyo MOU record SOLAS V/19-2 deficiencies under specific codes; Paris MOU navigation-equipment codes are in the 131xx series, with BNWAS-specific deficiencies typically under 13164 (Bridge Navigational Watch Alarm System) covering inoperative, missing or improperly used BNWAS. Tokyo MOU uses parallel harmonised codes. Detention is discretionary and typically reserved for cases where the BNWAS is missing entirely on a ship that should be fitted, completely inoperative, in Off mode while underway without documented justification, the cabin-loudspeaker chain fully inoperative, or multiple reset stations unserviceable. Less severe deficiencies are classified as “rectify within 14 days” or “rectify before next port”, with rectification evidenced on next-port follow-up.

Relationship to ISM Code Section 6 bridge procedures

The ISM Code Section 6 (Resources and Personnel) and Section 7 (Development of Plans for Shipboard Operations) require the operator to define and implement bridge procedures within the SMS. The SMS must define selection of Tr by route and operational context; conditions for Manual mode (port operations, alongside cargo work); conditions for Off mode (anchor or berth only); master’s authority to authorise mode changes; designated additional crew cabins for Stage 3; response procedures for Stage 3 (master’s response time, log entry, post-event assessment of OOW fitness); periodic test and verification; and training for new OOW. The procedures are auditable on operator internal audit, flag-State DoC and SMC audits, and PSC inspection. A common audit finding is misalignment between SMS-defined procedures and actual operating practice, most frequently masters defaulting to Manual mode in coastal pilotage waters without SMS justification.

Master + Chief Officer night-order interface

The master’s night orders (the “night-order book”) is the standing document by which the master communicates instructions to the OOW for night watches. BNWAS interacts with the night-order book in two ways. First, the orders typically specify the Tr setting (open-ocean Tr 10 minutes; coastal Tr 5 minutes; pilotage Tr 3 minutes or BNWAS in Manual on). Second, the orders specify when the OOW must call the master (visibility falling below 5 nautical miles; CPA within 1 nautical mile; departure from passage plan; mechanical or medical concern). A Stage 3 alarm creates automatic master-summoning that bypasses the OOW’s call discretion: regardless of whether the OOW would have called, the cabin alarm alerts the master and chief officer. For master and chief officer this is a defence against an OOW reluctant to call in marginal conditions; for the OOW it is a backstop closing the gap between policy and behaviour.

Wakashio 2020 limitation case study

The grounding of the Mitsui-OSK Lines bulk carrier MV Wakashio on Pointe d’Esny reef off Mauritius on 25 July 2020 is an instructive limitation case. The 203,130 DWT Capesize bulk carrier on ballast voyage Singapore to Brazil grounded approximately 2 nautical miles inshore of the Mauritius coast in clear weather, leading to a massive oil spill of approximately 1,000 tonnes of fuel oil as documented in MV Wakashio 2020 Mauritius oil spill. The Panama Maritime Authority investigation identified that the bridge team had deliberately deviated from the planned passage to gain mobile-phone signal close to shore, the ECDIS chart was set with anti-grounding alarms disabled, bridge-team awareness of distance-to-shore was inadequate, and the BNWAS was operational throughout. The OOW was actively engaged, the master was on the bridge during the period of approach, the reset cycle was being maintained, and Stage 1, 2, 3 alarms never escalated.

Wakashio illustrates the scope limitation of BNWAS: the system detects OOW absence, sleep, incapacitation and bridge desertion, but does not detect deliberate deviation, misjudgement, ECDIS misuse or BRM breakdown when the bridge is staffed and the reset cycle is being maintained. BNWAS is one of several layered defences; it does not substitute for ECDIS anti-grounding alarms, AIS proximity alarms, the master’s authority to override OOW decisions, or operator-level passage-planning discipline. The casualty has been widely cited in IMO BRM and bridge-procedure work since 2020 and in the 2024 alarm-prioritisation review.

Operational best practices for OOW

Best practice: reset deliberately rather than reflexively, with each reset accompanying a bridge-status assessment (radar scan, lookout sweep, position check); do not delegate reset to lookout or helmsman; use chartroom and bridge-wing reset stations during normal watchkeeping; record Tr in the bridge log at watch handover; respond promptly to Stage 1; do not silence Stage 2 by reset-and-ignore (reaching Stage 2 should prompt self-assessment of fatigue); call the master if Stage 2 is reached repeatedly; do not select Off without master authority; verify GNSS and AIS interfaces pre-watch (the MSC.355(92) automatic Auto-mode triggering depends on these inputs).

Formula, assumptions, and limits

This section provides the regulatory and quantitative anchor for the topic.

Formula

The regulatory and operational envelope is anchored by explicit numerical specifications under MSC.282(86), MSC.128(75), MSC.355(92) and IEC 62616:

GTmin⁡=150 for SOLAS V/19-2 application \text{GT}_{\min} = 150 \text{ for SOLAS V/19-2 application}

Tr∈[3,12] minutes (adjustable reset interval) T_{r} \in [3, 12] \text{ minutes (adjustable reset interval)}

Tstage 1 to stage 2≈15 seconds T_{\text{stage 1 to stage 2}} \approx 15 \text{ seconds}

Tstage 2 to stage 3≈90 seconds T_{\text{stage 2 to stage 3}} \approx 90 \text{ seconds}

Nalarm stages=3 N_{\text{alarm stages}} = 3

Cinstalled∈[2,500,8,000] USD C_{\text{installed}} \in [2{,}500, 8{,}000] \text{ USD}

The carriage thresholds are encoded as:

Passenger ships of any size+Cargo ships≥150 GT+HSC \text{Passenger ships of any size} + \text{Cargo ships} \geq 150 \text{ GT} + \text{HSC}

Entry into force: 1 July 2011 new builds; phased retrofit through 1 July 2014 \text{Entry into force: 1 July 2011 new builds; phased retrofit through 1 July 2014}

The escalation timeline from a missed reset to Stage 3:

Tescalation=Tr+Tstage 1 to stage 2+Tstage 2 to stage 3≈(3 to 12)+15s+90s T_{\text{escalation}} = T_{r} + T_{\text{stage 1 to stage 2}} + T_{\text{stage 2 to stage 3}} \approx (3 \text{ to } 12) + 15s + 90s

At Tr 3 minutes (180 seconds), total time from last reset to Stage 3 cabin alarm is approximately 285 seconds (~4 min 45 sec). At Tr 12 minutes (720 seconds), total time is approximately 825 seconds (~13 min 45 sec). Within this window the master and chief officer become aware of the bridge-vigilance failure and can respond.

Derivation

The 150 GT carriage threshold was set by reference to the small-cargo and short-sea casualty record. Below 150 GT the SOLAS application boundary is determined by Article I and Regulation 1 of SOLAS Chapter I; above 150 GT the cargo-ship category is fully within SOLAS for navigation-equipment purposes. The 150 GT threshold captures the small-cargo fleet on international voyages, exposed to single-watchkeeper bridge configurations and fatigue-related incapacitation events.

The 3 to 12 minute Tr range was derived from sleep-physiology evidence and operational watchkeeping practice. The 3-minute floor is the level below which the cycle becomes operationally intrusive. The 12-minute ceiling is set above the level at which an OOW could enter and exit a sleep state without triggering Stage 2; sleep-onset and sleep-awakening latencies in fatigued individuals are typically in the 5 to 15 minute range. The 15-second Stage 1 to Stage 2 interval reflects observation that an OOW returning from a brief side-task typically completes the round trip in under 15 seconds. The 90-second Stage 2 to Stage 3 interval reflects observation that a conscious OOW would respond to an audible alarm within seconds.

Assumptions

  • The BNWAS carried meets the performance standard applicable at its date of fitment (MSC.128(75) for early units, MSC.355(92) for units fitted from approximately 2014) and the corresponding IEC 62616.
  • The type-approval certificate issued by an IACS member society (or by another society recognised by the flag State) is valid and on board, and the equipment installation matches the type-approved configuration.
  • The BNWAS is in Auto mode whenever the ship is underway at sea, with the master’s mode selection logged.
  • The Tr setting is selected by the master by operational context and is recorded in the bridge log.
  • Reset stations are operationally functional, distributed per the manufacturer’s installation manual, and reachable from normal watchkeeping positions.
  • Cabin loudspeakers in master’s, chief officer’s and designated additional crew cabins are functional, with sound-pressure level sufficient to wake a sleeping officer.
  • The OOW is aware of the BNWAS, has been familiarised during ship induction, and resets deliberately during normal watchkeeping.
  • The SMS-defined bridge procedures align with ISM Code Sections 6 and 7 and STCW Chapter VIII rest-hour regime.

Worked example

A 15,000 DWT product tanker built in 2018 trades internationally and is subject to the V/19-2 carriage requirement (cargo ship of 3,000 GT and above built after 1 July 2011, MSC.355(92) BNWAS at delivery). The owner specifies a Furuno BR-500 at new-build, type-approved by NK and DNV, installed with four reset stations (port wing, starboard wing, chartroom, conning console) and four cabin loudspeakers (master, chief officer, second officer, chief engineer). Initial cost: USD 4,800 installed.

  • Singapore to Yokohama: master selects Auto; Tr 8 minutes for open-ocean Strait of Malacca and South China Sea; logged.
  • Approach Tokyo Bay: master reduces Tr to 4 minutes for high-traffic-density approach; logged.
  • Tokyo Bay pilotage: master switches to Manual on (pilot on board, master and chief officer on bridge with OOW).
  • Alongside Yokohama: master switches to Off after secure all-fast and pilot disembarked.
  • Yokohama to Long Beach: master reverts to Auto at sea; Tr 10 minutes for open-Pacific transit.

Annual operating cost: BNWAS verification is included in the annual class survey at no marginal cost; replacement push-buttons and loudspeaker cones cost approximately USD 100 to 200 per annum. Total 25-year life-cycle cost: approximately USD 4,800 (initial) + USD 7,500 (operating) + USD 1,500 (mid-life refurbishment) = approximately USD 13,800. The investment is justified by V/19-2 mandatory carriage; the operational benefit is the cabin-alarm escalation that brings the master to the bridge within 13 min 45 sec maximum from the last reset.

Edge cases and limits

  • OOW actively engaged but bridge-team breakdown: BNWAS does not detect bridge-team failure when the OOW performs the reset cycle. Wakashio 2020 is the canonical example.
  • OOW absent but lookout maintaining reset: a pathological case; PSC and operator audit rely on bridge log, VDR audio and CCTV (where fitted) to identify such events.
  • Tr at upper bound and OOW micro-sleep: at Tr 12 minutes an OOW could enter a brief sleep of 5 to 8 minutes and exit before Stage 2. Rationale for reducing Tr in approach and pilotage waters.
  • Cabin loudspeaker fault: a single failed loudspeaker limits Stage 3 alerting; detection at PSC or class survey is straightforward through demonstration.
  • Master selects Off mode underway: a serious deficiency; the BNWAS internal log records mode changes with timestamps and PSC can detect a recent Off-while-underway event. May trigger detention.
  • GNSS or AIS interface fault: where MSC.355(92) automatic Auto-mode triggering depends on GNSS or AIS, a fault may default to Manual; the master must take direct mode-selection responsibility.
  • Pilotage with pilot at the conn: BNWAS continues to operate; the master typically keeps Manual on so the alarm runs with master and chief officer also on the bridge.
  • Single-handed bridge below 150 GT: vessels below the threshold are not required to fit BNWAS but face equivalent fatigue exposure; voluntary fitment is prudent.
  • Polar trading: operate the BNWAS through the cold-temperature envelope; IEC 60945 covers polar operation but the unit must be specified for the cold range.
  • MASS Degree 3 / Degree 4: BNWAS as a bridge-vigilance device becomes inapplicable to autonomous ships with no OOW on board; the IMO MASS Code work stream is examining how the function transfers to remote-control-station and shore-control-centre environments.

Regulatory basis

  • SOLAS Chapter V Regulation 19-2 (Bridge Navigational Watch Alarm Systems), as inserted by MSC.282(86) 2009.
  • IMO Resolution MSC.282(86) (June 2009) Adoption of amendments to SOLAS introducing V/19-2.
  • IMO Resolution MSC.128(75) (May 2002) original BNWAS performance standard.
  • IMO Resolution MSC.355(92) (June 2013) current BNWAS performance standard.
  • IMO Assembly Resolution A.694(17) (1991) general requirements for shipborne radio equipment.
  • IEC 62616 Maritime navigation and radiocommunication equipment - BNWAS.
  • IEC 60945 General requirements, methods of testing and required test results.
  • IMO Resolution MSC.428(98) (2017) Maritime cyber risk management in safety management systems.
  • IACS Procedural Requirement PR16 Type Approval of Equipment.
  • STCW Convention Chapter VIII Standards regarding watchkeeping (rest hours and competence).
  • MLC 2006 Maritime Labour Convention, Title 2 hours of work and hours of rest.
  • ISM Code International Safety Management Code, Sections 6 and 7.

Common errors

  • Treating BNWAS as a fatigue-management substitute: BNWAS does not replace STCW Chapter VIII rest-hour compliance, MLC 2006 or operator fatigue-risk management.
  • Defaulting Tr to maximum 12 minutes: the upper bound should be selected only for low-traffic open-ocean transits; 12 minutes in coastal or pilotage waters is operationally inappropriate.
  • Selecting Manual mode in coastal pilotage without justification: the master may select Manual but must document the operational context; undocumented Manual selection is a recurring PSC finding.
  • Failing to record mode changes in the bridge log: every mode change should be logged with date, time, master’s authorisation and reason.
  • Ignoring repeated Stage 2 escalations: a pattern indicates OOW fatigue or attention-management failure; the master must address the root cause.
  • Treating cabin-loudspeaker test as optional: the Stage 3 cabin alarm is the principal value-add; a failed loudspeaker defeats the master-summoning purpose.
  • Assuming GNSS and AIS integration is universal: older MSC.128(75) units rely on master-side mode selection only.
  • Forgetting password recovery procedures: loss of the master-only password (master change-over without handover) can leave the system locked.
  • Fitting an unapproved BNWAS: only equipment with a current type-approval certificate is acceptable.
  • Treating PSC Stage 1 to Stage 3 demonstration as routine: the demonstration disturbs the master and chief officer cabins; inspectors typically request demonstration alongside or at anchor with a supplementary OOW on standby.

See also

References

The principal source for SOLAS V/19-2 carriage of BNWAS is the IMO consolidated text of the International Convention for the Safety of Life at Sea, 1974, as amended, with Regulation 19-2 of Chapter V supplying the carriage threshold for passenger ships of any size and cargo ships of 150 GT and above including HSC. The introducing instrument is IMO Resolution MSC.282(86), adopted at MSC 86 on 5 June 2009 under the SOLAS Article VIII tacit-acceptance procedure, deemed accepted on 1 January 2011 and entered into force on 1 July 2011. The performance-standard lineage is set out in IMO Resolution MSC.128(75) of May 2002 (the original voluntary standard) and IMO Resolution MSC.355(92) of June 2013 (the current standard, refining GNSS and AIS integration and tightening alarm characteristics). The horizontal performance standard for shipborne radio equipment and electronic navigational aids is IMO Assembly Resolution A.694(17) of November 1991, supplying the environmental, EMC and mechanical baseline. The cyber-risk-management framework is supplied by IMO Resolution MSC.428(98) of 2017. The international electrotechnical testing and conformance standard is IEC 62616, with the horizontal testing standard IEC 60945 establishing the baseline for shipborne electronic equipment. The classification-society implementation is set out in IACS Procedural Requirement PR16 Type Approval of Equipment, with type-approval certificates issued by IACS member societies (DNV, Lloyd’s Register, ABS, Bureau Veritas, ClassNK, RINA, Korean Register, China Classification Society, Russian Maritime Register of Shipping and Indian Register of Shipping) covering the principal manufacturers (Furuno, JRC, Kongsberg, Sperry Marine, Raytheon Anschutz, Tokyo Keiki, Imtech, Saab and others). Port-State-control enforcement is operated through the Paris Memorandum of Understanding and the Tokyo Memorandum of Understanding secretariats, with annual deficiency reports providing the principal evidence base. The casualty record informing the 2009 adoption includes the Australian Transport Safety Bureau report MAIR 243 on the MV Pasha Bulker grounding at Newcastle on 8 June 2007, the long line of UK MAIB reports on fatigue-related groundings, and the equivalent records of the US NTSB, the Norwegian Safety Investigation Authority and other flag-State bodies, aggregated in the IMO GISIS Marine Casualties and Incidents module. The limitation case study documented in the MV Wakashio grounding off Pointe d’Esny, Mauritius, on 25 July 2020 is reported by the Panama Maritime Authority and supporting flag-State inquiries, illustrating the scope boundary of BNWAS in the presence of an actively-engaged but mistaken bridge team. The interface to seafarer hours of work and rest is supplied by STCW Chapter VIII and MLC 2006 Title 2, implemented under the ISM Code Sections 6 and 7.

Related calculators