Define Alert Rules & Escalations for a Transport Control Tower
N.B. If available, upload historical financials for both companies and a recent cap table. Specify accounting basis (IFRS/US GAAP) if different from default. Confirm whether to exclude stock-based compensation from EPS.
📄 Prompt Template
Create a unified alerting and escalation framework for [Company]’s control tower operating on [System] across [Region]. Identify top risk signals tied to SLA breaches for [MetricA], [MetricB], and [MetricC] (e.g., ETA variance > X min, temperature excursion, customs hold, yard congestion). For each signal, define detection logic, suppression rules, alert severity, and ownership across [RoleOps], [RoleCustomer], and [RoleCarrier].
Output format:
Alert Policy YAML (blocks per signal: signal_id, description, trigger_logic, debounce, severity, channels, owner, SLA, playbook_link).
Escalation Matrix (Markdown table: Severity | T+5 | T+15 | T+60 | 24h | Executive).
Incident Playbook Template (checklist: contain → communicate → correct → confirm).
Service Recovery Credits Rules aligned to [SLATargets].
Metrics to Monitor Alert Quality (precision, recall, time-to-ack, time-to-resolve).
Ensure the design closes the loop with post-incident reviews feeding backlog prioritization and weekly trend reviews. Provide example trigger logic using ETA vs. PTA, dwell > threshold, and IoT sensor failure detection.