Deployment record

Every system you delivered, documented and versioned for years.

Koddex keeps each delivered system as a living record: its requirements linked to the components and sub-components that answer them, its configuration frozen at commissioning, and every revision since. Years later, you know exactly what runs at each site.
Simulated example: system, sites and numbers are fictitious.

The three questions behind every delivered system

  1. 1What exactly runs at this customer site today?
  2. 2Which requirement does this component answer, and where is the proof?
  3. 3What changed since commissioning, when and why?
An engineer with a tablet on a factory floor during commissioning

Your deployment records live in Excel, Drive and Word.

Today
Scattered. Outdated.
  • 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
With Koddex
Recorded. Versioned.
  • 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. »
Former R&D director, imaging equipment group
« Production has built ten of these systems. We need to know which version of the product was made. »
Controls engineering manager, automation integrator
« I started making component and function matrices in Excel, and it's a mess. »
Production manager, industrial equipment maker
Heard in our demo meetings, 2026. Anonymised.
AI agent

The agent does the work. The engineer keeps the decision.

It works within your permissions, on the data of the backbone, and every action is logged. Nothing goes out before an engineer approves it.
app.koddex.io · AI agents
AI configuration engineerReady
Freeze SN-0412 as delivered at the Lyon site, link each component to its requirements and compare it with the design.SN-0412 · LyonCPR-400 rev D · commissioned 2025-03-14
  1. Read the as-built recordqueued
  2. Link to requirementsqueued
  3. Compare with the designqueued

SN-0412 · as-built vs design

ItemAs builtStatus
    Simulated example
    01

    Link each requirement to the part that answers it.

    Requirements are allocated to components and sub-components, with the test or document that proves each one. Coverage is computed, not checked by hand.
    02

    Freeze what you delivered, site by site.

    At commissioning, the system is frozen as built: components, revisions, firmware and gaps against the design.
    03

    Find any revision, years later.

    Each later change becomes a new revision with its reason and its approval, so maintenance and upgrades start from what is really installed.
    Exotec

    Exotec runs its systems on Koddex, on three continents.

    Exotec, the French leader in robotic storage systems, designs, delivers and keeps its systems traced in Koddex, with its partners, across 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
    2 weeks
    1 day
    for a change impact analysis, instead of 2 weeks
    Figures from Exotec. 1 day: measured after a year in use. We walk through the calculation on your perimeter during the demo.

    Frequently asked questions

    See all questions

    Each 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.

    Let's see what Koddex changes on one of your projects.

    Bring a project you just sold. 20 minutes, on an example close to your systems.

    We use cookies to keep the site running and to understand how it's used so we can improve it, like most sites do. Read the cookie policy