How do you compute a district metered area (DMA) and why is it used for water audit?

How do you compute a district metered area (DMA) and why is it used for water audit?

• A. Aggregate all meters to compute citywide leaks.
• B. Remove meters to simplify accounting.
• C. Use only weather data to estimate leaks.
• D. Segment the network with metering to create a district; used to isolate flows for leakage detection and performance benchmarking.

Answer: (D)

Segmenting the distribution network with metering to create districts allows you to isolate flows and measure what happens in a defined area. To compute a DMA, boundaries are established by using valves or other control points to form a distinct district, and a boundary flow meter is placed at the edge to capture all water entering and leaving that district. Inside the DMA, all customer meters and known uses are accounted for. The water balance then compares the inflow measured at the boundary to the sum of measured internal demand and known outflows. The difference reveals leakage and any unmetered or unaccounted water. This approach is used for water audits because it makes leakage detection more precise and provides a meaningful benchmark of performance. By limiting the analysis to a bounded area, you can identify where leaks are, track progress over time, and compare NRW and leakage performance across DMAs, rather than getting obscured by citywide variability. Other options don’t fit: aggregating meters citywide hides localized leaks; removing meters undermines data quality; and relying only on weather data ignores actual measured flows and losses needed for a reliable water balance.

Segmenting the distribution network with metering to create districts allows you to isolate flows and measure what happens in a defined area. To compute a DMA, boundaries are established by using valves or other control points to form a distinct district, and a boundary flow meter is placed at the edge to capture all water entering and leaving that district. Inside the DMA, all customer meters and known uses are accounted for. The water balance then compares the inflow measured at the boundary to the sum of measured internal demand and known outflows. The difference reveals leakage and any unmetered or unaccounted water.

This approach is used for water audits because it makes leakage detection more precise and provides a meaningful benchmark of performance. By limiting the analysis to a bounded area, you can identify where leaks are, track progress over time, and compare NRW and leakage performance across DMAs, rather than getting obscured by citywide variability.

Other options don’t fit: aggregating meters citywide hides localized leaks; removing meters undermines data quality; and relying only on weather data ignores actual measured flows and losses needed for a reliable water balance.