Case Study
How Sella Delivers Scalable Credit Risk Explanations with Prometheux
Read More
By Industry / Energy & Utilities

Trusted Agents for
Energy and Utilities

From grid operations and asset maintenance to customers, trading and investment planning, Prometheux runs your knowledge as rules on the data you already have, across GIS, asset, meter, billing, market and operational systems. Teams and their AI agents get the same answer every time, with the rules and source rows behind it. No migration, no new data store.

Proven in production

Why utility decisions stay slow

The Business Is Connected.
Its Data Isn't.

Grid, assets, customers, markets and partners each run on their own systems, and the knowledge that connects them sits with a few experts. Every outage review, investment case, billing query and emissions or regulatory report starts by stitching data together again, by hand.

Today
With Prometheux
Network, asset, customer, market and partner data spread across systems that were never built to talk
One model of your network, assets, customers and contracts, codified once and shared by every team
Data copied into yet another platform before anyone can use it, then kept in sync
Data is processed in place, where it already lives: nothing to copy or migrate
AI pilots give different answers to the same question, so they never reach operations or customers
Agents call deterministic rules over MCP: same question, same answer, ready for real work
Answers a regulator, board or ombudsman can't follow back to the data
Every result comes with the rules and source rows behind it, and replays identically
Modernisation means a multi-year migration before reliability, cost or reporting improve
Start on one use case on today's systems, then reuse the model for the next
AI spend grows with every model call, whatever the question
Rules and graph steps do the reasoning; LLM steps only where language is needed
Use case menu

Where Energy and
Utility Teams Start

Use cases across delivery, assets, customers and markets, and planning, each run as rules on the data you already have. Pick one, prove it on your own data, then reuse the model for the next.

Grid & Network

Keep supply reliable by planning, operating and restoring the network from one picture of how it connects.

01Outage impact by feeder and customer
Which feeders, customers and critical sites does a fault affect, and through which path?Recursion →
02Demand and load forecasting inputs
Python steps find trends and anomalies in meter and network data, and rules tie them to the feeders and substations they load.High-Performance Data Engine →
03Planned outages without surprises
Which overlapping planned outages would leave a critical customer on a single feed or with none at all?Recursion →
04Root cause traced through the network
Which upstream event explains most of the active alarms, walked through the network with every step shown?Graph Analytics without a Graph Database →
05Control-room assistants you can check
Agents answer network questions by calling your outage and connectivity rules over MCP, with the derivation behind each answer.AI Agents →

Assets & Field Operations

Spend maintenance and field effort where reliability and safety depend on it, from one view of every asset.

01Risk-based maintenance priorities
Which assets serve the most customers and critical sites, ranked by centrality and your condition rules, so they're maintained first?Graph Analytics without a Graph Database →
02Early warning from sensor data
Which assets show readings drifting from their own trend, found by a Python step on historian data and joined to the asset record?Cross-Database Processing →
03Field work prioritised by impact
Which open work orders sit on assets that supply critical sites or many customers, so crews know what to tackle first?Recursion →
04Spare parts for at-risk assets
Which flagged assets have no compatible spare in stock, checked across the asset register and inventory systems?Cross-Database Processing →
05Overdue inspections rolled up
Which substations and regions carry the most components past their inspection date, from component to bay to site, raised as work orders when data changes?Agentic Workflows →

Customers & Markets

Bill correctly, serve customers consistently and see commercial exposure across books.

01Billing exceptions before they're sent
Which bills don't match the meter readings, tariff and contract terms they should follow, and where do they differ?Cross-Database Processing →
02Customer 360 across the business
Which accounts across supply, services, B2B and trading are the same customer or counterparty, with the rule behind each link?Entity Resolution →
03Tariff and support eligibility
Which customers qualify for which tariff or support scheme under your current rules, and which rule decided each one?Deterministic AI →
04Customers at risk of leaving
Which customers show the usage, complaint and contract-date signals your retention rules look for, and why each was flagged?Deterministic AI →
05Counterparty exposure across books
What is the total position and contract volume per counterparty across trading, wholesale and retail books, on a schedule or when data changes?Cross-Database Processing →
06Service agents with the reason
Agents explain why a bill came out as it did, with the tariff rule and readings behind it; an LLM step drafts the wording, marked non-deterministic.AI Lineage →

