Head of Systems Engineering

    Every dependency. Every decision. One traceable graph.

    Koddex gives systems engineers a living model of their product: requirements, components, tests, and revisions, explicitly linked and always consistent.

    Systems engineer reviewing technical models on a multi-monitor workstation
    WHAT SYSTEMS ENGINEERS ACTUALLY TOLD US

    The link they need most is the one that exists in no tool they own.

    Four tools, and the certification impact counted by hand

    Requirements in a spreadsheet, parts in the PLM, CAD in a second tool, the standard as a PDF. Every design change means opening all four and working out by hand what it just invalidated.

    4disconnected tools

    PLM, CAD, the standard as a PDF, and a spreadsheet

    Changed requirement
    « worked out by hand, every time »
    Tests to re-run
    « We need requirements traceability to replace the manual spreadsheets before the launch. »
    Engineering Lead · Medical device
    When it gets paid forEvery design change

    How do you answer that today?

    One graph: changing a requirement names the tests it just invalidated.

    The standard everyone is sure about is the 2015 one

    Standards get revised a handful of times in a career, so people stay confident in the version they learned. Then two thousand units have to be built to it, by technicians nobody trained on the current text.

    2 000units to build

    to a standard that ages in people's heads

    « He was completely sure of himself — on a version of the standard that was true fifteen years ago. »
    Business Unit Director · Nuclear instrumentation
    When it gets paid forTraining the production technicians
    The standard is a dated version in the model, not a memory.

    The reliability tests do not match how customers use it

    The bench tests pass. Then the machine meets an apron in July, a night shift and an operator in a hurry, and fails in a way no test described. The gap only shows up as field returns, a year after sign-off.

    0tests in real conditions

    reliability proven on the bench only

    Bench test
    « never described anywhere »
    Real conditions
    Field return
    « Our reliability testing is not representative of the conditions the customer actually runs in. »
    Engineering Manager · Ground support equipment
    When it gets paid forField returns
    A test condition is an attribute, so a gap in it is visible before shipping.
    1. 01

      Requirements drift silently. You write requirements in Confluence or Word. Components evolve in CAD. Nobody maintains the link. Coverage gaps only surface during verification, or customer reviews.

    2. 02

      Impact analysis takes days. A change request arrives. You spend two days tracing which subsystems are affected, which tests need rerunning, which docs need updating. Manually.

    3. 03

      The model and the reality diverge. Your MBSE model is kept up to date by one expert. The actual system configuration lives in Excel. They disagree. You find out when it matters most.

    The model your team works in is the system itself.

    1. 01

      Requirements stay linked to reality.

      Every requirement is wired to the components, tests and outputs that satisfy it. Coverage gaps surface the moment they appear, not during a verification campaign or a customer review.

    2. 02

      Impact analysis in seconds, not days.

      Trace the full propagation path of any change through the graph before you commit it. No two-day manual hunt for which subsystems, tests and documents are affected.

    3. 03

      One living model, never a model and a spreadsheet.

      Configuration, requirements and revisions share a single graph. There's no second source of truth to keep in sync, because there's only one.

    METAMODELING

    Model your system the way you think about it.

    Define your own object types and relationships. Every schema is typed, validated, and reusable across programs.

    REQ-042
    COMP-17
    TEST-09
    3/3 linked

    REQUIREMENTS TRACEABILITY

    From requirement to test. No gaps.

    Link requirements to components, verification methods, and test results. Query coverage at any level of the hierarchy.

    IMPACT ANALYSIS

    Change one thing. Know everything it touches.

    Before committing a revision, trace the full propagation path through the system graph.

    Rev A
    →
    Rev B
    →
    Rev C
    →
    Rev D

    REVISIONS

    Freeze. Branch. Evolve. Without losing history.

    Every revision is linked to its predecessor. Full lineage, always intact. No folder naming conventions required.

    Related use cases

    Audit-ready traceability

    Every change traced. Click Export when the auditor arrives.

    Impact analysis

    See the full cascade of any change before you commit.

    Systems engineering across our industries

    MedTech

    Class II–III device makers under EU MDR, FDA QMSR, ISO 13485.

    Robotics

    Industrial, mobile and humanoid platforms under ISO 10218, EN ISO 13482, IEC 61508.

    Aerospace & Defense

    AS9100, DO-178C, DO-254 and EASA Part 21 programs with locked baselines.

    Nuclear & Energy

    RCC-M, 10 CFR 50 App. B, IAEA SSG-39 design control for reactor and SMR systems.

    Advanced Manufacturing

    ISO 9001 / IATF 16949 plants with structured BOMs and revision control.

    Renewable Energy

    IEC 61400, IEC 61215 and DNV-GL wind, solar and storage assets with locked baselines.

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

    Recommended reading for systems engineers

    Career & Culture

    The Systems Engineering Renaissance: Why Hardware Teams Are Rediscovering SE Fundamentals

    After years of being dismissed as bureaucratic overhead, systems engineering is experiencing a revival driven by system complexity and regulatory pressure.

    8 minRead

    Industry Trends

    MBSE in France: Where Adoption Is Real and Where It Is Still Theatre

    Toulouse and Saclay are pulling ahead. Most of the rest of France is still running on Word documents. The gap is now structural.

    7 minRead

    Industry Trends

    The V-Model Is Not Dead. It Has Evolved. Here's What It Looks Like in 2026

    Reports of the V-model's death have been greatly exaggerated. Modern hardware teams are adapting it with graph-based traceability and iterative loops.

    8 minRead