TwinEdge Water Loss OS
The Water OS operating layer for NRW, DMA health, leak evidence, field action, and board reporting.
Water Loss OS is the NRW module inside the TwinEdge water utility operating layer. It connects DMAs, master meters, customer consumption, pressure, MNF drift, burst localization, acoustic and satellite evidence, ELL scenarios, work orders, regulatory reports, and copilot citations around one source-backed operating record.
DMA health
IWA balance
MNF drift
Burst localization
Apparent loss
ELL economics
Water Loss OS connects the network model, customer meter record, pressure signal, leak evidence, repair work, and reporting pack inside Water OS.
Platform in action
Water-loss operations as a connected Water OS module
These screens come from the Water Loss OS module. The value is not another dashboard: each surface is tied to Water OS identity, telemetry, meter data, evidence, approval state, field work, and reporting.
Water-loss command center
The NRW dashboard combines approved water-balance results, DMA health, open bursts, MNF drift, recent audits, and the next operating actions.
District metered areas
DMA records carry boundaries, inlet and outlet meters, service class, customer count, main length, pressure, status, and current health.
IWA water balance
Audits structure system input, authorized consumption, apparent losses, real losses, NRW volume, ILI, cost, validity, and approval state.
Minimum night flow drift
MNF baselines, legitimate night use, drift severity, excess flow, investigation status, and supporting DMA context stay in one review queue.
Bursts and leaks
Burst candidates combine flow anomalies, pressure transients, acoustic or satellite evidence, confidence, estimated cost, and dispatch readiness.
Workflow
From NRW signal to reviewed action and defensible reporting
Water Loss OS turns network, meter, pressure, acoustic, satellite, and field evidence into a controlled operating loop that operations, revenue assurance, finance, and leadership can trust.
Model the water-loss operating objects
Map DMAs, service connections, meter registers, inlet and outlet meters, master meters, pressure zones, mains, customer classes, GIS assets, SCADA flow, AMI/MDM/CIS readings, work history, and evidence sources into the Water OS spine.
Separate real loss from apparent loss
Use IWA/AWWA balance, validity grading, MNF baselines, pressure behavior, burst candidates, logger evidence, satellite polygons, meter drift, stuck meters, unauthorized use, and data-handling exceptions to classify loss mode before action.
Prioritize reviewed action with evidence
Rank investigations by DMA health, excess flow, confidence, cost, service impact, pressure opportunity, ELL economics, repair feasibility, approval status, and planner-reviewed work-order readiness.
Capabilities
What Water Loss OS delivers
Built for distribution operations, NRW analysts, revenue assurance, field crews, finance, compliance, and utility leadership.
DMA health and IWA/AWWA water balance
DMA records, boundary context, inlet/outlet/master meters, service class, connection count, main length, current NRW percentage, ILI, cost, validity grade, and audit history.
Detection, localization, and apparent-loss intelligence
MNF baselines, drift events, burst confidence, pressure transients, acoustic logger review, satellite leak polygons, meter drift, unauthorized use, stuck meters, and billing-data exceptions.
Economics, work, reporting, and copilot
ELL scenarios, pressure/FAVAD analysis, estimated volume and cost, planner-reviewed work orders, repair evidence, NRW scorecards, M36/IWA board packs, regulatory handoff, and cited copilot answers.
Industry vertical fit
Water Loss OS makes the distribution side of Water OS commercially actionable.
Non-revenue water is not only an engineering problem. It touches distribution operations, customer metering, revenue recovery, capital planning, compliance evidence, and public trust.
Distribution networks
DMAs, pressure zones, PRVs, mains, valves, hydrants, service connections, burst events, pressure traces, and pipe context help operators locate and prioritize real losses.
Customer metering and revenue assurance
Residential, commercial, mixed, and industrial service classes connect AMI/MDM/CIS evidence to meter drift, stuck reads, data errors, unauthorized use, and apparent-loss recovery.
Field, finance, and compliance
Repair work, crew closeout, estimated recovered volume, avoided cost, regulatory water-balance evidence, and board reporting stay tied to the same source facts.
Operating layer implementation
The module is packaged as a Water OS operating loop, not a disconnected NRW dashboard.
The implementation spans Water OS navigation, module permissions, water-loss API domains, canonical water objects, event history, reports, and field-action handoffs so every screen works from the same operating record.
Canonical network and meter context
DMAs, service connections, meter registers, pressure zones, assets, work, logger evidence, and satellite polygons are represented as operating objects with relationships back to the utility network.
Analytic engines behind the workflow
IWA/AWWA balance, validity grading, MNF learning, burst localization, apparent-loss findings, pressure/FAVAD, ELL optimization, forecasts, reports, and copilot answers are exposed as governed module services.
Action, approval, and evidence lifecycle
Findings move through review states, permissions, work-order paths, field evidence, regulatory report generation, board packs, and source citations instead of ending as static analytics.
Connected surfaces
One NRW operating record across the platform
The customer value comes from linking water-loss analytics to the operating systems utilities already use, then carrying the evidence through investigation, repair, and reporting.
Engineering controls
Governed controls for water-loss decisions.
Water Loss OS supports advisory NRW analytics, reviewed repair prioritization, and evidence-backed reporting without claiming uncontrolled field dispatch or SCADA replacement.
Advisory first
Loss findings explain DMA context, source evidence, confidence, volume, cost, and recommended next step before teams approve action.
Source system respect
Water Loss OS works above GIS, SCADA, AMI/MDM, CIS, acoustic, satellite, CMMS, and regulatory systems instead of replacing them.
Planner-reviewed action
Burst response, leak investigation, meter review, pressure changes, and repair work move through reviewable workflows and work-order paths.
Evidence by default
Water audits, MNF drift, pressure traces, logger evidence, satellite polygons, repair photos, and report approvals remain traceable.
Outcomes
Customer outcomes
Water Loss OS helps customers reduce avoidable water loss, focus scarce field capacity, recover revenue, and explain NRW investments from evidence that stays attached to the operating layer.
Operations and field teams
Stop chasing every alarm. Start with the DMAs, bursts, pressure events, and leak evidence that show the strongest volume, confidence, and repair-readiness signal.
Revenue assurance and compliance teams
Separate real losses from apparent losses with IWA/AWWA structure, meter evidence, audit validity, and source-backed explanations for regulators and internal review.
Finance and utility leadership
Quantify lost volume, avoided cost, repair ROI, pressure-management tradeoffs, capital needs, and board-level progress without rebuilding the story in spreadsheets.
Connected platform
Connected to the TwinEdge water industry spine
Water Loss OS is packaged as a module inside the TwinEdge water vertical, so NRW work inherits network, meter, telemetry, asset, field, regulatory, governance, and evidence context instead of living beside it.
Water OS passes distribution network, pressure zone, customer meter, asset, work, and compliance context into Water Loss OS.
GIS, SCADA, historians, AMI/MDM, CIS, acoustic loggers, satellite leak polygons, CMMS/EAM, and regulatory systems keep their role.
DMA records connect boundaries, inlets, outlets, master meters, service class, customer count, pipe length, pressure, and health score.
IWA/AWWA water balance, MNF baselines, pressure events, burst candidates, apparent-loss findings, and ELL scenarios share one operating record.
Repair priorities move into planner-reviewed work orders while field evidence, estimated volume, cost, and closeout status stay attached.
Reports, board packs, regulatory submissions, and copilot answers cite the same source facts instead of creating another spreadsheet trail.
Evaluate TwinEdge
Turn non-revenue water into a measurable Water OS operating loop.
Start with the highest-risk DMAs, connect meter and pressure evidence, prioritize leak and apparent-loss work, then expand into a utility-wide NRW program using the same TwinEdge operating context.