Product Structure and Bill of Materials

Introduction

Material Requirements Planning (MRP) converts a production plan into time-phased requirements for components, subassemblies, raw materials and purchased parts. The central information structure enabling this conversion is the product structure, usually represented operationally through a bill of materials (BOM).

A BOM is not merely a parts list. It is a controlled description of how items are related, in what quantities they are required, and under which engineering, manufacturing or configuration conditions they are valid. Errors in a BOM can produce shortages, excess inventory, incorrect product costing, invalid work orders and even unsafe products. Consequently, BOM management is simultaneously an engineering, operations, information-systems and governance responsibility.

This chapter examines BOM structures, BOM explosion, modular and planning BOMs, phantom assemblies, engineering changes, effectivity and product configuration. The treatment assumes an MRP environment in which inventory records, master production schedules, lead times and lot-sizing rules are maintained separately but interact with the BOM.

Learning Objectives

After studying this chapter, the reader should be able to:

1. Explain the role of product structure and BOM data in MRP.
2. Construct and interpret single-level and multilevel BOMs.
3. Distinguish engineering, manufacturing, modular, planning and phantom BOMs.
4. Perform a gross requirements BOM explosion and interpret the result.
5. Explain engineering-change control, effectivity and revision management.
6. Analyse configuration alternatives and their implications for planning and control.
7. Evaluate BOM data-quality, governance and implementation challenges.

1. Product Structure as the Foundation of MRP

A product structure describes the hierarchical relationship between a parent item and its immediate components. The finished product is normally placed at level 0; its direct components occupy level 1; components of those components occupy level 2, and so forth. A component may appear in more than one branch of the same product structure. Such a component is often called a common component.

A BOM record normally includes:

• parent item and component item identifiers;
• quantity per assembly;
• unit of measure;
• component scrap or yield information;
• operation or work-centre assignment, where relevant;
• revision and effectivity data;
• alternative, substitute or optional-component information;
• planning, procurement and configuration attributes.

The relationship between a parent and a component is often called a usage or component relationship. A BOM is therefore a network of item relationships, although it is commonly displayed as a tree.

Product structure versus item master

The item master describes an item as an entity: its identification, description, unit of measure, make-or-buy status, lead time, costing data and planning parameters. The BOM describes how that item is used in a parent. Confusing these two structures creates poor data ownership. For example, the item master may state that a motor is purchased, while the BOM states that two motors are used in a particular machine.

Indented and summarized views

An indented BOM displays the hierarchy and is useful for engineering and manufacturing review. A summarized BOM lists the total quantity of each component required for one parent, regardless of the level at which it occurs. The summarized quantity is useful for purchasing and material aggregation, but it hides assembly relationships and should not replace the indented view for technical analysis.

2. Types of Bills of Materials

2.1 Single-level BOM

A single-level BOM lists only the immediate components of a parent. It does not show the components within a subassembly. For a pump assembly, a single-level BOM might list a casing, impeller, shaft, seal kit and motor. The internal components of the motor or seal kit are excluded.

Single-level BOMs are useful for:

• shop-floor issue and assembly instructions;
• checking immediate component usage;
• defining one manufacturing operation or assembly stage;
• simple products with no significant subassembly structure.

2.2 Multilevel BOM

A multilevel BOM expands the product through all relevant levels. It supports MRP explosion because requirements for lower-level components depend on planned production of their parent assemblies. It also supports product costing, capacity analysis, traceability and maintenance planning.

A multilevel structure should be acyclic: an item must not, directly or indirectly, contain itself. A circular relationship prevents the planning system from determining the lowest-level requirements.

2.3 Engineering BOM and manufacturing BOM

An engineering BOM (EBOM) represents the product as designed. It may be organized by functional systems, design assemblies or CAD structures. An EBOM answers questions such as: “What components constitute the design?”

A manufacturing BOM (MBOM) represents how the product is assembled and produced. It may include manufacturing fixtures, consumables, packaging, phantoms, operation-specific materials and shop-floor assemblies. An MBOM answers: “What must production prepare, issue and assemble, and in what sequence?”

The two structures should be aligned but need not be identical. A design assembly may be invisible to manufacturing, while manufacturing may require a temporary kit or packaging assembly not represented as a functional design element. A controlled EBOM-to-MBOM transformation is therefore preferable to informal copying.

2.4 Modular BOM

A modular BOM groups components into modules that can be combined to create a range of finished products. Modules are particularly valuable where product variety is high but the number of basic modules is manageable.

