Skip to content
How we work
Start a conversation Talk to us

For energy and utility operators

Meter, asset and operations data your teams can rely on

A data platform for energy and utilities brings meter readings, asset records and operational events into one governed place, checks them as they arrive and serves monitoring, reporting and forecasts from the same data. We would build it inside the boundaries your operations and security teams set.

Free first conversation · A person replies within one business day · You own the code and accounts

Play the scenarios →

01 How we work

How we would work with an operator

  • Operational systems stay protected

    We would read from operational systems only through the interfaces and network boundaries your teams approve. Nothing writes back to control systems unless that is designed and agreed as separate work.

  • Readings checked before they count

    Gaps, duplicates, estimated reads and meter exchanges are flagged as data arrives, so every report or forecast states what it was built on.

  • Forecasts kept apart from measurements

    Demand and consumption forecasts are labeled as forecasts and reported separately from measured results, each with the baseline it is compared against.

  • Access agreed with your security team

    Least-privilege access, encryption, audit logging and data classification are agreed before the build, and we work within your vendor-risk and security review.

What we'll tell you

If your reports only need a daily refresh, we will say so. Streaming earns its running cost only where someone acts on the data sooner.

Event stream

Follow an event from the field to the action

Pick a situation an operator might face. The events show where a check or a rule fires, and what a person does next.

Scripted walkthrough

  • Event
  • Alert
  • Action
Pick a scenario

A meter feed sends gaps and estimated readings

  1. 06:00:00 Event Interval readings arrive from the head-end system for a group of meters
  2. 06:00:04 Event Readings validated, with timestamps, units and meter identifiers checked
  3. 06:00:05 Alert Gap found: part of the group sent no readings for the last interval
  4. 06:00:06 Action The missing readings are marked as missing, not zero, and logged for the metering team
  5. 07:15:00 Action Late readings arrive and fill the gap, and the daily report notes the correction

An asset starts drifting outside its normal range

  1. 11:20:00 Event Transformer telemetry arrives from a substation through the approved gateway
  2. 11:20:30 Event Readings compared with the asset's recent history and its agreed limits
  3. 11:42:00 Alert Temperature trend stays outside the agreed range for longer than the set window
  4. 11:42:01 Action The asset owner is notified with the trend and the asset record attached
  5. 11:55:00 Action An engineer reviews it and raises a work order in the existing maintenance system

Energy reporting needs one set of numbers

  1. 00:05:00 Event Daily consumption totals calculated for each site from validated readings
  2. 00:05:01 Event Site totals reconciled against the billing system for the same period
  3. 00:05:02 Alert One site differs from billing by more than the agreed tolerance
  4. 00:05:03 Action That site is held back and the difference goes to its data owner
  5. 08:30:00 Event The report is published for every other site, with the held site marked pending

How it starts

  1. Map the sources

    We list meter, asset, billing and operational systems, who owns each one, and how data may leave it under your security policy.

  2. Agree definitions and limits

    Consumption, availability and asset health are defined once with your teams, along with the thresholds each alert should use.

  3. One stream, end to end

    A single feed, such as one region's meter data or one asset class, runs from source to a monitoring view with checks and alerts in place.

  4. Review with operations

    Your operations and IT teams judge the first stream on real data. The next source is added only when the value is clear to them.

The usual engagement model: Fixed-scope implementation

Talk this through with us →

Ready to talk it through?

Start a conversation

02 A typical situation

What this usually looks like

A regional utility might come to us with meter data in a head-end system, asset records in a separate maintenance tool, and energy reports assembled by hand from both at the end of every month.

We would start with the meter data: one governed pipeline with validation, gap handling and reconciliation, and a monitoring view the operations team actually uses. Asset telemetry and forecasting would follow once that first stream is trusted.

03 Questions

Questions people ask

Only through the read-only interfaces and network boundaries your operations and security teams approve. Our work sits on the data side, and we do not change how control systems operate.

Yes, once the readings behind them are reliable. Each forecast is labeled as a forecast, compared with a baseline and kept separate from measured results in every report, so nobody mistakes a projection for a result.

Your regulatory and finance teams do. We would build the reporting pipeline to the definitions they set, with lineage so each figure can be traced to its readings, and we would not claim on our own that a report meets a rule.

Each reading keeps a flag for its type, such as actual, estimated or corrected, and a meter exchange starts a new series linked to the old one, so totals stay traceable across the change.

04 Start

Start with the feed that causes the most work

Book a call with an engineer. We will ask where your meter and asset data lives and suggest a first stream worth building.

What happens next

  1. You pick a time, or send us a message.
  2. A person at Nexstella reads what you shared before we talk.
  3. You leave with a clear next step, even when that step is to wait.

Or write to [email protected]. Send a brief instead

Meet

Pick a time with an engineer

What is your work email? The calendar invite and the video link go there.

The invite goes to the calendar you work from. Personal address? Use the Contact tab . If you stop before picking a time, we send one reminder to this address, and nothing else.

30 minutes, video call with an engineer · Times show in your time zone

What happens next

  1. You pick a time, or send us a message.
  2. A person at Nexstella reads what you shared before we talk.
  3. You leave with a clear next step, even when that step is to wait.

Contact

Send us a message

Pick the topic that fits and tell us what you are working on. A person replies within one business day.

A person replies from a real address.

Phone (optional)

Choose the country code, then type the number without it.

The topic leads the subject line, so the right person picks it up first.

A few sentences is plenty. You do not need to know which technology you need.

We use what you send to reply and, if it leads somewhere, to scope the work. Read the privacy notice, or write to [email protected].

Want the full picture? Read Energy and utilities.

Also written for you: Real-time data pipelines , Manufacturing and logistics .

Last updated