"Who is right?"
When something breaks, it is one vendor's claim against another's. Without evidence, the argument takes days.
Home Products
A LogistiXpert product
Prove conformance. Don't assume it.
A conformance checker for VDA5050, M2X and VDMA LIF — for log files and for live traffic. The standard describes messages; it does not prove that two systems read them the same way. This does.
The situation
The interface is in the standard. Practice is not.
Vehicle and fleet controller come from different vendors. The specification describes the messages — it does not prove that both sides read them the same way. When they do not, three questions cost real time.
"What was checked?"
A green tick without a scope is worthless. An acceptance test has to state which rules ran, which did not apply and why.
"What happened there?"
The fault appears once, on a Friday evening. Without a recording that keeps its context, all that is left is to reproduce it — and hope.
The answer
One tool, three specifications
90checks
VDA5050
2.1.0 and 3.0Schema, protocol header, order and state structure, node, edge and action lifecycles, order-state correlation, battery and safety.
11checks
M2X
0.9.0 · previewPeripheral interfaces: load handling, doors, lifts, signal lights, charging devices and transport orders — against the official schemas.
13checks
VDMA LIF
1.0.0Layout files: schema, node and edge integrity, reachability across the network, station references.
M2X is not final yet. Its results are marked as a preview and carry no certification claim — VDA5050 and LIF are unaffected.
Ways in
Three ways in — whichever you have
Import a log file
.log, .txt, .json or
.ndjson. The importer detects the message type, reports lines it
could not read and keeps the field order of the source.
Record live
A capture profile connects to the broker, records in the background and analyses every message as it arrives — several profiles at once.
Sit in between
The same profile can mirror the traffic onto a second broker, running as a transparent proxy between vehicles and controller without changing operation.
Depth
What is actually checked
Not one pass over the text — four layers, each building on the last.
-
Schema first
Every message against the official JSON schema of the target version — 2.1.0 and 3.0 separately, because 3.0 renamed fields.
Layer 1 -
Then structure
Required fields, types, ISO-8601 timestamps, semantic version, arrays where arrays belong.
Layer 2 -
Then sequence
headerId gaps and regressions, timestamp regressions, node and edge sequences, action lifecycles.
Layer 3 -
Then coherence
Is an order acknowledged? Does the reported progress match the order that was issued? Both per vehicle.
Layer 4
In use
From a finding to the message in one click
The finding, with the evidence for it
Each finding shows the message that triggered it, with the offending field path highlighted — not just a line number. Beside it, the previous, current and next message scroll as one, so a deviation is read in its context.
Filter by severity and by vehicle, grouped by check or by message — depending on whether you are after a pattern or a single incident.
Watch the installation at work — or replay what already happened
Every vehicle on the LIF layout in its own colour, the last order issued against the last position reported. When the map and the vehicle disagree, it says so — that is the point. Findings appear as they happen.
The same view replays any finished capture or imported log, forwards or backwards, step by step and up to 20×, true to the real message intervals and showing only what was known at each point.
Auditable verdicts
Every rule is Active, No data or Switched off — never a silent pass. Each run records the target version, the scope, the schema revisions, an input checksum and the time.
Order over the real track
The order path is drawn on the imported LIF layout and compared node by node and edge by edge — the most common reason a vehicle rejects an order. On a mismatch, every missing node is named.
Fleet-ready
headerIds are counted per topic; the topic carries manufacturer and serial. Every sequence, lifecycle and correlation is evaluated per vehicle, so ten vehicles are not one vehicle's findings times ten.
Unattended monitoring
Record for days. A digest arrives on a schedule or once a threshold is crossed, broken down by severity, vehicle and check. A restart resumes where it stopped — nothing counted twice.
Who it is for
Where it pays off
AGV and robot manufacturers
Prove the conformance of your own vehicles before shipping — and show, when a complaint arrives, that the messages matched the standard.
Fleet controller vendors
Test orders and instantActions against several vehicle types before the customer does. Spot regressions between releases with the same scope on a new build.
Integrators and operators
Accept third-party systems without taking the vendor's word for it. A weekend-long run, a report on Monday.
Test houses and consultancies
A documented, repeatable scope instead of home-grown scripts — multi-client through enterprises and projects.
Operations and security
Runs where the data has to stay
Recordings from a live installation rarely leave the network. The analyzer runs where they are.
-
On your own premises
Docker Compose — one file, one command. Your hardware, your network or a hosted instance.
-
Credentials encrypted
Broker passwords are stored encrypted, never in clear text.
-
Links that cannot be guessed
Reports and runs hang off unguessable ids, on top of an ownership check on every access.
-
Roles with limits
Member, superuser, administrator — who may delete what is defined and enforced in one place.
-
Teams and projects
Colleagues share one enterprise and one message contingent; logs, layouts and reports file under a job and filter by it.
-
Quality on record
527 automated tests run before every release.
The next step
Three ways to start
Demonstration
A walk-through on the demo package that ships with the product — one clean and one faulty data set with a matching layout.
Pilot on your data
One recording from your installation, analysed and discussed together.
Operation
Hosted at vda5050.logistixpert.de or in your own network with Docker.
The LogIQ VDA5050 Analyzer produces diagnostic guidance. It issues no certification and no release approval. VDA5050, M2X and LIF are the marks of their respective bodies; this is an independent tool and is not endorsed by them.