1
subsidiary
You acquired the company. You did not acquire how it works
« We still do not know exactly which tools and processes the subsidiary uses. »The process is written down in Koddex as a model, so it stays when the people who knew it leave.
Use case · Engineering · Project management
Keep the reason for each design decision on the item it concerns.
On the V-model · Operations to the next V: design decisions stay with the productKoddex keeps each decision, its rationale and its history on the part or requirement it concerns, instead of in email. New engineers can read why a value was chosen, and the AI agents answer from the same records.
1 month
to model every business process
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
Knowledge continuity · Koddex
01
The method that lives in one person's head
1
spreadsheet
One reactor, one spreadsheet
« We need to get professional about this. »Configuration is a locked structure, not a file someone maintains.
2
product lines
Two product lines, two standards, nothing shared
« The unit that works only for defence has military standards. It has nothing like the same things to comply with. »One model, two baselines. Inheritance is traced, not retyped.
Decisions stay when people leave
Each decision is kept on the element it concerns, with the reason and the change request behind it.
Onboarding from the product data
A new engineer opens a part and reads its history, its requirements and its decisions, instead of asking the one person who remembers.
Context the agents can use
Because the knowledge is structured, AI agents use it when they work on a task, within your permissions, instead of guessing from documents.
02
Knowledge kept where the work happens
01
Your processes, modelled in Koddex
Your team models its processes in Koddex, with their steps, objects and rules, so the next team reads them instead of rebuilding them.
02
Each decision kept with its reason
Every revision records the decision and its reason, so six months later anyone can see which decision caused which effect.
03
The configuration handed over, complete
When a programme changes hands, its configuration, its decisions and their history go with it in one export.
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
▸Find out why the gripper tolerance is 0.05 mm.
- Reads the parts, requirements and tests
- Follows the links, within your rights
- Proposes it on a branch for you to sign
It was tightened in rev B after a field return on the V1 fleet. The change request links the failed test and the requirement it protects. I added both to the part's comments so the next engineer finds them.
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 the process only one person knows. In the demo, we show how Koddex keeps a process and its decisions on the items they concern.
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