Equipment identity
A conveyor segment, machine, cell or station is bound to the warehouse topology and site.
Fixed material flow
Connect warehouse tasks to machines while their controllers remain in charge.
Ysend links each task, load and destination to conveyors, sorters, put-wall stations, finish lines, packaging machines and robotic cells. PLCs and machine controllers retain sequencing, interlocks and emergency-stop authority.
Material path
Each load stays identifiable through every cell
-
Release Work enters the line
The warehouse workflow names the load, destination and required operation.
-
Route Conveyor and sorter state shape the path
Segment availability, buffers and equipment bindings constrain the next handoff.
-
Process A station performs its bounded action
Put-wall, finish-line, packing machine or robotic cell reports accepted state and outcome.
-
Handoff Warehouse custody advances
The next operation opens only after the expected identity and completion evidence reconcile.
PLC binding
Registers become semantic equipment state
The integration maps controller data to named warehouse equipment and operations instead of exposing raw addresses as business commands.
Register map
Inputs, outputs, state and acknowledgements follow the versioned controller mapping for that device.
Load details
LPN, carton, tote, pallet or task identity stays attached to the expected handoff.
Semantic command gate
The application asks for an outcome, not arbitrary register writes
Allowlist
Only commands defined for the equipment type and current workflow state can pass.
Watchdog
Missing acknowledgements, expired state and connection loss close the command path.
Role and scope
Warehouse, device, user and authorisation scope are checked before an operator action is issued.
Audit
Request, controller acknowledgement, resulting state and exception remain attributable.
Buffers and faults
Recover material flow from a known physical position
Blocked segment
The affected loads and the queue upstream are visible before a reroute or intervention.
Station refusal
A rejected command remains a failed request; it is not converted into a completed warehouse operation.
Manual recovery
The operator follows a guided procedure that rechecks identity, location and custody before resuming.
Replay
Line state and warehouse events can be reviewed together to explain the interruption.
Walk the line from release to recovery
Bring the equipment list, register maps, load identifiers, controller owner and safety boundaries. We will map each handoff to the warehouse workflow.