Materials Planning and Enterprise Operations Systems

Introduction and Context

Materials planning connects market requirements with the physical and informational resources needed to produce goods and deliver services. In a manufacturing organisation, a customer order is translated into a master production schedule, a bill of materials, purchase and production orders, capacity requirements, inventory transactions, and financial commitments. The quality of this translation determines whether the organisation can meet delivery promises without excessive inventory, overtime, expediting, or idle capacity.

The central systems examined in this chapter are material requirements planning (MRP), capacity requirements planning (CRP), manufacturing resource planning (MRP II), and enterprise resource planning (ERP). These systems are not merely software packages. They represent increasingly broad managerial logics for coordinating dependent demand, production capacity, procurement, inventory, finance, sales, engineering, and human decision-making.

MRP answers primarily: what components are needed, how many are needed, and when are they needed? CRP asks whether the planned work can be performed with available resources. MRP II extends the analysis across manufacturing, while ERP integrates manufacturing with enterprise-wide processes such as finance, sales, maintenance, quality, human resources, and supply-chain management.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Explain independent and dependent demand and their implications for planning.
2. Construct and interpret bills of materials and low-level codes.
3. Perform basic MRP netting and planned-order calculations.
4. Explain the relationship between MPS, MRP, CRP, MRP II, and ERP.
5. Evaluate data, capacity, governance, implementation, and behavioural risks.
6. Recommend managerial actions when a plan is infeasible or unstable.

1. Demand Logic and the Planning Hierarchy

Independent demand arises from external customers or markets and must generally be forecast or observed through orders. Dependent demand is derived from the demand for another item. For example, demand for bicycle wheels depends on the number and design of bicycles to be assembled. Dependent demand is therefore calculated from planned parent production rather than forecast independently.

A typical planning hierarchy is:

• Sales and operations planning (S&OP): balances aggregate demand, supply, and financial objectives over medium-term time buckets.
• Master production scheduling (MPS): specifies when end items or major assemblies should be completed.
• Material requirements planning (MRP): translates the MPS into time-phased component and raw-material requirements.
• Capacity requirements planning (CRP): evaluates the work-centre load implied by planned orders.
• Execution and control: releases orders, monitors progress, records receipts, and revises plans.

The hierarchy is iterative rather than strictly one-directional. If CRP reveals insufficient capacity, the MPS may need to change. If suppliers cannot meet component dates, purchasing and scheduling decisions must be reconsidered. Thus, planning is a coordinated feedback process rather than a single calculation.

2. Bills of Materials

A bill of materials (BOM) is a structured description of the components, subassemblies, materials, quantities, and sometimes process-related attributes required to make an item. A single-level BOM lists immediate components. An indented or multilevel BOM shows the product structure across successive levels.

A BOM must distinguish at least three concepts:

• Usage quantity: the number of units of a component required per unit of its parent.
• Effectivity: the dates, serial numbers, model versions, or engineering changes for which the relationship applies.
• Assembly status: whether the item is purchased, made, phantom, configurable, or supplied externally.

If a finished product requires 2 units of subassembly A, and each A requires 3 units of component B, the gross requirement for B is 6 units per finished product. In general, if a component has a chain of parent relationships, its usage per end item is the product of the usage quantities along that path. Where multiple paths exist, the quantities must be added.

A low-level code identifies the lowest level at which an item appears in any product structure. It ensures that all parent requirements are exploded before the item’s total gross requirement is calculated. BOM accuracy is essential: an incorrect quantity, obsolete revision, missing scrap factor, or unrecorded substitute can create systematic shortages or surplus inventory.

Illustrative product structure

Figure: A multilevel BOM; numbers in parentheses indicate quantity per immediate parent.

3. Material Requirements Planning

MRP is a time-phased planning technique for converting end-item schedules into planned orders for components and materials. Its principal inputs are:

1. the MPS;
2. the BOM;
3. inventory records, including on-hand balances, scheduled receipts, lead times, lot-sizing rules, safety stock, and order policies.

The principal output is a set of planned order releases and planned order receipts. A planned order receipt indicates when an order should be available; a planned order release indicates when it should be started or placed, after considering lead time.

