Closed-Loop MRP, MRP II and ERP Integration

Introduction and context

Material Requirements Planning (MRP) began as a method for translating a production schedule into time-phased requirements for components and raw materials. Its central contribution was to replace informal expediting and purely order-point practices with a logically coordinated plan based on the master production schedule, bills of material, inventory records and lead times. However, materials decisions do not occur in isolation. A feasible material plan depends on machine capacity, labour, supplier capability, cash availability, quality performance, maintenance schedules, warehouse operations and customer commitments.

This broader systems perspective led to closed-loop MRP, Manufacturing Resource Planning (MRP II), and ultimately Enterprise Resource Planning (ERP). These developments should not be understood simply as successive software products. They represent expanding managerial boundaries: from material availability, to production feasibility, to enterprise-wide coordination and, increasingly, inter-organisational and product-lifecycle integration.

For a production manager, the strategic question is not whether an organisation should install the newest system. It is whether the organisation can create reliable data, disciplined processes, effective decision rights and feedback mechanisms that convert plans into controlled operational action.

Learning objectives

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

1. Distinguish MRP, closed-loop MRP, MRP II and ERP.
2. Explain how planning feedback connects production, capacity, procurement and execution.
3. Integrate materials planning with finance, quality, maintenance, warehousing, logistics and product lifecycle management.
4. Evaluate implementation risks, governance requirements and performance measures.
5. Apply an integrated planning approach to a realistic manufacturing situation.

1. From material planning to enterprise coordination

1.1 The logic of basic MRP

Basic MRP converts independent demand for finished products into dependent demand for components. The principal inputs are:

• the master production schedule (MPS), which states what finished products are required and when;
• the bill of material (BOM), which identifies component relationships and quantities;
• inventory and transaction records, including on-hand balances, scheduled receipts and open orders; and
• planning parameters such as lead times, lot-sizing rules, safety stocks and order policies.

For a component, the projected available balance in a period can be represented as:

where PAB_t is projected available balance in period t, SR_t is scheduled receipt, POR_t is planned order receipt, and GR_t is gross requirement. All terms must use the same quantity unit and period. The expression assumes that inventory records are accurate and that receipts and requirements occur according to the period convention used by the planning system.

Net requirements are commonly calculated as:

where NR_t is net requirement and SS_t is desired safety stock. This formulation is applicable when safety stock is treated as a minimum ending balance and when projected available inventory before planned receipt is the relevant supply position. Different systems may use alternative safety-stock and allocation conventions.

A planned order receipt is then generated according to the selected lot-sizing rule. If the lot-for-lot rule is used, the planned receipt equals the net requirement. The planned order release is offset by the planned lead time:

where PORel is planned order release, PORec is planned order receipt, and L is the lead time measured in planning periods. This assumes a deterministic lead time and no additional release, inspection or transportation delay.

Basic MRP is powerful but incomplete. It may produce a mathematically valid material plan that cannot be manufactured because required work-centre hours exceed available capacity. It may also create purchasing actions that conflict with cash constraints, supplier capacity or quality requirements.

1.2 Closed-loop MRP

Closed-loop MRP adds feedback from execution and capacity planning to the material plan. The term “closed-loop” refers to the repeated cycle of planning, authorisation, execution, measurement and replanning. Its major elements include:

• rough-cut capacity planning for the MPS;
• detailed capacity requirements planning (CRP) for work centres;
• shop-floor control and dispatching;
• purchasing and supplier follow-up;
• inventory and order-status feedback; and
• corrective replanning when actual performance differs from assumptions.

The loop is not merely a technical data cycle. It is a management-control cycle. A planner may release an order only after confirming that materials, capacity, tooling, labour and priorities are sufficiently aligned. Actual completions, scrap, delays and receipts are then fed back into the next planning run.

Closed-loop MRP therefore addresses a fundamental weakness of open-loop planning: the assumption that plans automatically become reality. It recognises that lead times vary, machines fail, suppliers miss dates and production yields are imperfect.

1.3 Manufacturing Resource Planning (MRP II)

MRP II extends closed-loop MRP by integrating a wider range of manufacturing resources and financial consequences. Typical MRP II modules include:

