Leaders Insights
Leaders Insights

Rester au meilleur niveau, un peu chaque jour.

DomainesMarketingDataFinanceIA
RessourcesApprendreTestOutilsBlogGlossaire
© 2026 Leaders Insights — Tous droits réservés.
Formations/AI in energy/Governance, risks and checks/Why energy AI needs its own rulebook
1/4+150 XP

Governance, risks and checks

10Why energy AI needs its own rulebook+15011When the model is wrong and the lights matter+15012The bias hiding in your meter data+15013The pre-launch checklist utilities can't skip+150

Why energy AI needs its own rulebook

# Why energy AI needs its own rulebook

A transmission operator in Texas wants to deploy a machine learning model to predict 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 → failures before they happen. The model needs real-time data from grid sensors. Those sensors sit inside systems classified as Bulk Electric System (BES) Cyber Assets under NERC CIP, the Critical Infrastructure Protection standards enforced by the North American Electric Reliability Corporation. The same utility, if it operates in Europe, may also need to check whether that model counts as "high-risk AI" under the EU AI Act. Three regulatory regimes, one deployment, and none of them were written with each other in mind.

This is the actual state of AI governance in energy today: overlapping rulebooks that were not designed to talk to each other, applied to infrastructure where failure means blackouts, not just bad customer service.

The collision, concretely

Picture the transformer-failure model again. Before go-live, the utility has to answer questions from at least three directions:

transformer
A 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 →

Grid reliability regulators ask: does this model touch systems that control or monitor the bulk power system? If yes, NERC CIP standards (CIP-005 for electronic security perimeters, CIP-010 for configuration management) apply. Any new software touching a BES Cyber Asset typically needs a documented change management process and security testing before deployment, not after.

AI-specific regulators ask: does this system make or materially influence decisions about critical infrastructure operation? Under the EU AI Act, AI systems used as safety components in the management of critical infrastructure (energy, water, gas) are explicitly listed as "high-risk" (Annex III). High-risk status triggers requirements: risk management systems, data governancedata governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.Voir la définition complète → documentation, human oversight mechanisms, and conformity assessments before market placement.

National grid codes and market operators ask: does this change how the asset behaves in ways that affect grid stability, dispatch, or market bidding? In the US, regional transmission organizations like PJM or ERCOT have interconnection and operating procedures that were not written with adaptive, self-updating software in mind at all.

None of these three regimes reference the others. A model can be CIP-compliant and still fail an AI Act conformity assessment. It can pass an AI Act risk assessment and still violate a NERC change management window. Compliance teams that treat these as one checklist get it wrong.

Why "high-risk AI" hits energy especially hard

The EU AI Act sorts AI systems into risk tiers: unacceptable (banned), high-risk (heavily regulated), limited risk (transparency duties), and minimal risk (mostly unregulated). Energy infrastructure sits disproportionately in the high-risk bucket because the Act's Annex III explicitly names AI used in the operation of critical infrastructure.

That matters for a wide range of ordinary utility use cases, not just exotic ones:

  • Predictive maintenance models that decide equipment inspection priority
  • Load forecasting models that feed into dispatch decisions
  • AI-based protection relays or fault-detection systems
  • Demand response algorithms that automatically curtail customer load

If an AI system's output materially shapes an operational decision on the grid, it is likely to be treated as high-risk. That triggers obligations before deployment, not just monitoring afterward: a risk management system spanning the model's lifecycle, technical documentation, logging capable of traceability, and human oversight designed so a qualified operator can intervene or override.

The NERC CIP layer: security first, AI second

NERC CIP predates modern AI by two decades and was built around a different threat model: protecting the grid from cyberattacks and unauthorized access. It does not mention machine learning. But it still governs almost everything an AI system touches if that system sits near BES Cyber Assets.

Three CIP requirements bite hardest for AI projects:

1. CIP-005 (Electronic Security Perimeters): any AI system pulling data from or sending commands to protected grid systems needs to cross a defined, monitored boundary. Cloud-based AI training pipelines often violate this by default if not architected carefully.

2. CIP-010 (Configuration Change Management): deploying a new or updated model onto in-scope systems is a "change" that needs to be documented, tested, and authorized, similarly to a firmware update.

3. CIP-004 (Personnel and Training): anyone with access to train, tune, or operate the AI system on in-scope assets needs background checks and role-based access training.

Utilities that build AI in an innovation lab, disconnected from CIP-scoped environments, often discover late that production deployment requires re-architecting the whole data pipelinedata pipelineETL (Extract, Transform, Load) is a data integration process that pulls data from sources, reshapes it into a consistent format, and writes it into a target system.Voir la définition complète → to satisfy electronic security perimeter rules. This is one of the most common causes of AI project delay in the sector, according to compliance practitioners speaking at NERC's own Grid Security Conference proceedings.

