Ship Subsystems & EngineeringSkipssystemer og maskinteknikk · Engineering system cardTeknisk systemkort

Shipboard Identification, Tracking, and Bridge Logging Systems

These four SOLAS Chapter V systems integrate local collision avoidance, global vessel tracking, casualty forensics, and bridge watchkeeper supervision.

min readmin lesing
24
wordsord
5,112

#AIS#LRIT#VDR#Bridge Systems

Part 1: System cardDel 1: Systemkort

1. Core Function

These four SOLAS Chapter V systems integrate local collision avoidance, global vessel tracking, casualty forensics, and bridge watchkeeper supervision1. Class A AIS continuously broadcasts vessel identity, position, and course/speed kinematics over VHF for surrounding traffic awareness3. LRIT transmits closed, access-controlled satellite position reports at least every six hours to authorized States for global maritime domain awareness2. VDR and S-VDR capture bridge audio, sensors, and display imagery in protected capsules for accident investigation4. BNWAS monitors Officer of the Watch (OOW) alertness via preset timers and cascading alarms to warn of incapacitation1.

2. Primary Operational Tasks

  • Execute autonomous local VHF ship-to-ship and ship-to-shore data exchange for collision avoidance, Vessel Traffic Services (VTS) monitoring, and Aids to Navigation (AtoN) broadcasting3.
  • Deliver automated, scheduled global satellite vessel tracking reports (identity, latitude/longitude, date and time) via closed governmental data networks to Flag, Coastal, Port, and Search and Rescue (SAR) authorities2.
  • Continuously record bridge communications, navigation sensor telemetry, and raw radar/ECDIS imagery onto protected fixed, float-free, and/or long-term storage media to preserve casualty evidence4.
  • Supervise Officer of the Watch (OOW) alertness on the bridge via configurable dormancy countdowns that escalate from local bridge alerts to remote officer cabin and crew alarms if unacknowledged1.
  • Support emergency distress localization and watch escalation through post-sinking acoustic pinging, float-free homing beacons, AIS safety messaging, and optional immediate bridge Emergency Call activation1.

3. System Interconnections

Inputs: Sensor, audio, video, and control feeds converge across these bridge systems via IEC 61162-1/2 (NMEA 0183), IEC 61162-450 Ethernet, CAN bus, binary telemetry relays, and video frame grabbers10. Class A AIS ingests GNSS position and UTC timing, gyrocompass heading, rate-of-turn data, speed/course feeds, and manual voyage/static entries via its Minimum Keyboard and Display (MKD) or onboard peripherals6. LRIT takes ship identity, latitude/longitude position, and date/time2 (the cited regulatory texts define these transmitted parameters rather than specifying underlying GNSS input wiring). MSC.333(90) VDR Data Acquisition Units (DAUs) record 20 defined data items (several conditional on shipboard fit): date and time, GNSS position, speed, heading, multi-track bridge microphones (conning and wings), VHF 1 and 2 audio, X- and S-band radar video (via DVI/VGA/LAN frame grabbers), ECDIS display imagery and route data, echo sounder depth, main alarms, rudder and engine orders/responses, hull openings, watertight and fire door status (binary relays), accelerations, wind, rolling, and AIS10. BNWAS takes heading/track control (autopilot) status for Automatic mode, illuminated reset pushbuttons, Passive Infrared (PIR) motion sensors where accepted by Class, and contact, equivalent-circuit, or serial reset signals from external bridge equipment at proper-lookout positions1.

Outputs: Class A AIS broadcasts unencrypted VHF TDMA packets (Messages 1–3, 5, 27, and safety/binary messages) while outputting target data via IEC 61162 (NMEA 0183) to radar, ECDIS, and the VDR3. LRIT routes closed satcom transmissions via Inmarsat or Low-Earth Orbit (LEO) Iridium constellations through Communication and Application Service Providers (CSPs/ASPs) to entitled Flag, Coastal, Port, and SAR Data Centres governed by the IMO Data Distribution Plan (DDP)9. MSC.333(90)-compliant VDRs write simultaneously to fixed, float-free, and long-term media (while S-VDRs write to a fixed or float-free protective capsule)4; upon vessel sinking, a fixed capsule emits an underwater acoustic pinger signal, while a float-free capsule activates an EPIRB homing signal (including a 406 MHz COSPAS-SARSAT EPIRB and AIS homing transmitter in commercial units)4. BNWAS triggers a bridge flashing visual indication, Stage 1 bridge audible alarm, Stage 2 remote audible alarm in the backup officer and/or Master cabin, and Stage 3 remote audible alarm at locations of further crew members capable of taking corrective action (acting as crew-wide watch escalation rather than necessarily activating the ship-wide SOLAS General Emergency Alarm, though non-passenger ships may sound Stage 2/3 across all remote locations simultaneously), plus malfunction outputs to any central alarm panel1.

4. Redundancy & Criticality

SOLAS Chapter V establishes tiered carriage mandates, tamper-protection controls, and emergency power provisions, enforced through mandatory annual testing for AIS and VDR2.

System

SOLAS Chapter V Carriage Mandate

Tamper-Proof & Security Rules

Emergency Power & Survival Backup

AIS (Class A)

Regulation V/19.2.4: All ships ≥300 GT on international voyages; cargo ships ≥500 GT not on international voyages; all passenger ships irrespective of size2.