• business and sales planning;
• production planning and the MPS;
• MRP and CRP;
• shop-floor control;
• purchasing and supplier management;
• inventory control;
• cost accounting and financial planning; and
• performance measurement.

A key feature is the use of common plans at different levels. The business plan expresses aggregate demand and financial direction. Sales and operations planning (S&OP) reconciles demand, supply and inventory at an aggregate level. The MPS translates that agreement into end-item schedules, and MRP translates the MPS into component requirements.

MRP II is broader than MRP but remains primarily manufacturing-centred. It attempts to answer two linked questions: “Can the factory produce the required output?” and “What are the operational and financial consequences of that plan?”

1.4 ERP

ERP integrates core processes across the enterprise using a common database, shared master data and connected transaction flows. In addition to manufacturing, ERP commonly includes finance, sales, distribution, procurement, inventory, human resources, maintenance, quality and project management. Modern ERP platforms may also connect with supply-chain planning, customer relationship management, product lifecycle management, warehouse management and manufacturing execution systems.

ERP does not eliminate MRP or MRP II. Rather, MRP is usually a planning function within an ERP environment, while MRP II describes an integrated manufacturing-management philosophy. ERP expands the scope from manufacturing resources to enterprise transactions and cross-functional governance.

2. Comparative framework

The boundaries are conceptual rather than absolute. Commercial systems may use different labels, and many modern ERP packages contain functions that historically belonged to MRP II.

3. The integrated planning architecture

An integrated planning environment operates through linked planning horizons.

Strategic and aggregate horizon

The business plan establishes broad objectives for markets, capacity, profitability and investment. S&OP reconciles the demand forecast with supply capability, workforce, inventory and financial targets. Decisions at this level are normally expressed in product families rather than individual stock-keeping units.

Tactical horizon

The MPS converts aggregate decisions into specific finished products and due dates. It must be checked against rough-cut capacity, critical materials and customer priorities. A stable MPS is particularly important because frequent changes create nervousness throughout the BOM.

Operational horizon

MRP calculates component requirements, planned receipts and release dates. CRP translates planned and released orders into work-centre loads. Purchasing, warehouse operations and shop-floor control execute the plan, while actual transactions update the system.

Execution and feedback

A closed-loop system compares planned and actual quantities, dates, yields, labour hours, machine availability and supplier performance. Deviations trigger exception management rather than automatic replanning of every order. The objective is controlled responsiveness, not perpetual system-induced change.

4. Functional integration beyond materials

4.1 Procurement and supplier management

MRP generates planned purchase requisitions or purchase orders, but procurement must validate supplier lead times, minimum order quantities, price breaks, contractual terms, capacity commitments and quality status. Supplier schedules should distinguish firm releases from forecast information. Electronic supplier collaboration can provide acknowledgements, advance shipping notices and exception alerts.

A major governance issue is the separation of duties. The person who creates a material requirement should not necessarily be able to approve a supplier or release payment. ERP workflow can enforce approval limits, supplier qualification and three-way matching among purchase order, goods receipt and invoice.

4.2 Finance and controlling

Every material movement has a financial consequence. A purchase receipt affects inventory valuation and liabilities; a production issue affects work-in-process; a sale affects revenue and receivables. Integrated costing links the operational plan with budgets, standard costs, variance analysis and cash requirements.

A simple inventory-accounting relationship is:

The equation is an accounting identity, not a physical-flow equation. Monetary values must use a consistent valuation method, such as standard, moving-average or an approved actual-cost method. Physical quantities and financial values should not be mixed without an appropriate unit-cost conversion.

MRP II and ERP allow alternative production plans to be evaluated for material cost, labour, overhead, inventory investment and expected margin. However, system-generated costs remain dependent on the quality of bills of material, routings, labour rates and costing rules.

4.3 Quality management

Quality integration includes inspection plans, supplier quality status, nonconformance records, corrective actions, certificates of analysis, statistical process information and traceability. A component placed on quality hold should not be treated as unrestricted available inventory merely because it is physically present.

