← Use Cases

    The knowledge leaves with the people. A model that outlives the team.

    How the programme actually works lives in a spreadsheet one person wrote and in the memory of three more. Koddex makes it a model the organisation owns.

    WHAT LEAVES WHEN THEY DO

    What walks out of the door when they do.

    You acquired the company. You did not acquire how it works

    The acquisition closed in July. Two months on, nobody at group level knows which tools or which processes the subsidiary's quality team actually uses. The only way to find out is to ask them, in a meeting.

    1subsidiary

    acquired, its processes still undocumented

    « We still do not know exactly which tools and processes the subsidiary uses. »
    Operations Lead · Robotics
    When it gets paid forPost-acquisition integration

    How do you answer that today?

    The process is a model in the graph, so it survives the people.

    “Followed artistically”

    No PLM. Each project manager tracks the standards their own way, in their own Google Docs and spreadsheets. Which means nothing is tracked. Finding out what was decided means finding the person who decided it.

    0shared method

    one per project manager, so none

    « To put it kindly, requirements were followed artistically. Everyone had their own method, so nothing was tracked. »
    Business Unit Director · Nuclear instrumentation
    When it gets paid forA project manager resigns
    One model the project manager owns, that every team fills the same way.

    One reactor, one spreadsheet

    Configuration management for a reactor programme lives in a single spreadsheet. It holds, because the people who wrote it are still there. Nobody has asked what happens when they are not.

    1spreadsheet

    for the configuration of a whole reactor programme

    « We need to get professional about this. »
    Project Director · Nuclear engineering
    When it gets paid forEvery new programme
    Configuration is a locked structure, not a file someone maintains.
    Novae Systems / US Probe US-300
    • US Probe US-300COMPUTED 308 g
    • Piezo Transducer PZT-7COMPUTED 53 g
    • Piezo Element PZT-5H×118 g
    • Acoustic Matching Layer×28 g
    • Absorbent Backing×112 g
    • Silver Electrodes×21 g
    • Ergonomic Housing IP67×1180 g
    • Shielded Coaxial Cable 2 m×155 g
    • M-Series Connector×18 g
    • PVDF Acoustic Lens×112 g
    Requirements coverage67%
    • EXG-001Frequency 7.5 MHzcovered
    • EXG-002Sealing IP67covered
    • EXG-005Sterilization cyclenot covered

    The Koddex way

    The method becomes a model: typed objects, required attributes and relationships that every team fills the same way.

    1. 01

      The project manager owns the model

      Define the objects, attributes and relationships your programme needs. Teams fill them in; they cannot invent a shape of their own.

    2. 02

      Decisions carry their reasoning

      Every change records who, when and why, attached to the item rather than to a thread, so the rationale survives the author.

    3. 03

      The standard is a dated version, not a memory

      Reference the revision of the standard an item answers to, so training and production follow the text in force instead of the one someone learned.

    4. 04

      An acquired team inherits a structure

      Model their process once and it becomes visible and comparable at group level, instead of staying tacit until somebody asks.

    Measurable Outcomes

    BeforeAfterContext
    One convention per project managerOne model the whole programme fillsStructure, not discipline
    A reactor configuration in a spreadsheetA configuration under revision controlIt survives its author
    Rationale lost in email threadsRationale attached to the itemWho, when and why
    Technicians trained on a 2015 standardThe version in force, datedOn the item itself

    Performance Impact

    1
    Model per programme, not per person
    0
    Decisions that live only in a head
    Dated
    Standard version on every item
    Queryable
    Rationale behind every change
    SE
    HE
    Q/
    TE
    VE
    PM
    Koddex

    Drive complex systems without frictions.

    Stop bleeding hours on version chasing, audit prep and cross-team sync. Ship certified hardware faster, on a foundation built for the next decade of complexity.

    Enterprise-grade security. Library of certification-friendly templates. Custom deployment for teams of 200+.