When the board asks "what was our NRW last quarter?" — finance pulls from billing, ops from the AMI portal, engineering from SCADA. Each on a different schedule, each rounded differently. The number that hits the board packet depends on who built the slide. Orbit Insights is the one place all three teams pull from.
Non-Revenue Water by DMA
Week of May 12 · refreshed 2 min ago
System NRW
7.9%
↓ 0.4 WoW
Highest DMA
DMA-8 · 18.7%
↑ 8.4pp WoW
Lowest DMA
DMA-9 · 3.8%
↓ 0.1 WoW
What we hear at the water conference
Same AMI, SCADA, GIS, and billing data — one reconciled view that finance, ops, and engineering all pull from. Refreshing as data comes in, not once a year.
Which 50 meters had the biggest jump in usage last month?
Results · 50 accounts
+ 45 more accounts
Sourced from billing + AMI · reconciled this morning · 12,847 accounts evaluated
What Orbit Insights does
Beyond "everything in one place" — the questions utilities ask first.
Localized to each district metering area, refreshing weekly. Color-coded by severity. The DMA that jumped 8% week-over-week is the one your crew investigates Monday.
"Which 50 meters had the biggest jump in usage last month?" Returns the list + chart in seconds. No SQL, no analyst.
The annual compliance doc that usually takes someone two weeks. Pulled from the same data Insights already has. Continuous, not annual.
Identifies accounts where winter-quarter averaging is over- or under-charging vs actual usage. Defensible to rate-case commissioners.
Production vs distribution, automated weekly. The reconciliation runtime that took 6-8 hours now runs in under 20 minutes.
Leak signature detected on a specific account creates a draft WO with meter location and customer info. Dispatcher reviews and assigns.
See the surfaces your team actually uses
For the analyst nobody has
Insights speaks the question your finance director asked at the council meeting. No SQL, no waiting on IT, no analyst translating the question into a query.
Which 50 meters had the biggest jump in usage last month?
Results · 50 accounts
+ 45 more accounts
Sourced from billing + AMI · reconciled this morning · 12,847 accounts evaluated
For your annual M36 audit
Same AWWA M36 framework you (or your consultant) ran annually. Orbit pulls the inputs from your live data continuously. Tuesday morning the number is current, validity-scored, ready for AWWA submission.
AWWA M36 Water Audit · Continuous
Water Supplied (MG)
847.2
AMI + production meter
Authorized Consumption (MG)
781.4
92.2% · billed + unbilled
Apparent Losses (MG)
12.8
meter inaccuracy + admin
Real Losses (MG)
53.0
leakage + breaks
NRW (system-wide)
7.8%
below industry median
ILI (Infrastructure Leakage Index)
2.1
efficient zone
Data validity score: 78 / 100
Production meter calibration is >12 months old. Audit defensible but score improves to 86 after calibration.
How utilities use Insights day-to-day
Finance Director
Mid-market utility · board meeting next week
Used to defend three different NRW numbers from three different teams in the same board meeting. Orbit consolidates AMI, SCADA, GIS, and billing into a single reconciled view. Finance, ops, and engineering pull from the same place.
Engineering Manager
8K-meter utility
Used to look at system-wide NRW (7.9%) and shrug. Orbit's by-DMA view showed DMA-8 jumped to 18.7% — investigation found 3 small leaks and a faulty pressure regulator. Back below 6% within a quarter.
Ops Director
M36 audit time, every year
Annual M36 audit used to mean 2 weeks with a consultant, then signoff weeks later. Orbit runs the audit continuously — Tuesday morning the FY26 number was ready, fully reconciled, validity-scored, ready for AWWA submission.
One platform, not three integrations
The data layer everyone else pulls from — anomalies become WOs, alerts become resident messages, audits become board packets.
AMI ↔ SCADA reconciliation
Weekly run, DMA-level NRW computed
High-loss DMA flagged
Auto-creates investigation WO batch
Leak survey dispatched
Crew assigned by DMA boundary
Residents in DMA notified
Heads-up SMS about service investigation
Field findings flow back
Loss source confirmed, NRW number updates
Common questions
Reference reading
Plain-English reference content on the regulations, frameworks, and operational programs this product touches.
NRW by DMA
Why the system-wide NRW number hides where the loss actually is — and how DMA-level visibility surfaces it.
Read →
AWWA M36 Water Audit
The standard framework for measuring and reporting water loss. Methodology, validity scoring, ILI.
Read →
AMI/SCADA Reconciliation
Why AMI, SCADA, and billing data don't match — and how to reconcile them into a defensible loss number.
Read →
Water Loss Control
How utilities measure, prioritize, and reduce water loss across apparent and real losses.
Read →
Infrastructure Leakage Index (ILI)
The water-loss benchmark that lets you compare your utility against any other regardless of size.
Read →
M36 Data Validity Score
The 0-100 score that tells regulators how much to trust your water audit.
Read →
Built by people who installed the meters
100K+
meters installed
21
states
200+
collectors deployed
We built Orbit because the software our crews were handed didn't work. Then we made it available to every utility we work with.
More of the Orbit platform
Magic-link in and explore a pre-seeded utility workspace. Real WOs, real reports, no setup.
We'll email you a one-time link to utilitysandbox.orbitwork.io
Book a 15-minute demo and see how Orbit can streamline your field operations. No commitment, no pressure — just a quick look at what's possible.