Every system you delivered, documented and versioned for years.
The three questions behind every delivered system
- 1What exactly runs at this customer site today?
- 2Which requirement does this component answer, and where is the proof?
- 3What changed since commissioning, when and why?

Your deployment records live in Excel, Drive and Word.
- One spreadsheet per project, one folder per site, one version per person
- Requirements and components linked by hand, if at all
- The as-built known only by the engineer who commissioned it
- Years later, nobody knows which revision runs where
- One record per delivered system, on one backbone
- Each requirement linked to its component and sub-component
- The configuration frozen at commissioning, then revised with every change
- Any two revisions compared side by side, years later
What engineering teams told us in demos.
« Come back three years later and you can't find anything. You rebuild it from memory. »
« Production has built ten of these systems. We need to know which version of the product was made. »
« I started making component and function matrices in Excel, and it's a mess. »
The agent does the work. The engineer keeps the decision.
- Read the as-built recordqueued
- Link to requirementsqueued
- Compare with the designqueued
SN-0412 · as-built vs design
Link each requirement to the part that answers it.
Freeze what you delivered, site by site.
Find any revision, years later.

Exotec runs its systems on Koddex, on three continents.
- 1,000+
- users in Koddex at Exotec
- 20
- partner organisations working in the same backbone
- up to 30%
- of engineering time freed up
- 1 day
- for a change impact analysis, instead of 2 weeks
From the tender to the installed base, one project at a time.
Frequently asked questions
See all questionsEach delivered system can be frozen: its components are locked, then the system itself. Later changes become new revisions with their full lineage, which you compare side by side, and each customer site keeps its own configuration.
Yes. Every table imports CSV, and BOMs and specifications can come from structured or unstructured files or through the API. The Koddex team loads your data with you at the start, so nobody types it again by hand.
No. Koddex is the engineering backbone that sits with your CAD, PLM and ERP, not instead of them. It centralizes requirements, BOM, documents and every change on one graph, so each system you deploy stays traced, and it connects to PLM, QMS, ERP and MES platforms through its API.
A Koddex deployment engineer sets up your first use case on site in under 3 days, and you see the value within two to three weeks, with 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.
