Bijection for Utilities
One network record. Not a map and five spreadsheets.
Customers, meters, assets and work orders in one model, with every bill correction and field change reviewed.
- Missing readings
- Bill corrections
- Outage updates
- Planned maintenance
- Field work orders
- Move-ins
A meter reading comes in wrong, and the bill that follows is wrong too. Fixing it means checking the meter data, the billing system, the work order history and the customer’s account, each owned by a different team.
Bijection links customers, meters, readings, assets and work orders into one model. Bill corrections, field visits and outage updates become reviewed workflows, and each change is written back to the system that owns it.
Missing readings
Starts: A meter goes three cycles without a reading
- List the meters and their last actual reading.
- Schedule a field visit or ask the customer for a reading.
- The next bill waits for the reading or the visit.
Bill corrections
Starts: A customer disputes a bill
- Show the readings, tariff and previous bills.
- An agent proposes a corrected bill.
- Corrections above your limit wait for approval before billing is updated.
Outage updates
Starts: An outage is reported
- Find the customers on the affected part of the network.
- Send them the estimated restoration time by SMS.
- Update them again when the work order closes.
Planned maintenance
Starts: Work is scheduled on an asset
- Find the customers who will lose supply.
- Notify them before the work starts.
- Record the notice against each account.
Field work orders
Starts: A fault is confirmed
- Create a work order with the asset’s history attached.
- Assign it to a crew with the right skills.
- It closes when the crew reports back, and the asset record is updated.
Move-ins
Starts: A customer moves into a property
- Take a final reading for the previous occupant.
- Open the new account on the same meter.
- Both bills use the same reading.
Build your bijection.
Bring us a business process, the systems it touches, and the rules it needs to follow. We'll help you work through the first implementation.