# When the model is wrong and the lights matter
In February 2021, Texas came within minutes of a total grid blackout. ERCOT (Electric Reliability Council of Texas, the grid operator for most of the state) had load and generation forecasts that badly underestimated how much capacity would freeze offline during Winter Storm Uri. The result: rolling blackouts for millions, over 200 deaths by official count, and tens of billions in damages. No single AI model caused Uri. But the episode is the clearest illustration available of what happens when a forecasting error meets a physical system with no undo button. That is the scenario this lesson is built around: what happens when a load-forecast or outage-prediction model misfires, and how you classify the risk before it happens rather than after.
Modern grid operators lean on machine learning for three core forecasting jobs: short-term load forecasting (predicting demand hours to days ahead), renewable generation forecasting (wind and solar output), and outage or fault prediction (which lines or transformers are likely to fail).
Here is a plausible failure chain, drawn from real categories of incident:
1. A load-forecast model, trained mostly on mild-winter data, underpredicts peak demand during an extreme cold snap.
2. Grid operators commit less reserve generation than actually needed, because the model says demand will be moderate.
3. Demand spikes past the forecast. Reserves are thin.
4. Operators must shed load (deliberate blackouts) to keep the grid from a cascading failure, where the imbalance trips protective relays across a wide area, a failure mode that produced the 2003 Northeast blackout affecting 50 million people.
5. Hospitals, water pumping stations, and gas compressor stations (which need electricity to keep gas flowing to power plants) lose power, compounding the crisis.
The model error at step 1 looks small: a forecast off by 10 to 15%. The consequence at step 5 is not small at all. That gap between the size of the input error and the size of the output consequence is the entire point of this lesson.
Borrow two dimensions from safety engineering, not from generic AI ethics lists, because they mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.Voir la définition complète → directly onto grid physics.
Blast radius: how many people, assets, or systems are affected if the model is wrong.
Reversibility: how easily you can undo the consequence once it happens.
Plot any energy AI use case on this 2x2, and you get a practical governance rule: the higher the blast radius and the lower the reversibility, the more human oversight and pre-deployment testing you require, regardless of how good the model's accuracy metrics look in a lab.
| Use case | Blast radius | Reversibility | Oversight needed |
|---|---|---|---|
| Predictive maintenance scheduling for one transformertransformerA Transformer is a neural network architecture that uses self-attention to process sequences in parallel, powering most modern language and generative AI models.Voir la définition complète → | Narrow | High | Standard monitoring |
| Day-ahead load forecast feeding market bids | Wide | Medium (costly, correctable) | Strong validation, human sign-off |
| Real-time dispatch / automatic load shedding | Wide | Low | Human-in-the-loop mandatory, extensive stress testing |
| Protective relay settings driven by AI | Wide | Very low (can damage equipment, cause injury) | Treat as safety-critical, not "AI feature" |
This is the same logic behind the EU AI Act's (the European Union's risk-tiered AI regulation, in force since 2024 with phased obligations through 2027) risk categories. Energy infrastructure management is explicitly named as a domain that can trigger "high-risk" classification, requiring conformity assessments, human oversight, and documented risk management before deployment. See the European Commission's overview of the AI Act's risk-based approach for the source text.
Don't assume there is a single "AI in energy" law. There isn't, in either jurisdiction, as of 2026. Instead:
United States: NERC (North American Electric Reliability Corporation, the body that sets mandatory reliability standards for the bulk power system) does not yet have an AI-specific standard. Existing CIP (Critical Infrastructure Protection) standards govern cybersecurity and operational risk broadly, and NERC has published guidance treating AI-driven tools used in grid operations as subject to the same reliability and change-management scrutiny as any other operational software. FERC (Federal Energy Regulatory Commission) has opened inquiries into AI's role in grid planning and load forecasting given the surge in data-center demand, but binding AI-specific rules are still emerging.
European Union: the AI Act is the binding instrument. Energy grid management systems fall under Annex III high-risk categories when they affect the safety of critical infrastructure. That triggers requirements for risk management systems, technical documentation, human oversight, and post-market monitoring, obligations that phase in through 2026 to 2027.
Practical takeaway for a manager: regulation lags deployment. That means internal governance (the checks in the next section) is currently doing more real-world risk reduction than external law, especially in the US.
A concrete pre-deployment checklist, calibrated by blast radius:
A simple monitoring snippet, the kind of thing an ops-adjacent analyst should be able to read even if not written by one:
# Flag when live forecast error exceeds backtested tolerance
forecast_error = abs(actual_load - predicted_load) / actual_load
if forecast_error > 0.08: # 8% threshold, calibrated from historical extremes
trigger_alert("Load forecast deviation exceeds safe threshold")
escalate_to_human_operator()The threshold value (8% here, illustrative) should come from your own backtesting, not a vendor default.
Vérification des acquis
1. What is the core lesson illustrated by the Winter Storm Uri scenario for grid forecasting models?
2. Why is a load-forecast model trained mostly on mild-winter data particularly risky for grid operations?
3. What distinguishes this lesson's approach of classifying risk 'before it happens rather than after'?
4. Select ALL correct answers about the three core machine learning forecasting jobs used by grid operators mentioned in the lesson.
Sélectionnez toutes les réponses correctes.
5. Select ALL correct answers about why the failure cascade described in the lesson compounds beyond the initial forecasting error.
Sélectionnez toutes les réponses correctes.
Governance only works if accountability is named in advance, not litigated after the fact.
Utilities using third-party AI forecasting tools (common: Enel, EDF, and US utilities like Duke Energy and Southern Company all use external or hybrid vendor models for load and renewable forecasting) still hold operational responsibility for reliability under NERC standards in the US or national regulator equivalents in the EU. Vendor contracts should specify model validation obligations, but the reliability obligation does not transfer away from the utility just because the model came from a third party.
This is the single most important governance sentence in this lesson: you cannot outsource accountability for a decision just because you outsourced the model that informed it.