Today
Quarries, processing and process plants run heavy equipment with small maintenance teams and few planned shutdowns. The task list is built from memory, spreadsheets and paper reports. Whatever is missed in the shutdown forces an extra stop later.
An example
Ahead of the annual shutdown at Montanis Hartsteinwerke, the agent lists 34 tasks for the 250 t/h crushing line. They include a change of the Mn18 jaw plates, which by recorded tonnage would wear out before the next shutdown, and an inspection of the B 1,200 mm conveyor belt. Two parts are out of stock; the purchase requests wait for the site manager's approval.
Your data, wherever it lives
Operating hours and tonnage sit today in controllers and belt scales, work orders and deferred tasks in the CMMS, inspection dates in spreadsheets, manuals as PDFs in the DMS, spare parts in the ERP and old reports only as paper scans. demi reads, understands and links them per asset, with your rights. The task list for the next shutdown, missing parts included, is ready in minutes instead of after half a day of compiling lists, and the site manager decides what goes in.
Where the data lives today
- Machines & sensors
- Tickets
- Office files
- PDFs
- DMS & archive
- ERP
- Scans & paper
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 CMMS, ERP, spreadsheets and DMS. demi replaces nothing and links operating hours, tonnage, maintenance orders, inspection dates, manuals, spare-part stock and contractors for each asset, including deferred tasks and old paper reports. demi writes back only after approval.
- 2 · PermitPermission Layer
Each site team sees its own equipment. The site manager approves the shutdown task list, and every change is recorded.
- 3 · ActIntelligence Layer
The agent selects the tasks that fall due before the shutdown after next, calculated from recorded hours, tonnage and deadlines, and checks parts and contractors. For every task it cites the manual interval or the report behind it.
How it runs
- 1
Connect assets, meter readings, orders and deadlines per site
- 2
Compute due dates from hours, tonnage and inspection intervals
- 3
Select the tasks due before the shutdown after next
- 4
Check spare parts and contractors for the shutdown window
- 5
Get the list approved and write the orders back after approval
What changes
Every shutdown used in full
Fewer extra stops
Parts and contractors ready in time
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
+58 hfreed per year
Assumptions and calculation
demi collects due maintenance and inspections per machine and fits them into the shutdown; you agree the plan.
4 h → 2.8 h per case
How we calculate
4 shutdown plans × 4 h × 30% × 1.0 (manual) × 12 months = 58 h
Value per year, before demi costs
Freed per year+58 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
+€3,770
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
Does this work if our maintenance reports are on paper?
Yes. demi reads scanned reports and inspection logs and assigns them to the right asset. The agent flags anything uncertain, and your team confirms it once. From then on demi works with that data like any other record.
Does demi plan by tonnage or by operating hours?
By whatever applies to the part. Crusher wear parts often run by tonnage, gearboxes and bearings by operating hours, inspections by calendar date. demi computes each task with its own counter and shows where the reading comes from.
Who approves the shutdown task list?
The site manager, or whoever you assign. The agent proposes the list and gives a reason for every task. demi creates orders and purchase requests only after approval, and every change is logged.
What happens to tasks that don't fit into the shutdown?
The agent lists them separately, each with the reason: a missing part, no contractor available or not enough time in the window. You then decide whether to bring them forward, postpone them or plan a short stop.
We plan shutdowns in spreadsheets today. Is that enough?
Yes. demi works with your spreadsheets; the CMMS and ERP are part of the landscape the data layer is built for. The finished list goes back as a spreadsheet or as approved orders ready to write back. Nothing gets replaced.
