The short answer
VDA 5050 is an open standard for communication between mobile robots and a central fleet control. It defines the messages a master control uses to send transport orders to automated guided vehicles (AGVs), autonomous mobile robots (AMRs) and autonomous forklifts, and the messages those vehicles use to report their state back. It is published jointly by the German Association of the Automotive Industry (VDA) and the VDMA Materials Handling and Intralogistics Association, with technical supervision from the Institute for Material Handling and Logistics (IFL) at the Karlsruhe Institute of Technology. Because the interface is the same whoever built the vehicle, one master control can run a fleet made up of several manufacturers' machines.
At a glance
| Item | VDA 5050 |
|---|---|
| What it is | An interface specification between a master control (fleet manager) and mobile robots |
| Published by | VDA and VDMA, with IFL at the Karlsruhe Institute of Technology |
| Transport and format | MQTT messages with JSON payloads |
| Current version | 3.0, released in spring 2026 |
| Availability | Open source on GitHub; the specification document is published by the VDA |
| Typical machines | AGVs, AMRs, tuggers and autonomous forklifts |
The problem it solves
Most manufacturers ship fleet software that runs only their own machines. A warehouse that buys tuggers from one maker, pallet movers from a second and autonomous forklifts from a third ends up with three traffic systems that cannot see each other. Vehicles block one another at crossings, and every new vendor means another screen for the control room. VDA 5050 moves traffic control out of the vehicle maker's software and into a single master control that speaks the same language to every vehicle.
How VDA 5050 works
The standard splits the job in two. The master control knows the site, the jobs and the traffic. The vehicle knows how to drive, localize itself and stay safe. They exchange JSON messages over MQTT, a lightweight publish and subscribe protocol, through a message broker.
| Message | Direction | What it carries |
|---|---|---|
| Order | Master control to vehicle | The route as a chain of nodes and edges, with the actions to carry out along it |
| Instant actions | Master control to vehicle | Commands to act on immediately, such as pausing or cancelling an order |
| State | Vehicle to master control | Position, order progress, battery, loads, errors and safety status |
| Visualization | Vehicle to master control | Frequent position updates for display on a map |
| Connection | Vehicle to master control | Whether the vehicle is online, offline or has lost its connection |
| Factsheet | Vehicle to master control | What the vehicle is and can do: type, dimensions, supported actions |
An order is a graph. Nodes are points the vehicle passes or stops at, and edges are the paths between them. Actions, such as picking up or dropping a load, are attached to nodes or edges. The master control releases the route in stages: the part the vehicle is cleared to drive is the base, and the part that is planned but not yet released is the horizon. Releasing the route a section at a time is how the master control keeps two vehicles out of the same aisle.
What changed in version 3.0
VDMA and VDA formally adopted version 3.0 in February 2026, and the VDA announced the release on 20 April 2026 after a public consultation on GitHub. Earlier versions were written around vehicles that follow fixed, predefined paths. According to the VDA, version 3.0 is the first to take the key characteristics of freely navigating mobile robots into account. The main additions are:
- Zones. The master control can give movement rules for areas of the site: restricted areas, one-way routes, and areas a robot may only enter after the master control releases them.
- On-board route planning with path sharing. A robot can plan its own route between waypoints and share that path, so the master control can still manage traffic.
- Corridors and trajectories stay. Predefined trajectories and corridors for obstacle avoidance remain part of the interface, so the structure used can match how autonomous the robot is.
- Error messages in local languages, using languages stored on the vehicle.
- A standard power-saving action, so a robot can be put into and brought out of an energy-saving mode.
The VDA describes version 3.0 as a toolkit: which parts are used depends on the robot's level of autonomy and the needs of the project.
What VDA 5050 does not do
VDA 5050 standardizes the conversation between vehicle and master control. It does not make a mixed fleet plug and play. Points to plan for:
- Maps. The standard does not define a common map format, so the master control's layout and each vehicle's own map have to be aligned during commissioning.
- Security. Securing the MQTT broker, the network and access to it is the integrator's job.
- Recovery. Vehicles report errors, but how the fleet recovers from a blocked aisle or a failed vehicle is decided by the master control, not the standard.
- Coverage. Vehicles differ in which version and which optional actions they implement. Two machines that both "support VDA 5050" may not support the same things.
- Scope. It addresses mobile robots under a central control. Lifts, automatic doors, fixed machinery and robots that are not transport vehicles need other integration routes.
VDA 5050, Open-RMF and ROS 2 compared
| Route | What it is | Best fit |
|---|---|---|
| VDA 5050 | Interface specification between a master control and vehicles, over MQTT with JSON | AGVs, AMRs, tuggers and autonomous forklifts in factories and warehouses |
| Open-RMF | Open-source framework, managed by the Open Source Robotics Alliance, that coordinates robots with each other and with lifts, doors and other shared infrastructure | Service, cleaning and security robots sharing a building |
| ROS 2 | The robotics middleware many modern machines are built on | Machines whose makers expose their ROS 2 interface, such as inspection quadrupeds |
| Vendor API | A connector written against a manufacturer's own REST or SDK interface | Machines whose makers have not adopted a standard, including most port and heavy equipment |
These routes are not rivals. A site can run forklifts over VDA 5050, cleaning robots through Open-RMF and a patrol robot through its maker's API, as long as one layer above them holds the shared map and rules. That is the subject of robot fleet management across vendors. Where fleets should stay independent but see each other, the MassRobotics interoperability standard shares position and destinations without giving orders.
Questions to ask a supplier
- Which version? Ask which VDA 5050 version the vehicle implements, and whether an update to 3.0 is available.
- Which actions? Ask for the factsheet and the list of supported actions, and compare it with the jobs you need done.
- Tested against what? Ask which master control systems the vehicle has already run under on a live site.
- Free navigation. If the robot plans its own routes, ask whether it supports zones and path sharing.
- What stays proprietary? Charging, map editing and diagnostics often still run through the maker's own tools.
- Who owns the integration? Decide in the contract who aligns the maps, secures the broker and tests the mixed fleet.
How HORMĒ uses VDA 5050
HORMĒ is a Behavioral Intelligence platform for autonomous machines, based in Dubai, United Arab Emirates. Its behavior layer sits above the vendors' own systems and connects machines through VDA 5050, Open-RMF, ROS 2 or a connector written against the manufacturer's interface, so a machine already on the floor can join the fleet without being replaced. Where a manufacturer's stack is closed, HORMĒ says so before you buy. The layer is licensed per machine per month: Core from $149, Autonomy from $349 and Assured from $690, indicative. See what Behavioral Intelligence is, pricing, and the machines it most often applies to: warehouse robots and autonomous forklifts and autonomous port equipment. For budgets, see what a warehouse robot costs in the UAE.
Frequently asked questions
What is VDA 5050?
VDA 5050 is an open standard for communication between mobile robots, such as AGVs, AMRs and autonomous forklifts, and a central fleet control. It is published by the German automotive association VDA and the VDMA Materials Handling and Intralogistics Association, and it lets vehicles from different manufacturers be run by one master control.
How does VDA 5050 work?
A master control sends each vehicle an order made of nodes and edges, with actions to carry out along the way, and the vehicle reports its state back. The messages are JSON sent over MQTT, a lightweight publish and subscribe protocol, on a fixed set of topics for orders, instant actions, state, visualization, connection and the vehicle factsheet.
What is new in VDA 5050 version 3.0?
Version 3.0 was released in spring 2026 and is the first version to take freely navigating mobile robots into account. It adds a zone concept for traffic rules such as restricted areas and one-way routes, lets robots plan their own routes between waypoints and share the planned path with the master control, and adds error messages in local languages and a standard power-saving action.
Is VDA 5050 free to use?
Yes. VDA 5050 is published as open source on GitHub, and the specification document is published by the VDA. The interface is free to implement; the fleet control software and the vehicles that use it are commercial products.
Does VDA 5050 make robots from different vendors plug and play?
No. VDA 5050 standardizes the messages between vehicle and master control, but it does not define a common map format, a security model or how recovery from errors is coordinated across robots. Each new vehicle type still needs integration and testing against the master control.
What is the difference between VDA 5050 and Open-RMF?
VDA 5050 is an interface specification between a master control and vehicles, used mainly for AGVs, AMRs and forklifts in factories and warehouses. Open-RMF is an open-source software framework that coordinates robot fleets with each other and with building infrastructure such as lifts and doors. The two can be used together.
Does HORMĒ support VDA 5050?
Yes. HORMĒ connects machines to its behavior layer through VDA 5050, Open-RMF, ROS 2 or a connector written against the manufacturer's own interface, so that machines from different vendors run as one fleet.
Check the current specification before relying on any detail; where sources differ, the document published on the VDA website is the valid one. Sources: VDA press release on version 3.0, VDA 5050 on GitHub, idealworks on the 3.0 release, BlueBotics overview, Open-RMF.
Ask about a mixed fleet