Robotics · R-06
Robots that talk to your warehouse, hotel or store systems.
Connections between robots and the systems a site already runs: WMS, WES and ERP in warehouses, PMS and POS in hotels and stores, elevators and doors in buildings, and the VDA 5050 and Open-RMF interfaces between robots and the systems that dispatch them.
- WarehouseWMS, WES and ERP
- Hotel and storePMS and POS
- Buildingelevators and doors
- StandardsVDA 5050 and Open-RMF
What we connect
Tasks in, status out, every message logged
Each integration is an adapter in your repositories, with retries, logs and a test suite that runs against a sandbox before it touches a live site.
Warehouse systems
Tasks from the WMS or WES to the robots, status and exceptions back, and the counts the ERP needs, mapped field by field and agreed with the site in writing.
Hotel PMS and store POS
Deliveries and room service triggered from the property system, orders from the point of sale, and the status a guest or a cashier can see.
Elevators and doors
Calls to elevators and door controllers through the building's own interfaces and on its owner's integration terms, so a robot can move between floors and rooms.
VDA 5050
The VDA 5050 interface between mobile robots and a master control, for sites that dispatch robots from more than one maker.
Open-RMF
Open-RMF adapters for buildings where robots from different makers share corridors, lifts and doors.
Adapters you can run
Retries, dead-letter queues, logs per message and alerts when a system stops answering, with a runbook your team or the integrator can follow.
How it starts
One site, one system, then the next
- NDA first. Then the site, the systems it runs and what the robots should do with them
- A written integration note: messages, fields, errors and who owns each system
- An adapter tested against a sandbox or a copy of the system, then on one site
- More sites and systems, then handover with a runbook, or we stay on
Who does what
- Digi117: the adapters, tests, logs and runbook
- The system owner: access, test accounts and integration terms
- The robot's own software: motion and safety
- You: the final say on every go-live
Questions about robot integrations
Do you work with the robot maker's own fleet manager?
Yes, where it has an API. The adapter talks to the fleet manager, and the fleet manager talks to the robots.
Our WMS is old and has no API. Can you still connect it?
Often, through files, a database view or a message queue it already writes to. The integration note says which route and why.
Who owns the integration code?
You do. It lives in your repositories from the first commit, with tests and a runbook.
Can robots from different makers share one site?
That is what VDA 5050 and Open-RMF are for. We build the adapters for the robots and the site systems that need them.
More robotics service lines: North America launch for robot makers · Fleet console and remote operations · Signed software updates for robots · ROS 1 to ROS 2 move. All ten on the Robotics page.
Tell us which systems and which robots.
Send the site type, the systems it runs and the robots on it. We reply with what we would connect first.
Reply within one business day