Bills of Material, Product Structures and MRP Linkages

Introduction

Master Production Scheduling (MPS) converts the aggregate production plan into a time-phased schedule for specific end items. The schedule becomes operationally meaningful only when it can be translated into requirements for components, subassemblies, raw materials, packaging and purchased parts. This translation is enabled by the bill of material (BOM), the product structure and the material requirements planning (MRP) logic linked to the MPS.

A BOM is not merely a parts list. It is a controlled representation of how an item is designed, assembled, purchased and serviced. Its accuracy affects procurement quantities, shop-floor priorities, inventory investment, capacity plans, costing, product configuration and customer delivery performance. Inaccurate or poorly governed product data can cause an MRP system to generate technically precise but operationally wrong recommendations.

This chapter examines conventional bills of material, planning and modular bills, low-level coding, MPS explosion, lead-time offsetting, engineering changes and data governance. The emphasis is on managerial interpretation as well as technical calculation.

Learning Objectives

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

1. Interpret single-level, multilevel, planning, modular and phantom bills of material.
2. Explain parent–component relationships and low-level coding.
3. Demonstrate how an MPS is exploded into time-phased material requirements.
4. Apply lot-sizing, inventory and lead-time logic to an MRP record.
5. Assess the effects of engineering changes, inaccurate data and changing lead times.
6. Recommend governance and improvement practices for BOM–MPS–MRP integration.

1. The Product Structure as the Link between Demand and Supply

An end item is the output for which independent demand exists. Examples include a finished pump, an industrial control panel or a configured automobile. Components normally have dependent demand: their requirements are derived from the planned production of a parent item.

The product structure represents the hierarchical relationship between a parent and its components. A parent may be a finished product, a subassembly or a purchased assembly. Each relationship normally specifies:

• component item identity;
• quantity per parent;
• unit of measure;
• effectivity date or revision;
• scrap or yield information, where applicable;
• operation or work-centre reference;
• issue, phantom or bulk-material status.

For example, if one finished unit requires two brackets and each bracket requires four bolts, the product structure is:

Finished unit → 2 brackets → 4 bolts per bracket.

The gross requirement for bolts is therefore eight per finished unit, before considering scrap, inventory or scheduled receipts. The hierarchical structure matters because the timing of a component requirement depends on the planned availability of its parent and the parent’s manufacturing lead time.

A product structure can be viewed in two complementary ways:

• Design view: what the product contains from an engineering perspective.
• Planning and manufacturing view: what must be purchased, fabricated, assembled and available at each point in time.

These views are not always identical. Engineering may define a functional assembly, while manufacturing may use a phantom assembly or an alternate process. Effective planning therefore requires integration among engineering BOMs, manufacturing BOMs, service BOMs and the enterprise resource planning (ERP) item master.

2. Types of Bills of Material

2.1 Single-level and multilevel BOMs

A single-level BOM lists the immediate components of a parent but does not display the components of those components. It is useful for issuing material to one assembly operation and for simple products.

A multilevel BOM displays the complete hierarchy. Each level indicates the number of parent–child relationships between the end item and a component. Multilevel structures are essential for MRP because requirements must be passed down through every relevant level.

Consider the following simplified structure:

One Product P requires three Part B units and therefore twelve Fastener Z units. It also requires two units of Material X and two units of Material Y.

2.2 Engineering BOM and manufacturing BOM

An engineering BOM (EBOM) describes the product as designed. It often emphasizes functional systems, design ownership and revision control. A manufacturing BOM (MBOM) reorganizes the same product for production. It may include process-specific assemblies, consumables, packaging, routings and point-of-use information.

Differences between EBOM and MBOM are legitimate when they are controlled and traceable. They become dangerous when engineering changes are released in one representation but not propagated to procurement, production planning, quality or service functions.

2.3 Production, service and sales BOMs

A production BOM supports manufacturing and MRP. A service BOM identifies replaceable parts and service assemblies, which may differ from the original production structure. A sales BOM represents a commercial configuration, such as a computer sold with a selected memory and software package. The sales BOM must ultimately resolve into a valid manufacturing and procurement structure.

2.4 Modular BOMs

