Reviewed relationships 1
Verified
VDA and VDMA Organization publishes VDA 5050 3.0
Scope version 3.0
Boundary The standard defines mixed-fleet exchange; no site-listed robot support is inferred.
Canonical evidence claims 6
Claims are projected from authored tables. A dash remains an explicit missing value; it is never filled from a neighboring product or name match.
Robot developer ecosystems, SDKs, and simulation Fleet Interoperability 6 rows · 1 declared gap
| Metric | Value and evidence |
|---|---|
| Artifact kind | open communication interface for mobile robots and master control [M28] |
| Coordination scope | heterogeneous mobile robots from different manufacturers in one logistics environment [M28] |
| Distribution / governance | version 3.0 published open source after public consultation [M28] |
| Infrastructure scope | mobile-robot traffic, restricted and one-way zones, authorization areas, and power-saving actions [M28] |
| Planning / control boundary | zones carry movement rules; autonomous robots plan locally and share paths while the master retains traffic influence [M28] |
| Robot support proven on this site | Declared gap |
Source ledger 1
What is not inferred
No fuzzy entity matching, adjacent-column borrowing, universal compatibility, commercial maturity, or checkpoint-to-product identity. Absence of a relation means unreviewed or unsupported here—not proven incompatibility.