Use cases
Situations,
not case studies.
We do not publish client names, sites or sectors, and we will not start. These are the failures the instruments are specified against — and what each one looks like while it is happening.
Situations
Agriculture · Water
A pump runs dry overnight
Nobody knows until someone is standing there in the morning. A level sensor and a run-state input turn that into a reading with a time on it.
Energy
A generator does not change over
The site is dark and the first anyone hears is a phone call. Changeover state is one digital input.
Water
A tank drains between visits
Consumption looks normal on a monthly reading and abnormal on a continuous one. The step is visible the day it happens.
RTUs & Gateways
A remote site cannot be reached
Where there is no line, the gateway holds readings and forwards them when the link returns, with their original times intact.
The simulations are illustrations built from synthetic values, not readings from any customer site. They show the shape of each failure, which is the part worth recognising. References are given on request with the client’s written permission.
Energy mesh metering
About RF Mesh AMI.
Electricity and water meters on the same RF mesh, each one also a repeater for the meters around it. A cluster needs one backhaul, not a modem per meter — and when a neighbour goes, the meters behind it re-form the route themselves instead of going quiet.
01
Meter mesh
Electricity and water meters, each one also a repeater for the meters around it.
02
Concentrator
One per cluster. It gathers the mesh and carries it out over a single 868 MHz backhaul.
03
Head-end system
Talks to the meters: scheduled reads, events and alarms, firmware and keys, comms health.
04
Meter data management
Decides what is a good reading before anything downstream sees it, and keeps the interval history behind every figure.
The head end and the meter data management system are ours: built here and run in our cloud, alongside Telemetry-X. Readings go out to your billing engine, ERP or SCADA over an API.
What is fitted, how often it is read and which functions are enabled are decided at survey and written into the scope. We do not publish client names, sites or meter counts.