Today
When a machine fails, the phone calls begin: how long is the repair, which orders depend on it, which machine can take them, is the program even there? The answers sit in maintenance, the ERP, the MES and the supervisor's head. Hours pass before a new plan is in place, and the customer learns about the delay when the truck does not come.
An example
At Tannried Möbelwerk, the spindle of CNC machining centre BAZ 3 fails on Tuesday at 6:20; the replacement spindle arrives in five days. The machine has 31 orders scheduled. demi shows: 22 fit on BAZ 1 and 2 with existing programs, 9 need the five-axis unit of BAZ 3, and without action the due dates of 4 customers slip, including a medical practice fit-out with 14 cabinets. Planning chooses a Saturday shift on BAZ 1 and subcontracts 5 of the 9 five-axis orders to a partner; two dates remain at risk, and the back office sends those customers the prepared message with a new date.
Your data, wherever it lives
What you need in a breakdown sits in many places today: fault and repair time in the maintenance system, orders and due dates in the ERP, queues and programs in the MES and on the machines, customer contacts in e-mails. demi reads, understands and links them, with your rights. Plan B is ready in minutes instead of after a morning on the phone, and production planning decides which option applies.
Where the data lives today
- ERP
- MES
- Tickets
- Machines & sensors
- E-mails
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 ERP, MES, maintenance system, machine data and e-mail. demi replaces nothing and links the breakdown and the expected repair time with the orders scheduled on the machine, their routings, the capabilities of the other machines and the promised delivery dates. For every order you see where else it can run.
- 2 · PermitPermission Layer
Only production planning changes the plan; demi proposes and calculates. demi drafts customer messages with the contacts from the ERP; they go out only after release by the sales back office. Who chose which option is recorded.
- 3 · ActIntelligence Layer
For every affected order, the agent checks which machine covers format, operations and program and when capacity is free there, and computes the new completion dates from the routings. It puts two or three options side by side, such as an alternative machine, an extra shift or subcontracting, each with the due dates that hold or slip. Dates and times come from the data; the language model only writes the explanation and the customer message.
How it runs
- 1
The breakdown arrives from the maintenance system, from the machine or by phone, with the expected repair time.
- 2
demi lists every order scheduled on the machine, with due date and customer.
- 3
For each order the agent checks which other machine can make it and when there is room.
- 4
It puts options side by side with the due dates that hold or slip and drafts the customer messages.
- 5
Production planning picks the option, the back office releases the messages.
What changes
A new plan in minutes instead of hours on the phone
Customers learn about delays early and honestly
Alternative machines put to use that nobody had in mind
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
+96 hfreed per year
Assumptions and calculation
demi shows alternative machines, slipping dates and options and drafts the customer message; you decide.
2.5 h → 1.5 h per case
How we calculate
8 machine breakdowns × 2.5 h × 40% × 1.0 (manual) × 12 months = 96 h
Value per year, before demi costs
Freed per year+96 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
+€6,240
gained per year
96 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
How does demi know which machine can take an order?
From routings, machine master data and what has actually run so far: format, operations, units, existing programs and tools. If a program is missing on an alternative machine, demi shows it and names the effort of earlier transfers. The supervisor decides in the end whether a solution fits technically.
How does demi learn about the breakdown?
Through what happens anyway: the fault report in the maintenance system, the stop in the machine data or a call from the shift lead. The expected repair time comes from the technician; if it changes, demi recalculates the options.
Does demi send customers a message by itself?
No, demi drafts it: new date, short reason, a partial delivery as an offer if you wish. The message goes out only when the sales back office releases it. You can mark key customers so that demi proposes a call instead of an e-mail.
How does the chosen option get into our planning system?
Plan and sequence stay in your ERP or planning system; demi does not replace it. Where an interface exists, demi hands the chosen option back; otherwise planning transfers it as usual.
