Impact analysis · Computed

Edit a product, see the entire impact path

With the Computed system, every element lives inside another element, and every attribute — mass, size, coefficient — feeds a formula. Change one characteristic on a leaf of the tree and Koddex recomputes the whole chain instantly, both directions, up to the requirement it might break.

Elements within elements, all the way down the BOM
Formula-linked attributes that propagate in a cascade
The impacted requirement is flagged before you commit

Product tree · propagation

Drone airframesystem mass

Propulsion assemblyΣ mass roll-up

Motor mountmass

Connector XLR-8mass 8 g → 11 g

Req. MAX-MASS≤ 320 g · now 322 g

The impact path, live

Impact path — EU MDR violation

Every component is bidirectionally linked at every depth. A single edit on a leaf attribute propagates an alert up the entire chain — and reverting the edit clears the chain back to green.

Root system

Sub-assembly

Component

Alert — MDR breach

Normal link

Alert path

Stable — every link green

The pain

One change, unknown blast radius

A supplier swaps a connector. It quietly touches mass budgets, three product lines and two locked baselines — but nobody can see that cascade before the change is already in.

Impact surfaces at the worst possible moment

A shared component changes and three programs discover the consequences two months later, in a regulatory review. The cascade stayed invisible until it hit.

Invisible cross-product dependencies

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.

Change committed before its consequences are known

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.

one structured graph

The Koddex way

01 / 04