The MRP record

For each item and time bucket, an MRP record commonly contains:

• gross requirements;
• scheduled receipts;
• projected available balance;
• net requirements;
• planned order receipts;
• planned order releases.

The basic projected-balance relationship is:

where PAB_t is projected available balance at the end of period t, SR_t is a scheduled receipt, POR_t is a planned order receipt, and GR_t is gross requirement. All quantities must use the same unit and time bucket. The relationship assumes that receipts and requirements are assigned consistently within the period.

If projected availability before planned ordering is insufficient to satisfy the requirement and any specified safety stock, net requirement is:

where NR_t is net requirement and SS_t is required safety stock. This expression assumes that existing projected inventory is usable and that no other reservations or allocations have been omitted.

Lot-sizing converts a net requirement into an order receipt. Under lot-for-lot ordering, the planned receipt equals the net requirement. Under fixed-order quantity, it is the smallest permitted multiple or fixed quantity that covers the requirement. A planned release is offset from its receipt by the item’s lead time; if lead time is two periods, a receipt in period 6 requires release in period 4, subject to calendars and order-processing time.

Worked example: component netting

Suppose a product has an MPS of 100 units in week 5. Each product uses 2 units of component X. Therefore, X has a gross requirement of 200 units in week 5. At the beginning of week 5, 60 usable units are projected, and a scheduled receipt of 50 units is due in week 5. The required safety stock is 20 units. The net requirement is:

With lot-for-lot ordering, the planned receipt is 110 units in week 5. If X has a lead time of two weeks, the planned release is 110 units in week 3. If the supplier sells only in cartons of 50, the receipt must be rounded up to 150 units, unless an approved alternative policy applies. The resulting ending balance would be 60 + 50 + 150 − 200 = 60 units, which is above the stated safety stock but may represent deliberate order-rounding excess.

MRP assumptions and limitations

MRP is most useful when demand is relatively well defined, product structures are known, lead times are credible, and transactions are recorded promptly. It is not a complete optimisation model. Basic MRP often treats lead times as fixed, assumes infinite capacity, and does not automatically represent supplier reliability, setup interactions, quality losses, transport constraints, or economic trade-offs comprehensively.

Common causes of nervousness include frequent MPS changes, inaccurate inventory, unstable lead times, inappropriate safety stocks, and excessive use of exception messages. Planners should distinguish a genuine change in customer need from a system-generated rescheduling signal caused by poor data.

4. Capacity Requirements Planning

CRP translates planned and released orders into time-phased work-centre loads. It uses routing data, operation times, setup times, work-centre calendars, queue assumptions, and order quantities. Its purpose is to identify overloads and underloads before commitments become operational failures.

For an operation, the basic load contribution can be represented as:

where Q is the number of orders or batches, t_s is setup time per batch, q is quantity processed per batch, and t_r is run time per unit. Units are typically machine-hours or labour-hours. If setup is performed once for the entire order rather than once per batch, the batching assumption must be changed.

Available capacity for a period can be estimated as:

where N is the number of equivalent resources, H is scheduled hours per resource, U is planned utilisation, and E is efficiency relative to the standard. The factors must be defined consistently. Utilisation measures the proportion of scheduled time actually loaded; efficiency compares achieved standard output with available productive time. Because these are managerial estimates, the result is a planning approximation, not a guaranteed output.

A simple load ratio is:

A ratio above 1 indicates a nominal overload. It does not automatically prove that delivery is impossible, because overtime, alternate work centres, subcontracting, yield improvement, or sequence changes may provide relief. Conversely, a ratio below 1 does not guarantee feasibility if material shortages, downtime, labour skills, or quality constraints are ignored.

Resolving infeasibility

Managers may respond to an overload by changing the MPS, moving orders, authorising overtime, adding shifts, using alternate equipment, subcontracting, reducing setup time, changing lot sizes, revising routings, or negotiating customer dates. Each response has cost, risk, and strategic consequences. A sound decision considers total throughput, due-date performance, inventory, labour sustainability, supplier dependence, and quality—not only the displayed load percentage.

5. From MRP to MRP II and ERP

