BOM explosion and where-used analysis: understanding requirements and dependencies

A product can contain subassemblies, and those subassemblies can contain components. Understanding only the top level can hide material requirements deeper in the structure.

BOM analysis answers two complementary questions: what a product needs, and which products depend on a particular component. These questions support planning, substitution review, and engineering changes.

Structure and explosion

A tree explains how the recipe is organised. An explosion translates the structure and quantity factors into requirements for a defined output quantity. DNA documents Tree and Explosion views for these different purposes.

If one finished assembly needs two subassemblies and each subassembly needs three fasteners, the finished assembly requires six fasteners before other defined allowances. A run of 50 finished assemblies therefore implies 300 fasteners under this simplified structure.

The calculation depends on the correct base quantities and units at every level. An error in a lower-level factor can multiply through the whole plan.

Where-used analysis

Where-used asks the reverse question: which recipes depend on this component? This is valuable when a supplier discontinues a part, a quality issue affects a material, or an engineering change proposes a substitute.

DNA's Where-Used view helps identify those dependencies. The business can then evaluate affected products and the wider implications rather than treating the component as an isolated purchasing record.

A practical shortage

A common seal is used in three pump assemblies. Purchasing learns that the next supply is delayed. Looking only at the seal's current purchase order does not explain which customer commitments may be affected.

Where-used identifies the product relationships. Planning and order information then help determine which demands depend on the delayed supply. The response may involve prioritisation, a qualified substitute, or revised delivery expectations.

Structure is not timing

A BOM explosion explains quantity relationships. It does not alone prove when components must be available or whether capacity can produce the output by the required date. Routing, lead-time, calendar, and planning information add those dimensions.

Similarly, a where-used result identifies dependency, not automatic approval to replace a component. Technical suitability and controlled version changes still matter.

Why these analyses improve decisions

The company can understand the full material consequence of an output plan and the full product consequence of a component change. That visibility reduces surprises and supports a more credible discussion between engineering, purchasing, planning, and production.