Grid SCADA Database Incident Post-Mortem Briefing

Role: Lead Industrial Data Architect specializing in mission-critical SCADA database clusters.

Context

• Grid operating entity: {{grid_operator_name}}
• Database cluster ID: {{cluster_identifier}}
• Root cause trigger: {{incident_trigger_cause}}
• Telemetry ingestion downtime: {{telemetry_loss_duration}}
• Maximum observed replication lag: {{replication_lag_seconds}}
• Primary corrective remediation: {{remediation_action}}

Task

Generate an incident post-mortem email addressed to grid software engineering leadership and operational stakeholders, detailing the root cause, recovery timeline, replication dynamics, and permanent corrective actions for the SCADA database event.

Method

1. Formulate an informative subject line incorporating cluster severity and incident reference code.
2. State the timeline of the disruption impacting {{cluster_identifier}} at {{grid_operator_name}}.
3. Describe the mechanism by which {{incident_trigger_cause}} degraded write throughput and caused {{replication_lag_seconds}} seconds of replica drift.
4. Clarify the telemetry exposure window of {{telemetry_loss_duration}} and how backpressure buffering handled incoming substation signals.
5. Detail the immediate containment steps taken by database on-call engineers to stabilize primary-replica quorum.
6. Elaborate on {{remediation_action}} as the permanent preventative measure.
7. Provide an itemized action matrix assigning technical tasks, Jira epics, and target resolution dates.

Constraints

• MUST maintain an objective, blame-free blameless post-mortem tone.
• MUST NOT expose raw credential strings, internal IP ranges, or restricted grid operational topology.
• Keep total email length under 450 words while preserving technical rigor.
• MUST explicitly differentiate between database downtime and end-user grid control impairment.

Output format

An email formatted with:

• Email Header: Subject, Intended Audience, Incident Reference Number, Severity Classification
• Incident Overview (3 bullet points covering duration, cluster, and impact)
• Chronological Recovery Timeline (3-5 milestone timestamps)
• Root Cause & Data Integrity Analysis (concise technical paragraph)
• Corrective Action Items (markdown table with Action, Owner, Due Date)

Self-review

• Confirm that the replication lag metric of {{replication_lag_seconds}} seconds is placed in technical context.
• Ensure the relationship between {{incident_trigger_cause}} and {{telemetry_loss_duration}} is clearly articulated.
• Validate that all action items are assigned to operational roles rather than specific named individuals.