Unified data infrastructure
GitHub Let's talk

Utilities

Assets, outages and consumption in one view.

A utility is a graph with a time series attached: the network says what is connected to what, and the meters say what is flowing through it.

See Time-series Workloads All of Industrial

The grid is a graph, the meters are a series — one layer holds both.

The story

The grid is a graph, the meters are a series — one layer holds both.

Where it starts

Meter and sensor reads

Consumption, voltage, current and quality measurements. It is the first of 4 workloads running in Utilities.

The question it raises

Outage to cause

Restoration events, switching operations and asset condition read together, so an outage is explained rather than annotated.

Why one question is hard

From Generate to Maintain

Utilities data moves through 5 stages — Generate → Distribute → Meter → Operate → Maintain. The shapes in play are Time series, SQL, Events, Graph, Objects, and answering one question means reading across all of them.

What PLOMID contributes

Grid data is relational and temporal at once. These are the parts that hold both without a second system.

  • Time-ordered storage Measurements and events are stored beside the records and documents they describe, so history and current state agree.
  • Predicates narrow the work Indexes and access paths decide what a query touches before a page is read, so operational reads stay bounded.
  • One plan per request A request is planned once against the layer rather than per system, which is where cross-system glue usually accumulates.
The environment

Grid topology, meter reads, asset condition and customer records.

Topology is relationship data, meter reads are time-ordered, customers and assets are records, and maintenance history is documents. Today those sit in four systems and are joined by convention. PLOMID keeps them in one layer, which is what makes a customer question or an outage analysis a single query rather than a project.

One environment · many workloads

What runs against utilities data.

4 workload families over one set of shapes. Choose one to see what it moves and where it lands.

Consumption, voltage, current and quality measurements.

  • Planned once against the layer, not once per store
  • Read beside the records it shares a key with
  • Persisted under one storage contract
The data journey

How utilities data reaches one layer.

Walk the path the data takes, from the environment that produces it to the questions it answers. Select a station, or a shape, to read each step.

The grid is a graph, the meters are a series — one layer holds both.

Environment

The network

Substations, feeders and transformers connected in a topology.

Graph

Where the data goes to work

Questions the field asks daily.

Each one is a workload over the shapes above, answered from the same layer rather than from a purpose-built copy.

Outage to cause

Restoration events, switching operations and asset condition read together, so an outage is explained rather than annotated.

  • Time series

Customer to network

An account resolves to its service point, its meter series and its maintenance history in one request.

  • Time series
  • SQL

Loss and quality analysis

Reads and topology in one layer make losses a computed property rather than a reconciliation exercise.

  • Time series
  • SQL

Asset condition evidence

Inspection documents and measurements stay attached to the asset that carries them.

  • Events
  • Graph
Data models in play

The shapes, in one layer.

5 shapes carry this domain. Choose a stage to read the operation, or a shape to see every stage that handles it.

PLOMID · Utilities generate · distribute · meter · operate · maintain Select a stage
Stage

Generate

Generation and transmission measurements

Time series

Workload map Utilities workload map. Every shape on it is a surface of the layer, and each stage names the part of the operation it carries.
  • Time series Measurements and events in time order
  • SQL Records, keys and joins
  • Events Operational events as they happen
  • Graph Relationships and traversal
  • Objects Large assets with queryable metadata
Workload architecture

Which workload touches which model.

The work, the shapes it names and the path a request takes — from the field to the control room.

Utilities · workload architecture
Workloads

What runs against this data.

  • Meter and sensor reads
  • Network topology
  • Asset and customer records
  • Switching and outage events
Data models

The shapes those workloads read and write.

  • Time series
  • SQL
  • Events
  • Graph
  • Objects
The layer

One path from a request to the data it names.

  • Planning Predicates narrow the work before it runs
  • Execution Records, fields and windows answered together
  • Transactions Readers and writers do not block each other
Surfaces

How the work reaches the layer.

  • SQL surface The query language the layer is documented in
  • Applications Services and jobs writing and reading as they run
  • Analytics & AI clients The same layer, the same access path
Deployment & residency

Where this data is allowed to run.

Distribution substations and the control room both read the same network state.

Deployment, residency and control
What you build next

Time-series Workloads

Measurements and events stored beside the records they describe.

If Outage to cause is your question, start here.

See Time-series Workloads Every solution
Next

Where to go next

Solutions The workload answers this industry leans on, with their models and status. Platform The data models in the product today, and the ones extending the layer. Architecture How a request is planned, executed and persisted once it reaches the layer.