Today
The emergency plan sits in a binder last opened for the audit. Phone numbers are outdated, the on-call manager has changed, and only IT knows which systems depend on each other. When an attack encrypts the servers early on a Saturday, nobody knows who calls whom, and the plan sits on exactly the server that is down.
An example
At Aldevo Wassertechnik, an attack encrypts the file servers at five o'clock on a Saturday morning. The on-call manager calls the emergency number. demi guides him through the plan: disconnect the network, alert the crisis team, and the call tree runs by call and text message until all seven members have confirmed. The agent shows which systems depend on the file servers, that service jobs at three water utilities can continue with the emergency binder, and when the reporting deadline to the authority ends. Two months earlier demi had rehearsed this scenario with the crisis team and found two outdated phone numbers.
Your data, wherever it lives
The emergency plan and contact lists sit in a binder, the wiki or a PDF on the file server today, roles and phone numbers in the HR system, the system landscape in tickets and in IT's heads, contracts with suppliers and insurers in the DMS. demi reads, understands and links them, with your permissions. The AI keeps the plan current, rehearses it with you and in an emergency guides you through the steps by phone within minutes, and the crisis team decides.
Where the data lives today
- HR system
- Tickets
- Wiki & intranet
- DMS & archive
- Folders & drives
- PDFs
- Phone & voice
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: HR system, ticket system and IT's system inventory, wiki, DMS, folders and phone. demi replaces nothing and links the emergency plan, roles, deputies, on-call rotas and contact details with systems, their dependencies, suppliers and fallbacks. The plan stays reachable even when your own servers are down, and a printed emergency binder is ready as well.
- 2 · PermitPermission Layer
Management and the crisis team see the whole plan, each department its own procedures. demi uses private phone numbers only with consent and only in an emergency. Every change to the plan is released by a responsible person, and in an emergency every decision is logged with name and time.
- 3 · ActIntelligence Layer
The agent spots changes that affect the plan and proposes the update. It rehearses scenarios with the crisis team, guides people through the plan by voice in an emergency, alerts the call tree and keeps the situation report current. It follows the approved plan; the crisis team makes the decisions.
How it runs
- 1
demi links emergency plan, roles, deputies, contact details, system landscape and key suppliers into one plan.
- 2
When something changes, such as a new on-call manager, a new system or a different supplier, the agent proposes the update and the responsible person releases it.
- 3
Every quarter the agent rehearses a scenario with the crisis team, by phone or in chat, and notes where things stall.
- 4
In an emergency you call the emergency number: demi alerts the call tree, guides you step by step through the plan and logs every decision.
- 5
The crisis team decides; the agent tracks reporting deadlines, drafts notifications to authorities, customers and insurers and keeps the situation report current.
What changes
An emergency plan that matches today
Call trees that reach everyone within minutes
A record of every decision for authorities and insurers
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
+43 hfreed per year
Assumptions and calculation
demi keeps plan, contacts and dependencies current and prepares drills; the crisis team decides.
90 min → 63 min per case
How we calculate
8 plan updates and drills × 90 min × 30% × 1.0 (manual) × 12 months = 2,592 min = 43 h
Value per year, before demi costs
Freed per year+43 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
+$2,795
gained per year
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
What if our own IT is down in an emergency?
That is exactly what this case is built for. Plan, call trees and dependencies live in demi, outside your own servers, and can be reached by phone. On top of that, demi keeps a current emergency binder ready to print after every change.
How does demi rehearse an emergency with the crisis team?
The agent plays through a scenario, such as a fire in the plant, the failure of a key supplier or an attack on IT, by phone or in chat. It asks the questions that would come in a real emergency and notes where roles, numbers or fallbacks are missing.
Does a cyberattack have to be reported?
Often yes: depending on the case to authorities, to customers with reporting duties in their contracts, to the insurer and, where personal data is involved, to the data protection authority. The agent shows which deadlines apply to you, reminds you in time and drafts the notifications. Only an authorized person may send them.
Who maintains the emergency plan when something changes?
demi notices changes that affect the plan: a new person in a role, a different supplier, a new system. The agent proposes the update and the responsible person releases it. The plan stays current without anyone rewriting it every year.
