ERP Core ConceptsGlossary

What Is BOM (Bill of Materials)?

Also known as: bill of materials, product structure, parts list

Definition

A BOM (bill of materials) is the structured, hierarchical list of components, sub-assemblies, and quantities required to produce one unit of a parent item, and it is the primary input MRP explodes to calculate material requirements.

BOM (Bill of Materials) Explained

A bill of materials is a parent-child structure, not a flat list. Each line records the component item, the quantity per parent, a unit of measure, an operation sequence that ties the component to the routing step where it is consumed, a scrap or yield factor, and effectivity dates. Multi-level bills nest: a finished assembly points to sub-assemblies, which point to their own components, down to purchased raw material. MRP walks this tree level by level, which is why structural integrity matters more than any single field.

Different bill of materials views serve different consumers. The engineering bill reflects design intent and often mirrors the CAD structure. The manufacturing bill reflects how the shop actually builds, including packaging, consumables, and phantom levels that exist only to organize the structure and are blown through by MRP rather than stocked. Costed bills roll material, labor, and overhead upward to produce a standard cost. Confusing engineering and manufacturing bills is a leading cause of shortages, because the design structure rarely includes shop supplies or the extra material lost to setup scrap.

Effectivity control is how bills change without breaking history. Date effectivity turns lines on and off by calendar date, while serial or lot effectivity ties changes to specific units, which is standard in aerospace and defense where a configuration must be reproducible years later. Engineering change orders drive these updates, and a disciplined change process is what allows you to answer the question of exactly what was in the unit shipped 30 months ago.

Scrap factors and yield deserve particular attention because they compound. A five percent component scrap factor at three consecutive levels does not add to fifteen percent, it multiplies, and on a high-volume assembly that difference is real money sitting in excess raw material. Many shops set scrap factors once during implementation from a supplier estimate or an engineer's guess and never revisit them against measured yield, leaving MRP quietly over-ordering for years while the finance team hunts for the cause of persistently unfavorable material usage variance.

Why It Matters

  • The bill of materials is the direct input to MRP, so a wrong quantity per assembly multiplies into every purchase order for that component.
  • Costed bills determine standard cost, which sets inventory valuation and every variance the plant is measured on.
  • Configuration control on bills is a hard requirement for AS9100, ITAR, and most defense contracts, where as-built traceability is auditable.
  • Engineering and manufacturing bill divergence causes shortages that look like supplier failures but are actually data defects.

In Practice

Worked example: an assembly consumes four fasteners per unit, but the bill lists quantity per as 1 with unit of measure box of 100. MRP then plans one box per unit and purchasing buys 100 times the true need. Always validate that quantity per and unit of measure are consistent with the purchasing unit of measure and any conversion factor, especially on parts bought in packs.

Frequently Asked Questions

What is a phantom BOM?

A phantom is a bill of materials level that exists for structural clarity but is never stocked or ordered. MRP blows straight through it, passing requirements to its components. Phantoms are common for kits and transient sub-assemblies that go directly into the next operation. The gotcha is that if a phantom ever gets stocked, inventory accuracy breaks in ways that are hard to trace.

How many BOM levels is too many?

There is no hard limit, but every level adds an MRP netting pass, a potential inventory transaction, and a place for error. Levels should exist where you genuinely stock, cost, or transact a sub-assembly. If a level is never counted, never sold, and never sits on a shelf, it is usually better modeled as a phantom or flattened into the parent.

Working with BOM (Bill of Materials) in a live environment? Our engineers do this every day - and our AI agents automate most of it.