Today
Everyone on the shop floor has a theory about where things jam, usually at the most expensive machine. It is rarely measured, because bookings, machine data and shift plans live in different systems and an analysis takes days. So overtime and investment go to machines that are not the bottleneck, and lead times stay long.
An example
Wallner+Hardt Sensortechnik plans a second placement machine because the WS-420 pressure sensors are finished later and later. demi analyses 14 weeks of bookings and machine data: the placement machine runs at 61 % utilization, while lots wait an average of 2.8 days before temperature calibration, because the two climate chambers are only loaded in two shifts. demi runs two options: a night load prepared by the late shift adds 18 % throughput without investment, a third shift 27 %. Production management shelves the placement machine and starts the night load.
Your data, wherever it lives
The times of your production are spread out today: log-ons and log-offs in the MES, states and stops in the machine controls, routings and orders in the ERP, shift models in spreadsheets. demi reads, understands and links them per work center and lot, with your rights. The AI shows in minutes, not after a weeks-long study, where things really jam, and you decide what to change.
Where the data lives today
- MES
- Machines & sensors
- ERP
- Office files
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 MES, machine data, ERP and spreadsheets. demi replaces nothing and links bookings, machine states, routings, shift models and production orders per work center. For every lot you see when it arrived, how long it waited and how long it was processed.
- 2 · PermitPermission Layer
The analysis covers work centers and orders, not people: demi shows no times of individual employees. Production management, process planning and plant management see the analysis; they decide on shifts and subcontracting as before, and every option is recorded with its assumptions.
- 3 · ActIntelligence Layer
The agent measures throughput, utilization, queues and idle times per work center from the bookings and shows where lots pile up. It runs options such as an extra shift, subcontracting, other lot sizes or a second machine with the recorded times, not estimates. The language model explains the result in plain words, every figure with its source.
How it runs
- 1
The MES, machine data, ERP and shift plans are connected.
- 2
demi computes arrival, waiting, processing and idle time per work center for every lot.
- 3
The agent shows where lots pile up and which work center limits throughput.
- 4
It runs options such as an extra shift, subcontracting or smaller lots with the recorded times.
- 5
Production management decides, and demi measures whether the measure works.
What changes
Overtime and investment at the real bottleneck
More throughput from the machines you have
Decisions on measured values, not gut feeling
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 measures waiting and processing times from the bookings and runs the options; you decide.
8 h → 4.8 h per case
How we calculate
4 bottleneck analyses × 8 h × 40% × 1.0 (manual) × 12 months = 154 h
Value per year, before demi costs
Freed per year+154 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
+$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
How does demi know the waiting and idle times?
From the time stamps that exist anyway: log-ons and log-offs in the MES, machine states and bookings in the ERP. Where there is no booking between two work centers, demi shows the gap instead of estimating it. If manual stations have no bookings, a scan when the lot arrives and leaves is enough.
Does demi rate my employees' performance?
No. demi analyses work centers, machines and orders, not people, and shows no times of individual employees. You agree with the works council how the analysis is used, and demi follows those rules.
What if the bottleneck moves?
It often does, depending on product mix and shift. demi keeps recalculating and reports when another work center becomes the bottleneck, for example because a large order with many variants arrives. For each option demi also shows where the next bottleneck will appear.
Can demi calculate investments too?
Yes, with your figures: cost of a machine, shift premiums, prices for subcontracting. demi puts throughput, lead time and cost of the options side by side, every assumption visible. Plant or production management makes the decision.
