Today
Requirements, risks and test evidence sit in separate documents and spreadsheets. Traceability gaps only surface in a customer audit or during approval.
An example
The specification for the KS-HV high-voltage wiring harness at Arnstein holds 840 requirements. demi shows 22 without a test and 3 hazards from the ISO 26262 analysis whose mitigation has no verification evidence yet.
Your data, wherever it lives
Today specifications arrive as PDFs running to hundreds of pages, design revisions sit in the PLM, risk analyses and traceability matrices in spreadsheets, test cases and results in the test database or ALM, and test reports in the DMS. demi reads, understands and links them per requirement, with your rights. The AI breaks a specification down in hours instead of weeks and shows every gap on the way to the evidence, and the project team confirms the links.
Where the data lives today
- PDFs
- PLM
- Office files
- Databases
- 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, DMS, ALM and spreadsheets. demi replaces nothing and links specifications, design elements, risk analyses, test plans and test results into one network in which every requirement has a path to its evidence. demi writes back only after approval.
- 2 · PermitPermission Layer
Each discipline confirms its own links. Quality signs off the trace report in line with your process, and every confirmation is recorded.
- 3 · ActIntelligence Layer
The agent splits specifications into single requirements with chapter and page and proposes links. It builds the gap list from confirmed links only, not from guesses: missing tests, mitigations and evidence.
How it runs
- 1
Import the specification and split it into single requirements
- 2
Get link proposals to design, risk and test, then confirm them
- 3
See the gaps: requirements without tests, hazards without evidence
- 4
Generate the trace report and sign it off before the audit
What changes
Traceability that holds up in an audit
Gaps found early, not in the audit
Less manual work on the matrix
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
+180 hfreed per year
Assumptions and calculation
demi links each requirement to design, risk and test and shows the gaps; you close them.
15 min → 10.5 min per case
How we calculate
200 requirements × 15 min × 30% × 1.0 (manual) × 12 months = 10,800 min = 180 h
Value per year, before demi costs
Freed per year+180 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
+€11,700
gained per year
180 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
Can it read requirements from customer specifications?
Yes. demi reads specifications as PDF, text document or spreadsheet and splits them into single requirements with chapter and page. Each requirement keeps a reference to where it appears in the original.
How are links confirmed?
The agent proposes, the responsible person confirms or rejects. Only confirmed links count for the trace report. The history shows who confirmed what and when.
Does it support risk files such as an FMEA?
Yes. Hazards and mitigations from risk analyses are linked the same way as requirements. You can see which mitigation has verification evidence and which does not.
What happens when a requirement changes?
demi flags every linked design element, test and piece of evidence for review. A changed requirement never becomes a silent break in the chain.
