Definition
DMA (District Metering Area) is a pipeline network management method in smart water services. It divides the water supply network into independent metering areas (usually 500–5000 households), and installs flow meters, pressure meters, water quality sensors, etc., at the entrances and exits of each area to monitor the water inflow, outflow, pressure, and water quality in real time. Through water balance analysis (inflow - legal water consumption ≈ leakage), it can detect leaks, abnormal water usage, and illegal water extraction.
DMA relies on data acquisition and upload from IoT devices such as flow meters, pressure meters, and data collection terminals (RTU). IoT SIM cards provide connectivity for DMA flow meters, pressure meters, and data collection terminals, supporting leakage analysis, remote monitoring, and nighttime minimum flow (MNF) analysis. DMA is similar to the FTU zoning concept in distribution networks, both achieving refined management through zoned metering.
Technical Features
DMA uses wireless communication such as NB-IoT and 4G, making it suitable for scenarios where the network is dispersed or wired deployment is difficult. The data collection frequency is usually 15 minutes to 1 hour and supports real-time reporting of abnormal alarms. When integrated with GIS, SCADA, and leakage management platforms, it can achieve a unified network map, leakage localization, and pressure optimization scheduling.
Use Cases
DMA is applied in smart water services, water supply networks, leakage control, secondary water supply management, and more. Typical scenarios include zoned flow monitoring, leakage analysis, abnormal pressure warning, remote meter reading, water quality monitoring, and DMA performance evaluation. SimtoLink provides IoT SIM cards, dedicated APN, VPDN private networks, and smart water solutions for DMA zoned metering.
Why minimum night flow depends on the clock
District metering estimates leakage from the difference between inlet and outlet flow. The IoT SIM carries flow, pressure, and where needed water quality from a chamber or a gallery to the analysis platform. The difference means something only for the same period and the same district boundary. Minimum night flow is used to see how much water is still moving when legitimate use is at its lowest. If the inlet meter and the outlet meter disagree by ten minutes, the low point is matched to the wrong time. The difference mixes in normal use from the neighboring period, and leakage is either enlarged or hidden. A SIM that is online does not replace that time alignment. If one meter on the district boundary has not reported, the missing value must not be written as zero and then balanced.
The district boundary has to have been checked in the field. Meter direction, diameter, and the straight pipe at the install must meet the measurement requirement. The logger must be able to keep at least one analysis period in a damp, shielded chamber. Stagger reporting times so every district in the city does not attach in the same minute. Pressure and flow may be uploaded from the same point, but do not use the pressure terminal’s clock to rewrite the time of the flow curve. Bind the SIM to the district id and the chamber location. After a valve change or a district merge, update the boundary immediately, or the new flow is counted into the old district. Restricted access should reach only the water platform. A solar or battery logger, when voltage is low, should prefer to keep the minimum-flow interval already collected, not keep registering to the network.
A common error is to divide daily cumulative volume by twenty-four hours and call that night flow. The daily total is online and the night curve is empty, so the minimum flow does not exist. Another is catch-up stored by arrival time, so night data is drawn in the morning and the balance shows a false daytime leak. A third is an inlet meter whose multiplier was not updated after replacement. The difference changes sign and is explained as an improvement in non-revenue water. A metal cover lets the site report by day and fail to send at night in power-save. A rule that looks only at daily online rate misses the hours that actually judge leakage. Acceptance should pick one district, drop the uplink during the night window, restore it, and check that minimum flow still falls in the original period and that a gap is not filled with zero. One way to code the meter object is described under DLMS/COSEM. Cumulative reporting on the agricultural side is described under agricultural water metering.
Boundary changes, valve movements, and mains flushing have to be events. Flow difference in those intervals does not go straight into the leakage assessment. Compute minimum night flow only when both inlet and outlet have data with the original timestamp. If either side is missing, output “cannot be calculated,” not a substitute built from the daily total. A meter installed backward changes the sign of the difference. At commissioning, check direction with one known use. If damp in a chamber makes the terminal restart intermittently, sequence numbers must stay continuous across the restart, or the platform treats the restart as a new district. Look at a pressure jump next to a flow jump. Pressure without flow is not, by itself, a leak conclusion. Update the SIM-to-chamber binding on the day districts are merged, and stop issuing a report for the old district. After catch-up inside the analysis period finishes, recompute that night’s minimum flow, and keep both the value before and the value after, so the report does not change quietly after catch-up with no note. In winter, check whether a solar terminal can still cover the night window. If it cannot, treat the night gap as a known limit. Do not lower the judgment standard to make the number fit.
Generate the official district report once, after catch-up ends. Mark figures before that as provisional. Do not use provisional figures for assessment. If either the inlet or the outlet meter is under maintenance, do not calculate leakage for that district that day, and leave the maintenance event in the report. On the first night after a chamber SIM is replaced, look separately at whether minimum flow still falls in the original period, and confirm that the clock and the district id were both inherited. A district that failed inheritance does not get a leakage conclusion that day.