Material Requirements Planning and Enterprise Systems

Introduction

Material Requirements Planning (MRP) is a time-phased planning method used to determine what materials and components are required, how many are required, and when they should be available. It converts a production plan for finished goods into detailed requirements for purchased items, subassemblies, and internally manufactured components. MRP is therefore a central link between demand management, production scheduling, purchasing, inventory control, and shop-floor operations.

MRP is especially valuable where demand for components is dependent on the production of another item. For example, the demand for wheels, seats, and engines depends on the number of vehicles scheduled for production. This differs from independent demand, such as customer demand for finished vehicles, which must normally be forecast or observed directly.

Modern organizations rarely operate MRP as an isolated calculation. Closed-loop MRP connects material planning with capacity and execution feedback. MRP II extends the approach to manufacturing resources, finance, and management planning. Enterprise Resource Planning (ERP) integrates these activities across the organization, often using a common database and real-time transaction processing.

Learning Objectives

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

1. Distinguish independent and dependent demand.
2. Interpret and construct a bill of materials (BOM).
3. Explain the role of the master production schedule (MPS) and inventory records.
4. Apply the logic of MRP to calculate gross requirements, projected available balance, net requirements, planned order receipts, and planned order releases.
5. Compare common lot-sizing methods and recognize their assumptions.
6. Explain closed-loop MRP, MRP II, and ERP.
7. Evaluate implementation, data-quality, governance, and operational issues in integrated planning systems.

1. Foundations of MRP

Independent and dependent demand

Independent demand originates outside the production system, usually from customers or markets. Examples include demand for finished products, service parts, and replacement items. It is commonly estimated using forecasts, customer orders, or statistical methods.

Dependent demand is derived from the planned production of another item. If one finished product requires four bolts, the gross requirement for bolts is four times the planned production quantity, subject to inventory, scrap, and engineering specifications. Dependent demand is therefore calculated rather than forecast independently.

MRP is most appropriate when:

• products have identifiable components;
• component relationships can be represented in a BOM;
• requirements are time-phased;
• inventory and lead-time data are reasonably accurate; and
• production and purchasing transactions are recorded systematically.

MRP is less suitable when demand is highly unpredictable, products are fully continuous-flow commodities, or the data required for planning are unreliable.

The central MRP questions

For every item and time period, MRP answers three questions:

1. What is required? This is the gross requirement.
2. What is already available or expected? This includes inventory and scheduled receipts.
3. What must be ordered or produced, and when? This is expressed through planned order receipts and releases.

The logic is not simply “order when stock is low.” It considers future requirements, existing orders, lead times, order policies, and the structure of the product.

2. The Three Primary MRP Inputs

2.1 Master Production Schedule

The MPS specifies which finished products will be produced, in what quantities, and in which time periods. It translates aggregate production plans into a more detailed, feasible schedule.

An MPS normally includes:

• finished-product identity;
• planning periods, such as weeks;
• production quantities;
• customer orders and forecast demand;
• available finished-goods inventory;
• confirmed production commitments; and
• production or delivery dates.

The MPS must be realistic. If it promises more production than available labor, machinery, materials, or supplier capacity can support, the resulting MRP plan will be mathematically consistent but operationally impossible.

2.2 Bill of Materials

A BOM is a structured description of every component, subassembly, raw material, and quantity required to make one unit of a parent item. It is often shown as a product tree.

For example, suppose one desk requires:

• one desktop;
• four legs; and
• eight screws.

If each leg requires one foot pad, the BOM is:

BOM accuracy requires correct quantities, units of measure, effective dates, engineering revisions, scrap factors, and identification of alternative or interchangeable components. A “phantom” assembly may be included for planning or design purposes but not stocked as a separate physical item. A modular BOM may represent product options and variants.

The quantity relationship can be expressed as follows. If a parent requirement is P units and each parent requires q units of a component, then the component gross requirement is:

Here, G is the component gross requirement in units. This relationship assumes that the BOM quantity is correct and that scrap, yield loss, and design changes are not yet separately included. If a scrap proportion s is included as a planning allowance, a simple adjusted requirement may be calculated as:

where s is expressed as a decimal. The adjustment should be used only where the organization’s planning policy treats scrap in this manner; some systems represent scrap through separate item or operation parameters.

2.3 Inventory records

The inventory record contains the time-phased information needed for each item. Important fields include:

• beginning or on-hand inventory;
• gross requirements;
• scheduled receipts from existing orders;
• planned order receipts;
• planned order releases;
• safety stock;
• lead time;
• lot-size rule;
• order policy;
• allocated or reserved inventory; and
• open purchase or manufacturing orders.