For example, a configurable vehicle may contain modules for powertrain, seating, instrumentation and body colour. A customer order selects one valid option from each relevant module. Modularization postpones final differentiation and can reduce planning complexity, but it requires clear rules for option compatibility.

2.5 Planning BOM

A planning BOM, also called a pseudo or aggregate BOM in some systems, represents a family or forecastable product group rather than one exact sellable product. It is used to plan common materials, capacity or modules before the precise customer configuration is known.

Suppose a product family has three models with expected proportions of 50%, 30% and 20%. A planning BOM may use these proportions to derive approximate requirements for shared modules. The proportions are planning assumptions, not physical quantities that must be installed in every unit. When actual orders are received, the planning structure is replaced or resolved into a valid configuration.

2.6 Phantom BOM

A phantom is a logical assembly that is not normally stocked or built as an independent inventory item. During MRP or work-order processing, the system passes through the phantom and explodes its components into the higher-level parent.

For example, a hardware kit may be defined as a phantom containing four bolts, four washers and four nuts. The kit is convenient for engineering and shop-floor definition, but the components may be picked directly for the parent assembly.

Phantoms are useful for standard substructures and simplification of BOM maintenance. They must be used cautiously where the alleged subassembly has its own lead time, quality inspection, inventory, capacity or traceability requirements. In such cases it should normally be a real manufactured or purchased item, not a phantom.

2.7 Service, sales and costing BOMs

A service BOM identifies replaceable parts for maintenance and field service. A sales BOM defines a commercial package, such as a computer sold with a monitor and accessories. A costing BOM is structured to represent cost accumulation and may include labour, overhead or cost-only items. These views can coexist, but their purposes and ownership must be explicit.

3. BOM Quantities, Units and Data Conventions

The quantity on a component relationship is normally the quantity required per one unit of the parent. If a subassembly requires three bearings and the finished product requires two such subassemblies, the finished product requires six bearings through that branch.

Unit-of-measure discipline is essential. A BOM should distinguish pieces, kilograms, metres, litres and other units. Conversions must be controlled rather than assumed. A quantity of 0.25 metre is not interchangeable with 0.25 kilogram merely because both are numeric values.

Scrap and yield require careful interpretation. If a process has a yield of 95%, the gross input required for a net output quantity Q is:

Here Q and gross input use the same physical unit, and the yield is expressed as a decimal. This relationship applies when loss is represented as a process yield and is assumed to be stable and independent of lot size. If scrap is instead represented as an additional percentage of net usage, a different convention may apply. Organisations must not mix the two conventions.

When the quantity per parent is q and the parent production quantity is P, the direct gross requirement for the component is:

where GR is the component gross requirement in the component’s unit, P is the number of parent units and q is the component quantity per parent. This is a direct-usage relationship and does not yet account for inventory, scheduled receipts, lot sizing, safety stock or scrap.

4. BOM Explosion

BOM explosion is the systematic process of multiplying parent requirements by component usage quantities and propagating the resulting requirements through successive levels. In MRP, explosion is time-phased: the planned order release of a parent creates a component gross requirement at the date the component is needed, subject to lead times and offsets.

For a simple, single-path structure, if a level-0 item requires q₁ units of a level-1 component and that component requires q₂ units of a level-2 component, then the level-2 requirement per finished product is:

For multiple paths, requirements are summed across all paths:

The summation applies when the same component is used in multiple branches. These formulas assume valid, fixed quantities and no alternative-selection or configuration restriction.

Worked example: multilevel gross explosion

Consider product P with the following structure:

The planned production quantity is 100 units of P. The direct requirements are:

• A: 100 × 2 = 200 units;
• B: 100 × 1 = 100 units.

Exploding A gives:

• C through A: 200 × 3 = 600 units;
• D: 200 × 2 = 400 units.

Exploding B gives:

• C through B: 100 × 4 = 400 units;
• E: 100 × 1 = 100 units.

Therefore, the total gross requirement for C is 600 + 400 = 1,000 units. The result is:

This is a gross explosion only. Net requirements would require inventory balances, scheduled receipts, safety stock, allocations, open orders and lead-time timing.

Time-phased explosion

If P must be completed in week 10 and A has a one-week lead time, A must be available in week 9. If C is required at the start of A’s production and has a two-week lead time, the planned release for C may be required in week 7. Exact dates depend on the organisation’s calendar, operation offsets, queue time and whether the component is needed at assembly start or completion.

A useful distinction is:

• Gross requirement: demand before considering available supply.
• Projected available balance: expected inventory after demand and receipts.
• Net requirement: additional supply required after considering eligible inventory, receipts and policy stocks.
• Planned order receipt: quantity scheduled to become available.
• Planned order release: receipt quantity offset backward by lead time.

BOM explosion generates demand; the MRP logic then applies inventory and replenishment rules.

5. Configuration and Option Management

A configurable product has a common structure plus selectable features. Configuration management determines which components are valid for a particular order. It should prevent incompatible options from being simultaneously selected and should ensure that every valid configuration maps to an executable BOM and routing.

Common mechanisms include:

• Option selection: the customer chooses from defined alternatives.
• Effectivity rules: a component is valid for a date, serial range, lot range or model revision.
• 150-percent BOM: includes all possible components and options; rules select the approximately 100-percent valid product structure for a particular configuration.
• Super BOM: a broad configurable structure containing standard and optional components.
• Variant BOM: a separate structure maintained for each defined product variant.
• Constraint rules: logical conditions governing compatibility, such as “four-wheel drive requires the heavy-duty transmission.”

A 150-percent BOM must not be exploded as though every item were physically required. Configuration selection must occur before final demand generation, or the planning system must apply explicit probabilities or planning factors at the aggregate stage.

6. Engineering Change Management

Products evolve because of cost reduction, supplier changes, quality improvements, regulation, obsolescence and customer requirements. An engineering change process provides a controlled method for altering the BOM without losing traceability.

A robust process generally includes:

1. Change request: identifies the problem, opportunity or requirement.
2. Technical and commercial analysis: evaluates function, risk, cost, inventory, tooling, suppliers, service impact and compliance.
3. Approval: authorised engineering, operations, quality, supply-chain and financial stakeholders approve the change according to governance rules.
4. Implementation planning: defines the effective date, serial or lot break, disposition of old inventory, work-in-process treatment and communication plan.
5. BOM and document update: revises the approved structure, drawings, routings, specifications and planning data.
6. Validation and release: confirms that the new configuration can be produced, inspected, serviced and procured.
7. Post-implementation review: checks performance and closes residual actions.

Effectivity

Effectivity defines when or where a BOM relationship is valid. Common forms include:

• date effectivity, such as valid from 1 July;
• serial-number effectivity, such as units 5001 onward;
• lot or batch effectivity;
• model-year or product-variant effectivity;
• plant or location effectivity;
• quantity-based effectivity, where the first defined number of units use one revision.

Effectivity is not the same as the date on which a record is entered into the system. A record may be entered earlier but become effective later. Systems should also support overlapping-effectivity checks, because two competing valid relationships can create ambiguous planning results.

Revision control

A revision identifies a controlled state of a product definition. Revision discipline requires that old revisions remain available for historical production, warranty analysis and service records, while new orders use the correct current revision. Deleting obsolete BOMs destroys traceability and can make it impossible to reconstruct what was built.

The changeover decision should address three inventories:

• on-hand material: can it be consumed, returned, reworked or scrapped?
• work in process: can partially completed units be completed under the old definition?
• finished goods and field units: are service parts or retrofit instructions required?

7. Applied Case: Configurable Industrial Pump

The following is an illustrative case, not a report of a particular company.

Background

A pump manufacturer sells a standard pump frame with alternative impellers, seals and motors. The organisation maintains an engineering structure in which the impeller family is represented as one option group. Production, however, reports shortages because MRP occasionally plans every possible impeller.

Problem

The company uses a 150-percent BOM for sales configuration but passes the unfiltered structure to a legacy MRP interface. In addition, an improved seal has been approved for new orders, while service records still require the previous seal for pumps below a specified serial number.

Analysis

The investigation identifies three causes:

1. Option-selection rules are stored in the sales system but are not transmitted with the order.
2. The MRP interface treats optional components as mandatory.
3. The seal change has a date effectivity in engineering records but requires serial effectivity for service and warranty traceability.

Approach and solution

The manufacturer separates the process into three controlled structures:

• a design-oriented EBOM;
• a manufacturing super BOM with explicit option classes and compatibility rules;
• an order-specific configured BOM released to MRP.

For each accepted order, the configuration engine selects one valid impeller, one seal and one motor. The resulting BOM is checked against compatibility constraints and then assigned a configuration identifier. The seal change is represented with both an effective production date and a serial break. Existing stock is dispositioned by quality engineering, and service planning retains both seal revisions.

Outcome