MRP II, or manufacturing resource planning, extends material planning by integrating production planning, capacity, purchasing, shop-floor control, engineering, costing, and financial evaluation. It supports closed-loop planning: plans are tested against capacity and execution feedback, and the resulting information is used to revise future plans.

ERP extends the integration boundary further. A typical ERP architecture uses a common database or coordinated data model for finance, procurement, inventory, production, sales, distribution, maintenance, quality, projects, and human resources. A transaction such as a sales order may affect available-to-promise quantities, demand, production planning, receivables, tax, shipment planning, and revenue recognition. The value of ERP lies in process integration and shared information, not simply in installing software.

Figure: Enterprise operations planning as an integrated, feedback-based process.

ERP does not eliminate functional conflict. Sales may seek maximum responsiveness, finance may seek lower working capital, production may seek long runs, and procurement may seek supplier economies. Integrated information makes these trade-offs more visible; governance and decision rights are still required to resolve them.

6. Data, Governance, and Implementation

The most important ERP and MRP data are often called master data. They include item identifiers, units of measure, BOMs, routings, work centres, calendars, lead times, supplier records, locations, lot sizes, safety stocks, and planning parameters. Transaction data include orders, receipts, issues, completions, scrap, transfers, and inventory adjustments.

A practical data-governance system should establish:

• one accountable owner for each critical data object;
• controlled definitions and naming conventions;
• approval and effectivity procedures for engineering changes;
• cycle counting and inventory reconciliation;
• validation rules for units, quantities, and lead times;
• audit trails for changes and overrides;
• periodic measurement of data accuracy and planning performance.

Implementation should begin with process design rather than software screens. Organisations should map current and desired processes, remove unnecessary variation, define controls, cleanse data, test integration, train users, and deploy in manageable stages. A technically correct system can fail if planners do not trust it, operators bypass transactions, or managers reward local optimisation.

Useful performance measures include schedule adherence, inventory record accuracy, forecast error where forecasting is relevant, supplier on-time delivery, planned-order stability, capacity utilisation, manufacturing lead time, stockouts, expedites, and customer on-time-in-full performance. Metrics should be interpreted together. For example, high utilisation may coexist with poor delivery if bottlenecks create queues and late orders.

7. Digital Technologies and Contemporary Developments

Modern ERP and planning platforms increasingly use cloud deployment, application programming interfaces, event-driven integration, advanced planning and scheduling, internet-of-things data, digital twins, and machine learning. These technologies can improve visibility and prediction, but they do not remove the need for sound BOMs, disciplined transaction recording, or managerial judgement.

Artificial intelligence can support demand sensing, anomaly detection, lead-time estimation, inventory segmentation, predictive maintenance, and exception prioritisation. Its use requires attention to data lineage, model drift, explainability, cybersecurity, privacy, and human approval. An AI system trained on historically biased allocation decisions may reproduce those biases. Automated rescheduling can also amplify instability if it reacts to every short-term fluctuation.

Cloud ERP may improve scalability and access, but creates dependence on vendors, connectivity, service-level agreements, data-location arrangements, and cybersecurity controls. Integration with suppliers and customers should apply least-privilege access, authentication, segregation of duties, backup, recovery testing, and monitoring. In regulated industries, retention, traceability, product genealogy, and electronic approval requirements must be designed into the process.

8. Illustrative Case: Meridian Medical Devices

Background

Meridian Medical Devices assembles diagnostic instruments in three product families. It uses an ERP system, but planners report frequent shortages of electronic modules, excess safety stock, and overtime in final assembly. Customer service has begun promising dates without consulting production.

Problem

An audit finds that two engineering revisions share one item code, several supplier lead times have not been reviewed for two years, and inventory transactions are sometimes posted at the end of a shift rather than when material moves. The MPS changes daily in response to sales requests. CRP shows that the calibration work centre is overloaded by 35 percent in the next month.

Analysis

The apparent inventory problem is not simply a question of increasing stock. The shared item code causes MRP to treat incompatible revisions as interchangeable. Delayed transactions make projected balances unreliable. The unstable MPS generates repeated planned-order changes, while the calibration bottleneck prevents the final schedule from being feasible. The organisation has software integration but weak process integration.

