Simplified VDR (S-VDR)
A simplified VDR captures the same post-incident evidence as a full VDR — audio, radar image, AIS, heading and GPS — but with fewer mandatory data channels and a smaller capsule, which is why SOLAS accepts it only on cargo ships built before 2002 rather than on new construction.
Read more — Simplified VDR (S-VDR) explained ▾
What makes the simplified version different
A full Voyage Data Recorder logs a wide set of bridge parameters: radar video, ECDIS data, speed and depth, rudder and engine orders, wind, hull stress on some ships, and bridge audio from several microphones. The Simplified VDR (S-VDR) was created so that older cargo ships did not have to be rewired to collect data their original bridge instruments never produced. It still captures the core evidence needed after a casualty — date and time, ship's position, speed, heading, bridge audio, radio communications audio, radar data and AIS data — but drops parameters such as full ECDIS chart data, wind and hull stress that a full VDR carries. It is accepted only as a retrofit on existing cargo ships; new cargo ships must fit a full VDR.
Main components
Data acquisition unit
Collects and time-stamps signals from the gyro or heading sensor, GPS, radar, AIS transponder, echo sounder and bridge microphones, compresses the audio and radar image, and passes the combined stream to the recording capsule.
Final recording medium (capsule)
A fixed or float-free protective capsule, built to survive fire, shock and deep submersion, stores at minimum the last 48 hours of data in a continuous loop. Float-free capsules carry a locating beacon and release automatically if the ship sinks.
Bridge microphones and interface unit
At least one microphone covers the main conning position; the interface unit multiplexes sensor signals and provides the playback interface used by investigators, normally accessed by an authorised technician rather than the crew.
Selection and retrofit considerations
Because an S-VDR is fitted to an existing bridge, the deciding factors are compatibility rather than raw capacity:
- Availability of a suitable NMEA or serial output from the existing gyro, GPS and echo sounder, since older instruments may need an interface converter.
- Capsule type, fixed or float-free, and hull location clear of interference with existing structure.
- Whether the ship's AIS unit already outputs the data fields the S-VDR needs to log without modification.
- Power supply arrangement, since the capsule must run from an uninterruptible source that survives a main power failure for at least two hours.
Regulations and class
SOLAS Chapter V Regulation 20 sets the carriage requirement; cargo ships of 3,000 gross tonnage and upwards constructed before 1 July 2002 were permitted to fit an S-VDR instead of a full VDR. IMO Resolution MSC.163(78) and the related performance standard set the minimum data set and the 48-hour recording capacity. Class requires an annual performance test by an approved technician, checking that all required data channels are actually being recorded and that the capsule can be recovered and played back, with the results recorded in the ship's certificate.
Typical faults
| Fault | Consequence |
|---|---|
| Microphone gain drifted or channel dead | Bridge audio missing or unintelligible in the recording, a common annual test failure |
| Interface converter fault on an old sensor feed | One or more required data channels stop recording without an obvious alarm |
| Capsule battery for the locating beacon expired | Float-free capsule will not transmit its position if released after a casualty |
| Data overwritten before retrieval after an incident | Evidence lost because the continuous loop recorded over the event before the capsule was saved |
| UPS battery failed | Recording stops during the power failure that is often exactly when it is needed most |
What to look for in a supplier
- Technician certified by the VDR manufacturer to carry out the annual performance test, not a general electronics contractor.
- Experience integrating older bridge instruments typical of pre-2002 tonnage, since the interfacing work is where most S-VDR problems originate.
- Stock of replacement capsules and beacons compatible with the installed model, given these units are eventually discontinued by the maker.
- A clear procedure for securing the data after an incident, including how quickly the capsule can be downloaded before the loop recording overwrites it.
Test the bridge audio channel by talking normally from the actual conning position, not next to the microphone; annual tests have been passed on a system that could not pick up a watch officer's voice from where he actually stands.
11 manufacturers · 12 models
Danelec Marine
2- Sensor, antenna or transducer fault, typically indicated by missing, unstable or implausible navigation data
- Power-supply or processor failure, typically indicated by blank display, rebooting or unavailable function
- Network/interface fault, typically indicated by missing data on connected bridge systems or communication alarms
- Cable/connector corrosion or water ingress, typically indicated by intermittent operation or signal loss
- Recording/storage or software fault on recorder-type equipment, typically indicated by data gaps, recording alarms or failed playback
- Sensor, antenna or transducer fault, typically indicated by missing, unstable or implausible navigation data
- Power-supply or processor failure, typically indicated by blank display, rebooting or unavailable function
- Network/interface fault, typically indicated by missing data on connected bridge systems or communication alarms
- Cable/connector corrosion or water ingress, typically indicated by intermittent operation or signal loss
- Recording/storage or software fault on recorder-type equipment, typically indicated by data gaps, recording alarms or failed playback
AMI Marine
1- Sensor or interface failure causes missing channels, invalid data or system alarms
- Microphone or audio-interface faults cause missing bridge or radio audio in the recording
- Storage-media or protected-capsule faults cause recording alarms or gaps in retained data
- Network, serial or power-supply faults cause intermittent acquisition, restart or loss of recording
- Incorrect time synchronization or configuration causes misaligned or incorrectly identified recorded data
Consilium Marine
1- Loss of electrical, hydraulic, pneumatic, fluid, or other service supply from a protection trip, leakage, blockage, or upstream fault results in failed starting or loss of function
- Mechanical wear, corrosion, fouling, or contamination of moving and wetted parts causes increased noise, leakage, sticking, vibration, or reduced performance
- Seal, gasket, hose, cable, or connection deterioration from age, heat, vibration, or environmental exposure produces visible leakage, intermittent signals, or loss of pressure
- Sensor, switch, actuator, relay, or control-system faults cause incorrect indication, nuisance alarms, failed automatic sequences, or loss of remote control
- Incorrect adjustment, assembly, or maintenance leads to unstable operation, recurrent alarms, or performance that differs from the vessel's normal baseline
Furuno
1- Sensor or antenna degradation caused by contamination, damage, ageing or poor exposure can produce missing, unstable or implausible data
- Connector, cable or network faults caused by vibration, corrosion or disturbed terminations can cause intermittent data loss or interface alarms
- Power-supply or internal electronics failure caused by ageing, heat or poor ventilation can result in resets, blank indications or complete loss of function
- Configuration or software errors after service or replacement can cause incorrect data, rejected inputs or loss of communication with other bridge equipment
- Mechanical damage or water ingress at exposed components can lead to erratic readings, repeated alarms or loss of the affected channel
Hyundai Welding
1- Sensor, antenna or transducer fault, typically indicated by missing, unstable or implausible navigation data
- Power-supply or processor failure, typically indicated by blank display, rebooting or unavailable function
- Network/interface fault, typically indicated by missing data on connected bridge systems or communication alarms
- Cable/connector corrosion or water ingress, typically indicated by intermittent operation or signal loss
- Recording/storage or software fault on recorder-type equipment, typically indicated by data gaps, recording alarms or failed playback
JRC
1- Loss of electrical, hydraulic, pneumatic, or other service supply caused by a tripped protection device, leakage, blockage, or upstream fault results in failed starting or loss of function
- Mechanical wear, corrosion, fouling, or contamination of moving and wetted parts causes increased noise, leakage, sticking, vibration, or reduced performance
- Seal, gasket, hose, cable, or connection deterioration from age, heat, vibration, or environmental exposure produces visible leakage, intermittent signals, or loss of pressure
- Sensor, switch, actuator, relay, or control-system faults can cause incorrect indication, nuisance alarms, failed automatic sequences, or loss of remote control
- Incorrect adjustment, assembly, or maintenance can lead to unstable operation, recurrent alarms, or performance that differs from the vessel's normal baseline
Kelvin Hughes
1- Recording or storage failure caused by disk, memory, processor or software faults, resulting in recorder alarms or missing data channels
- Power-supply failure caused by breaker, converter or wiring faults, resulting in loss of the equipment or repeated restarts
- Network or interface failure caused by damaged cabling, port faults or configuration changes, resulting in loss of data to connected systems
- Display, processor or control failure caused by hardware or software faults, resulting in frozen indications, alarms or unavailable functions
- Incorrect configuration or time, position or sensor input caused by setup or upstream faults, resulting in misleading or incomplete information
L3 Technologies
1- Recording or storage failure caused by disk, memory, processor or software faults, resulting in recorder alarms or missing data channels
- Power-supply failure caused by breaker, converter or wiring faults, resulting in loss of the equipment or repeated restarts
- Network or interface failure caused by damaged cabling, port faults or configuration changes, resulting in loss of data to connected systems
- Display, processor or control failure caused by hardware or software faults, resulting in frozen indications, alarms or unavailable functions
- Incorrect configuration or time, position or sensor input caused by setup or upstream faults, resulting in misleading or incomplete information
Netwave
1- Sensor, camera or input failure causes missing data, blank images or channel alarms
- Power-supply, UPS or network faults cause system restart, loss of recording or unavailable remote status
- Storage-media or recorder faults cause gaps in retained data or failed self-tests
- Incorrect time, configuration or interface data causes inconsistent records or false alarms
- Control, acknowledgment or communication faults cause unavailable watchkeeping or security functions
Rutter
1- Sensor, antenna or transducer fault, typically indicated by missing, unstable or implausible navigation data
- Power-supply or processor failure, typically indicated by blank display, rebooting or unavailable function
- Network/interface fault, typically indicated by missing data on connected bridge systems or communication alarms
- Cable/connector corrosion or water ingress, typically indicated by intermittent operation or signal loss
- Recording/storage or software fault on recorder-type equipment, typically indicated by data gaps, recording alarms or failed playback
Samsung Heavy Industries
1- Recording or storage failure caused by disk, memory, processor or software faults, resulting in recorder alarms or missing data channels
- Power-supply failure caused by breaker, converter or wiring faults, resulting in loss of the equipment or repeated restarts
- Network or interface failure caused by damaged cabling, port faults or configuration changes, resulting in loss of data to connected systems
- Display, processor or control failure caused by hardware or software faults, resulting in frozen indications, alarms or unavailable functions
- Incorrect configuration or time, position or sensor input caused by setup or upstream faults, resulting in misleading or incomplete information