← Use Cases

    Three teams, three tools, no structure all three can write into.

    One single, always-current source of truth, so version conflicts and misaligned data stop causing delays.

    BEFORE ANY OF THIS WORKS

    What three teams on three sites actually told us.

    A hundred and twenty engineers, no technical data tool

    The R&D team grew to a hundred and twenty people without ever acquiring a technical data management tool. Files have no revision stamp, so nothing is searchable and nothing can be shown to be compliant.

    0tools

    for 120 people in R&D

    « We have no technical data management tool at all. Searching and proving compliance are both hard. »
    Technical Director · Medical components
    When it gets paid forEvery compliance request

    How do you answer that today?

    Structure first, then the search works because the data has shape.

    Three sites, three continents, one machine

    The same machine is configured and built on three continents. Each site rebuilds the bill of materials line by line from the others' exports, because there is no structure all three can write into.

    3sites

    no shared source, BOMs retyped line by line

    « If it is complicated, people simply do not do it. »
    Engineering Manager · Ground support equipment
    When it gets paid forEvery site synchronisation
    One workspace the three sites write into, not three that export.

    Three bills of materials pretending to be one

    Engineering, process and production each need a different view of the same product. There is one BOM, so aligning them means rewriting drawings that did not need to change — and the engineering office absorbs it.

    3views, one BOM

    so every change means redrawing

    CAD model
    Engineering BOM
    « the same list, three jobs »
    Process BOM
    Production BOM
    « Aligning the engineering and production BOMs forces pointless drawing updates that overload the engineering office. »
    Hardware Manager · Medical gas equipment
    When it gets paid forEvery engineering change
    One structure, three views. Each discipline reads what it needs.

    Author the BOM you actually ship, then lock it without freezing your team.

    Define your engineering objects once with typed attributes. Compose the product BOM from those models. Lock the structure for audit, revise with full lineage, submit edits without breaking certification.

    Model · Engineering object
    v0.3 · draft
    nameCARDIAC_PUMP_PCB
    Attributes (5)
    • textPart Numberrequired
    • numberMasskg · float
    • enumLifecycle StatusDraft / Released / EoL
    • refSupplier→ Vendor
    • docDatasheetPDF · controlled
    Bill of Materials · Pump v2.4
    Submitted Mar 12
    • PUMP-PCB-A4· Rev 2.4Locked
    • MTR-DC-32· Rev 1.0Locked
    • BAT-LiPo-1200· Rev 0.3 → Rev 0.4Revising
    • ENC-Optical-512· Rev 1.2Locked
    • FW-Pump-Core· Rev 0.9Draft

    Define once → Reuse across the BOM → Lock & revise with lineage

    Lock once. Revise safely. See the impact before you commit.

    A locked baseline is structurally immutable. To evolve, you create a revision, and every change is impact-analysed before it lands.

    Configuration draft, every attribute editable
    koddex.app · MED-SYS-001 · baseline manager
    v1.0draft

    v1.0 · attributes

    • REQ-22

      Biocompatibility

      ISO 10993-1
    • ACT-J3

      Joint Actuator J3

      612 g
    • PWR-04

      Power Module

      12 V / 5 V
    • SHL-05

      EMC Shield

      60 dB
    • SEAL-06

      IP67 Seal

      IP67

    Certification-friendly templates for complex systems

    Start from templates tuned to the standards each market demands, so structure, formulas, limits and evidence are wired to the certification from day one.

    See the templates for each sector

    The Koddex way

    Model the BOM together, lock and revise on branches, start from certified templates.

    1. 01

      Model the BOM as one live tree

      Build your product structure once, collaboratively: every discipline edits the same live model, no exports, no "which file is current".

    2. 02

      Requirements at every level

      Attach requirements from the system down to the leaf component, with coverage computed live so gaps surface on day one, not at submission.

    3. 03

      Lock, branch and revise safely

      Freeze a baseline, keep V1 in production, and revise V2 on its own branch with full lineage and zero collision.

    4. 04

      Start from certification-ready templates

      Spin up new programs from reusable, sector-tuned templates so you ship certified products fast, not from a blank sheet.

    Performance Impact

    1
    Live BOM model
    0
    V1 / V2 collisions
    ÷3
    Time to certified release
    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+.