15
prototypes
“Show me the room-14 prototype, on the day of the test”
« Proving that the room-14 prototype was at that document level on the day of the test is computerised nowhere. »A test run is a dated fact, attached to one revision.
Use case · Quality & certification · Project management
Export audit evidence in one click instead of rebuilding it.
On the V-model · Whole V: requirement to evidence, at every gateKoddex records requirements, tests, results and deviations as the engineering work happens. The traceability your certifier expects is ready at any date, and you export only the scope each party needs.
1 click
to export the certification file
10 s
to find the right information, instead of 45 min across many tools
Measured at our reference customer after a year in use. Your first scope measures them on your own programme.
Watch it in 60 seconds
Audit-ready traceability · Koddex
01
What the auditor asks for, and where the answer is not
2 000
units to build
The standard everyone is sure about is the 2015 one
« He was completely sure of himself — on a version of the standard that was true fifteen years ago. »The standard is a dated version in the model, not a memory.
5 / 30
engineers
Five people out of thirty do the paperwork
« The administrative load of design control took five people for a team of twenty to thirty. »Evidence is a by-product of the work, not a second job.
Evidence in minutes, not weeks
Every change, test result and approval is recorded as the work happens, so the audit dossier is an export of existing data rather than weeks of collection.
Provable at any date
Koddex keeps the history of every change, so you can show the configuration and its evidence as they were on the day a unit shipped.
The scope each party needs, nothing more
The authority, the customer and each supplier receive only their part of the traceability, and the rest of your design data stays private.
02
Traceability as a by-product of the work
01
Every change logged, down to the attribute
Koddex logs who changed which value, when, and through which change request, directly on the item instead of in a separate tool.
02
From the clause to the evidence
Follow a requirement from the standard's clause to the system element, the test and its result.
03
A scoped export for the auditor
Select a scope and a date, and the export contains the requirements, the evidence and the approvals behind them in one file.
03
Assign the task to the AI verification engineer.
It picks up the task in Koddex, works on your product data, comments on what it found and hands you the result to approve.
AI verification engineer
▸Prepare the evidence pack for the landing gear at the CDR baseline.
- Reads the parts, requirements and tests
- Follows the links, within your rights
- Proposes it on a branch for you to sign
The CDR baseline holds 212 requirements: 198 have a passed test and 14 are still open. The pack is ready with the 14 open items listed first, and I commented each one for its owner. It waits for your approval before it goes to the quality team.
Every agent action logged · scoped to the user's permissions
Discover more use cases
Frequently asked questions
See all questionsNo. Koddex sits with your CAD, PLM and ERP, not instead of them. It links what is already there on one graph and computes the effects of a change, and it connects to PLM, QMS, ERP and MES platforms through its API.
The first use case is typically live within 48 hours, and full onboarding takes about three weeks, led by a dedicated Customer Success Manager.
Exclusively in the European Union, in the AWS Europe (Ireland) region. No customer data leaves the European Economic Area without your prior written agreement.
A 20-min demo. Your first use case live in 1 month.
Bring a recent audit request. In the demo, we show how Koddex exports the evidence an auditor asks for.
0-5 min
you describe the product and the change
5-15 min
we show the use case in Koddex on a product like yours
15-20 min
you leave with a plan for your first use case, live within a month