A modular BOM groups frequently reused components into modules. A module is a standard subassembly or option that can be planned, manufactured or stocked independently. Modular structures are especially valuable in configure-to-order and assemble-to-order environments.

For example, a machine may contain a base frame, a standard drive module and one of three control modules. The MPS can schedule the machine family or modules, while the customer order determines the final configuration. Modularity reduces planning complexity, supports postponement and improves reuse of common parts.

However, modular planning requires accurate rules. The system must know which modules are mandatory, which are optional, which options are mutually exclusive and how a customer configuration maps to component demand.

2.5 Planning bills and super bills

A planning bill of material represents an anticipated product family or average configuration rather than one physically manufactured item. It is used for medium-range planning, forecasting and aggregate MPS development.

A planning BOM may assign percentages to options. For example, a product family may be expected to comprise 60% standard versions and 40% premium versions. If the family forecast is 1,000 units, preliminary planning may use 600 standard and 400 premium configurations. These proportions are planning assumptions, not proof of actual customer orders.

A super bill is a planning structure containing all possible options, often with usage percentages or planning factors. It supports aggregate planning but must not be used indiscriminately for detailed execution. Once actual orders or a frozen configuration are available, the planning structure should be replaced or resolved into the applicable production BOM.

2.6 Phantom BOMs

A phantom is a logical grouping used to simplify engineering or planning but not normally stocked as an independent inventory item. During MRP explosion, the phantom is passed through and its components are planned directly against the higher-level parent requirement.

Phantoms can reduce unnecessary work orders and inventory transactions. They can also create confusion if planners assume that a phantom has an independent lead time, stock balance or purchase order. Its treatment must therefore be explicit in the ERP system.

3. Low-Level Coding

Low-level coding assigns each item the lowest level at which it appears in any product structure. It ensures that an item used in several branches is planned only after all relevant parent requirements have been calculated.

Suppose Component C appears directly under Product P in one branch and under Assembly A in another. It may appear at levels 1 and 2 in different paths. Its low-level code is 2, the deepest level at which it occurs. MRP processes the item at its low-level code after all higher-level explosions have contributed to its total gross requirement.

The rule is:

An item’s low-level code is the maximum number of parent–child links from any end item to that item across all valid product structures.

Low-level coding prevents premature netting. If an item were planned before all parent demands were accumulated, the system could understate its total requirement or create separate, poorly coordinated planned orders.

Low-level coding is especially important when:

• a common component is used in several assemblies;
• a subassembly is used in multiple products;
• alternate BOMs create different paths;
• a component is both purchased directly and included in a manufactured assembly.

4. Core MRP Relationships

MRP begins with the MPS for end items and explodes requirements through the BOM. For each item and time bucket, the basic record contains gross requirements, scheduled receipts, projected available balance, net requirements, planned order receipts and planned order releases.

A commonly used inventory relationship is:

where:

• PAB_t = projected available balance at the end of period t;
• PAB_t−1 = projected available balance at the end of the previous period;
• SR_t = scheduled receipt in period t;
• POR_t = planned order receipt in period t;
• GR_t = gross requirement in period t.

All quantities must be expressed in the same unit, such as pieces or kilograms. The equation assumes that receipts and requirements are assigned to the same planning bucket and that inventory records are accurate.

If the projected balance would fall below the planned safety-stock level, the shortfall becomes a net requirement. A general expression is:

where NR_t is net requirement and SS_t is the desired safety-stock level at the end of period t. If no safety stock is required, SS_t is zero. This expression is a planning convention; organizations may use additional rules for nonnegative inventory, minimum order quantities, service levels or time-phased safety stock.

The planned receipt is obtained by applying the lot-sizing rule to the net requirement. Under lot-for-lot sizing:

Under a fixed order quantity, the receipt is normally the smallest permitted multiple that covers the net requirement. For a fixed quantity Q, this may be represented as:

and zero when NR_t = 0. Here, ceil means rounding upward to the next whole multiple. The rule is applicable only when the fixed-quantity policy is valid and excess inventory is acceptable.

Lead-time offsetting

