Scenario pattern / exception recoveryMeasure the path back to controlled flow
A throughput run under clean conditions cannot demonstrate how the system behaves when a destination is occupied, a load identity is missing or a confirmation arrives late. The script injects one defined condition, records which layer detects it and observes the action that clears or escalates it.
Recovery time is interpreted with the affected flow boundary. A robot-level reset, a route closure and a facility-wide material-flow interruption are not equivalent events. The acceptance record states the start event, end event, exclusions and any manual actions so later comparisons use the same definition.
In a representative goods-to-person feed cell, a blocked-destination drill is often timed across a 30-minute observation window after a 15-minute stabilization period. The log captures fleet management system alarms, PLC handshake timeouts in seconds and whether tote identity is restored before the next order wave. These timings are method templates; site-specific scripts replace them after the load table and interface revision are locked.
- Trigger
- Blocked station, message timeout or invalid identity
- Observation
- Alarm propagation, mission state and physical load position
- Closeout
- Authorized restart and downstream inventory confirmation