Quality data can also improve planning. Persistent scrap or rework changes effective material requirements and capacity consumption. For a process with a constant yield rate y, the input required for a desired good output Q is:

Here y is expressed as a decimal between 0 and 1. The relationship assumes a single-stage process and a stable yield. Multiple-stage processes require multiplication of stage yields, and rework loops require a more detailed model.

4.4 Maintenance and asset management

Maintenance integration is essential when machine availability constrains capacity. Preventive-maintenance work orders consume labour, tools and machine time; breakdowns reduce available capacity and may alter planned completion dates. ERP maintenance modules can connect asset histories, spare-parts inventories, failure reports, permits and maintenance schedules.

Production and maintenance should not compete through disconnected schedules. A planned shutdown may be the best time to perform maintenance, while a short-term production emergency may justify a controlled rescheduling decision. The decision should consider safety, regulatory requirements, asset criticality and total cost rather than output alone.

4.5 Warehousing and logistics

MRP plans requirements; warehouse management controls physical location, handling, picking, replenishment, lot and serial tracking, and inventory accuracy. Logistics systems manage transportation, shipment consolidation, route planning, customs information and delivery confirmation.

Integration is particularly important for components with shelf-life, hazardous characteristics or serial-number traceability. Goods-receipt transactions should update available, inspection and blocked stocks according to defined status rules. Barcode, RFID and mobile transactions can improve timeliness, but technology cannot compensate for poorly designed counting and authorisation processes.

4.6 Product lifecycle management

Product Lifecycle Management (PLM) manages product structures, drawings, specifications, revisions, engineering changes and technical approvals. ERP manages the commercial and operational consequences of those structures. The engineering BOM, manufacturing BOM and service BOM may serve different purposes and must be governed through controlled mappings.

An engineering change should not be treated as complete merely because a new drawing has been approved. Effective-date controls, obsolete inventory disposition, supplier communication, work-instruction updates, tooling changes and customer/regulatory approvals may all be required. A controlled change process prevents a planner from procuring a component that production can no longer use.

5. Planning integrity and master-data governance

Integration increases the consequences of bad data. Important master-data objects include item numbers, units of measure, BOM quantities, scrap factors, routings, work centres, lead times, lot sizes, safety stocks, supplier records, locations, revision levels and accounting classifications.

A practical data-governance framework assigns:

• an owner responsible for the meaning and quality of each data object;
• a steward responsible for maintenance and validation;
• an approval authority for changes; and
• an audit trail showing who changed what, when and why.

Common data defects include duplicate items, inconsistent units, phantom BOMs that are not properly maintained, unrealistic lead times, inactive suppliers that remain selectable, and transactions posted after the physical event. These defects create false precision: the system produces exact dates and quantities that appear authoritative but are operationally unreliable.

Planning parameters should be periodically reviewed using actual performance. For example, if supplier lead time is variable, a single deterministic lead time may systematically understate risk. Safety stock can be estimated using statistical policies, but the selected method must reflect demand variability, lead-time variability, service objectives and the independence or correlation of those sources. There is no universally correct safety-stock number.

6. Worked application: capacity feedback in closed-loop MRP

Consider an illustrative manufacturer that must deliver 100 finished units in week 6. Each finished unit requires two units of component A. On-hand component A is 60 units, and 10 units are already scheduled to arrive in week 5. No safety stock is required.

Gross requirement in week 6 is:

Projected supply before a new planned receipt is 70 units. Therefore:

Assume a two-week purchasing lead time. The planned order release is therefore in week 4 for a week-6 receipt, subject to supplier calendars and receiving rules.

The material plan alone is insufficient. The routing requires 0.5 machine-hours per finished unit at a work centre with 45 available hours in week 6. Required load is:

The capacity shortfall is 5 hours. A closed-loop response could involve overtime, an alternate work centre, subcontracting, an earlier production date, or a revised MPS. If the organisation simply releases the 130-unit purchase order without resolving capacity, it may create excess component inventory and still miss the customer due date.

