MRP Logic and Time-Phased Calculations

Introduction

Material Requirements Planning (MRP) converts a production plan into a time-phased schedule of component requirements and replenishment actions. Its central question is not simply “How much material is needed?” but “What item, in what quantity, is required, and in which period must action be taken?”

MRP is therefore a planning logic that links four records: the master production schedule (MPS), the bill of materials (BOM), inventory and open-order records, and item-planning parameters. It uses netting to recognize available supply, explosion to derive dependent requirements, offsetting to determine release dates, and pegging to trace component requirements back to their sources.

The calculations in this chapter assume a discrete, deterministic planning environment unless stated otherwise. Demand, lead times, lot-sizing rules, scheduled receipts, inventory records and BOM relationships are treated as known. In practice, uncertainty, capacity limitations, engineering changes and data errors can materially affect the results.

Learning Objectives

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

1. Explain the logic and data requirements of an MRP system.
2. Distinguish independent demand from dependent demand.
3. Calculate gross requirements, projected available balances and net requirements.
4. Apply lot-sizing, safety-stock and scheduled-receipt rules.
5. Offset planned-order receipts to obtain planned-order releases.
6. Explode parent requirements through a multilevel BOM.
7. Use pegging to identify the source of a component requirement.
8. Interpret MRP records critically and recognize their operational limitations.

1. The Logic of MRP

1.1 Independent and dependent demand

Independent demand is demand that originates outside the particular inventory system, such as customer orders, forecasts or a contractual delivery schedule. Finished products commonly have independent demand.

Dependent demand is demand derived from the requirements of another item. If one finished product requires four brackets, the production of 100 finished products creates a dependent gross requirement for 400 brackets. Dependent demand should generally be calculated rather than forecast separately, because its quantity and timing are determined by the parent schedule and BOM.

MRP is most effective when demand is dependent, inventory records are reasonably accurate, BOMs are valid, and lead times are sufficiently stable for time-phased planning.

1.2 Required inputs

An MRP calculation is only as reliable as these inputs. A mathematically correct calculation based on an obsolete BOM still produces an operationally incorrect plan.

1.3 The MRP record

A conventional MRP record contains the following rows for each item:

• Gross requirements: total demand before considering available supply.
• Scheduled receipts: open orders already released and expected to arrive.
• Projected available balance (PAB): inventory expected to remain after satisfying requirements.
• Net requirements: additional supply needed after considering inventory and scheduled receipts.
• Planned-order receipts: orders that the system proposes to receive.
• Planned-order releases: orders that must be released earlier, after lead-time offsetting.

A time bucket may represent a day, week, or another planning period. The selected bucket must be consistent with the precision of demand and lead-time data.

2. Core Equations and Assumptions

Let period t identify a planning bucket. Define:

• GR_t = gross requirement in period t;
• SR_t = scheduled receipt in period t;
• POR_t = planned-order receipt in period t;
• PAB_t = projected available balance at the end of period t;
• NR_t = net requirement in period t;
• SS = required safety-stock level;
• PAB_t-1 = prior-period projected available balance.

The basic inventory balance is:

This identity assumes that receipts become available during period t before the period’s requirements are consumed, or that the organization uses an equivalent netting convention. If the operational sequence differs, the timing convention must be stated explicitly.

A common net-requirement equation is:

This form assumes that safety stock is protected and that no planned receipt has yet been inserted for period t. If a scheduled receipt already covers the requirement, the net requirement is zero. If the expression inside the maximum is negative, no new receipt is required.

After selecting a planned receipt quantity, the projected balance becomes:

The resulting balance should normally be at least SS when safety stock is a hard requirement. If safety stock is a target rather than a constraint, temporary violations may be permitted by policy.

2.1 Gross requirements

For a finished item, gross requirements are usually obtained from the MPS. For a component, gross requirements are generated by BOM explosion. If parent item p has a planned-order release of PORL_{p,t]] in period t, and each parent requires q_cp units of component c, then:

If several parent items consume the same component, requirements are added:

This equation assumes that component usage is fixed and that scrap, yield losses and usage probabilities are not separately modeled. Where a scrap factor s is applicable, a planning adjustment may be made, for example:

where s is expressed as a decimal between 0 and 1. This adjustment is appropriate only when the organization’s policy defines scrap as a proportion of input that fails; alternative definitions require alternative treatment.

