Today
A complaint comes in and the customer wants an 8D response fast. The data sits across the quality system, ERP, MES and inboxes, and is pulled together by hand under pressure. Similar cases from earlier years rarely surface.
An example
At Arnstein a customer reports cracks in AlSi10Mg housings AG-2140. The agent links two production lots, their inspection data and a similar case from last year caused by a mould temperature deviation. The quality engineer checks the hint at the casting cell and confirms the cause.
Your data, wherever it lives
Today complaints arrive with photos by e-mail, lots and production orders sit in the ERP, inspection and process data in the MES, actions in the QM system and earlier 8D reports as PDFs in folders. demi reads, understands and links them per complaint and lot, with your rights. The AI pre-fills D1 to D4 in minutes instead of hours and finds similar past cases, and your quality team confirms the root cause.
Where the data lives today
- E-mails
- Photos, video & audio
- ERP
- MES
- QM system
- PDFs
- Folders & drives
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 quality system, ERP, MES and e-mail. demi replaces nothing and joins the complaint into one case with the affected lots, production orders, inspection results, supplier data and earlier 8D cases. demi only writes back after approval.
- 2 · PermitPermission Layer
The responsible quality engineer owns and approves the report. The customer receives only that version, supplier data and internal notes stay internal, and every approval is recorded.
- 3 · ActIntelligence Layer
The agent pre-fills D1 to D4 with linked facts and finds similar past cases and their root causes; affected lots and quantities come from traceability, not from an estimate. It only proposes the root cause; the team confirms it.
How it runs
- 1
Take over the complaint from the portal, e-mail or quality system
- 2
Link the affected lots, orders and inspection data
- 3
Pre-fill D1 to D4 and show similar past cases with their causes
- 4
Confirm the root cause as a team and assign actions
- 5
Send the released version to the customer and track actions to closure
What changes
Faster 8D responses to customers
Root-cause analysis built on evidence, not memory
Lessons from past cases reach every new one
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
+162 hfreed per year
Assumptions and calculation
demi pre-fills the 8D report with facts from complaint, production and past cases; you settle the cause.
3 h → 2.1 h per case
How we calculate
15 8D reports × 3 h × 30% × 1.0 (manual) × 12 months = 162 h
Value per year, before demi costs
Freed per year+162 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
+€10,530
gained per year
162 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 follow our 8D template?
Yes. demi fills your template and your fields, not a foreign format. Customer-specific forms can be set up as their own templates. Every pre-filled entry links to the record it came from.
How does it find similar past cases?
Through the linked data: the same or similar parts, materials, defect types, lines and suppliers. The agent also compares the failure descriptions by meaning. You see why a case counts as similar and can dismiss it.
Who decides the root cause?
Your team. The agent proposes possible causes with evidence but does not decide. The cause only goes into the report once the responsible engineer confirms it, and that confirmation is recorded.
Does the customer see internal data?
No. The customer only gets the version you release. Supplier names, internal comments and cost details stay in demi and are not visible to them.
Which systems does the 8D report need?
At minimum the system where complaints land and the ERP with lots and orders. MES data and inspection results make the report more complete. How the data from these systems gets to demi, we clarify in a conversation; your systems stay as they are.
