A nightly material requirements planning run will report that every line is covered while the shop floor is short of three parts. The arithmetic is usually right. What went in was not: a bill of material that no longer matches the revision being built, a lead time typed in two years ago, or a quantity that ignores the multiple the part actually ships in.
The run is a calculator, not a check: its output is only as good as the records feeding it.
Why the MRP run and the shop floor disagree
Two revisions of the same assembly can be open at once. The engineering change is released, the new BOM is loaded, and the older work orders still carry the older part list because they were released before the change. The run nets against whatever is attached to each work order, so the same part number is both over-ordered for one build and missing for another.
Lead time offsets drift quietly. A part quoted at twelve weeks two years ago may now run at twenty six, and the planner only finds out when the purchase order comes back with a ship date in a later quarter. Until that happens the system plans a release date that no supplier can meet.
Pack multiples break the shortage list. A calculation for 2,400 pieces against a reel of 3,000 shows a shortage of 600 that will never be bought, while a genuine gap of 200 pieces hides inside the same rounding. Planners learn to distrust the list, and once they distrust it they stop reading the exception messages that matter.
The inputs that decide whether the run is worth reading
Seven fields carry almost all of the risk. Each one is cheap to hold and expensive to leave stale.
| Input | How it usually fails | What it does to the plan |
|---|---|---|
| BOM revision and effectivity date | Change released, work orders left on the old list | Splits demand across two parts and covers neither |
| Quoted lead time against history | Field updated once at setup and never again | Release date lands after the date the line needs material |
| Minimum order and pack multiple | Not carried at all, so every figure is theoretical | Shortages that cannot be bought, and buys nobody planned |
| On-hand by location | Stock in inspection or kitting counted as free | Netting against material that is not available to issue |
| Scrap and attrition rate | Flat two percent for every part class | Fine pitch and small chip parts run short late in the build |
| Shelf life and storage class | Held as a note in a spreadsheet | Plans a buy that expires before the build consumes it |
| Approved alternates | Known to the buyer, unknown to the system | Expedites a part when a released equivalent was already on the shelf |
Only the first of the seven is normally maintained by planning. The rest sit with purchasing, quality and the customer, which is why the run degrades whenever a handover drops.
What a planner does with the exception messages
Each message type asks a different question.
| Message | What to verify first | Decision it leads to |
|---|---|---|
| Expedite | Is the need date real, or pulled in by a forecast nobody confirmed | Pay for speed, or move the build |
| De-expedite | Will the material still be inside its shelf life on the new date | Push the receipt out, or hold and consume first |
| Cancel | Is the order cancellable without a charge, and is the part common to another program | Cancel, or keep as shared buffer |
| Release | Does a released alternate exist before the order goes out | Buy the approved equivalent instead |
| Past due | Has the supplier acknowledged a date, or only received the order | Chase a confirmed ship date, not an order number |
Acknowledgement and confirmation are different states. An order that has been received has a place in the system and no material behind it, and the difference is exactly the two weeks that turns a covered line into a stopped one.
How SUPERB PCBA supports an MRP-driven build
Before a BOM is loaded, the lines are checked against what the package and the maker data actually say: part number, package, tolerance, temperature grade and the revision printed on the drawing. Rows that disagree are queried rather than silently substituted, because a part that reaches the line under the wrong description is a defect no inspection step can catch later.
Material is counted by X-ray against the reel or tray rather than trusted by label, and quantity is reconciled before the shortage report is issued. Parts with a shelf life carry a date code and a storage class in the record, so the plan can see a buy that would expire before the build consumes it. Moisture sensitive parts are baked at 125 C to J-STD-033 and held under ESD S20.20 in an SMT area at ISO 8, 22 plus or minus 3 C and 45 to 65 percent relative humidity.
The assembly side runs seven SMT lines with 01005 placement, 3D SPI, 3D AOI, X-ray at IPC-7095 with voiding under five percent, and a seventeen step flow with ten QC stations under IPC-A-610 Class 2 and Class 3, ISO 9001 and ISO 13485. Material is warranted for 730 days, and a pin-to-pin alternate is only used with written customer approval.
Effectivity, phantoms and the scrap allowance
Effectivity dates are the most common source of phantom demand. A change with a date in the future still needs the old part for builds released before that date, and a run that only reads the current BOM will stop buying it too early.
A phantom level that is never stocked still explodes into real parts, and if it is carried as a stocked item the run buys a level no build consumes.
Attrition belongs to the part class and the process: two percent is reasonable for a 0603 resistor and poor for a 0.4 mm pitch BGA reflowed twice.
Material requirements planning questions
How often should lead times be refreshed?
At the point an order is placed and again when the ship date is confirmed, because the confirmed date is the only figure that reflects the current market. The pages linked under component lead time solutions set out what to do once a figure has moved.
Should the buffer live in the BOM or in safety stock?
Attrition belongs in the BOM as a scrap allowance, because it is consumed by the process. Variability in demand and supply belongs in stock, where it can be reviewed and released.
What happens when the run cannot be satisfied at all?
That is a shortage, not a planning problem, and it moves to recovery: see BOM shortage recovery for the sequence from confirmed gap to released alternate.
Next step
Send the BOM with the revision and effectivity date, the build schedule, and whatever lead times you are currently planning against. The reply returns a scrubbed BOM with the rows that disagree flagged, a shortage view at the pack multiple, and the parts where an approved alternate would remove the risk. For the procurement side of the same work, see one stop BOM sourcing and kitting service.