2.2 Lot sizing

Net requirements do not always equal order quantities. A lot-sizing rule converts a net requirement into a planned receipt. Common rules include:

For lot-for-lot planning:

For a fixed order quantity Q, a simple rule is:

where ceil(x) means the smallest integer greater than or equal to x. This rule may create inventory above the safety stock and may require a separate policy for maximum inventory, minimum order quantities or multiples.

3. Netting: The Time-Phased Calculation Procedure

Netting is performed period by period. A robust sequence is:

1. Establish the beginning projected available balance.
2. Enter scheduled receipts in their promised periods.
3. Enter gross requirements.
4. Determine whether available supply covers the requirement and safety stock.
5. Calculate any net requirement.
6. Apply the lot-sizing rule to create a planned-order receipt.
7. Recalculate the projected balance.
8. Offset the receipt by the item’s lead time to obtain a planned-order release.

Worked Example 1: Single-level netting

An item has the following parameters:

• Beginning on-hand inventory: 70 units;
• Safety stock: 20 units;
• Lead time: 1 week;
• Lot-for-lot ordering;
• A scheduled receipt of 30 units in week 2;
• Gross requirements of 40, 80, 30 and 70 units in weeks 1–4.

The calculation is shown below. Planned receipts are inserted only when required to preserve safety stock.

For week 2:

The two subtractions represent the beginning balance and the scheduled receipt. The planned receipt of 40 units produces an ending balance of 20 units:

The release is one week earlier than the receipt because the lead time is one week. Notice that the scheduled receipt is not replanned automatically. It is treated as available unless the planner changes or cancels it.

Timing conventions

Organizations must define whether a receipt arriving in a period can satisfy that same period’s requirement. Two common conventions are:

• Beginning-of-period receipt: receipt is available before consumption in the bucket.
• End-of-period receipt: receipt is available only after consumption; it may need to be planned in an earlier bucket.

Both can be valid, but mixing conventions produces apparent errors. The planning calendar should also specify whether lead time is expressed in calendar days, working days, weeks or manufacturing hours.

4. Offsetting Planned Orders

Offsetting converts a planned-order receipt into a planned-order release. If the receipt is required in period t and lead time is L periods, then:

where PORL denotes the planned-order release. The equation assumes fixed lead time, no queue delay, no capacity restriction and a lead-time unit compatible with the planning buckets.

If a release would fall before the planning horizon, the system may display an exception message such as “release order early” or “past-due release.” If the required release occurs on a nonworking day, a calendar rule may move it to the preceding working day.

Offsetting is not merely an arithmetic shift. It is a managerial commitment: releasing an order earlier may increase work-in-process and holding cost, while releasing later may jeopardize customer service.

5. Explosion Through a Multilevel BOM

5.1 BOM relationships

A BOM is a structured representation of the materials, components and subassemblies required to make an item. It may be:

• Single-level, showing only immediate components;
• Multilevel, showing components several stages below the finished product;
• Modular, using common assemblies and options;
• Planning or phantom, used for planning logic without necessarily representing a stocked item.

Explosion proceeds from a parent’s planned-order releases to its components’ gross requirements. It should not normally use the parent’s gross requirements directly, because the component is required when the parent is released to production or assembly, not necessarily when the finished product is delivered.

Worked Example 2: Two-level explosion

A finished product A requires two units of subassembly B and three units of component C. Each B requires four units of C. The MPS creates the following planned-order releases for A:

Assume B and C are needed in the same period as the release of their parent. The gross requirements are:

For B:

For direct component C:

The subassembly B creates additional requirements for C when B is released. If B has a one-period lead time, its planned-order releases may occur in weeks 3 and 5. Therefore:

The direct and subassembly-derived requirements must be placed in their correct time buckets and combined only when they occur in the same period. This example illustrates why explosion and offsetting are interdependent: the component’s timing depends on the parent’s planned release, which depends on the parent’s own lead time and netting calculation.

5.2 Common explosion errors

Typical errors include:

• multiplying by the parent’s finished-product demand rather than its planned release;
• ignoring scrap, yield or usage quantity;
• placing component demand in the finished-product delivery period;
• double-counting a common component through both a parent and a subassembly;
• failing to account for engineering-change effectivity dates;
• treating a phantom assembly as a normal stocked item when the system requires immediate lower-level explosion.

