What Installing a Water Monitoring System Actually Involves, From Site Survey to Handover
TL;DR: A water monitoring system goes from first conversation to live dashboards in six stages: scoping, a site survey, connectivity design, installation, commissioning of alerts and dashboards, and training with handover. For a single point it is often one site visit; for AQUAIOT, first contact to live data typically takes two to four weeks. Most of the work that decides whether it succeeds happens before and after installation day, not during it.
Last updated: 28 September 2026
On this page
Key takeaways
- A water monitoring system deployment runs in six stages: scope, survey, connectivity design, installation, commissioning and handover.
- For AQUAIOT, first contact to live dashboards typically takes two to four weeks, and most single-point installations need one site visit.
- HSE says that wherever possible you should avoid carrying out tasks in confined spaces, which shapes how chamber sensors are fitted.
- LoRaWAN is a low power, wide area specification for battery-operated devices, with range of up to 15 km in rural areas according to the LoRa Alliance.
- Alerts need a baseline: a week or two of normal data before thresholds are tightened avoids a flood of false alarms.
- Large estates usually start with one pilot site, prove the value, then phase the rest by risk.
How does a water monitoring system go from enquiry to live data?
A water monitoring system goes live in six stages: agree what needs watching and why, survey the site, design how each sensor will connect, install, commission the dashboards and alerts, then train the people who will act on them. The hardware is the quick part. Scoping and commissioning decide whether the data gets used.
The timescale depends mostly on access. AQUAIOT’s clamp-on flow deployments, for example, typically run two to four weeks from first contact to live dashboards, depending on site access and survey scheduling, and most single-point installations are finished in one site visit. Multi-site programmes are planned and phased.
The first conversation is about outcomes, not sensors. Which failure would hurt most: a flooded plant room, a failed Legionella record, a blocked drain, a leak on a buried main? The answer decides where the first sensors go and who receives the first alert.
What happens at the site survey?
The site survey for a water monitoring system confirms that each proposed sensor can be fitted, powered, reached safely and connected. Engineers check pipe materials, sizes and access for flow meters, chamber depths and covers for level sensors, the locations of plant rooms and risers, and radio signal at every point. The survey is also where a proposal becomes a firm specification.
For flow, the detail is the pipe itself: outside diameter, wall thickness, material and a straight run long enough for an accurate reading. For level, it is the chamber: depth, cover type, whether the atmosphere could be hazardous, and whether the sensor can be mounted without anyone going in.
Safe access shapes the design. HSE describes a confined space as one that is enclosed or largely enclosed and has a reasonably foreseeable risk of fire, explosion, loss of consciousness, asphyxiation or drowning, and says that wherever possible you should avoid carrying out tasks in confined spaces. Many manholes, wet wells and tanks fit that description, so a good design mounts sensors from the opening wherever it can.
At AQUAIOT the survey carries no commitment. Its output is a list of points, the sensor for each, the connectivity route and anything the site needs to prepare, such as a key for a locked chamber or a permit for a plant room.
How is connectivity chosen?
Connectivity for a water monitoring system is chosen point by point from three options: LoRaWAN radio to a gateway, cellular 4G direct to the cloud, or a wired RS485 and Modbus link into an existing building management or SCADA system. The choice depends on how many sensors are close together, how deep underground they sit, and what systems the data needs to reach.
LoRaWAN suits many sensors spread across one site. The LoRa Alliance describes it as a low power, wide area networking specification designed to connect battery-operated devices, with bi-directional communication and end-to-end security, and range of up to 15 km in rural areas. A single gateway can often cover a campus, and battery-powered sensors can last for years.
Cellular suits isolated points with no gateway nearby, such as a single pumping station or a river level site. Wired links suit plant rooms where a BMS is already the control system. Our guide to LoRaWAN or cellular for water monitoring compares the two.
Security is part of a water monitoring system’s design, not an afterthought. AQUAIOT telemetry uses encrypted payloads and supports over-the-air configuration and firmware updates. Councils deploying sensors in public spaces will also find the National Cyber Security Centre’s connected places cyber security principles a useful checklist for systems that collect data through sensors and IoT devices.
What happens on installation day?
Installing a water monitoring system is usually quick because the design work is already done. Clamp-on flow meters strap to the outside of live pipes, level sensors mount under chamber covers, leak sensors sit on the floors they protect, and each device is registered to the platform and checked for signal before the engineer leaves. Nothing needs to be shut down.
The details differ by sensor. A clamp-on ultrasonic flow meter is fitted with the system live and under pressure, with no cutting, tapping or isolation. A radar level sensor is fixed below the cover and aimed at the water. A leak sensor goes where water would appear first, beside a tank, under a calorifier or at the low point of a plant room floor.
Every point in the water monitoring system is tested before the engineer leaves: the device reports, the reading makes sense, and the reading appears in the right place on the dashboard.
How are alerts and dashboards set up?
Alerts and dashboards for a water monitoring system are set up in two passes. The first pass applies sensible default thresholds and routes alerts to named people by role. After a week or two of real data, the second pass tightens thresholds around each point’s normal behaviour, so alerts mean something when they arrive.
Baselining matters more than any setting. A steady night flow that is normal for a hospital would be alarming in an empty office. A chamber that fills every time it rains is healthy; one that fills in dry weather is not. Without a baseline, a water monitoring system either misses faults or sends so many alerts that people stop reading them.
Routing is the other half. Each alert should reach someone who can act, by SMS, email or app, with an escalation if nobody acknowledges it. Our guide to water alarm escalation covers who should receive what, and when.
Integration closes the loop. Data can flow into an existing BMS or SCADA system over RS485 and Modbus, or into CAFM and analytics tools through open APIs, so the water monitoring system works alongside the tools a team already uses. See our guide to BMS water monitoring.
What does training and handover cover?
Training on a new water monitoring system covers what each person sees, what to do when an alert arrives, and how to pull reports. Handover leaves the site with a list of every sensor and its location, the alert rules and who receives them, and a named contact for support. The aim is a team that trusts the system enough to act on it.
Role-based dashboards help. An estates manager wants a map of every site. A duty holder wants temperature records for the Legionella log. A maintenance supervisor wants today’s alerts and nothing else. Setting those views up during handover, rather than after the first missed alert, is what keeps a water monitoring system in daily use.
Support continues after go-live. Firmware and configuration can be updated over the air, thresholds are revisited as the site changes, and new points can be added as the programme grows.
How do you roll out across a large estate?
Roll out a water monitoring system across a large estate by starting small and spreading by risk. A pilot on one building or one type of asset proves the data is useful, shows the savings or avoided incidents, and builds the case for the next phase. The later phases then reuse the same gateways, dashboards and alert rules.
A typical order is to start with the assets where failure is most expensive or most visible, such as plant rooms above occupied floors, drainage that has flooded before, or tanks under Legionella control, then widen to leakage zones and water quality. Our guide to multi-site water monitoring covers how to compare sites once they are all connected.
The full AQUAIOT deployment capability stack
Every layer of an AQUAIOT water monitoring system uses the same survey, connectivity, dashboards and alert routing, which is why a first deployment makes every later one quicker.
Level in chambers, tanks and rivers
The AQUAIOT Radar measures level without contact using 60 GHz radar, accurate to within 2 mm, with ATEX variants for hazardous environments.
Flow on live pipes
The clamp-on ultrasonic flow meter covers pipes from DN8 to DN100 and installs without cutting or shutdown.
Leaks inside buildings
A leak sensor triggers the moment water touches its sensing membrane, runs on LoRaWAN and lasts up to 10 years on battery.
Rainwater and surface water
The AQUAIOT Smart Water Butt retrofits to standard collectors in typically under 30 minutes per unit and releases stored water ahead of forecast rain.
Water quality
The iSPA-T and iSPS-X bring multi-parameter water quality readings into the same platform.
Platform and delivery
The AQUAIOT Cloud provides role-based dashboards, alarms, trendlines and exports, and AQUAIOT engineers deliver the survey, installation, cloud configuration, alert routing and training themselves.
Frequently asked questions
How long does it take to install a water monitoring system?
Installing a single sensor usually takes one site visit. For AQUAIOT deployments, the full journey from first contact to live dashboards typically runs two to four weeks, depending on site access and survey scheduling. Estate-wide programmes are phased over longer periods, site by site.
Do you need to shut off the water to install monitoring?
Usually not, because most parts of a water monitoring system fit around live services. Clamp-on flow meters strap to the outside of live pipes with no cutting or isolation, radar level sensors mount above the water, and leak sensors sit on floors. A shutdown is only needed if a site chooses a meter that has to be cut into the pipe.
Does a water monitoring system need Wi-Fi?
No. A water monitoring system normally connects over LoRaWAN radio to a gateway, over cellular 4G, or by a wired RS485 and Modbus link to an existing building system. Site Wi-Fi is optional, which keeps the monitoring separate from the corporate network.
Is sensor installation in manholes a confined space task?
It can be. HSE defines a confined space as enclosed or largely enclosed with a reasonably foreseeable risk such as asphyxiation or drowning, and says tasks in confined spaces should be avoided wherever possible. Sensors that mount from the opening, such as radar under a cover, help avoid entry.
What happens after a water monitoring system goes live?
After go-live, thresholds are tuned against a week or two of normal data, alerts are routed to named people by role, and the team is trained on dashboards and reports. Firmware and settings can be updated over the air, and new points can be added as the programme expands.
Where to start
Start with one question: which water failure would cost your organisation the most this year? Put the first part of your water monitoring system there, learn from the data, and let the results decide the next phase.
To plan a first deployment, tell us about your site and a UK engineer will come back within one working day with a survey proposal and no commitment.