IoT & Smart Water Companies
Smart water platforms, connected meters, sensors, analytics, and predictive maintenance for utilities and industry.
25 specialist providers · 13 countries
Qualified suppliers come to you.
Filter results
Country
Industry
Technology
Not sure where to start?
Showing 1-20 of 25
Buyer's guide
The buyer's guide to iot & smart water
IoT Smart Water Networks: Sensor Architecture, Communication Protocols, and Data Analytics
IoT smart water systems deploy networks of sensors (pressure loggers, flow meters, water quality monitors, level sensors) connected via low-power wide-area networks (LPWAN: LoRaWAN, NB-IoT, or LTE-M) or cellular (4G/5G) to cloud data platforms. LoRaWAN provides up to 10 km range at sub-GHz frequencies with battery life exceeding 10 years at 15-minute reporting intervals; NB-IoT offers better in-building penetration and guaranteed QoS but requires mobile network coverage and SIM management. Smart pressure loggers (typically 4 to 20 mA output with telemetry, accuracy plus or minus 0.25 percent full scale) enable real-time detection of pipe bursts (sudden pressure drop) and pressure transients that cause pipe fatigue and customer complaint.
Data analytics layers include: anomaly detection algorithms (comparing current readings against baseline seasonal/diurnal patterns, flagging deviations above 2 to 3 sigma); hydraulic model integration (real-time calibration using sensor data); leakage estimation (minimum night flow analysis across DMA boundaries, automated calculation of night-line leakage every 15 minutes); and predictive maintenance (machine learning models trained on historical sensor data and failure events to predict asset failure probability). Digital twin platforms from the established water-software vendors combine hydraulic models with sensor feeds for scenario simulation and operational decision support.
Smart water meter programmes (AMI - Advanced Metering Infrastructure) replace traditional bulk meter reads with continuous data (hourly or more frequent) transmitted via mesh network or cellular. Benefits: leak alert to customer (detection of continuous flow above 0.03 m3 per hr for 24 hours, indicating internal leak), demand forecasting (30-minute interval data for network pressure management), revenue assurance (eliminating estimated billing, improving debt collection), and usage insights (supporting water efficiency programmes). Smart meter unit costs: $100 to $300 per meter installed including data communications module. UK government and water regulators are requiring smart meter rollout programmes; Ofwat requires all companies to progress smart metering with targets in RIIO-PR24 price review.
Frequently asked questions
What are the main benefits of smart water metering?
Smart water meters provide continuous hourly or sub-hourly data versus quarterly manual meter reads. Key benefits: (1) Leak detection - automatic alert when continuous flow detected for 24-plus hours (typical customer-side leak savings: 10 to 15 percent of total demand in areas with ageing plumbing); (2) Demand management - real-time consumption data enables time-of-use tariffs and consumption alerts nudging behaviour change (5 to 10 percent voluntary demand reduction in pilot programmes); (3) Revenue assurance - eliminates estimated bills, identifies meter tampering and bypasses; (4) Network operations - high-resolution demand profiles improve pressure management and leakage detection; (5) Customer engagement - online portals showing hourly usage are proven to increase water efficiency awareness. UK water companies with completed smart meter programmes (Thames Water, Portsmouth Water) report 5 to 15 percent reduction in per capita consumption within 5 years of rollout.
How does IoT sensor data improve leakage management?
Traditional leakage management uses minimum night flow analysis (MNF) monthly from district meter area (DMA) boundary meters: minimum flow measured between 2 and 4 AM minus estimated legitimate night use gives an estimate of background leakage. IoT enables: (1) Continuous MNF analysis at 15-minute intervals (detecting step changes indicating new leaks within hours vs days); (2) Smart pressure loggers throughout the DMA enable real-time burst detection (pressure drop signature analysis using machine learning, distinguishing bursts from demand events); (3) Distributed noise loggers provide permanent acoustic monitoring, supplementing annual mobile leak survey programmes; (4) Machine learning anomaly detection integrating flow, pressure, and quality data identifies unusual patterns requiring investigation. Industry evidence: utilities deploying advanced IoT analytics report 20 to 40 percent reduction in time-to-detect for large leaks vs manual survey-based approaches.
What communication technology is used for smart water sensors?
Communication technology selection depends on coverage, battery life, data rate, and cost: (1) LoRaWAN (Long Range Wide Area Network): sub-GHz (868 MHz EU, 915 MHz US), range 2 to 15 km (urban to rural), battery life 10-plus years at 15-minute intervals, data rate 250 bps to 50 kbps (adequate for sensor readings), low infrastructure cost (one gateway per 10 km2 urban coverage). Used by most water utilities deploying pressure loggers. (2) NB-IoT (Narrowband IoT): cellular network (licensed spectrum), deeper building penetration than LoRa, guaranteed QoS, requires SIM and mobile operator connectivity, ongoing SIM cost $2 to $8 per device per year. (3) LTE-M: higher data rate, suitable for smart meters with large data uploads. (4) Mesh networks: 169 MHz or 2.4 GHz peer-to-peer relay, no gateway needed, suitable for dense smart meter deployments. Most smart meter networks use proprietary mesh radio from the established meter manufacturers.
How is smart water data integrated with existing SCADA systems?
Smart water sensor data is integrated with existing SCADA through data APIs and middleware platforms. Most modern IoT platforms offer REST API or MQTT protocol outputs that the major SCADA platforms can ingest via standard OPC-UA or MQTT connectors. Legacy SCADA systems without API support require middleware (a process data historian or a cloud SCADA platform) to receive IoT data and re-publish in SCADA-compatible format. Data architecture: edge devices (sensors) send data to a cloud IoT platform (a major public cloud IoT service or a utility-owned server), which performs data validation, aggregation, and anomaly detection before publishing to SCADA dashboard and hydraulic model. Data security requires: encrypted transmission (TLS 1.2 or higher), device authentication (unique certificates per device), and network segmentation (OT/IT separation per IEC 62443 for critical infrastructure).
Illustrative scenario · Municipal water distribution
A composite drawn from typical projects in this category, not a single client engagement. Figures are indicative.
- Challenge
- A regional UK water company operating a rural distribution network with 40,000 connections had a leakage rate of 28 percent of water put into supply, significantly above its Ofwat AMP8 performance commitment of 18 percent. The network had 62 DMAs, of which 40 were monitored only by quarterly manual flow surveys. Burst detection relied on customer complaints, with average time-to-detect of 3.2 days.
- Approach
- Deployed a LoRaWAN IoT pressure and flow logging network across all 62 DMAs, installing 145 pressure loggers at valve chambers and hydrant posts and upgrading 40 DMA inlet meters with continuous data telemetry. Integrated the IoT platform with the existing commercial hydraulic model via REST API for real-time minimum night flow analysis. Machine learning anomaly detection (trained on 18 months of historical data) was applied to identify step-change leakage events.
- Outcome
- Average time-to-detect for new leaks fell from 3.2 days to 6.4 hours. Leakage rate reduced from 28 percent to 19.5 percent of water put into supply in the first 18 months, within 1.5 percent of the AMP8 target. The IoT network identified 34 previously unknown active leaks in the first 90 days of operation. Total investment including platform, devices, and integration: 380,000 GBP, with estimated water savings of 1.8 ML per day.
Questions to ask shortlisted providers
5
- 01
What communication protocol and network coverage does your solution use in our specific geography, and what is the fallback for areas with poor LoRaWAN or cellular coverage?
IoT deployments in rural UK face coverage gaps for both LoRaWAN (gateway spacing) and NB-IoT (cellular). A solution that works well in urban areas may fail in the rural parts of the network where leakage rates are often highest and manual survey coverage is lowest. Ask for a coverage prediction map for your specific deployment area and confirm the fallback for areas below signal threshold (satellite IoT, additional gateway, or mesh network).
- 02
How does the platform handle sensor failure, data dropout, and battery replacement, and what is the mean time between maintenance visits per device?
IoT networks degrade over time as batteries fail, sensors drift, and radio interference increases. A platform that requires monthly site visits to maintain data quality has much higher operational cost than one designed for 5 to 10 year maintenance intervals. Ask for the mean time between failures (MTBF) for field devices, the failure detection mechanism (missing data flag), and the maintenance protocol for device replacement.
- 03
What is the latency between a step-change leakage event occurring and an alert being generated, and how has this been validated on existing deployments?
The value of IoT leak detection is directly proportional to detection speed: a 1 L per s leak detected within 4 hours wastes 14 m3, versus 276 m3 if detected after 3 days. Latency depends on reporting interval (15 minutes is standard for LoRaWAN pressure loggers), platform processing speed, and alert threshold sensitivity. Ask for case study evidence of actual detection times achieved on equivalent networks, not theoretical minimum latency.
- 04
How does the solution integrate with our hydraulic model, and does it support real-time model calibration using live sensor data?
The long-term value of an IoT network extends beyond immediate leak detection to real-time hydraulic model calibration and digital twin capability. A platform that exposes data only through a proprietary dashboard (not via open API to SCADA and hydraulic model software) creates a data silo with limited operational leverage. Confirm API compatibility with your specific hydraulic model software (whether a commercial package or EPANET) and SCADA vendor.
- 05
What data ownership, sovereignty, and cyber security arrangements apply to the sensor data collected from our network, and what is your compliance with UK NIS Regulations 2018?
Water distribution network topology, pressure zone boundaries, and operational data are classified as critical national infrastructure. UK NIS Regulations 2018 require water companies to protect operational technology data. A cloud IoT platform that stores UK water network data on non-UK servers or in multi-tenant cloud infrastructure without contractual data sovereignty protections creates regulatory compliance risk. Confirm where data is stored, who can access it, and how the platform is aligned with NCSC Cyber Assessment Framework requirements.
What drives cost in this category
4
- Network size and device density
- A 10-DMA IoT deployment with 30 pressure loggers and 10 flow meters costs 50,000 to 120,000 GBP in hardware and installation. A 60-DMA network with 150 loggers and 60 flow meter upgrades costs 250,000 to 500,000 GBP. Platform costs (cloud hosting, analytics, API integration) add 15,000 to 50,000 GBP per year as an ongoing subscription. The economic case is driven by leakage saved: 1 ML per day leakage reduction at 1.50 GBP per m3 saves 547,000 GBP per year.
- Communication infrastructure (LoRaWAN vs cellular)
- LoRaWAN requires private gateway infrastructure: 1 gateway per 2 to 10 km2 depending on terrain, at 500 to 2,000 GBP per gateway plus installation. Coverage of a 500 km2 rural network may require 50 to 250 gateways at 25,000 to 500,000 GBP. NB-IoT uses existing cellular infrastructure (no gateway cost) but incurs ongoing SIM costs (3 to 8 GBP per device per year) and depends on mobile operator coverage. For large rural networks, LoRaWAN private infrastructure typically achieves lower total communication cost over a 7-year horizon.
- Integration with existing systems
- Integrating IoT data with an existing hydraulic model (via REST API, data mapping, and model calibration workflow) costs 20,000 to 80,000 GBP in implementation depending on model complexity and data architecture. SCADA integration (MQTT or OPC-UA connector, alarm configuration, dashboard development) adds 15,000 to 50,000 GBP. Off-the-shelf platforms with pre-built connectors for the leading hydraulic modelling packages and SCADA vendors reduce integration cost by 30 to 50 percent versus bespoke development.
- Leakage reduction achieved versus Ofwat performance commitment
- Ofwat AMP8 ODI (Output Delivery Incentive) penalties for leakage above commitment are calculated as a percentage of Regulatory Capital Value per ML per day above target. For a company with 15 ML per day excess leakage versus commitment, the ODI penalty can reach 5 to 15 million GBP per year. An IoT deployment that reduces leakage by 3 ML per day (achievable on a well-designed network within 18 months) avoids 1 to 5 million GBP per year in ODI penalties, dwarfing the capital cost of the deployment.
Key regulations and standards
4
- UK NIS Regulations 2018: Critical Infrastructure Cyber Security
- The Network and Information Systems (NIS) Regulations 2018 implement the EU NIS Directive in the UK. Water companies serving above 50,000 connections are classified as Operators of Essential Services (OES) and must implement appropriate security measures for network and information systems (including OT/SCADA and IoT platforms). The NCSC Cyber Assessment Framework (CAF) is the accepted methodology for demonstrating compliance. IoT platforms handling water network operational data must be assessed against CAF objectives for data security, system protection, and incident detection.
- Ofwat AMP8 Leakage Performance Commitments and ODI Regime
- Ofwat's PR24 Final Determination sets binding leakage reduction performance commitments for each water company in AMP8 (2025 to 2030). Output Delivery Incentives apply financial penalties for leakage above commitment at a rate specified per ML per day per year. IoT-based leakage detection and active pressure management are the primary technologies enabling the step-change leakage reductions required by AMP8. Ofwat's guidance explicitly recognises IoT and advanced metering as enabling technologies for the required performance improvement.
- Water Industry Act 1991 and Smart Metering Requirements
- Ofwat's methodology for AMP8 requires water companies to develop and submit smart metering rollout programmes. The Water Industry Act 1991 framework requires companies to improve their efficiency in the use of water, which is interpreted to include smart meter rollout. The UK Smart Metering Implementation Programme (for gas and electricity) and Ofwat's metering guidance are driving convergence toward AMI (Advanced Metering Infrastructure) standards for interoperability and data format.
- GDPR and Data Protection Act 2018: Smart Meter Customer Data
- Smart water meters collect hourly or sub-hourly household consumption data, which may be considered personal data under GDPR if it can identify individual behaviour patterns. Water companies operating smart meter programmes must conduct Data Protection Impact Assessments (DPIAs), establish lawful processing bases (legitimate interest or public task under WIA 1991), and implement data minimisation and retention policies. Customer consent for behavioural analytics (beyond basic billing and leak detection) should be obtained explicitly.