Unified data infrastructure
GitHub Let's talk

Energy

Grid, generation and meters read as one system.

Energy operations run a plant and a position at the same time: what the asset is producing, and what that production is worth and accountable for.

See Time-series Workloads All of Industrial

From sub-second plant telemetry to a settlement both sides accept.

The story

From sub-second plant telemetry to a settlement both sides accept.

Where it starts

Plant telemetry

Output, availability, temperatures and status as measurements. It is the first of 4 workloads running in Energy.

The question it raises

Availability as measured

Availability computed from telemetry and from records in one statement, rather than two definitions that disagree.

Why one question is hard

From Generate to Settle

Energy data moves through 4 stages — Generate → Dispatch → Meter → Settle. The shapes in play are Time series, SQL, Events, JSON / documents, and answering one question means reading across all of them.

What PLOMID contributes

Operations and settlement ask different questions of the same data. These are the parts that let both be answered.

The environment

Generation output, plant state, market positions and settlement records.

Sub-second telemetry describes plant state, while settlement and contract records describe obligations. The two are reconciled today in reports assembled after the fact. PLOMID holds measurements and records in one layer, so availability, output and settlement can be read from one source.

One environment · many workloads

What runs against energy data.

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

Output, availability, temperatures and status as 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 energy 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.

From sub-second plant telemetry to a settlement both sides accept.

Environment

The unit

A generation unit producing, curtailed or dispatched, around the clock.

Time series

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.

Availability as measured

Availability computed from telemetry and from records in one statement, rather than two definitions that disagree.

  • Time series

Dispatch to settlement

A dispatch instruction and the meter data that followed it are read together, which shortens reconciliation arguments.

  • Events
  • SQL

Plant and portfolio reporting

Aggregates over operational data serve both the operations room and the settlement view.

  • Time series
  • SQL

Asset history in one place

Unit records, outages and measurements share a layer, so a unit’s story is queryable rather than filed.

  • SQL
  • JSON / documents
Data models in play

The shapes, in one layer.

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

PLOMID · Energy generate · dispatch · meter · settle Select a stage
Stage

Generate

Unit output and availability measurements

Time series

Workload map Energy 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
  • JSON / documents Documents and nested objects
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.

Energy · workload architecture
Workloads

What runs against this data.

  • Plant telemetry
  • Asset and contract records
  • Market and dispatch events
  • Settlement documents
Data models

The shapes those workloads read and write.

  • Time series
  • SQL
  • Events
  • JSON / documents
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.

Generation sites and trading desks read the same data across a wide network.

Deployment, residency and control
What you build next

Time-series Workloads

Measurements and events stored beside the records they describe.

If Availability as measured 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.