6. Pegging and Traceability

Pegging identifies the parent requirement or customer order that generated a planned order or gross requirement. It may be:

• Single-level pegging, linking a component to its immediate parent;
• Full pegging, tracing the component through all BOM levels to a top-level item or customer order;
• Exception pegging, showing only requirements affected by a shortage or rescheduling event.

Pegging supports shortage analysis, customer-priority decisions, engineering-change evaluation, and rescheduling. For example, if 25 units of a component are short, pegging can show whether those units support an urgent export order, a service part, or a low-priority replenishment order.

Pegging is a traceability mechanism, not a substitute for judgment. A component may be physically interchangeable among orders, even though the planning system assigns it to a particular demand source. Allocation rules and reservation policies must therefore be understood before a pegged shortage is escalated.

7. Integrated Application: A Two-Level MRP Case

Background

The following is an illustrative case involving a manufacturer of industrial pump assemblies. Product P requires one housing H and two seal kits S. The housing requires three castings C. The firm plans in weekly buckets.

Problem

The MPS requires 40 pumps in week 4 and 30 pumps in week 6. The pump has a one-week assembly lead time. The housing has a two-week lead time, and the seal kit has a one-week lead time. Beginning inventory and lot-sizing data are:

Assume that components are required when their parent is released, and that receipts are available at the beginning of their stated week.

Analysis of the top-level item

The MPS requires pump completions in weeks 4 and 6. With a one-week assembly lead time, pump releases occur in weeks 3 and 5. These releases drive component gross requirements:

• Housing: 1 × 40 in week 3 and 1 × 30 in week 5.
• Seal kit: 2 × 40 = 80 in week 3 and 2 × 30 = 60 in week 5.

Housing netting

Housing begins with 10 units and has a scheduled receipt of 20 in week 3. Its safety stock is 5.

For week 3:

Housing planned receipts are therefore 15 in week 3 and 30 in week 5. With a two-week lead time, releases occur in weeks 1 and 3. These releases create casting requirements in weeks 1 and 3 because each housing requires three castings:

• Week 1: 3 × 15 = 45 castings;
• Week 3: 3 × 30 = 90 castings.

Seal-kit netting

For week 3:

The fixed-lot rule requires 100 units, not 60. The resulting balance is 50 units. In week 5:

A further fixed lot of 50 is planned, leaving 40 units. With a one-week lead time, seal-kit releases occur in weeks 2 and 4.

Casting netting

Casting gross requirements are 45 in week 1 and 90 in week 3. Beginning inventory is 100, safety stock is 20, and a scheduled receipt of 100 arrives in week 2.

No new casting order is required in the horizon. The scheduled receipt creates a substantial balance, illustrating why planned orders should not be generated without considering open supply.

Outcome and learning points

The integrated plan produces:

• housing releases in weeks 1 and 3;
• seal-kit releases in weeks 2 and 4;
• no additional casting releases;
• ending balances that preserve stated safety stocks under the assumptions given.

The case demonstrates the sequence of MRP logic: the MPS drives top-level releases; those releases are exploded into component requirements; each item is independently netted; planned receipts are offset by lead time; and pegging can trace, for example, the 45 castings in week 1 to the 15 housing units required for the week-4 pump order.

8. Managerial Interpretation and System Governance

8.1 Exception messages

MRP systems commonly report exceptions such as:

• release order;
• expedite order;
• defer order;
• cancel order;
• increase or reduce order quantity;
• past-due receipt;
• insufficient lead time;
• component shortage.

These messages require review rather than automatic acceptance. A system may recommend expediting an order because a receipt is late, but the planner must consider supplier reliability, transportation cost, production priority and customer commitments.

8.2 Capacity and feasibility

Traditional MRP is primarily a material-planning logic. It may produce a material schedule that cannot be executed because machines, labor, tooling, warehouse space or suppliers lack capacity. Capacity requirements planning (CRP), finite-capacity scheduling and supplier-capacity analysis are therefore required for feasibility validation.

A planned-order release is not automatically a realistic production order. It becomes credible only after capacity, quality, procurement and operational constraints have been checked.

8.3 Data quality and governance

Important controls include:

• cycle counting and inventory accuracy measurement;
• formal BOM and engineering-change control;
• lead-time review based on actual performance;
• explicit unit-of-measure conversion;
• approval of safety-stock and lot-sizing parameters;
• audit trails for manual overrides;
• reconciliation between purchase, production and receiving records.

