TYPICAL CURRENT STATE
Disconnected information.
Demand, fleet and receiving stations report separate states. Dispatchers investigate waiting loads manually; retry can duplicate missions if prior acceptance is unknown.
TRUSTED FACTORYFLOW
Internal transport with explicit handovers
Turn movement demand into gated, observable execution that reconciles with its source system.
Equipment is moving. Has the work actually finished?
The bottleneck to resolve
A robot mission often covers movement only. Factory work also depends on material readiness, destination capacity, recipient actions and source-system confirmation. If each party closes work at a different milestone, managers cannot distinguish travel, handover waiting and accepted completion.
Start with an identified source/destination route, described load and one fleet/traffic authority. Equipment participates through selected profiles; controllers are not assumed to share a protocol.
Where does the operating flow change?
REFERENCE CONFIGURATION
Explicit confirmation milestones.
Executions retain source-task and vendor-mission IDs. WCS exposes blockers; the selected fleet coordinates vehicles. Pickup/drop-off evidence returns to the business owner for closure.
Follow one demand to its outcome.
Transport dispatcher · station owner · fleet operations · integrator
MOVE-030 → TASK-030 → EXE-030 → MSN-030
-
01
The source system requests a move from A-03 to STATION-03 with load requirements.
-
02
Check material, handover station and executor profile; hold ineligible work.
-
03
Dispatch through fleet/adapter, retain the vendor mission ID and distinguish ACK from progress.
-
04
Validate pickup/drop-off and reconcile the source task before business closure.
When work does not follow the expected path.
Each blocker has its own data, authority and resumption conditions.
Destination occupied
Hold execution at the relevant step and expose the station owner. Destination changes require authority, route and source-task rechecks.
Ineligible equipment
Compare load and station needs with permitted profiles; reassign only after reconciling the old mission to avoid dual pickup.
Lost acknowledgement
Query external mission IDs and late callbacks. Retain unresolved outcomes; timeout does not establish failure or authorize recreation.
Measure the right problem before scaling.
Measures to agree for the pilot, not promised improvement levels.
Completion time
Separate source wait, dispatch wait, travel and recipient wait before deciding whether more robots address the bottleneck.
Intervention rate
Measure executions needing intervention by cause against the in-period total; separate business blockers from robot faults.
Duplicate effects
Compare each source demand with created missions and accepted outcomes; resolve duplication before scaling.
Initial scope and expansion conditions.
A pilot with explicit outputs
Choose one load type, route and handover group. Test occupied destinations, unavailable equipment, timeout and cancellation during execution. Acceptance checks physical state and vendor IDs, not HTTP responses alone.
Conditional expansion
Scale after agreeing map/points, traffic authority and handover rules in each area. Multi-vendor coordination is designed by orchestration domain; competing traffic masters cannot independently command the same scope.
Components and assessment documents.
Map this use case to your factory.
Discuss stations, existing systems and the measurement period to define the first investment scope.