See the zone
Each district has meters, pressure, night flow, and a health score.
TwinEdge Water Loss OS
Find the leak. Send the crew. Prove the savings.
A Water OS module for water you treated but did not sell.
Water Loss OS is the non-revenue water module inside Water OS. It shows which district is leaking, splits a real leak from a bad meter, and ranks the next job. A person still sends the crew.
- Fewer wasted visits. Start with the zone that is losing the most water, not every alarm.
- The right kind of work. Do not send a leak crew when the meter is the problem.
- A number the board can trust. Volume, cost, and payback stay on the same record as the repair.
NON-REVENUE WATER
Non-revenue water %, yearly cost, open bursts, and a map of which districts need a look.
START WITHFlow · pressure · asset location
TWINEDGE CONNECTSFind the issue in its network
MOVE FORWARD WITHA targeted field response
THE WORKFLOW
From missing water to a reviewed repair.
Explain the missing water
The water balance splits a leak from a meter error before anyone digs.
Send the right crew
A person reviews the burst, then a work order goes to the field.
Fewer wasted visits
Start with the zone that is losing the most water.
The right kind of work
Do not send a leak crew when the meter is the problem.
A number the board can trust
Volume, cost, and payback stay on the same record as the repair.
FROM THE PRODUCT
See the work in context.
Select a screen to explore the workflow. Open it for a closer look.
01 / INSIDE TWINEDGE
Lost-water command center
See non-revenue water %, yearly cost, open bursts, night-flow alerts, and a map of which districts need a look.
BUILT FOR THE OPERATION
What this module covers.
Zones and the water balance
Districts (DMAs), IWA/AWWA M36 audits, NRW %, ILI, and data-quality grades with draft → review → publish.
Find the leak. or the bad meter
Night-flow drift, burst location, acoustic loggers, satellite leak polygons, stuck meters, and unauthorized use.
Work, payback, and the board pack
Reviewed work orders, leak-program payback, pressure options, NRW scorecards, and reports that cite the same facts.
GO DEEPER
Details for your operating context.
Lost water is a money problem, not only a pipe problem.
You paid to treat and pump that water. Some of it leaked. Some of it was never billed. Water Loss OS keeps both stories on the same district record so operations, metering, and finance stop arguing from different spreadsheets.
- Distribution crews. See which district is leaking, how much extra night flow, and where the burst is likely — then take a work order to that street.
- Metering and revenue. Find stuck meters, under-reads, and unauthorized use so you do not treat a billing problem as a leak.
- Finance and the board. See yearly NRW cost, recovered volume, and which leak program pays back before you fund the next one.
A gated Water OS module. not a second operating system.
In the product this is a permission-gated Water OS module. It sits in Water OS navigation, uses the water-loss services, and needs tenant and user permission. It is not a standalone plant OS.
- The district is the unit of work. Meters, pressure, night flow, bursts, logger hits, and satellite polygons hang off the same DMA. You do not rebuild the network in a leak tool.
- The engines behind the screens. IWA/AWWA balance, night-flow baselines, burst location, meter-error findings, pressure/FAVAD, and leak-payback scenarios are real services — not slides.
- A person still decides. Audits need publish permission. Bursts need dispatch permission. Copilot answers cite the record. TwinEdge does not send a crew on its own.
One lost-water record across the utility
The value is linking leak work to the systems you already run, then carrying the evidence through repair and reporting.
- Water OS
- Districts (DMAs)
- Pressure zones
- Customer meters
- AMI / MDM / billing
- SCADA flow
- GIS
- IWA water balance
- AWWA M36
- Night flow
- Burst location
- Acoustic loggers
- Satellite leak polygons
- Meter error
- Unauthorized use
- Leak payback (ELL)
- CMMS work orders
- Field closeout
- NRW scorecards
- Board packs
CONNECTED BY DESIGN
Fits the systems around it.
Keep source context available as the workflow moves between teams and applications.
One connected record.
TwinEdge Water Loss OS
- Water OS owns the network, zones, meters, assets, and work.
- Your GIS, SCADA, AMI/MDM, billing, acoustic loggers, and satellite scans stay in place.
- Each district (DMA) keeps its meters, pressure, pipe length, customer count, and health score on one record.
- The IWA/AWWA water balance, night-flow drift, burst map, meter-error findings, and leak-payback scenarios share that record.
- A person reviews a burst, then TwinEdge can open a CMMS work order.
- Reports and board packs cite the same water-balance, leak, and repair facts.
BEFORE YOU START
A few useful answers.
Is Water Loss OS a separate product from Water OS?
No. It is a gated module inside Water OS. You do not buy it instead of the network OS. It is the lost-water program on the same district record: zones, water balance, night flow, bursts, and reports.
Does TwinEdge send a crew on its own?
No. Burst findings show zone, evidence, volume, and cost. A person with burst-dispatch permission reviews them. TwinEdge can then open a CMMS work order. It does not dispatch the field on its own.
Does it replace SCADA, GIS, or billing?
No. It reads GIS, SCADA, AMI/MDM, billing, acoustic loggers, and satellite scans. Those systems stay. TwinEdge sits on top so leak work and the water balance share one record.
What is non-revenue water, in plain language?
Water you treated and pumped but did not get paid for. Some of it leaked. Some of it was never billed because a meter stuck, a read was wrong, or someone took water without a meter. Water Loss OS keeps both kinds of loss on the same district.
THE NEXT CONNECTION
Explore the product familyBuild the rest of your loop.
START WITH YOUR OPERATION
Put the next decision in motion.
Discuss your sources, assets, and the outcomes your team wants to improve.