Water tank level monitoring is a system that continuously measures the water height in a tank or reservoir and shows it as litres or cubic metres on one central screen. It alerts the right person before overflow, when the level falls below a critical point or when the tank empties unusually fast, so problems surface before complaints do.
How tanks are still checked today
Municipal reservoirs, factory process and fire water tanks, break tanks in hospitals and residential blocks, and farm irrigation ponds all raise one question: how much water is in there right now? Often the answer still comes from a technician climbing a ladder, or from a float gauge on the tank wall, read once a day at best and rarely recorded.
So problems show up at the worst moment. A fill pump fails to stop and the tank overflows until morning; a burst main drains a reservoir and the first to notice is a neighbourhood without water. A fire water tank that has dropped below its required reserve is often only noticed during an inspection.
The cost of not monitoring tank levels
Not knowing a tank's level wastes water and energy, and losses in Türkiye's drinking water networks remain significant:
According to the Urban Water Efficiency page of the General Directorate of Water Management at 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. The ministry notes that loss rates in developed countries range from 8% to 24%.
The same page recommends wider use of remote monitoring and minimum night flow analysis. Reservoir level is a cheap input: a tank draining faster than expected at night points to leakage in the zone it feeds. We explain how losses are broken down zone by zone in our guide to water loss analysis.
Power cuts hit tanks directly too. According to TEDAŞ's 2024 Türkiye Electricity Distribution Sector Report, the average unplanned interruption duration per user in Türkiye was 1,099 minutes in 2024. While the power is out the fill pump stops, and an operator without remote level data cannot tell how many hours of supply remain.
Choosing the right level sensor
Accuracy depends largely on the sensor, chosen according to tank material and height, water quality, condensation and available power:
| Sensor type | How it measures | Strength | Watch out for |
|---|---|---|---|
| Ultrasonic | Sends a sound pulse down from the roof and times the echo | Non-contact, easy to fit | Condensation, foam and false echoes in narrow hatches |
| Radar | Measures distance with a microwave signal | Little affected by vapour, temperature or condensation | Higher upfront cost; mounting angle matters |
| Hydrostatic (pressure) | Calculates height from water pressure at the tank floor | Reliable in closed, low or buried tanks | Submerged; cable and sealing must be robust |
| Float / level switch | Opens or closes a contact at a set height | Simple and cheap; ideal as a pump interlock | Gives a threshold only, not a continuous value |
| Capacitive | Measures capacitance change along a probe | Practical in small tanks and process vessels | Scale and fouling can cause drift |
Most sites do best with two layers: a continuous analogue sensor plus an independent high/low level switch that still protects the pump if the sensor fails. For outdoor tanks, our guide to IP65 and IP67 ratings explains how to protect the sensor and logger enclosure against moisture and dust.
From level to volume: calibration and data quality
A sensor measures centimetres; operators think in cubic metres. In horizontal cylinders, spheres or irregular concrete reservoirs, level and volume are not linear. For these, build a strapping table from the design drawings or from readings taken during a controlled fill.
Subtract what you cannot use: the blind zone below the sensor, the dead volume under the pump suction and the fire reserve. Otherwise a tank that looks full on screen may hold only a few hours of usable supply.
Three rules keep the data trustworthy: average over a short window to smooth out sloshing, timestamp readings on the device, and buffer them when the link drops. Our article on time-series databases for sensor data covers how to store and query long runs of level history.
Connectivity and power: decide on site
For a tank on a powered site, a wired link or an existing PLC is the simplest route. Hilltop reservoirs, rural tanks and farm ponds often lack mains power and coverage, which is where battery-powered devices that report infrequently fit. If a farm pond is monitored alongside the irrigation schedule, our guide to irrigation monitoring with IoT covers that side.
According to the LoRa Alliance, LoRaWAN is an ITU-approved standard designed for ranges of up to 15 km in rural areas and battery life of more than 10 years. On the cellular side, the Ericsson Mobility Report says cellular IoT connections reached around 4.5 billion at the end of 2025, with long-battery-life technologies such as NB-IoT and Cat-M still being rolled out. Our comparison of LoRa, NB-IoT and cellular helps you decide which fits your sites, and if you choose LoRaWAN, our LoRaWAN gateway guide covers where to place the gateway that serves several tanks.
Reporting frequency drives battery life: hourly readings usually suffice, with the device reporting faster when the level moves quickly or nears a threshold.
Seven steps to set up water tank level monitoring
- List your tanks. Record each tank's location, type, capacity, the zone or process it serves, its fill and outlet arrangement, and available power in one list.
- Write down the question for each tank. "Is it overflowing?", "How many hours of water are left?", "Why does it drain at night?", "Is the fire reserve intact?" The question decides the sensor and the alarm.
- Choose the sensor and mounting point. Pick the analogue sensor, add a level switch where needed, and mount away from the inlet and turbulence.
- Measure signal and power on site. Check signal strength at the tank itself, then choose battery, mains or a small solar panel.
- Calibrate. Define the strapping table, dead volume, blind zone and reserve, and compare the sensor against manual dips during the first week.
- Write alarm and reporting rules. Which threshold goes to whom, through which channel; who is on call out of hours; which events belong in the daily report?
- Pilot, then roll out. Start with two or three problem tanks, tune thresholds on a month of data, then add the rest.
Alarm design: which rule catches what?
A single "low level" alarm is not enough, because different events leave different signatures. This checklist is a good starting point:
| Alarm rule | What it catches | Who gets it? |
|---|---|---|
| High level (pre-overflow) | Fill pump or valve failed to close | On-call operator, immediately |
| Critical low level | Zone or process about to run dry | On-call operator and unit manager, immediately |
| Abnormal drain rate | Burst main, open valve, leakage | On-call operator immediately, plus daily report |
| Expected refill missing | Pump did not restart after a power cut, supply fault | Pump station lead |
| Below fire reserve | Fire water used, or a leak | Health and safety lead and facility manager |
| No data | Device, battery or link problem | Technical team, delayed |
Give each rule a short delay so ripples do not trigger alarms, and log who acknowledged each one. To catch unusual drain behaviour without fixed thresholds, models that learn normal patterns are covered in our anomaly detection guide.
Pumps usually start and stop on reservoir level; we cover monitoring both together in remote pump station monitoring. Break tanks and fire water tanks in buildings are usually brought into the building management system (BMS).
How we deliver this at Digital Bridge
One team handles everything from sensor to dashboard: electronics, enclosures, firmware and web and mobile panels.
- Discovery and needs analysis. We survey your tanks, existing sensors and PLCs, power and connectivity on site. Site assessments for Industry 4.0 projects are free; scope, phases and price are set out in a written proposal.
- Field device. Where an off-the-shelf device does not suit the site, our device manufacturing and IoT team designs a battery-powered or panel-mounted logger, with a free technical feasibility check. Our IoT device development process article walks through how custom devices are built.
- Pilot. We start with two or three tanks and tune calibration and alarm thresholds with your team, based on real data from the first weeks.
- Central monitoring. Readings are collected on our subscription-based remote monitoring platform with map view, alarm rules and mobile notifications, with no server to install. If you already run a control room, or tanks need to be managed together with pumps and valves, we build custom SCADA and HMI software; with custom SCADA the source code belongs to you and there are no extra licence fees.
- Integration. Our energy and utilities solutions combine level data with meter reading and loss analysis, our public sector and municipal solutions serve water utilities, and our smart building (BMS) integration brings the same data into building screens. To see tanks on the same map as pipes and valves, read about GIS for water utilities.
We serve every province of Türkiye, remotely and on site, with 24/7 technical support. For what to look for in a platform, read our guide to an IoT platform for remote monitoring; for the central software side, see what SCADA is.
Next step
Pick your three most troublesome tanks and note each one's type, capacity, recent overflow or run-dry incidents, and on-site power and coverage. Then get in touch with us and we will work out together which sensor, connectivity and alarm setup will deliver results fastest. More guides on sensors, connectivity and field hardware are on our IoT & Hardware page.