Download presentation
Presentation is loading. Please wait.
Published byColin Lambert Modified over 8 years ago
1
Copyright 2009 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Resource Planning Operations Management - 6 th Edition Chapter 15 Roberta Russell & Bernard W. Taylor, III
2
Copyright 2009 John Wiley & Sons, Inc.15-2 Lecture Outline Material Requirements Planning (MRP) Capacity Requirements Planning (CRP) Enterprise Resource Planning (ERP) Customer Relationship Management (CRM) Supply Chain Management (SCM) Product Lifecycle Management (PLM)
3
Copyright 2009 John Wiley & Sons, Inc.15-3 Just ERP?? ERP starts on slide 52
4
Copyright 2009 John Wiley & Sons, Inc.15-4 Resource Planning for Manufacturing
5
Copyright 2009 John Wiley & Sons, Inc.15-5 Material Requirements Planning (MRP) Computerized inventory control and production planning system When to use MRP? Dependent demand items Discrete demand items Complex products Job shop production Assemble-to-order environments
6
Copyright 2009 John Wiley & Sons, Inc.15-6 Demand Characteristics 12345 Week 400 400 – 300 300 – 200 200 – 100 100 – No. of tables Continuous demand M T W Th F M T W Th F 400 400 – 300 300 – 200 200 – 100 100 – No. of tables Discrete demand Independent demand 100 tables Dependent demand 100 x 1 = 100 tabletops 100 x 4 = 400 table legs
7
Copyright 2009 John Wiley & Sons, Inc.15-7 Material Requirements Planning Material requirements planning Planned order releases Work orders Purchase orders Rescheduling notices Item master file Product structure file Master production schedule
8
Copyright 2009 John Wiley & Sons, Inc.15-8 MRP Inputs and Outputs Inputs Master production schedule Master production schedule Product structure file Product structure file Item master file Item master file Outputs Planned order releases Planned order releases Work orders Work orders Purchase orders Purchase orders Rescheduling notices Rescheduling notices
9
Copyright 2009 John Wiley & Sons, Inc.15-9 Master Production Schedule Drives MRP process with a schedule of finished products Quantities represent production not demand Quantities may consist of a combination of customer orders and demand forecasts Quantities represent what needs to be produced, not what can be produced Quantities represent end items that may or may not be finished products
10
Copyright 2009 John Wiley & Sons, Inc.15-10 Master Production Schedule (cont.) PERIOD MPS ITEM12345 Pencil Case125125125125125 Clipboard8595120100100 Lapboard75120472017 Lapdesk0500500
11
Copyright 2009 John Wiley & Sons, Inc.15-11 Product Structure File
12
Copyright 2009 John Wiley & Sons, Inc.15-12 Product Structure Top clip (1)Bottom clip (1) Pivot (1)Spring (1) Rivets (2) Finished clipboardPressboard (1) Clipboard
13
Copyright 2009 John Wiley & Sons, Inc.15-13 Product Structure Tree Clipboard Level 0 Level 1 Level 2 Spring (1) Bottom Clip (1) Top Clip (1) Pivot (1) Rivets (2) Clip Ass’y (1) Pressboard (1)
14
Copyright 2009 John Wiley & Sons, Inc.15-14 Multilevel Indented BOM 0 - - - -Clipboardea1 - 1 - - -Clip Assemblyea1 - - 2 - -Top Clipea1 - - 2 - -Bottom Clipea1 - - 2 - -Pivotea1 - - 2 - -Springea1 - 1 - - -Rivetea2 - 1 - - -Press Boardea1 LEVELITEMUNIT OF MEASUREQUANTITY
15
Copyright 2009 John Wiley & Sons, Inc.15-15 Specialized BOMs Phantom bills Transient subassemblies Transient subassemblies Never stocked Never stocked Immediately consumed in next stage Immediately consumed in next stage K-bills Group small, loose parts under pseudo-item number Group small, loose parts under pseudo-item number Reduces paperwork, processing time, and file space Reduces paperwork, processing time, and file space
16
Copyright 2009 John Wiley & Sons, Inc.15-16 Specialized BOMs (cont.) Modular bills Product assembled from major subassemblies and customer options Product assembled from major subassemblies and customer options Modular bill kept for each major subassembly Modular bill kept for each major subassembly Simplifies forecasting and planning Simplifies forecasting and planning X10 automobile example X10 automobile example 3 x 8 x 3 x 8 x 4 = 2,304 configurations 3 x 8 x 3 x 8 x 4 = 2,304 configurations 3 + 8 + 3 + 8 + 4 = 26 modular bills 3 + 8 + 3 + 8 + 4 = 26 modular bills
17
Copyright 2009 John Wiley & Sons, Inc.15-17 4-Cylinder (.40)Bright red (.10)Leather (.20)Grey (.10)Sports coupe (.20) 6-Cylinder (.50)White linen (.10)Tweed (.40)Light blue (.10)Two-door (.20) 8-Cylinder (.10)Sulphur yellow (.10)Plush (.40)Rose (.10)Four-door (.30) Neon orange (.10)Off-white (.20)Station wagon (.30) Metallic blue (.10)Cool green (.10) Emerald green (.10)Black (.20) Jet black (.20)Brown (.10) Champagne (.20)B/W checked (.10) X10 Automobile EnginesExterior colorInteriorInterior colorBody (1 of 3)(1 of 8)(1 of 3)(1 of 8)(1 of 4) Modular BOMs
18
Copyright 2009 John Wiley & Sons, Inc.15-18 Time-phased Bills Forward scheduling: start at today‘s date and schedule forward to determine the earliest date the job can be finished. If each item takes one period to complete, the clipboards can be finished in three periods Backward scheduling: start at the due date and schedule backwards to determine when to begin work. If an order for clipboards is due by period three, we should start production now an assembly chart shown against a time scale
19
Copyright 2009 John Wiley & Sons, Inc.15-19 Item Master File DESCRIPTIONINVENTORY POLICY ItemPressboardLead time1 Item no.7341Annual demand5000 Item typePurchHolding cost1 Product/sales classCompOrdering/setup cost50 Value classBSafety stock 0 Buyer/plannerRSRReorder point39 Vendor/drawing07142EOQ316 Phantom codeNMinimum order qty100 Unit price/cost1.25Maximum order qty500 PeggingYMultiple order qty1 LLC1Policy code3
20
Copyright 2009 John Wiley & Sons, Inc.15-20 Item Master File (cont.) PHYSICAL INVENTORYUSAGE/SALES CODES On hand150YTD usage/sales1100 LocationW142MTD usage/sales75 On order100YTD receipts1200 Allocated75MTD receipts0 Cycle3Last receipt8/25 Last count9/5Last issue10/5 Difference-2 Cost acct.00754 Routing00326 Engr07142
21
Copyright 2009 John Wiley & Sons, Inc.15-21 MRP Processes Exploding the bill of material Netting out inventory Lot sizing Time-phasing requirements Netting process of subtracting on- hand quantities and scheduled receipts from gross requirements to produce net requirements process of subtracting on- hand quantities and scheduled receipts from gross requirements to produce net requirements Lot sizing determining the quantities in which items are usually made or purchased determining the quantities in which items are usually made or purchased
22
Copyright 2009 John Wiley & Sons, Inc.15-22 MRP Matrix
23
Copyright 2009 John Wiley & Sons, Inc.15-23 MRP: Example Master Production Schedule 12345 Clipboard8595120100100 Lapdesk0600600 Item Master File CLIPBOARDLAPDESKPRESSBOARD On hand2520150 On order175 (Period 1)00 (sch receipt) (sch receipt) LLC001 Lot sizeL4LMult 50Min 100 Lead time111
24
Copyright 2009 John Wiley & Sons, Inc.15-24 MRP: Example (cont.) Product Structure Record Clipboard Lapdesk Pressboard (2) Trim (3’) Beanbag (1) Glue (4 oz) Level 0 Pressboard (1) Clip Ass’y (1) Rivets (2) Level 1
25
Copyright 2009 John Wiley & Sons, Inc.15-25 ITEM: CLIPBOARDLLC: 0PERIOD LOT SIZE: L4LLT: 112345 Gross Requirements8595120100100 Scheduled Receipts175 Projected on Hand25 Net Requirements Planned Order Receipts Planned Order Releases MRP: Example (cont.)
26
Copyright 2009 John Wiley & Sons, Inc.15-26 MRP: Example (cont.) ITEM: CLIPBOARDLLC: 0PERIOD LOT SIZE: L4LLT: 112345 Gross Requirements8595120100100 Scheduled Receipts175 Projected on Hand25115 Net Requirements0 Planned Order Receipts Planned Order Releases (25 + 175) = 200 units available (200 - 85) = 115 on hand at the end of Period 1
27
Copyright 2009 John Wiley & Sons, Inc.15-27 ITEM: CLIPBOARDLLC: 0PERIOD LOT SIZE: L4LLT: 112345 Gross Requirements8595120100100 Scheduled Receipts175 Projected on Hand2511520 Net Requirements00 Planned Order Receipts Planned Order Releases 115 units available (115 - 85) = 20 on hand at the end of Period 2 MRP: Example (cont.)
28
Copyright 2009 John Wiley & Sons, Inc.15-28 ITEM: CLIPBOARDLLC: 0PERIOD LOT SIZE: L4LLT: 112345 Gross Requirements8595120100100 Scheduled Receipts175 Projected on Hand25115200 Net Requirements00100 Planned Order Receipts100 Planned Order Releases100 20 units available (20 - 120) = -100 — 100 additional Clipboards are required Order must be placed in Period 2 to be received in Period 3 MRP: Example (cont.)
29
Copyright 2009 John Wiley & Sons, Inc.15-29 ITEM: CLIPBOARDLLC: 0PERIOD LOT SIZE: L4LLT: 112345 Gross Requirements8595120100100 Scheduled Receipts175 Projected on Hand2511520000 Net Requirements00100100100 Planned Order Receipts100100100 Planned Order Releases100100100 Following the same logic Gross Requirements in Periods 4 and 5 develop Net Requirements, Planned Order Receipts, and Planned Order Releases MRP: Example (cont.)
30
Copyright 2009 John Wiley & Sons, Inc.15-30 ITEM: LAPDESKLLC: 0PERIOD LOT SIZE: MULT 50LT: 112345 Gross Requirements0600600 Scheduled Receipts Projected on Hand20 Net Requirements Planned Order Receipts Planned Order Releases MRP: Example (cont.)
31
Copyright 2009 John Wiley & Sons, Inc.15-31 ITEM: LAPDESKLLC: 0PERIOD LOT SIZE: MULT 50LT: 112345 Gross Requirements0600600 Scheduled Receipts Projected on Hand2020101000 Net Requirements04050 Planned Order Receipts5050 Planned Order Releases5050 Following the same logic, the Lapdesk MRP matrix is completed as shown MRP: Example (cont.)
32
Copyright 2009 John Wiley & Sons, Inc.15-32 ITEM: PRESSBOARDLLC: 0PERIOD LOT SIZE: MIN 100LT: 112345 Gross Requirements Scheduled Receipts Projected on Hand150 Net Requirements Planned Order Receipts Planned Order Releases ITEM: CLIPBOARDLLC: 0PERIOD LOT SIZE: L4LLT: 112345 Planned Order Releases100100100 ITEM: LAPDESKLLC: 0PERIOD LOT SIZE: MULT 50LT: 112345 Planned Order Releases5050 MRP: Example (cont.)
33
Copyright 2009 John Wiley & Sons, Inc.15-33 ITEM: PRESSBOARDLLC: 0PERIOD LOT SIZE: MIN 100LT: 112345 Gross Requirements1001002001000 Scheduled Receipts Projected on Hand150 Net Requirements Planned Order Receipts Planned Order Releases ITEM: CLIPBOARDLLC: 0PERIOD LOT SIZE: L4LLT: 112345 Planned Order Releases100100100 ITEM: LAPDESKLLC: 0PERIOD LOT SIZE: MULT 50LT: 112345 Planned Order Releases5050 x2 x2 x1 x1 x1 MRP: Example (cont.)
34
Copyright 2009 John Wiley & Sons, Inc.15-34 ITEM: PRESSBOARDLLC: 0PERIOD LOT SIZE: MIN 100LT: 112345 Gross Requirements1001002001000 Scheduled Receipts Projected on Hand1505050000 Net Requirements50150100 Planned Order Receipts100150100 Planned Order Releases100150100 ITEM: CLIPBOARDLLC: 0PERIOD LOT SIZE: L4LLT: 112345 Planned Order Releases100100100 ITEM: LAPDESKLLC: 0PERIOD LOT SIZE: MULT 50LT: 112345 Planned Order Releases5050 MRP: Example (cont.)
35
Copyright 2009 John Wiley & Sons, Inc.15-35 Planned Order Report PERIOD ITEM12345 Clipboard100100100 Lapdesk5050 Pressboard100150100 MRP: Example (cont.)
36
Copyright 2009 John Wiley & Sons, Inc.15-36 Lot Sizing in MRP Systems Lot-for-lot ordering policy Fixed-size lot ordering policy Minimum order quantities Maximum order quantities Multiple order quantities Economic order quantity Periodic order quantity
37
Copyright 2009 John Wiley & Sons, Inc.15-37 Using Excel for MRP Calculations
38
Copyright 2009 John Wiley & Sons, Inc.15-38 Advanced Lot Sizing Rules: L4L Total cost of L4L = (4 X $60) + (0 X $1) = $240
39
Copyright 2009 John Wiley & Sons, Inc.15-39 Advanced Lot Sizing Rules: EOQ minimum order quantity Total cost of EOQ = (2 X $60) + [(10 + 50 + 40) X $1)] = $220
40
Copyright 2009 John Wiley & Sons, Inc.15-40 Advanced Lot Sizing Rules: POQ periods worth of requirements Total cost of POQ = (2 X $60) + [(20 + 40) X $1] = $180
41
Copyright 2009 John Wiley & Sons, Inc.15-41 Planned Order Report Item#2740Date9 - 25 - 05 On hand100Lead time2 weeks On order200Lot size200 Allocated50Safety stock50 SCHEDULEDPROJECTED DATEORDER NO.GROSS REQS.RECEIPTSON HANDACTION 50 9-26AL 44162525 9-30AL 4174250 10-01GR 647050- 50 10-08SR 7542200150Expedite SR 10-01 10-10CO 44717575 10-15GR 64715025 10-23GR 6471250 10-27GR 647350- 50Release PO 10-13 Key:AL= allocatedWO= work order CO= customer orderSR= scheduled receipt PO= purchase orderGR= gross requirement
42
Copyright 2009 John Wiley & Sons, Inc.15-42 MRP Action Report Current date 9-25-08 ITEMDATEORDER NO.QTY.ACTION #274010-087542200ExpediteSR10-01 #361610-09Move forwardPO10-07 #241210-10Move forwardPO10-05 #342710-15Move backwardPO10-25 #251610-207648100De-expediteSR10-30 #274010-27200ReleasePO10-13 #366610-3150ReleaseWO10-24
43
Copyright 2009 John Wiley & Sons, Inc.15-43 Capacity Requirements Planning (CRP) Creates a load profile Identifies under-loads and over-loads Inputs Planned order releases Routing file Open orders file
44
Copyright 2009 John Wiley & Sons, Inc.15-44 CRP MRP planned order releases Routing file Capacity requirements planning Open orders file Load profile for each process
45
Copyright 2009 John Wiley & Sons, Inc.15-45 Calculating Capacity Maximum capability to produce Rated Capacity Theoretical output that could be attained if a process were operating at full speed without interruption, exceptions, or downtime Theoretical output that could be attained if a process were operating at full speed without interruption, exceptions, or downtime Effective Capacity Takes into account the efficiency with which a particular product or customer can be processed and the utilization of the scheduled hours or work Takes into account the efficiency with which a particular product or customer can be processed and the utilization of the scheduled hours or work Effective Daily Capacity = (no. of machines or workers) x (hours per shift) x (no. of shifts) x (utilization) x ( efficiency)
46
Copyright 2009 John Wiley & Sons, Inc.15-46 Calculating Capacity (cont.) Utilization Percent of available time spent working Percent of available time spent working Efficiency How well a machine or worker performs compared to a standard output level How well a machine or worker performs compared to a standard output level Load Standard hours of work assigned to a facility Standard hours of work assigned to a facility Load Percent Ratio of load to capacity Ratio of load to capacity Load Percent = x 100% load capacity
47
Copyright 2009 John Wiley & Sons, Inc.15-47 Load Profiles graphical comparison of load versus capacity Leveling underloaded conditions: Acquire more work Acquire more work Pull work ahead that is scheduled for later time periods Pull work ahead that is scheduled for later time periods Reduce normal capacity Reduce normal capacity
48
Copyright 2009 John Wiley & Sons, Inc.15-48 Reducing Over-load Conditions Eliminating unnecessary requirements Rerouting jobs to alternative machines, workers, or work centers Splitting lots between two or more machines Increasing normal capacity Subcontracting Increasing efficiency of the operation Pushing work back to later time periods Revising master schedule
49
Copyright 2009 John Wiley & Sons, Inc.15-49 Initial Load Profile Hours of capacity 123456123456123456123456 Time (weeks) Normalcapacity 120 120 – 110 110 – 100 100 – 90 90 – 80 80 – 70 70 – 60 60 – 50 50 – 40 40 – 30 30 – 20 20 – 10 10 – 0 0 –
50
Copyright 2009 John Wiley & Sons, Inc.15-50 Adjusted Load Profile Hours of capacity 123456123456123456123456 Time (weeks) Normalcapacity 120 120 – 110 110 – 100 100 – 90 90 – 80 80 – 70 70 – 60 60 – 50 50 – 40 40 – 30 30 – 20 20 – 10 10 – 0 0 – Pull ahead Push back Overtime Work an extra shift Load leveling process of balancing underloads and overloads process of balancing underloads and overloads
51
Copyright 2009 John Wiley & Sons, Inc.15-51 Relaxing MRP Assumptions Material is not always the most constraining resource Lead times can vary Not every transaction needs to be recorded Shop floor may require a more sophisticated scheduling system Scheduling in advance may not be appropriate for on-demand production.
52
Copyright 2009 John Wiley & Sons, Inc.15-52 Enterprise Resource Planning (ERP) Software that organizes and manages a company’s business processes by sharing information across functional areas integrating business processes facilitating customer interaction providing benefit to global companies
53
Copyright 2009 John Wiley & Sons, Inc.15-53 Enterprise Resource Planning (ERP) Starts on page 665 of 5 th ed, 668 of 6 th ed Software that organizes and manages a company’s business processes by sharing information across functional areas integrating business processes facilitating customer interaction providing benefit to global companies
54
Copyright 2009 John Wiley & Sons, Inc.15-54 ERP and MRP First came MRP around 1970 Thanks to George Plossl, Oliver Wight, Joseph Orlicki Thanks to George Plossl, Oliver Wight, Joseph Orlicki MRP is Material Requirements Planning MRP is Material Requirements Planning Then came MRP II around 1980 MRP II is Manufacturing Resource Planning MRP II is Manufacturing Resource Planning Then came ERP around 1990 Today, its ERP II
55
Copyright 2009 John Wiley & Sons, Inc.15-55 Evolution of ERP II
56
Copyright 2009 John Wiley & Sons, Inc.15-56 A lesson in Information Architecture First, we need a problem-solving methodology
57
Copyright 2009 John Wiley & Sons, Inc.15-57 Goldratt Methodology (Thinking Process) What to change?? What to change to?? How to cause the change??
58
Copyright 2009 John Wiley & Sons, Inc.15-58 WHAT TO CHANGE CIRCA 1993: Problems with the Mainframe Architecture Poor data visibility Long lead times on maintenance, modifications to legacy software (36 months) No GUI interfaces
59
Copyright 2009 John Wiley & Sons, Inc.15-59 More problems New software apps were expensive and time consuming to develop Mainframes were computational bottlenecks Desktop PCs sat idle 99% of the time
60
Copyright 2009 John Wiley & Sons, Inc.15-60 Components of any Software Application
61
Copyright 2009 John Wiley & Sons, Inc.15-61 Components in brief
62
Copyright 2009 John Wiley & Sons, Inc.15-62 Mainframe Architecture
63
Copyright 2009 John Wiley & Sons, Inc.15-63 Goldratt: We will build a tree Called a current reality tree Begin by identifying the UNDESIRABLE EFFECTS the stakeholders are experiencing The basic tree relationship: IF {box a}, then {box b}.
64
Copyright 2009 John Wiley & Sons, Inc.15-64 Only the centralized MIS shop could do maintenance and new development work Mainframes were computational bottlenecks Each application had to reside entirely on the mainframe Many new applications were being built Change requests for existing apps were frequent and increasing Centralized MIS shop backlogs were extending out to 36 months Competitive and customer environments are changing rapidly Budgets for MIS shops were stretched to their limits
65
Copyright 2009 John Wiley & Sons, Inc.15-65 Sales cannot see what is happening in accounts receivable Sales cannot track customer orders through the manufacturing/distribution process Information visibility across the enterprise is impossible Independent data pools are created that cannot be integrated Islands of automation are created End users develop their own independent applications that run on departmental PC’s Centralized MIS shops have lead times of 36 months or longer Centralized mainframes are computing bottlenecks
66
Copyright 2009 John Wiley & Sons, Inc.15-66 WHAT TO CHANGE TO: An architecture in which the data are totally integrated An architecture in which most of the processing is not done on mainframes Decentralization of MIS What architecture was this???
67
Copyright 2009 John Wiley & Sons, Inc.15-67 HOW TO CAUSE THE CHANGE: ERP implementation Solves the problems identified above
68
Copyright 2009 John Wiley & Sons, Inc.15-68 Organizational Data Flows Source: Adapted from Joseph Brady, Ellen Monk, and Bret Wagner, Concepts in Enterprise Resource Planning (Boston: Course Technology, 2001), pp. 7–12
69
Copyright 2009 John Wiley & Sons, Inc.15-69 ERP’s Central Database
70
Copyright 2009 John Wiley & Sons, Inc.15-70 Selected Enterprise Software Vendors
71
Copyright 2009 John Wiley & Sons, Inc.15-71 ERP Implementation Analyze business processes Choose modules to implement Which processes have the biggest impact on customer relations? Which processes have the biggest impact on customer relations? Which process would benefit the most from integration? Which process would benefit the most from integration? Which processes should be standardized? Which processes should be standardized? Align level of sophistication Finalize delivery and access Link with external partners
72
Copyright 2009 John Wiley & Sons, Inc.15-72 Customer Relationship Management (CRM) Software that Plans and executes business processes Plans and executes business processes Involves customer interaction Involves customer interaction Changes focus from managing products to managing customers Changes focus from managing products to managing customers Analyzes point-of-sale data for patterns used to predict future behavior Analyzes point-of-sale data for patterns used to predict future behavior
73
Copyright 2009 John Wiley & Sons, Inc.15-73 Supply Chain Management Software that plans and executes business processes related to supply chains Includes Supply chain planning Supply chain planning Supply chain execution Supply chain execution Supplier relationship management Supplier relationship management Distinctions between ERP and SCM are becoming increasingly blurred
74
Copyright 2009 John Wiley & Sons, Inc.15-74 Product Lifecycle Management (PLM) Software that Incorporates new product design and development and product life cycle management Incorporates new product design and development and product life cycle management Integrates customers and suppliers in the design process though the entire product life cycle Integrates customers and suppliers in the design process though the entire product life cycle
75
Copyright 2009 John Wiley & Sons, Inc.15-75 ERP and Software Systems
76
Copyright 2009 John Wiley & Sons, Inc.15-76 Connectivity Application programming interfaces (APIs) give other programs well-defined ways of speaking to them give other programs well-defined ways of speaking to them Enterprise Application Integration (EAI) solutions EDI is being replaced by XML, business language of Internet Service-oriented architecture (SOA) collection of “services” that communicate with each other within software or between software collection of “services” that communicate with each other within software or between software
77
Copyright 2009 John Wiley & Sons, Inc.15-77 Copyright 2009 John Wiley & Sons, Inc. All rights reserved. Reproduction or translation of this work beyond that permitted in section 117 of the 1976 United States Copyright Act without express permission of the copyright owner is unlawful. Request for further information should be addressed to the Permission Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own use only and not for distribution or resale. The Publisher assumes no responsibility for errors, omissions, or damages caused by the use of these programs or from the use of the information herein.
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.