Inventory records must distinguish a scheduled receipt from a planned receipt. A scheduled receipt is an existing order that has been released and is expected to arrive. A planned order receipt is a recommended future order that has not necessarily been released.

3. MRP Logic and Core Calculations

MRP is usually performed in discrete time buckets, such as days or weeks. The following notation is used:

A basic projected available balance calculation is:

This equation assumes that all relevant receipts and requirements are recorded in the same time bucket and that inventory is measured in consistent units. If safety stock must be protected, the planned receipt must be large enough to prevent the projected balance from falling below SS. A general net-requirement expression is:

This form applies when the opening balance and scheduled receipt are available before satisfying the current gross requirement. In practice, software may calculate the projected balance sequentially and apply safety stock according to specific configuration rules.

The planned order receipt depends on the lot-sizing rule. If the policy is lot-for-lot (L4L), the planned receipt normally equals the net requirement:

The planned order release is offset by lead time. If the lead time is L periods and there are no timing constraints inside the period, then:

This means that a receipt required in period t must be released L periods earlier. The equation assumes a fixed, known lead time and an effective planning calendar.

Worked example: lot-for-lot planning

A component has 20 units on hand at the beginning of week 1. There are no scheduled receipts, no safety stock, and a one-week lead time. Gross requirements are 10, 25, and 15 units in weeks 1, 2, and 3 respectively.

For week 2:

For week 3:

Because lead time is one week, the week-2 receipt is released in week 1, and the week-3 receipt is released in week 2. The example illustrates why MRP is time-phased: an order is released before the material is physically needed.

4. Lot-Sizing Decisions

Lot sizing determines the quantity to be ordered or produced when a net requirement occurs. It affects setup cost, ordering cost, inventory holding cost, space, obsolescence, and supplier convenience.

Lot-for-lot

Lot-for-lot orders exactly the net requirement in each period. It minimizes planned leftover inventory and is useful for expensive, perishable, customized, or rapidly changing items. However, it may create many purchase orders or production setups.

Fixed-order quantity

A fixed-order quantity orders a predetermined quantity, such as 500 units, whenever a requirement occurs. It may reflect supplier minimums, packaging quantities, economic order quantities, or machine batch sizes. It can produce excess inventory.

Economic order quantity

For relatively stable independent demand, the classical EOQ is:

where Q* is the order quantity in units, 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 model assumes known and constant demand, constant lead time, instantaneous replenishment, no quantity discounts, and no shortages. These assumptions are often unrealistic in MRP environments, so EOQ should be treated as a policy aid rather than an automatic answer.

Period-order quantity and part-period balancing

Period-order quantity groups requirements over a selected number of periods. Part-period balancing adds periods while attempting to balance incremental holding cost against an additional ordering or setup cost. These methods can reduce order frequency but require careful review when demand is volatile.

Choosing a lot-sizing rule

A professional decision considers:

• demand pattern and variability;
• supplier minimum order and package size;
• setup or ordering cost;
• holding cost and storage capacity;
• product value and obsolescence risk;
• shelf life and quality constraints;
• service-level requirements; and
• production flexibility.

No lot-sizing method is universally optimal. The policy should be periodically reviewed rather than embedded permanently in software without managerial oversight.

5. MRP Explosion and Multilevel Planning

The term explosion describes the process of translating a parent requirement through each BOM level. If 100 desks are scheduled and each desk needs four legs, the gross requirement for legs is 400. If each leg needs one foot pad, the gross requirement for foot pads is also 400, before considering inventory and other orders.

For a multilevel product, planning normally proceeds from the top-level MPS item toward lower-level components. Low-level coding assigns an item to the lowest level at which it appears in the BOM. This helps ensure that requirements for the same component are consolidated correctly across different branches of the product structure.

MRP can produce requirements that appear larger than the final production quantity because the same component may be used in multiple subassemblies. It may also produce requirements in different periods because each level has its own lead time. Accurate lead times are therefore as important as accurate quantities.

6. From MRP to Closed-Loop MRP

Early MRP systems primarily calculated material requirements. They did not necessarily test whether available work centres, labor, tooling, or supplier capacity could support the plan. Closed-loop MRP added feedback and control.

A closed-loop system connects:

1. production planning;
2. MPS development;
3. MRP calculation;
4. capacity requirements planning;
5. shop-floor and purchasing execution; and
6. feedback on actual progress, shortages, delays, and capacity.

