Chapter 9 Master Production Scheduling and MRP Logic

Master Production Scheduling and MRP Logic

Introduction

Inventory control and material requirements planning (MRP) connect market demand with the detailed purchasing and production decisions required to satisfy it. Aggregate planning establishes broad output, workforce, and capacity intentions. The master production schedule (MPS) converts those intentions into specific end-item quantities and completion dates. MRP then translates the MPS into time-phased requirements for components, subassemblies, raw materials, and purchased items.

The central logic is deceptively simple: determine what is required, subtract what is already available or scheduled to arrive, and plan sufficient replenishment early enough to meet the requirement date. In practice, the logic must cope with multilevel bills of material (BOMs), lot-sizing rules, safety stock, lead times, scheduled receipts, order policies, planning time fences, engineering changes, and uncertain data.

This chapter explains how MPS and MRP operate as an integrated planning system. It emphasizes the managerial interpretation of MRP outputs rather than treating the system as merely a computational routine.

Learning Objectives

1. From Aggregate Planning to the MPS

Aggregate planning normally uses product families and monthly or quarterly periods. It balances forecast demand, backlog, capacity, workforce, inventory, subcontracting, and cost. Its output is not usually a feasible work-order schedule. It may state, for example, that the firm should produce 2,400 units of a product family in April.

The MPS disaggregates this intention into identified end items, quantities, and time buckets. An MPS for a configure-to-stock manufacturer may specify 400 Model A units in week 4 and 300 Model B units in week 5. For make-to-order environments, the MPS may combine confirmed orders, forecast demand, and strategic stock requirements.

The MPS is both a demand statement and a capacity commitment. It should therefore be checked against rough-cut capacity planning (RCCP), which tests critical resources such as labor hours, bottleneck machines, tooling, and supplier capacity. An MPS that is mathematically neat but capacity-infeasible will generate unstable MRP recommendations.

Planning level	Typical horizon	Main question	Output
Aggregate plan	Months to years	How much family-level capacity is needed?	Family production, workforce, inventory plan
MPS	Weeks to months	Which end items are completed when?	End-item quantities and dates
MRP	Days to weeks	Which components are needed when?	Planned receipts and releases
Shop-floor and purchasing control	Days to weeks	What should be executed now?	Work orders, purchase orders, dispatch priorities

2. Core Data Structures

2.1 The master production schedule

An MPS record normally includes forecast demand, customer orders, the selected production quantity, projected available balance, and ATP. The schedule may be stated in finished units, standard batches, or final assembly options. Its time bucket must match the decision problem: weekly buckets are common for tactical planning, while daily buckets may be needed near the frozen zone.

2.2 The bill of material

A BOM describes the parent–component relationship. If one bicycle requires two wheels and each wheel requires one tire, the BOM has two levels: bicycle → wheel and wheel → tire. The quantity per parent is called the usage quantity or quantity-per. A planning BOM may differ from an engineering BOM because it can include planning substitutes, phantom assemblies, common components, or percentage scrap.

For a component used at several levels, MRP must avoid both omission and double counting. Low-level coding assigns each item the lowest level at which it appears in the product structure, allowing requirements to be processed in a logical order.

2.3 Inventory and planning records

Data accuracy is not an administrative detail. An incorrect inventory balance, BOM quantity, or lead time propagates through every dependent item.

3. MRP Logic

MRP uses independent demand for end items to calculate dependent demand for components. Independent demand originates outside the product structure, such as a customer order or forecast. Dependent demand is derived from the planned production of a parent.

3.1 Gross requirements and BOM explosion

If a parent has a planned order receipt of P_t units in period t, and each parent requires q units of a component, the component’s gross requirement generated by that parent is:

where GR_t is the component gross requirement in units and q is units of component per parent. If several parents use the component, requirements are summed across parents. Scrap can be incorporated through a scrap factor s when the factor represents the proportion lost:

This expression assumes that scrap is proportional and that 0 ≤ s < 1. A fixed setup loss should not be modeled with this percentage formula; it should be represented separately.

