VDA 5050 consulting: choose the right AGVs and AMRs, then test what really works togetherMixing robot brands? VDA 5050 rarely works out of the box.
An independent VDA 5050 consultant for operations and automation teams bringing more than one robot brand under one fleet control. We write the interface scope, choose the master control, and test every vehicle before go-live. We don't sell hardware, so our advice stays independent.
Free 30-minute call with an adviser · written proposal with the price after · fixed-scope engagements from £3k.
When you need a VDA 5050 consultant
A VDA 5050 consultant specifies and tests how AGVs and AMRs from different manufacturers take orders from one fleet control. That means naming the version and topics each vehicle must support, deciding who owns maps and zones, choosing between an OEM fleet manager and an independent master, and running mixed-fleet acceptance tests on your floor rather than trusting a “compliant” badge.
When VDA 5050 starts to matter:
- A second robot brand is arriving and the two fleets will share doors, aisles or chargers.
- Every proposal says “VDA 5050 compliant”, but none says which version, which topics, or which fleet control it has been proven with.
- OEM fleet manager or independent master? You need the trade-off written down before the next purchase locks it in.
- Legacy AGVs must coexist with new AMRs without ripping out infrastructure.
- A multi-supplier pilot deadlocks at peak or stalls in integration with the WMS, MES or ERP.
What we do
| Stage | Deliverable | Why it matters |
|---|---|---|
| 1 · Fleet and flow inventory | Each vehicle’s VDA 5050 version, native or adapter support, factsheet, and the flows it serves | Shows where interoperability is real and where it is custom glue |
| 2 · Interface scope | Version, required and optional topics, instantActions, zone types, map handling and error behaviour, written into the RFP | A generic “VDA 5050 support” clause cannot be enforced |
| 3 · Fleet control selection | OEM-native fleet manager vs independent master: requirements, shortlist, scripted demos on your flows, scored matrix and five-year TCO | Traffic management is not in the standard, so it is where products really differ |
| 4 · Integration architecture | WMS/MES/ERP job flow, doors, lifts and chargers, traffic and charging rules, event schema, MQTT broker and network zoning (IEC 62443) | The standard excludes peripherals and external IT, which is where mixed fleets stall |
| 5 · Simulation & pilot | Peak-density simulation and pilot KPIs: jobs per hour, blocked time, mission success, uptime | Demo-day averages hide peak-hour failure |
| 6 · Mixed-fleet acceptance | Scripted interoperability tests run per vehicle type against the chosen fleet control | Proves each vehicle and fleet-control pair before go-live |
What VDA 5050 does, and does not, standardise
VDA 5050 standardises the communication between fleet control and mobile robots over MQTT (version 3.1.1 or later) with JSON messages. According to the published version 3.0.0 specification, it does not cover three things buyers often assume it does:
- Safety. It defines no functional or system safety requirements and must not be applied as a safety standard.
- Traffic-management logic. Routing, prioritisation, congestion handling and deadlock resolution are left to the fleet control product.
- Other interfaces. Doors, lifts, chargers and other infrastructure, and external IT systems such as your WMS, are outside its scope.
Those three gaps are where mixed fleets fail, and where an independent specification and acceptance test earn their fee.
Specify topics, not the badge
| Topic | Direction | In v3.0.0 | What to pin down in the RFP |
|---|---|---|---|
order | Fleet control → robot | Mandatory | Node/edge limits, horizon handling, order-update behaviour, rejection cases |
instantActions | Fleet control → robot | Mandatory | Which actions each vehicle supports (pause, resume, cancel, map download and enable, factsheet request) and vehicle-specific ones |
state | Robot → fleet control | Mandatory | Error levels and references, battery and load reporting, update interval |
connection | Broker / robot → fleet control | Mandatory | Behaviour on connection loss and reconnect |
factsheet | Robot → fleet control | Mandatory | Protocol limits, supported actions and supported zone types, delivered before integration starts |
visualization | Robot → visualisation systems | Optional | Whether you need a higher-rate position and path feed |
zoneSet | Fleet control → robot | Optional | Which zone types each vehicle understands; blocked, speed-limited and interactive zones |
responses | Fleet control → robot | Optional | Needed for interactive zones where a robot requests release or replanning |
Name the version and the migration path
Version 3.0 was released by the VDA on 19 March 2026 and announced by the VDA and VDMA on 20 April 2026. It adds support for freely navigating robots (planned path sharing and a zone concept) and renames a number of parameters, which the release notes mark as breaking. VDA 5050 uses semantic versioning, so a major version can include breaking changes. Installed fleets often run earlier 1.x or 2.x versions: the RFP should state a minimum version, a target version and how the fleet control handles vehicles on different versions during migration.
Decide who owns maps and zones
In version 3.0 the fleet control can distribute maps to robots from a map server, identified by map ID and map version, and enable or delete them by instant action. It is the fleet control’s responsibility to make sure the right maps are enabled. Write down which system is the source of truth for layout, nodes, edges and zones, and who updates it after a racking change. Robots declare in their factsheet which zone types they understand. Some cannot process zones at all.
Native support or adapter, with an owner
Some vehicles implement VDA 5050 natively. Others need an adapter that translates the manufacturer’s own interface. Adapters work, but they add a component with its own latency, firmware dependency and maintenance owner. Put that owner in the contract.
Script the mixed-fleet acceptance test
At minimum: order acceptance and rejection; order updates; cancel mid-mission; pause and resume; error and battery reporting in state; connection loss and reconnect; map download and enable; charging hand-off; two brands contesting a shared intersection or door; and sustained peak density.
OEM fleet manager or independent master control
Robot manufacturers’ own fleet managers run their own vehicles best, and some manufacturers, such as OTTO and MiR, are building VDA 5050 support so their vehicles can take orders from a third-party master; conformance varies by firmware version, so we test it rather than take it on trust. Third-party fleet-control and master-control products on our assessment list include SYNAOS, idealworks, NAiSE, Meili FMS, Navitec Navithor, BlueBotics ANT and Kollmorgen NDC. We hold no preferred list.
The real difference is rarely the VDA 5050 badge. It is which vehicles have been proven with which fleet control in production, how traffic and charging are handled across brands, whether manual forklifts and people are in scope, and how cleanly jobs arrive from your WMS, MES or SAP EWM. See fleet orchestration under VDA 5050 and our supplier reviews.
Engagement and fees
| Entry point | Model | Typical duration | Indicative fee |
|---|---|---|---|
| Discovery & scoping stage | Fees agreed in writing after scoping | typically 1 to 5 days on site | £3k to £30k |
| Supplier & fleet-control selection | Fees agreed in writing after scoping | typically 3 to 6 weeks | £3k to £30k |
| Pilot design & oversight | Fees agreed in writing after scoping plus day-rate | with timings agreed per site | £3k to £30k |
| Advisory day | Day-rate | Per day | £1,200 / day |
Each stage ends with a gate where you can stop and keep the artefacts. Fees exclude hardware, software licences and travel. See pricing.
Worked example: AMR/AGV fleet intelligence, an engagement our advisers led in earlier roles; the client name is withheld under NDA.
Outside our scope
- We don't sell hardware or take commissions from vendors.
- We are not the machine builder or system integrator of record, and we do not issue CE or conformity declarations. We specify, check and accept that work on your behalf.
- We do not write vehicle-side adapter firmware. We specify, test and accept it.
Frequently asked questions
What does a VDA 5050 consultant do?
A VDA 5050 consultant specifies and verifies multi-supplier robot interoperability from the buyer’s side: which version and topics each vehicle and the fleet control must support, OEM fleet manager or independent master, how jobs arrive from the WMS, MES or ERP, and a scripted acceptance test for every vehicle and fleet-control pair. The aim is a fleet you can extend with another brand without starting again.
Which VDA 5050 version should we specify?
For new procurements, ask whether vehicles and fleet control support version 3.0, released by the VDA on 19 March 2026 and announced by the VDA and VDMA on 20 April 2026. Many installed vehicles run earlier 1.x or 2.x versions. VDA 5050 uses semantic versioning, so a major version can contain breaking changes: state the minimum version, the target version and how mixed versions are handled during migration.
Does VDA 5050 handle traffic management and deadlocks?
No. The specification defines the communication interface between fleet control and mobile robots. It explicitly excludes traffic-management logic such as routing, prioritisation, congestion handling and deadlock resolution, which remain features of the fleet control you choose. That is why fleet-manager selection and peak-density testing matter as much as the interface.
Is “VDA 5050 compliant” the same as proven?
No. Compliance is usually a supplier’s own claim about a version and a set of topics. Some manufacturers state VDA 5050 support for their vehicles or offer adapters. Treat that as a claim to test, not a certification. What matters is whether that vehicle works with your chosen fleet control in your layout, so we write a site acceptance test for each pair into the contract.
Do we need to replace our existing AGVs?
Usually not. We assess each vehicle’s VDA 5050 support. Vehicles without native support can often be bridged with an adapter, provided someone owns its maintenance. Where a bridge is not viable, we set out the cost of running them under separate control versus replacing them, so the decision rests on throughput and total cost.
Does VDA 5050 cover safety?
No. The specification states that it does not define safety requirements and must not be applied as a safety standard. Personnel protection stays with each vehicle and its conformity, for example under ISO 3691-4, plus zoning and speed rules for shared aisles. We check that evidence during acceptance but do not issue conformity declarations.
How much does VDA 5050 consulting cost?
Engagements usually start with a discovery and scoping stage (typically 1 to 5 days on site) or with supplier selection and RFP support. Every engagement is scoped per project and priced in writing before work starts: £3k to £30k per project, or £1,200 a day in the UK. Regional ranges for Europe, North America and other regions are on how we work.
Last updated: 5 October 2026