Capacity requirements planning compares planned work with available capacity. If a work centre is overloaded, management may revise the MPS, alter routing, authorize overtime, subcontract work, change lot sizes, or reschedule orders. The “loop” is closed because actual results influence subsequent plans.

Closed-loop MRP does not guarantee feasible production. It improves the ability to detect infeasibility and respond systematically. Its performance depends on accurate routings, work-centre calendars, labor standards, queue information, and transaction discipline.

7. MRP II: Manufacturing Resource Planning

MRP II broadens closed-loop MRP into an integrated manufacturing planning system. It commonly includes:

• business and sales planning;
• production and aggregate planning;
• MPS;
• MRP;
• capacity planning;
• purchasing and shop-floor control;
• inventory and cost information; and
• financial evaluation.

MRP II supports “what-if” analysis. For example, planners may assess whether a sales increase can be met through overtime, additional equipment, subcontracting, or a revised delivery promise. Financial information helps management evaluate the consequences of inventory investment, capacity expansion, and production alternatives.

MRP II is primarily a manufacturing planning philosophy and system architecture. It is broader than material calculation but narrower than the organization-wide scope normally associated with ERP.

8. Enterprise Resource Planning

ERP integrates processes across functions using shared data, standardized transactions, and interconnected modules. Typical modules include:

• sales and distribution;
• demand management;
• procurement;
• inventory and warehouse management;
• production planning and control;
• quality management;
• maintenance;
• finance and accounting;
• human resources; and
• supply-chain management.

A customer order can therefore trigger or influence delivery planning, inventory allocation, MRP, purchasing, production, invoicing, and financial reporting. The major value of ERP is not merely automation. It is the creation of a common organizational record and coordinated process ownership.

MRP, MRP II, and ERP compared

ERP does not replace managerial judgment. It processes rules and data at scale, but decisions about priorities, customer commitments, supplier relationships, risk, and exceptions still require responsible human oversight.

9. Implementation and Data Governance

Data quality

MRP and ERP systems amplify both good and bad data. Common errors include:

• incorrect BOM quantities;
• obsolete engineering revisions;
• wrong lead times;
• inaccurate on-hand balances;
• unrecorded scrap or losses;
• duplicate item codes;
• incorrect units of measure;
• unclosed purchase or production orders; and
• inaccurate safety-stock or lot-size parameters.

A disciplined organization establishes item-master ownership, engineering-change control, cycle counting, supplier-data review, and regular parameter audits.

Transaction discipline

A system cannot plan accurately if physical events are not recorded. Receipts, issues, transfers, completions, rejects, returns, and order changes should be recorded promptly. Barcode scanning, radio-frequency identification, mobile terminals, and warehouse management systems can improve transaction accuracy, but technology does not eliminate the need for clear procedures.

Implementation principles

Successful implementation generally includes:

1. documenting current and desired processes;
2. defining data ownership and approval authority;
3. cleansing item, BOM, routing, and inventory data;
4. configuring policies rather than excessive custom code;
5. piloting with a manageable product family or site;
6. training users in both system operation and planning logic;
7. measuring results after go-live; and
8. maintaining continuous improvement.

Governance, security, and ethics

ERP data may include supplier prices, employee information, customer details, production costs, and strategic forecasts. Access should follow role-based authorization and segregation of duties. Audit trails should identify who changed a BOM, approved a purchase order, or altered a planning parameter.

Ethical issues include the use of supplier data, concealment of shortages, manipulation of inventory records, inappropriate access to commercial information, and automated decisions that disadvantage particular suppliers without justified criteria. Forecasting and AI tools must be explainable enough for planners to challenge unusual recommendations. Organizations should also address cybersecurity, data retention, privacy obligations, and business continuity.

10. Technology and Contemporary Developments

Cloud ERP makes enterprise systems accessible without every organization owning its own infrastructure, although it introduces dependency on connectivity, vendors, and contractual service levels. Application programming interfaces can connect ERP with e-commerce, supplier portals, transport systems, warehouse automation, and manufacturing execution systems.

Advanced analytics can identify abnormal usage, late suppliers, excess inventory, and likely stockouts. Machine-learning models may improve forecasts or estimate lead-time variability, but they should complement—not replace—BOM discipline, operational knowledge, and exception management. Digital twins and control towers can provide broader supply-chain visibility, while Internet of Things devices can report machine status and material movement.

These technologies create new risks: poor-quality sensor data, opaque algorithms, cyberattacks, excessive alerts, and overconfidence in automated recommendations. The proper objective is better decisions and resilience, not automation for its own sake.