Planning & Reporting

Plan investment and connections, and report figures, from the same model, computed by your definitions and traced to source.

01Investment cases from one network picture
Which reinforcement candidates sit above the most constrained substations and customers, by the planning rules you define?Recursion →
02Connection headroom by your rules
Which substations have room for new renewable, storage or demand connections under your ratings and planning rules, and why?Deterministic AI →
03Emissions and regulatory figures you can defend
Each reported figure is computed by your own definitions and factors, with lineage to the meter, asset and customer records behind it.Data Lineage →
04One set of definitions everywhere
Regulatory, board and investor reports draw on the same versioned definitions, so a figure means the same thing everywhere.Semantic Layer →
05Modernise without a big-bang migration
Move reporting and data workloads across clouds and platforms while the rules keep running where the data lives.Data Modernization →
Where connected data matters

The Questions Other
Tools Can't Answer

Outage

Who Loses Supply

If this substation trips, which feeders, transformers and customers lose supply, which of them are critical sites or priority customers, and through which path? A recursive walk down the network at any depth, counted per asset.

Resilience

Single Points of Failure

Which hospitals, water works and other critical sites are supplied by one path only, so a single open switch or failed transformer cuts them off?

Assets

Hierarchies That Roll Up

Which substations carry the most components past their inspection date, rolled up from component to bay to site to region, with each count traced to the records behind it?

Records

One Asset, Many Records

Which entries in GIS, the asset register and maintenance history are the same physical asset? Every match cites its rule. See entity resolution.

Architecture

One Model Across
Grid and Business

Typical industrial data platforms consolidate OT and IT data into their own store before anyone can use it. Prometheux sits between your grid, asset and customer data and the people, tools and agents that act on it, and runs the knowledge where the data already lives.

Analytics

Control-room dashboards, graph and BI

Integrations

Back into the databases behind GIS, asset, billing and work-order systems

Agents

Utility agents, deterministic answers

Models

Define the ontology, read answers, and power analytics, integrations and agents

Your grid, asset and customer data

Network connectivity, asset registers, operational, meter, billing and customer data, connected in place. Nothing to migrate.

  • Grid, Asset and Customer Operations

    • Outage impact, asset roll-ups, tariff and billing checks and transition reporting on one model
    • Agents call deterministic rules over MCP and API, with the derivation behind every answer
    • Results written back to the databases behind GIS, asset, billing and work-order systems, on a schedule or when data changes
  • The Utility Knowledge Engine

    • One network, asset and customer model across systems, instead of a separate copy per tool
    • Recursion with aggregation and graph algorithms: customers per feeder, critical load per substation, assets per site
    • Same input, same output, with lineage to the rules and source rows
  • Cloud Agnostic

    • Run in your own data centre, any cloud or inside your data platform, under your own controls
    • Scale horizontally on clusters as meter and network data grows, with optional GPU acceleration
    • 1-click deployment anywhere: EKS, AKS, GKE, Databricks Clusters, Snowpark Containers
  • Utility-Data Agnostic

    • Read and write connectivity, asset, meter, billing and operational data in any database, format and schema
    • Connect data lakes, warehouses, object storage, files and APIs across clouds and on-premises
    • No new data store or twin to migrate into and keep in sync
Layer by layer

Same Layers.
Better Built.

Map a typical energy data or grid-twin platform to Prometheux and the difference is where the work happens: in place, in rules you own, with an answer you can check, for the grid and the business around it.

