← Back to knowledge center

Mixed AMR fleets: VDA 5050 and OPC UA without illusions

An open interface can connect robots from different vendors, but it does not make the machines identical. Kinematics, navigation, payload constraints, charging and diagnostic behaviour still differ.

V
Virtek Robotics TeamRobotics, automation and systems integration

Separate two types of communication

VDA 5050 connects a central fleet controller with mobile robots and structures orders, state messages and instant actions. OPC UA Robotics provides an information model for robot-system data and is well suited to telemetry, equipment structure and production-system integration. The interfaces complement rather than replace one another.

Do not turn the mission controller into a telemetry historian, CMDB and safety system at the same time. Those functions have different lifecycles and assurance requirements.

Define a compatibility profile

Vendors may support different capabilities even under the same specification version. Record supported nodes and edges, actions, zone handling, permitted deviations, maps, charging, pause, cancellation and error semantics. Run contract tests for every robot type before it enters the live fleet.

Treat robot or fleet-software upgrades as interface changes. Validate compatibility in a test environment before production rollout.

Manage zones and conflicts explicitly

The controller must know where a robot can stop, turn, yield and recover a route. Lifts, doors, shared equipment and areas with people should be represented as resources with ownership rules and timeouts. Otherwise, a multi-robot deadlock becomes a manual dispatch problem.

Local robot safety remains independent of a network instruction. Loss of communication must not disable protective functions.

Build shared observability

Correlate mission ID, route, robot state, map version, battery status, operator action and upstream-system event. Time synchronization and consistent reason codes are essential: “mission failed” is not sufficient evidence.

Track completed missions, waiting time, zone contention, interventions, errors by type, availability, charging cycle and communication recovery.

Preserve supplier portability

Keep the business task separate from a vendor-specific command, version maps and zone rules, and isolate non-standard extensions behind explicit adapters. A new supplier will still need a profile and acceptance tests, but the business process will not need to be rewritten.

Need an architecture
for your workload?

We will review inputs, risks and constraints, then propose a reasoned solution.

Talk to an engineer↗︎