SOLAS Chapter V Regulation 19.2.2.3 has required a Bridge Navigation Watch Alarm System on essentially every cargo ship over 150 gross tons and every passenger vessel since 1 July 2011, with phased retrofit deadlines closing through July 2014. The compliance language sounds simple. The alarm chain that confirms the officer of the watch is awake and alert is the alarm chain that confirms the officer of the watch is awake and alert. The hardware behind that chain is more specific than most procurement specs assume.

A BNWAS is not a single black box. It is a dormant timer, a conning-station indicator, an audible escalation network, a set of weather-rated reset push-buttons, and a cascade alarm path into the master and back-up officer cabins. Specifying it as one part number hides the moving parts that actually drive type-approval, watch ergonomics, and total installed cost. This guide breaks the system into the layers a bridge engineer or fleet superintendent actually procures.

Why Does Every SOLAS Bridge Need a BNWAS?

The bridge navigation watch alarm system exists because casualty investigations kept identifying the same failure mode. A sole officer on a quiet night watch, a comfortable chair, a warm wheelhouse, and a darkened ECDIS screen. The vessel runs straight at autopilot for hours while the watchstander becomes incapacitated by fatigue, a medical event, or simple distraction. The 2003 Tricolor collision and several earlier passenger-ferry incidents pushed IMO to act, and Resolution MSC.282(86) formalized the BNWAS requirement at IMO MSC 86.

The functional intent is narrow. A BNWAS does not detect collisions, it does not navigate, and it does not replace lookout duties. It detects an absent OOW. If the bridge alarm system observes no operator interaction for a configured dormant period, it escalates through audible alarms first on the bridge, then in the master and back-up officer cabins, until someone responds. That is the entire job.

From a hardware standpoint, that narrow job creates four design constraints. The system has to run independently of the autopilot and the ECDIS so a frozen application cannot mask the dormancy. It has to be visible at every watch station, including a darkened wheelhouse and a sunlit bridge wing. The reset action has to be deliberate so a chart click or a coffee cup cannot cancel the dormant timer accidentally. And the cascade alarms have to physically wake people in cabins, which means real sound pressure levels and indicator lamps at the bedhead. Each of those constraints maps to a specific device and a specific cable run inside a modern integrated bridge system.

What Stages Does a BNWAS Cycle Through During the Watch?

IEC 62616 defines the staged alarm sequence that every type-approved BNWAS must implement. The timing is configurable, but the structure is fixed and worth specifying clearly because each stage drives different hardware behavior.

Stage 1 is the dormant period itself. The system arms when the vessel is under way and the BNWAS is set to Automatic or On. The dormant timer runs between 3 and 12 minutes, with 12 minutes as the IMO upper bound. During this interval the system is silent. The officer of the watch is presumed to be performing nav duties such as managing chart scale, scanning radar, or monitoring traffic, and the BNWAS does not interrupt that work.

Stage 2 is the visual indication. When the dormant timer expires, a flashing visual alarm appears at the conning station only. There is no audible component yet. The visual signal gives the alert OOW a quiet chance to reset without involving the wider bridge. The hardware here is a daylight-readable indicator at the helm, usually integrated into the bridge alarm panel or carried on a dedicated BNWAS HMI.

Stage 3 is the bridge audible alarm. Fifteen seconds after the visual alarm, an audible tone sounds on the bridge. This is the moment that confirms an OOW is either present and overdue on a reset, or genuinely unresponsive. Sound pressure has to be high enough to overcome ambient noise from VHF, engine vibration carried into the wheelhouse, and HVAC.

Stage 4 is the back-up officer alarm. If the bridge alarm is not reset within an additional period, typically 90 seconds, the audible alarm cascades to the back-up officer and the master cabins. After a further escalation interval, usually 3 minutes total, the alarm extends to additional crew alerting points such as the engine control room and the chief officer cabin. The reset has to be performed at the bridge, by physical operator interaction. ECDIS clicks and radar interactions only count as resets if they are explicitly wired and type-approved as reset sources, which they often are not. For OOWs already managing chart scale through a coastal watch, the BNWAS reset must be a separate, deliberate action.

What Hardware Actually Sits Behind the BNWAS Panel?

A compliant BNWAS installation has five hardware layers, and a clean procurement spec calls out each one separately rather than rolling them into a single line item.

The first layer is the central BNWAS controller. This is the IEC 62616 type-approved device that runs the dormant timer, drives the staged alarms, accepts reset inputs, and signals VDR. It is the unit that classification societies actually inspect. The controller typically sits in the bridge equipment cabinet behind the helm console and communicates over discrete wiring or NMEA 0183 to the rest of the bridge.

The second layer is the conning-station alarm panel. This is the device the OOW sees at the helm. It includes the visual stage-2 indicator, the audible stage-3 alarm, and a reset push-button. The visual indicator has to be readable in direct sunlight on a clear day with the wheelhouse blinds open, and dim enough for night-watch use without destroying dark-adaptation. That means an indicator driven by a bridge display capable of at least 1,000 nits sustained, with proper night-mode dimming.

The third layer is the bridge-wing reset units. SOLAS V/19 specifically requires reset capability accessible from the conning position and from each bridge wing. On large vessels with open wings, that means weather-rated push-buttons mounted at the pilot stations on each side. Bridge wings see direct salt spray, rain washdown, and UV exposure, so the housings must clear the ingress-protection thresholds that separate splash-rated and washdown-rated marine hardware. IP66 is the minimum sensible bar, and IP67 is preferable for wings that catch green water.

