Demand
Warehouse task names source, destination, load, capability, priority, tenant, and business context.
Mobile-robot integration
Orchestrate robot missions without taking motion authority.
Available with configuration
XMS Cloud converts warehouse demand into canonical missions, reservations, acknowledgements, and reconciliation. Vendor fleet managers, robot controllers, and safety systems retain route execution, motion, and interlocks.
Mission contract
One business handoff across different fleet dialects.
Reserve
Lease robot, lane, lift, charger, traffic zone, station, or shared resource before dispatch.
Dispatch
Translate canonical mission intent into the configured fleet-master, VDA 5050, per-robot, TCP, or HTTP dialect.
Reconcile
Track accepted, rejected, active, completed, cancelled, timed-out, and physically divergent state.
Cataloged dialects
Protocol availability and robot capability are separate.
E300 fleet API
HTTP fleet adapter with emulator coverage and canonical exchange recording.
HeLi SL100 D2 and HSAS/HRCS
HTTP fleet integrations; SL100 D2 is transfer-only with no jack or cruise mission claim.
VDA 5050
MQTT fleet dialect with vehicle-negotiated version and topic/security configuration.
OKAGV ACI
TCP binary fleet-master integration; transfer-only with no map or pose telemetry claim.
SEER RDSCore
HTTP order API for master-controlled fleets; sealed transfer orders with no map-raster claim.
MiR REST
Per-robot REST v2.0.0 integration; transfer missions, while robot scheduling owns charging.
Simulated fleet
In-process adapter for mission, exception, UI, and recovery rehearsal before hardware binding.
Safety and failure boundary
Unknown state does not become completed work.
Trip the mission watchdog.
Retain command and business context, stop blind progression, and route recovery ownership.
Reject before dispatch.
Do not send jack, pick, cruise, elevator, or charging work to a dialect that does not expose it.
Compare intent with the floor.
Raise one evolving alert when pose, lane occupancy, load state, or reservation disagrees.
Preserve mission ownership.
Retry only idempotent handoffs; do not create a second commander or silently duplicate movement.
Controller remains final authority.
XMS Cloud does not bypass robot, fleet, PLC, or certified safety behavior.
Requalify the adapter.
Vendor firmware, API, protocol, map, or fleet-master changes invalidate stale proof until regression passes.
Fleet supervision
See health, mission, and position beside warehouse work.
The control surface keeps vendor, robot, battery, pose, mission, reservation, alert, and digital-twin context visible without claiming to be the safety controller.
- Canonical mission and vendor exchange evidence.
- Shared-resource reservation and release.
- Physical divergence and recovery ownership.
AGV compatibility review
Bring the vendor, fleet master, robot capabilities, map, missions, and safety boundary.
Qualify protocol, authentication, version, topology, acknowledgements, failure behavior, exchange recording, and recovery.