
Early-Warning Indicators (KRIs) & Trigger Architecture
📄 Prompt Template
Establish a disruption early-warning system for [Company] by defining [KRIs] linked to actionable triggers. Specify data pipelines from [DataSources], alert logic using [AlertThresholds], and a [MonitoringCadence]. Produce: (A) Executive Summary; (B) Indicator Catalogue (markdown table: KRI, Definition, Source, Threshold, Owner, Response); (C) Trigger-to-Action Map with time-bound playbooks; (D) Dashboard specification (latency, availability, drilldowns); (E) Governance & On-call Roster ([Owners]); (F) Backtesting results and false-positive mitigation. Include examples: port queue length, berth delays, AIS congestion heat, weather alerts, customs holds, driver availability, cyber IOC hits. Define severity tiers and SLAs for response. Conclude with a roadmap to automate alerts into TMS/WMS workflows.