Assets & infrastructure
Networks operated, not just owned
Water and sewerage, district heating, waste collection and public lighting, from the network record to the customer who reports a fault.
Why it matters
An outage you can explain
Utility work is asset work with customers attached. The same platform holds the network, the planned and reactive jobs on it, the readings that show how it behaves, and the service requests from the people it serves — which is what makes an outage explainable.
The network and the jobs on it
Planned and reactive work sit on the same asset.
Readings that show behaviour
Measurement is part of the operational record.
Requests from the people served
What customers report belongs to the same file as the fault.
What it covers
The network, the work and the customer
Six records that together explain what the network did and who it affected.
Network records
Pipes, cables, chambers, meters and connection points with their attributes.
Planned work
Flushing, servicing, replacement programmes and seasonal preparation.
Incidents and outages
Detection, isolation, restoration and the affected connections.
Meters and readings
Manual and remote readings, consumption and anomaly detection.
Collection rounds
Waste routes, containers, frequencies and confirmed collection.
Customer service
Connection requests, complaints and billing enquiries against the connection.
How it works
Mapped, programmed, restored, reported
Spatial network data is what lets an incident name the customers behind it.
01
Hold the network
Assets and connections are recorded spatially, so an incident can be traced to the customers it affects.
02
Run planned programmes
Servicing and replacement generate work orders inside the same schedule as reactive jobs.
03
Respond to incidents
A fault report or a sensor alarm creates a job with the network context already attached.
04
Report to customers
Affected connections are notified, and the customer who reported the fault is told what was done.
Outcomes
What changes
Fewer unexplained outages, and a clearer view of where the network loses.
Outages that can be explained
Which network section, which customers, how long.
Losses that are visible
Readings and network data show where consumption does not add up.
One queue for the network
Planned and reactive work compete transparently for the same crews.
Configured per administration
What is configured
- the networks operated and their asset model
- connection and customer records
- planned programmes and their frequency
- incident categories and response times
- meter types and reading collection
- collection routes and confirmation rules
- notification rules to affected customers
- the regulatory reporting required
Connected to
The rest of the platform
- GIS, as the base for every network record
- Field service and public works
- Urban IoT, for remote readings and alarms
- The citizen portal, for fault reports and connection requests
On your own network
See utility operations from fault to restoration.
We take one section of your network, trace an incident to the connections behind it, and follow the job, the notification and the report that close it.