A structured list of all items, quantities, and relationships needed to build a product or assembly in manufacturing.
A **bill of material (BOM)** is a structured list of all items required to build a specific product, assembly, or configuration. It typically includes:
– Each component, subassembly, and raw material
– Required quantities and units of measure
– Hierarchical relationships between parent and child items
– Identifiers such as part numbers, revisions, and descriptions
In industrial and regulated manufacturing, the BOM acts as a central product data structure linking engineering, planning, procurement, manufacturing, and quality records.
Common forms of BOMs include:
– **Engineering BOM (EBOM)**: Derived from product design; represents how the product is engineered (often managed in CAD/PLM). Focuses on design-valid parts and revisions.
– **Manufacturing BOM (MBOM)**: Structured for how the product is built on the shop floor, often re-grouped by operations, work centers, or kits. Used by MES and ERP for planning and execution.
– **Service or maintenance BOM**: Represents the as-designed or as-maintained structure of an asset in the field, supporting spare parts and service operations.
– **Configurable or variant BOM**: Parameterized structure that supports multiple product options and variants from a common base design.
A single product may have multiple BOM views that must be synchronized through change control.
In operational workflows, a BOM commonly:
– Drives **material planning and purchasing** in ERP/MRP systems
– Defines **what materials MES expects** at each operation or work center
– Supports **traceability**, by identifying which parts and lots can be used in a given product and revision
– Provides the **reference structure** for work instructions, routings, and quality plans
– Serves as a basis for **costing** (material cost roll-ups) and variance analysis
In regulated industries (such as aerospace, pharma, or medical devices), BOMs are tightly controlled and linked to formal change processes, approved suppliers, and documented specifications.
A bill of material:
– **Includes**: Physical components, subassemblies, raw materials, consumables, and sometimes shop-replaceable units that are required to realize the product.
– **May include** (depending on practice): Non-stock items like labels, documentation, or tooling references if they are required to deliver the defined product.
– **Does not inherently include**: Process routing, operation sequence, cycle times, or work instructions. These are typically managed in routings, process plans, or MES master data, even when displayed together with BOM information.
It also does not by itself represent inventory on hand or location; that information usually resides in inventory and warehouse management functions that reference the BOM.
– **BOM vs. routing**: A BOM defines *what* materials are needed; a routing defines *how* and *in what sequence* operations are performed. Many systems link these but store them separately.
– **BOM vs. product structure**: In some tools these terms overlap. “Product structure” may describe higher-level configuration relationships, whereas the BOM is the operational list used for planning and execution.
– **BOM vs. recipe/formula**: In process industries, a recipe or formula serves a similar role but typically includes more detailed process parameters (temperatures, times, etc.), not just material lists.
In environments such as aerospace manufacturing, BOM quality and control strongly influence inventory accuracy and traceability:
– Incorrect or outdated BOMs can lead to **over-issues or under-issues** of components versus what is planned in ERP or MES.
– Poor alignment between EBOM and MBOM can drive **workarounds on the shop floor**, such as substituting parts or adding unplanned hardware without recorded changes.
– Incomplete handling of **kits, alternates, and substitutes** in BOM data can cause mismatches between system inventory and actual consumed parts.
For these reasons, BOM management is typically integrated with change control, configuration management, and cross-system synchronization between PLM, ERP, and MES.