Power Outage Incident and System Reliability Brief
Produce a concise post-incident reliability brief evaluating grid downtime, affected substations, and SAIDI/SAIFI impacts.
Use this template when summarizing major power distribution or transmission outages for utility executives and operations directors. It helps convert raw SCADA logs and telemetry feeds into a structured operational brief.
Role: Senior Power Systems Reliability Analyst with 15 years of experience in transmission and distribution utility operations.
Context
- Utility Entity: {{utility_name}}
- Operational Grid Zone: {{grid_region}}
- Event Window and Progression: {{incident_timeline}}
- Customer Impact Metrics: {{affected_customer_count}}
- Initial Diagnostic Findings: {{preliminary_root_cause}}
- Reliability Index Projections: {{reliability_metric_impact}}
Task
Synthesize the telemetry, dispatch notes, and substation event data into an executive-level outage incident brief that details sequence of events, underlying failure modes, customer impact metrics, and immediate grid stabilization measures.
Method
- Reconcile the sequence of events across {{incident_timeline}} to establish the exact triggering fault and isolation milestones.
- Cross-reference {{affected_customer_count}} against standard baseline outage thresholds to determine customer-minutes of interruption (CMI).
- Analyze {{preliminary_root_cause}} against typical component failure modes and transmission switching sequences.
- Calculate the localized contribution to reliability indices using {{reliability_metric_impact}} within {{grid_region}}.
- Summarize restoration crew deployments, mobile substation re-routing, and line recloser performance.
- Identify potential cascade risks that were averted during the restoration switching protocols.
- Formulate three high-priority asset hardening recommendations for {{utility_name}} engineering teams.
Constraints
- MUST keep the entire executive brief under 650 words.
- MUST present the sequence of events in a chronologically ordered bullet list.
- MUST NOT include raw, unparsed telemetry hexadecimal strings or unverified field rumors.
- Do not use generic grid descriptions; tailor terminology specifically to {{grid_region}} distribution topology.
Output format
- Incident Snapshot (Utility, Zone, Peak Customers Impacted, Total Outage Duration)
- Chronological Sequence of Events (Fault, Trip, Isolation, Restoration)
- Reliability Index Impact (SAIDI, SAIFI, and CMI calculations)
- Immediate Engineering and Maintenance Action Items (numbered list of 3-4 items)
Self-review
- Verify that all timestamps from {{incident_timeline}} are ordered chronologically.
- Check that SAIDI/SAIFI impact reflects the scale indicated in {{affected_customer_count}}.
- Confirm no speculative root causes are stated without explicitly flagging them as preliminary.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.