Utility Tabletop Exercise: Grid Strain and a Control-Center Incident
A generic, reusable tabletop exercise template for electric, gas, and water utilities. Run it on paper in about 90 minutes. Replace bracketed details to fit your organization. No real organization names are used.
This exercise is aligned to NERC CIP incident-response and recovery expectations and designed to support utility emergency-operations and mutual-assistance planning. It does not by itself satisfy any standard or ensure compliance.
Scenario summary
An extreme-weather event drives demand and stresses the system just as a control-center anomaly raises the question of whether a failure is equipment, human error, or something deliberate. Over the exercise the team manages load and reliability, works a possible insider or intrusion concern without jumping to conclusions, protects crews and the public, coordinates with regulators and neighboring utilities, and communicates through a long, escalating event where the margin keeps thinning.
Exercise objectives
- Maintain reliability and make load-management decisions under stress, with a clear decision owner and a documented rationale.
- Triage a control-system anomaly across equipment failure, human error, and malicious causes without prematurely committing to one.
- Protect field crews and the public, with a clear rule set for what work proceeds and what holds.
- Engage regulators, neighboring utilities, and mutual assistance on the right timelines.
- Communicate consistently with customers and the public through a long, uncertain event.
- Preserve the information and evidence needed for later root-cause and reporting, without impeding operations.
Participants and roles
- Incident commander — senior operations executive who runs the response.
- Control-center / operations lead — reliability, load, and the real-time picture.
- Security (OT/physical) — intrusion, insider, and site-security questions.
- Field operations — crew safety and restoration work.
- Regulatory / compliance — reporting obligations and reliability coordination.
- Communications / PR — customer, public, and official messaging.
- Executive sponsor — approves major trade-offs and external posture.
- Facilitator — delivers injects, keeps time, captures decisions (not a participant).
Injects
T+0 — Demand climbs and something looks wrong. Delivered to: control-center lead → incident commander. An extreme-weather event is driving demand toward the system's limits. A setpoint on a control system reads differently than expected, and it is not yet clear whether it is a sensor fault, a mistake, or a change no one authorized.
- What is the first reliability action as demand rises, and who owns it?
- How do you triage the anomaly without assuming either "glitch" or "attack"?
- What information do you start preserving now in case this becomes an investigation?
T+25m — Units start tripping. Delivered to: control-center lead. Generation or supply units begin dropping, and the operating margin narrows. Shedding load would relieve the strain but affects customers, some of them sensitive.
- How is the load-management decision made, and who holds the authority?
- How do you account for medically sensitive or critical customers?
- What do you commit to publicly, and when?
T+50m — The anomaly points inward. Delivered to: security (OT/physical) + operations. A review traces the changed setpoint to internal credentials, and the account belongs to someone recently passed over. Nothing is confirmed, and the person is on an upcoming shift.
- How do you handle a possible insider concern fairly while protecting the system?
- Who makes the call about that person's access and shift, and on what basis?
- How do you keep this contained so you do not taint an innocent employee or an investigation?
T+1h30 — A public-safety report. Delivered to: field operations + communications. Conditions are producing real public-safety risks (for example, carbon-monoxide calls in an outage, or hazards near downed assets). Field crews are stretched, and some work cannot be done safely right now.
- What is the rule for what work proceeds and what holds, and who enforces it?
- How do you prioritize crews across competing emergencies?
- What does the public need to hear to stay safe?
T+3h — Regulators and neighbors. Delivered to: regulatory / compliance + incident commander. A regulator asks for a situation report with what is known, estimated, and unknown kept distinct. Mutual-assistance crews from neighboring utilities are offered or arriving with no one assigned to integrate them.
- What do you report, and how do you separate fact from estimate?
- Who folds in mutual-assistance crews so they are useful rather than idle?
- What reporting clocks, if any, have started?
T+6h — The margin is nearly gone. Delivered to: control-center lead + executive sponsor. The system is holding but thin, one failure away from harder measures, and the event is not close to over. Fatigue is setting in across operations.
- How do you sustain operations and decision quality over a long event?
- What is the threshold that triggers the next, harder step, and who decides?
- How do you set honest public expectations about duration?
T+12h — The story turns. Delivered to: communications + executive sponsor. As conditions ease, coverage questions whether the event was avoidable, and a public account from an affected customer spreads. A regulator signals a review.
- How do you respond without pre-judging your own root-cause findings?
- What do you owe the affected customer and the public now?
- Who speaks for the utility as scrutiny grows?
Contingency — A second front. Delivered to: incident commander. A second weather system or a second damaged asset appears while crews and margin are already drawn down.
- How do you re-prioritize with resources already stretched?
- What changes about the public message when the event extends?
After-action checklist
- Load-management decisions made with a clear owner, rationale, and timing.
- Anomaly triaged across equipment, human-error, and malicious causes without premature commitment.
- Insider/intrusion concern handled fairly, with access decisions documented.
- Crew-safety and public-safety rules applied consistently under pressure.
- Regulator reporting and mutual-assistance coordination run on the right timelines.
- Public communication consistent and honest about fact versus estimate.
- Evidence and information preserved for root-cause and reporting without impeding operations.
- Sustainment plan for a long event (staffing, fatigue, decision cadence) exercised.
Frequently asked questions
How long does this utility tabletop exercise take?
About 90 minutes, covering an extreme-weather demand surge, a control-system anomaly, crew and public safety, and regulator coordination.
Can electric, gas and water utilities all use it?
Yes. It's written for any utility. Replace the bracketed details with your own systems, sites and reporting obligations.
Can this tabletop count toward NERC CIP-008 testing?
CIP-008 accepts a tabletop exercise as one way to test a Cyber Security Incident response plan at least once every 15 calendar months for high and medium impact BES Cyber Systems. This template is aligned to NERC CIP incident-response expectations but doesn't by itself satisfy the standard.
Why does it include a possible insider?
Real incidents rarely start labeled. The exercise tests whether your team can look at equipment failure, human error and deliberate action together, without accusing anyone too early.