Today
A tool shop runs many one-off projects on the same machines, planned on whiteboards and in spreadsheets. Every customer change and every machine breakdown shifts everything. That a sampling date will not hold often becomes clear only shortly before.
An example
At Norvelta a customer change to the 4-cavity tool W-2219 adds 30 hours of EDM. The agent shows that this pushes back the sampling of tool W-2230 unless one EDM job moves to the weekend. The shop manager approves the weekend shift.
Your data, wherever it lives
In the tool shop, planning sits today in spreadsheets, projects and operations in the ERP, booked hours and breakdowns in the MES; customer changes arrive as new CAD models by e-mail, sampling dates sit in the calendar. demi reads, understands and links them per tool and component, with your rights. After every change the scheduling engine recalculates, the AI shows within minutes which sampling date is at risk and why, and the tool shop manager releases the plan.
Where the data lives today
- Office files
- ERP
- MES
- CAD & drawings
- E-mails
- Calendars
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 ERP, MES and spreadsheets. demi replaces nothing and links tool projects and components with operations, machine calendars, booked hours and the customer's milestones. The plan goes back to your systems only after your approval.
- 2 · PermitPermission Layer
Project managers see their own tools; the shop manager sees all machines, sets priorities and releases the plan. Every change to the plan is recorded with name and reason.
- 3 · ActIntelligence Layer
The machine plan is computed by your existing planning tool or a connected scheduling solver from booked hours and machine calendars, not by the language model. The agent explains the result, shows milestone risks with project and component and triggers a recalculation after changes or breakdowns.
How it runs
- 1
The case needs projects, components and remaining work from ERP and MES.
- 2
The solver places milling, EDM and assembly on the machines.
- 3
The agent shows which milestones are at risk and why.
- 4
After a change or a breakdown, the plan is recalculated.
- 5
The shop manager chooses the variant and releases the plan.
What changes
Reliable sampling dates
Better use of expensive machines
Quick replanning after changes
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
+115 hfreed per year
Assumptions and calculation
demi schedules milling, EDM and assembly across all projects and shows slipping milestones; you steer.
8 h → 5.6 h per case
How we calculate
4 planning rounds × 8 h × 30% × 1.0 (manual) × 12 months = 115 h
Value per year, before demi costs
Freed per year+115 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
+$7,475
gained per year
115 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
Does it handle a shop full of one-off projects?
Yes, that is what it is built for. Every tool is a project with its own components and operations. Where no hours are booked yet, the agent estimates the effort from similar past tools and shows what it is based on.
How does it react to customer changes?
The change is recorded on the tool and its extra effort goes into the plan. The plan is recalculated, and the agent shows which milestones move in which projects. The shop manager decides on priorities.
Does it use booked hours?
Yes. Planned and booked hours give the remaining work per component. If a component starts running over, you see it before the milestone slips.
Do we need a new planning system?
No. demi uses your existing planning tool or brings in a scheduling solver. demi writes back only after approval. The whiteboard can stay if you like it.
