Today
Inspection reports pile up as PDFs and exchange files, coded to different standards. Turning them into a ranked rehabilitation plan with costs is slow engineering work. Often only a sample of the findings makes it into the plan.
An example
On behalf of a municipal network operator, the agent at Aldevo Wassertechnik reads the inspection reports for 140 km of sewer network and lists 62 pipe sections that need rehabilitation soon, most of them DN 150. It ranks them by condition and groups neighboring sections into four construction lots. It estimates the cost per lot from past projects with HDPE pipe; the network engineer checks the ranking before release.
Your data, wherever it lives
Inspection reports sit today as PDFs and exchange files on shared drives, coded to different standards, with the CCTV videos and photos next to them, pipe sections and manholes in the GIS, and the costs of past rehabilitations in spreadsheets and project files in the DMS. demi reads, understands and links them per pipe section, with your rights. The AI assesses every finding rather than a sample and proposes a ranking with costs within days, and the network engineers confirm it before approval.
Where the data lives today
- PDFs
- Photos, video & audio
- Folders & drives
- Databases
- DMS & archive
- Office files
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
Data sources in this case: the GIS, DMS and spreadsheets. demi replaces nothing and links inspection reports, damage codes, network and manhole data and past rehabilitation projects to every single pipe section. demi writes condition classes and ranking back only after approval.
- 2 · PermitPermission Layer
Network engineers see their own area. The head of department approves the rehabilitation plan and budget, and every approval is recorded.
- 3 · ActIntelligence Layer
The agent maps damage codes to one standard, derives condition classes by the defined rule set and ranks pipe sections by condition and risk, each citing its inspection report. It costs the draft plan from past projects; the engineers confirm the ranking.
How it runs
- 1
Read inspection reports and exchange files
- 2
Map damage codes to one standard
- 3
Derive condition classes per section by rule set
- 4
Rank sections by condition and risk, group neighbors into lots
- 5
Submit the plan with costs from past projects for release
What changes
Plans from all findings, not a sample
Consistent coding across all reports
Budgets grounded in real projects
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
+192 hfreed per year
Assumptions and calculation
demi links damage codes to the sewer network and proposes a ranking; you plan the renewal.
60 min → 36 min per case
How we calculate
40 inspection reports × 60 min × 40% × 1.0 (manual) × 12 months = 11,520 min = 192 h
Value per year, before demi costs
Freed per year+192 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
+$12,480
gained per year
192 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
Does demi analyze the camera videos?
demi works with the coded findings that were produced from the video during inspection. Videos and photos stay linked to the pipe section, so an engineer can look at disputed spots directly. Nothing is re-coded automatically.
Which coding standards does demi understand?
The coding systems commonly used for sewer inspection in Europe, including older catalogs from earlier surveys. The agent maps them to the standard you choose and shows the original code for every conversion. Ambiguous cases go to the network team.
Can demi write back to our network database?
Yes. Condition classes and ranking can be handed over as an exchange file, whichever format your system accepts. Nothing is written back before release, and every change is logged.
Who decides on the ranking?
The engineers. The agent derives condition classes by the defined rule set and proposes a ranking, always with the findings behind it. The network team confirms or changes it, and the head of department releases plan and budget.
