High priority, destination unavailable
Priority orders eligible work. WCS retains blockers and assesses independent executions under dispatch policy.
TRUSTED FACTORYFLOW
Automation & Robotics
WCS connects business demand to executions, fleet missions and robot cells under explicit execution conditions.
Equipment works within explicit business conditions.
Automation & robotics
Robot count alone cannot establish flow. Priority work may wait for a station, load capability or cell condition; an acknowledgement does not establish delivery. The workspace links tasks, executions and vendor work to expose blockers and reconciliation needs.
WCS checks eligibility, organizes steps and dispatches through fleets or adapters. Robot cells bind work orders to approved recipes/programs and QC. The selected fleet/RCS retains its traffic domain; controllers/PLCs retain field motion and safety interlocks.
People and records in this workspace.
ROLES
WCS dispatcher · fleet operator · cell engineer · station owner · OT integrator
OBJECTS
Tasks, executions, steps, stations, maps/profiles, vendor missions, cell jobs, recipes/programs and QC.
Hold for explicit reasons. Execute eligible work.
Reference journey with sample data.
TASK-010 / EXE-010 / MSN-010 · WO-070 / JOB-070
-
01
Receive released TASK-010 with material, stations and source reference.
-
02
High-priority EXE-010 waits for occupied LINE-01 with an assigned resolver.
-
03
Independent eligible EXE-011 is assessed for dispatch under policy.
-
04
Retain mission/job IDs, verify handover or QC and return outcomes to the business owner.
Inspect records at the decision point.
A workspace-specific concept; open the illustration to inspect the records.
When authorized intervention is needed.
Timeout after dispatch
Query retained vendor IDs and late callbacks. Reconcile UNKNOWN before recreation or reassignment.
Cell program mismatch
Compare approved recipe with actual program/configuration. Engineers resolve mismatch before start; program and QC outcomes bind to the exact run.
Outputs to inspect and accept.
- Separate source waiting, dispatch waiting, travel and recipient waiting.
- Intervention rate by business, equipment and connectivity causes.
- Cells: recipe-specific cycles, QC outcomes and stop causes.
What does this workspace connect to?
A starting scope you can verify.
Select one route or cell and an explicit profile. Test occupied stations, missing ACKs, duplicate callbacks, program mismatch and recovery. Accept physical milestones and business outcomes under one traffic authority per domain.