Approach and solution

A cross-functional team first separated revision-controlled items and introduced effectivity dates in the BOM. It performed a physical cycle count for high-value and shortage-prone items, corrected units of measure, and required point-of-use transaction discipline. Procurement reviewed supplier lead times using recent performance and established review dates. Sales and operations agreed to a two-week frozen zone in the MPS, within which changes required executive approval.

CRP was then used to compare alternatives. Meridian shifted selected calibration work to a qualified partner, added a temporary second shift, and redesigned two products to use a common approved module. A daily exception meeting reviewed only material, capacity, quality, and customer-date exceptions exceeding defined thresholds.

Outcome

In this illustrative case, after three planning cycles, shortages declined, overtime became predictable, and schedule adherence improved. Total inventory did not fall immediately because the organisation retained protection during the data-stabilisation period. The important improvement was not a single parameter change; it was the alignment of engineering control, transaction accuracy, sales governance, supplier management, and capacity decisions.

Learning points

1. ERP outputs are only as reliable as master and transaction data.
2. Revision and effectivity control are operational requirements, not clerical details.
3. MPS stability can be more valuable than constant short-term responsiveness.
4. Capacity constraints must be addressed alongside material planning.
5. Cross-functional governance converts integrated information into integrated decisions.

9. Critical Evaluation and Best Practices

MRP is powerful for structured dependent demand, but it can create false precision. A requirement dated for a particular week is not necessarily achievable if supplier variability, transport disruption, machine failure, or labour absence is ignored. Conversely, purely manual planning may conceal dependencies and produce inconsistent priorities. The appropriate approach combines systematic calculation with exception-based managerial review.

Best practices include:

• maintain a controlled, revision-aware BOM and routing;
• use realistic lead times based on evidence and periodically re-estimate them;
• separate forecast, customer-order, safety-stock, and project demand appropriately;
• establish a credible MPS and a defined frozen zone;
• validate MRP results through CRP and supplier-capacity review;
• use lot-sizing policies that reflect total cost, service, shelf life, and risk;
• measure data accuracy and planning stability, not only inventory value;
• define escalation rules for shortages and overloads;
• preserve human accountability for material, capacity, quality, and customer commitments;
• treat cybersecurity, segregation of duties, privacy, and auditability as operational controls.

Chapter Summary

Materials planning translates external demand into coordinated decisions about products, components, capacity, suppliers, inventory, and cash. BOMs describe product structure and determine how dependent demand is exploded. MRP uses the MPS, BOM, and inventory records to calculate time-phased gross requirements, net requirements, planned receipts, and releases. Its logic depends on accurate data, credible lead times, appropriate lot-sizing, and disciplined transactions.

CRP tests whether planned work can be performed by available work centres, while MRP II closes the loop between manufacturing planning, capacity, execution, and finance. ERP extends the shared-data and process perspective across the enterprise. None of these systems automatically resolves strategic trade-offs or poor governance. Successful use requires master-data ownership, revision control, stable planning policies, cross-functional decision rights, cybersecurity, and continuous performance review. Digital and AI capabilities can strengthen visibility and prediction, but they must remain explainable, controlled, and subject to managerial accountability.

Key Terms

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

Dependent demand: Demand calculated from the requirements of a parent item.

Independent demand: Demand originating from external customers or markets.

Master production schedule: Time-phased schedule for producing end items or major assemblies.

Material requirements planning: Systematic calculation of time-phased material requirements and planned orders.

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

Net requirement: Requirement remaining after usable projected supply and safety stock are considered.

Planned order receipt: Quantity planned to become available in a specified period.

Planned order release: Planned start or placement date of an order.

Low-level code: Code identifying the lowest product-structure level at which an item occurs.

Lot sizing: Rule used to convert net requirements into order quantities.

Capacity requirements planning: Time-phased evaluation of work-centre loads against available capacity.

Routing: Sequence of operations and resources used to make an item.

MRP II: Manufacturing resource planning that integrates materials with capacity, manufacturing, and financial planning.