Suppose management authorises 5 hours of overtime. The material plan remains feasible, but the overtime cost must be reflected in the production cost estimate. If overtime is not available, the MPS may be reduced to 90 units in week 6 and 10 units moved to week 7. That change reduces week-6 component demand by 20 units, but it may create a customer-service issue and must be communicated across sales, logistics and finance.

The example illustrates the closed loop: MRP identifies material need; CRP identifies capacity conflict; management selects a corrective action; the revised decision updates procurement, production, costing and customer commitments.

7. Implementation and operating model

Process design before software configuration

An organisation should document current and desired processes before configuring an ERP. Questions include: Who owns the MPS? What constitutes a firm order? How are emergency changes approved? Which inventory statuses are available? When does a purchase requisition become a binding supplier commitment? How are obsolete materials handled?

Phased deployment and testing

A phased approach may reduce risk, although excessive fragmentation can create temporary interfaces and duplicated data. Testing should include unit testing, integration testing, volume testing, security testing, user acceptance testing and realistic end-to-end scenarios. A complete scenario may run from customer demand through MPS, MRP, purchase order, receipt, inspection, issue to production, finished-goods receipt, shipment, invoice and accounting entry.

Change management and competence

ERP implementation changes roles. Planners may spend less time manually expediting and more time managing exceptions. Buyers may need to interpret system signals rather than relying on informal supplier relationships. Supervisors must record production, scrap and downtime accurately. Training should therefore explain process logic and consequences, not just screen navigation.

Performance management

Useful measures include schedule adherence, plan stability, inventory accuracy, supplier on-time delivery, purchase-price variance, inventory turns, stockout frequency, capacity utilisation, overall equipment effectiveness, first-pass yield, order-cycle time and cash-to-cash performance. Measures must be balanced. Maximising machine utilisation, for example, can increase inventory and reduce responsiveness if it encourages large batches and poor flow.

8. Challenges, limitations and critical evaluation

Data and behavioural limitations

ERP integration does not guarantee truth. Transaction discipline, master-data maintenance and cross-functional cooperation remain essential. Employees may bypass the system if it is slow, difficult or inconsistent with actual work.

Planning nervousness

Frequent changes in forecasts or priorities can cascade through the BOM. Time fences, order policies, exception thresholds and management approval for schedule changes can reduce unnecessary nervousness. Nevertheless, excessive rigidity can make the system unable to respond to genuine market changes.

Centralisation versus local responsiveness

An enterprise-wide system promotes standardisation and visibility, but plants may have legitimate differences in products, regulations, process technologies and labour arrangements. A sound design standardises common principles while allowing controlled local variation.

Technology and AI

Modern systems use cloud platforms, application programming interfaces, digital twins, advanced planning, machine learning and event-driven alerts. AI may help forecast demand, identify anomalous transactions, predict equipment failure or recommend rescheduling. It should be treated as decision support rather than an unquestionable authority. Models can amplify biased historical data, conceal uncertainty and recommend actions that violate capacity, safety or contractual constraints.

Human review is particularly important for high-impact decisions such as supplier termination, allocation of scarce medical or safety-critical components, workforce reduction and release of regulated products. AI governance should address data provenance, explainability, access control, validation, cybersecurity and accountability.

Cybersecurity and continuity

Integrated systems create concentrated operational risk. A cyberattack, data corruption event or cloud outage can disrupt procurement, production and shipment simultaneously. Organisations need role-based access, segregation of duties, multifactor authentication, backups, recovery objectives, incident-response procedures and tested manual-continuity processes.

9. Strategic best practices

1. Establish a cross-functional governance structure linking operations, finance, procurement, quality, maintenance, IT and product engineering.
2. Define one authoritative source for each critical master-data object.
3. Stabilise S&OP and MPS processes before seeking highly detailed optimisation.
4. Use closed-loop feedback and exception management rather than relying on static plans.
5. Integrate quality and maintenance status into available-capacity and available-inventory logic.
6. Link engineering changes to effective dates, inventory disposition and manufacturing readiness.
7. Measure total system performance, including service, cash, quality, flexibility and risk.
8. Treat implementation as organisational redesign, not merely software installation.
9. Validate AI recommendations against business rules, safety requirements and human accountability.
10. Review planning parameters using actual performance and changing strategic conditions.

Illustrative case: Orion Medical Devices

Background

Orion Medical Devices, a fictional mid-sized manufacturer, produces diagnostic instruments with purchased electronic boards, machined housings and regulated disposable cartridges. It operated a basic MRP package while finance, maintenance, quality and warehouse records were maintained in separate applications.

Problem

The company experienced frequent shortages of approved electronic boards, excess obsolete components after engineering changes, unreliable promised dates and unexplained inventory differences. Production supervisors often used spreadsheets because the formal system did not show machine downtime or quality holds.

Analysis

An investigation found that the BOM used by production was not synchronised with engineering revisions. Components under inspection were counted as available by MRP. Supplier lead times had not been updated for three years. Maintenance shutdowns were absent from capacity calendars, and purchase orders were sometimes received without timely inspection-status transactions. Finance consequently reported inventory values that did not agree with physical and quality-controlled quantities.

Approach and solution

Orion introduced an integrated governance board and assigned owners for item masters, BOMs, routings, supplier records and inventory statuses. PLM became the authority for engineering revisions, while approved manufacturing BOMs were transferred to ERP through a controlled change process. Quality status was made visible to MRP, and warehouse scanning was introduced at receipt, movement and issue.

The company also connected maintenance work orders to work-centre calendars and created an S&OP process involving sales, operations, procurement and finance. A two-stage planning policy was adopted: aggregate decisions were reviewed monthly, while the near-term MPS was frozen within a defined time fence except for authorised exceptions. Suppliers received firm releases and forecast visibility through a portal.

Outcome

Within two planning cycles, planners reported fewer false shortages and fewer emergency purchase orders. Inventory accuracy improved because physical and system transactions occurred at the point of movement. The company also reduced engineering-change disruption by identifying obsolete stock before releasing new purchase orders. The most important improvement was not a particular software module; it was the agreement on process ownership, data definitions and escalation rules.

Learning points

The case demonstrates that integration is organisational as well as technological. MRP cannot plan correctly when quality status, engineering revision, supplier capability and maintenance availability are invisible. ERP creates the possibility of integration, but disciplined governance and timely transactions create the business value.

Chapter Summary

Basic MRP translates the MPS, BOM and inventory records into time-phased material plans. Closed-loop MRP adds capacity planning, shop-floor control, purchasing feedback and corrective replanning. MRP II extends this logic across manufacturing resources and links operational plans with financial consequences. ERP broadens integration to enterprise processes, including finance, procurement, quality, maintenance, warehousing, logistics and product lifecycle management.

The strategic value of these systems depends on coherent planning horizons, accurate master data, controlled engineering changes, timely execution feedback and cross-functional governance. Integration can improve visibility and coordination, but it also increases the consequences of inaccurate data, weak controls and cybersecurity failures. AI and advanced analytics can support forecasting, maintenance and exception management, but responsible human oversight remains essential.

Key Terms

MRP: A system for calculating time-phased dependent material requirements.

Closed-loop MRP: MRP linked with capacity planning, execution feedback and corrective replanning.

MRP II: Manufacturing Resource Planning, integrating manufacturing, capacity, purchasing and financial planning.

ERP: Enterprise Resource Planning, integrating major organisational processes through shared data and transactions.

Master Production Schedule: A time-phased plan for producing specified finished products.

Bill of Material: A structured record of components and quantities required for a product.

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

Capacity Requirements Planning: Detailed assessment of work-centre capacity against planned and released orders.

Sales and Operations Planning: Cross-functional process that reconciles aggregate demand, supply and financial objectives.

Projected Available Balance: Expected inventory position after considering requirements and receipts.

Planned Order Release: Recommended date on which an order should be launched to meet a planned receipt date.

Master data: Relatively stable data defining items, BOMs, routings, suppliers, locations and planning parameters.

Product Lifecycle Management: Governance of product definitions, revisions, specifications and engineering changes.

Quality hold: Inventory status preventing unrestricted use until inspection or disposition is complete.

Engineering change: Authorised alteration to a product, process, specification or technical document.

Exception management: Focusing managerial attention on significant deviations from plan.