A planned order receipt must be released early enough to arrive when required. If the item lead time is two weeks, a receipt planned for week 6 generally requires a release in week 4, subject to calendars, queue time, inspection and supplier commitments.

where POL_t−L is the planned order release, POR_t is the planned order receipt, and L is the lead time in planning periods. This relationship assumes a fixed lead time and ignores capacity disruption, transportation uncertainty and variable processing time. In practice, safety lead time or safety stock may be used to protect against uncertainty.

5. MPS Explosion through a Product Structure

The gross requirement for a component is generated from the planned order release of its parent, not ordinarily from the parent’s end-item demand in the same period. If a parent is planned for release in period t and each parent requires q units of a component, then the component gross requirement attributable to that parent is:

If several parents use the same component, their requirements are added:

where q_ij is the quantity of component i required by parent j and POL_j,t is the planned order release of parent j in period t. The summation is valid when units, effectivity and configuration assumptions are compatible.

Worked example

A company produces Product P. The structure is:

• One P requires two units of Assembly A and three units of Component X.
• One A requires four units of Component Y.
• P has a one-week assembly lead time.
• A has a one-week production lead time.
• X and Y are purchased with two-week lead times.
• The MPS requires 100 units of P in week 6.
• There is no opening inventory, no scheduled receipt and lot-for-lot sizing.

First, the planned receipt of P is 100 units in week 6. Its release is 100 units in week 5.

Assembly A requirement:

Since A has a one-week lead time, 200 units of A are released in week 4. Therefore, the gross requirement for Y is:

Y has a two-week purchasing lead time, so its planned order release is in week 2. Component X is required directly for P:

X must therefore be released in week 3. The resulting logic is summarized below.

The example demonstrates two important principles. First, component requirements are time-phased according to parent releases. Second, a lower-level item can be required much earlier than the finished product because multiple manufacturing and purchasing lead times accumulate through the structure.

6. Inventory, Scrap, Yield and Lot-Sizing Effects

The simple explosion assumes perfect yield and no scrap. If a process has an expected yield of 95%, the required input may be increased. Under a basic yield assumption, the input quantity required for a target output is:

If yield is expressed as a decimal, 95% becomes 0.95. Producing 95 good units from 100 units of input implies that 100 units are needed for 95 good units. Yield factors should be governed carefully because indiscriminate inflation can create excessive inventory.

Scrap may be represented as a percentage. If s is the scrap fraction and the requirement is based on input consumption, a common planning adjustment is:

This equation assumes that scrap is statistically stable and that the organization defines scrap consistently. It should not be used automatically for rework, recoverable material or scrap already embedded in a standard quantity.

Lot-sizing changes timing and inventory. Lot-for-lot minimizes planned excess but may create many small orders. Fixed order quantities, minimum order quantities, economic order quantities, periods-of-supply rules and part-period balancing may reduce ordering or setup costs but create surplus inventory and potentially obscure demand signals. Lot-sizing policy should reflect item value, replenishment economics, supplier constraints, shelf life and customer service requirements.

7. Engineering Changes and Effectivity Control

An engineering change may alter item identity, quantity per assembly, specification, supplier, process, revision or effectivity date. Its impact is not limited to future design records. Open purchase orders, work orders, on-hand inventory, safety stock, customer commitments and field service stock may all be affected.

A controlled engineering change process normally includes:

1. change request and technical justification;
2. cross-functional impact assessment;
3. approval by authorized engineering, operations, quality and commercial personnel;
4. definition of revision and effectivity date or serial-number range;
5. update of EBOM, MBOM, routings, item master and documentation;
6. disposition of obsolete or transitional inventory;
7. communication to suppliers and production personnel;
8. verification after implementation.

Effectivity methods

• Date effectivity: the new component becomes valid from a specified calendar date.
• Unit or serial effectivity: the change applies from a specified serial or lot number.
• Order effectivity: the change applies to selected customer orders.
• Stock depletion: the old component is used until available stock is exhausted, subject to quality and regulatory constraints.

A change without effectivity discipline can cause MRP to mix old and new components, issue obsolete parts, or generate unnecessary rescheduling. Conversely, excessive reluctance to revise the BOM may leave the organization manufacturing to an invalid specification.

