VHF Data Exchange System (VDES) Made Simple: 2025 Update

AIS is the continuous VHF broadcast that shares identity and position for safety and awareness. VDES is the wider VHF data system that keeps AIS, and adds additional managed data links so ships, shore, and satellites can exchange structured digital messages beyond basic AIS reports.
🧪 What is it and Keep it Simple...
VDES is the VHF Data Exchange System. Think of it as an expanded VHF data system that includes AIS and adds additional, managed data links for structured messages. It is not a free-form “chat” channel. Ships, shore stations, and (where available) VDES satellite services can exchange more than basic AIS position reports using the VHF spectrum.
- What it adds: Additional VHF data channels (beyond classic AIS) designed for richer, structured messages such as Maritime Safety Information, targeted safety or operational updates, route-related exchanges, and Just-in-Time style port call coordination.
- Where it works: Near coasts where terrestrial VDES networks exist (VDE-TER), with satellite VDES capability (VDE-SAT) depending on service availability and footprint. Offshore performance is not “automatic” and varies by provider and region.
- How it fits: AIS continues to provide the safety broadcast. VDES adds more capacity and message options for compact, time-sensitive updates. On the bridge, it is best treated as an additional communications path alongside AIS, VHF voice, and satcom, not a replacement for broadband.
- Why shipowners care: Potential to offload some routine, structured updates from IP satcom where shore services exist, plus added resilience from having another independent path for critical short messages. Regulatory and carriage expectations are still evolving.
- What to look for: “VDES-ready” terminals that support AIS, application-specific messaging, and VDE channels, plus clean integration to ECDIS, routing, and port call systems so crews can use it with minimal extra workflow.
⚗️ 2025 VDES Rundown
- Is it real today: VDES is defined in international standards and has been progressing from trials into early deployments. Real-world availability is still uneven and depends on whether specific coastal networks and service providers are active on your routes.
- What it carries: Primarily short, structured messages. Typical examples include maritime safety and service information, defined application-specific messages, targeted operational updates related to navigation or port calls, and small equipment status pings. It is not designed for free-form chat or bulk data transfer.
- How it performs: In areas with terrestrial VDES (VDE-TER) coverage, the VDE channels provide substantially more data capacity than classic AIS channels. Actual throughput and latency still vary with local channel plans, traffic density, radio conditions, and how the shore network schedules messages.
- Regulatory path: Work at the IMO has been advancing on how VDES fits into the e-navigation and SOLAS ecosystem. Carriage requirements are not broadly mandatory yet, and timelines and scope can change as amendments and guidance mature across flags and classes.
- What owners can do now: Take a lane-by-lane approach. Specify upgradeable “VDES-ready” terminals where it makes sense, confirm interoperability with your bridge stack (ECDIS, routing, port call systems), and run practical coverage and workflow trials in your busiest coastal trades and approaches before committing fleetwide.
🧮 VDES - ROI, Payback & NPV
Scenario calculator for adding VDES-capable equipment alongside AIS and satcom. Results depend on route coverage, satcom contract structure, and whether shore services are active on your trades.
We welcome your feedback, suggestions, corrections, and ideas for enhancements. Please click here to get in touch.