Material requirements planning (MRP) was introduced in the 1970s as a computerized inventory control system that would calculate the demand for component items, keep track of when they are needed, and generate work orders and purchase orders that take into account the lead time required to make the items in-house or buy them from a supplier. Much of the credit for introducing MRP and educating industry about its benefits goes to three individuals, Joseph Orlicky, George Plossl, and Oliver Wight, and to a professional society they endorsed, known as the American Production and Inventory Control Society APICS. Basically an information system, MRP was quite revolutionary in its early days, because it brought computers and systematic planning to the manufacturing function. Since its introduction, the system has undergone several revisions that reflect the increased power and accessibility of computers and the changing role of manufacturing. For example, MRP II for manufacturing resource planning is much broader in scope than the original material planner, incorporating marketing and financial functions as well. In today's modern factories, MRP II is the standard for management information systems and an important component of computer-integrated manufacturing (CIM).
The main objective of any inventory system is to ensure that material is available when needed--which can easily lead to a tremendous investment of funds in unnecessary inventory. One objective of MRP is to maintain the lowest possible level of inventory. MRP does this by determining when component items are needed and scheduling them to be ready at that time, no earlier and no later.
MRP was the first inventory system to recognize that inventories of raw materials, components, and finished goods may need to be handled differently. In the process of planning inventory levels for these various types of goods, the system also planned purchasing activities (for raw materials and purchased components), manufacturing activities (for component parts and assemblies), and delivery schedules (for finished products). Thus, the system was more than an inventory control system; it became a production scheduling system as well.
One of the few certainties in a manufacturing environment is that things rarely go as planned--orders arrive late, machines break down, workers are absent, designs are changed, and so on. With its computerized database, MRP is able to keep track of the relationship of job orders so that if a delay in one aspect of production is unavoidable, other related activities can be rescheduled, too. MRP systems have the ability to keep schedules valid and up-to-date.
Managing component demand inventory is different from managing finished goods inventory. For one thing, the demand for component parts does not have to be forecasted; it can be derived from the demand for the finished product. For example, suppose demand for a table, consisting of four legs and a tabletop, is 100 units per week. Then, demand for tabletops would also be 100 per week and demand for table legs would be 400 per week. Demand for table legs is totally dependent on the demand for tables. The demand for tables may be forecasted, but the demand for table legs is calculated. The tables are an example of independent demand. The tabletop and table legs exhibit dependent demand.
Another difference between finished products and component parts is the continuity of their demand. For the inventory control systems in the previous chapter, we assumed demand occurred at a constant rate. The inventory systems were designed to keep some inventory on hand at all times, enough, we hoped, to meet each day's demand. With component items, demand does not necessarily occur on a continuous basis. Let us assume in our table example that table legs are the last items to be assembled onto the tables before shipping. Also assume that it takes one week to make a batch of tables and that table legs are assembled onto the tabletops every Friday. If we were to graph the demand for table legs, it would be zero for Monday, Tuesday, Wednesday, and Thursday, but on Friday the demand for table legs would jump to 400. The same pattern would repeat the following week. With this scenario, we do not need to keep an inventory of table legs available on Monday through Thursday of any week. We need table legs only on Fridays. Looking at our graph, demand for table legs occurs in lumps; it is discrete, not continuous. Using an inventory system such as EOQ for component items would result in inventory being held that we know will not be needed until a later date. The excess inventory takes up space, soaks up funds, and requires additional resources for counting, sorting, storing, and moving.
Industries that manufacture complex products, requiring the coordination of component production, find MRP especially useful. A complex product may have hundreds of component parts, dozens of assemblies, and several levels of assembly. MRP tries to ensure that multiple components of an assembly are ready at the same time so that they can be assembled together. Products with simple structures do not need MRP to plan production or monitor inventory levels.
The advantages of MRP are more evident when the manufacturing environment is complex and uncertain. Manufacturing environments in which customer orders are erratic, each job takes a different path through the system, lead time is uncertain, and due dates vary need an information system such as MRP to keep track of the different jobs and coordinate their schedules. The type of environment we are describing is characteristic of batch, or job shop, processes.1 Although MRP is currently available for continuous and repetitive manufacturing, it was designed primarily for systems that produce goods in batches.
Finally, MRP systems are very useful in industries where the customer is allowed to choose among many different options. These products have many common components and are inventoried in some form before the customer order is received. For example, customers of a well-known electronics firm routinely expect delivery in six weeks on goods that take twenty-eight weeks to manufacture. The manufacturer copes with this seemingly unrealistic demand by producing major assemblies and subassemblies in advance of the customer order and then completing the product upon receipt of the order. This type of operation is called assemble-to-order.
There are three major inputs to the MRP process:
The master production schedule (MPS), also called the master schedule, specifies which end items or finished products a firm is to produce, how many are needed, and when they are needed. Recall that aggregate production planning creates a similar schedule for product lines or families, given by months or quarters of a year. The master production schedule works within the constraints of the production plan but produces a more specific schedule by individual products. The time frame is more specific, too. An MPS is usually expressed in days or weeks and may extend over several months to cover the complete manufacture of the items contained in the MPS. The total length of time required to manufacture a product is called its cumulative lead time. Several comments should be made concerning the quantities contained in the MPS:
The MPS for clipboards and lapboards shown in Table 13.1 illustrates two approaches to future scheduling. For clipboards, production beyond period 3 is based on demand forecasts of an even 100 units per period. Projecting these requirements now based on past demand data helps in planning for the availability of resources. For lapdesks, production beyond period 3 appears sparse, probably because it is based on actual customer orders received. We can expect those numbers to increase as the future time periods draw nearer. Evidently, a lengthy lead time is not necessary to gather the resources for producing lap desks.
The master production schedule drives the MRP process. The schedule of finished products provided by the master schedule is needed before the MRP system can do its job of generating production schedules for component items.
Once the MPS is set, the MRP system accesses the product structure file to determine which component items need to be scheduled. The product structure file contains a bill of material (BOM) for every item produced. The bill of material for a product lists the items that go into the product, includes a brief description of each item, and specifies when and in what quantity each item is needed in the assembly process.
When each item is needed can best be described in the form of a product structure diagram, for a clipboard. An assembled item is sometimes referred to as a parent, and a component as a child. The number in parentheses beside each item is the quantity of a given component needed to make one parent. Thus, one clip assembly, two rivets, and one board are needed to make each clipboard. The clip assembly, rivets, and board appear at the same level of the product structure because they are to be assembled together.
A diagram can be converted to a computerized bill of material by labeling the levels in the product structure. The final product, or end item, at the top of the structure--in this case, the clipboard--is labeled level 0. The level number increases as we move down the product structure. The clipboard has three levels of assembly. The bill of material for the clipboard, shows some levels indented underneath others. This specifies which components belong to which parents and can easily be matched to the product structure diagram.
Several specialized bills of material have been designed to simplify information requirements, clarify relationships, and reduce computer processing time. They include phantom bills, K-bills, and modular bills.
The creation of a product structure file can take a considerable amount of time. Accurate bills of material are essential to an effective MRP system. The bill of material must specify how a product is actually manufactured rather than how it was designed to be manufactured. Redundant or obsolete part numbers must be purged from the system. This may not seem like a big task, but in some companies every time a part is purchased from a different supplier, it is assigned a different part number. One firm in the process of implementing MRP was able to eliminate 6,000 extra part numbers from its database and dispose of thousands of dollars of obsolete inventory that had not previously been identified as such!
The inventory master file contains an extensive amount of information on every item that is produced, ordered, or inventoried in the system. It includes such data as on-hand quantities, on-order quantities, lot sizes, safety stock, lead time, and past usage figures. The inventory master file is updated whenever items are withdrawn from or added to inventory or whenever an order is released, revised, or completed. Accuracy of inventory transactions is essential to MRP's ability to keep inventory levels at a minimum. It is estimated that 95 percent inventory accuracy is a prerequisite for an effective MRP system. Although technologies such as bar codes, voice-activated systems, and automated "picking" equipment can improve inventory accuracy considerably, a general overhaul of inventory procedures is often needed. This involves:
If you have taken part in an end-of-year inventory count, you can verify the wide discrepancies that are commonly found between what the records say is in inventory and what is physically there. Unfortunately, by the time the errors are discovered, it is too late to correct them or find out why they occurred. The slate is merely cleaned for next year's record, with the hope or promise that next time will be better.
Cycle counting is taking physical counts of at least some inventory items daily and reconciling differences as they occur. The system specifies which items are to be counted each day on a computer printout and may tie the frequency of the count to the frequency of orders for the item within the MRP system. Thus, items that are used more often are counted more often. The cycle counting system may also be related to the ABC classification system. A items would be counted more often than B items. C items may still be counted only once a year. Approved cycle counting systems are accepted by the accounting standards board as valid replacements for end-of-year physical inventories.
The MRP system is responsible for scheduling the production of all items beneath the end item level. It recommends the release of work orders and purchase orders, and issues rescheduling notices when necessary.
Companies differ in their approach to implementing MRP, but seldom will a company purchase an entire MRP system at one time. Most firms install the product structure/bill-of-material (BOM) processor first and then add the inventory module, followed by the MRP module. The BOM and inventory modules have large databases and serve as major inputs to the rest of the process.Purchasing is also brought online early, usually shortly after the BOM module is installed. Assemble-to-order companies tend to implement the customer order entry module as soon as possible.
It may be some time before the master schedule module or higher-level planning modules are added. How, you may wonder, does the MRP system run without a master schedule? Actually, a master production schedule is used, but it is not generated or maintained by the MRP system; it is input by hand.
The capacity planning module is important for a well-run MRP system, and its absence often separates the successful MRP user from the unsuccessful user.
Shop floor control is a difficult module to implement and is probably the most disappointing one in practice.
As MRP evolved and more modules and features were added in the areas of capacity planning, marketing, and finance, it became clear that the name material requirements planning was no longer adequate to describe the full range of activities this system could coordinate. In keeping with the MRP acronym, the new and improved MRP became known as MRP II, for manufacturing resource planning. The term closed loop has been used to describe the numerous feedback loops between plans for production and available capacity and between planned and actual occurrences.Manufacturing resource planning is a misnomer because MRP II software is also used in services, such as education, architecture, health care, distribution, and the like. Thus, systems such as SRP (service requirements planning), DRP (distribution requirements planning), and BRP (business requirements planning), are also available.
Companies that have carefully implemented MRP have seen dramatic improvements in performance and reductions in cost. Reports of 40 percent reductions in inventory levels, 33 percent improvements in customer service levels, and 20 percent reductions in production costs are common. Still, MRP has never fully achieved the successes that were promised in the early 1970s, when the concept was first introduced. Many of its problems have been associated with poor implementation strategies, lack of support by top management, and lack of commitment by other company personnel. Expectations for what MRP could accomplish were inflated by software vendors and consultants, who seemed to assure managers that the "problem" of manufacturing could be solved if they purchased certain hardware and software products. Money was thrown at the problem, in the form of MRP-related purchases, without an understanding of actual manufacturing needs. Automated systems, especially those dealing with large amounts of information, are only as good as the input provided to them. Inaccurate data can ruin an MRP system. Adding fancy options, such as lot sizing and safety stock, and unrealistic assessments of capacity are other common sources of problems.
As a common database for the entire firm, MRP tends to be perceived initially by those in different functional areas as an intrusion into their turf. For example, with MRP, marketing can look at the production figures and determine whether manufacturing has scheduled enough production to meet demand, production can monitor the accuracy of marketing's demand forecasts by comparing planned against actual figures, and salespersons can access the status of customer orders themselves without relying on promises of service from production. Eventually, the common access to information improves managerial decision making, but there is an adjustment period while managers learn to work together.
MRP was the first computerized system used on the factory floor. And it was quite disruptive. Shop supervisors, whose jobs for the past twenty years had consisted of making daily schedules for their workers, were handed a computer printout on Monday mornings that laid out worker assignments for a week in advance. Workers accustomed to long queues of work waiting to be processed, instinctively slowed down their production rate as the results of tight MRP scheduling began to take effect and queues dwindled. These examples are representative of the behavioral problems that faced MRP in its early stages of development. As with many new technologies or concepts, the technical issues of MRP were solved far in advance of the behavioral issues. Fortunately, the passage of time and the educational efforts associated with a broadened MRP concept have helped to smooth the way for effective implementation of MRP II.
With implementation problems no longer at the forefront, practitioners and academicians alike began to search for the "real" problems inherent with MRP. They found that some aspects of the MRP concept do not match the realities of manufacturing. These mismatches include the following:
With these basic problems, what then are the prospects for MRP/MRP II in the future? Actually, they are quite good, but in a modified form. Some industries, primarily companies that produce goods in standard batches, can successfully use MRP/MRP II as is. However, for most companies, the real benefits of MRP II are obtained from its ability to coordinate a company's strategy among different functional areas--that is, to "plan." The common database and simulation capabilities are very useful in responding quickly to what-if? questions at various levels of detail. BOM processors, purchasing modules, and customer order entry are standard requirements for manufacturing information systems. They are especially helpful in monitoring design quality, vendor quality, and customer service. The transparency of MRP-related decisions to different areas of the firm is invaluable in building trust, teamwork, and better decisions. The financial tie-ins can produce superior fine-tuning of cash flow planning and profit/cost projections.
These capabilities are at the heart of a new generation of planning and control systems called enterprise resource planning (ERP).Rapid advances in information technology and the globalization of markets and production have challenged the capabilities of MRP and MRP II systems. Enterprise resource planning (ERP) updates MRP II with relational database management, simple user interfaces, and client/server architecture. Traditional MRP systems focus on an individual plant's operation, whereas ERP systems manage the resources of an entire enterprise. Contrast an MRP system concerned with customer demand, production schedules, inventory levels, and available capacity at work centers within a plant, to an ERP system concerned with customer demand and available capacity at company plants worldwide, and production schedules and inventory levels along its supply chain as well as throughout the company. ERP systems typically contain production-oriented MRP modules, as well as MRP II-type modules for business planning, customer service, financial management, and accounting. Support for multiple languages and currencies, foreign taxes and accounting rules, integrated logistics, and electronic commerce are also common.
Sales of ERP software are expected to reach $6 billion by 2002 for vendors such as PeopleSoft, Baan, Oracle, and SAP. We introduced the process orientation and supply chain portion of SAP's premier product, R/3. For consistency, we have again chosen SAP's R/3 product to use as an example--this time of an ERP system.
R/3, like many MRP systems before it, consists of a series of application modules that can be used alone or in concert. The modules are fully integrated, use a common database, and support processes that extend across functional areas. Transactions in one module are immediately available to all other modules at all relevant sites, whether they be corporate headquarters, manufacturing plants, suppliers, sales offices, or subsidiaries. In most cases, sites are connected via the Internet or intranets.
R/3's modules can be grouped into six main categories: (1) Accounting and Controlling, (2) Sales and Distribution, (3) Production and Materials Management, (4) Quality Management, (5) Human Resources, and (6) Project Management.
The accounting and controlling module encompasses financial accounting, investment management, cost control, treasury management, asset management, and enterprise controlling. Included are cost centers, profit centers, activity-based costing, capital budgeting, and profitability analysis, as well as enterprise measures of performance.
The sales and distribution module supports customer-related activities such as order processing, product configuration, and delivery quotations. Pricing, promotions, availability, and shipping options are determined as sales orders are entered. Managers can reserve inventory for specific customers, request certain supplier options, and customize orders. Products may be assembled-to-order, built-to-order, or engineered-to-order. Distribution requirements, transportation management, shipping schedules, and export controls are included in the module, as are billing, invoicing, rebate processing, product registrations, and customer complaints.
Materials management manages all tasks related to the supply chain, including purchasing, inventory and warehouse functions, supplier evaluations, JIT deliveries, and invoice verification. Production planning is set up to handle all types of manufacturing--make-to-order, assemble-to-order, repetitive and continuous. The module interfaces with CAD programs; performs process planning, bill-of-material processing, and product costing; processes engineering change orders; plans material requirements (MRP); allocates resources; and schedules and monitors production. Kanbans, Gantt charts, master schedules, and available-to-promise are all supported.
Quality management monitors, captures and manages all processes related to quality along the entire supply chain. It coordinates inspections of incoming and in-process material, integrates SPC initiatives with production planning, takes corrective measures, and integrates laboratory information. Included with quality management are plant maintenance and customer service. Plant maintenance plans, controls, and schedules preventive maintenance and performs breakdown maintenance to ensure the maximum availability of physical assets. Customer service relates to the repair, return, and replacement of unsatisfactory items, the availability of service parts, product reliability and customer satisfaction.
The human resources module covers all personnel management tasks, including workforce planning, employee scheduling, training and development, payroll and benefits, travel expense reimbursement, applicant data, job descriptions, organization charts, and work flow analysis.
The project management module coordinates and controls all phases of a project from quotation to design and approval, to resource management and cost settlement. It plans and monitors data and resources using work breakdown structures, critical path analysis, and project crashing.
Together, these modules form an integrated information technology strategy for effectively managing the entire enterprise. R/3 connects processes that belong together, giving every employee fast, convenient access to the information required for their jobs.
Both the scope and detail of ERP systems are impressive. As might be expected, these systems require considerable time and skill to implement. Like MRP systems of the past, ERP comes with droves of consultants promising swift, easy installations. Those companies successful with ERP have taken the time to think about how their processes work and how they can best be integrated before "automating" them. SAP has collected "best practices" from its customers and shares them in the form of industry solutions. Solution maps and stories of successful implementations are also available for aerospace and defense, apparel, automotive, chemicals, consumer products, engineering and construction, health care, high-tech industries, insurance, media, oil and gas, pharmaceuticals, the public sector, real estate, retail, telecommunications, and utilities.
Material requirements planning (MRP) is a computerized inventory control and production planning system. It has enjoyed widespread use in U.S. industry, primarily for batch manufacturing, as an information system that improves manufacturing decision making. MRP began as a system for ensuring that sufficient material was available when needed. However, in application, it became clear that material was not the only resource in short supply. Planning capabilities for machine and labor resources were added to the system in the form of capacity requirements planning (CRP).
MRP requires input from other functional areas of a firm, such as marketing and finance. As these areas began to see the power of a common database system, they encouraged the expansion of MRP into areas such as demand forecasting, demand management, customer order entry, accounts payable, accounts receivable, budgets, and cash-flow analysis. Clearly, this enhanced version was more powerful than the original MRP systems that ordered material and scheduled production. It provided a common database that the entire company could use. Its what-if? capability proved invaluable in evaluating trade-offs, and the easy access to information encouraged more sophisticated planning. The "new" MRP, called MRP II, for manufacturing resource planning, has become a standard component for computer-integrated manufacturing (CIM).
However, there are some drawbacks to MRP II. The system requires a lot of information, and the information must be accurate and timely. The reporting requirements are sometimes overwhelming, especially as manufacturers move toward more rapid production and shorter cycle times. Fixed lead time assumptions cause problems when schedules hit the shop floor.
Enterprise resource planning (ERP) systems are more technologically advanced and more comprehensive than MRP II systems. They integrate processes, information, and people across functions, plants, companies, and geographic locations. Although MRP is still at the heart of ERP, there are many other resources available, such as JIT and finite scheduling, that can improve shop floor performance.