Today
Hundreds of alarms reach the control room every shift, most of them needing no action: alarms that have stood for weeks, alarms that come and go every minute, consequential alarms of a single fault. The shift acknowledges on autopilot, and the one alarm that matters gets lost. Cleaning up alarms by hand takes months, so it never gets done.
An example
The control room of the blending plant at Orvelon receives an average of 1,900 alarms a day. The agent shows that twelve alarms cause more than half of them: a level alarm on tank T-204 chatters because its limit sits exactly at the usual fill level, and every agitator shutdown triggers eight consequential alarms. It proposes deadband, delay and suppression during shutdown; one of the twelve, a safety function alarm, it only flags for a sensor check. Process control engineering implements eleven proposals through the change procedure.
Your data, wherever it lives
Your alarms sit today in event logs and control system exports, the alarm list in spreadsheets, the alarm philosophy as a PDF, hints of faulty measuring points in the shift log and maintenance orders. demi reads, understands and links them per measuring point, with your rights. The AI finds in hours the worst offenders that take months to clean up by hand, and operations and process control engineering decide what changes.
Where the data lives today
- Machines & sensors
- Databases
- Office files
- PDFs
- Tickets
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: control system exports, the event database, alarm lists, the alarm philosophy, the shift log and maintenance orders. demi replaces nothing and links every alarm to its tag, plant section, limit, priority, operating state and the orders for that measuring point.
- 2 · PermitPermission Layer
Plant management, process control engineers and shift supervisors see the analysis for their units. The agent marks alarms of safety functions and proposes no weakening for them. Every change goes through your plant's change procedure, is implemented in the control system by process control engineering and is recorded.
- 3 · ActIntelligence Layer
The agent counts alarms per operator console and period, finds the worst offenders and standing, chattering and consequential alarms, and proposes a change for each: deadband, delay, a different priority, suppression during shutdown or grouping. Every proposal states the frequency from the log and the rule of the alarm philosophy it relies on. After implementation, it measures whether the alarm rate falls.
How it runs
- 1
demi reads the alarm and event logs of recent months, the alarm list and the alarm philosophy.
- 2
The agent shows the alarm rate per operator console and the few alarms causing most of it.
- 3
For each of these alarms it proposes a change, justified by frequency, operating state and alarm philosophy.
- 4
Operations and process control engineering review the proposals in the change procedure and implement them in the control system.
- 5
Afterwards the agent measures whether the alarm rate falls and reports new bad actors.
What changes
A calmer control room
Important alarms stand out again
Alarm clean-up in weeks, not months
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
+154 hfreed per year
Assumptions and calculation
demi analyses the alarm logs and proposes changes; you check and implement them.
8 h → 4.8 h per case
How we calculate
4 alarm reviews × 8 h × 40% × 1.0 (manual) × 12 months = 154 h
Value per year, before demi costs
Freed per year+154 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,010
gained per year
154 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 rules does demi use to assess our alarms?
Your alarm philosophy and recognised guidelines such as NAMUR NA 102, IEC 62682 and EEMUA 191. The agent measures, for example, the alarm rate per console, alarm floods, standing and chattering alarms. Every figure shows the log entries it comes from.
Does demi change limits in the control system?
No. demi reads logs and lists and makes proposals. Your process control engineers implement them in the control system, following your plant's change procedure. Every change stays reviewed and documented.
What about alarms of safety functions?
The agent marks them using your alarm list and proposes no weakening for them. If such an alarm chatters, it reports this as a finding to process control engineering and maintenance, for example as a sign of a faulty sensor. A person always makes the decision.
Will the control room stay calm afterwards?
Alarms move: new measuring points, modifications, wear. The agent keeps watching the alarm rate and reports when an alarm becomes a new bad actor, with a proposal attached. The clean-up does not stay a one-off project.
