Materials Requirements Planning Systems

In the world of manufacturing, few challenges are as costly or disruptive as running out of a critical component on the assembly line. Conversely, tying up capital in excessive inventory can cripple a company's financial health. Materials Requirements Planning (MRP) is the foundational, computer-based logic that solves this dilemma. It is a systematic approach for calculating exactly what materials are needed, in what quantities, and at what time, to fulfill a production plan. By transforming a sales forecast into a precise material procurement and production schedule, MRP systems coordinate the complex dance of dependent demand, ensuring components arrive just as they are needed for assembly.

The Core Inputs: The Foundation of MRP Logic

An MRP system is only as good as the data fed into it. Three master files form the essential input triad, and their accuracy is non-negotiable for the system to function correctly.

First, the Master Production Schedule (MPS) is the primary driver. It states which end items are to be produced, in what quantities, and by when. Think of it as the company's formal game plan for production, derived from firm customer orders and sales forecasts. The MPS is a statement of independent demand—demand for a finished product that comes from outside the factory.

Second, the Bill of Materials (BOM) is the recipe for each product listed in the MPS. It is a hierarchical listing of all raw materials, components, subassemblies, and assemblies required to make one unit of a parent item. A BOM is structured in levels, with the finished product at level 0. For a simple table, level 0 is the table itself; level 1 might include the tabletop and four legs; level 2 for a leg might include wood, glue, and a bolt. The BOM defines the parent-component relationships and specifies the quantity of each component needed per parent.

Third, Inventory Records provide the current state of material availability. This file contains precise, real-time data for every item in the BOM: the number of units on hand (physical inventory), the number already allocated to other work orders (allocated inventory), and the number on order from suppliers (scheduled receipts). This data is used to calculate the net requirement, which is the actual amount that must be purchased or produced.

The MRP Processing Engine: Netting, Offsetting, and Exploding

With the three inputs loaded, the MRP software executes a rigorous, time-phased calculation often referred to as the "MRP explosion." This process happens in a specific, logical sequence.

Step 1: Netting. For each item in the BOM, starting with the top-level MPS items, the system calculates the net requirement. The formula is straightforward: Net Requirements = Gross Requirements (from the parent's plan) - (Inventory On Hand + Scheduled Receipts). This step answers the question, "After accounting for what we already have and what's already coming in, what do we still need?"

Step 2: Offsetting for Lead Time. Materials and components cannot be conjured instantly. Lead time is the span between placing an order (either with a supplier or an internal work center) and receiving the items. Offsetting involves planning backwards from the date the material is needed (the requirement date) to determine when the order must be released. If a leg assembly is needed on June 10th and has a 2-day lead time, the order to make or buy it must be released on June 8th.

Step 3: Exploding and Gross-to-Net Calculation. This is where the system works through the BOM hierarchy. The planned order releases for a parent item (e.g., a table) become the gross requirements for its components (tabletop, legs). The system then performs the netting and offsetting calculations for those components, using their BOMs and inventory records. This process "explodes" down through every level of the BOM, generating time-phased requirements for every single part, from finished goods down to raw bolts and glue.

The final output is a set of planned order releases—detailed instructions saying what to make or buy, in what quantity, and when to release the order to meet the MPS. These are not yet firm orders; they are dynamic recommendations that are recalculated (usually daily or weekly) as new orders come in, inventory changes, or delays occur.

Outputs and the Closed-Loop MRP System

The primary outputs of an MRP run are the planned orders for production and purchase. However, a sophisticated system generates several other critical reports that enable proactive management. Exception reports highlight problems like overdue scheduled receipts, items with requirements in the past (past due), or items where capacity is insufficient. Performance reports track metrics like schedule adherence and inventory accuracy. Planning reports allow managers to simulate "what-if" scenarios, such as the impact of a delayed supplier shipment or a new large customer order.

This feedback mechanism is what creates a closed-loop MRP system. In a closed-loop system, the outputs (particularly exception reports) are used to revise the inputs. If a planned order cannot be executed due to a machine breakdown (a capacity issue), the information feeds back to adjust the MPS. This loop between planning, execution, and feedback is crucial for maintaining a realistic and achievable plan, transforming MRP from a simple calculator into a dynamic management tool.

From MRP to MRP II and ERP: The Evolution of Integration

Standalone MRP has a critical limitation: it assumes infinite capacity. It brilliantly plans material needs but ignores whether the factory's machines and labor have the time to do the work. This led to the development of Manufacturing Resource Planning (MRP II). MRP II integrates capacity planning with material planning. After the MRP system generates planned orders, the MRP II system checks the required work centers against available capacity (manpower and machines). If a capacity shortfall is identified, the plan must be adjusted—either by modifying the MPS, adding overtime, or subcontracting work. MRP II creates a more feasible, synchronized plan for all manufacturing resources.

MRP and MRP II form the operational core of modern Enterprise Resource Planning (ERP) systems. An ERP system integrates MRP II's manufacturing logic with all other business functions—finance, human resources, sales, and customer relationship management—into a single, unified database. When a sales order is entered in an ERP system, it can immediately trigger updates to the MPS, MRP calculations, capacity plans, and financial forecasts. This seamless integration is why MRP is considered the foundational engine for manufacturing within today's comprehensive business software platforms.

Common Pitfalls

1. Garbage In, Garbage Out (GIGO). The most common and catastrophic failure of an MRP implementation is inaccurate data. If inventory records are wrong, the net requirements will be wrong. If BOMs are outdated, the system will plan for the wrong components. If lead times in the system are guesses rather than measured averages, orders will be released too early or too late. Rigorous data discipline is the first requirement for MRP success.

2. Treating the MRP Plan as Static. An MRP plan is a snapshot based on the data at the time of the run. The real world is dynamic. Failing to regularly regenerate the plan (re-planning) in response to new customer orders, inventory counts, or supplier delays quickly renders the plan obsolete. Companies must establish a firm schedule for net-change or regenerative replanning to keep the system relevant.

3. Ignoring Capacity Constraints. Using basic MRP without regard for capacity is a recipe for an unexecutable plan. A shop floor may be flooded with planned orders it physically cannot complete on time, leading to widespread delays and missed schedules. Implementing closed-loop feedback or advancing to an MRP II system that performs Capacity Requirements Planning (CRP) is essential for creating a realistic production schedule.

4. Over-reliance on the System without Human Oversight. MRP is a powerful tool for calculation, but it is not an artificial intelligence. It cannot account for qualitative factors like a supplier's reliability, an upcoming labor strike, or a salesperson's promise to a key client. Planners must use the system's exception and planning reports to apply judgment, make adjustments, and manage the exceptions that inevitably arise.

Summary

• Materials Requirements Planning (MRP) is a time-phased, priority-planning technique that uses a Master Production Schedule (MPS), Bill of Materials (BOM), and Inventory Records to calculate net material requirements and generate planned purchase and production orders.
• The core MRP logic involves netting requirements against current inventory, offsetting for lead times, and exploding demands down through all levels of the product structure.
• Effective MRP requires a closed-loop system where execution feedback is used to continuously adjust plans, ensuring they remain realistic and achievable.
• MRP evolves into Manufacturing Resource Planning (MRP II) by integrating capacity planning, and ultimately serves as the operational foundation for comprehensive Enterprise Resource Planning (ERP) systems.
• Success depends entirely on data accuracy, regular system regeneration, consideration of capacity limits, and the informed judgment of human planners to manage exceptions.