← Use Cases

    Ship on time. Every time.

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

    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 pain

    The BOM lives in spreadsheets, not a model

    Your product structure is scattered across CAD exports and spreadsheets. Nobody can model it, branch it, or trust it as the single thing the whole team builds from.

    No safe way to revise without breaking production

    R&D edits the same files production runs on. There's no branch, no lock, no clean way to revise V2 while V1 keeps shipping, so every change is a risk.

    Requirements don't reach every level

    Top-level specs never connect down to the sub-components and tests that must satisfy them. Coverage gaps stay hidden until far too late.

    Every program starts from a blank sheet

    With no reusable template, each project re-models the same structure and re-derives the same certification scaffolding by hand, slowly.

    one structured graph
    The Koddex way
    01 / 04

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

    02 / 04

    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.

    03 / 04

    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.

    04 / 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+.