Multi-level BOMs with computed roll-ups, bidirectional requirements coverage, and a complete lifecycle history — in one structured graph. From the smallest part to the system, from the first requirement to the certified delivery.
Mass, cost and quantity roll-ups are recomputed across spreadsheets at every change. Variants drift in parallel files. Nobody is sure which one is current.
The traceability matrix is a one-person spreadsheet, always slightly stale. Coverage gaps surface during certification review, not during development.
Why a material changed eight months ago lives in a closed Jira ticket and an old email thread. Reconstruction before an audit takes days.
When a component changes at depth 5, no one knows which requirements, baselines or earlier decisions are impacted until someone traces it manually.
One graph. Parts, requirements and history connected by construction.
Koddex models parts, assemblies, requirements and decisions as typed objects in the same graph. Roll-ups (mass, cost, coverage, completion) are computed at any depth. Requirements are linked bidirectionally to the components that cover them. Every modification is automatically logged with actor, timestamp, old value and new value. The matrix, the BOM tree and the design history file are three views of the same source of truth — never reconstructed, always current.
Define Part and Assembly types once. Mass, cost, quantity and any custom attribute roll up automatically across every level — depth 2 or depth 10, 1 variant or N.
Requirements are typed items linked explicitly to the components that cover them. Coverage rate is live. Gaps are visible from day one, navigable component → requirement and back.
Every change to every item is timestamped with the actor and the diff. No manual effort. The full history is queryable in seconds, not weeks.
From any part, jump to the requirements it covers, the baselines it belongs to, and every revision it went through. From any requirement, see every component, test and decision in its chain of evidence.
Part, Assembly, Requirement and Revision types — one graph, computed roll-ups and bidirectional coverage
item.mass_g + item.sub_components::MAP(.total_mass_g)::SUM()Recursive BOM tree with live requirements coverage and lifecycle log