The fourth layer is the cabin alarm units. These are the audible-plus-visual alerts in the master cabin and the back-up officer cabin, with extension into the chief officer cabin and engine control room when the vessel configuration calls for it. The audible has to be loud enough to wake someone through a closed cabin door, which means the sounder must be specified for the cabin layout, not generic. The visual lamp serves the deaf or hearing-protected crew member.

The fifth layer is the power and supervision wiring. The BNWAS must run on the vessel main 24 VDC bus with an emergency switchboard fallback so a partial blackout does not silently disable the watch alarm. Supervision wiring runs back to the bridge alarm management system so a cut cable to a wing reset unit raises a fault, not a silent failure.

How Should BNWAS Integrate With the Rest of the Bridge?

BNWAS does not live in isolation. It plugs into VDR, alarm management, ECDIS, and the operator-display layer. Each of those integration points is also a hardware decision.

The VDR interface is mandatory. SOLAS V/20 already requires a voyage data recorder on most vessel classes, and the BNWAS state has to be one of the data items the VDR captures, alongside ECDIS, gyro, radar, and engine telegraph. Investigators rely on the BNWAS log to reconstruct watch behavior after an incident. The wiring is typically a discrete contact closure plus NMEA sentence, and the BNWAS controller must support both.

The alarm management integration is where vessels with central alarm panels run into trouble. A central bridge alarm management system can display BNWAS alarms, but it must not be the sole annunciator. The IEC 62616 type approval specifically requires that the BNWAS audible and visual annunciation work without the alarm management system, because the alarm management system itself can fail. That is a wiring rule, not a software rule.

The ECDIS and radar tie-in is the most commonly misconfigured part. Many bridge teams assume that touching ECDIS or moving a radar cursor resets the BNWAS. It only does so if the BNWAS controller has been type-approved with those inputs as recognized reset sources, and only when those inputs are physically wired to the BNWAS controller. Without that, the OOW must press a dedicated reset button. This is a deliberate design choice, because a stuck-on radar trackball or a frozen ECDIS would otherwise silently mask an incapacitated officer.

The display-layer integration is the most visible to the OOW. Whether the BNWAS state appears on a dedicated indicator panel or on one of the bridge multifunction displays, the underlying hardware must keep that state visible regardless of which application has focus. That is one of the reasons commercial bridges run dedicated, type-approved marine bridge displays rather than retasking general-purpose monitors. The display chain has to survive a single application crash without losing the BNWAS readout.

Where Should a BNWAS Hardware Upgrade Start?

Most BNWAS hardware in service today was installed during the 2011 to 2014 retrofit window. That equipment is now 11 to 14 years old, which is past the typical service life for electrolytic capacitors in alarm controllers and well past the OEM software support horizon for many controllers. A practical upgrade audit covers four checks before any new hardware is ordered.

Verify the current dormant timer setting and the reset path. Confirm that the dormant period matches the operator company watch policy and that the reset really requires deliberate OOW action. Walk the cable runs to each wing reset unit and confirm the supervision wiring still raises a fault on disconnect. Test each cabin alarm with the cabin door closed and the HVAC running, with the duty officer in the bunk. Confirm the IEC 62616 type-approval certificate is current for the installed controller and that the classification society has not flagged it as superseded at the next periodical survey.

From there, the BNWAS upgrade lines up naturally with a broader bridge modernization plan. Replacing the BNWAS controller alone is the cheapest option. Replacing the controller along with the alarm panel, wing reset units, and the conning-station display chain at the same time produces a coherent watch-alarm layer that will survive the next type-approval cycle and the next classification society inspection.

Frequently Asked Questions

Which vessels are required to carry a BNWAS?

SOLAS Chapter V Regulation 19.2.2.3 requires a BNWAS on cargo ships of 150 gross tons and upward and on passenger ships of any size built on or after 1 July 2011. Existing vessels were phased in between 2012 and 2014 depending on tonnage. Smaller domestic vessels not subject to SOLAS may still be required to carry one by flag-state regulation or class society rule.

What standard governs the equipment design?

IEC 62616 is the performance standard for BNWAS equipment, building on IMO Resolution MSC.128(75) and the operational requirement in SOLAS V/19. Type-approval testing under IEC 62616 covers the staged alarm timing, the reset behavior, the cabin cascade, and the interface to VDR and bridge alarm systems. Most classification societies certify against IEC 62616 plus IEC 60945 environmental conditions for marine electronics.

Can ECDIS or radar interaction reset the BNWAS automatically?

Only when the ECDIS or radar is wired into the BNWAS controller as a recognized reset source and the combined installation is type-approved that way. Otherwise the BNWAS reset must come from a dedicated push-button. Most controllers ship without automatic ECDIS or radar reset enabled because a stuck cursor would otherwise mask an incapacitated officer.

How long is the dormant period typically set to?

Between 3 and 12 minutes, configurable in 1-minute steps, with 12 minutes as the IMO upper bound. Most commercial operators set the dormant period at the longer end during open-ocean transit and shorten it during coastal or pilot waters. The chosen interval should match the operator company watchkeeping policy and be documented in the safety management system.

Does the BNWAS need its own power supply?

The BNWAS runs from the vessel main 24 VDC bus with an emergency-switchboard fallback. A short main-bus interruption must not silently disable the watch alarm, so the controller has internal hold-up plus emergency-bus feed. Cabling supervision raises a fault if a reset-unit cable is cut, so the alarm is never quietly defeated by a damaged conductor.

Who has authority to enable or disable the BNWAS?

Only the master, by direct action through a protected mode-selection on the BNWAS controller. The mode change is logged and reported to the VDR. Bridge officers cannot disable the system from the conning station, and the alarm cannot be silenced for longer than the next stage interval. The system arms automatically when the vessel is under way and Auto mode is selected.