No cryptographic RF authentication or encryption3; annual test verifies static programming and sensor links2; switch-off allowed only at Master discretion if safety/security is compromised19.

Supplied from shipboard power; no standalone internal battery backup duration is specified in the cited SOLAS Chapter V or AIS technical standards.

LRIT

Regulation V/19-1: Passenger ships (incl. HSC), cargo ships (incl. HSC) ≥300 GT, and MODUs on international voyages; exempt if AIS-fitted exclusively in Sea Area A12.

Closed DDP restricts access to authorized States9; switch-off restricted to data-protection agreements or exceptional Master safety/security cases, requiring log entry and Administration notice2.

Type-approved under SOLAS V/19-1 and GMDSS Regulation IV/1431; no separate standalone LRIT battery endurance period is specified in the cited MSC.263(84) or SOLAS V/19-1 texts.

VDR / S-VDR

Regulation V/20: Full VDR for passenger ships and cargo ships ≥3,000 GT built ≥1 Jul 2002; S-VDR for cargo ships ≥3,000 GT built <1 Jul 200210.

Must prevent physical/electronic manipulation or deletion and log any interference attempt4. Hardened fixed capsule resists fire, shock, and deep-sea pressure4.

Main and emergency ship power4, plus dedicated reserve battery powering bridge audio for 2 hours before automatic shut-off4. Under MSC.333(90), fixed ULB pings ≥90 days; float-free homing runs ≥48 hours over ≥168 hours4.

BNWAS

Regulation V/19.2.2.3: Cargo ships ≥150 GT and all passenger ships irrespective of size; must operate whenever underway at sea27.

Mode selection and dormancy timer locked to Master access only; continuous activation of any reset device cannot prolong dormancy or suppress alarms1.

Ship's main power supply, with a battery-maintained supply powering malfunction/power-fail indication and any Emergency Call facility (exact hour endurance not fixed in MSC.128(75))1.

Part 2: Technical deep diveDel 2: Teknisk dybdeanalyse

1. AIS (Class A) Architecture & SOTDMA

Class A shipborne AIS transceivers are governed by IMO Resolution MSC.74(69) Annex 3, Recommendation ITU-R M.1371, and type-testing standard IEC 61993-2, operating across the 156.025–162.025 MHz VHF maritime mobile band with 25 kHz channel spacing5. Normal ship-to-ship and ship-to-shore messaging uses two dedicated simplex channels carved from marine VHF channels 87 and 88: AIS 1 at 161.975 MHz (Channel 87B / 2087) and AIS 2 at 162.025 MHz (Channel 2088)3. Class A stations also require Digital Selective Calling (DSC) on 156.525 MHz (VHF Channel 70), and broadcast Long-Range AIS position reports (Message 27) every 3 minutes on VHF Channels 75 (AIS3) and 76 (AIS4) for satellite reception unless suppressed by a controlling base station group assignment message5. According to technical vendor specifications and explainers, Class A radio transmissions run at 12.5 W (versus 2 W for Class B "CS" and 5 W for Class B "SO") using Gaussian Minimum-Shift Keying (GMSK) at 9,600 bps, spectrum-filtered to stay within the 25 kHz channel mask3.

To prevent RF collisions without central shore coordination, Class A transceivers employ Self-Organizing Time Division Multiple Access (SOTDMA)3. Each 60-second frame on a channel is divided into 2,250 time slots—yielding 4,500 slots per minute across AIS 1 and AIS 2, aligning with the IEC 4,500-report/min design requirement above the IMO 2,000-report/min minimum5. Every slot spans 256 bits (approximately 26 ms at 9,600 bps) and is synchronized tightly to Coordinated Universal Time (UTC) using the connected GNSS receiver as the primary timing reference20. Most AIS messages occupy a single slot, though multi-part transmissions can take up to five consecutive slots17. In autonomous SOTDMA operation, each mobile unit continuously listens to the VHF Data Link (VDL) to map occupied slots within radio range, selects free slots, and announces in advance which slot it will use next so surrounding ships avoid transmitting simultaneously3. Under heavy traffic congestion, SOTDMA degrades deliberately rather than failing while Class A maintains transmission priority; by contrast, Class B "CS" units using Carrier-Sense TDMA (CSTDMA) listen for a quiet slot before transmitting and may remain silent in congested harbors, causing small craft to disappear from displays while large vessels stay visible3.

Alongside SOTDMA for periodic position reports, the AIS link layer uses three complementary TDMA access schemes and supports Autonomous, Assigned (via base-station Message 16/23), and Polled/Interrogated (Message 15) operating modes5:

  • ITDMA (Incremental TDMA): Allocates slots for periodic transmissions whenever a reporting interval changes (such as during vessel speed changes) and supports non-periodic scheduled transmissions such as Message 523.
  • RATDMA (Random Access TDMA): Handles non-periodic, ad hoc transmissions such as Message 5 static/voyage reports, safety-related broadcasts (Messages 12 and 14), and interrogation responses (Message 3)23.
  • FATDMA (Fixed Access TDMA): Used by coastal base stations (Message 20 Data Link Management) to pre-announce and reserve fixed slot schedules that mobile units avoid, as well as by transmit-only Aids to Navigation17.

