Today
Engineers simplify a part and repeat a failure that was solved years ago. The reason for a thicker plate, an extra rib or a more expensive material sits in old e-mails, in a test report in the archive and in the head of a colleague who retired long ago. The drawing shows only the dimension, not the why.
An example
At Conveyra Fördertechnik a young engineer wants to save weight on the end carriage of the BK 10 t bridge crane and reduce the web plate from 8 to 6 mm; the static calculation allows it. He asks demi why it is 8 mm. demi tells the story from four sources: a 2017 complaint reports a cracked weld on the end carriage of a crane in a foundry, the service technician's e-mail shows photos of the crack, the 8D report names vibration when starting under full load as the cause, and the change request raises the plate to 8 mm. The engineer leaves the plate as it is and attaches question and answer to the part as a note.
Your data, wherever it lives
Today the why behind a design is scattered: change requests in the PLM, reasons in old e-mails, test and 8D reports in the QM system, complaints in tickets, the rest in project folders on the drive and in review recordings. demi reads and understands all of it, links it to the part it concerns and keeps your access rights. The AI then answers in minutes what used to take days in the archive, and you decide what follows from it.
Where the data lives today
- PLM
- E-mails
- QM system
- DMS & archive
- Folders & drives
- Tickets
- Photos, video & audio
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 PLM, mailboxes, the QM system, the DMS, old project folders and complaint tickets. demi replaces nothing and attaches change requests, e-mails, test and 8D reports and complaints to the part they concern. So every part has a history, across years and system changes.
- 2 · PermitPermission Layer
Everyone sees a part's history only from sources they are allowed to see: customer names and prices from complaints stay with those entitled to them. A design review is recorded only with every participant's consent, and release in the PLM stays with the head of design.
- 3 · ActIntelligence Layer
The agent answers the question why with a timeline: what was changed, when, by whom and for what reason, each step with its source. It invents no reasons; if a link in the chain is missing, it says so. In the design review it records every finding with its decision, attaches it to part and change and reports while any point is open.
How it runs
- 1
You ask about a part or a dimension: why is it like this?
- 2
The agent searches change requests, e-mails, test reports and complaints for exactly this part.
- 3
It tells the story as a timeline, each step with its source.
- 4
In the design review demi records every finding with its decision and attaches it to part and change in the PLM.
- 5
While a finding is open, release waits; the head of design releases once everything is closed.
What changes
Solved failures are not repeated
The why behind every dimension stays when people leave
Design reviews end with closed findings, not open lists
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
+144 hfreed per year
Assumptions and calculation
demi pieces together a part's history from changes, e-mails and reports; you decide.
2 h → 1.4 h per case
How we calculate
20 design questions × 2 h × 30% × 1.0 (manual) × 12 months = 144 h
Value per year, before demi costs
Freed per year+144 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
+€9,360
gained per year
144 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 history of a part?
From what was created anyway: change requests in the PLM, e-mails, test and 8D reports, complaints and old project folders. demi links them to the part via part number, drawing and project, even if the part number used to be different. Every statement links to its source.
What if the reason is written down nowhere?
Then the agent says so and invents nothing. It shows what it found, for example the change request without a reason, and names the people involved back then who are still with the company. The answer you get, you attach to the part as a note.
Is every design review recorded?
Only if all participants agree. Then demi takes notes in the Teams call, sums up every finding with decision and owner and attaches it to part and change object. The moderator checks the minutes before they count.
How does demi hold a release?
The way the head of design sets it up: while a finding from the review is open, the agent shows it on the change object in the PLM and holds the release. Only the responsible person can close a finding, not the agent. Only the head of design can release.
