Early warning
See the fault before the customer calls
Why period end is too late
A period close usually runs long not because of the reading but because of when the gap is noticed. A modem fault that surfaces at month end forces that whole month to be estimated.
Request a demoEarly warning
What the system watches
A modem has gone quiet
Last-seen time is recorded for every device. A modem that misses its expected window rises to the top of the list, and you can tell whether the problem is in the building or on the network before going out.
M-Bus line voltage dropped
Line voltage is tracked in the panel. A drop usually means a short on the line, a loose terminal or an overloaded bus.
A meter is not answering
Meters that do not respond during a run are listed with the reason. Whether one flat went quiet or a whole branch did is clear at a glance.
The meter reports its own fault
A telegram carries more than the index: the device's own error code and battery state are read too. When a meter reports its own fault, it goes on record.
The index never moves
An index that stays flat for a long time can mean a closed valve, a removed meter or a stopped mechanism. Those meters are collected in a separate list.
Consumption looks wrong
Values below the previous index, sudden jumps and readings above the limit are flagged. In those cases the field app makes a photo mandatory.
Early warning
From warning to closure
The reading run ends and unresponsive meters and silent modems are listed.
The warning appears with its reason: line voltage, device error code or a flat index.
If needed a re-read runs from the same screen; if the problem persists a work order opens.
The work order is assigned to a field technician and appears on their phone.
The field record closes with a photo and a note, and the result joins the fault's history.
At period close, the statement shows which unit was estimated and why.
Early warning
What this gives the business
Fewer estimated units
When a fault is fixed within the period, that unit is billed on its real consumption. Estimation is the most common cause of disputes.
Field visits become planned
Several jobs in the same building are combined into one visit; planned routes replace emergency call-outs.
The conversation changes
The site management does not report the fault to you — you inform them. The direction of the relationship reverses.
No surprises at period close
Instead of a pile of gaps appearing at month end, a short list has been worked down day by day.
Questions
See the fault before the customer calls
Do warnings arrive as notifications too?
Yes. With notification automation, defined conditions can be sent by e-mail and SMS, and who receives which warning is set per role.
Is meter data lost while a modem is offline?
No. Pending readings are sent once the connection returns, so the archive has no gap. The length of the outage is visible from last-seen.
How is an abnormal consumption warning decided?
Values below the previous index, sudden jumps and readings above the limit are flagged. Thresholds are set per project — consumption patterns are not the same on every site.
What if a warning is not worth a site visit?
The warning can be closed with its reason recorded. When the same meter warns again its history is visible, so recurring problems stand out.
Let's look at how many of your meters are silent
Request a demo to see the unread-meter rate and modem status across your current projects; we will work through an example on your own data.