Keep the meter, supply point and dated occupancy in one history. Preserve the readings when meters change, and give communication failures, inspection dates and unusual usage a place to be investigated.
See who occupied the service point and when.
Record the old meter’s final and new meter’s opening readings.
Acknowledge an event, resolve it or link it to a work order.
Meters are replaced. Occupants move. A spreadsheet rarely preserves the whole sequence.
It is difficult to establish who was responsible for the supply on a particular date.
Store occupancy periods against the service point and reject overlapping periods.
Closing and opening readings are stored in different files.
Keep the removed meter’s record and final reading alongside the replacement’s opening details.
Silence is discovered after the gap has already affected the record.
Scheduled checks open events for stale devices and approaching inspection dates.
A suspicious reading is noted, but never linked to an investigation.
Review register regression and unusual-use events, record a resolution or create a linked work order.
See how a meter and its faults stay tied to one service point in Imara Nexus.
Scheduled checks open events when a device stops communicating or an inspection date approaches. Register readings that move backwards, or show usage well above their recent median, join the same queue.
Explore it in your workspaceReview the event beside its meter, service point, source and the readings that raised it. Record how it was resolved, or have a manager create a linked work order. The original event stays in the history.
Explore it in your workspaceRecorded in Imara Nexus with sample data: the meters, service points and meter events are sample entries. Dropdown choices step through their options without opening the list. No meter is installed and no work order is created.
Follow one service point through installation, readings and a fault investigation.
Give the supply location a permanent code and record its occupancy dates.
Link its serial number, opening reading, seal and inspection date to the point.
Capture readings against the meter, with connected devices posting through the telemetry API.
Check an unusual-use or communication event alongside the installation record.
Record the resolution or create a linked work order. Keep the original event in the history.
No. It maintains meter and service-point records, readings and fault history for use alongside your billing process.
Record the end of one occupancy and the beginning of the next. Overlapping periods are rejected.
It detects unusual use, register regression, communication gaps and inspection dates. Leak or tamper events can also arrive from your gateway.
Yes. An authorised user can create a linked work order from the event.
Tell us where installation, occupancy and reading records diverge. Discuss the history and fault workflow you need around one supply point.
Prefer to explore first? Start a core-platform trial. Specialist workflows are enabled and configured separately.