Skip to content

Utilities, energy & water

For energy and water networks: use against what you expected, equipment that keeps failing, areas losing service, maintenance falling behind, and what is lost between delivered and billed.

Connect → Understand → Verify → Steer → Ask → Act

Flip the card: here is the answer

Every question is tied to the report that answers it.

The reports setup proposes

One for each goal you pick, plus Data health. Open the tabs.

Utility Operations 360 — Follow consumption against what you expected

Over time

shape only

What it answers
A deviation is either a fault or a loss — both need looking at.
What it reads
Your meter readings, with their date and location.
Example finding
Use in one district is well above what was expected for the season.

Shapes and findings are examples. Each report is built only when your data holds what it reads; one that cannot be built is named at setup, never estimated.

Everything converges into a single model

From Snowflake, Amazon S3, PostgreSQL, MySQL, Odoo, Salesforce or a file from your computer. What is missing gets flagged, not guessed.

SnowflakeAmazon S3PostgreSQLMySQLOdooSalesforce+ 1 moreYourmodelReportsData healthAlertsExports
  • Your meter readings, with their date and location.
  • Your incidents with the asset, the date and how long it lasted.
  • Your outages with their area, start time and end time.
Data360One model of your business
  • Your work orders with the date planned and the date done.
  • Your volumes delivered and your volumes invoiced.

None of this is required. Each report reads only its own line; one whose data is missing is named at setup, never guessed.

What Data360 finds in your data

Every issue is translated into a business consequence.

Checks running

5 checks
  • Gaps in meter readings
  • Readings that cannot be right, such as negative use
  • Equipment written two different ways
  • The same incident recorded twice
  • Readings in mixed units

Rows that pass each check

Measured on the same data your reports read.

85%
Recent enough
95%
Nothing missing
79%
Everything agrees
75%
Counted once

Percent of rows, illustrative. Real scores are measured on your own data.

Business findings, not technical alerts

Each finding names the report it comes from.

  • Use in one district is well above what was expected for the season.

    From the report Follow consumption against what you expected

  • The same five pumps account for most repeat incidents.

    From the report See where incidents keep coming back

  • One area has had more interruptions every month this year.

    From the report Track interruptions area by area

  • Overdue work on critical equipment has grown for six weeks.

    From the report Know what maintenance is falling behind

  • One site has sent no meter readings for nine days.

    From the report Data health

Example findings. Real ones come from your own data, in the report that produces them.

A finding with no follow-up is worth nothing

Six things Data360 does once a figure matters.

  • AlertSet a line on a figure that matters and see when it is crossed.
  • Tell peopleTell you, chosen teammates, or everyone who can open the app.
  • Refresh reportsRead the figures again so every report is current.
  • Re-check qualityMeasure the tables again and flag what broke.
  • Clean and saveRemove duplicates, filter, combine and total, then save the result as a table.
  • ExportTake the rows behind a figure away as a spreadsheet file, or save them as a table.

See Utility Operations 360 on your own data.

Your goals, your data — and the reports built from them.