11. Illustrative Case: Northstar Appliances

Background

Northstar Appliances manufactures 500-millilitre electric kettles. A kettle requires one housing, one heating assembly, one lid, one switch, and two terminal screws. The company uses weekly planning. The MPS schedules 100 kettles in week 3 and 120 in week 4.

Problem

The purchasing department repeatedly expedited screws even though total warehouse inventory appeared sufficient. Investigation showed that the inventory record included 100 screws reserved for a different product and that the supplier lead time had increased from one to two weeks.

Analysis

The gross screw requirements are:

• Week 3: 100 × 2 = 200 screws.
• Week 4: 120 × 2 = 240 screws.

Only unrestricted, usable inventory should offset these requirements. The reserved 100 screws are not available to the kettle plan. If 150 usable screws are on hand and no scheduled receipt exists, week 3 has a net requirement of 50 screws. With a two-week lead time, the purchase release must occur in week 1 for a week-3 receipt.

The company also discovered that the BOM for one kettle had been revised from two to three terminal screws but the ERP item structure had not been updated. The resulting underplanning was a data-governance failure, not a mathematical failure of MRP.

Approach and solution

Northstar took four actions:

1. engineering approved and dated the revised BOM;
2. inventory control separated unrestricted, allocated, and quarantined stock;
3. purchasing updated supplier lead times using recent performance evidence; and
4. planners introduced a weekly exception review for shortages, late orders, and unusual requirements.

The organization retained lot-for-lot planning for screws because their unit value was low but shortages stopped assembly. For the heating assembly, it used a supplier minimum quantity because the supplier required fixed production batches.

Outcome

After three planning cycles, emergency freight declined and assembly interruptions were reduced. The improvement resulted from coordinated master data, inventory status, supplier information, and planner review—not from installing software alone.

Learning points

The case demonstrates that MRP depends on the integrity of the MPS, BOM, inventory records, lead times, and status codes. It also shows why exception management is essential: planners should focus attention on shortages, invalid data, late receipts, and capacity conflicts rather than manually reviewing every normal item.

12. Limitations and Best Practices

MRP can generate nervousness when small changes in the MPS create many rescheduled orders. Long or uncertain lead times, inaccurate forecasts, capacity constraints, engineering changes, and supplier unreliability can reduce plan stability. Systems may also encourage excessive inventory if safety stocks and order quantities are set without analysis.

Best practices include:

• maintain a realistic and controlled MPS;
• use one approved BOM and revision process;
• measure and update lead times;
• distinguish available, allocated, quarantined, and obsolete stock;
• use cycle counting and inventory accuracy targets;
• review lot-sizing and safety-stock policies;
• freeze near-term schedules where practical;
• use exception messages intelligently;
• coordinate MRP with capacity planning and supplier collaboration; and
• measure service, inventory, schedule adherence, expedites, and plan stability together.

MRP is a planning system, not a substitute for sound operations management. Its value is greatest when data, people, processes, and technology reinforce one another.

Chapter Summary

MRP converts a master production schedule into time-phased requirements for components and materials. Its essential inputs are the MPS, BOM, and inventory records. Gross requirements are derived through BOM relationships; net requirements account for available inventory, scheduled receipts, and safety-stock policy; planned receipts are sized using lot-sizing rules; and planned releases are offset by lead time.

Lot-for-lot, fixed-order quantity, EOQ, period-order quantity, and part-period methods involve different trade-offs between ordering effort, setup cost, holding cost, and operational flexibility. Closed-loop MRP adds capacity and execution feedback. MRP II extends the system to broader manufacturing resources and financial planning. ERP integrates planning and transactions across the enterprise.

The effectiveness of these systems depends on accurate BOMs, inventory balances, lead times, routings, calendars, and transaction discipline. Governance, security, ethical data use, cybersecurity, and human review are essential. Contemporary cloud, analytics, IoT, and AI technologies can improve visibility and decision support, but they cannot compensate for poor foundational data or weak management processes.

Key Terms

Bill of materials (BOM): Structured list of components and quantities required to make a parent item.

Closed-loop MRP: MRP connected to capacity planning, execution, and feedback.

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

Enterprise Resource Planning (ERP): Integrated system supporting cross-functional organizational processes and data.

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

Fixed-order quantity: Lot-sizing rule using a predetermined order quantity.

Gross requirement: Total quantity needed before considering inventory and scheduled receipts.

Independent demand: Demand originating from customers or markets rather than another item.

