Today
Utilities receive more and more connection requests for solar systems, heat pumps, charging points and new buildings. Many are incomplete and wait weeks for a first answer. Network planners spend their time chasing paperwork instead of engineering.
An example
The grid operator of a district town receives a request for a 30 kW solar system without a single-line diagram. The agent requests the diagram, finds the feeder at the local substation with its 630 kVA transformer and marks the case as standard once the file is complete.
Your data, wherever it lives
Today connection requests arrive via the portal and by e-mail, with site plans, circuit diagrams and datasheets as PDFs or scans; network points and assets sit in the GIS database, customers and meters in the ERP. demi reads, understands and links them per request and network point, with your rights. The AI checks each request against your connection rules in minutes, finds the network point and drafts the document request or the reply, instead of weeks of waiting, and network planning decides on the connection.
Where the data lives today
- Web & portals
- E-mails
- PDFs
- Scans & paper
- Databases
- ERP
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 request portal, inbox, GIS and ERP. demi replaces nothing and links each request to its address, network point, asset data and your technical connection rules. demi writes back only after approval.
- 2 · PermitPermission Layer
Network data stays with network planning; applicants see only their own case. An engineer from network planning approves every technical commitment, and the approval is recorded.
- 3 · ActIntelligence Layer
The agent checks the documents against your fixed connection rules, finds the network point and flags simple cases for fast handling. If something is missing, it drafts the request with an exact list and a reference to the rule that requires it.
How it runs
- 1
A request comes in via portal or email.
- 2
The agent checks the documents against the connection rules.
- 3
Missing documents are requested from the applicant.
- 4
It finds the network point and marks the case as standard or complex.
- 5
Network planning reviews and approves the reply.
What changes
Faster first answers
Fewer incomplete cases
Engineers focus on the hard cases
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
+270 hfreed per year
Assumptions and calculation
demi checks completeness and grid data and drafts the reply; you decide on the connection.
30 min → 21 min per case
How we calculate
150 connection requests × 30 min × 30% × 1.0 (manual) × 12 months = 16,200 min = 270 h
Value per year, before demi costs
Freed per year+270 h
Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.
= Value per year, before demi costs
+€17,550
gained per year
270 h ÷ 1,760 h per role = 0.2 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 it work with our network information system?
The data layer is designed for network data such as lines, substations and feeders from the GIS; how the data from the GIS gets to demi, we clarify in a conversation. The system stays as it is. Network planning decides which data the agent may see.
Which cases can be pre-approved?
You decide with your own rules, for example small generation units at a network point with enough capacity. The agent pre-sorts those cases. A qualified engineer always gives the technical approval.
How are applicants kept informed?
The agent drafts the receipt, the request for missing documents and status updates. They go out through the portal or by email. Applicants only see their own case.
Does this also work for water and heat connections?
Yes. The logic is the same: check documents against rules, find the network point, request what is missing. Only the rules and the network data differ.
