Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Utility Management edition of October 29, 2026

Government evaluationCautionaryRecent

Attorney General Tong, Consumer Counsel Coleman Petition PURA for Probe of Artificial Intelligence Use by Public Utilities

Connecticut Office of the Attorney General and Office of Consumer Counsel · State utility regulation (electric, gas, water) · Connecticut, United States

Publisher
Connecticut Office of the Attorney General
Original publication
13 Oct 2026 (press release)
Source retrieved
2026-10-30
Event date
2026-10-13
Read original source

What happened

Connecticut's Attorney General and Consumer Counsel petitioned PURA to open a comprehensive review of utility AI use, asking that utilities report all AI systems, their objectives, level of human oversight and governing policies, and that PURA review data-security and cybersecurity protections and breaches. Requested scope covers storm response, customer systems, asset management, load and water-demand forecasting, procurement, grid/plant/water treatment operations, third-party vendors and AMI. The petitioners cite risks including hallucination and bias, and reports that conventional weather models outperformed AI models for a February nor'easter.

Why it matters

Signals that state regulators and consumer advocates may require AI inventories and human-oversight disclosures from electric and water utilities, following New York's September 2026 order already in the SLED archive.

Evidence and measured results

Advocacy petition and press release; it states concerns and requested scope but presents no new measured findings. Whether PURA opens the docket was not established at retrieval.

Limitations and uncertainty

Petition only; PURA action and timing unknown. Claims about AI forecast performance are cited by the petitioners, not independently evidenced in the release. Named utilities are investor-owned (Avangrid, Eversource), though water utilities are in requested scope. Classed government-evaluation as the closest schema class; it contains no evaluative findings.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Utilities may soon need to disclose all AI use, oversight and safeguards to regulators but lack a complete inventory.
Stakeholders
  • Regulatory affairs director
  • CIO
  • CISO
  • General counsel
  • Operations leadership
Discovery questions
  • Could you list every AI system in operations, customer service and vendor platforms today?
  • How do you document human oversight for AI-informed decisions?
  • Which vendor contracts disclose embedded AI features?
Value hypothesis
A prepared inventory and policy baseline may reduce scramble and disclosure risk if regulators open an inquiry; it does not guarantee regulatory approval.
Potential engagement
A time-boxed AI inventory and governance gap assessment against NIST AI RMF categories.
Unsupported claims
  • That PURA has opened a docket
  • Specific future compliance requirements
  • That AI forecasts are generally worse than conventional models

Pre-sales engineering

Role takeaway
Fit
Fits utilities with mixed IT/OT estates and vendor platforms carrying embedded AI.
Architecture and integration
Inventory spans SCADA/OT analytics, AMI head-end and MDM analytics, CIS/billing, outage management and enterprise copilots.
Prerequisites
  • Application and asset inventories
  • Vendor contract access
  • OT network documentation
Constraints
  • Connecticut-specific; outcome of petition unknown
  • Sensitive OT details may need confidential filing treatment
Security
Inventory must classify data sensitivity and avoid publishing exploitable OT architecture details.
Proof of value
  • Sampled inventory of two domains with oversight tags
  • Gap map against one governance framework

Delivery

Role takeaway
Work
Build an AI system register, oversight classification, and policy alignment package.
Dependencies
  • Executive sponsor
  • Vendor cooperation
  • Legal review
Ownership
Regulatory affairs lead with CIO/CISO.
Skills and adoption
Staff need shared AI definitions and a lightweight intake process for new tools.
Governance checkpoints
  • Legal review before filing
  • CISO review of disclosure content
  • Annual register refresh
Acceptance criteria
  • Proposed: register covers all named scope areas
  • Proposed: each entry has owner, purpose, oversight level and data class
Risks
  • Missed embedded vendor AI
  • Over-disclosure of OT details
  • Definitions drift across departments

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Utilities would need an inventory of AI systems across OT, AMI, customer systems and vendor platforms, including embedded vendor AI.

Governance

Who approves, reviews and stays accountable for outcomes?

Expect regulator requests for AI use-case inventories, oversight levels, and policies benchmarked against industry standards; third-party vendor AI is explicitly in scope.

Security and privacy

What data, permissions and controls need testing?

Requests review of AI and non-AI cybersecurity protections and breaches, and protection of sensitive customer information, including AMI data.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Requires staff time across departments; human-oversight documentation may surface training needs.

Procurement

What should contracts, pricing and exit terms secure?

Third-party vendors are named in scope; contracts may need AI disclosure and audit clauses.

Operating model

Which teams own the service once it runs?

Moves AI governance from ad hoc IT policy toward a regulator-facing register maintained by regulatory affairs.

Publication history

  1. 2026-10-29Utility Management · Issue 0110 resources
Read preserved resource versions (JSON)

Stable resource ID: ct-ag-occ-pura-ai-utility-probe-petition-2026