Inventory record: Time-phased record of balances, requirements, receipts, releases, and planning parameters.

Lead time: Time between releasing an order and receiving or completing it.

Lot sizing: Determination of the quantity ordered or produced for a requirement.

Master production schedule (MPS): Time-phased plan for producing finished products.

MRP: Material Requirements Planning system for calculating time-phased material needs.

MRP II: Manufacturing Resource Planning approach integrating materials, capacity, manufacturing, and financial information.

Net requirement: Requirement remaining after usable inventory and scheduled receipts are considered.

Planned order receipt: Future receipt recommended by the MRP calculation.

Planned order release: Date on which a planned order should be issued to meet a required receipt date.

Scheduled receipt: Quantity from an existing released order expected in a specified period.

Safety stock: Inventory deliberately maintained to protect against uncertainty or variation.

Review Questions

Short Answer Questions

1. What is the difference between independent and dependent demand?
2. Identify the three primary inputs to an MRP system.
3. Why must planned order releases be offset from planned order receipts?
4. What is the purpose of a low-level code in multilevel MRP?
5. State two data-quality problems that can cause MRP failure.

Long Answer Questions

1. Explain the structure and purpose of a bill of materials, including the importance of quantities, revisions, units, and effective dates.
2. Describe the MRP calculation sequence from gross requirements through planned order releases.
3. Compare lot-for-lot, fixed-order quantity, and EOQ approaches, including their assumptions and operational consequences.
4. Explain how closed-loop MRP and MRP II extend basic MRP.
5. Discuss how ERP integrates materials planning with purchasing, production, finance, and other functions.

Analytical / Application Questions

1. A product requires three components of item X. The MPS schedules 80 units in week 4 and 60 units in week 5. If 100 usable units of X are available and there are no scheduled receipts, calculate the gross and net requirements for each week using lot-for-lot planning. Assume no safety stock.
2. A component has a two-week lead time, a fixed order quantity of 500 units, and gross requirements of 300 and 450 units in consecutive weeks. Explain when orders should be released and how the fixed quantity affects projected inventory.
3. An ERP system produces repeated shortages even though physical stock appears adequate. Develop a diagnostic plan covering BOM accuracy, inventory status, allocations, lead times, open orders, transaction discipline, and user governance.

Multiple Choice Questions with Answers

Question 1

Which input translates the finished-product plan into component relationships?

A. Bill of materials

B. Supplier invoice

C. General ledger

D. Employee roster

Correct Answer: A. Bill of materials

Question 2

Demand for components derived from a planned production schedule is called:

A. Independent demand

B. Dependent demand

C. Seasonal demand

D. Random demand

Correct Answer: B. Dependent demand

Question 3

A component has 20 units available and a gross requirement of 35 units, with no scheduled receipt or safety stock. Its net requirement is:

A. 15 units

B. 20 units

C. 35 units

D. 55 units

Correct Answer: A. 15 units

Question 4

If a planned order receipt is required in week 6 and lead time is two weeks, the planned release is generally in:

A. Week 4

B. Week 5

C. Week 6

D. Week 8

Correct Answer: A. Week 4

Question 5

Under lot-for-lot planning, the planned order receipt normally equals the:

A. Gross requirement

B. Net requirement

C. Safety stock

D. Opening inventory

Correct Answer: B. Net requirement

Question 6

Which feature most clearly distinguishes closed-loop MRP from basic MRP?

A. Use of product labels

B. Feedback from capacity and execution

C. Elimination of lead times

D. Removal of inventory records

Correct Answer: B. Feedback from capacity and execution

Question 7

MRP II extends MRP primarily by integrating:

A. Only customer complaints

B. Manufacturing resources and financial planning

C. Only warehouse locations

D. Only product advertising

Correct Answer: B. Manufacturing resources and financial planning

Question 8

Which is a scheduled receipt?

A. An unapproved suggestion for a future order

B. An existing released order expected to arrive

C. A forecast without a date

D. A deleted purchase order

Correct Answer: B. An existing released order expected to arrive

Question 9

Using Q* = √(2DS ÷ H), if D = 100 units/year, S = 18 currency units/order, and H = 2 currency units/unit/year, the EOQ is:

A. 30 units

B. 42.4 units

C. 60 units

D. 180 units

Correct Answer: B. 42.4 units

Question 10

Which ERP practice best supports data governance?

A. Allowing all users to change BOMs freely

B. Using role-based access and controlled revisions

C. Ignoring inventory transactions until month-end

D. Deleting audit trails

Correct Answer: B. Using role-based access and controlled revisions