ERP: Enterprise resource planning system integrating major organisational processes and data.

Master data: Relatively stable data such as items, BOMs, routings, suppliers, and work centres.

Effectivity: Conditions, such as dates or revisions, defining when a product-structure relationship applies.

Frozen zone: Near-term planning interval in which schedule changes are restricted.

Review Questions

Short Answer Questions

1. Distinguish independent demand from dependent demand and give one example of each.
2. What are the principal inputs to an MRP system?
3. Explain the difference between a planned order receipt and a planned order release.
4. Why is a low-level code useful in BOM explosion?
5. State two reasons why an ERP implementation may fail despite technically functional software.

Long Answer Questions

1. Explain the relationship among S&OP, MPS, MRP, CRP, MRP II, and ERP. Discuss how feedback moves between the levels.
2. Describe the structure of an MRP record and explain how projected available balance and net requirements are calculated.
3. Evaluate the assumptions and limitations of conventional MRP in an environment of uncertain supply and variable capacity.
4. Discuss how master-data governance, engineering-change control, and transaction discipline affect planning performance.
5. Compare alternative responses to a CRP-identified overload, including overtime, subcontracting, rescheduling, and process improvement.

Analytical / Application Questions

1. An item has a gross requirement of 500 units, projected beginning balance of 120 units, scheduled receipt of 80 units, and safety stock of 50 units. Calculate the net requirement under the assumptions used in this chapter. Explain how a fixed carton size of 100 would change the planned receipt.
2. A work centre has 3 machines, 40 scheduled hours per machine, utilisation of 85 percent, and efficiency of 90 percent. Calculate approximate available capacity and explain why this figure should not be interpreted as a guaranteed output.
3. Design a cross-functional action plan for a firm experiencing frequent MRP rescheduling, inaccurate inventory records, supplier lateness, and a bottleneck work centre. Justify the sequence of your actions.

Multiple Choice Questions with Answers

Question 1

Which input is essential for basic material requirements planning?

A. Bill of materials

B. Employee performance appraisal

C. Corporate tax return

D. Advertising expenditure

Correct Answer: A. Bill of materials

Question 2

A product requires 2 units of A, and each A requires 3 units of B. How many B units are required per finished product?

A. 2

B. 3

C. 5

D. 6

Correct Answer: D. 6

Question 3

A component has gross requirement 200, projected beginning balance 60, scheduled receipt 50, and safety stock 20. What is its net requirement?

A. 70

B. 90

C. 110

D. 130

Correct Answer: C. 110

Question 4

A planned order release differs from a planned order receipt primarily because of:

A. Safety stock

B. Lead-time offset

C. Product price

D. Forecast error

Correct Answer: B. Lead-time offset

Question 5

Which system most directly tests planned work-centre loads against available capacity?

A. CRP

B. CRM

C. Payroll

D. Point-of-sale reporting

Correct Answer: A. CRP

Question 6

Which statement best describes dependent demand?

A. It is always random

B. It is derived from demand for a parent item

C. It can never be calculated

D. It applies only to services

Correct Answer: B. It is derived from demand for a parent item

Question 7

MRP II extends MRP mainly by integrating materials planning with:

A. Only product advertising

B. Manufacturing resources, capacity, and financial planning

C. Only customer complaints

D. Only external financial markets

Correct Answer: B. Manufacturing resources, capacity, and financial planning

Question 8

Which is an example of master data?

A. A single receipt posted today

B. A one-time inventory adjustment

C. A controlled bill of materials

D. A temporary customer email

Correct Answer: C. A controlled bill of materials

Question 9

Available capacity is estimated as N × H × U × E. If N = 3, H = 40 hours, U = 0.85, and E = 0.90, what is the result?

A. 91.8 hours

B. 102.0 hours

C. 108.0 hours

D. 120.0 hours

Correct Answer: A. 91.8 hours

Question 10

Which practice best reduces ERP planning instability?

A. Allow every user to change BOMs freely

B. Ignore transaction timing

C. Use revision control and a defined MPS frozen zone

D. Increase all safety stocks without analysis

Correct Answer: C. Use revision control and a defined MPS frozen zone