Machine learning already touches most of the energy value chain: artificial intelligence analyzes the massive volumes of consumption, generation, and sensor data that utilities and industrial energy users collect through IoT devices. Turning that raw signal into a decision — a maintenance ticket, a price, a dispatch instruction — still requires collecting unstructured data, structuring it, storing it, and only then applying models to find the correlations that matter. That pipeline is why applying machine learning in the energy industry takes a genuine engineering program to get right.
What’s changed since this pipeline became standard practice is the demand side of the equation.
The story below covers both halves: how utilities and energy companies use ML on their existing operations, and how rapid growth in AI-related data-center electricity demand is becoming a major factor in utility planning.
KEY TAKEAWAYS
Each use case below is described in terms of what it does and why it matters. Model architectures, benchmarks, and technique-level detail — which vary by deployment and aren’t tied to any single use case — are consolidated in their own subsection further down.
Raw electricity-consumption data rarely shows where power is going, which makes a failing or misconfigured piece of equipment hard to spot before it causes an outage — or, in the worst case, a fire. ML models can classify a facility type (a supermarket, a school), learn its normal consumption pattern, and flag deviations in real time, so operators can act before a small anomaly becomes a costly one.
This is the highest-volume application of ML in the sector: predicting how much energy will be consumed or generated over a given horizon, from the next few hours to several days out. Utilities and facility managers use these forecasts to plan energy-saving policies and size storage; manufacturers use them to schedule production around cheaper or cleaner power windows.
Pricing models forecast demand and recommend prices to help energy companies meet target margins. Compared with expert-based pricing, they can process far larger datasets, surface non-linear supply-demand correlations a human analyst would miss, and produce a transparent, auditable pricing trail — freeing pricing managers to focus on exceptions rather than routine adjustments.
ML-driven recommendation engines support pricing, production, and sales decisions by continuously modeling changing customer needs, giving commercial teams a quantitative reference point rather than intuition alone.
Algorithms that select the optimal contracted capacity level help industrial energy buyers avoid both over-provisioning (paying for capacity they don’t use) and under-provisioning (triggering penalty charges), minimizing total energy cost.
Disaggregation models separate the consumption signature of individual appliances or receivers from an aggregate energy-use signal, giving facility managers appliance-level visibility without appliance-level metering — the basis for more targeted efficiency programs.
A virtual power plant (VPP) aggregates distributed energy resources — home batteries, EVs, smart thermostats, rooftop solar, commercial loads — into a single, dispatchable resource that a utility can call on like a power plant, without building new generation.
AI-driven DER orchestration platforms make this possible at scale: they forecast each device’s available flexibility, decide which to dispatch, and verify performance after the fact.
AI-driven DER orchestration platforms that do this today include Uplight (which includes the former AutoGrid) and Utopus Insights, both of which forecast device-level flexibility and manage large portfolios of orchestrated capacity for utility clients.
Utilities use ML to flag developing equipment problems — transformer faults, cable insulation breakdown, wildfire ignition risk — before they cause an outage or a safety incident. What follows are results reported directly by named organizations, treated as company-reported outcomes rather than independently audited findings, and kept separate by system type (wildfire/safety monitoring vs. asset predictive maintenance vs. outage-prediction pilots):
Reported results: wildfire monitoring, predictive maintenance, and outage prediction
| Organization | System type | Reported outcome (as stated by the organization) |
|---|---|---|
| PG&E | Wildfire safety monitoring — Continuous Monitoring Center combining wildfire cameras, early fault detection sensors, and smart-meter data | PG&E said its Continuous Monitoring Center helped intercept 17 potential ignitions in 2025, avoid 12 million customer outage minutes, reduce emergency response time by 2,620 hours, and save about $6 million in operating costs. (PG&E Corporation) |
| Duke Energy | Asset predictive maintenance — sensor-based monitoring and diagnostics on generating equipment | In one published case, Duke Energy’s Monitoring & Diagnostics team reported that an identified issue could have resulted in up to $34 million in repair and outage costs if left undetected — a single avoided-cost event, not a recurring annual saving. (AVEVA) |
| SDG&E (with Itron/Toumetis) | Outage-prevention pilot — Cascadence ML platform fusing smart-meter, substation, and relay data across 800+ distribution circuits | Deployed to support earlier fault detection and improve reliability metrics; the deployment has not yet published measured post-deployment SAIFI/SAIDI results. (Barchart) |
| Eversource Energy (proof of concept, with EY) | Outage-prediction proof of concept using existing utility data | Eversource and EY reported that the outage-prediction proof of concept helped avoid approximately 40,000 customer outages over two months by helping teams prioritize preventive field interventions — a labeled proof-of-concept result, not an independently audited, long-term production outcome. (EY) |
Note: These are predictive/decision-support applications, they flag risk and prioritize inspection, but a human still decides and acts. That’s a different category from closed-loop control systems that act automatically, and from safety-critical functions, a distinction that matters both operationally and, as covered later, under the EU AI Act.
Illegal meter tapping and billing fraud (“non-technical losses”) cost utilities billions annually. ML classifiers flag anomalous consumption patterns for inspection. Performance in production depends heavily on data quality, class imbalance, false-positive costs, adversarial behavior, and inspection workflows — see the model-types subsection below for the specific model families and a benchmark result.
A related grid-optimization use case: ML models continuously adjust voltage and reactive power settings across the distribution network to reduce technical line losses and hold voltage within tolerance as solar and EV load fluctuate.
Generative AI can draft and summarize customer communications — account histories, billing questions, service requests — cutting the time staff spend on routine responses so they can focus on complex cases. Agentic AI extends this to the field workforce: AI-based scheduling and routing tools can plan technicians’ daily jobs automatically, adjusting in real time as jobs are added or completed.
Example: Octopus Energy’s Kraken platform does both: its “Magic Ink” tool drafts customer responses, and its AI-based routing schedules field engineers’ jobs. techUK reported (2024) that about a third of Magic Ink’s messages needed no edits, with roughly 35% of customer emails written using it. (techUK) A separate Mapbox case study reported that AI routing raised completed jobs per field engineer from 3 to 8 per day, a result specific to that deployment. (Mapbox)
Machine learning also supports sizing energy storage, scaling EV charging infrastructure, calibrating photovoltaic (PV) output, selecting optimal distribution-system-operator tariffs, and correlating power-quality parameters with equipment failures and customer productivity.
Three of the twelve use cases above have specific, sourceable technical detail worth separating out — named model architectures, published benchmarks, or documented sensor techniques.
The other nine use cases do not have dedicated subsections for specific reasons—not because they were overlooked:
Below, each subsection is named after the use case it extends:
Energy forecasting uses a range of model families: gradient-boosted trees are common for structured short-term load and price forecasts; recurrent and convolutional-recurrent models are used for sequential renewable-generation data; and transformer-based weather and time-series models are increasingly used for longer-horizon or high-dimensional forecasting.
The best choice depends on data quality, forecast horizon, geography, and operational requirements; there is no single “standard” model.
| Model type | Typical use | What it’s good at |
|---|---|---|
| Gradient-boosted trees (XGBoost, LightGBM) | Short-term load forecasting, price forecasting | Fast training, strong performance on tabular data with weather/calendar features |
| LSTM / GRU networks | Wind and solar output forecasting, sequential consumption patterns | Capturing long time-series dependencies; commonly hybridized with CNNs for spatial patterns |
| Transformer-based models | Multi-day weather-driven generation forecasts | Used for longer-horizon or high-dimensional forecasting, as in Google’s WeatherNext 2 and GenCast |
Example: Google DeepMind reported that a neural-network system trained on weather forecasts and historical turbine data across 700 MW of U.S. wind capacity could predict generation up to 36 hours ahead. The forecasts enabled day-ahead delivery commitments, which Google said increased the value of the wind energy by about 20%. (Google DeepMind)
The named deployments above rely on a handful of specific sensing and modeling techniques:
| Technique | What it detects |
|---|---|
| Dissolved gas analysis (DGA) | ML models trained on transformer oil gas concentrations flag insulation degradation before failure |
| Partial-discharge monitoring | Pattern-recognition models detect the electrical signatures of insulation breakdown in cables and switchgear |
| LiDAR inspection | Used to model vegetation encroachment risk near transmission lines |
| Computer-vision drone inspection | Automated defect detection on towers, insulators, and turbine blades, replacing manual visual inspection |
Detecting illegal meter tapping and billing fraud from consumption data draws on a small set of established classifier families:
| Model type | Note |
|---|---|
| Random forest | Common baseline classifier for structured consumption features |
| XGBoost | Frequently used for tabular consumption data with engineered features |
| SVM | Used in earlier non-technical-loss research; still a common comparison baseline |
| LSTM-based classifiers | Capture sequential consumption patterns; the basis for the ETD-LSTM benchmark below |
In a published smart-meter benchmark, an ETD-LSTM model reported 93.6% classification accuracy — a research-conditions figure, not a utility-production outcome. (Nature Scientific Reports)
ML signals still need to reach the people who act on them, and in energy that reporting layer has a specific technical backbone: process historians and utility data standards, not generic dashboards.
Time-series “historian” platforms—most notably AVEVA PI System (formerly OSIsoft PI)—are widely used to capture and store years of operational data at scale. AVEVA says the platform is used by more than 1,000 power and utilities organizations worldwide, as well as companies in oil and gas and other process industries.
AVEVA’s case studies illustrate the potential value. DCP Midstream reported $25 million in savings in one fiscal year after using PI System data to improve plant efficiency. UC Davis reported a 46% reduction in energy-use intensity since 2009 and $15 million in savings through PI-based monitoring. These are vendor-reported case studies, not independently audited results.
Production and outage analysis in practice means integrating a historian or SCADA data feed with a utility’s outage management system (OMS) and GIS — the same distribution fault-anticipation and grid-analytics platforms described in the predictive-maintenance section above (PG&E, SDG&E/Itron/Toumetis) sit on top of this layer.
Real-time monitoring pairs a historian’s live data feed with alerting and ML-based anomaly detection so unusual conditions surface to operators as they happen, rather than being discovered in a post-incident review — the same principle behind the wildfire and fault-detection systems described earlier in this article.
Generic claims about “improved data quality” don’t say much on their own. In the energy sector, data governance has a concrete technical anchor: the IEC Common Information Model (CIM) – standardized under IEC 61970 (transmission/EMS) and IEC 61968 (distribution) – defines a shared vocabulary for grid topology, assets, and equipment so that applications built by different vendors (a historian, an EMS, an asset-management system) can exchange data without custom point-to-point integration for every pair of systems.
Master data management (MDM) in this context means maintaining a single, CIM-aligned model of a utility’s key entities assets, customers, vendors, so that a transformer or a customer record means the same thing across the outage-management system, the billing system, and the ML models built on top of them.
Without that alignment, the same asset can show up as a different ID in three different systems, which quietly breaks any model trained across them.
Everything above covers what machine learning actually does in the energy sector. The rest of this article covers the business and regulatory context around adopting it: how vendors compare, what the market is worth, what compliance requires, and what tends to slow rollouts down.
Energy companies buying rather than building ML capability typically evaluate a small set of industrial platforms. The following distinctions are illustrative and should be validated against each vendor’s current portfolio, regional availability, integration requirements, and target operating model:
| Vendor | Platform | Core strength | Best fit |
|---|---|---|---|
| GE Vernova | GridOS®, Digital Twin (APM) | Deep integration across physical turbines/generation equipment and grid software | Utilities with heavy GE-installed generation and grid hardware |
| Siemens Energy | Spectrum Power, SICAM, and related Siemens digital-industries software | Strong hardware plus industrial-automation heritage | Large, diversified generation-and-T&D operators |
| Schneider Electric | EcoStruxure | Electrification and software leadership, DER/demand-side management | Utilities prioritizing distributed energy and demand-side management |
| Oracle | Oracle Utilities / Cloud ERP integration | Enterprise-system integration (billing, asset management, ERP) rather than OT-layer AI | Utilities consolidating enterprise data before scaling AI use cases |
Note on the Schneider Electric row: Schneider previously owned the DER/VPP platform AutoGrid, sold to Uplight in a deal announced December 2023 and closed February 2024; Uplight reported the combined organization then managed over 8,300 MW of flexible resources. Uplight has separately estimated that scaling VPPs could help meet a material share of U.S. peak demand and reduce grid costs — a vendor projection, not an independently validated sector-wide outcome.
Commercial estimates of the AI-in-energy market vary sharply because firms use different definitions — for example, whether they include grid software, industrial analytics, customer-service AI, energy-management systems, or hardware-enabled solutions. These figures should be used as directional market signals rather than interchangeable measurements:
Three types of evidence answer different questions:
The gap between benchmark results and real-world outcomes usually comes down to three things:
This is also consistent with EY‘s reporting on utility AI adoption: AI usage appears to be growing faster than staff confidence that it has delivered on expectations. Check EY’s original publication for the survey sample, geography, question wording, and any specific percentages before citing them.
The fix is to measure your own deployment against your own documented baseline, not a vendor’s headline number. A workable set of metrics, and what to actually track for each:
| Metric | What to measure |
|---|---|
| Unplanned outage minutes avoided | Compare the same season/weather conditions pre- and post-deployment — raw before/after totals are misleading if one period had milder weather |
| Maintenance cost per asset | Track avoided-cost events individually (like Duke Energy’s single $34M case above) rather than annualizing one event into a recurring saving |
| Forecast error (e.g., MAPE) | Benchmark against your previous forecasting method on the same historical period, not against a published research figure |
| Cost per customer interaction | Separate cases the model handled with no human edit from cases where staff had to substantially rewrite the output — the two have very different cost profiles |
| False-positive / false-negative rates | Track both, not just accuracy — a high-accuracy model can still generate more false alerts than your team can act on |
| Adoption rate | The share of model recommendations actually reviewed, accepted, and acted on — a model nobody acts on has zero ROI regardless of its accuracy |
Under the EU AI Act, Annex III, point 2 covers AI systems intended to be used as safety components in the management or operation of critical infrastructure, including the supply of electricity, gas, heating, and water.
The deciding factor is intended purpose, not the technology itself: closed-loop or safety-critical operational control is more likely to fall within scope than general analytics, reporting, maintenance prioritization, or advisory load forecasting.
In practice, that means most of the predictive/decision-support use cases in Part 1 (forecasting, predictive maintenance, fraud detection) sit outside high-risk scope, while automated fault-isolation, dispatch, or protection systems that act without human sign-off are the ones to review closely.
| Obligation | What it means in practice |
|---|---|
| Risk-management system | Documented, ongoing process for identifying and mitigating the system’s risks |
| Data governance | Controls over training/input data quality, provenance, and relevance |
| Technical documentation and logging | Records sufficient to reconstruct how the system reached a decision |
| Human oversight | A defined mechanism for a person to review, override, or stop the system |
| Accuracy, robustness, and cybersecurity testing | Evidence the system performs as intended and resists tampering (Articles 9–15) |
| Deployer obligations | Separate duties for the organization using the system, not just the one that built it (Article 26) |
Non-compliance penalties can reach €15 million or 3% of global annual turnover (Baker Botts)
The AI Omnibus, which entered into force on July 27, 2026, pushed the application date for Annex III high-risk rules to December 2, 2027. That’s more runway, but the obligations above still apply once the date arrives.
An energy organization’s obligations depend on whether it develops, substantially modifies, deploys, or operates a given AI system. These roles — provider, deployer, system integrator, operator — can fall on different parties across the same system: the model developer, the integrator who embeds it into grid software, and the utility that runs it may each carry different duties.
There’s no single answer that applies to “energy companies” as a category; it has to be worked out system by system.
More sensors and more automation mean more attack surface. AI cuts both ways here:
ML models learn the “normal” behavior of OT/IT network traffic and flag deviations — including insider threats, false data injection, and denial-of-service patterns — that a human analyst would otherwise have to catch manually.
Example: One research study reported 99.8% binary-classification accuracy on its test dataset using an LSTM and random-forest framework. This result should not be treated as evidence of production security effectiveness without false-positive, false-negative, dataset, and external-validation context, and it should not be read as implying such models will reliably detect sophisticated operational-technology attacks in real utility environments. (Nature Scientific Reports)
AI applied to satellite imagery can pinpoint pipeline and facility gas leaks that would otherwise go undetected until a routine inspection or a reported incident.
Example: Companies like Kayrros apply AI to satellite imagery (Sentinel, and previously data destined for Google’s MethaneSAT) to pinpoint leaks in near real time; Kayrros has identified roughly 10,000 leak events globally since 2019, per its own reporting. (CleanTechnica; energynews)
In tightly controlled environments, security orchestration systems may automate predefined containment actions, such as isolating a network segment, once an intrusion is detected.
Example: Utilities should implement such actions with rigorous safety, human-oversight, and operational-technology security controls rather than treating containment as fully autonomous. (Xylem)
The trade-off utilities face is that the same automation that improves detection speed also becomes a new dependency to secure — which is part of why grid AI systems sit inside the EU AI Act’s high-risk category above.
Despite the market growth, most utilities are still early in deployment. NewGen Strategies describes this as a “96-to-26 paradox.” (NewGen Strategies) The recurring barriers, in rough order of how often they’re cited:
Utilities that are ahead tend to address these in sequence: unify data infrastructure once rather than per use case, run a small number of production deployments to build organizational trust before scaling, and bring compliance and operations teams into AI projects from day one rather than after a pilot succeeds.
The rest of this article covers ML applied to the energy sector. This section is different: it’s about how AI’s own electricity use is changing the inputs those ML systems have to work with — specifically, the forecasting and grid-planning use cases from Part 1.
The scale of the shift. Deloitte projects U.S. AI-specific data-center power demand could rise from 4 GW in 2024 to 123 GW in 2035 — a scenario, not a settled figure. (Deloitte) The IEA separately projects global data-center electricity use reaching about 945 TWh by 2030 in its base case. (IEA) Whatever the exact number, utility load-growth forecasts — the direct output of the forecasting models covered earlier — are being revised upward across the board.
Three of the use cases from Part 1 are directly affected:
One more ML-specific data point worth flagging: AI is also being used to speed up nuclear licensing itself, a knock-on effect of rising demand pushing utilities toward SMRs and reactor restarts. Idaho National Laboratory worked with Microsoft on an Azure AI system to help generate the engineering and safety-analysis reports that go into NRC license applications. (Neutron Bytes)
BUILD YOUR ENERGY ML STACK ON A GOVERNED DATA FOUNDATION
Forecasting demand, running predictive maintenance, or orchestrating a VPP is the easy part to prototype. Scaling it across SCADA, smart-meter, and enterprise data , with the access controls, consistent asset definitions, and traceable model decisions that EU AI Act compliance now expects, is where most pilots stall.
Addepto helps energy companies build the data engineering foundation for production ML: governed data platforms, reliable forecasting and maintenance pipelines, and secure integration patterns across OT and IT systems.
Evaluating ML for your energy operations? Talk to our data engineering and AI integration team about designing an architecture that moves beyond a pilot without creating uncontrolled data sprawl or compliance risk.
Deloitte projects that AI could account for about 70% of the 176 GW of U.S. data-center power demand it expects by 2035 — a projection, not a settled figure. Utilities are responding with cluster-study interconnection reform, revised capital plans, and demand-response contracts that treat hyperscaler load as partly flexible.
Some hyperscalers now treat their data-center load as partly flexible rather than fixed. Google has signed demand-response agreements covering 1 GW of data-center load with five U.S. utilities, letting utilities call on that flexibility during periods of grid stress.
Gradient-boosted trees are common for structured short-term load and price forecasts; recurrent and convolutional-recurrent (LSTM/GRU) models are used for sequential renewable-generation data; transformer-based models are increasingly used for longer-horizon or high-dimensional forecasting. The best choice depends on data quality, forecast horizon, geography, and operational requirements — there is no single default.
Google DeepMind reported that a neural-network system trained on weather forecasts and historical turbine data across 700 MW of U.S. wind capacity could predict generation up to 36 hours ahead, enabling day-ahead delivery commitments. Google said this increased the value of the wind energy by about 20%.
A VPP aggregates distributed resources — batteries, EVs, thermostats, solar — into one dispatchable unit. Uplight, which acquired AutoGrid from Schneider Electric in a deal announced in December 2023 and closed in February 2024, reported managing more than 8,300 MW of flexible resources for clients at the time of the acquisition.
Dissolved gas analysis flags transformer insulation degradation; partial-discharge monitoring detects cable and switchgear breakdown signatures; LiDAR assesses vegetation risk near transmission lines; computer-vision drone inspection automates defect detection on towers and turbine blades. These are predictive/decision-support tools — a person still reviews and acts on the output.
PG&E said its Continuous Monitoring Center helped intercept 17 potential ignitions in 2025, avoid 12 million customer outage minutes, and save about $6 million in operating costs. Duke Energy’s Monitoring & Diagnostics team reported that one identified equipment issue could have resulted in up to $34 million in repair and outage costs if left undetected — a single avoided-cost event, not a recurring annual saving.
Annex III, point 2 covers AI systems intended as safety components in managing critical infrastructure, including electricity supply. Whether a specific system is high-risk depends on its intended purpose — closed-loop or safety-critical control is more likely to qualify than general analytics or advisory forecasting. The application date for these rules was moved from August 2026 to December 2, 2027.
More than 2.2 terawatts of generation and storage sit in U.S. interconnection queues. FERC Order No. 2023 requires a shift toward cluster-study processing, and grid-planning software can help transmission planners evaluate more scenarios faster — but it does not remove the permitting, construction, and regulatory constraints that drive queue delays.
Rising data-center demand is one factor pushing utilities toward SMRs and reactor restarts, alongside broader energy-security and reliability drivers. AI’s more direct role is in speeding reactor licensing itself: Idaho National Laboratory worked with Microsoft on an Azure AI system to help generate engineering and safety-analysis reports for NRC license applications.
Octopus Energy’s Kraken platform uses generative AI (“Magic Ink”) to draft customer responses; techUK reported in 2024 that about a third of generated messages needed no or minimal edits and roughly 35% of customer emails were written with its assistance. A separate Mapbox case study reported AI-based routing raised completed jobs per field engineer from 3 to 8 per day for Octopus’s field team specifically.
More sensors and automation mean more attack surface for false-data-injection and malware threats. One research study reported 99.8% binary-classification accuracy for an LSTM/random-forest anomaly-detection framework on its test dataset — a research result that should not be read as evidence of production security effectiveness. Satellite-AI tools like Kayrros separately detect methane leaks across pipeline networks.
Estimates vary widely by market definition: Grand View Research puts the market at $5.1B in 2025; Fortune Business Insights, using a broader definition, puts it at $42.26B in 2026. Both point to strong growth, with machine learning and predictive analytics commonly identified as leading segments — but the figures aren’t directly comparable.
GE Vernova integrates physical generation equipment with grid software (GridOS). Siemens Energy combines hardware with an industrial-automation software heritage. Schneider Electric focuses on electrification and demand-side management (it previously owned AutoGrid, since sold to Uplight). Oracle focuses on enterprise-system integration — billing, asset management, ERP — rather than OT-layer AI. These are illustrative distinctions to validate against each vendor’s current offering.
Reported ROI varies substantially by asset type, data maturity, and process redesign, so sector-wide benchmarks should be treated cautiously. Track outage minutes avoided, maintenance cost per asset, forecast error versus your prior method, cost per customer interaction, false-positive/negative rates, and the share of recommendations actually acted on — measured against your own documented baseline.
Deloitte’s 2026 survey found 53% cite data silos, 51% cite legacy systems, 38% cite slow operational adoption, and 36% cite regulatory uncertainty. Eurelectric reports a 34% AI/data-science talent gap in Europe’s power sector. Utilities that are further along tend to unify data infrastructure once rather than per use case and involve compliance teams from the start of AI projects.
Category:
Discover how AI turns CAD files, ERP data, and planning exports into structured knowledge graphs-ready for queries in engineering and digital twin operations.