What this demo shows
Disruption to verified recovery, with proof the rest of the plan was left alone.Objective
Something breaks on the inbound side. Show which lines are at risk and when, price the recovery options against downtime avoided rather than a yes/no, verify every option is legal before offering it, and prove the shipments the disruption never touched are byte-identical to the baseline.
Try this
- Set scenario New model launch ramp, plant North Assembly. The baseline shows roughly 523 shipments, all LEGAL.
- Run Carrier breakdown with a 14 hour delay. The truck now docks after
receiving closes and
receiving_windowsays by exactly how much. - Run Customs hold. One event hits 46 cross-border shipments at once and adds roughly 100 hours of downtime.
- Run JIS sequence break. The cart arrives short of a whole block, so
sequence_integrityfails: parts on the dock, line still stops. - Compare the four recovery options on cost per hour avoided, not sticker price.
What to look for
- The baseline is legal before you touch it. Any rule failure you see is caused by the disruption, never by sloppy plan generation.
- The broken rule names the measured value and the limit, not just a red light. That trace is the product.
- An option landing after the stop cannot prevent it and says so, while still showing the downtime it removes. "We are going down, the question is how long" is a real answer.
- The cheapest option is often not the best value per hour recovered.
- Untouched shipments are hashed and compared server side, so the guarantee is asserted rather than claimed.
Synthetic, seeded data. Recovery costs are illustrative parameters, not benchmarked freight rates. Full method: Re-Planning documentation · related: Line-Down Clock, EDI Transaction Health.
Baseline inbound plan
Every inbound shipment is split to fit one trailer on cube and payload, given a dock slot inside the receiving window with door capacity respected, and checked against all six inbound rules. The baseline is legal by construction, so a disruption is what breaks it, never sloppy plan generation.
Introduce a disruption
Five inbound failure modes. Each one recomputes the clock, re-verifies the whole plan, prices recovery options against downtime avoided, and diffs the result against the baseline.
Impact
| Part | Supplier | Before | After | Stops at | Downtime before | Downtime after | Delta |
|---|
Rules the disruption broke
Complete certificates for shipments that no longer pass. Every rule is shown with its measured value and limit, pass or fail: the full trace is the product, not a black-box OK.
Recovery options
Each option is built as a real shipment and verified against all six rules before it is offered. Ranked by cost per downtime hour avoided, which is the decision a plant actually makes. An option that lands after the line already stopped cannot prevent the stop, and the board says so rather than hiding it.
Untouched-plan guarantee
Every shipment the disruption did not touch is hashed before and after and compared. This is asserted server side, so a drift would raise rather than quietly ship.