Automatic meter reading (AMR, known in Türkiye as OSOS) means fitting water, electricity, gas and heat meters with a communication device that reads the index at set intervals and sends it to central software. Nobody walks from door to door, readings are no longer typed by hand, so billing errors and disputes fall, and a stopped meter or an illegal connection shows up long before the next billing cycle. Getting it right depends on planning three things together: the meter types, the network coverage on site and the billing system the data must reach.
What manual reading actually looks like on the ground
In a water utility, an organised industrial zone or a multi-block residential estate, manual reading repeats the same cycle every month. A crew drives out, hunts for the key to the meter cabinet, and estimates the reading wherever a door stays shut. Every link in the chain, from the handheld terminal to the billing system, can fail: digits are misread, entered against the wrong account or never captured.
The deeper problem is timing. If a meter stops, a pipe bursts or someone bypasses the meter, a monthly read only reveals it weeks later. The consumption in between is either never billed or disputed, and with one data point per month, analyses such as night-time flow or zone-level losses are impossible.
Automatic meter reading changes this in two ways. It cuts the cost and error rate of reading, and, more importantly, it raises the reading frequency so that problems surface when they happen rather than at the end of the month.
What doing nothing costs
On the water side, the cost is measurable because water supplied but not billed is recorded:
According to Türkiye's Ministry of Agriculture and Forestry, the average water loss rate in drinking water networks fell from 39% in 2015 to 31.6% in 2024, and metropolitan and provincial municipalities must bring it down to at most 25% by 2028. (Ministry of Agriculture and Forestry — Urban Water Efficiency)
That target is a legal obligation, not a recommendation. Türkiye's 2014 Regulation on the Control of Water Losses in Drinking Water Systems sets limits of 30% by 2028 and 25% by 2033 for smaller municipalities too. Commercial losses such as misreads, under-registering meters and theft stay largely invisible without accurate, frequent meter data.
Globally the picture is starker still. The World Bank's assessment of non-revenue water puts water produced but never billed at 126 billion cubic metres a year, equivalent to nearly $40 billion in annual losses from waste and foregone revenue.
In energy, measurement is the precondition for efficiency. According to the Turkish Ministry of Energy's Second National Energy Efficiency Action Plan, buildings and services accounted for 32.6% of Türkiye's final energy consumption in 2022, and industry for 31.6%. That share cannot come down without seeing consumption per flat, building or line.
How an AMR system works
Every automatic meter reading system has four layers, and each one needs its own decision:
- The meter. Mechanical or ultrasonic water meters, single- or three-phase electricity meters, gas meters or heat meters. Whether the meter has a pulse output, an optical port or an M-Bus/RS-485 interface decides which reading device can be used.
- The communication device. A module fitted to or beside the meter reads the index and transmits it. At this layer you decide between battery and mains power, and whether the device should detect cover removal and tampering. For damp spots such as meter cabinets and chambers, the enclosure's IP67 rating is chosen here too.
- The network. Data reaches the centre over a cellular network (GPRS/4G or NB-IoT), a private LoRaWAN network run by the organisation, or a wired M-Bus/RS-485 line.
- The central software. It validates readings, flags missing ones, raises alerts for zero consumption or unusual spikes (using anomaly detection), and passes billing data to the billing or customer system at the end of each period.
The layer most often neglected is the fourth. Automating reading while someone still copies data into a spreadsheet leaves half the cost in place. Billing integration should be designed from day one, which is why a system integration review of how your customer system accepts data belongs at the start of the project.
Choosing the communication technology
The right choice depends on coverage, meter density and who will operate the infrastructure.
| Technology | Best suited to | Watch out for |
|---|---|---|
| GPRS / 4G | Scattered customers, existing operator coverage | Per-SIM subscription; high power draw on battery devices |
| NB-IoT | Basements, meter cabinets and other hard-to-reach points; long battery operation | Operator NB-IoT coverage must be confirmed locally |
| LoRaWAN | Dense meter areas where the organisation runs its own network | Gateway placement and maintenance fall to the organisation |
| M-Bus / RS-485 (wired) | Many meters in one building, estates and industrial zones | Requires cabling; far easier in new builds |
Cellular IoT is no longer experimental. The Ericsson Mobility Report says cellular IoT connections reached around 4.5 billion at the end of 2025, and that NB-IoT and Cat-M continue to be rolled out for low-cost devices with long battery lives. We compare power, coverage and operating models in more depth in our LoRa vs NB-IoT vs cellular guide.
The practical rule: decide with field measurements. Skip measuring signal at the five hardest meter locations in the pilot area (a basement, a metal cabinet, an underground chamber) and you risk the most expensive mistake at roll-out.
From pilot to roll-out: a six-step framework
- Define the goal in numbers. Cutting reading costs, reducing commercial losses and monitoring night-time consumption each need different reading intervals and reports. Write down how success will be measured before you start.
- Build a meter inventory. Make, model, size, age and interface are needed before any device can be chosen. Replace faulty meters first; reading a bad meter remotely just delivers bad data faster.
- Choose a representative pilot area. Not just an easy neighbourhood, but one that includes difficult coverage points. If you have a geographic information system (GIS) layer, placing meters on the map makes both the pilot and the roll-out easier; we explain how to set up that layer in our guide to GIS for municipalities.
- Set the reading interval to match the goal. Daily reads are often enough for billing; loss analysis needs hourly profiles. Higher frequency costs battery life and airtime, so make that trade-off deliberately.
- Define alerts and owners. Who receives zero-consumption, reverse-flow, tamper and spike alerts, and who acts on them within how many hours? A system that raises alerts nobody owns is soon ignored.
- Test billing transfer, then scale. Run the pilot in parallel with manual reading for at least one full billing cycle. Do not scale up until every discrepancy is explained.
The water-loss side of this framework, covering district metered areas and minimum night flow analysis, is covered in our guide to non-revenue water loss analysis.
Common mistakes
- Looking only at the device price. SIM subscriptions, battery replacement, gateway maintenance and software operation make up a large share of total cost.
- Forgetting personal data. Household consumption data is personal data under KVKK, Türkiye's data protection law (broadly comparable to the GDPR). Decide early who can access it, how long it is kept and how customers are informed; setting this up through data protection compliance consultancy is easier than fixing it later.
- Skipping tamper detection. A reader that cannot detect cover removal or magnetic interference will struggle to reveal theft.
- Leaving the field team out. Meter readers do not disappear; they move to fault finding, maintenance and theft checks. If that shift is not planned, it creates resistance.
How we deliver AMR at Digital Bridge
We treat automatic meter reading as a system designed for your site rather than a box off the shelf. Our electronics, enclosure design, embedded software and web/mobile panel come from one team (we describe the stages in our IoT product development process guide), so when something fails or needs changing, there is one party responsible.
- We start with a free technical feasibility study. We review your meter inventory, site coverage and billing system, and set out in writing which communication route makes sense.
- We design and manufacture the communication device for your site. Our AMR meter reading system uses GPRS/4G, LoRaWAN, NB-IoT or wired M-Bus/RS-485 depending on conditions on the ground. For requirements beyond that, our IoT device design and manufacturing service takes over.
- We deliver software and integration together. The management software shows the latest reading, consumption charts, device health (signal, battery, last contact) and anomaly alerts in one panel, and passes billing data to your billing system via API. Pump stations, reservoirs and other sites can join the same remote monitoring platform.
- We work in your sector's terms. For water utilities and distribution companies we shape the project through our energy and utilities solutions; for municipalities, through our public sector and municipal solutions.
- We make on-site consumption visible too. Factories and campuses that want to track electricity, water and gas per line use the same data foundation through our energy monitoring and management service.
The order is always the same: needs analysis, a written proposal setting out scope, phases and cost, a pilot, then roll-out.
Next step
You do not need a big decision to get started. Prepare your meter inventory (types, quantities, rough locations) and the name of your current billing system, then get in touch through our contact page. We will plan signal measurements in a pilot area with you and find out, with real data, which technology will actually work on your site.