
Control Tower Alerts & Incident Playbooks
N.B. Upload cohort cash flows and allocate shared overheads consistently. Clarify treatment of goodwill and construction-in-progress for invested capital.
📄 Prompt Template
Design a control-tower monitoring and response framework for distribution resilience tailored to [Role]. Define leading/lagging signals for [KPI1], alert thresholds at [AlertThreshold], and escalation SLAs (acknowledge within [TimeToAcknowledge]). Create standardized playbooks with a clear [EscalationPath] for DC outages, port congestion, carrier failure, customs holds, and extreme weather.
Output format: (1) “Alert_Definitions” JSON array with fields: kpi, signal, threshold, condition, frequency, owner_role, channel, sla_minutes. (2) “Incident_Playbooks” markdown sections (one per incident) with Triggers; First Hour Actions; Containment; Comms Template; Recovery; Exit Criteria. (3) RACI table by function for critical decisions.