RobotAtom interface evidence record

Which software pair and message scope were tested?

Put the integration requirement beside its evidence. Keep unknown builds, unsupported features and missing test traces visible before a procurement decision.

Compare the required exchange with the tested exchange

Name both software builds and the exact interface document. Record what must cross the boundary separately from what the test actually demonstrated. A blank tested field stays open even when the requirement is complete.

Required exchange
Tested exchange

12 open interface-evidence fields

This checks record completeness, not compatibility or conformance. It sends no messages to robots, fleet managers or brokers.

  • Required exchange: Robot model and software build
  • Required exchange: Fleet manager and software build
  • Required exchange: Interface specification and document revision
  • Required exchange: Message profile, optional features and extensions
  • Required exchange: Test environment, scenario, dated log and outcome
  • Required exchange: Evidence owner and retest decision
  • Tested exchange: Robot model and software build
  • Tested exchange: Fleet manager and software build
  • Tested exchange: Interface specification and document revision
  • Tested exchange: Message profile, optional features and extensions
  • Tested exchange: Test environment, scenario, dated log and outcome
  • Tested exchange: Evidence owner and retest decision

Entries stay in this tab and local download. Aggregate tool-use events contain no entries. Save the download if you need to retain the record.

What happened to the previous order?

Keep one replay or outdated-update scenario separate from a successful dispatch demonstration. Record the expected handling beside the observed response and prior-order state. Use approved test evidence; this tool connects to no robot or broker and performs no replay.

Entries stay in this tab and local download. Aggregate analytics receives no typed values. Use non-sensitive references, not credentials or confidential message payloads.

7 replay-evidence fields remain open

  • Robot and fleet software pair, protocol revision and test environment
  • Prior accepted order identifiers, content reference and state evidence
  • Incoming update identifiers, content reference and arrival time
  • Expected handling and exact specification or agreed requirement reference
  • Observed response, error reference and timestamped trace
  • Observed prior-order continuation or replacement, and evidence gaps
  • Reviewer disposition, restrictions, owner and next dated action

A complete record can still withhold acceptance. No trace inspection, schema validation, protocol simulation, conformance finding or operating approval is performed.

Replay evidence added 13 October 2026

VDA 5050's pinned 3.0.0 source distinguishes an outdated update from a repeated update with unchanged or changed content. Its release notes highlight the repeated-ID check. These are specification expectations, not evidence that a named software pair implements them.

Record both the response and what happened to the prior order. An observed warning alone may leave the operational outcome unestablished. The worksheet is RobotAtom's coordination method, not a conformance test suite.

Official VDA 5050 release notes, checked 13 October 2026

A comparison record, not a compatibility checker

VDA 5050 distinguishes mandatory topics, optional topics and supported optional parameters. MassRobotics' implementation material describes shared status information and receiver-side schema checks. These are different scopes; neither document proves that your proposed software pair works at your site.

Use a trace reference and an accountable owner for each material requirement. A matching version string is not a test result. After a build or profile change, have the integration owner decide what evidence needs to be renewed. This record does not replace engineering or safety review.

Read the interoperability requirement guide · Discuss your integration evidence