Human factors, alarms, bridge ergonomics, and integration
What the exam tests
This domain tests alarm management, bridge layout and integration. It asks whether the human watchkeeper can detect, understand and act on the information the instruments provide.
Core rules
Alarms should be prioritized by consequence, grouped by system, and presented consistently. A central alarm panel on the bridge should identify the system and location; repeated nuisance alarms must be corrected, not permanently inhibited. BNWAS supports watchkeeping but does not replace a lookout. ECDIS, radar, AIS and conning displays should be arranged so that primary navigation information is visible without excessive movement or mode confusion. Night lighting must preserve night vision. Integration must fail safely: a sensor failure should be indicated, not hidden. Procedures should define who responds to machinery, fire and navigation alarms.
Worked example
A bilge alarm repeats every watch because a level sensor is fouled. The crew silence it each time. This is an alarm-management failure: the sensor should be cleaned or replaced, the alarm tested, and the temporary response recorded. If the alarm is inhibited to stop the noise, the bridge loses the flooding warning. The correct fix is maintenance and a risk assessment, not a permanent inhibit.
Traps
Do not treat more alarms as better safety. Do not use color alone to show alarm priority. Do not let an ECDIS route or AIS target override a visual lookout. Do not accept an integrated bridge where a single display failure removes heading, position and alarm indication without a backup.