20
pages
A twenty-page checklist, completeness judged by eye
« We estimate whether the analysis is complete. Finger in the air. »Koddex lists every requirement and test a change affects, so no one has to judge completeness by eye.
Use case · Engineering · Project management
Know what a change affects before you approve it.
On the V-model · Both branches: a design change re-opens the tests that verified itBefore a change is approved, Koddex lists every requirement, part, test and variant it touches. The list is computed from the links in your product data, with the mass and cost difference of each affected assembly.
1 day
for a change impact analysis, instead of 2 weeks of meetings and spreadsheets
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
Impact analysis · Koddex
01
Change impact is still assessed from memory
4
disconnected tools
Four tools, and the certification impact counted by hand
« We need requirements traceability to replace the manual spreadsheets before the launch. »When a requirement changes, Koddex names the tests it invalidates, so traceability no longer lives in spreadsheets.
2
systems
Between the PLM and the ERP, there is Excel
« There is a gap between our PLM and our ERP, filled with Excel and Word files. Traceability becomes a nightmare. »Koddex links PLM and ERP items in one model, so engineering no longer fills the gap with Excel and Word.
No surprise rework
Koddex follows the declared links from the changed item to every requirement, variant and test it reaches, so the change board sees the full impact before it decides.
Decide with the cost in front of you
Mass, unit cost and lead time roll up the BOM automatically, so the change board sees the difference per variant and per customer in one view.
Bring products to market faster
The impact of a change takes seconds to compute instead of days, so teams try more design options early, avoid late rework and shorten their time to market.
02
What Koddex shows when a part changes
01
Every dependent item, upstream and downstream
Select a part, requirement, system element or test, and Koddex returns every item linked to it, upstream and downstream, grouped by type.
02
Assembly totals updated with the part
Quantities, unit mass and unit price roll up the BOM, so when a part changes every parent assembly shows its new total, per variant.
03
An impact list with owners and statuses
Each affected item comes back with its owner and its status, and the approved change keeps the decision and its reason in the item history.
03
Assign the task to the AI engineering system assistant.
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 engineering system assistant
▸Check what swapping supplier B on the gripper bracket affects, and prepare the change request.
- Reads the parts, requirements and tests
- Follows the links, within your rights
- Proposes it on a branch for you to sign
Done. The bracket is used in 2 variants, 3 requirements reference its mass and 7 tests verify them. I drafted the change request with this impact attached and assigned it to you for review.
Every agent action logged · scoped to the user's permissions
Who uses it
Discover more use cases
Frequently asked questions
See all questionsDependencies are typed links in your data model, not inferred from text. When you link a requirement to a component or a test to a requirement, Koddex records that link. Impact analysis follows the links you already declared, so nothing is guessed.
No. You model what you already have: import your BOM, requirements and test records, then declare the links between them. Teams typically start with one subsystem and one certification scope rather than the whole product.
No. 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 change that was hard to assess last quarter. In the demo, we run the impact analysis in Koddex on a product like yours. Your first use case is live within a month.
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