Model risk: what can actually go wrong

Beyond formal compliance, three risk categories dominate energy AI deployments:

Data drift and silent failure. A load forecasting model trained on five years of historical weather and demand data can degrade quietly as consumption patterns shift (electrification of heating, EV charging growth). Unlike a website recommendation engine, a bad forecast here can cascade into under-procurement of generation capacity.

Opacity in high-stakes decisions. Deep learning models used for fault prediction or dynamic line rating often cannot fully explain a specific output. Regulators and grid operators increasingly require some form of explainability, not full mathematical transparency, but enough that a human operator understands why the model flagged a 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 → as high-risk.

Automation bias. Operators trained to trust a model's outputs may stop applying independent judgment, especially under time pressure during a grid event. This is precisely why human oversight is a formal requirement, not a nice-to-have, in both the EU AI Act's high-risk provisions and most utility internal risk frameworks.

A simplified way engineering teams frame acceptable model risk before go-live:

if model_confidence < threshold or data_drift_detected:
    flag_for_human_review()
    do_not_auto_execute()
else:
    proceed_with_logged_justification()

Simple in code, hard in practice: setting the right threshold, defining drift, and making sure "flag for human review" actually reaches someone with authority to act, especially at 3am during a storm event.

Vérification des acquis

1. Why does a single AI model deployed by a transmission operator potentially need to satisfy NERC CIP, the EU AI Act, and national grid codes simultaneously?

2. What is the key trigger that determines whether NERC CIP standards like CIP-005 and CIP-010 apply to a new AI model in a utility's operations?

3. Under the EU AI Act's Annex III framework, why would a transformer-failure prediction model used in grid operations likely be classified as 'high-risk'?

CHOIX MULTIPLES

4. Select ALL correct answers about what distinguishes energy-sector AI governance from AI governance in less safety-critical industries.

Sélectionnez toutes les réponses correctes.

CHOIX MULTIPLES

5. Select ALL correct answers about the type of requirements that 'high-risk' classification under the EU AI Act typically triggers for a system.

Sélectionnez toutes les réponses correctes.

What compliance actually requires before go-live

Strip away the acronyms and the practical pre-deployment checklist looks like this:

  • Scope determination: is this system touching BES Cyber Assets (CIP applies) and/or acting as a safety component for critical infrastructure (AI Act high-risk applies)? Get legal and OT (operational technology) engineering to agree on scope jointly, not separately.
  • Documented risk management system: covering data provenancedata provenanceData lineage maps how data moves and transforms across systems, from origin to consumption, showing where it came from, what changed it, and where it goes.Voir la définition complète →, testing methodology, and known limitations, maintained across the model's life, not just at launch.
  • Human oversight design: a named role, with defined authority, who can override or halt the AI output, and who is trained to do so.
  • Change management record: for CIP-scoped systems, a change ticket showing testing, authorization, and rollback plan.
  • Logging and traceability: outputs must be reconstructable after the fact, both for CIP audits and for AI Act conformity evidence.
  • Cybersecurity boundary review: confirm the AI pipelinepipelineAll active sales opportunities across the stages of the sales process, together with their combined potential value and probability of closing.Voir la définition complète → (training data ingestion, model serving, monitoring) does not create a new, unmonitored path across the electronic security perimeter.

None of this is exotic. It is closer to the discipline utilities already apply to SCADA (Supervisory Control and Data Acquisition) system upgrades, extended to cover a new kind of software that learns and drifts rather than just executes fixed logic.

🎬 [VIDEO: "How the EU AI Act Classifies Risk" — youtube.com — search for European Commission or Reuters explainer walking through the AI Act's risk tiers and why critical infrastructure is treated as high-risk]

Key Takeaways

  • Energy AI deployments sit at the intersection of at least three regulatory regimes (grid reliability standards like NERC CIP, national grid codes, and AI-specific rules like the EU AI Act), and none were designed to reference each other.
  • The EU AI Act classifies most AI used to operate or safeguard critical infrastructure as "high-risk," triggering mandatory risk management, documentation, and human oversight requirements before deployment.
  • NERC CIP standards (CIP-005, CIP-010, CIP-004) treat AI systems touching Bulk Electric System assets like any other change to protected infrastructure: documented, tested, and access-controlled.
  • The core model risks in this sector are data drift, decision opacity, and automation bias, each of which needs a specific control, not just a general compliance statement.
  • Before go-live, utilities need joint sign-off from legal, OT engineering, and cybersecurity teams confirming scope, oversight design, and traceability, treating AI governance as an extension of existing grid security discipline, not a separate track.

Suivant

When the model is wrong and the lights matter