Today
Leak alarms, fault reports and calls from residents arrive without context. Network data, damage history and maintenance sit in separate systems, so the crew on site does not know the history. Renewal planning and statistics for authorities lack solid evidence.
An example
A municipal water association triages the fault reports of its drinking water network with demi. A pressure drop in zone 7 is linked to a DN 150 cast-iron main from 1962 with five earlier bursts and ranked urgent. The agent attaches the damage history to the work order, the control room sends the crew out, and the main goes on the renewal planning list.
Your data, wherever it lives
Today leak alarms come from the control system, fault reports by e-mail and notices from residents by phone or through the portal, while pipes and assets sit in the GIS and damage and work orders in the maintenance system. demi reads, understands and links them per network segment and asset, with your rights. The AI attaches the history to every report in seconds and rates its urgency by your network rules instead of someone searching three systems, and the control room sends the crew.
Where the data lives today
- Machines & sensors
- E-mails
- Phone & voice
- Web & portals
- Databases
- Tickets
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the GIS, CMMS, ERP, e-mail and portal. demi replaces nothing and assigns every report to its network segment or asset, with material, year built, damage, outages and work orders. demi only writes back after approval.
- 2 · PermitPermission Layer
Network data stays with the utility, and crews see only the assets of their job. The responsible manager approves every report to the authorities, and this is recorded.
- 3 · ActIntelligence Layer
The agent attaches the history and ranks urgency by fixed rules set by your network operations. It flags pipes with repeated damage for renewal planning and calculates outage statistics from recorded events, every figure with its source.
How it runs
- 1
An alarm, fault report or resident's call comes in from the control system, by e-mail or via the portal.
- 2
demi links the report to the network segment or asset by location and ID.
- 3
The agent shows material, year built, earlier damage and open work orders and ranks urgency by rule.
- 4
The crew gets the job with the history; completion goes back after approval.
- 5
Repeated damage goes into renewal planning, outage times into the statistics.
What changes
Every crew knows the history before it goes out
Evidence for renewal planning
Outage statistics ready for reporting
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+180 hfreed per year
Assumptions and calculation
demi links each report to the pipe, its age and past damage and ranks it; you dispatch the crew.
15 min → 10.5 min per case
How we calculate
200 fault reports × 15 min × 30% × 1.0 (manual) × 12 months = 10,800 min = 180 h
Value per year, before demi costs
Freed per year+180 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$11,700
gained per year
180 h ÷ 1,760 h per role = 0.1 full-time roles
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
Can demi match fault reports against our network information system?
Your existing GIS and maintenance system stay in place; nothing is replaced. Network segments and assets keep their IDs and are linked with damage and work orders. demi writes completed work orders back after approval.
How is urgency decided?
By fixed rules your network operations team sets, for example by report type, supply area, material and damage history. The agent applies them and shows which rule applied to each report. The control room can change the ranking with a reason.
Can demi prepare outage statistics for the authorities?
demi prepares them from recorded events: outage times, affected segments and number of reports, each with its source. You decide which figures you report and how. The responsible manager releases and sends the report.
Does this also work for power grids?
Yes. Instead of pipe segments, demi links substations, cables and overhead lines with faults and maintenance. After a storm, the control room sees which stations have failed before. The process and the rules stay the same.
Does our network data stay under our control?
Yes. The network data belongs to the utility, demi is hosted in the EU, and every person sees only what belongs to their role. Every access and every change is logged.
