BOM

Core meaning

BOM (bill of materials) is a structured list that defines all items required to build, test, and package a product or configured item. It typically includes:

– Components and subassemblies
– Raw and semi-finished materials
– Standard parts (e.g., fasteners, fittings)
– Consumables when they are controlled (e.g., adhesives, sealants)
– Documentation and references needed for release (e.g., drawings, specs)

A BOM usually specifies quantities, units of measure, revision or version identifiers, and relationships between parent items and child components.

Use in manufacturing and regulated operations

In industrial and regulated environments, a BOM commonly refers to one or more of the following structures:

– **Engineering BOM (EBOM)**: Product definition from design/engineering, aligned to drawings and design intent.
– **Manufacturing BOM (MBOM)**: Product definition aligned to how the product is built, sequenced, or grouped on the shop floor.
– **Service or maintenance BOM**: Parts and assemblies needed to maintain, repair, or overhaul the product.

In practice, BOMs are used to:

– Drive material planning and procurement in ERP/MRP
– Define what must be issued to, and consumed on, work orders in MES
– Support configuration control and variation management (options, variants, effectivity)
– Provide traceability for components and materials in quality and compliance records

BOM in MES, quality, and configuration control (site context)

Within MES and quality systems, especially in high-regulation sectors such as aerospace:

– The BOM identifies **which part numbers and revisions** are valid for a given product or work order.
– MES may compare **actual components scanned or recorded on the line** against the BOM to detect:
– Wrong part numbers
– Wrong revisions or superseded parts
– Missing required components
– Alerts can be configured when a build deviates from the approved BOM, supporting scrap prevention and nonconformance control.
– BOM information is often linked to **routing/operations**, **process plans**, and **specification documents** to ensure the right material and documentation are used together.

Boundaries and exclusions

– A BOM defines **what** items are required, not **how** they are processed. Operation steps, machines, and process parameters are typically defined in routings, travelers, or work instructions, not in the BOM itself.
– A BOM is not the same as:
– A **routing** or process plan (sequence of operations and resources)
– A **recipe** (parameterized processing instructions, often for process industries)
– A **production schedule** (timing and quantity of planned orders)

However, all of these structures usually reference or depend on a consistent, controlled BOM.

Common variations of BOM structures

Organizations may define specialized BOM types, such as:

– **Configurable or variant BOM**: Supports options and variants, often used with configuration rules.
– **Phantom BOM**: Logical grouping of items used for planning, not built as a separate stockkeeping unit.
– **As-planned, as-released, as-built, and as-maintained BOM views**: Different life-cycle views of the same product, important for traceability in regulated industries.

Terminology and exact behavior can differ by ERP/MES vendor, but all of these remain specific ways of structuring the underlying bill of materials.

Common confusion and misuse

– **BOM vs. part list on a drawing**: A drawing parts list may be one representation of a BOM, but in most controlled environments the master BOM is maintained in a PLM, PDM, or ERP system, with drawings acting as a reference.
– **BOM vs. inventory list**: A BOM specifies what is required for one unit (or another defined quantity) of a product. Inventory lists show what is available in stock, regardless of any single product.
– **BOM vs. specification**: Specifications define requirements (e.g., material properties, tolerances). The BOM references which materials or parts are used to meet those requirements, but does not replace the specs themselves.

Understanding these boundaries helps keep engineering change, MES configuration, and quality records aligned around a single, controlled definition of the product structure.