Leak and loss localisation
District inflow is balanced against the sum of downstream meters, and minimum night flow is tracked per zone. Persistent gaps narrow a loss to a district, segment or single meter.
Utilities & Metering
Consumption measured monthly is managed monthly.
Continuous flow, pressure and consumption monitoring across distributed infrastructure — so losses are located, demand is understood, and crews are sent to a problem 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 is actually happening 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 number that says something went wrong somewhere, last month.
- 02Crews are dispatched to search.
Field time is spent finding the problem rather than fixing it.
- 03Consumption is 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 unmanned and 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 genuine loss and leakage from normal demand.
- 4
Send crews to a place
A field job is raised with the segment, meter and evidence attached, and closed back into the record when the fix is done.
/ What you get /
Capability, not just visibility.
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 quality readings trigger alerts tied to their location.
Consumption analytics and profiles
Interval reads build daily and seasonal profiles by site, tenant and process. Abnormal usage is flagged against that profile rather than a fixed limit.
Field dispatch with location attached
Confirmed alarms create work orders in your work management system 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 battery-powered 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 are based on measured use rather than estimates.
Dispatch crews to a location
Raise field jobs with coordinates, meter and readings attached, 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 instead of a monthly balance.
02
Revenue
Silent, stuck and tampered meters are identified automatically, and billing works from known reads and known gaps.
03
Field teams
Crews arrive at a located problem with the evidence, and spend their time fixing rather than searching.
04
IT
Validated reads flow to billing, CIS and GIS through APIs or scheduled files, across mixed meter brands and protocols.
/ In practice /
What it looks like on an ordinary Tuesday.
Three moments where the platform earns its place. 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 — changing how crews were dispatched.
Story pending customer confirmation/ What you measure /
Numbers that replace arguments.
The indicators this solution produces 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 districts or sites 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 on the same model. Weeks, not quarters, per wave.
/ Security & sovereignty /
Sovereign is a place, not a promise.
In-Kingdom residency
Data stored and processed inside Saudi Arabia, on infrastructure you can name in a tender.
Built to national controls
Designed to align with NCA cybersecurity controls and the Personal Data Protection Law.
Isolated by tenant
Tenant isolation, role-based access and a full audit trail across users, actions and devices.
Your cloud or site
Deploy into a sovereign cloud, your private cloud or on-premises without becoming a different product.
/ Built on IoT Cube /
Runs on the platform, not beside it.
Products already running this solution on the shared foundation.
/ Industries /
Where this solution shows up.
/ Questions /
Frequently asked.
Do we have to replace our meters?
Often not. Pulse outputs and retrofit modules bring existing meters onto the platform.
What about sites with no power or coverage?
Battery endpoints and low-power networks are standard for exactly this.
Can tenants see their own consumption?
Yes, multi-tenancy is native to the platform rather than bolted on.
Does it integrate with our billing, CIS and GIS?
Yes. Validated reads go to billing and CIS, alarms and losses are placed on your GIS network model, and field jobs go to work management — through APIs, webhooks or scheduled files.
Which meter protocols do you support?
DLMS/COSEM, Modbus, M-Bus and pulse outputs are common starting points, over LoRaWAN, NB-IoT or cellular. If a meter speaks something else, we test it before we commit.
Can it produce reporting for the utility regulator?
The continuous record of consumption, losses and incidents is there to report from. Tell us the submissions you make to the utility regulator and we will map the reports to them.
/ Explore more /
Other solutions on the same foundation.
Fleet & Asset Operations
Know where assets are, how they are performing, and where attention is needed.
Cold Chain & Compliance
Monitor conditions continuously and create the operational record while products move.
Driver Safety & Journey Management
Connect journeys, behaviour, safety events and operational response.
Bring us the decision that takes too long today.
Start with the problem. IoT Cube provides the foundation underneath.