Leak and loss localisation
District inflow is balanced against downstream meters and minimum night flow is tracked per zone. Persistent gaps narrow a loss to a segment or a single meter.
Utilities & Metering
Consumption measured monthly is managed monthly.
Continuous flow, pressure and consumption monitoring across distributed infrastructure, so losses are located and crews are sent to a street rather than a district.
- Built for
- Network, operations and revenue teams
- Connects
- Meters, flow, pressure and SCADA
- Deploys
- Sovereign cloud, private cloud or on-site
/ The shift /
What happens today, and what changes.
Flip between the operation as it runs now and the operation once the data is joined up.
- 01Losses appear on an invoice, a month after they started.
- 02Crews are dispatched to search, so field time goes on finding the fault.
- 03Consumption arrives as a total, not a pattern, which makes forecasting, tariffing and tenant billing an argument.
/ How it works /
From signal to decision in four moves.
Each step runs on the shared IoT Cube foundation, so nothing here is a separate system to maintain.
- 1
Read every meter remotely
Smart meters, pulse retrofits, flow and pressure sensors report over low-power networks or cellular, including unpowered sites.
- 2
Place readings on the network
Each meter is linked to its district, site, tenant and GIS location, so consumption can be balanced zone by zone.
- 3
Locate the abnormal
Night flow, inflow-versus-billed balance and pressure patterns separate loss from normal demand.
- 4
Send crews to a place
A field job carries the segment, meter and readings, and closes back into the record on repair.
/ What you get /
What utilities & metering gives you.
Remote metering on unmanned sites
Battery-powered endpoints report over LoRaWAN or NB-IoT on a set schedule. Missing reads, tamper flags and low battery raise their own alerts.
Pressure, flow and quality monitoring
Pressure, flow and water-quality sensors are sampled continuously. Transients, low-pressure events and out-of-range readings alert with their location.
Consumption analytics and profiles
Interval reads build daily and seasonal profiles by site, tenant and process, and abnormal usage is flagged against that profile.
Field dispatch with location attached
Confirmed alarms create work orders with coordinates, asset and readings, and the outcome is recorded on close.
Regulator, tenant and internal reports
Consumption, losses, incidents and meter performance are reported per period and audience, from tenant statements to internal loss reviews.
/ Use cases /
Where teams put it to work first.
Locate network leakage
Balance district inflow against downstream meters and night flow, then narrow a loss to a segment before crews leave.
Read unmanned sites remotely
Bring meters on remote and unpowered sites onto low-power networks, with alerts for missing reads and tamper.
Bill tenants from actual reads
Give each tenant or process its own consumption profile, so statements rest on measured use.
Dispatch crews to a location
Raise field jobs with coordinates, meter and readings, and close the outcome back into the network record.
/ Benefits by team /
Every team gets a different answer from the same record.
01
Network operations
Losses are placed on the network within hours, so engineers work from a location.
02
Revenue
Silent, stuck and tampered meters are identified automatically, so billing works from known reads and known gaps.
03
Field teams
Crews arrive at a located problem with the readings attached.
04
IT
Validated reads flow to billing, CIS and GIS by API or scheduled file, across mixed meter protocols.
/ In practice /
Three moments from a working week.
Each one starts with a signal and ends with someone acting on it. The scenarios are illustrative.
The signal
Minimum night flow in a district metered area in north Riyadh rises and stays high for three nights.
- 1
The platform flags the sustained rise against that district’s night-flow profile.
- 2
The network engineer compares pressure data and narrows the loss to one street segment.
- 3
A crew is dispatched to the segment with the location and readings.
The outcome
The crew goes to a street, not a district.
/ Technology /
Four layers. One record underneath.
Device-neutral at the bottom, open at the top, and sovereign all the way through.
01
Devices in the field
Keep the hardware you already have
- Smart water, gas and electricity meters
- Flow and pressure sensors
- Pulse and Modbus retrofits
- LoRaWAN and NB-IoT endpoints
- Pumps and valves
02
Connectivity & protocols
Any carrier, any protocol
- DLMS/COSEM
- Modbus TCP / RTU
- M-Bus
- LoRaWAN
- NB-IoT / LTE-M
- LwM2M
- MQTT
- 4G/5G via any Saudi carrier
03
IoT Cube platform
Sovereign, multi-tenant, AI-neutral
- Device registry & OTA
- Time-series store
- Geospatial engine
- Rules & alerting engine
- Workflow automation
- Reporting & exports
04
Your systems of record
Data lands where decisions are made
- Billing
- CIS
- GIS
- SCADA
- Work management
A utility moved from monthly reads to continuous monitoring and turned an estimated loss figure into a located one, which changed how crews were dispatched.
Story pending customer confirmation/ What you measure /
The numbers this produces.
Measured continuously, per asset, per site and per contract.
Non-revenue water
Volume entering the network that is not billed, by district metered area and period.
Minimum night flow
Lowest flow into a zone during night hours, used as a leakage indicator.
Read success rate
Share of meters delivering a valid read within their reporting window.
Time to locate
Time from a loss or leak alert to a confirmed location in the field.
Pressure compliance
Time each zone spends inside its target pressure band.
Consumption by segment
Usage by site, tenant, process and period, compared with its own profile.
/ Rollout /
Start with one decision. Scale what works.
- Phase 1
Map the network and meters
We review meter types, protocols, coverage, GIS data and billing flows, and pick the districts where losses are least understood.
- Phase 2
Meter a pilot district
Bulk and customer meters in one district are connected, with inflow, pressure and GIS locations brought into the same model.
- Phase 3
Prove a located loss
Night-flow and balance alerts are followed into the field until crews confirm leaks where the platform placed them.
- Phase 4
Extend district by district
More districts, meter types and billing integrations join the same model, one district metered area at a time.
/ Security & sovereignty /
Where your data lives, and who can reach it.
- In-Kingdom residency
- Built to national controls
- Isolated by tenant
- Your cloud or site
/ Built on IoT Cube /
Products already doing this.
Each one runs this solution on the shared foundation.
/ Industries /
Where this solution shows up.
/ Questions /
Frequently asked.
Often not. Pulse outputs and retrofit modules bring existing mechanical meters onto the platform unchanged.
/ Explore more /
Other solutions on the same foundation.
See utilities & metering on your own assets.
Bring the hardware you already run. We will connect a sample of it and show you the operating picture it produces.