AIS partitions shipboard data into static, voyage-related, and dynamic categories transmitted at distinct intervals driven by vessel speed and course-change sensors over IEC 61162-1/2 (NMEA 0183 at 4,800 or 38,400 bps) and IEC 61162-450 Ethernet interfaces6.

AIS Data Category & Message ID

Principal Parameters

Access Scheme

Nominal Reporting Interval (Class A)

Static Data (Message 5)

Vessel name, call sign, IMO number, length/beam dimensions (plus MMSI)6

RATDMA, ITDMA

Every 6 min, upon data amendment, or when interrogated23

Voyage-Related Data (Message 5)

Draught, cargo, port of destination, ETA (manual entry)6

RATDMA, ITDMA

Every 6 min, upon data amendment, or when interrogated23

Dynamic Data — At anchor/moored, ≤3 kn (Messages 1, 2, 3)

Position, COG, SOG, true heading, Rate of Turn (ROT), nav status3

SOTDMA / RATDMA / ITDMA

Every 3 min23

Dynamic Data — At anchor/moored, >3 kn (Messages 1, 2, 3)

Same real-time sensor telemetry

SOTDMA / RATDMA / ITDMA

Every 10 s23

Dynamic Data — Underway 0–14 kn (Messages 1, 2, 3)

Same real-time sensor telemetry

SOTDMA / RATDMA / ITDMA

10 s (not changing course) / 3 1/3 s (changing course)23

Dynamic Data — Underway 14–23 kn (Messages 1, 2, 3)

Same real-time sensor telemetry

SOTDMA / RATDMA / ITDMA

6 s (not changing course) / 2 s (changing course)23

Dynamic Data — Underway >23 kn (Messages 1, 2, 3)

Same real-time sensor telemetry

SOTDMA / RATDMA / ITDMA

2 s (not changing course or changing course)23

Long-Range Position Report (Message 27)

Position, COG, SOG, navigational status only (VHF Ch 75/76)6

Autonomous outside base coverage

Every 3 min6

Every Class A transceiver must include a dedicated, type-approved Minimum Keyboard and Display (MKD) alongside multiple input-output ports and a single output interface, distinguishing it from Class B units that lack an MKD requirement17. Through IEC 61162 / NMEA 0183 connections, the Class A transponder exchanges data with onboard peripherals so AIS target symbols can be overlaid directly onto radar and ECDIS displays while manually entered voyage details are supplied to the broadcast17.

Beyond vessel transponders, AIS supports physical and Virtual Aids to Navigation (AtoNs) via Message 21, broadcast autonomously every 3 minutes (occupying up to two slots, or assigned via Message 16) by buoy/beacon stations or integrated into fixed shore stations23. Hardware implementations include Type 1 transmit-only FATDMA stations (which cut power consumption by omitting VDL receive periods), Type 2 FATDMA stations with a receiver for remote configuration, and Type 3 transceive-capable units supporting either FATDMA or autonomous RATDMA slot allocation (with typical AtoN transmission ranges of 5–15 nautical miles per manufacturer guidance)34. For floating physical AtoNs (Virtual AtoN flag = 0), Message 21 provides an off-position indicator triggered against configured guard zones when the UTC time stamp is 59 or below43. When a station sets the Virtual AtoN flag = 1 with dimensions defaulted to A=B=C=D=0, Message 21 places a charted synthetic navigational mark on vessel displays where no physical buoy exists—classified across 32 AtoN type codes aligned with the IALA Maritime Buoyage System and named using 20 base characters plus up to 14 additional 6-bit ASCII characters in the extension field3.

2. LRIT vs. AIS

Long-Range Identification and Tracking (LRIT) under SOLAS V/19-1 and IMO Resolution MSC.263(84) complements AIS by overcoming VHF line-of-sight range constraints and unauthenticated open broadcasting2. Rather than transmitting continuously to nearby traffic, an LRIT-compliant shipborne terminal automatically transmits a concise satellite position report containing three fields—ship identity, latitude/longitude position, and the date and time of that position—at a standard cadence of at least every 6 hours, which authorized authorities can adjust/poll down to 15-minute intervals2.

