
Cyber/OT Disruption Scenario for DCs (WMS/TMS Outage)
N.B. Upload SKU- or segment-level history to enable accurate mix calculations. Confirm whether discounts/rebates are netted in price and whether cost inflation is embedded in [CostMetric].
📄 Prompt Template
Construct a cyber/OT disruption scenario where [WMSVendor] is unavailable across [SitesImpacted]. Define business impacts (receiving, putaway, picking, loading), manual fallbacks, data reconciliation, and safe operations. Specify RTO [RTO] and RPO [RPO], cutover steps to degraded mode, and re-cutover back to normal; detail dependencies on [ThirdPartyIT].
Output format: (1) “Resilience_Controls” markdown table with columns: Control; Scope; Prevent/Detect/Respond; Owner; Test Frequency; Evidence. (2) “Runbook_Degraded_Mode” numbered steps for day-0 to day-3 with staffing, batch printing, shadow inventory, and shipment release criteria. (3) “Recovery_Runbook” steps with data validation, inventory cycle count, and risk acceptance gate.