No. 89 / 339
What changes for utilities with AI?
The shift
Synthesizing sensor, SCADA, and smart-meter data into a usable read on grid or network state — and drafting the regulatory filings, outage reports, and customer responses built on top of it — goes from scarce analyst and engineer time to abundant, fast, and near-free. Keeping the power on, the water clean, and the rate case honest stays exactly as scarce as before, because none of that runs on tokens.
The axioms
- Grid and network operation requires humans in the loop reading dashboards and calling judgment on anomalies — synthesis of high-volume telemetry is scarce, specialist time.
- Load forecasting and demand-response planning depend on scarce analytical capacity to turn weather, usage, and market data into a plan.
- Rate cases, tariff filings, and compliance reports are gated by scarce regulatory-affairs staff who can synthesize evidence into a filing a commission will accept.
- Customer service (billing disputes, outage status, service requests) is gated by scarce call-center and support headcount.
- Asset management — deciding which transformer, pipe, or line segment fails next — rests on scarce engineering judgment applied to inspection and maintenance history.
- The physical acts of generation, transmission, distribution, and repair are scarce: only crews and machines in the field move electrons, gas, and water.
- The regulated monopoly relationship rests on scarce, hard-won trust: a utility commission and public grant a monopoly in exchange for accountability when things go wrong.
- Outage response and restoration require scarce real-time coordination between crews, equipment, and grid state under time pressure.
- Cybersecurity and grid-control integrity depend on scarce specialized expertise defending systems where an error is catastrophic, not recoverable by a retry.
Invalid axioms
- Reading and triaging high-volume telemetry requires a room of analysts. Pattern-matching across SCADA feeds, smart-meter data, and weather feeds to flag anomalies is exactly the synthesis-at-scale AI is now cheap at. The habit-trap: utilities still staff monitoring centers sized for an era when a human had to eyeball every dashboard, rather than for an era where a model pre-triages and a smaller team verifies exceptions.
- Drafting rate-case filings, tariff language, and compliance reports is slow, expensive specialist work. First-draft synthesis of financial, engineering, and legal inputs into filing-ready text is now near-instant. The habit-trap: regulatory-affairs teams are still budgeted and timelined as if the drafting itself, not the strategy and evidence behind it, were the bottleneck.
- Tier-1 customer service (billing questions, outage status, service requests) needs proportional headcount to call volume. This is generic-domain conversation with well-documented account and outage data behind it — squarely in AI's competent-generalist zone. The habit-trap: call centers still scale staffing to forecasted call volume instead of to the shrinking tail of cases that actually need a human.
- Load forecasting and scenario planning require a dedicated modeling team to hand-build and re-run models. Generating and iterating first-draft forecasts, demand-response scenarios, and what-if analyses across weather, price, and usage data is now abundant. The habit-trap: planning cycles are still paced as if building the scenario were the slow part, when the slow part is now deciding which scenario to trust.
Unchanged axioms
- The physical acts of generation, transmission, distribution, and repair are scarce. No model dispatches a bucket truck, replaces a transformer, or clears a downed line. Capital planning and field labor stay the real constraint on service.
- Accountability for keeping the lights, water, and gas on rests on the utility and its licensed engineers, not a model. When a substation fails or water is unsafe, the commission and the public hold the utility answerable — a model can't hold a license or testify under oath at a rate hearing.
- Judgment on novel, high-stakes grid and network events stays human. A cascading failure, an unprecedented storm, a first-of-its-kind cyberattack on control systems — these are exactly the low-pattern, high-stakes situations where confident-but-wrong AI output is most dangerous, and where a real operator's judgment is what prevents blackout-scale failure.
- The regulated-monopoly trust relationship is earned through track record, not generated text. A commission grants and renews a monopoly based on demonstrated reliability and integrity over years — a fast, plausible filing doesn't substitute for that standing, and a filing later found to overstate or misrepresent facts destroys it faster than ever.
- Control-system security is a scarce, adversarial discipline. Defending SCADA and ICS environments against attackers who are also using AI is a live arms race requiring specialized human expertise; a control-system compromise is physical-world damage, not a redo-able mistake.
- Deciding which capital projects to fund — substation upgrades, pipe replacement, grid hardening against climate risk — is a taste and priority call under real financial and political constraints. AI can model options; it can't own the trade-off between rate impact, reliability, and long-term risk.
New axioms
- When anomaly-flagging is cheap and constant, who decides which flagged anomaly is real and who's accountable for the ones missed. Abundant monitoring output creates alert volume that didn't exist before; verification and triage capacity, not detection, becomes the bottleneck, and someone has to own the false-negative that matters.
- When regulatory filings can be drafted in minutes, commissions and intervenors face a volume of AI-assisted filings and comments that outstrips their own review capacity. The scarcity moves from "who can write the filing" to "who can verify what's actually in it" — on both sides of the docket.
- When AI can generate plausible-looking grid or demand forecasts fast, distinguishing a well-grounded forecast from a confidently wrong one becomes the actual planning risk. Utilities that used to trust a forecast because it took a team weeks to build now need a new way to calibrate trust in a forecast that took minutes.
- When customer-facing AI handles routine contacts at scale, the utility needs a new way to catch the rising share of edge cases — safety hazards, medical-necessity service issues, fraud — that get routed like routine tickets but aren't. Speed and volume in the easy cases raise the cost of missing the hard ones.
- Control systems and utility IT increasingly rely on AI-assisted tooling for operations and coding, which widens the attack surface AI-equipped adversaries can also exploit. Utilities now have to defend against attackers with the same synthesis and pattern-matching abundance they themselves adopted.
Where it breaks
Utilities cut monitoring-center and regulatory-drafting headcount because synthesis and first-draft generation got cheap (invalid axiom 1 and 2) right as alert volume and filing volume from AI-assisted actors on both sides explode (new problem 1 and 2). The teams sized down for "less synthesis work" are the same teams now needed to verify a flood of AI-generated anomalies and filings — cutting the wrong side of the ledger leaves nobody watching the exception queue that actually matters.
A second collision: customer service headcount shrinks because routine contact volume got automated (invalid axiom 3), while the edge cases that need a human — safety hazards, fraud, medical-necessity outages — get harder to catch precisely because they now arrive mixed into a much larger AI-handled stream (new problem 4). The safety net thins exactly where it needs to hold.
Related axioms
Other axioms
Cybersecurity
What changes for cybersecurity with AI?
Engineering
Should we still require human review of AI-selected training data before it ships into production?
Media
What changes for journalism with AI?
Legal
Who's liable when in-house counsel signs off on an AI-drafted contract that turns out wrong?
Healthcare
Is the radiologist obsolete now that AI reads scans as well as humans, or did the job just move to accountability?
Engineering
What shifts in accountability when an autonomous agent, not a human, executes the remediation?