Typical energy data platform
Prometheux
Data: OT and IT data aggregated into the platform's own store
Data: sources read and written in place, across clouds and on-premises; no new store
Model: a contextualised data model or digital twin that describes the network
Model: a network, asset and customer model whose relationships and rules execute
Analytics: ML models and scenario simulation
Analytics: deterministic rules, graph algorithms and Python steps, with lineage on each result
Questions: dependency walks of known depth
Questions: recursion with aggregation at every hop: customers per feeder, critical load per substation, overdue assets per site, connected capacity per region
Reporting: dashboards over consolidated data
Reporting: operational, customer and transition figures computed by versioned rules, each traced to its source rows
AI interface: low-code agents over the platform
AI interface: agents call deterministic rules over MCP and see how each answer was reached
Deployment: the vendor's platform
Deployment: Prometheux cloud, your cloud, your own servers on Docker or Kubernetes, or inside Snowflake and Databricks
Why energy teams choose it

Your Grid.
Your Rules.

Network knowledge sits with a few engineers and inside tools that each cover part of the picture. Prometheux turns that knowledge into readable rules that run on your existing GIS, asset, meter and customer data, so outage reviews, investment cases and regulatory reporting all start from the same, checkable answers.

Owned, Not Vendor-Bound

The model spans GIS, asset, meter and customer systems and stays with you, in rules your engineers can read and version.

Deterministic and Explained

The same network state gives the same answer, with the rules and source rows behind it, which is what an outage review or a regulator asks for.

Built for Grid Scale

Rules run as distributed, parallel jobs, with optional GPU acceleration, on compute you already have. See high-performance engine.

Portable by Design

Run in Prometheux cloud, your cloud, or on your own servers on Docker or Kubernetes, inside your own security boundary. See on-premises.

What this means for you ⟶

Bring one use case

Codify grid knowledge once. Reuse it for outages, assets and reporting. Give agents rules they can be trusted on.

How utilities start

One Use Case.
Then the Next.

01

Connect in Place

Point Prometheux at the data for one network area, one billing process or one report. The data is processed where it lives; nothing is copied.

02

Codify the Knowledge

Your engineers and analysts, our forward deployed engineers and the AI assistant turn network rules, asset hierarchies, tariff logic and reporting definitions into readable rules in days, not months.

03

Run One Use Case

Outage impact, an asset roll-up, a billing check or one transition figure, on live data, for people and agents alike.

04

Expand Across the Business

Each new network area, process or report reuses the rules already written, so the model grows without rebuilding context for every tool.

FAQ

Questions,
Answered

Is this another data platform or digital twin?

No. Prometheux reads your GIS, asset, meter, billing, operational and customer data where it already lives, across clouds and on-premises, and runs the rules there. The model is logical: there's nothing new to migrate or keep in sync.

Do we have to replace our GIS, asset, billing or outage systems?

No. Keep them. Prometheux reads from them, adds the cross-system reasoning, and writes results back to the systems your teams already use, on a schedule, when data changes or on demand.

Does it replace power-flow or physics simulation?

No. Prometheux reasons over connectivity, assets, customers and business rules. Simulation results stored in your databases or files can be read as one more source, alongside everything else.

Does it come with emissions or ESG calculations built in?

No. Your reporting definitions and factors are codified as rules; Prometheux computes each figure from them on your data and shows the lineage to the source rows, so the same inputs always give the same figure.

Our operational data can't leave our environment. Can it run there?

Yes. Prometheux runs on your own servers on Docker or Kubernetes, or in your own cloud, so the data stays under your controls. It works within existing access controls such as Unity Catalog and Snowflake RBAC, and Prometheux is SOC 2 Type II certified.

What does it cost at our data volumes?

It depends on your data and use cases, so we measure it on yours rather than quote a generic figure. Most utilities start with one network area, one process or one report, prove the value, then expand.

Bring One Energy
Use Case.

Outage impact, an asset roll-up, a billing check or one transition figure, on your own data. Our forward deployed engineers will run it with you, in place, on your infrastructure.

We use some essential cookies to make this site work. By clicking "Accept All" you agree to the storing of cookies on your device to enhance site navigation, analyse site usage and assist our marketing efforts. For more detailed information see our Cookie Notice.

Accept AllDecline