8. Lead-Time Integrity and Nervousness

MRP results are highly sensitive to lead times. A lead time that is too short creates late orders and expediting; one that is too long creates early releases, excess work-in-process and inflated inventory. Lead time should be decomposed where possible into queue, setup, run, move, inspection, purchasing, transportation and receipt-processing time.

A planning system may use fixed lead times even though actual lead times vary. This simplification is practical but creates risk. Managers should monitor actual versus planned lead time, supplier reliability, capacity loading and order lateness. Statistical buffers, safety lead time and supplier collaboration can reduce risk, but buffers should be based on evidence rather than habit.

MRP nervousness refers to frequent changes in planned orders caused by small changes in demand, inventory, lead time or supply status. Nervousness can impose high administrative and operational costs. Common stabilizing practices include:

• time fences and frozen zones in the MPS;
• planning time fences for purchase and production orders;
• exception messages rather than automatic rescheduling;
• minimum planning horizons;
• firm supplier commitments;
• appropriate lot-sizing and order modifiers;
• review of root causes rather than repeated manual overrides.

A frozen MPS does not mean that reality is ignored. It means that changes within a defined near-term horizon require explicit authorization and impact analysis.

9. Data Accuracy and Governance

MRP follows its input logic. If the BOM, inventory balance, open-order status, lead time or calendar is wrong, the resulting recommendation may be wrong even when the software is functioning correctly.

Important data-quality dimensions include:

Data governance assigns ownership, approval authority, change history and auditability. A useful governance model distinguishes:

• engineering ownership of design definition;
• manufacturing ownership of process use and MBOM structure;
• materials-management ownership of planning parameters;
• finance ownership of costing implications;
• quality and regulatory ownership of compliance impacts;
• master-data governance ownership of workflow and integrity.

Key performance indicators may include BOM accuracy, percentage of items with verified lead times, engineering-change implementation time, inventory-record accuracy, supplier on-time delivery and MRP exception closure time. A single aggregate data-quality percentage is often less useful than measures tied to operational outcomes.

10. Applied Case: Modular Industrial Pump

Background

The following is an illustrative case. Meridian Pumps manufactures industrial pumps in make-to-order and assemble-to-order modes. Its product family contains a standard pump body, a drive module and one of three control modules. The company uses a planning BOM for quarterly capacity planning and modular production BOMs for customer orders.

Problem

Planners observed shortages of control-panel components despite apparently adequate finished-goods inventory. Expedites increased, and engineering reported that a revised sensor had been approved but was not consistently appearing in production orders.

Analysis

An audit identified four linked problems:

1. The planning BOM used a 50:30:20 option mix, while actual orders were 35:25:40.
2. The control module was represented as a phantom in one plant but as a stocked assembly in another.
3. The sensor revision was effective by date in engineering but by serial number in manufacturing.
4. Supplier lead time for the revised sensor had increased from four to seven weeks, while MRP still used four weeks.

The MPS correctly scheduled pump-family output, but the planning assumptions distorted the mix of control modules. The inconsistent phantom treatment caused different levels of demand aggregation. The engineering change produced mixed requirements, and the obsolete lead time caused releases that could not meet actual need dates.

Approach and solution

The company adopted the following controls:

• a governed planning BOM updated monthly from order history;
• explicit module definitions and a common phantom policy;
• a cross-functional change notice with serial-number effectivity;
• separate planned lead time and supplier performance review;
• a two-week frozen MPS zone for released customer orders;
• exception reporting for shortages, late receipts and revision conflicts;
• reconciliation of on-hand sensors and open purchase orders before cutover.

The MPS was then exploded through the selected control-module BOM rather than through an unvalidated family average. The revised sensor was purchased using the seven-week lead time, while existing compliant stock was allocated to orders within the approved transition rules.

Outcome

The principal improvement was not a new algorithm. It was alignment among configuration logic, effectivity, lead times and execution ownership. Expedites declined, shortages became visible earlier and planners could distinguish genuine demand changes from master-data errors.

Learning points

