sailing Foudra MRP
Reference manual chevron_rightmanual/introduction

1. What MRP II is, and what this system is

The problem

You make things out of other things. A bicycle is a frame, two wheels, a drivetrain, brakes, a cockpit; a wheel is a hub, a rim, thirty-two spokes and a tyre; a frame is tube, dropouts, paint. Some of those you buy, some you make, and every one of them has to be there — in the right quantity, at the right time — or the bicycle does not get built. Six hulls in the warehouse and no rudder bushings is not a bicycle problem, but it is exactly this problem.

The naive answer is to keep plenty of everything. That ties up money, fills shelves, and still fails, because "plenty" is a guess and the one part you run out of is the one you didn't guess about.

Material Requirements Planning

MRP is the calculation that replaces the guess. It was worked out in the 1960s on early IBM computers, written up by Joseph Orlicky in Material Requirements Planning (1975), and spread through the 1970s by APICS as something of a crusade. Its central insight is a distinction:

Decide to build six bikes in March and you know you need twelve wheels, three hundred and eighty-four spokes, six frames, and so on down every level of every bill of materials. That is the explosion. Subtract what is on hand and what is already on order, and you have net requirements. Push each requirement back by its lead time — spokes take thirty days from Switzerland, so the order must go in early February — and you have a plan of when to order and when to start making. Run that every week as reality changes, and you have MRP.

Three inputs, in Orlicky's words:

  1. The master production schedule — what you intend to make, and when.
  2. The bill of materials — what everything is made of, level by level.
  3. Inventory records — what you have and what is coming.

And one hard truth that the MRP literature repeats until it is tedious: the calculation is only as good as the records. A bill of materials that is 90% right and stock counts that are 90% right produce a plan that is wrong somewhere in nearly every product. The practitioners of the 1970s learned to insist on record accuracy above 95%, kept honest by cycle counting — counting a few locations every day rather than everything once a year. This system takes the same view: the stock ledger is never edited, only added to, and the reconcile tool exists to prove the cached totals against it.

MRP II

By 1980 the calculation had grown a company around it, and Oliver Wight coined Manufacturing Resource Planning — MRP II — for the result. The original MRP plans materials and quietly assumes infinite capacity: it will happily schedule forty wheels on Tuesday whether or not anyone can build them. MRP II closes that loop:

Later the same idea, extended to everything a company does, was renamed ERP by Gartner in 1990. That is the world of SAP and Oracle; it is not where this system is going.

People say "MRP" for both disciplines, and it causes confusion. In Foudra, MRP always means MRP II: materials, capacity, the shop floor and purchasing planned together, not the materials calculation on its own.

What this system is

Foudra is an MRP II system for small manufacturers: the materials calculation, closed into a loop with capacity, the shop floor, purchasing and costing, on one set of records.

MRP II element Here
Master production schedule Demand: customer orders and forecasts, each a part, a quantity and a due date
Item master Parts, with versions as separate rows so history never changes meaning
Inventory records The stock ledger and its per-location totals
Bills of materials BOMs, multi-level, with phantoms and reference designators
Material requirements planning The planning run, nightly or on demand: explosion, netting against stock and open orders, lot sizing, lead-time offsetting, proposals to make or buy
Routings and work centres Routings with setup and run times, workstation groups and stations
Capacity Working hours for the company and each station, closures, and the capacity chart that books open and proposed work into them and shows what will finish late
Shop floor control Work orders with per-step backflushing, and station status for people and machines
Purchasing Suppliers, sourcing, purchase orders with receiving into the ledger
Standard costing standard_cost on the part, separate from what any order actually paid, and stock valued at it

The plan works both ways. Backwards from what is needed and when, it says what to start and when to start it. Forwards from today, through purchase orders' expected dates, routing times and the hours each workstation actually has, it predicts when each order will really be ready, and says why when that is later than needed: a late delivery, or a group of workstations already full.

Alongside the plan sits the older, simpler logic most small manufacturers actually run on: a reorder point per part, the stock you always keep. The planning run honours it at every level, so you can use dated demand for what is promised and reorder points for what is routine.

The MRP II idea a small shop uses most is the simplest: buildable quantity with its binding constraint, how many of something you could assemble from the shelf right now, and which component stops you making more. That is the explosion, run backwards, for today.

Words that matter here

A handful of terms the rest of the manual uses without explanation:

On to setting up.