UMP
A manufacturer-neutral protocol built to test world models.
Universal Machine Protocol was built as a testbed for Ontos world models. It lets robots from different manufacturers describe identity, capability, activity, and operational state while preserving native control and safety boundaries.
The interoperability problem
Robots expose different message formats, fleet interfaces, capability descriptions, and operational assumptions. Sharing state across those systems often requires one-off integrations that fragment as manufacturers and sites change.
UMP defines a common semantic layer for awareness and high-level collaboration. It does not control joints, motors, navigation, manipulation, gait, or emergency stops.
Identity, capability, and authority
The versioned UMP 0.1 wire protocol covers identity, capability, activity, intent, progress, availability, pose, safety, health, battery, and freshness. Goals and assignments are bounded by plan validation, owner-issued authority leases, adapter constraints, and native acceptance.
The manufacturer adapter begins read-only. Missing information remains unknown rather than being guessed, and every robot keeps its own controller, autonomy, and safety system.
Communication and integrations
The reference implementation includes mutual-TLS transport, discovery, authentication, replay protection, disclosure policy, durable inboxes and outboxes, restart reconciliation, and a read-only traffic inspector.
Documented integration boundaries cover MassRobotics, VDA 5050, Open-RMF, ROS 2, and OPC UA Robotics. These are protocol and laboratory integrations, not proof that arbitrary robots from those ecosystems are physically interoperable.
Implementation and qualification status
UMP is an alpha reference implementation and software qualification laboratory. Its mixed-fleet laboratory provides deterministic scenarios, live middleware probes, fault and load profiles, signed evidence, and a Gazebo reference world.
A passing software path proves protocol behavior under its test conditions. It does not certify a robot, replace manufacturer controls, or prove physical compatibility. Supervised hardware trials should begin only after the documented readiness gate passes.
Common questions
What is Universal Machine Protocol?
UMP is a manufacturer-neutral protocol and reference implementation built as a testbed for Ontos world models. It supports shared robot identity, capability, state, and bounded high-level assignments.
Can robots from different manufacturers communicate through UMP?
UMP provides a common semantic and transport boundary for adapters. Each manufacturer integration still needs explicit mappings, acceptance checks, and qualification.
Does UMP control motors or replace robot safety systems?
No. Native controllers execute work and retain their safety systems. UMP carries awareness and bounded assignments above that boundary.