Parent–child relationships without a fixed depth
A district meter can feed neighborhood meters, and a neighborhood meter can feed streets, sites or customer clusters. The same logic repeats at every level.
Hierarchical water balance
Move beyond fixed, single-layer zone definitions. Connect meters according to the physical network relationship and follow consumption, child totals, defined use and the difference to investigate at every node.
Operational value
A district meter can feed neighborhood meters, and a neighborhood meter can feed streets, sites or customer clusters. The same logic repeats at every level.
Orion's calculation cut-off data helps compare different points of the hierarchy within the same measurement window.
Start with the difference in the largest zone, move down the branch where it continues and reduce field work to a smaller area.
When a child meter is missing or the measurement window does not match, the result must be presented with its data-quality status rather than as a definitive value.
Zone water balance
See how much of the parent meter consumption is represented by its child meters. If the difference continues, move down one level; if the branch balances, evaluate another branch.
Simplified calculation
A difference is not proof of physical leakage on its own. Meter error, missing data, unauthorized consumption, undefined operational use, boundary transfers or storage changes can also create a difference.
DMA data becomes meaningful alongside leak investigation, meter inspection, field verification, pressure management and network rehabilitation.
Let us model your network together
Review your main inlet, subzones and customer clusters with us. We can define the metering boundary and shared calculation-cut-off approach for your existing infrastructure.