Today
A change request sets off days of searching through PLM, ERP and file shares. An open order, a stock batch or an operating manual gets missed. The result is scrap or a wrong delivery.
An example
Talwerk Antriebstechnik wants to make shaft 210-118 from 42CrMo4 instead of C45. Before release, demi shows 4 BOMs, 2 open production orders, 60 shafts in stock, one operating manual and 38 gearboxes at customer sites.
Your data, wherever it lives
Today parts, BOMs and drawings sit in PLM and CAD, open orders, stock and delivered serial numbers in the ERP, running production orders in the MES and operating manuals in the DMS. demi reads, understands and links them into one network per part, with your rights. Before release, the AI shows every affected BOM, order, stock item and customer in minutes instead of days of searching, and you decide on the change.
Where the data lives today
- PLM
- CAD & drawings
- ERP
- MES
- DMS & archive
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 PLM, ERP, MES and DMS. demi replaces nothing and links parts, BOMs, open orders, stock, suppliers, documents and delivered machines into one network in which every dependency can be followed across all sources of the case.
- 2 · PermitPermission Layer
The request follows the approval chain of your org chart. Each reviewer sees the impact on their own area and approves their part, and every approval is recorded.
- 3 · ActIntelligence Layer
The agent follows every recorded link and lists the affected items with quantities and dates, each linked to its record; the list comes from the links, not from the language model. It drafts the change notice and tracks which documents still need updating.
How it runs
- 1
Raise the change request in PLM or by e-mail
- 2
demi follows every link to BOMs, orders, stock, documents and installed machines
- 3
Each department reviews its part of the list and signs off
- 4
The change notice goes out and open documents are tracked
What changes
Changes released with the full impact in view
No missed order, no forgotten manual
A shorter change process
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
+288 hfreed per year
Assumptions and calculation
demi shows every affected bill of materials, order, stock and customer; you decide on the release.
2 h → 1.4 h per case
How we calculate
40 engineering changes × 2 h × 30% × 1.0 (manual) × 12 months = 288 h
Value per year, before demi costs
Freed per year+288 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
+$18,720
gained per year
288 h ÷ 1,760 h per role = 0.2 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 also find affected documents and manuals?
Yes, as long as the document is linked to the part or product or contains its part number. demi maps documents to parts. How the documents get from the DMS to demi, we clarify in a conversation. Documents without a clear link show up as a hint, not as a confirmed hit.
How do we handle changes a customer asks for?
A customer request is raised like an internal one, linked to the customer and the order. The impact list then also shows which deliveries and commitments to that customer are affected. Sales can give a solid answer before agreeing to anything.
Can we see earlier changes to the same part?
Yes. Every request, review and approval stays on the part. You can see who changed what and when, and what was affected at the time.
Do we have to replace our PLM?
No. Your data lives in PLM, ERP, MES and DMS, and demi replaces none of them. demi only writes back after approval. The formal release can stay in your PLM.