An organization should distinguish between a genuine demand change and a planning-data error. Repeated nervousness in MRP recommendations may indicate unstable parameters rather than unstable demand.

8.4 Technology and contemporary developments

Modern enterprise resource planning and advanced planning systems automate explosion, netting, pegging and exception reporting. They may also connect MRP with supplier portals, barcode transactions, warehouse systems and manufacturing execution systems.

Artificial intelligence can assist with lead-time estimation, anomaly detection, parameter recommendation and exception prioritization. It should not silently override BOM validity, approved engineering changes or authorization controls. AI-generated recommendations require explainability, data lineage, human review and protection against biased or corrupted transactional data.

9. Limitations and Critical Evaluation

MRP’s deterministic logic has several limitations:

1. Parameter sensitivity: Small changes in lead time, lot size or inventory accuracy can shift releases substantially.
2. Nervousness: Frequent demand or supply changes can cause repeated order rescheduling.
3. Infinite-capacity assumption: Basic MRP may ignore resource bottlenecks.
4. Forecast dependence: Finished-product forecasts and MPS decisions remain uncertain.
5. BOM rigidity: Fixed usage quantities may not represent actual process variation.
6. Execution gaps: A mathematically correct plan fails if transactions are late or inaccurate.
7. Cost blindness: Basic netting does not by itself optimize total cost, service, risk or working capital.

MRP should therefore be treated as a disciplined planning framework, not an autonomous decision maker. Lean systems may seek to reduce reliance on detailed forecasts for stable repetitive flows, while MRP remains valuable for complex, low-volume, multilevel products and changing production environments. Many organizations use hybrid approaches: MRP for planning and procurement, kanban for repetitive replenishment, and finite scheduling for constrained resources.

Best-Practice Checklist

Before approving an MRP plan, the planner should ask:

• Is the MPS time-phased and authorized?
• Is the BOM current and effectivity-controlled?
• Are inventory balances physically credible?
• Are scheduled receipts confirmed rather than merely assumed?
• Are lot sizes and safety stocks policy-based?
• Are lead times expressed in the correct calendar units?
• Have releases been offset correctly?
• Can capacity and supplier commitments support the plan?
• Can every important shortage be pegged to a demand source?
• Are overrides documented and reviewed?

Chapter Summary

MRP translates a master production schedule into time-phased material actions. Its essential logic consists of gross-requirement calculation, netting of available supply, lot-sizing, planned-order receipt generation, lead-time offsetting and multilevel BOM explosion. The projected available balance is updated period by period using beginning inventory, scheduled receipts, planned receipts and gross requirements. Net requirements arise when available supply cannot satisfy demand while preserving the required safety stock.

Explosion transfers parent planned-order releases into component gross requirements. Offsetting moves planned receipts backward by lead time to determine release dates. Pegging provides traceability from component demand to parent items and, where required, to customer orders. Accurate results depend on valid BOMs, inventory records, calendars, lead times and planning policies.

At postgraduate level, MRP should be evaluated not only as a calculation procedure but also as a governance and decision-support system. Its recommendations must be tested against capacity, supplier reliability, cost, quality, engineering change and customer priority. Technology can improve speed and visibility, but it cannot compensate for uncontrolled master data or weak managerial judgment.

Key Terms

Independent demand: Demand originating from customers, forecasts or external commitments.

Dependent demand: Demand calculated from the requirements of another item.

Master production schedule: Time-phased statement of planned finished-product output.

Bill of materials: Structured record of components and usage quantities required for an item.

Gross requirement: Total demand for an item before available supply is considered.

Scheduled receipt: An already-released order expected to arrive in a specified period.

Projected available balance: Expected inventory remaining after requirements and receipts are considered.

Net requirement: Additional quantity needed after accounting for available inventory and scheduled receipts.

Planned-order receipt: Proposed supply scheduled to arrive in a specified period.

Planned-order release: Proposed order launch date after lead-time offsetting.

Netting: Process of subtracting available and scheduled supply from gross requirements.

Explosion: Translation of parent requirements into component requirements through the BOM.

Offsetting: Moving a planned receipt backward by its lead time.

Pegging: Tracing a requirement or order to its originating parent or customer demand.