Time fence: A defined planning interval within which changes are restricted or require approval.

Segregation of duties: Control principle separating incompatible responsibilities to reduce error and fraud.

Review Questions

Short Answer Questions

1. What is the principal difference between basic MRP and closed-loop MRP?
2. Why is MRP II broader than closed-loop MRP?
3. How can a quality hold affect material planning?
4. What role does PLM play in ERP integration?
5. State two risks associated with poor master-data governance.

Long Answer Questions

1. Compare MRP, closed-loop MRP, MRP II and ERP in terms of scope, inputs, outputs and managerial purpose.
2. Explain how S&OP, the MPS, MRP and CRP form a hierarchy of integrated planning.
3. Discuss the integration of materials planning with procurement, finance, quality and maintenance.
4. Evaluate the advantages and limitations of enterprise-wide standardisation in ERP implementation.
5. Develop a governance framework for controlling engineering changes in an integrated manufacturing system.

Analytical / Application Questions

1. A plant requires 240 component units in week 8. It has 70 units available and 30 scheduled to arrive in week 7. There is no safety stock. Calculate the net requirement and explain how a two-week lead time affects the planned release date.
2. A production schedule requires 150 hours at a work centre, but only 132 hours are available after preventive maintenance. Identify three possible closed-loop responses and discuss their operational and financial consequences.
3. Design an integration plan for a manufacturer whose ERP shows inventory receipts but does not distinguish unrestricted, inspection and rejected stock. Identify the data, process, control and performance changes required.

Multiple Choice Questions with Answers

Question 1

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

A. Use of a bill of material

B. Feedback from capacity and execution to planning

C. Calculation of dependent demand

D. Time-phased inventory records

Correct Answer: B. Feedback from capacity and execution to planning

Question 2

MRP II primarily extends MRP by integrating materials planning with:

A. Only customer relationship management

B. Manufacturing resources and financial planning

C. Only product design drawings

D. Only transportation routing

Correct Answer: B. Manufacturing resources and financial planning

Question 3

In the projected balance equation, which item increases projected available balance?

A. Gross requirement

B. Scrap consumption

C. Scheduled receipt

D. Component issue

Correct Answer: C. Scheduled receipt

Question 4

A finished product requires two units of a component. For 100 finished units, with 60 units on hand and 10 scheduled to arrive, what is the net requirement when safety stock is zero?

A. 70 units

B. 120 units

C. 130 units

D. 200 units

Correct Answer: C. 130 units

Question 5

What is the principal purpose of Capacity Requirements Planning?

A. To approve supplier invoices

B. To compare work-centre load with available capacity

C. To define engineering revisions

D. To calculate customer profitability only

Correct Answer: B. To compare work-centre load with available capacity

Question 6

Which system should generally govern engineering drawings and product revisions?

A. Product Lifecycle Management system

B. Payroll system

C. Transport management system

D. Accounts receivable system

Correct Answer: A. Product Lifecycle Management system

Question 7

Why should inventory under quality inspection not automatically be treated as unrestricted available stock?

A. It has no monetary value

B. It may not yet be approved for production use

C. It cannot be physically counted

D. It is always obsolete

Correct Answer: B. It may not yet be approved for production use

Question 8

Which practice best supports ERP data governance?

A. Allowing every user to change master data freely

B. Assigning ownership, stewardship and approval authority

C. Maintaining separate item numbers in every department

D. Avoiding audit trails to speed transactions

Correct Answer: B. Assigning ownership, stewardship and approval authority

Question 9

A work centre requires 0.5 machine-hours per unit and a schedule contains 100 units. What is the required load?

A. 50 machine-hours

B. 100 machine-hours

C. 150 machine-hours

D. 200 machine-hours

Correct Answer: A. 50 machine-hours

Question 10

Which statement about AI in integrated planning is most appropriate?

A. AI recommendations never require human review

B. AI can support decisions but must be checked against constraints and governance requirements

C. AI removes the need for accurate master data

D. AI makes cybersecurity controls unnecessary

Correct Answer: B. AI can support decisions but must be checked against constraints and governance requirements