Material Requirements Planning (MRP)
Material Requirements Planning (MRP)
Material Requirements Planning (MRP)
History
Begun around 1960 as computerized approach to purchasing and
production scheduling.
Joseph Orlicky, Oliver Wight, and others.
APICS launched MRP Crusade in 1972 to promote MRP.
Key Insight
Independent Demand finished products
Dependent Demand components
Assumptions
1. Known deterministic demands.
2. Fixed, known production leadtimes.
3. Infinite capacity.
MRP Procedure
1. Netting: net requirements against projected inventory
2. Lot Sizing: planned order quantities
3. Time Phasing: planned orders backed out by leadtime
4. BOM Explosion: gross requirements for components
Inputs
Master Production Schedule (MPS): due dates and quantities for all
top level items
Bills of Material (BOM): for all parent items
Inventory Status: (on hand plus scheduled receipts) for all items
Planned Leadtimes: for all items
Example - Stool
Indented BOM
Graphical BOM
Stool
Stool
Base (1)
Level 1
Base
(1)
Seat
(1)
Legs (4)
Bolts (2)
Bolts (2) Level 2
Bolts (2)
they occur for MRP calcs. Actually, they might
be left off BOM altogether in practice.
Level 0
Example
Item: Stool (Leadtime = 1 week)
Week
Gross Reqs
Sched Receipts
Proj Inventory
Net Reqs
Planned Orders
5
120
20
20
20
20
20
-100
100
-100
100
4
100
-100
100
-100
-100
100
Example (cont.)
BOM explosion
Item: Legs (Leadtime = 2 weeks)
Week
Gross Reqs
Sched Receipts
Proj Inventory
Net Reqs
Planned Orders
200
200
200
3
400
-200
200
-200
-200
-200
Terminology
Level Code: lowest level on any BOM on which part is
found
Planning Horizon: should be longer than longest
cumulative leadtime for any product
Time Bucket: units planning horizon is divided into
Lot-for-Lot: batch sizes equal demands (other lot sizing
techniques, e.g., EOQ or Wagner-Whitin can be used)
Pegging: identify gross requirements with next level in
BOM (single pegging) or customer order (full pegging)
that generated it. Single usually used because full is
difficult due to lot-sizing, yield loss, safety stocks, etc.
More Terminology
Firm Planned Orders (FPOs): planned order that the MRP system
does not automatically change when conditions change can
stabilize system
Service Parts: parts used in service and maintenance must be
included in gross requirements
Order Launching: process of releasing orders to shop or vendors
may include inflation factor to compensate for shrinkage
Exception Codes: codes to identify possible data inaccuracy (e.g.,
dates beyond planning horizon, exceptionally large or small order
quantities, invalid part numbers, etc.) or system diagnostics (e.g.,
orders open past due, component delays, etc.)
1
20
80
20
2
50
3
10
50
10
4
50
130
50
5
50
6
10
7
20
50
10
20
8
40
90
40
9
20
10
30
20
30
A 100
h 1
300
D
30
10
Lot-for-Lot: $1000
2 AD
2 100 30
77
h
1
t
1
2
3
4
5
6
Dt
20 50 10 50 50 10
Qt
77
77
77
Setup
100
100
100
Holding
57 7 74 24 51
Total
7
20
8
9
40 20
77
100
41 21 58
10
30
38
Total
300
308
$400
$371
$771
t
1
2
Dt
20 50
Qt
80
Setup
100
Holding
60
Total
3
10
4
5
50 50
110
100
10 0 60
6
10
7
8
20 40
80
100
10 0 60
9
20
10
30
30
100
20 0
Total
300
308
$400
$220
$620
Nervousness
Item A (Leadtime = 2 weeks, Order Interval = 5 weeks)
Week
0
1
2
3
4
5
6
7
Gross Reqs
2
24
3
5
1
3
4
Sched Receipts
Proj Inventory
28
26
2
-1
-6
-7
-10 -14
Net Reqs
1
5
1
3
4
Planned Orders
14
50
8
50
-64
50
* Past Due
8
50
-63
50
Reducing Nervousness
Reduce Causes of Plan Changes:
Handling Change
Causes of Change:
Responses to Change:
Comparison:
Rescheduling
Top Down Planning: use MRP system with changes (e.g.,
altered MPS or scheduled receipts) to recompute plan
can lead to infeasibilities (exception codes)
Orlicky suggested using minimum leadtimes
bottom line is that MPS may be infeasible
Safety Leadtimes:
inflate production leadtimes in part record
used as hedge against time uncertainty (e.g.,
delivery delays)
2
400
500
100
4
200
5
800
100
-100
120
800
-900
800
120
1
20
40
20
2
40
50
30
3
20
4
0
5
30
10
10
-20
20
3
20
4
0
5
30
10
10
10
-20
30
50
Safety Stock = 20 units
Week
Gross Reqs
Sched Receipts
Proj Inventory
Net Reqs
Planned Orders
1
20
40
20
50
2
40
50
30
1
20
40
20
2
40
50
30
50
3
20
4
0
5
30
10
10
-20
20
Aggregate Production
Planning
Rough-cut Capacity
Planning
Master Production
Scheduling
Bills of
Material
Inventory
Status
Material Requirements
Planning
Job
Pool
Capacity Requirements
Planning
Job
Release
Routing
Data
Job
Dispatching
BPR
MRP
IT
MRP II
ERP
Goal: link information
across entire enterprise:
manufacturing
distribution
accounting
financial
personnel
integrated functionality
consistent user interfaces
integrated database
single vendor and contract
unified architecture
unified product support
Disadvantages:
incompatibility with existing systems
long and expensive implementation
incompatibility with existing management
practices
loss of flexibility to use tactical point
systems
long product development and
implementation cycles
long payback period
lack of technological innovation
Conclusions
Insight: distinction between independent and
dependent demands
Advantages:
General approach
Supports planning hierarchy (MRP II, ERP)
Problems:
Assumptions especially infinite capacity
Cultural factors e.g., data accuracy, training, etc.
Focus authority delegated to computer