The revised interface eliminates demand for unselected options, improves purchasing visibility and allows service personnel to identify the correct seal from the pump serial number. The company also adds automated validation for missing quantities, circular structures, overlapping effectivity and unapproved components.

Learning points

The case demonstrates that BOM accuracy is not achieved by engineering maintenance alone. Configuration data, sales-order processing, MRP interfaces, inventory disposition and service history must share a consistent product definition.

8. BOM Governance, Technology and Data Quality

BOM governance assigns ownership and defines standards for naming, revision, units, approvals, effectivity and change communication. Important controls include:

• unique and stable item identifiers;
• controlled descriptions and units of measure;
• mandatory quantity and effectivity fields;
• duplicate and circularity detection;
• approval workflows and segregation of duties;
• version history and audit trails;
• reconciliation between EBOM, MBOM, routings and work instructions;
• periodic comparison of planned and actual component usage;
• formal treatment of substitutes and alternates.

Product lifecycle management (PLM) systems commonly manage engineering definitions, while enterprise resource planning (ERP) and MRP systems execute manufacturing and procurement. Digital thread architectures seek to connect these systems so that a released engineering change flows consistently into manufacturing, purchasing, quality, service and analytics.

Artificial intelligence can assist with duplicate-part detection, natural-language classification, anomaly detection and identification of likely BOM errors. It should not independently approve a safety-critical engineering change. Human accountability, explainability, access control and auditability remain essential. AI-generated suggestions must be validated against approved specifications and configuration rules.

9. Challenges and Limitations

BOM implementation is difficult for reasons extending beyond software:

• engineering and manufacturing may use different structures and terminology;
• legacy products may lack reliable historical revisions;
• informal substitutions may bypass formal change control;
• effectivity may differ by plant, market or serial range;
• scrap factors may be confused with yield factors;
• configurable products create combinatorial complexity;
• phantom use may conceal genuine capacity or quality requirements;
• outsourced operations may require supplier-specific structures;
• excessive detail can make maintenance costly, while insufficient detail weakens planning.

A BOM is a model of reality, not reality itself. It must be sufficiently detailed for the decisions it supports. A purchasing BOM, service BOM and manufacturing BOM may legitimately differ, provided their relationships are controlled and traceable.

10. Best-Practice Checklist

Before releasing a BOM for MRP, verify that:

1. Every item and unit of measure is valid.
2. The parent and components are at the correct revision.
3. Quantities are stated per one parent and use the approved unit convention.
4. The structure contains no circular relationships.
5. Optional and alternative components have explicit selection rules.
6. Effectivity is complete and does not overlap ambiguously.
7. Phantom status reflects actual inventory and manufacturing practice.
8. Scrap and yield assumptions are documented.
9. The routing, work instructions and BOM agree.
10. Engineering, operations, purchasing, quality and service impacts have been assessed.
11. Existing inventory and work in process have a documented disposition.
12. The released data has passed an independent validation or controlled test explosion.

Chapter Summary

Product structure is the hierarchical representation of how a product is composed. The BOM converts that representation into controlled parent-component relationships used by engineering, manufacturing, purchasing, costing, service and MRP. Single-level BOMs show immediate usage, whereas multilevel BOMs support complete product explosion. Engineering BOMs describe the designed product; manufacturing BOMs describe how it is built. Modular, planning and phantom BOMs address variety, aggregate planning and logical non-stocked assemblies respectively.

BOM explosion multiplies parent requirements by component quantities and aggregates common components across paths. In an MRP environment, explosion must be combined with time-phased lead times, inventory, scheduled receipts, lot sizing, safety stock and configuration rules. Configurable products require option selection and compatibility control; a 150-percent or super BOM cannot be treated as a mandatory physical structure.

Engineering changes must be authorised, validated and implemented with revision and effectivity control. Date, serial, lot, plant and model-year effectivity support traceability, while inventory and work-in-process disposition prevent uncontrolled transition. Effective BOM governance links PLM, ERP, MRP, quality, service and human decision-making. Accurate BOMs are therefore a strategic production-management capability rather than a clerical data-maintenance task.

Key Terms

Product structure: Hierarchical representation of parent and component relationships.

Bill of materials (BOM): Controlled list of components and quantities required for a parent item.

Single-level BOM: BOM showing only a parent’s immediate components.

Multilevel BOM: BOM showing components through several product levels.

Engineering BOM (EBOM): Product structure representing the designed product.

Manufacturing BOM (MBOM): Product structure representing how production builds the product.