LRIT functions as a closed, access-controlled governmental network rather than a public RF broadcast7. Each transmission travels from Shipborne Equipment via Satellite to a Communication Service Provider (CSP), onward to an Application Service Provider (ASP), and into authorized LRIT Data Centres (DCs) interconnected across international exchange routing governed by the IMO Data Distribution Plan (DDP) server9. Routing intermediaries inspect only message headers during exchange7. Under DDP rules, Flag States, Coastal States (entitled to receive LRIT reports for vessels within 1,000 nautical miles of their coastlines, provided this does not infringe another country's territory), Port States, and Search and Rescue (SAR) authorities receive data strictly according to their defined entitlements7 (granular DDP port-call entitlement triggers are not detailed in the cited summaries).

Satellite geometry directly governs LRIT terminal selection across GMDSS sea areas. Vessels fitted with AIS that operate exclusively within VHF coastal Sea Area A1 are exempt from LRIT carriage2. Ships operating in Sea Areas A2 and A3 predominantly rely on geostationary Inmarsat terminals (such as Inmarsat-C)2. However, Inmarsat-C does not support polar Sea Area A4 above 70 degrees latitude25. Vessels operating in Sea Area A4 therefore require an Administration-approved non-Inmarsat terminal utilizing a Low-Earth Orbit (LEO) CSP network25; vendor and distributor technical datasheets identify Iridium LRIT terminals as the compliant pole-to-pole Sea Area A4 solution25.

Although Satellite-AIS (S-AIS) receivers in orbit now detect Class A Message 27 and standard VHF broadcasts from space, S-AIS suffers from fundamental RF physics: ships 500 nautical miles apart cannot hear each other's terrestrial SOTDMA reservations, so they may transmit in the same time slot—which works locally on the surface, but causes simultaneous packet collisions at the orbital receiver where neither message can be decoded3. LRIT avoids VHF slot contention altogether through scheduled satellite communications7.

Feature / Dimension

Class A AIS (Terrestrial & S-AIS)

LRIT (SOLAS V/19-1 / MSC.263(84))

Primary Purpose

Tactical collision avoidance, VTS traffic management, AtoN marking3

Strategic maritime domain awareness, security, SAR7

Transmission Medium & Band

VHF maritime mobile band (161.975 / 162.025 MHz; Ch 75/76 for Msg 27)3

Satellite (Inmarsat for A2/A3; LEO Iridium for polar A4 >70° lat.)25

Effective Coverage

Line-of-sight VHF (~5–15 nm AtoN baseline); S-AIS degraded by >500 nm orbital slot collisions3

Global pole-to-pole coverage (with LEO terminal in Sea Area A4)25

Update Cadence

Dynamic: 2–10 s underway, 3 min anchored; Static/Voyage: 6 min6

Standard: at least every 6 hours; pollable down to 15 minutes8

Access & Security Model

Open, unencrypted, unauthenticated broadcast; zero verification3

Closed, access-controlled governmental routing governed by DDP7

Core Data Payload

Identity, kinematics, dimensions, draught, cargo, destination, ETA6

Ship identity, latitude/longitude position, date and time of position2

Authorized Shutdown Rules

Master discretion only if safety/security compromised; restart once danger passes19

International data-protection agreements or exceptional Master safety/security case; must log and notify Administration without undue delay2

3. VDR & S-VDR (Voyage Data Recorder)

Shipborne Voyage Data Recorders under SOLAS Chapter V Regulation 20 preserve a tamper-resistant record of bridge commands and vessel parameters for casualty investigation4. Passenger ships and cargo vessels of 3,000 GT and upwards constructed on or after 1 July 2002 require a Full VDR, while cargo ships of 3,000 GT and upwards built before 1 July 2002 were retrofitted (between 2006 and 2010 per industry training references) with a Simplified VDR (S-VDR) under IMO Resolution MSC.163(78) (later amended by MSC.493(104))10. Because older ships lacked standardized digital sensor buses, S-VDRs record fewer channels (for example, AIS is optional alongside radar) and store 12 hours in legacy configurations14. Full VDRs installed before 1 July 2014 follow IMO Resolution A.861(20) (as amended by MSC.214(81), 12-hour retention), whereas every full VDR installed on or after 1 July 2014 must meet revised IMO Resolution MSC.333(90) (and IEC 61996-1 Edition 2, amended by MSC.494(104))11.

The central architectural requirement of MSC.333(90) is a three-part Final Recording Medium—combining a Fixed Recording Medium, a Float-Free Recording Medium, and an internal Long-Term Recording Medium—such that access to any one medium enables full data recovery and playback4. According to marine engineering service documentation referencing MSC.333(90) and IEC 61996-1 testing, the external fixed protective capsule (bolted to the monkey island or wheelhouse top in high-visibility fluorescent orange housing with retro-reflective markings) must withstand a 1,100°C fire test for 1 hour, a 260°C low-temperature fire test for 10 hours, 6,000 m ocean depth (60 MPa) hydrostatic pressure for 30 days, and 50g mechanical impact shock / 1-ton puncture drop pin4. Its integral Underwater Locator Beacon (ULB) acoustic pinger is mandated under MSC.333(90) to emit pings for at least 90 days once submerged, powered by a lithium battery pack with a typical 3–6 year replacement life per service guides10. Alongside it, the external float-free capsule sits in a Hydrostatic Release Unit (HRU) bracket; service literature indicates automatic detachment at 1.5–4 m depth if the vessel sinks, activating an integral EPIRB (compliant with Resolution A.810(19)26, specified in vendor guides as a 406 MHz COSPAS-SARSAT EPIRB and AIS homing transmitter10) that transmits a homing signal for at least 48 hours over a period of not less than 7 days (168 hours)4.

Recording Medium (MSC.333(90))

Minimum Rolling Retention

Post-Termination Data Survival

Recovery & Location Aids

Fixed Protective Capsule

At least 48 hours4

At least 2 years4

High-visibility orange housing, retro-reflective material, ≥90-day ULB acoustic pinger4

Float-Free Capsule

At least 48 hours4

At least 6 months4

HRU release (1.5–4 m depth), EPIRB homing signal (≥48 h over ≥168 h), grappling and recovery features4

Long-Term Recording Medium

At least 30 days (720 hours)4

Not specified separately in cited MSC.333(90) summary (built into non-removable DAU memory)11

Accessible from bridge DAU / main CPU enclosure following non-sinking incidents4

Under MSC.333(90), the VDR Data Acquisition Unit (DAU) captures 20 defined data items (several recorded only where shipboard equipment is fitted) across IEC 61162-1/2 (NMEA 0183) serial lines, IEC 61162-450 high-speed Ethernet, digital contact closures, CAN bus links, binary telemetry relays, and DVI/VGA/LAN frame grabbers10. Captured streams encompass date and UTC time, GNSS position (GLL/GGA), speed (VBW), gyro true heading (HDT), echo sounder depth, main bridge alarms, rudder and engine orders and responses, hull openings, watertight and fire door status relays, accelerations, wind, rolling, and AIS traffic data, paired with multi-track bridge audio (conning and bridge wing microphones) and separate VHF 1 and 2 radio communications channels10. Visual situational awareness is preserved via high-resolution X- and S-band raw radar screen captures and primary ECDIS screen streaming (plus active route data), both sampled at a minimum rate of 1 frame every 15 seconds per engineering guidance10.

Data-integrity clauses in MSC.333(90) prohibit altering or deleting recorded data and mandate logging any attempt to interfere with data integrity or recording4. Operating from both main and emergency shipboard power4, the VDR must switch seamlessly on total electrical blackout to a dedicated reserve power source (typically a 24V DC battery backup per service guides10) to continue recording Bridge Audio for 2 hours, after which all recording must cease automatically to protect the prior voyage window4.

Under SOLAS Chapter V Regulation 18, every VDR and S-VDR must undergo an Annual Performance Test (APT) performed by an approved testing or servicing facility, with a Certificate of Compliance retained on board2. The APT verifies accuracy, duration, and recoverability across all sensor, audio, and video channels; performs a live reserve-battery discharge test verifying 2-hour audio operation and automatic shut-off timing; checks ULB transducer output/frequency and battery expiry; inspects HRU release mechanisms; and executes a formal examination of MSC.333(90) float-free capsules in accordance with MSC.1/Circ.1040/Rev.12.

4. BNWAS (Bridge Navigational Watch Alarm System)

Adopted under IMO Resolution MSC.128(75) (tested to IEC 62616) and mandated by SOLAS V/19.2.2.3 (added via Resolution MSC.282(86)), BNWAS monitors OOW activity to trigger timely warnings if the watchkeeper becomes incapacitated by accident, illness, or security breaches such as piracy or hijacking1. Carriage applies to all passenger ships irrespective of size and cargo ships of 150 GT and upwards, and the system must be in operation whenever the ship is underway at sea (with Administration discretion to exempt installations fitted prior to 1 July 2011 from full compliance)2.

MSC.128(75) mandates three operational modes, with both operational mode selection and dormant period duration strictly security-protected and restricted to Master access only1:

  • Automatic: Automatically brought into operation whenever the ship's heading or track control system is activated, and inhibited when that system is not activated1.
  • Manual ON: Operates constantly regardless of steering mode1.
  • Manual OFF: Inhibited under all circumstances1.

When active, the BNWAS enters a dormant period (Td) configurable between 3 and 12 minutes (typically adjustable in 1-minute increments in setup mode per manufacturer manuals), achieving all specified timings within an accuracy of 5% or 5 seconds, whichever is less1. If no valid reset occurs before Td expires, the escalating alarm sequence initiates1:

Alarm Stage

Elapsed Time Trigger

Target Zone & Signal Type

Operational Characteristics & Variants

Visual Indication (Stage 0)

At Td (3–12 min)

Bridge operational positions (flashing visual signal)

Silent pre-warning visible from all operational positions on the bridge1

Stage 1 Audible Alarm

Td + 15 s

Bridge interior (audible alarm)

Characteristic tone/modulation designed to alert without startling the OOW1

Stage 2 Remote Alarm

Td + 30 s (15 s after Stage 1)

Back-up officer's and/or Master's location

Urgent, easily identifiable remote alarm loud enough to wake sleeping officers1

Stage 3 Remote Alarm

Td + 120 s (90 s after Stage 2)

Locations of further crew members capable of taking corrective action

On non-passenger vessels, Stage 2 or Stage 3 may sound across all remote locations simultaneously (omitting separate Stage 3 if Stage 2 sounds in all); on larger vessels, Stage 2-to-3 delay may be set up to 3 minutes (180 s) upon installation1

An optional Emergency Call facility allows bridge personnel to immediately activate Stage 2 (followed by Stage 3) remote alarms without waiting for Td1. While ship's main power supplies routine operation, MSC.128(75) requires a battery-maintained supply to power both the system malfunction/power-failure indication (repeatable on any central alarm panel) and all elements of the Emergency Call facility1.

Valid reset rules under MSC.128(75) guard against accidental or fraudulent cancellation. A reset requires a single operator action—defined as activating a hard-key or soft-key including any necessary cursor movement—which cancels all active visual/audible warnings and restarts a full dormant period1. Resets must only be possible from physical bridge locations providing a proper lookout (conning position, navigating/manoeuvring workstation, monitoring workstation, and bridge wings)1. Integral reset pushbuttons must be uniform, night-illuminated, and positioned preferably adjacent to visual indications, while continuous activation of any reset device must never prolong the dormant period or suppress the alarm sequence1.

On valid reset triggers, industry implementation varies between pushbuttons, motion sensors, and workstation interfaces. Many commercial BNWAS units integrate PIR motion sensors alongside illuminated pushbuttons15, yet manufacturer documentation explicitly warns that Lloyd's Register does not accept motion sensors as a valid reset device, requiring LR-classed vessels to operate without active PIR resets22. Regarding radar or ECDIS interaction, MSC.128(75) expressly permits external reset inputs via contacts, equivalent circuits, or serial data from other bridge equipment at proper-lookout positions capable of registering physical activity and mental alertness (including hard-key/soft-key and cursor actions)—enabling integrated bridge consoles such as radar or ECDIS workstations to reset the timer when wired appropriately—though the cited IMO text and vendor installation manuals specify these interfaces generically at the equipment/serial-contact level rather than detailing radar- or ECDIS-specific trigger protocols1.

5. Failure Modes, Cybersecurity & Compliance

Because these four bridge systems couple physical sensors, open RF links, and human watchkeeping discipline, hardware defects and crew workarounds create both navigational hazards and major Port State Control (PSC) exposure.

AIS Vulnerabilities and Voyage Data Faults: AIS has zero cryptographic security—no authentication, no encryption, and no verification—relying entirely on participants transmitting honestly3. Consequently, its open VHF channels (161.975 and 162.025 MHz) are inherently exposed to spoofing and fabricated identity or position broadcasts3. Routine data corruption is equally pervasive: because voyage-related fields (draught, cargo, destination, ETA) depend on manual entry, un-updated crew entries degrade traffic accuracy, while missing or failed external sensors such as a gyrocompass cause the transponder to transmit "not available" fields6. Unauthorized shutdowns outside strict Master safety/security exceptions obscure vessel tracking19, while satellite AIS reception loses packets to >500 nm orbital slot collisions and Class B "CS" craft drop off screens in congested ports3.

VDR Recording Blind Spots and Recovery Failures: A VDR failure often remains invisible until an investigation or APT exposes missing streams. Because the DAU multiplexes up to 20 separate serial, Ethernet, relay, audio, and video inputs, any disconnected NMEA wire, silent conning/bridge-wing microphone, dead VHF audio tap, or frozen DVI/VGA radar/ECDIS frame grabber leaves a gap in the casualty record10. On recovery hardware, critical failure points include exhausted reserve batteries (failing the mandatory 2-hour post-blackout audio requirement), expired ULB acoustic pinger batteries (3–6 year replacement window per service guides), out-of-date HRUs on float-free capsules, and compromised capsule fixings, junction boxes, or cable seals10.

BNWAS Sensor Blind Spots and Deliberate Bypasses: Where PIR motion sensors are installed, passive motion detection cannot confirm OOW mental alertness and depends on physical line-of-sight placement (one reason Lloyd's Register rejects PIRs as valid reset triggers22); poorly placed sensors or reset buttons outside proper-lookout zones violate MSC.128(75) ergonomics1. More severely, marine inspection guidance compiling Paris MoU findings reports frequent deliberate defeats by bridge teams, including taped-over motion sensors, disconnected buzzers, reset buttons rigged within reach of a chair, unlocked mode selectors, and systems switched off while underway at sea57.

Port State Control (PSC) Inspection & Detention Risk: Paris MoU and Tokyo MoU inspections use harmonized five-digit THETIS deficiency codes under Area 10 (Safety of Navigation)58. Under updated inspection guidelines (Paris MoU PSCC59/2026/03 of June 2026 and IMO Resolution A.1206(34)), Tokyo MoU continues recording detainable deficiencies with action code 30, whereas Paris MoU marks detainable items using a "grounds for detention" indicator rather than numeric code 3061. In a compiled industry analysis of Paris MoU inspection records published by Marine Inspection, BNWAS leads all navigation deficiencies in detention severity at 26.5% (480 detentions across 1,811 deficiencies) because PSCOs treat a bypassed or disabled watch alarm as a fundamental watchkeeping failure rather than a minor equipment fault, while VDR carries a 13.0% detention ratio (383 detentions across 2,949 deficiencies)57.

System

Harmonized PSC Code

Detention Risk (Compiled Industry Analysis of Paris MoU Data)

Core PSCO Onboard Inspection Checks

AIS

1011358

Not separately ranked in cited industry top-8 list57

Current annual test report on board (SOLAS V/18); accurate static programming and sensor data exchange (GNSS, gyro); radio frequency and on-air VTS verification2.

VDR / S-VDR

1011460

13.0% (383 detentions / 2,949 deficiencies)57

Valid Annual Performance Test (APT) Certificate of Compliance (SOLAS V/18); active error-free recording; in-date ULB pinger, HRU, and 2-hour reserve battery; MSC.1/Circ.1040/Rev.1 float-free exam2.

LRIT

1013760

Not separately ranked in cited industry top-8 list57

Type-approved LRIT terminal compliant with MSC.263(84) and SOLAS V/19-1; active 6-hour transmission compliance and Administration/log records for any switch-off (non-compliance risks denial of port or territorial entry)2.

BNWAS

1013860

26.5% (480 detentions / 1,811 deficiencies — highest among nav items)57

Continuous operation underway; Master-locked mode/timer controls; physical inspection against taped PIRs, disconnected buzzers, or relocated buttons; documented periodic testing of Stage 1, 2, and 3 alarms1.

References

  1. MSC.128(75) (adopted on 20 May 2002) Performance Standards for, https://wwwcdn.imo.org/localresources/en/KnowledgeCentre/IndexofIMOResolutions/MSCResolutions/MSC.128(75).pdf
  2. International Convention for the Safety of Life at Sea (SOLAS), 1974, https://www.imorules.com/solas/06_chapter_V.html
  3. AIS: How Ships Broadcast Position, and Where It Breaks Down, https://bigoceandata.com/ais-explained/
  4. RESOLUTION MSC.333(90) (adopted on 22 May 2012) ADOPTION, https://wwwcdn.imo.org/localresources/en/KnowledgeCentre/IndexofIMOResolutions/MSCResolutions/MSC.333%2890%29.pdf
  5. OPERATOR'S MANUAL, https://www.furuno.it/docs/OPERATOR%20MANUALOME44900C_FA170.pdf
  6. AIS Fundamentals, https://www.spglobal.com/content/dam/spglobal/mi/en/documents/general/research-analysis/840090525_0222_MT_MAT_AIS-Fundamentals_Brochure_Final_LowRes.pdf
  7. Long Range Identification & Tracking System (Main) | PDF - Scribd, https://www.scribd.com/document/1037186085/01-Long-Range-Identification-Tracking-System-Main
  8. App. 9 - Guidelines for PSC related to LRIT - RiSK4SEA, https://risk4sea.com/psc-wiki-risk4sea/appendices/guidelines-for-psc-related-to-lrit/
  9. Understanding the LRIT System Architecture & the Flow of Data, https://captainsmode.com/understanding-lrit-system-architecture/
  10. Voyage Data Recorder (VDR): Fixed & Float-Free Capsules, APT, https://seanavmarine.org/voyage-data-recorder-vdr-capsule-installation-apt/
  11. SOLAS VDR Compliance & Annual Performance Test Guide, https://marineinspection.app/blog/solas-voyage-data-recorder-vdr-compliance-test-guide
  12. Audi's ASM Oral Notes - Final | PDF - Scribd, https://www.scribd.com/document/769154313/Audi-s-ASM-Oral-Notes-Final
  13. Circular N.º 46 - DGRM, https://www.dgrm.pt/documents/20143/87524/C_46_EN+%281%29.pdf/45c57f23-3f7a-c6f3-e58e-bb79485420d2
  14. VDR Full Training - DM Technical Training-1 - 240313 - 081744, https://www.scribd.com/document/715932556/VDR-Full-Training-DM-Technical-Training-1-240313-081744
  15. X150 BNWAS Installation Manual - Iss02 Rev02, https://www.brommeland.no/file/standardmappe-uni/0801-x150-bnwas-installation-manual-iss02-rev02.pdf
  16. Recommendation ITU-R M.1371-4, https://www.itu.int/dms_pubrec/itu-r/rec/m/R-REC-M.1371-4-201004-S!!PDF-E.pdf
  17. IALA GUIDELINE 1082 AN OVERVIEW OF AIS Edition 1.0, https://www.e-navigation.nl/sites/default/files/1082-Ed.2-Overview-of-AIS_June2016-1.pdf
  18. jrc-handbook-2015.pdf, https://www.fcmarine.co.uk/wp-content/uploads/2017/11/jrc-handbook-2015.pdf
  19. FA-150 - Seattle.gov, https://www.seattle.gov/documents/departments/pscsc/findings/furunofa150operatorsmanual.pdf
  20. Marine AIS | CML Microcircuits, https://cmlmicro.com/wp-content/uploads/2026/06/WP_AIS.pdf
  21. A200 AIS Class A / Inland transceiver, https://www.brommeland.no/file/standardmappe-uni/em-trak-a200-user-manual-v2.pdf
  22. BNWAS Navgard Installation Manual D12 | PDF - Scribd, https://www.scribd.com/document/685711137/BNWAS-Navgard-Installation-Manual-D12
  23. about_ais - Nauticast Automatic Identification Systems AIS, https://www.nauticast.com/bg/cms/about_ais
  24. Marine Circular MC-2/2008/11/12/4 - Tuvalu Ship Registry, https://tvship.com/resources/downloads/circulars/mc%202-2008-11-12-4_v6_lrit.pdf
  25. long range identification and tracking of ships (lrit), https://maritimenaoero.com/content/resources/circulars/nma_c8_lrit_rev2.pdf
  26. Annual Testing of Voyage Data Recorders - INSB Class, https://insb.gr/technicalnotice/solas-annual-testing-of-voyage-data-recorders/
  27. GUIDELINES, https://lk.rs-class.org/regbook/getDocument2?type=rules3&d=31894F53-B790-42C2-9D44-FC5F50748A23&f=2-030101-053
  28. SOLAS V/19 bridge equipment carriage requirements, https://alsafwanmarine.com/academy/navigation-radio-vdr/solas-chapter-v-bridge-equipment
  29. SOLAS V Carriage Requirements for Ships | PDF | Radar | Tonnage, https://www.scribd.com/document/801592218/Bridge-Equipment-Requirement
  30. MN-2-011-25 - REPUBLIC OF THE MARSHALL ISLANDS, https://www.register-iri.com/wp-content/uploads/MN-2-011-25.pdf
  31. Iridium LRIT CONFORMANCE TESTING, https://static.mackaycomm.com/wp-content/uploads/2021/08/Pole_Star_LRIT-Iridium-ConformTest-Overview_datasheet_MackayIrd_0212_LR.pdf
  32. Technical Information - Text Version - | ClassNK - English, https://www.classnk.or.jp/hp/en/tech_info/tech_text.aspx?techno=664
  33. Regulation 19 - Carriage Requirements for Shipborne Navigational, https://media.liscr.com/marketing/liscr/media/liscr/online%20library/maritime/solas%20v_reg19.pdf
  34. How each product works, http://www.allaboutais.com/index.php/en/technical-info/how-each-product-works-technically
  35. IALA Guideline No. 1028 On The Automatic Identification System, https://www.e-navigation.nl/sites/default/files/universal-automatic-identification-ais-volume-1-part-1-operational-issues-1028.pdf
  36. FA-170 AIS Operator's Manual | PDF | Menu (Computing) - Scribd, https://www.scribd.com/document/382506459/FA170-Operators-Manual-A
  37. about_ais - Nauticast Automatic Identification Systems AIS, https://www.nauticast.com/bv/cms/about_ais
  38. Ais Reporting Intervals - Ais Decoder, https://arundaleais.github.io/docs/ais/ais_reporting_rates.html
  39. ais for aton - quick guide - Sabik, https://sabik.com/wp-content/uploads/2024/11/sabik_marine_quick_guide_1_ais_for_aton_2019.pdf
  40. Marine Electronics - Furuno, https://www.furuno.com/files/Brochure/GC2026_EN.pdf
  41. AIS Technology in Digital Yacht Products Explained, https://digitalyacht.co.uk/wp-content/uploads/2017/10/AIS-Training-V1_01.pdf
  42. AIS Aids to Navigation (ATON) Report (Message 21) - uscg navcen, https://navcen.uscg.gov/ais-aton-report
  43. Message 21: Aids-to-navigation report (AtoN), https://navcen.uscg.gov/sites/default/files/pdf/AIS/ITU-R_M1371-3_AIS_Msg_21.pdf
  44. GP Rating Course Overview and Benefits | PDF | Communication, https://www.scribd.com/document/718961548/Gp-Rating-Handouts-Merge-final
  45. JUE-87 - JRC World, https://www.jrc-world.com/files/secured/docuware_documents/303-SatcomC+JRC+JUE-87+Instruction+Manual++1-2-2023.pdf
  46. MSC 2020-21 - International Maritime Organization, https://www.imo.org/en/knowledgecentre/indexofimoresolutions/pages/msc-2020-21.aspx
  47. Voyage Data Recorder requirements - Danelec Newsroom, https://www.danelec.com/newsroom/voyage-data-recorder-regulations-and-performance-standards
  48. Annex - Guidelines on Annual Testing of VDR and S-VDR, https://imorules.com/GUID-E7FBA379-98BD-423E-9EF1-6DD3D1106194.html
  49. Marine Operations Note: 03/2023 - Voyage Data Recorder, SVDR, https://www.liscr.com/marketing/liscr/media/liscr/online%20library/maritime/marine-operations-note-03_2023.pdf
  50. Automated Vulnerability Scanning and Security Audit Framework for, https://pearl.plymouth.ac.uk/context/secam-theses/article/1554/viewcontent/2025vineethaharish10761543phd.pdf
  51. JCY-1900 1950 Service Manual Ed2 | PDF | Electricity - Scribd, https://www.scribd.com/document/605409187/JCY-1900-1950-Service-Manual-ed2
  52. NetWave NW6000 Installation, Operation And Maintenance Manual, https://www.manualslib.com/manual/2199681/Netwave-Nw6000.html
  53. IEC 62616 - iTeh Standards, https://cdn.standards.iteh.ai/samples/17534/5a8dda2be77f4a878d3bc7536981a769/IEC-62616-2010.pdf
  54. OPERATOR'S MANUAL, https://www.furuno.it/docs/OPERATOR%20MANUALOME44610G4_BR500.pdf
  55. TOR-BNW User Manual for BNWAS System | PDF - Scribd, https://www.scribd.com/document/925408704/12-BNWAS-User-Manual
  56. JCX-161 161 - ManualLib, https://www.manuallib.com/download/2023-10-19/JRC%20Bridge%20Navigational%20Watch%20Alarm%20System%20JCX-161%20Instruction%20Manual.pdf
  57. SOLAS Chapter V Navigation Safety Inspection Checklist, https://marineinspection.app/article/solas-chapter-v-navigation-safety-inspection-checklist
  58. Paris MoU – Overview of Deficiency Codes 01 July 2024, https://maritime.public.lu/dam-assets/fsi/paris-mou-overview-of-deficiency-codes-01-july-2024.pdf
  59. Tokyo MOU Deficiency Code List | PDF | Oil Tanker - Scribd, https://www.scribd.com/document/853533033/Tokyo-MOU-Deficiency-Codes-December-2024
  60. Paris MoU – Overview of Deficiency Codes 01 July 2023, https://maritime.public.lu/dam-assets/circulaires/2024/list-of-paris-mou-deficiency-codes.pdf
  61. PSC deficiency codes explained: what each code means - Fleetward, https://www.fleetward.io/guides/psc/deficiency-codes-explained
  62. Port State Control Deficiency Codes | PDF | Water Transport - Scribd, https://www.scribd.com/document/532621818/Port-State-control-deficiency-codes
  63. Port State Control Deficiency Codes | PDF | Water Transport - Scribd, https://es.scribd.com/document/532621818/Port-State-control-deficiency-codes