Edge, IoT & Compute · Module
Robotics Bridge
Robot missions from business events, with safety kept in the vendor's system
Robotics Bridge is planned to connect robot fleets to business events through Actions, with named approvals and recorded interlocks. One3 never sends motion commands and never overrides a vendor safety system. It is a later-wave (W6) module.
What it does
Robots and business systems often do not talk, so someone re-enters every mission. Robotics Bridge registers robots and fleets (AMRs, delivery and inspection robots, drones; cobot arms read-only), connects to the vendor's fleet manager and standard interfaces through a ROS 2 bridge on the site edge box, and turns One3 events such as pick orders, patrol schedules, deliveries and inspections into missions.
Safety stays where it belongs
One3 never sends motion commands. Missions go to the vendor fleet manager, whose safety system remains authoritative. Safety zones are imported from the vendor configuration and can only be equal or stricter in One3; attempts to weaken them are blocked, and zone changes need the safety owner's approval. An emergency-stop request from One3 is propagated to the vendor system, and the interface states clearly that physical e-stop devices remain primary.
Every mission is physical-risk
Each mission has a named approval, either per mission or a standing template approval with expiry held by a named safety owner. At dispatch an interlock checklist is recorded: vendor safety system active, zones valid, human presence signals clear. Missing interlock evidence blocks dispatch. Anonymous presence signals from Vision AI can add restrictions but never relax a vendor safety condition. Agents may propose missions and schedules but never approve them or hold standing approvals. New templates must pass simulation before going live.
Exceptions go to people
A stuck robot, blocked path or failed pick creates a frontline assistance task with location. Robot incidents always create an EHS incident proposal with mission, robot, telemetry and time. Robots are registered as assets, so errors and run hours create maintenance proposals.
Measured outcomes
Mission analytics track completion rate, cycle time, interventions per 100 missions, utilisation and energy. The roadmap sets physical pilots with positive customer ROI as a W6 gate, and safety interlock design is to be reviewed by a qualified safety professional. Drone plans require an airspace check reference, permissions and a named responsible person (rules to verify).
Features
What Robotics Bridge includes
Robot and fleet registry
AMRs, delivery and inspection robots and drones (cobot arms read-only) with vendor, capabilities, site and thing identities.
Fleet connectors
One vendor fleet manager connector plus an open interface such as VDA 5050 (verify), via a ROS 2 bridge on the edge box.
Site maps and safety zones
No-entry, speed-limited and human-presence zones mirrored from vendor configuration, never weaker.
Mission templates and requests
Move pallet, patrol route, deliver tote and inspection round templates triggered by One3 events.
Physical-risk approval and interlock record
Per-mission or standing approvals with expiry and a recorded interlock checklist at dispatch.
Dispatch and tracking
Approved missions dispatched to the vendor fleet manager with progress and retries.
Live fleet view
Positions, battery, state and errors on site maps with a list alternative.
Exceptions to people
Stuck robots and blocked paths create frontline assistance tasks with location.
E-stop propagation and incidents
E-stop requests sent to the authoritative vendor system; EHS incident proposals with evidence.
Mission analytics
Completion rate, cycle time, interventions per 100 missions, utilisation and energy.
WMS orchestration
Missions sequenced with Inventory & Warehouse tasks and human-robot split proposals.
Mission simulation
Templates dry-run in a simulator before live enablement.
Multi-vendor fleets and drones
Shared zones across fleet managers via a certified orchestrator; drone plans with airspace and permission records.
Robot maintenance
Robots as assets; error codes and run hours create maintenance proposals.
Workflow
Event to safe mission
- 1
A One3 event such as a pick order or patrol schedule fires
- 2
A mission request is created from a template
- 3
A valid standing approval applies, or a named approver reviews
- 4
Interlock checks confirm vendor safety active, zones valid and presence clear
- 5
Mission dispatched to the vendor fleet manager
- 6
Progress tracked; exceptions become frontline tasks or incident proposals
- 7
Completion recorded with analytics and ROI entries
AI
AI skills and Digital Employees
Mission proposal
Drafts pick, move, patrol or inspection missions from business events; permanently capped at proposal.
Exception triage
Classifies stalled or failed missions and routes them to the right human queue.
Interference detection
Shows where robot and human traffic conflict and which zones cause the most interventions.
Incident pack assembly
Timeline, telemetry, zone state, presence signals and vendor log for an EHS incident proposal.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Does One3 drive the robots?
No. One3 never sends motion commands. Missions go to your vendor's fleet manager, whose safety system stays authoritative.
Can an AI agent approve a robot mission?
No. Agents may propose missions and schedules but never approve them or hold standing approvals.
When is Robotics Bridge planned?
W6 (Years 6–10), together with the physical-risk Action tier and safety interlocks.
Does it support drones?
Drone mission plans are planned with an airspace check reference, permissions document and named responsible person. Applicable drone rules are to be verified with counsel.
See Robotics Bridge in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.