Dependent requirements are normally timed to the parent’s planned order release, not its receipt. If a component is consumed at final assembly, its requirement occurs when assembly begins. If the BOM specifies a lead-time offset or operation-specific usage point, the requirement must be placed in that earlier bucket.

3.2 Netting

The projected available balance is the inventory expected to remain after satisfying requirements and adding receipts. A general form is:

The formula assumes all quantities are expressed in the same units and that receipts are usable in the stated period. If safety stock SS_t must be protected, a net requirement arises when the balance before a new planned receipt would fall below that level:

This formulation assumes that planned receipts are initially excluded from the calculation of the shortage. Different software systems may display net requirements using equivalent but differently ordered logic, so the planning policy must be documented.

3.3 Lot sizing

If the calculated net requirement is 137 units, the planned receipt depends on the lot-sizing policy. Common policies include:

Policy	Rule	Typical use
Lot-for-lot	Receipt equals net requirement	Expensive, variable, or short-life items
Fixed lot size	Receipt is a specified multiple or quantity	Process constraints or supplier packs
Economic order quantity	Receipt follows an economically calculated batch	Relatively stable demand
Period-order quantity	One receipt covers a defined number of periods	Balancing ordering and holding costs
Minimum/multiple	Receipt must meet minimum and packaging multiple	Supplier or handling constraints

The classical economic order quantity is sometimes used as an input, but it is not universally appropriate in MRP. The familiar expression is:

where Q* is the economic order quantity, D is annual demand in units per year, S is ordering or setup cost per order, and H is annual holding cost per unit. The formula assumes relatively constant demand, instantaneous replenishment, no quantity discounts, and a constant unit holding cost. MRP environments often violate these assumptions; therefore, capacity, supplier multiples, and schedule synchronization may dominate the purely cost-based quantity.

3.4 Lead-time offsetting

A planned order receipt must be released early enough to arrive when needed. If the receipt is required in period t and lead time is L time buckets, the basic release period is:

Lead time must be measured in the same buckets as the schedule. A two-week lead time is not necessarily two planning periods if the calendar uses monthly buckets. In a multilevel BOM, the release of a parent creates a gross requirement for its components; component orders are then offset by their own lead times. Queue, setup, run, inspection, transit, and receiving time should be included where relevant.

4. Worked MRP Example

Consider a component X used in a finished product. The planning horizon has six weekly periods. Beginning inventory is 80 units, safety stock is 20 units, lead time is one week, and the lot-sizing rule is lot-for-lot. A scheduled receipt of 60 units arrives in week 2. The MPS generates parent releases that require X as follows: 50 units in week 1, 70 in week 2, 40 in week 3, 90 in week 4, and 30 in week 5.

The MRP record is calculated as follows. In week 1, available inventory before a new receipt is 80 − 50 = 30, which is above safety stock; no planned receipt is required. In week 2, the balance is 30 + 60 − 70 = 20, exactly the safety stock. In week 3, the balance before a planned receipt is 20 − 40 = −20. To finish with 20 units, the net requirement is 40 units. Under lot-for-lot, the planned receipt is 40 in week 3, and the balance becomes 20. In week 4, the pre-receipt balance is 20 − 90 = −70, so a 90-unit receipt is required to finish with 20. In week 5, the pre-receipt balance is 20 − 30 = −10, so a 30-unit receipt is required. Week 6 has no requirement, leaving 20 units.

The planned receipts in weeks 3–5 are released in weeks 2–4. In a real system, the week-2 release of 40 units would be subject to supplier calendars, approval status, and available capacity. The example also shows why scheduled receipts must be distinguished from planned receipts: scheduled receipts are commitments already released, whereas planned receipts are recommendations generated by MRP.

5. Multilevel Explosion and Pegging

MRP explodes the MPS through every relevant BOM level. Suppose one finished unit requires two assemblies A and one component B. Each A requires three units of component C. If the MPS calls for 100 finished units, the gross requirement is 200 A, 100 B, and 600 C, assuming no inventory, scrap, or alternative sources. C is driven by the planned release of A, not necessarily by the finished-good completion date.

