Cancel during execution
Separate cancel requests from confirmed stops. Query the controller/fleet and reconcile in-transit material before releasing reservations or reassigning work.
TRUSTED FACTORYFLOW
WCS. Turn demand into controlled execution.
Coordinate orders, handovers and execution systems with explicit authority and reconcilable outcomes.
A movement request has more gates than a mission.
WCS coordinates work between business and execution. The selected fleet/controller retains traffic, charging and motion authority.
From task to execution
A task describes required warehouse work. Execution coordinates steps and handovers. Missions or cell jobs assign work to execution systems. Linking these objects explains missing deliveries even when a robot reports completion.
A step opens when data, authority, business state and handover conditions are valid. Controller feedback retains provenance; application states do not replace field safety assessment. Orchestration is designed by use case, not a universal factory algorithm.
High priority does not bypass execution gates.
Reference decision example. Independent orders proceed only when rules and resources permit; this is not a production solver simulation.
| Order | Condition | Decision | Resolver |
|---|---|---|---|
| EXE-010 / high priority | LINE-01 occupied | Hold dispatch; recheck when ready | Coordinator / recipient station |
| EXE-011 / independent | Released task, ready destination/profile | Eligible under rules; locked resources remain protected | WCS / Fleet |
| EXE-012 / UNKNOWN | Previous physical effect unresolved | Query mission/field before retry | Adapter / field owner |
Who confirms what at each handover?
-
01
WMS/MES releases eligible work with source IDs.
-
02
WCS checks step dependencies, destination and permitted profile.
-
03
Fleet/cell accepts work; the adapter retains external IDs, ACK and native outcomes.
-
04
WCS reconciles execution; WMS/MES validates evidence and confirms business results.
See eligible work and explicit blockers.
EXE-010 waits for LINE-01; independent EXE-011 is eligible; EXE-012 needs reconciliation. Each decision retains accountability.
Cancel, pause and retry need actual state.
Lost response
Retain key, hash and external ID and inspect outcomes before resubmission. UNKNOWN cannot be automatically treated as failure.
Duplicate or stale callback
Deduplicate and order-check under contract. Use snapshots or authorized reconciliation for missing data; never regress domain state.
Measure bottlenecks before adding equipment.
Separate source wait, dispatch wait, travel and receipt wait during the pilot. Engineering tests duplicates/timeouts; management assesses whether process, integration or equipment capacity addresses the delay.