Demand
Order, replenishment, storage, sort, packaging, and exception work enters the shared task engine.
Warehouse automation orchestration
Put people and machines on one execution loop.
Translate warehouse demand into governed missions across autonomous guided vehicles, autonomous mobile robots, robot cells, sortation, put-to-wall, storage equipment, and packaging—without taking motion or safety authority from machine controllers.
Mission, not motion
The WMS owns business intent; controllers own safe movement.
XMS Cloud assigns and reconciles missions at the WES/WCS boundary. Vendor controllers and PLCs retain the device-level authority they are designed to hold.
Orchestrate
Match resource capability, priority, location, lease, safety state, and business constraint.
Dispatch
Send a governed mission through the configured vendor, fleet, cell, WCS, or PLC adapter.
Reconcile
Compare intended, commanded, acknowledged, observed, and completed state; escalate divergence.
AGV fleet control
One mission model across vendor fleets.
Supervise robot health, battery, pose, mission, reservations, keep-out zones, and digital-twin overlays without flattening vendor-specific capabilities.
- MiR, OKAGV, SEER, HeLi, and simulator adapters.
- Auto-dispatch, relay legs, queues, chargers, elevators, and safe reservations.
- Fail-closed checks before a physical command leaves the platform.
Automation lanes
Coordinate fixed and mobile automation with the floor.
Robot cells and sortation
Dispatch piece-pick work, account for gripper capability, track lanes and stations, and reconcile machine reports.
Put-wall and light guidance
Bind walls, slots, orders, PTL controllers, scans, exceptions, and completion to the same fulfilment state.
AS/RS, shuttles, VLM, lifts
Queue service, lease shared resources, detect divergence, and guide safe restart without hiding PLC ownership.
Finish line
Watch the automatic end-of-line as one system.
Carton erectors, sealer/labellers, palletizers, conveyors, and supporting machines expose health, consumables, jobs, exceptions, and OEE to warehouse control.
Machine healthMagazine levelOEEJob stateStuck probeClose pallet
The failure test
Prove that unsafe and unknown state cannot pass silently.
Ask for the raw transition evidence. A green equipment tile is not proof that the command was permitted, acknowledged, or physically completed.
Block before write.
Remove E-stop-clear, zone-empty, guard-closed, or upstream-ready from the observed set. The named command must be refused with no tag write.
Unknown is not commandable.
Return non-Good quality on a bound write or observation tag. The gateway must refuse or preserve not-observed state instead of assuming success.
Trip the watchdog.
Issue a permitted command but withhold acknowledgement and completion. The handshake must end timed out and retain the business context for recovery.
No automatic reset.
An unknown fault must require classification, operator acknowledgement, a complete safe-state checklist, and a manual restart decision.
Call it ScopeLimited.
A missing emulator or replay scenario must appear as uncovered capability bound to adapter and product build—not a generic supported badge.
Reconcile physical truth.
A lane, cell, or shared resource that disagrees with its reservation must remain an operational divergence until a clean observation or resolution.
Prove before hardware
Emulate the lane before commissioning it.
Simulator adapters and in-process twins exercise missions, reports, exception paths, and UI behavior without claiming a production machine is connected.
Hardware-free rehearsal
Run representative AGV, robot, sortation, MHE, and finish-line workflows before vendor credentials or equipment are available.
Explicit adapter readiness
Keep simulated, configured, connected, and production-qualified states distinct.
Test the failure path
Exercise timeout, rejection, divergence, retry, escalation, and safe restart before go-live.
Review one automation lane
Bring the demand, equipment, and authority boundary.
Map missions, safety gates, vendor APIs, programmable logic controller ownership, acknowledgements, exceptions, and recovery.