Modular BOM: Structure based on reusable modules and selectable options.

Planning BOM: Aggregate structure used for family-level forecasting and planning.

Phantom: Logical, normally non-stocked assembly that is exploded into its parent.

BOM explosion: Process of deriving component requirements from parent requirements.

Gross requirement: Demand before supply and inventory offsets are considered.

Net requirement: Additional quantity required after eligible supply is considered.

Effectivity: Rule specifying when, where or to which units a BOM relationship applies.

Revision: Controlled version of a product definition.

Engineering change: Authorised alteration to product design or manufacturing definition.

150-percent BOM: Configurable BOM containing all possible options before selection.

Configuration: Selection of valid features and components for a particular product order.

Common component: Item used in more than one branch or product structure.

BOM governance: Policies and controls ensuring accurate, authorised and traceable BOM data.

Review Questions

Short Answer Questions

1. What is the difference between an item master and a BOM?
2. Define a phantom BOM and state one appropriate use.
3. What information does effectivity provide?
4. Distinguish gross requirement from net requirement.
5. Why should a manufacturing BOM not simply be copied from an engineering BOM?

Long Answer Questions

1. Explain the role of multilevel BOMs in MRP and distinguish them from single-level BOMs.
2. Compare engineering, manufacturing, modular, planning and phantom BOMs.
3. Describe the stages of a controlled engineering-change process.
4. Explain how a configurable product can be represented using a 150-percent BOM.
5. Discuss the governance controls required for reliable BOM data.

Analytical / Application Questions

1. Product X requires 2 units of A and 3 units of B. A requires 4 units of C, while B requires 2 units of C. Calculate the gross requirement for C when 500 units of X are planned.
2. A component is valid from 1 January for serial numbers 1–10,000 and from 15 January for serial numbers 9,500 onward. Analyse the control problem and propose a correction.
3. A company defines a hardware kit as a phantom, but the kit is inspected, stocked for two weeks and issued as a separate subassembly. Evaluate whether phantom treatment remains appropriate and justify your recommendation.

Multiple Choice Questions with Answers

Question 1

Which BOM shows only the immediate components of a parent item?

A. Single-level BOM

B. Planning BOM

C. Service BOM

D. 150-percent BOM

Correct Answer: A. Single-level BOM

Question 2

A product requires 3 units of component A, and A requires 4 units of component B. How many units of B are required per finished product through this path?

A. 1

B. 7

C. 12

D. 16

Correct Answer: C. 12

Question 3

What is the principal characteristic of a phantom assembly?

A. It must always be purchased

B. It is normally exploded without being stocked as an independent assembly

C. It contains only optional components

D. It is used only for service products

Correct Answer: B. It is normally exploded without being stocked as an independent assembly

Question 4

Which structure primarily represents how a product is designed?

A. Engineering BOM

B. Manufacturing BOM

C. Planning BOM

D. Sales BOM

Correct Answer: A. Engineering BOM

Question 5

A 150-percent BOM generally contains:

A. Only mandatory components

B. All possible options before configuration selection

C. Only components already in inventory

D. Only service replacement parts

Correct Answer: B. All possible options before configuration selection

Question 6

If 100 parent units each require 5 components, what is the direct gross requirement before inventory offsets?

A. 20 units

B. 95 units

C. 105 units

D. 500 units

Correct Answer: D. 500 units

Question 7

Which effectivity method is most suitable when a design change applies beginning with a particular unit serial number?

A. Serial-number effectivity

B. Unit-of-measure conversion

C. Lot-sizing effectivity

D. Phantom effectivity

Correct Answer: A. Serial-number effectivity

Question 8

What is a major risk of treating a genuinely stocked and inspected subassembly as a phantom?

A. The product will have too many revisions

B. Its inventory, lead-time and capacity requirements may be hidden

C. Its components cannot be assigned quantities

D. It automatically becomes an engineering BOM

Correct Answer: B. Its inventory, lead-time and capacity requirements may be hidden

Question 9

In BOM explosion, the same common component used through two branches should generally be:

A. Ignored in one branch

B. Multiplied by only the lower quantity

C. Summed across the valid branches

D. Converted into a phantom

Correct Answer: C. Summed across the valid branches

Question 10

Which action best protects historical traceability after a BOM revision?

A. Delete the old BOM

B. Overwrite the old quantity without history

C. Retain the old revision and control its effectivity

D. Remove all service records

Correct Answer: C. Retain the old revision and control its effectivity