The case illustrates that MRP is a dependent-demand logic system, not an independent source of truth. A mathematically correct explosion cannot compensate for an incorrect product structure or uncontrolled engineering change. Modularization improves responsiveness only when option rules and revision governance are reliable.

11. Technology, Digital Integration and AI

Modern ERP and advanced planning systems can manage multilevel BOMs, revisions, configuration rules, alternate materials, supplier schedules and effectivity. Product lifecycle management (PLM) systems often control engineering definitions, while ERP systems execute manufacturing and procurement. Integration should preserve revision identity, effectivity, approvals and audit trails rather than merely copying item numbers.

Artificial intelligence can assist in detecting anomalous usage, identifying unusual lead-time patterns, predicting engineering-change impacts and prioritizing master-data audits. For example, a model may flag a component whose actual consumption consistently differs from its BOM quantity. Such a signal is not proof of a BOM error: it may reflect scrap, substitution, unrecorded rework or an undocumented process change. Human review and controlled authorization remain necessary.

AI-generated recommendations should be explainable, traceable to source data and subject to segregation of duties. Automatic modification of BOMs or release of purchase orders without authorization creates quality, financial and safety risks. In regulated industries, electronic records, approval signatures and revision history may also be subject to formal compliance requirements.

12. Managerial Implications and Best Practices

Managers should treat the BOM as a cross-functional control object rather than an engineering document alone. The following practices are particularly important:

1. Maintain one authoritative identity for each item, with controlled alternates and revisions.
2. Separate planning, engineering, manufacturing, sales and service views while preserving traceability.
3. Use low-level coding and validate common-component relationships.
4. Reconcile MPS, BOM, inventory, open orders and lead times before judging MRP performance.
5. Use planning BOMs for aggregate decisions and resolved production BOMs for execution.
6. Define effectivity before releasing an engineering change.
7. Review lead times against actual performance and capacity conditions.
8. Establish time fences and escalation rules for MPS changes.
9. Audit high-value, long-lead and safety-critical components more frequently.
10. Measure the business consequences of master-data errors, not only transaction completeness.

The central managerial question is not whether the system has produced a plan. It is whether the plan is feasible, authorized, synchronized with the product definition and robust against known uncertainty.

Chapter Summary

A bill of material expresses the parent–component relationships through which an MPS is translated into dependent material requirements. Single-level, multilevel, engineering, manufacturing, modular, planning, super and phantom BOMs serve different purposes and must not be confused. Low-level coding ensures that shared components are planned after all applicable parent requirements have been accumulated.

MRP calculates gross requirements by exploding parent planned order releases through the product structure. Net requirements depend on projected inventory, scheduled receipts, safety stock and lot-sizing policy. Lead-time offsetting converts planned receipts into planned releases, causing lower-level materials to be required earlier than end-item completion. Scrap, yield, order modifiers and inventory accuracy materially affect the result.

Engineering changes require controlled revision, effectivity, disposition and cross-functional communication. Inaccurate BOM quantities, lead times, units of measure, inventory balances or scheduled receipts can make MRP recommendations unreliable. Effective governance integrates engineering, manufacturing, materials, quality, finance and information systems. Technology and AI can improve detection and analysis, but they do not replace authorization, accountability or professional judgment.

Key Terms

Bill of material: A structured record of the components, quantities and relationships required to make or define an item.

Dependent demand: Demand calculated from the planned production of another item.

Engineering BOM: A product structure representing the product as designed.

Manufacturing BOM: A product structure organized to support production and material planning.

Planning BOM: A representative structure used for aggregate or family-level planning.

Modular BOM: A structure organized around standard subassemblies or options.

Super bill: A planning structure containing alternative options, often with usage proportions.

Phantom: A logical assembly normally passed through during MRP explosion rather than stocked.

Low-level code: The deepest product-structure level at which an item appears.

MPS explosion: The translation of end-item schedule quantities into component requirements.

Gross requirement: Total demand before considering inventory or scheduled receipts.

Net requirement: Demand remaining after available supply and applicable policies are considered.

Planned order receipt: A future receipt calculated by MRP.

Planned order release: The order authorization date obtained by offsetting a receipt by lead time.

Lead time: Time required between releasing an order and receiving the usable item.

