0
shared method
“Followed artistically”
« To put it kindly, requirements were followed artistically. Everyone had their own method, so nothing was tracked. »One model the project manager owns, that every team fills the same way.
Use case · Engineering · Quality & certification
Import a specification in minutes and link each requirement to its test.
On the V-model · Left branch: each requirement is verified by a test on the right branchImport a customer specification from PDF or Excel. The AI requirements engineer turns it into typed requirements, and you link each one to the system element that carries it and the test that verifies it.
10 s
to find the right information, instead of 45 min across many tools
1 click
to export the certification file
Measured at our reference customer after a year in use. Your first scope measures them on your own programme.
Watch it in 60 seconds
Requirements management · Koddex
01
Requirements as they are managed today
1
legacy intranet
Requirements live on an intranet from the 2000s
« The tool has to be simple enough for non-technical profiles, or it will not be used. »Coverage is computed, so it stops depending on who was careful.
3
months
The question about one line of the standard, still open
« Nobody knows the standard to the letter. You end up on some tiny detail that was never settled. »The reading you chose is recorded on the requirement, with its date and its author.
No requirement without a test
Koddex computes test coverage from the links, so a requirement with no verification method is visible the day it is written, not at the design review.
The spec stops drifting from the design
Requirements sit in Koddex alongside the parts and tests they constrain, so a design change shows which requirement it puts at risk.
Specifications structured instead of retyped
The AI requirements engineer reads PDF and Excel specifications and proposes typed, linked requirements that you review instead of retyping.
02
From the customer's PDF to a verified requirement
01
From a specification document to structured requirements
The agent reads the specification you upload, proposes each requirement with its type and source clause, and links it to the system elements it concerns.
02
A changed clause shows what it affects
When a standard or a customer spec changes, the requirements it reaches are flagged, with the parts and tests behind them.
03
Coverage updated when a test result is recorded
Each requirement carries its verification method and its latest result, so the coverage figure is recalculated as soon as a test is recorded.
03
Assign the task to the AI requirements 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 requirements engineer
▸Find the landing gear requirements that have no test yet.
- Reads the parts, requirements and tests
- Follows the links, within your rights
- Proposes it on a branch for you to sign
14 of 212 requirements have no verifying test, 9 of them safety-critical. I opened a task for each one and assigned them to the verification agent, which is drafting the test cases for your review.
Every agent action logged · scoped to the user's permissions
Discover more use cases
Frequently asked questions
See all questionsNot for engineering metrics. Charts are computed directly from the metamodel. If you already run Power BI or Tableau, webhooks push the same numbers into them.
As current as the data in Koddex. A change to a requirement, a baseline or a test run propagates to the dashboard as it happens, with no nightly batch.
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 one customer spec. In the demo, we show how Koddex structures a spec like yours and computes its coverage.
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