During a blackout drill the examiner asks you, as chief mate, to explain the emergency generator: what it powers, where it is located, how it starts, and when it must start automatically.

A. EMERGENCY GENERATOR — CHIEF MATE's KNOWLEDGE: SOLAS REQUIREMENT: SOLAS II-1/43 requires all vessels to have an emergency source of electrical power capable of supplying essential services. LOCATION: The emergency generator must be located ABOVE the bulkhead deck (above the waterline) and outside the machinery space — ensuring it remains operational if the main engine room is flooded or on fire. WHAT IT POWERS (Emergency Switchboard): (1) Navigation lights; (2) Internal communication — PA system, general alarm; (3) Emergency lighting — escape routes, muster stations; (4) Fire detection and fixed fire-fighting systems; (5) Day tank level gauges; (6) Emergency bilge pump; (7) Steering gear emergency supply; (8) GMDSS equipment; (9) AIS and VDR. STARTING REQUIREMENT: SOLAS requires the emergency generator to start automatically within 45 seconds of main power failure. The emergency switchboard receives power within this time. TESTING: SOLAS requires monthly testing under load and quarterly testing of automatic start and transfer. The emergency generator should run for at least 30 minutes under load. CHIEF MATE KNOWLEDGE: must know the location on the vessel, how to manually start it if auto-start fails (typically by key or pushbutton in the emergency generator room), and what equipment it powers.

B. The emergency generator is tested only at annual survey. The chief engineer is responsible for its maintenance and testing — the chief mate has no need to know its location or starting procedure.

C. The emergency generator powers all the same equipment as the main generators. There is no restriction on what can be connected to the emergency switchboard — it is a full backup for all ship's power.

D. Emergency generators are only required for passenger vessels. Cargo ships are required only to have a battery backup for navigation lights and internal communications.

A. BRIDGE ENGINE REMOTE CONTROL — PRINCIPLES AND TESTING: OPERATING PRINCIPLE: Modern vessels have a telegraph system that allows the bridge to command propulsion from three positions: (1) Bridge wing (port and starboard); (2) Bridge centre console (primary); (3) Engine room local control (manual override). The system typically uses an electronic or electro-pneumatic telegraph — the bridge moves the telegraph lever and the engine room control room (or automated system) responds with matching engine movement. REMOTE CONTROL TYPES: (a) Bridge full control: bridge moves engine telegraph → ECR or UMS system automatically adjusts fuel injection, ahead/astern valve, and RPM; (b) Telegraphed control: bridge signals intention, engine room carries out manually; (c) CPP (Controllable Pitch Propeller): blade pitch changes rather than engine RPM — bridge pitch lever directly adjusts thrust. PRE-DEPARTURE TEST: (1) Notify engine room of impending test; (2) Test both bridge wing controls and centre console — move telegraph full range ahead/stop/astern; (3) Confirm ECR repeater matches bridge telegraph position; (4) Test emergency stop function; (5) Confirm steering gear tested (SOLAS V/26 — 12 hours before departure); (6) Log all tests with times; (7) Confirm with chief engineer "engines ready for manoeuvring."

B. Bridge engine control is tested only at drydock. Between drydocks, the engineer officer of the watch is solely responsible for engine operations and the chief mate has no role in engine testing.

C. The bridge telegraph is advisory only. The engine room carries out all engine movements independently — the bridge telegraph is a communication tool, not a control system.

D. Engine testing before departure is done by increasing to full ahead for 5 minutes then stopping. Other tests are the chief engineer's responsibility and are covered by the SMS.

A. UMS ALARM — BRIDGE OOW/CHIEF MATE RESPONSIBILITIES: UMS BACKGROUND: SOLAS II-1/46-54 and the UMS Code (MSC/Circ.645) allow machinery spaces to be operated without continuous manning when the vessel meets prescribed equipment and alarm standards. The engineer is on call, not in the machinery space. OOW BRIDGE ACTIONS ON UMS ALARM: (1) ACKNOWLEDGE the alarm on the bridge alarm panel — this stops the audible alarm but keeps the visual; (2) RECORD: alarm type, time, and acknowledge time in the logbook; (3) CONTACT the duty engineer officer — give the alarm description and location; (4) MONITOR the alarm: if a second alarm follows rapidly (cascade alarms), or if a HIGH PRIORITY alarm activates (blackout, main engine shutdown, steering failure) — take immediate navigational action as appropriate; (5) DO NOT SILENCE AND IGNORE: the alarm system requires that alarms are responded to — an unresponded-to alarm triggers escalation to the next person on the call list; (6) HIGH PRIORITY ALARMS: main engine slowdown/shutdown → notify master, consider navigational implications (vessel now drifting or under reduced power); (7) Document all alarms, response times, and engineer actions taken in the UMS alarm log. CHIEF MATE UNDERSTANDING: must know which alarms require navigational response vs engineering response.

B. All UMS alarms are exclusively the duty engineer's responsibility. The bridge OOW should silence the alarm and wait for the engineer to respond — there is no bridge action required.

C. Wake the master for every UMS alarm. Only the master has authority to decide whether a UMS alarm requires action at night — the OOW should not make this assessment.

D. UMS alarms can be safely ignored for 30 minutes before escalation. The engineer's call response time is 30 minutes under SOLAS and the OOW should not contact the engineer before this period expires.