Pegging provides the reverse trace. It identifies the parent demand, customer order, or MPS line that caused a component requirement. A planner can therefore ask, “Why does the system recommend 240 units of this part?” and trace the quantity to particular finished products and dates. Pegging supports shortage analysis, customer-priority decisions, engineering-change evaluation, and cancellation of unnecessary orders. It is especially valuable when a component is common to many products.

A component may be both independently forecast and dependently required. Double counting is a serious risk. Forecast consumption, order-policy design, or a demand-time fence may be used to prevent the same demand from entering the plan twice.

6. Available-to-Promise

ATP addresses a customer-facing question: how many units can be promised to a new order without violating existing commitments? For a simple MPS, ATP in the first period can be represented as beginning available inventory plus the first MPS receipt minus customer orders until the next MPS receipt. For subsequent MPS receipts, ATP is the MPS quantity minus orders through the period before the next MPS receipt.

where ATP_i is available-to-promise associated with receipt i, MPS_i is the scheduled MPS receipt in that interval, Available_i is beginning uncommitted supply for the first interval, and the summation covers customer orders from interval i through the period immediately before the next MPS receipt j. The exact first-interval treatment varies by system configuration.

ATP is not the same as projected available balance. Projected balance considers all planned demand and supply, including forecasts and components; ATP focuses on uncommitted finished-goods supply that can be promised to customers. In capable-to-promise systems, capacity and component availability may also be checked before a promise is made.

7. Planning Time Fences and Schedule Stability

A planning time fence divides the planning horizon into zones with different change rules. A common arrangement is:

The fence need not be identical for every item. It should reflect cumulative lead time, supplier flexibility, setup economics, customer service commitments, and the cost of disruption. A frozen zone that is too long reduces responsiveness; one that is too short causes expediting, rescheduling, obsolete material, and loss of supplier credibility.

Time fences are governance mechanisms, not merely software parameters. Exception authority, escalation rules, reason codes, and change-impact analysis should be specified. A schedule change inside the frozen zone should show its effects on capacity, material availability, customer promises, and financial exposure.

8. Integrated Applied Case: Orion Medical Devices

Background

Orion Medical Devices assembles a disposable infusion pump. Demand is volatile, but hospitals require reliable delivery. The finished pump uses one control module, one housing, and two battery packs. The control module uses one circuit board and four connectors. Circuit boards have a four-week supplier lead time; connectors have a two-week lead time. The assembly plant has a one-week final-assembly lead time.

Problem

Sales accepted several hospital orders and then revised the forecast upward. The MPS was increased without checking whether circuit boards could support the new completion dates. MRP consequently produced planned order releases that were later than the supplier lead time. Planners responded with costly expediting, while some lower-priority orders were delayed.

Analysis

The team first froze the next two weeks of final assembly and separated firm hospital orders from forecast demand. It then reviewed the BOM, discovered that the connector quantity had changed after an engineering revision, and corrected the effective date. Pegging identified which circuit-board requirements supported emergency hospital orders. RCCP showed that final assembly had sufficient capacity, but the circuit-board supplier did not.

Approach and solution

Orion established a four-week component fence for circuit boards, a two-week fence for connectors, and a two-week final-assembly fence. Within the frozen zones, only the supply-chain director could authorize changes. ATP was recalculated using confirmed orders rather than treating the entire forecast as customer-committed supply. The firm negotiated a scheduled receipt with the circuit-board supplier, introduced a controlled safety-stock policy for common connectors, and required engineering changes to carry an effective date and supersession rule.

Outcome

The revised plan reduced emergency orders and made customer promises more credible. Some forecast demand was deliberately postponed rather than converted into infeasible MPS quantities. The main improvement did not come from a more sophisticated algorithm; it came from accurate master data, disciplined fences, cross-functional review, and visible pegging.

Learning points

9. Limitations, Governance, and Contemporary Practice

