Today
Machines at customer sites report on their own: by alarm e-mail, by text message, through telecontrol or building management. A power failure sends dozens of messages within minutes, and even on normal days so many arrive that nobody reads them all. The one alarm that matters drowns in the flood, and every ticket is created by hand, with unit and history gathered from three systems.
An example
Aldevo Wassertechnik looks after 180 plants at water utilities and industrial sites. During a thunderstorm night, 46 alarm e-mails arrive from one waterworks in the Sauerland within four minutes: mains failure, UV system off, dosing pump fault, zero flow. demi merges them into one case, "Power failure at waterworks", and once power is back sees that every alarm has cleared except one: UV irradiance on reactor 2 stays below the limit. That becomes its own ticket with top priority, because drinking water is at stake, with the serial number, the last lamp change 8,700 operating hours ago and the on-call technician as owner.
Your data, wherever it lives
Today alarms land as e-mails in a shared inbox, as text messages on the on-call phone and as messages in telecontrol or control systems, while unit history sits in the CMMS, contracts in the CRM and open tickets in the ticket system. demi reads these sources, understands which message belongs to which unit and cause, and links them into one case, with your rights. AI sorts the flood in seconds, and your service team decides who goes out.
Where the data lives today
- Machines & sensors
- E-mails
- Phone & voice
- Tickets
- Databases
- CRM
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 alarm mailbox, SMS gateway, telecontrol and control systems, ticket system, CMMS and CRM. demi replaces nothing and assigns every message to its unit by sender, identifier or serial number, with customer, contract, history and open tickets. Every alarm stays visible in the case, with time, text and source.
- 2 · PermitPermission Layer
A customer's alarms are visible only to the responsible service team, and the customer sees only the tickets for their own units in the portal. Service management sets the rules for which alarms belong together and which priority they get, and every decision shows its rule in the ticket. demi acknowledges nothing on the unit; that stays with the operator or the technician.
- 3 · ActIntelligence Layer
The agent reads alarms in any format, identifies unit and alarm class and merges messages with one cause into one case, such as all follow-on alarms after a power failure. It sets the priority by alarm class, contract and unit type, as a rule rather than a guess. If an alarm clears by itself, it notes this and puts the case up for closing; if it persists, it alerts the on-call team.
How it runs
- 1
Alarms reach demi as e-mail, as text message or from telecontrol and building management systems.
- 2
demi identifies unit, customer and contract by sender, identifier or serial number.
- 3
If many alarms share one cause, the agent merges them into one case and shows the chain.
- 4
It sets the priority by alarm class and contract, attaches history and open tickets and alerts the on-call team.
- 5
If the alarm clears by itself, demi puts the case up for closing; if it persists, the technician takes over.
What changes
Important alarms stand out from the flood
One case per cause instead of a hundred tickets
The technician starts with unit, history and priority
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
+160 hfreed per year
Assumptions and calculation
demi turns alarms into tickets with unit and priority and merges floods; the on-call team acts.
5 min → 3 min per case
How we calculate
400 alarm messages × 5 min × 40% × 1.0 (manual) × 12 months = 9,600 min = 160 h
Value per year, before demi costs
Freed per year+160 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
+€10,400
gained per year
160 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
Which sources can demi read alarms from?
From alarm e-mails, text messages via a gateway, telecontrol and building management alerts and controller exports that already reach you today. demi replaces none of these systems. How the messages get to demi, we clarify in a conversation.
How does demi tell that many alarms share one cause?
By time, place and known chains, such as power failure, then pumps off, then zero flow, and by rules you define. From the history demi learns further chains and shows them to you for confirmation. Every merge is visible in the ticket, and service can pull an alarm back out.
Does demi acknowledge alarms on the unit?
No. demi only reads alarms and acknowledges, switches or adjusts nothing on the unit. Acknowledging and intervening stay with the operator or your technician.
Who is alerted at night and at weekends?
The person on duty according to your on-call rota, by message, text or phone call depending on priority. If they do not confirm within the agreed time, the case goes to the next person on the list. Non-critical alarms wait in the service team's list until morning.
