15.9 Material Requirements Planning, Scheduling & Sequencing
Key Takeaways
- Scheduling and materials requirement planning are both named in the Production Planning and Control bullet of the CIL Mechanical Paper-II syllabus.
- MRP explodes the master production schedule through the bill of materials and offsets each requirement by its lead time to determine when orders must be released.
- MRP applies to dependent demand items whose requirements are calculated, whereas reorder-point inventory systems apply to independent demand items whose requirements are forecast.
- Johnson's rule sequences n jobs through two machines to minimise the total elapsed time by scheduling the shortest processing time first if it is on machine one and last if it is on machine two.
Dependent Versus Independent Demand
The single idea that justifies MRP is the distinction between two kinds of demand.
| Demand type | Character | Correct approach |
|---|---|---|
| Independent | Demand for a finished product, driven by the market | Forecast it; use reorder point and EOQ methods |
| Dependent | Demand for a component, driven entirely by the demand for its parent | Calculate it; use MRP |
If a shovel bucket needs six teeth, then the demand for teeth is not a matter for forecasting. It is arithmetic: six times the number of buckets. Applying reorder-point logic to dependent items produces the classic symptom of holding stock of every component while still being short of the one required.
Inputs to MRP
| Input | Content |
|---|---|
| Master Production Schedule (MPS) | What end items are to be made, in what quantity, in which period |
| Bill of Materials (BOM) | The product structure: which components go into which assemblies, and how many |
| Inventory Records | On-hand quantity, quantities already on order, lead times, lot sizing rules, safety stock |
The bill of materials is structured in levels, with the finished product at level 0, its major assemblies at level 1, their components at level 2, and so on. Where an item appears at more than one level, low-level coding assigns it the lowest level at which it occurs, so that all its requirements are accumulated before it is planned.
The MRP Logic
For each item, working down level by level:
- Gross requirements — the total quantity needed in each period, taken from the parent's planned order releases.
- Scheduled receipts — quantities already ordered and due to arrive.
- Projected on hand — the balance carried forward.
- Net requirements = Gross requirements minus scheduled receipts minus projected on hand available.
- Planned order receipts — when the net requirement must arrive, adjusted for lot sizing.
- Planned order releases — the receipt date offset backwards by the lead time.
The planned order releases at one level become the gross requirements at the next level down. This cascade is called the BOM explosion, and the backwards shift is lead time offsetting.
Worked example
A hydraulic cylinder assembly is required in quantity 100 in week 8. Each assembly uses 2 seal kits. Seal kits have a lead time of 3 weeks, 40 are in stock, and none are on order.
| Item | Value |
|---|---|
| Gross requirement for seal kits, week 8 | $100\times2 = 200$ |
| Less on hand | 40 |
| Net requirement | 160 |
| Planned order receipt | 160 in week 8 |
| Planned order release | 160 in week 5 (8 minus 3 weeks lead time) |
If the assembly's own lead time is 2 weeks, the seal kits are actually needed for assembly start in week 6, and the calculation would offset from there instead — a distinction that matters in practice and is a common source of error.
Lot Sizing Rules
| Rule | Method |
|---|---|
| Lot for lot | Order exactly the net requirement each period; minimum inventory, maximum number of setups |
| Fixed order quantity / EOQ | A standard quantity each time |
| Period order quantity | Cover a fixed number of periods |
| Least unit cost / part period balancing | Heuristics balancing setup against holding cost |
MRP Outputs and Extensions
Outputs include planned order releases, rescheduling notices for existing orders, cancellation notices, and exception reports where a requirement cannot be met.
| System | Scope |
|---|---|
| MRP | Material planning only |
| Closed-loop MRP | Adds capacity requirements planning and feedback from the shop floor |
| MRP II | Manufacturing Resource Planning; adds finance, marketing and engineering to a single plan |
| ERP | Enterprise Resource Planning; extends across the whole enterprise |
Limitations
MRP assumes fixed lead times independent of load, and infinite capacity unless capacity planning is added. Both assumptions fail in a congested shop, where lead time actually grows with queue length. It also depends critically on data accuracy: an inventory record error or an out-of-date bill of materials propagates through every dependent item. The commonly quoted requirement is inventory accuracy above 95% and bill of materials accuracy above 98% before MRP is worth implementing at all.
Scheduling and Sequencing
Scheduling assigns start and finish times to operations. Sequencing decides the order in which jobs waiting at a machine are processed. The two are related but distinct.
Key measures
| Measure | Definition |
|---|---|
| Flow time | Time a job spends in the system: completion time minus arrival time |
| Makespan | Total elapsed time to complete all jobs |
| Lateness | Completion time minus due date; may be negative |
| Tardiness | Lateness if positive, otherwise zero |
| Utilisation | Productive time as a fraction of available time |
Priority Sequencing Rules
| Rule | Basis | Minimises |
|---|---|---|
| SPT Shortest Processing Time | Shortest job first | Average flow time and average number of jobs in system; provably optimal for a single machine |
| EDD Earliest Due Date | Nearest due date first | Maximum lateness |
| FCFS First Come First Served | Arrival order | Nothing in particular; but is perceived as fair |
| LPT Longest Processing Time | Longest job first | Useful for balancing parallel machines |
| CR Critical Ratio | (Due date minus now) divided by remaining processing time | Responsive to due dates; ratio below 1 means the job is behind |
| Slack per operation | Slack divided by remaining operations | Balances urgency across routings |
Two results are worth memorising because they are provable and frequently examined:
- SPT minimises mean flow time on a single machine. Its weakness is that long jobs may be indefinitely postponed.
- EDD minimises maximum lateness on a single machine.
Note that SPT does not minimise the number of tardy jobs — that requires Moore's algorithm — and EDD does not minimise average lateness.
Johnson's Rule: Two Machines, n Jobs
For $n$ jobs that must pass through two machines in the same order, Johnson's rule finds the sequence that minimises makespan.
Procedure
- List the processing times of every job on both machines.
- Find the smallest processing time in the whole table.
- If it lies on Machine 1, schedule that job as early as possible (leftmost free position). If it lies on Machine 2, schedule it as late as possible (rightmost free position).
- Delete that job and repeat until every position is filled.
- Break ties arbitrarily; the makespan is unaffected.
Worked example
Five jobs must be turned then milled:
| Job | Turning (M1) | Milling (M2) |
|---|---|---|
| A | 5 | 2 |
| B | 1 | 6 |
| C | 9 | 7 |
| D | 3 | 8 |
| E | 10 | 4 |
Smallest overall is 1 (job B on M1) so B goes first. Next smallest is 2 (job A on M2) so A goes last. Next is 3 (job D on M1) so D goes second. Next is 4 (job E on M2) so E goes second-last. C takes the remaining middle slot.
Computing the makespan:
| Job | M1 in | M1 out | M2 in | M2 out |
|---|---|---|---|---|
| B | 0 | 1 | 1 | 7 |
| D | 1 | 4 | 7 | 15 |
| C | 4 | 13 | 15 | 22 |
| E | 13 | 23 | 23 | 27 |
| A | 23 | 28 | 28 | 30 |
The makespan is 30, and machine 2 idle time totals 1 unit at the start plus 1 unit between C and E.
Extension to Three Machines
Johnson's rule extends to three machines only if at least one of the following holds:
That is, the middle machine must be dominated. When the condition holds, form two pseudo-machines:
and apply the two-machine rule to $G$ and $H$. If the condition fails, no simple optimal rule exists and heuristics or enumeration must be used.
Gantt Charts and Loading
The Gantt chart remains the standard visual scheduling tool, plotting machines or jobs against time as horizontal bars. A load chart shows the workload assigned to each machine against its available capacity, immediately revealing bottlenecks.
Finite loading respects capacity limits and schedules accordingly; infinite loading assigns work regardless of capacity and leaves overloads visible for the planner to resolve. Standard MRP uses infinite loading, which is precisely why capacity requirements planning has to be bolted on to make closed-loop MRP work.
Application to a coal workshop
In a subsidiary's central repair workshop, the mix is characteristically high variety and low volume, with urgent breakdown work interrupting planned overhauls. In that setting, pure SPT would starve the large overhauls indefinitely, while pure FCFS would delay urgent breakdowns. Practice generally uses a critical ratio or slack-based rule, which keeps due dates in view while remaining responsive, with genuine breakdown work given a separate expedite priority.
Material requirements planning is the appropriate method for items with:
In MRP, the planned order release date is obtained from the planned order receipt date by:
On a single machine, the shortest processing time rule is known to minimise:
Under Johnson's rule for two machines, if the smallest processing time in the table occurs on the second machine, that job is scheduled: