Lock approved configurations structurally. Iterate safely with explicit revision lineage. Before any change is committed, see the full impact across components, requirements, calculations and baselines.
A file named v_FINAL_approved.xlsx is updated by someone who did not know it was the reference. The baseline is gone. Nobody notices until the audit.
Production runs on V1, R&D develops V2 in the same files. Work on V2 contaminates V1 references and creates confusion on the shopfloor.
A shared component is used in seven product lines. When it changes, three of them discover the impact two months later — in the worst possible review.
A material change affects biocompatibility. The corresponding ISO 10993 requirement is not flagged. The gap surfaces during regulatory submission, after the change is already in.
Lock from the bottom up. Simulate before you decide.
Koddex enforces structural coherence: a baseline cannot be locked until every referenced item is validated. Once locked, a baseline is immutable — no override, no backdoor. Before any change is committed, the system traverses the full graph of dependencies and surfaces every consequence: components, requirements, calculations, baselines and product lines impacted.
Sub-components first, then components, then the system. Koddex blocks any partial freeze and tells you exactly what is missing.
Once locked, no attribute can change. To evolve, create a revision: V1 stays intact in production while V2 develops in parallel, with full lineage and zero collision.
Change a mass, a material, a requirement status — the graph instantly shows every affected component, requirement, roll-up and locked baseline, in both directions.
Narrowed margins, broken coverage, contaminated baselines: all surfaced at the moment of decision, not three weeks before the regulatory review.
Total mass recalculates from 308g to 311g. Margin on EXG-003 (max 320g) narrows from 12g to 9g. 3 engineers notified automatically.
EXG-003 remains compliant but the margin has narrowed. An engineer must validate the tolerance is still acceptable.
All other requirements, baselines and dependent systems remain unaffected.
4 product lines reference this requirement. 2 are already compliant. 2 are not: the housing component does not meet IP67.
Locked baselines on the 2 non-compliant products cannot be modified. New revisions must be created before certification can proceed.
12 other products in the portfolio are unaffected by this requirement change.
7 assemblies across 3 product lines reference this component. All 7 have their computed mass budgets automatically updated.
2 of the 7 assemblies have locked baselines that referenced the previous material. A revision is required before revalidation.
Functional requirements and test plans are unaffected. The change is purely material, not dimensional.
Component, Requirement and Baseline types — every relation traversable for impact analysis
Revision lineage with locked baselines and live impact graph