Bill of Materials (BOM)

From ERPEDIA, the independent ERP knowledge base

A Bill of Materials (BOM) is a comprehensive list of raw materials, components, sub‑assemblies, and quantities required to manufacture a finished product. It is a fundamental data structure in manufacturing ERP systems, serving as the basis for MRP, costing, and production planning. This article covers BOM types, structures, and best practices.

1. What is a BOM?

A Bill of Materials defines:

  • All components (raw materials, sub‑assemblies) needed to make a product.
  • Quantities of each component (e.g., 4 wheels per car).
  • Hierarchical relationships (if multi‑level).
  • Reference designators (where components go).

The BOM is used by MRP to calculate material requirements, by costing to determine product cost, and by production to guide assembly.

Analogy: A BOM is like a recipe – it lists all ingredients (materials) and quantities needed to bake a cake (finished product).

2. Types of BOM

TypeDescriptionUse case
Single‑levelLists only components directly needed for a product, without sub‑assemblies.Simple products, high‑level planning.
Multi‑levelShows hierarchical structure with sub‑assemblies and their components.Complex products (e.g., cars, electronics).
Engineering BOMCreated by engineering, based on CAD/design. Often different from manufacturing BOM.Product development.
Manufacturing BOMUsed on shop floor – includes all items needed for production.Production execution.
Phantom BOMTransient sub‑assembly that is consumed immediately.Intermediate steps not stocked.
Template BOMGeneric BOM for configurable products (e.g., with options).Configure‑to‑order.

3. Single‑level BOM

A single‑level BOM lists only the components directly needed for a product. Example for a "Desk Lamp":

Finished product: Desk Lamp
- Base (plastic) – 1 pc
- Bulb (LED) – 1 pc
- Wiring kit – 1 set
- Shade – 1 pc

This is simple but doesn't show that the wiring kit itself has components (wire, plug, switch).

4. Multi‑level BOM

A multi‑level BOM shows the hierarchical structure. The same desk lamp with a wiring kit sub‑assembly:

Desk Lamp (Level 0) Base (plastic) – 1 pc Bulb (LED) – 1 pc Wiring kit – 1 set (Level 1) Wire – 2m (Level 2) Plug – 1 pc (Level 2) Switch – 1 pc (Level 2) Shade – 1 pc

MRP "explodes" the multi‑level BOM to calculate requirements for all levels.

5. Engineering vs Manufacturing BOM

Engineering BOM (EBOM): Created by product design teams, often from CAD systems. It reflects how the product is designed, which may differ from how it's built.

Manufacturing BOM (MBOM): Used on the shop floor. It includes all items needed for production, such as consumables, packaging, and instructions. It may also reflect assembly sequence.

ERP systems often need to manage both and synchronize changes (engineering change orders).

6. Phantom BOM

A phantom BOM represents a sub‑assembly that is consumed immediately in the next production step and never goes to stock. Example: In furniture manufacturing, you might assemble a drawer (sub‑assembly) and immediately attach it to a desk. The drawer is never stored as inventory.

Benefits:

  • Simplifies planning – MRP plans the components directly.
  • Avoids unnecessary inventory movements.
  • Common in repetitive manufacturing.
Note: Phantom BOMs are sometimes called "blow‑through" or "transient" BOMs.

7. BOM in MRP

Material Requirements Planning (MRP) uses the BOM to calculate component requirements. The process is called BOM explosion:

  1. MRP starts with demand for finished goods (sales orders, forecasts).
  2. It looks at the BOM for each finished good.
  3. It multiplies demand by component quantities to get gross requirements.
  4. It subtracts inventory and scheduled receipts to get net requirements.
  5. It repeats for each level of multi‑level BOM.
BOM explosion example:
Demand: 100 tables
BOM: 1 table top + 4 legs
On‑hand: 20 tops, 50 legs
→ Net requirements: 80 tops, 350 legs

8. Best practices

  • Maintain accuracy: BOM errors cause production delays and stock issues.
  • Use consistent units of measure: Ensure component quantities are in the right UOM (each, kg, meter).
  • Manage engineering changes: Have a formal process for BOM updates.
  • Structure for planning: Design BOM levels to match your manufacturing process.
  • Include all components: Don't forget packaging, labels, consumables.
  • Regular audits: Cycle‑count BOM accuracy by comparing to physical builds.

Key Takeaways

  • BOM is a complete list of components and quantities needed to make a product.
  • Single‑level BOM is flat; multi‑level BOM shows hierarchical relationships.
  • Engineering BOM (design) vs Manufacturing BOM (production) may differ.
  • Phantom BOMs handle transient sub‑assemblies not stocked.
  • MRP uses BOM explosion to calculate material requirements.
  • Accurate BOMs are critical for manufacturing efficiency and costing.

What is a BOM level? The hierarchical position in a multi‑level BOM. Level 0 is the finished product, Level 1 are direct components, Level 2 are components of sub‑assemblies, etc.

What is a where‑used list? A report showing all products that use a particular component. Inverse of BOM.

How often should BOMs be updated? Whenever there's an engineering change. Regular audits (e.g., quarterly) are recommended.

Continue Reading in ERPEDIA

ERPEDIA is maintained by Professionals Lobby as an independent ERP knowledge initiative focused on reducing ERP implementation risk in the UAE and GCC.
For structured, vendor‑neutral ERP advisory → Speak with an independent ERP advisor.