WATER UTILITIES AND MUNICIPALITIES
Smart metering affects non-revenue water investigation, customer service, field planning and crisis management at the same time. This page frames the investment through those four topics.
CONTEXT IN TÜRKİYE
The Water Efficiency Strategy Document and Action Plan sets dated water-loss targets for municipalities. Meeting them depends on seeing what happens in the network earlier and in more detail.
0%
Average drinking-water loss in Türkiye (2021)
Source: Water Efficiency Strategy Document and Action Plan, Ministry of Agriculture and Forestry
0%
Non-revenue water rate (2021)
Source: Water Efficiency Strategy Document and Action Plan
0%
2028 water-loss ceiling for metropolitan and provincial municipalities
National target; the 2040 target is 10 percent.
These figures are national averages and do not describe any single utility. The local baseline should be established through the utility's own water balance study.
USE CASES
The scenarios below concern different teams. The same data answers different questions.
Compared against zone inlet measurement, customer meter data shows where the gap concentrates. The field team then surveys the priority zone rather than the whole network. Combined with a DMA approach, the result is sharper still.
When index and consumption profile are stored together, a dispute is answered with a record rather than an estimate. High bills caused by leaks inside the property are noticed early.
Device health data turns battery replacement, weak signal and faulty valves into planned work. Visits are batched by zone instead of handled one by one.
During restrictions, consumption trends can be followed by zone and the effect of policy-driven throttling decisions can be measured. Graduated throttling instead of a full shut-off is an option that reduces social impact.
END USERS
Smart metering does not only make the utility's work easier. Set up properly, it has concrete benefits for the customer too.
Because the index is read remotely, estimated bills caused by nobody being home — and the corrections that follow — become rarer.
When continuous flow inside the property is detected early, the customer can act before facing a large bill.
Because the consumption profile is retained, a dispute is assessed against timestamped records rather than an estimate.
Where policy allows, graduated throttling rather than a full shut-off can preserve access to basic water supply.
Detailed consumption data can carry information about household behaviour. What is collected, how long it is kept and who can access it must therefore be communicated clearly to customers, and data minimisation must be part of the design.
OUTCOMES TO MEASURE
The items below are not a performance guarantee; they are indicators to be measured together during the pilot programme. Target values are set by the utility and the product team at the start of the project.
KPI 01
How many of the expected daily and weekly packets arrive on time, reported separately by coverage class.
KPI 02
The number of planned visits removed because configuration and firmware work can be done remotely.
KPI 03
The time between an event occurring on the device and the field team acting on it.
KPI 04
Missing and duplicate packet rates, together with P50/P95 data latency.
KPI 05
The share of devices completing an update in one rollout and the number needing a field visit.
KPI 06
The working days needed before data starts flowing into the utility's HES/MDM, SCADA or GIS system.
No target figure is published on this site for these items. The measurement method is defined in writing before the pilot so that a comparable baseline exists.
NEXT STEP
Let us validate the coverage, data, battery and integration assumptions together in a limited pilot. We write the success criteria before the pilot begins.
