VNTA Robotics · Validation
Early accessKnow what your robot integration actually does before deployment.
VNTA tests robot and fleet integrations against a repeatable validation suite and produces a readiness result backed by the messages, calls and failures it observed.
- 01 The vendor says what should work Documentation, datasheets and the interface itself declare what the system can do.
- 02 VNTA tests what actually works The same repeatable checks, including a dropped link and a restart, run against the connected system.
- 03 You get the evidence One readiness verdict, with every call, answer and raw message behind it.
The problem
Documentation tells you what should work. Deployment reveals what actually works.
What can this machine actually do, and do we have evidence that it works? A capability written in a manual is a claim. A capability that has been tested is evidence. VNTA keeps the two apart, for every function of every machine.
- Declared The vehicle describes its own functions when asked.
- Integration test Asked for its factsheet, it answered, but named no functions.
- VNTA evidence Failed. The raw reply, its timestamp and the reason are kept with the result.
Independent validation
An independent pre-deployment check for robot integrations.
VNTA provides independent technical validation of robot integrations. We test the behaviour of the connected software system and preserve the evidence behind each result.
Think of it as an MOT for the integration: a structured check of what actually works before deployment. VNTA provides technical validation, not regulatory certification.
Software and integration validation. It is not:
- Safety certification
- Regulatory certification
- Manufacturer commissioning
- Mechanical performance testing
What a validation run checks
-
Capability discovery
Asks the system what it can do, where its interface allows.
-
Declared and verified
Keeps what an interface claims apart from what a test saw work.
-
Mission lifecycle testing
Send, pause, resume, cancel, and what happens when the same order arrives twice.
-
Failure and reconnect testing
Cuts the link and restarts the system, then watches what comes back.
-
Protocol checks
For VDA 5050 2.1.0: every message judged against the official schemas, and behaviour over time.
-
Evidence
Every call, answer, latency and raw message, kept with the result.
-
Readiness report
One verdict with its reasons: ready, conditionally ready, not ready or incomplete.
-
Unknown is not a pass
A timeout is reported as unknown. Never as a pass, never as a fail.
Example result
See what the validation produces.
A readiness verdict, the checks behind it, every failure with its evidence, and what to change. Then the capability matrix: declared, and verified or not.
Verdict
Conditionally ready
Every behavioural check passed: orders, pause, resume, cancel, duplicates, charging, recovery after a restart. Three findings: capability discovery, and two on the connection topic.
- 32 / 37checks passed
- 23 / 25core checks
- 9 / 12protocol checks
- 13 / 14capabilities verified
Findings and remediation
- CAP-01 · PRO-04 Capability discovery Fail
Asked for its factsheet, the vehicle answered, but named no functions, and the factsheet did not pass the official schema.
RemediationSupply a factsheet that lists the vehicle’s functions, so a master control can discover them.
- PRO-09 Connection topic QoS Fail
The standard asks for the connection topic at QoS level 1. The vehicle’s ONLINE message and its last will both arrived at QoS 0.
RemediationPublish connection messages at QoS 1, as VDA 5050 2.1.0 requires.
- PRO-11 Connection state after reconnect Fail
After a cut link was restored, state messages resumed within about a second, but no ONLINE message followed. A late subscriber was handed the retained CONNECTIONBROKEN while the vehicle was connected and publishing. Every individual message was schema-valid; the fault only showed over time.
RemediationPublish ONLINE on the connection topic after every reconnect, not only after a restart, so a master control does not treat a live vehicle as lost.
How each check can end
- PassSeen to work.
- WarningWorked, with something to look at.
- FailTried, and did not work.
- UnsupportedNot offered by the system.
- UnknownNo answer in time. Never counted as a pass.
Evidence kept with each result
- Every call and answer, with its latency
- Raw protocol messages, with timestamps
- Schema results for each message
- What was done to the system: a dropped link, a restart
VNTA validation evaluates software integration behaviour against a chosen set of checks. It is not a functional-safety certification and does not replace manufacturer commissioning procedures.
Who it is for
For the people who have to sign off an integration.
-
For integrators
Catch integration failures before site acceptance.
Run the same validation approach across vendors and deployments, preserve the evidence, and give your customer a clear readiness result.
-
For operators
Verify what you are accepting.
See which capabilities were actually demonstrated before standardising an integration across a site or fleet.
Robot makers can use the same suite to check an interface before it ships.
Supported integrations
Above the systems you already run.
VNTA Robotics sits above VDA 5050, ROS 2, Open-RMF and vendor APIs, reaching each one through an adapter. It replaces none of them.
- VDA 5050 2.1 Supported today Version 2.1.0, over MQTT
- VDA 5050 3.0 Planned Not supported yet
- ROS 2 · Open-RMF Planned Future adapters, built with design partners
- Vendor APIs Planned Case by case, with design partners
Where Validation stands today
Validation has been tested against simulated systems and one external VDA 5050 implementation. It has not yet been run against a real robot. We are now taking on our first production design partners.
Part of every first project is writing the adapter for that system, so places are limited and scoped carefully. Technical status in full
Pricing
Start with one integration.
Priced per integration, not per robot. Every price is a starting point, ex VAT, for a scope agreed before work begins.
Design partner
From €2,500
For initial production integrations while Validation is being developed.
Become a design partnerValidation
From €6,500
Independent validation of a robot or fleet integration, with evidence and readiness findings.
Validate an integrationLarger deployments
Scoped
For multiple systems, sites, vendors or custom adapters.
Discuss an integration
Where VNTA goes next
One product today. A wider layer later.
Validation is the first layer of VNTA's infrastructure for interoperable autonomous systems. The rest is built on it, in order.
- Early access Validation The first module. Connects to an integration, finds out what it can do, tests it, and reports with evidence.
- In development Runtime The platform. Adapters, one capability model, and an API and SDK over capabilities that have been tested.
- Future Access Mission governance. Who may ask a machine to do what: policy, approvals, and a record before dispatch.
- Future Identity Machine trust. A verifiable identity for each machine: credentials, ownership, revocation.
Notes
What we built, and what it found.
- 22 October 2026 Twenty minutes with people who commission robots If you commission AMRs or AGVs, we would like 20 minutes. Five questions, and nothing to sell.
- 20 October 2026 What we tested against, exactly Four systems, and none of them is a real robot: three simulators we wrote, and one open-source virtual vehicle we did not.
- 15 October 2026 Declared is not verified A capability in a manual is a claim. A capability that has been tested is evidence. VNTA Robotics keeps the two apart.
Validate one integration before standardising the rest.
Bring one robot or fleet system. We agree what will be tested, run the suite, and go through the result and the evidence with you.
Product scope, supported integrations and pricing may change as Validation is used with early partners.