Introduction
The Bill of Materials (BOM) is the backbone of every manufactured product. It connects design intent to procurement, manufacturing planning, cost analysis, and service documentation. And yet, BOM management is one of the most consistently neglected areas of engineering practice — not because engineers don’t understand its importance, but because the tools and processes involved span multiple systems and organizational functions that don’t always communicate cleanly.
This article covers what design engineers specifically need to understand about BOM structure, how to maintain BOM accuracy through design changes, and how to work effectively with the downstream functions — procurement, manufacturing, ERP — that depend on BOM data.
BOM Types: Understanding What You’re Working With
“The BOM” is not a single entity. Multiple BOM types exist in most manufacturing organizations, each serving a different purpose. Engineers who confuse them create problems for the functions that depend on each type’s accuracy.
Engineering BOM (EBOM)
The EBOM is owned by the design engineering team. It represents the product as designed — part numbers, revision levels, quantities, materials, and the hierarchy of assemblies and sub-assemblies. The EBOM is the output of the CAD environment and PLM system. It is structured around design intent, not manufacturing process.
Manufacturing BOM (MBOM)
The MBOM is derived from the EBOM and restructured to reflect how the product is actually built. Manufacturing sequences, work center routing, phantom assemblies (intermediate configurations that exist during build but are not a stocked unit), and tooling are added to the MBOM. The MBOM is owned by manufacturing or industrial engineering, but it originates from the EBOM — so errors or omissions in the EBOM propagate directly into the MBOM.
Service BOM
The service BOM is structured around the field-replaceable units (FRUs) that service technicians will actually order. It may differ significantly from both the EBOM and MBOM — service BOMs often group sub-assemblies into larger line-replaceable units, omit manufacturing-only consumables, and include service-specific part numbers.
BOM Structure: The Design Decisions That Matter
How you structure the EBOM has downstream consequences that are not always obvious from a pure design perspective. Key structural decisions:
Assembly hierarchy depth
Deep hierarchies (many levels of sub-assembly) make the BOM more modular — they allow sub-assemblies to be changed, tested, and reused independently. Flat hierarchies (all parts under a single top-level assembly) are simpler to manage but create problems when sub-assemblies are shared across multiple products or when you need to make a change that affects only one of several products sharing a common sub-assembly.
The right depth is driven by: whether sub-assemblies are independently testable or procurable units; whether sub-assemblies are shared across multiple end products; and whether sub-assemblies go through separate manufacturing operations (an assembly that gets painted as a unit before being installed in a higher assembly should be its own BOM level).
Make vs. buy designation
Every item in the EBOM should be designated as either a make item (manufactured in-house or by a supplier from design drawings) or a buy item (procured as a standard catalog item). This designation drives procurement and planning strategies. Errors in make/buy designation — particularly calling a buy item a make item — result in procurement trying to source a part number that no supplier recognizes.
Reference designators and find numbers
In assemblies with many instances of the same part (fasteners, identical brackets), find numbers or reference designators identify the specific location in the assembly where each instance of the part is used. These are important for manufacturing instructions and service documentation. Maintaining accurate find numbers through design changes is tedious but critical for traceability.
Version Control and Revision Management
BOM revision control is one of the most error-prone aspects of product data management. Common failures:
- Releasing a drawing revision without updating the BOM to reflect the new revision level
- Changing a part in multiple product BOMs but missing one — creating a product with a mix of old and new part revisions
- Consuming BOM data at an incorrect revision level during manufacturing because the released revision wasn’t effectively communicated to the shop floor
Effective revision management practices
- Use a PDM/PLM system: Manual BOM management in spreadsheets creates version control problems that are nearly impossible to sustain accurately as product complexity grows. A PDM system enforces revision control and makes the current released BOM the single source of truth.
- Separate unreleased from released BOMs: In-design BOMs (work-in-progress) should be clearly distinguished from released BOMs (approved for manufacturing). Never mix revision levels from in-design and released status within a single BOM.
- Link BOM revisions to ECO (Engineering Change Order) numbers: Every change to a released BOM should be traceable to a specific change order. This provides the audit trail needed for quality systems and customer audits.
Engineering Change Integration
Design changes are inevitable. How changes are integrated into the BOM determines whether the engineering change is effectively implemented or silently lost in the translation from design to manufacturing.
The engineering change process
- Change Request: Identify and document the need for a change, with reason, affected parts, and preliminary impact assessment
- Impact Analysis: Assess which BOMs, drawings, test specifications, and downstream documentation are affected — including products that share the affected part
- Change Authorization: Obtain approvals from affected functions (design, manufacturing, quality, procurement, customer if required)
- Implementation: Update drawings, BOM, and related documentation simultaneously — not sequentially with gaps
- Effectivity: Define the effectivity point (serial number, date, or lot) at which the change takes effect in production
- Communication: Notify manufacturing, procurement, and service of the change and its effectivity
BOM Structure Reference
| BOM Type | Owner | Primary Users | Key Content |
|---|---|---|---|
| Engineering BOM (EBOM) | Design Engineering | Design, PLM, procurement | Part numbers, revisions, quantities, materials, hierarchy |
| Manufacturing BOM (MBOM) | Manufacturing/Industrial Eng. | Production, planning, ERP | Build sequence, work centers, phantom assemblies |
| Service BOM | Service Engineering | Service, spare parts, customers | Field-replaceable units, service part numbers |
| As-Built BOM | Quality/Manufacturing | Quality, service, regulatory | Actual parts (with serial/lot numbers) used in specific unit |
Common BOM Errors and Their Consequences
- Wrong quantity: Procurement orders insufficient parts; production line stops waiting for material
- Wrong revision level: Obsolete parts are manufactured or purchased; new revision is not implemented
- Missing items: Parts are not ordered; discovered at assembly; emergency procurement at premium cost
- Incorrect make/buy: Procurement cannot source a make part; or manufacturing produces a part that should be purchased
- Phantom assembly errors: Manufacturing builds incorrect sub-assemblies; inventory records incorrect
FAQ
Q: Who is responsible for maintaining the BOM — design engineering or a dedicated data management team?
A: This varies by organization. In most manufacturing companies, design engineers own the EBOM and are responsible for keeping it accurate through design changes. A dedicated document control or PLM administration team may manage the system infrastructure, enforce release workflows, and audit BOM quality. The designer cannot delegate accuracy — if your drawing changes, you are responsible for ensuring the BOM reflects that change before the next manufacturing release.
Q: How should I handle a part that is used in multiple products — do I change it everywhere simultaneously?
A: When you change a shared part (a part used in multiple product BOMs), the change affects all products simultaneously by definition. The impact analysis step of the ECO process must identify all affected products, and all affected BOMs must be updated at the same time as the drawing. If the change is appropriate for all products using the part, update all BOMs. If the change is appropriate only for one product, the part must be given a new part number (effectively making it a new part) so the other products continue to reference the unchanged original.
Q: What is the right level of detail for a BOM — should I include every fastener and seal?
A: Yes, for a complete EBOM used for procurement and manufacturing planning. Every purchased item that must be procured (including fasteners, seals, adhesives, and consumables) should appear in the BOM with the correct quantity. Items that are process materials (grinding wheel, cutting fluid) and not incorporated into the finished product may be handled separately in a process plan rather than the BOM. The practical test: if production would run short without ordering it, it belongs in the BOM.
コメント