Skip to content
Generators, networks, retailers and the engineers who keep them up

Energy & Utilities

Meter data validation, asset and outage triage, market and regulatory submissions, field work packs, grid telemetry and connection applications — built so the system assembles and a control engineer decides.

Everything is measured and very little is trusted. Meter reads, asset telemetry and outage records arrive late, incomplete or contradicting each other, and the regulatory cost of acting on a bad reading is far larger than the cost of waiting for a good one.

Workflows

What we automate, and where it stops

Every one of these ends one step short of the decision. In a regulated industry that is not caution, it is the architecture — and it is what makes the work approvable.

Meter data validation and estimation

  1. Reads
  2. Validate
  3. Exceptions with reason codes

An estimate is labelled an estimate, and a revenue figure is approved by a person.

Reads validated against their own history and the network position, with every failure carrying a reason code rather than a silent substitution.

Built with Platform & Data

Asset condition and outage triage

  1. Telemetry + reports
  2. Correlate
  3. Ranked work queue

A control engineer dispatches. Nothing switches the network.

Device telemetry, customer reports and protection events correlated into candidate causes, each carrying the signals that support it and the ones that argue against.

Built with Delivery Telemetry & Observability

Market and regulatory submissions

  1. Sources
  2. Assemble
  3. Submission with a derivation trail

A regulatory lead submits. The trail is as much the deliverable as the return.

Returns assembled from their sources with the derivation of every figure recorded, so a challenge years later has an answer that does not rely on memory.

Built with Platform & Data

Field work pack assembly

  1. Job
  2. Gather asset history and permits
  3. Pack, gaps flagged

A supervisor releases the job. A missing permit blocks it rather than being assumed.

Asset history, drawings, isolation requirements and permits assembled into a pack that is either complete or explicitly short of named items.

Built with Workflow Automation & Integration

Grid and generation telemetry

  1. Device streams
  2. Normalise
  3. Typed series, gaps marked

A gap reports as unknown. An interpolated value is never written as a reading.

Streams from field devices of wildly different vintages normalised into typed series that carry their own coverage, so a quiet device is visible as a quiet device.

Built with Robotics & Embedded

Connection applications and network studies

  1. Application
  2. Check against constraints
  3. Ranked queue with rationale

An engineer approves every connection offer.

Applications checked against network constraints and policy, with each position carrying the constraint it turns on and the headroom calculation behind it.

Built with AI & Applied ML

Constraints

What is actually hard here

There are no client names, logos or percentages on this page. Until there is a real figure with permission to publish it, the space is better spent on the difficulties we can defend.

Nothing switches the network

Every workflow stops short of an operational switching or dispatch decision, with a named engineer at the stop. The consequences here are physical and they are not reversible by a rollback.

Read the long version

An interpolated value is not a reading

Estimation is legitimate and labelling it is not optional. Once an estimate is stored in the same column and the same type as a measurement, no downstream consumer can tell them apart, and settlement runs on the difference.

The control has to survive a regulator

Evidence, segregation of duties and change management designed in, rather than reconstructed when somebody asks. A control that exists only in an engineer’s habit is not a control.

Read the long version

Field software is software you cannot patch

A device on a pole has a release cadence measured in years and a rollback story of sending a van. That changes what belongs on the device and what belongs behind it.

Read the long version

Verification is the work

Generating a draft is cheap and checking it is not. Capacity planning that assumes otherwise produces a pile of unreviewed output and calls it throughput.

Read the long version

Bring us the workflow, not the brief.

Describe what your team does by hand today and where it backs up. We will tell you which part is assembly, which part is judgement, and which of the two we would touch.