MRP is often described as a deterministic system, but its inputs are uncertain. Forecast error, supplier disruption, yield loss, variable lead time, and inaccurate inventory records can produce apparently precise but unreliable recommendations. MRP also tends to assume that capacity can be addressed separately; this is why MRP should be integrated with capacity planning, supplier collaboration, and finite scheduling when constraints are severe.

Common implementation failures include excessive nervousness, inappropriate lot sizes, obsolete BOMs, unrecorded scrap, inaccurate lead times, and uncontrolled manual overrides. Performance should be monitored through schedule adherence, shortage frequency, inventory record accuracy, supplier on-time delivery, planned-order conversion, expedite cost, and forecast-error measures.

Modern enterprise resource planning and advanced planning systems can recalculate plans rapidly, simulate alternatives, and connect MRP with supplier portals, warehouse systems, and customer-order promising. Artificial intelligence can assist with anomaly detection, lead-time estimation, demand sensing, and exception prioritization. It should not replace accountable planning judgment. AI recommendations require traceable data, explainable decision rules, controls against systematic bias, and human approval for high-impact schedule changes.

Ethically and operationally, planners should avoid promising scarce products selectively without a defensible allocation rule. In regulated industries, lot traceability, audit trails, validated master-data changes, and documented approval are essential. Cybersecurity also matters because manipulation of BOMs, inventory balances, or supplier receipts could create physical and financial harm.

Best practice is to treat MRP as a planning discipline rather than a software installation. Establish ownership for every master-data field, reconcile inventory regularly, review BOM and lead-time accuracy, measure exception quality, maintain realistic time fences, and integrate commercial, engineering, purchasing, production, and finance decisions.

Chapter Summary

The MPS translates aggregate plans into time-phased end-item quantities. MRP explodes those quantities through the BOM, nets gross requirements against inventory and scheduled receipts, applies lot-sizing rules, and offsets planned receipts by lead time to determine release dates. Projected available balance explains expected inventory, while ATP identifies uncommitted finished-goods supply that may be promised to customers. Pegging traces component needs back to parent demand and supports shortage prioritization. Planning time fences stabilize near-term execution while preserving flexibility farther into the future. Effective MRP depends less on computational complexity than on feasible schedules, accurate master data, disciplined governance, capacity coordination, and responsible use of digital technologies.

Key Terms

Master production schedule: A time-phased plan specifying which end items are to be completed and when.

Material requirements planning: A system for calculating time-phased component and material requirements.

Bill of material: A structured representation of parent–component relationships.

BOM explosion: The process of translating parent quantities into component requirements.

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

Scheduled receipt: An order already released and expected to arrive in a stated period.

Projected available balance: Expected ending inventory after requirements and receipts.

Net requirement: Additional quantity needed to meet demand and policy constraints.

Planned order release: The recommended period in which an order should be launched.

Lead-time offsetting: Moving a required receipt earlier by its replenishment lead time.

Available-to-promise: Uncommitted finished-goods supply available for customer orders.

Planning time fence: A boundary governing how much schedule change is permitted.

Rough-cut capacity planning: A high-level test of MPS feasibility against key resources.

Review Questions

Short Answer Questions

Long Answer Questions

Analytical / Application Questions

Multiple Choice Questions with Answers

Question 1

Question 2

Question 3

If beginning inventory is 80 units, gross requirement is 50, and no receipts occur, the projected balance is:

Question 4

Under lot-for-lot sizing, a net requirement of 137 units produces a planned receipt of:

Question 5

A receipt required in week 8 with a three-week lead time should normally be released in:

Question 6

Which record traces a component requirement back to its originating parent demand?

Question 7

Correct Answer: B. Uncommitted finished-goods supply available for promising

Question 8

Correct Answer: B. To prevent or control disruptive near-term schedule changes

Question 9

One finished unit uses four connectors. If 150 finished units are released, the connector gross requirement is:

Gross requirement

Scheduled receipt

Planned receipt

Projected available balance

Planned order release, one week earlier