VDES and NAVDAT: the Next Generation of Digital Maritime Communications
VDES extends existing AIS/VHF data exchange and was adopted as a future shipborne alternative to AIS from 2028; NAVDAT remains a separate MF/HF broadcast system under development, without a SOLAS carriage requirement.
Operational Explanation
MSC 111 introduced VDES into the IMO framework as a shipborne alternative for meeting AIS requirements, with expected entry into force on 1 January 2028. VDES includes AIS capability and expands the speed, security and scope of ship-to-ship and ship-shore digital exchange; maritime VHF already supported data services, so this is not a change from a previously voice-only channel.
NAVDAT is a separate MF/HF shore-to-ship digital broadcast project. The public IMO account of NCSR 12 documents work in progress, not a SOLAS carriage requirement or a certain approval date. Any later NCSR 13 or MSC 112 outcome should be attributed only to a published instrument or report.
SOLAS IV/7.1.4 requires receiver arrangements capable of receiving MSI and SAR-related information throughout the voyage. Amendments on dissemination through all operational RMSS concern providers and States: they neither require a shipborne receiver for each RMSS nor make a missed warning acceptable. The ship must carry approved equipment and services suitable for the sea areas and intended voyage.
Regulatory Reference
MSC 111: VDES introduced as a shipborne alternative to AIS, with expected entry into force on 1 January 2028; revised performance standards and onboard operational guidelines. MSC.496(105), SOLAS IV/7.1.4: receiver or receivers capable of receiving MSI and SAR-related information throughout the voyage. NCSR 12: progress on NAVDAT, without a SOLAS carriage requirement. Applicable rules and services must be checked against adopted instruments, equipment approval and voyage sea areas.
NAVDAT already has performance standards under MSC.569(109), adopted in 2024. Adoption of technical standards does not establish a carriage requirement or demonstrate service availability along the route. Check approved equipment, services and applicable rules separately before changing MSI/GMDSS arrangements. IMO MSC.569(109).
The report by PRS, a participant at NCSR 13 in June 2026, records an updated NAVDAT roadmap and nine priority actions. This is implementation progress, not a new SOLAS carriage requirement or a guaranteed service-availability date. PRS: NCSR 13 report.
For VDES, the IMO index identifies MSC.592(111) for introduction into the regulatory framework and MSC.593(111) for performance standards. Separately verify entry into force of the SOLAS amendments: these instruments do not mandate replacement of every existing AIS. IMO: MSC 111 resolutions.
Scope of Application
Ships subject to the relevant SOLAS Chapters IV and V. From 2028 VDES may provide the shipborne alternative to the AIS requirement under the applicable amendments and approval. MSI/GMDSS equipment must cover the entire intended voyage; NAVDAT is not a SOLAS carriage requirement.
Procedure / How to Complete It
- Check sea areas, voyage plan, approved equipment, selected provider and actual ability to receive MSI/SAR information throughout the voyage.
- Test reception, alerts, power supply, familiarisation and records under SOLAS, flag, maker and SMS requirements.
- For a VDES installation verify entry into force, type approval, AIS/VDES configuration and applicable operational guidelines.
- Do not infer from multi-RMSS dissemination either a duty to equip for every service or that a missed warning is acceptable.
- Treat NAVDAT as a separate development until published instruments define its status and use.
Practical Example
Before a voyage the Company verifies that the approved receiver arrangement covers every intended sea area and correctly receives the selected service. It does not automatically purchase terminals for every RMSS or accept an MSI gap merely because no multi-RMSS carriage duty exists.
What Typically Goes Wrong
Confusing the shore-side duty to disseminate through all RMSS with shipboard carriage, presenting a missed warning as harmless, or treating VDES and NAVDAT as one programme with the same regulatory status.
Common Mistakes Mistake Library
| Mistake | Consequence | How to Avoid It |
|---|---|---|
| Equipping for every RMSS or accepting an MSI gap based on dissemination rules | Incorrect configuration or compliance assessment | Check sea areas, approved equipment and reception throughout the voyage |
| Assigning VDES status to NAVDAT | Incorrect status and planning | Use the latest published IMO instrument for each system |
What the PSCO Checks
Operational Tips
- Verify coverage and service throughout the voyage.
- Keep VDES, NAVDAT and multi-RMSS dissemination distinct.
- Update status and dates only from published IMO instruments.
Preparation checklist
- Sea areas and voyage checked
- Approved receiver arrangement operational
- MSI/SAR available throughout the voyage
- VDES status verified
- NAVDAT treated separately
- No inferred acceptance of an MSI gap
FAQ
Related Topics
Last substantive revision of this page: 15 September 2026 · page fingerprint 88f6895f4cad