Lot sizing: The rule used to determine the quantity and timing of planned orders.

Effectivity: The date, serial range or condition under which a BOM or revision is valid.

Engineering change: A controlled modification to product, process or technical definition.

MRP nervousness: Frequent changes in planned orders caused by changing inputs or planning parameters.

Review Questions

5 Short Answer Questions

1. What is the difference between an engineering BOM and a manufacturing BOM?
2. Define low-level coding and state its purpose in MRP.
3. Why are component requirements usually based on parent planned order releases?
4. What is a phantom BOM, and how is it treated during MRP explosion?
5. Identify four data elements that can cause incorrect MRP recommendations.

5 Long Answer Questions

1. Explain the structure and managerial uses of single-level, multilevel, modular, planning and super bills of material.
2. Describe the complete process by which an MPS for an end item becomes time-phased requirements for purchased components.
3. Discuss how engineering changes should be governed from approval through implementation and inventory disposition.
4. Evaluate the effects of inaccurate lead times, lot-sizing rules and inventory records on production performance.
5. Explain how PLM, ERP and AI-enabled analytics can support BOM and MRP governance, including their limitations.

3 Analytical / Application Questions

1. A product requires three units of Assembly A and two units of Component X. The MPS releases 80 products in week 7. A requires two units of Y and has a one-week lead time; Y has a two-week lead time. Determine the gross requirements and release periods for A, X and Y, assuming no inventory and lot-for-lot sizing.
2. A company changes a component from a four-week to a seven-week supplier lead time while retaining a six-week customer promise. Analyze the operational risks and recommend at least four managerial actions.
3. A product family planning BOM assumes option proportions of 70% and 30%, but actual orders over three months are 45% and 55%. Explain how the error can affect MPS, component procurement, capacity and inventory, and propose a control mechanism.

Multiple Choice Questions with Answers

Question 1

Which BOM is primarily used to represent a product as designed?

A. Engineering BOM

B. Planning BOM

C. Service BOM

D. Super bill

Correct Answer: A. Engineering BOM

Question 2

An item appears at levels 1 and 3 in different product-structure paths. What is its low-level code?

A. 1

B. 2

C. 3

D. 4

Correct Answer: C. 3

Question 3

A parent planned order release is 120 units and each parent requires 4 units of a component. What is the component gross requirement?

A. 30 units

B. 124 units

C. 240 units

D. 480 units

Correct Answer: D. 480 units

Question 4

What is the main purpose of a planning BOM?

A. To record only service replacement parts

B. To support aggregate or family-level planning

C. To eliminate all engineering revisions

D. To define supplier payment terms

Correct Answer: B. To support aggregate or family-level planning

Question 5

A planned order receipt is required in week 8 and the item lead time is three weeks. In which week should the order normally be released?

A. Week 3

B. Week 5

C. Week 8

D. Week 11

Correct Answer: B. Week 5

Question 6

Under lot-for-lot sizing, the planned order receipt is normally equal to the:

A. Gross requirement plus safety stock

B. Net requirement

C. Fixed order quantity

D. Previous-period inventory balance

Correct Answer: B. Net requirement

Question 7

What is the defining characteristic of a phantom assembly?

A. It must always be purchased externally

B. It is normally passed through during MRP explosion

C. It has no components

D. It is always a finished end item

Correct Answer: B. It is normally passed through during MRP explosion

Question 8

Which change-control element specifies when a new BOM revision becomes valid?

A. Effectivity

B. Safety stock

C. Lot size

D. Projected available balance

Correct Answer: A. Effectivity

Question 9

If a component is required directly by two parents, its total gross requirement should generally be:

A. The larger parent requirement only

B. The average of the two requirements

C. The sum of the applicable parent-derived requirements

D. The smaller parent requirement only

Correct Answer: C. The sum of the applicable parent-derived requirements

Question 10

Which condition most directly contributes to MRP nervousness?

A. A stable frozen MPS

B. Frequent changes in demand, inventory or lead-time inputs

C. A fully controlled engineering revision

D. Accurate scheduled receipts

Correct Answer: B. Frequent changes in demand, inventory or lead-time inputs