Lot-for-lot: Lot-sizing rule in which the planned receipt equals the net requirement.

Safety stock: Inventory held to protect against uncertainty or service risk.

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

Nervousness: Frequent and potentially disruptive changes in MRP recommendations.

Exception message: System alert identifying a condition requiring planner attention.

Review Questions

Short Answer Questions

1. What is the difference between independent and dependent demand?
2. Define projected available balance and identify its principal inputs.
3. Why are planned-order releases usually earlier than planned-order receipts?
4. What is the purpose of pegging in an MRP system?
5. State two data-quality conditions necessary for reliable MRP calculations.

Long Answer Questions

1. Explain the complete sequence of netting, lot-sizing, offsetting and explosion in a multilevel MRP system.
2. Compare lot-for-lot, fixed-order-quantity and fixed-period lot-sizing policies, including their operational implications.
3. Discuss why a mathematically valid MRP plan may nevertheless be infeasible in a manufacturing environment.
4. Explain the role of safety stock in the net-requirement equation and discuss circumstances in which the policy might be relaxed.
5. Evaluate the use of AI in MRP parameter setting and exception management, including governance safeguards.

Analytical / Application Questions

1. An item has beginning inventory of 50 units, safety stock of 10 units, a scheduled receipt of 20 units in week 2, and gross requirements of 30 and 70 units in weeks 1 and 2. Using lot-for-lot ordering, calculate the net requirement and ending projected available balance for each week.
2. A parent item has planned-order releases of 60 units in week 5 and 40 units in week 7. Each parent requires three units of component X. The parent lead time is two weeks and X has a one-week lead time. Determine the gross requirements for X and explain the timing of the parent releases that generate them.
3. A planner observes repeated expedite and cancel messages although customer demand is stable. Diagnose at least four possible causes and propose a data-governance and process-improvement response.

Multiple Choice Questions with Answers

Question 1

Which MRP record represents demand before available inventory and scheduled receipts are considered?

A. Projected available balance

B. Gross requirement

C. Planned-order release

D. Safety stock

Correct Answer: B. Gross requirement

Question 2

An item has a beginning projected balance of 30 units, gross requirement of 80 units, scheduled receipt of 40 units, and safety stock of 10 units. Under the stated netting convention, what is the net requirement?

A. 0 units

B. 10 units

C. 20 units

D. 60 units

Correct Answer: B. 10 units

Question 3

Under lot-for-lot sizing, a net requirement of 47 units produces which planned-order receipt?

A. 40 units

B. 47 units

C. 50 units

D. 94 units

Correct Answer: B. 47 units

Question 4

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

A. Week 3

B. Week 5

C. Week 6

D. Week 11

Correct Answer: C. Week 6

Question 5

A parent planned-order release is 25 units and each parent uses four units of a component. What is the component gross requirement?

A. 6.25 units

B. 21 units

C. 29 units

D. 100 units

Correct Answer: D. 100 units

Question 6

Which MRP procedure traces a component requirement back to its originating parent or customer order?

A. Netting

B. Offsetting

C. Pegging

D. Lot sizing

Correct Answer: C. Pegging

Question 7

A fixed-order-quantity rule uses a lot size of 50 units. If the net requirement is 120 units, what receipt quantity is generated by the simple multiple rule?

A. 120 units

B. 150 units

C. 170 units

D. 200 units

Correct Answer: B. 150 units

Question 8

Why should component requirements generally be exploded from parent planned-order releases rather than finished-product delivery dates?

A. Components are always more expensive than finished products

B. The component is needed according to the parent’s production or assembly timing

C. Finished products cannot have gross requirements

D. Scheduled receipts apply only to finished products

Correct Answer: B. The component is needed according to the parent’s production or assembly timing

Question 9

Which condition is most directly associated with MRP nervousness?

A. Stable lead times and accurate inventory records

B. Frequent changes to demand, supply or planning parameters

C. Use of a multilevel BOM

D. A fixed safety-stock policy

Correct Answer: B. Frequent changes to demand, supply or planning parameters

Question 10

What is a principal limitation of basic MRP?

A. It cannot represent dependent demand

B. It cannot calculate planned-order releases

C. It may generate a material plan without fully checking capacity feasibility

D. It cannot use scheduled receipts

Correct Answer: C. It may generate a material plan without fully checking capacity feasibility