Material Requirements Planning (MRP) : Developed in 1970s, Raw Material Whenever
Material Requirements Planning (MRP) : Developed in 1970s, Raw Material Whenever
Material Requirements Planning (MRP) : Developed in 1970s, Raw Material Whenever
A set of techniques that uses bill of material data, inventory data, and the Master
Production Schedule (MPS) to calculate requirements for materials. It makes
recommendations to release replenishment orders for material. Further, because
it is time phased, it makes recommendations to reschedule open orders when
due dates and need dates are not in phase. Time-phased MRP begins with the
items listed on the MPS and determines (1) the quantity of all components and
materials required to fabricate those items and (2) the date that the components
and material are required. Time-phased MRP is accomplished by exploding the
bill of material, adjusting for inventory quantities on hand or on order, and off-
setting the net requirements by the appropriate lead times.
Simply put, MRP tells us how much of each item to order (purchase order)
and produce (work order) to meet our delivery dates. MRP also alerts the
planner when there is a problem needing attention.
How MRP Works
The MRP calculation begins with demand for finished parts, and time phases
these requirements into periods—usually days or weeks—by the due date of
each order. These are called the gross requirements for the parent items. MRP
then nets out (deducts from the gross requirement) finished parts in stock or
already scheduled for production within the appropriate time periods. The
resulting net requirements for finished parts in each time period are then
exploded down to the first level of components on the BOM, and MRP
then calculates time-phased requirements for each component at that level. It
then nets out components already in stock, on open purchase or production
orders, resulting in component net requirements at that level of the BOM for
each period. MRP continues down the BOM for all subsequent levels, per-
forming the same gross to net calculation at each level.
When it reaches the bottom level of the BOM for this part, the MRP cal-
culation proceeds to the next parent item and repeats the entire process. When
MRP is done with all the parts at all BOM levels, it totals all net requirements
for purchase and production and then time phases each part requirement
based on the standard purchase or production lead time value stored in each
item file. This means that if a particular part has a standard 10-day lead time,
the purchase or production order is issued 10 days ahead of when it is needed.
MRP then suggests the appropriate actions to the planner, who may turn these
suggestions into actual purchase orders that are sent to suppliers with expected
receipt dates and production work orders that are released to the shop floor
at the appropriate time to meet order delivery dates.
The APICS Dictionary describes several types of orders used by the MRP
engine:
• Open Orders—A released production or purchase order. Using the stan-
The three key questions that you must ask when planning for dependent demand are:
In determining how much material your product needs, MRP differs from consumption-
based planning (CBP). MRP logic uses information received either directly from
customers or from the sales forecast, calculating the material required based on the
dependencies of other materials. CBP calculates material requirements only via
historical consumption data. CBP does not consider the dependencies between
different materials, as it presumes that future consumption will follow the same pattern
that the historical data did.
MRP synchronizes the flow of materials, components, and parts in a phased order
system, considering the production schedule. It also combines and tracks hundreds of
variables, including:
Purchase orders
Sales orders
Shortage of materials
Expedited orders
Due dates
Forecasts
Marketplace demand
Material
Inventory
Data
Bill of material
For all companies, MRP has a few goals in common. These include making sure that
the inventory level is at a minimum, but high enough to provide for the customer need,
and that you plan all of the activities, including delivery, purchasing, and manufacturing.
There are some terms that will come up in MRP repeatedly. Some are terms related to
MRP as a concept, and some are specific to MRP software. These terms are as follows:
Item: In MRP, an item is the name or code number used for the event you’re
scheduling.
Low-Level Code: This is the lowest level code of an item in the bill of materials
and indicates the sequence in which you run items through an MRP. You use
low-level code because an MRP system recognizes and connects the level that
an item appears in the product chain and uses it to plan the proper time to meet
all of the system demands.
Lot Size: This is the quantity of units you order during manufacturing
Lead Time (LT): This is the time you need to assemble or manufacture an item
from beginning to end. Two types of lead time are ordering lead time and
manufacturing lead time. Ordering lead time is the time it takes from starting the
purchase to receiving the purchase. Manufacturing lead time is the time it takes
for the company to completely manufacture a product from start to end.
Past Due (PD): This is the time during which you consider orders behind
schedule.
Gross Requirements (GR): You generate this MRP calculation through
forecast scheduling using the number of produced units, the amount of required
material for each produced unit, the current stock, and the ordered stock /stock in
transit. This is the total demand for an item during a specific time period.
Scheduled Receipts (SR): These are the open orders for products that the
company currently possesses but has not yet fulfilled.
Projected on Hand (POH): This is the amount of inventory you’ve estimated to
be available after you meet the gross requirements. To calculate this sum, you
add the POH from the previous time period to the scheduled order receipts and
the planned order receipts and then subtract the gross requirements. (Current
POH = Previous POH + SR + POR – GR)
Net Requirements (NR): You generate this MRP calculation through master
scheduling using gross requirements, on-hand inventory, and other quantities.
This is the actual, required quantity to be produced in a particular time period.
Planned Order Receipts (POR): The quantity of orders during a time period that
is expected to be received. This planning for orders keeps the inventory from
going below the threshold necessary.
Planned Order Releases (PORL): This is the amount you plan to order per time
period. This is POR offset by the lead time.
Cumulative Lead Time: This is the greatest amount of time that it takes to
develop the product. You may calculate it by looking at each BOM and figuring
out which one takes the longest.
Product Structure Tree: This is a visual depiction of the bill of materials,
showing how many of each part and how many sub-parts you need to produce
the product.
However, with these advantages come a few drawbacks. Foremost, MRP is only
successful if the accounting is accurate. You must keep records of inventory and BOM
changes up to date. Inaccurate input causes inaccurate output. Another potential
downside to MRP is that it can be costly. If you don’t keep the input in a timely fashion,
it can be difficult and expensive when switching over to a new system.
After MRP receives the input, it generates the output. There are four main outputs.
These include:
Purchase Orders (PO): This is the recommended purchasing schedule that
includes the order you give to suppliers to send the materials. The PO includes a
schedule with quantities and start and finish dates to meet the MPS.
Material Plan: This details the raw materials, assembly items, and component
needs to make the end products with quantities and dates. We recommend that
you use attribute settings to set the time fences and to firm orders.
Work Orders: This details the work that goes into producing the end product,
including which departments are responsible for what part, what materials are
necessary, and what the start and end dates are.
Reports: MRP generates primary and secondary reports. The primary reports
include all three of the above — those that deal with production and inventory
planning and control. Secondary reports are those that detail things, such as
performance control, exception data (e.g., errors or late orders), deviations, and
predictors of future inventories and contracts.
The MRP technique can be vague at times because we call it a calculation process
without necessarily indicating how to compute the data outputs. MRP is about putting
mathematical controls into place using formulas that yield optimal results. MRP is an
optimal control problem that calculates the initial conditions, the dynamics, the
constraints, and the objective. The variables are the local inventory, the order size, the
local demand, the fixed order costs, the variable order costs, and the local inventory
holding costs. MRP comprises many methods and calculations. To find the order
quantities, you can use any number of methods. Three of the most popular are:
Dynamic Lot-Sizing: In inventory theory, this model assumes that the demand
for product fluctuates over time. This complex algorithm generalizes the
economic order quantity model. It requires dynamic programming to perform, so
mathematicians also developed the following models.
Silver-Meal Heuristic: This is an inventory control algorithm, also called least
period cost, that minimizes the total relevant cost per unit of time. In other words,
you use it to calculate the production quantities needed to meet the operational
requirements at the lowest cost possible.
Least-Unit-Cost (LUC) Heuristic: Although quite similar to Silver-Meal, LUC
chooses the period in the future based on average cost per unit rather than on
average cost per period.
The foundation of an ERP solution is a shared database that acts as a central repository
of information. All relevant stakeholders access this same repository of data. Reports
are then culled from this singular, uniform system to provide transparency, efficiency,
and consistency.
The roots of ERP go back to 1913, when an engineer named Ford Whitman Harris saw
a need for greater efficiency and developed a production scheduling model called
economic order quantity (EOQ). This paper-driven precursor to process planning
remained the industry standard until 1964, when Joseph Orlicky developed materials
requirements planning (MRP), and toolmaker Black + Decker became the first company
to adopt an MRP solution that combined EOQ concepts with a mainframe computer.
Rapid software adoption in the 1980s led to integration capabilities that expanded
functionality to include scheduling, bill of materials (BOM), and purchasing functions tied
to corporate financial reporting. Encompassing considerably more manufacturing
processes, manufacturing and resource planning (MRP II) replaced MRP as the
standard for data management and efficiency planning. When the systems expanded
beyond manufacturing processes to include human resources and accounting, they
were recast as enterprise resource planning.
ERP modules are designed for many business processes, such as inventory control and
finance, and can be bundled together for your business. The benefit of an ERP solution
is that the modules have a consistent look and feel, so everyone from the back office to
the front office to the production floor has the same experience. These modules are
integrated to ensure you have a shared system of data and workflows, as well as
standardized business processes.
ERP began as a tool for manufacturing, but has been adopted by industries that provide
services as well as finished goods. A strong ERP system combines integration, real-
time operational support, and a centralized database. That centralized database will
possess modern conveniences such as dashboards, cross-functional operations
reporting, and instant views of the organization as an entire, integrated unit. However, a
centralized database poses one risk: It can open the company to the threat of losing
sensitive information in the event of a security breach.