VDES vs AIS 10 Equipment Decisions Shipowners Should Make Before 2028
VDES turns AIS replacement into a fleet equipment strategy
I would treat the VDES transition less like a simple transponder swap and more like a bridge-electronics planning window. AIS has been the familiar safety and tracking layer for decades, but VDES brings more capacity, authentication potential, terrestrial and satellite data exchange, and a new compliance path beginning in 2028. The owner decision is not just “buy VDES or keep AIS.” It is which equipment should be replaced, which interfaces should be preserved, which systems need authentication support, and which ships should be upgraded early enough to avoid a rushed fleetwide procurement cycle.
VDES is not only a navigation-equipment topic
AIS replacement decisions usually sit with navigation teams. VDES decisions will pull in more departments: compliance, IT, cyber, procurement, bridge operations, shore operations, fleet performance, port-call teams, and data-service vendors. That is because VDES is not only about broadcasting identity and position. It can become a managed maritime data channel for authenticated safety messages, digital services, satellite-supported communications, and future e-navigation workflows.
The timing matters. If a ship is already scheduled for radar, ECDIS, GMDSS, VDR, GNSS, bridge network, or antenna work before 2028, VDES should be part of that specification. Waiting may force a second bridge-equipment job after cable routes, antennas, displays, and network interfaces were already touched.
Create a fleet AIS and VDES readiness register: equipment model, type approval path, antenna arrangement, ECDIS integration, GNSS source, VDR input, bridge network, software version, and replacement window.
Owners budget the transponder but miss antennas, cabling, display integration, VDR capture, cyber documentation, crew familiarization, software licenses, satellite service trials, and shore-system updates.
Any ship due for AIS replacement, bridge modernization, GMDSS work, ECDIS renewal, antenna overhaul, new GNSS receiver, or fleet cyber review before 2028 should be screened for VDES readiness.
The cheapest VDES transition is likely the one bundled into planned bridge work. The expensive version is a rushed standalone retrofit after the fleet discovers that displays, antennas, records, and procedures were not ready.
Shipowners should make these choices before the 2028 transition
The strongest operators will treat VDES as an equipment and workflow migration, not a last-minute compliance purchase.
Replace AIS now, buy VDES-ready, or wait for full type-approved VDES
The first decision is timing. Some owners may keep compliant AIS until the replacement cycle arrives. Others may choose VDES-ready equipment during a bridge refit to avoid buying twice. The safest path depends on type approval, flag expectations, equipment lifecycle status, and drydock timing.
Confirm AIS continuity during the VDES migration
VDES adoption does not remove the need for continuity with existing AIS users. A vessel still needs to be visible to ships, ports, VTS, pilots, charterers, terminals, and fleet systems that depend on today’s AIS data flow.
Review antenna, cabling, splitter, and RF layout before ordering hardware
VDES is still a VHF-band system, but the shipboard RF arrangement matters. Antenna placement, cable loss, filtering, interference, redundancy, mast access, and coexistence with VHF, AIS, GMDSS, and other antennas can decide whether the installation works cleanly.
Decide which bridge displays should show VDES data
A VDES transponder is only useful if the bridge team can see and manage the right information. ECDIS, radar, conning display, alert management, pilot plug, and dedicated VDES displays may all need interface decisions.
Check VDR and data-recording requirements before commissioning
If VDES becomes operationally important, the owner should know which data needs to be recorded, how it will be timestamped, and whether voyage-data, alert, or message records are captured in a way that supports audits and casualty investigation.
VDES planning goes beyond the transponder
Once the first five decisions are settled, owners still need to think through cybersecurity, satellite value, bridge training, message authentication, and fleet standardization.
Separate VDES cybersecurity from general satcom cybersecurity
VDES sits close to navigation and safety messaging, so it should not be treated like ordinary office connectivity. Authentication support, software maintenance, access control, vendor service methods, network segmentation, and update procedures all belong in the purchase decision.
Evaluate VDE-SAT service value by trading pattern
Satellite VDES may matter more for vessels that operate beyond dense coastal infrastructure, in polar routes, offshore sectors, remote fisheries, deep-sea corridors, or regions where safety messages and ship-shore data services need wider coverage.
Prepare for authenticated safety and port-service messages
One of the strongest VDES promises is trusted digital messaging. That can include navigational warnings, safety information, aids-to-navigation data, port coordination, ice information, traffic services, and other low-bandwidth operational messages.
Train bridge teams before the display becomes crowded
More capacity can become more noise if operational procedures are weak. VDES can add new message categories, authentication status, service channels, satellite or terrestrial status, alerts, and data-management choices for the bridge team.
Lock in lifecycle support, software maintenance, and fleet standardization
Early transition periods can create mixed fleets. One vessel may have AIS only, another VDES-ready hardware, another full VDES, and another vendor ecosystem entirely. That can create spares, training, service, cyber, software, and reporting friction.
VDES changes the buying checklist around AIS equipment
Shipowners should compare the installation as a system, not as a transponder line item.
| Equipment decision | AIS-era habit | VDES-era buying issue | Risk if ignored | Evidence to request | Priority |
|---|---|---|---|---|---|
| Transponder lifecycle | Replace AIS when it fails or ages out | Decide between AIS-only, VDES-ready, and full VDES hardware | Buying twice or getting stuck with short-life equipment | Type approval path, upgrade letter, lifecycle statement | Very high |
| AIS continuity | Assume everyone sees AIS as usual | Maintain compatibility during mixed AIS and VDES adoption | Bridge confusion, VTS issues, data gaps, fleet-system mismatch | AIS fallback and message compatibility documentation | Very high |
| RF installation | Reuse existing AIS antenna path | Validate antenna, cable loss, splitter, filtering, and interference | Poor performance after installation | RF survey, mast drawing, cable-loss calculation | High |
| Display integration | Feed AIS to ECDIS and radar | Decide which VDES messages appear on which bridge screens | Alert overload or missed safety messages | Display mapping, message filters, bridge workflow | High |
| Authentication | Trust received AIS-like data unless obviously wrong | Use authentication status and digital signatures where supported | Spoofed or unauthorized messages influence decisions | Authentication support and cyber documentation | Very high |
| Satellite services | Use AIS near shore and satellite AIS for tracking | Evaluate VDE-SAT for operational data services and safety messages | Subscription cost without real route value | Coverage, latency, service list, trial plan | Route dependent |
| VDR and records | Record standard navigation inputs | Decide which VDES messages, alerts, and logs are captured | Weak evidence after an incident or audit | Recording map, retention rules, export procedure | High |
| Crew procedures | AIS use is familiar and routine | Train watch teams for new message classes and authentication states | More data but weaker decision-making | Bridge checklist and familiarization record | High |
The strongest rollout starts with the ships already due for bridge work
A rushed fleetwide replacement program can be expensive. Owners should use scheduled maintenance and bridge-electronics renewal windows to avoid duplicated work.
Build the installed-base register
Record AIS model, serial number, software version, antenna path, ECDIS interface, radar interface, pilot plug, VDR input, GNSS source, cyber file, and replacement date.
Separate ships by refit timing
Put ships into three groups: immediate bridge work, 2027 equipment renewal, and later-cycle vessels that can keep AIS until the business case is clearer.
Run a VDES-ready specification
Require vendors to state type-approval pathway, upgradeability, VDES function set, AIS continuity, antenna requirements, display integration, and lifecycle support.
Test bridge workflow before fleet rollout
Use one pilot vessel to test message display, authentication indicators, VDR logging, crew procedure, shore support, and service-provider integration.
Standardize before mixed fleets become expensive
Limit the number of VDES hardware families, software tools, display behaviors, spares kits, training packages, and service agreements across the fleet.
VDES vendors should prove transition readiness, not only device capability
The best quote should explain how the system fits the ship, the bridge, the fleet, the class file, and the 2028 compliance path.
| Buyer question | Reason it matters | Weak answer | Strong answer | Evidence to request | Priority |
|---|---|---|---|---|---|
| Is the equipment VDES-ready or VDES-approved? | Upgradeability and type approval drive replacement timing | Future software upgrade expected | Clear status: AIS-only, VDES-ready, or type-approved VDES with timeline | Approval certificate, IEC test path, vendor lifecycle letter | Very high |
| Does AIS continue without operational disruption? | Mixed adoption will last for years | VDES includes AIS | AIS transmit, receive, display, and fallback behavior fully documented | Interface control document and bridge test procedure | Very high |
| Which antennas and RF changes are required? | Installation cost may exceed hardware expectations | Uses existing VHF antenna | Ship-specific antenna, cable, splitter, interference, and redundancy plan | RF survey and installation drawing | High |
| Can the bridge manage message volume? | More data can increase watchstander workload | Messages appear on the display | Filtering, alert priority, authentication status, and display routing defined | Bridge workflow and crew familiarization package | High |
| Does the system support authentication? | Authentication is one of the key advantages over conventional AIS | Cybersecure system | Specific digital-signature or authentication handling explained | Authentication method, update process, and cyber file | Very high |
| Does satellite VDES add route value? | Not every vessel needs the same service level | Global coverage planned | Coverage, latency, message type, commercial service, and trial plan matched to route | Coverage map, service agreement, pilot report | Route dependent |
| Will VDR and shore systems capture the right records? | Operational value depends on evidence and integration | Logs are available | VDR, fleet portal, shore dashboard, and export rules documented | Record map, test export, retention policy | High |
| Does the vendor support fleet standardization? | Mixed systems create training and spares cost | Global service available | Fleet rollout plan, common spares, training, software, and support agreement | Fleet support plan and spares list | High |
VDES Transition Equipment Readiness Scorecard
Use this tool to estimate whether a vessel should buy AIS replacement equipment now, specify VDES-ready hardware, or run a deeper VDES integration review.
This scorecard is a planning aid. Final decisions should involve the flag, class, bridge-equipment vendor, radio survey provider, VTS or coastal-service expectations, cyber team, and vessel operating department.
The 2028 transition rewards owners that buy once
VDES should not push every owner into an immediate equipment replacement. It should push owners into better timing. A ship with new AIS, limited service exposure, and no bridge refit may wait. A ship already entering a bridge upgrade should avoid installing short-life AIS equipment without checking VDES-ready options. A fleet with many sister vessels should standardize early before mixed hardware creates training, spares, data, and software problems.
Select one vessel with upcoming bridge work and test VDES-ready equipment, AIS continuity, antenna performance, ECDIS display behavior, VDR logging, authentication indicators, and crew procedure.
Do not buy the cheapest AIS replacement if the vessel will need another bridge-equipment job before or soon after 2028.
Track ships by AIS lifecycle status, VDES-ready hardware, antenna readiness, display integration, cyber file, VDR recording, crew training, and planned replacement window.
VDES is the rare compliance shift that also creates a commercial equipment decision. Owners that treat it as a fleet planning exercise can reduce duplicate purchases, improve bridge data quality, prepare for authenticated safety messages, and avoid a rushed retrofit cycle as the 2028 date approaches.
We welcome your feedback, suggestions, corrections, and ideas for enhancements.
Please click here to get in touch