Indoor delivery robots

Do mobile robots need a common standard to work in a building?

Understand the role of fleet and robot interfaces while keeping elevator, door, safety, building, and vendor compatibility as separate checks.

For: Technical buyers, building-system integrators, facility IT, and robotics vendors. Follow this topic

Short answer

What to know

A common interface can improve communication between robots and a fleet or master-control system, but it does not make every robot compatible with every building system. Buyers still need to validate the exact versions, workflow, elevator and door interfaces, safety behavior, network, security controls, and vendor support for the deployed configuration.

Match the standard to the interface

VDA 5050 is an example of an interface specification for communication between mobile robots and a master control system. Determine whether the vendors support the same version, required message features, and operational model. Ask which functions are actually interoperable and which remain proprietary or dependent on a vendor-specific adapter.

Do not extend an interface claim beyond its scope. Fleet coordination is distinct from elevator dispatch, door access, building-management systems, fire alarms, or public curb operations. Each boundary needs an owner, documented integration method, permission, test plan, and fallback.

Verify safety and lifecycle compatibility

Check applicable safety standards and the product’s intended operating environment, then have qualified professionals determine how they apply. ISO 3691-4 addresses safety requirements and verification for driverless industrial trucks and their systems; it should not be read as a universal certification for every service robot or building deployment.

Record versions, network dependencies, update policy, event logs, and vendor support commitments. Test two vendors or systems only if the building has a real multi-vendor requirement; otherwise avoid integration complexity that does not support a defined operating benefit. Revalidate after software, controller, or equipment changes.

Put it into practice

A site-planning checklist

  • Specific interface and standard edition
  • Compatibility matrix across all system boundaries
  • Applicable safety evidence and scope
  • Fallback for disconnected or unsupported interfaces
  • Version and update governance

Further reading

Primary references

  1. VDA — VDA 5050

    Interface specification for communication between mobile robots and a master control system; it does not certify a building or robot.

  2. ISO — ISO 3691-4:2020

    International safety requirements and verification for driverless industrial trucks and their systems; confirm current editions and scope before use.