Blog / Downtime
Downtime · Guide

Waiting for Material Downtime: Log and Cut It

OL By OEE Lab Editorial |Updated 2 November 2026 |7 min read
Short answer

Waiting for material downtime is time a line is scheduled to run but stands still because parts, packaging or raw material are not at the line. Log the missing item with one of four sub-codes, count the minutes as an availability loss in OEE, and start with shortages where the stock is already inside the building.

What counts as waiting for material

Use a simple test: the machine is ready, the crew is ready, and the material is not where it needs to be. If all three are true, the reason is waiting for material.

Three look-alikes need their own codes, because the owner of the fix is different.

  • No orders. Nothing was scheduled, so the time sits outside OEE. See OEE with no orders.
  • Starved by the machine before it. The material exists, but the upstream machine stopped feeding. That is a starved state, a line event.
  • Bad material at the line. It arrived but fails a check. Use the sub-code below, and open a quality hold if your site requires one.

Yes, it counts against OEE

The line was planned to run, so every minute of the wait is an availability loss. That follows the standard time model in Overall Equipment Effectiveness (R. C. Hansen, 2001), and the six big losses page shows the wider picture.

Do not move these minutes out of planned time to protect the score. The line had an order and a crew, and the customer still waited.

Practice does vary here. Some sites add a second score with outside waits removed, to show what the line itself controls, and that works if the standard OEE stays on the board and the second number is clearly labelled.

Availability = run time / planned production time
No material wait: (480 - 40) / 480 = 91.7%
With 62 min wait: (480 - 40 - 62) / 480 = 78.8%
Hypothetical line. The 62-minute wait takes 12.9 points off availability in one shift.

How to log it so the data is useful

A log entry that only says "no material" can start an argument, but it cannot start a fix. Capture five fields each time.

  • Start and end time of the stop, taken from the machine if you can.
  • Line and order number.
  • The item missing, by part number or a short name.
  • The sub-code from the table below.
  • When the shortage was reported, and to whom.

The last field shows how long the call took to reach someone who could act. Add these to your downtime log and follow the wider rules for building reason codes.

Sub-codeWhat happenedWho owns the fix
Not in plantSupplier late, or the order was placed too latePurchasing
In plant, not at lineStock exists, but no one brought itInternal logistics
Wrong or unusableWrong label, wrong batch, damaged palletWarehouse and quality
Plan changedJob moved up with no material checkPlanning
Four sub-codes are enough. Each one points to a different person.

One week of shortages on a packing line

Example: a packing line logs 310 minutes of waiting for material in a week. The plant first blames the supplier, so it sorts the minutes by sub-code.

In plant, not at line168 min
Wrong or unusable62 min
Not in plant50 min
Plan changed30 min
Hypothetical week. More than half of the wait had stock on site.

Only 50 of the 310 minutes point at the supplier. The biggest bar is a trip of a few hundred metres inside the building, so the first project needs no supplier meeting.

Put the result on a Pareto chart each week and let it choose the next project. Run the downtime cost calculator on the top bar, because a cost figure helps when you ask for a forklift route change.

How to cut each type

In plant, not at line

Call for material on a time basis, using the longest delivery time you actually see. Example: the line uses one pallet every 40 minutes and a delivery can take 25, so call with 35 minutes of stock left, which adds a 10-minute margin.

Mark that point on the floor or on the pallet stack. An operator should be able to see it from the machine without doing any sums.

Wrong or unusable

Check the next job's kit before the job starts, while there is time to swap it. A check at the end of the previous job costs a minute or two, against a stopped line later.

Not in plant

Give purchasing the item, the dates and the lost minutes for the past month. A short list of repeat items makes a much better conversation than a general complaint about shortages.

Plan changed

Add one rule: no job joins the schedule until its material is confirmed. Then keep the next few hours frozen, so the warehouse picks for the plan the line will really run.

A short interval control check every hour or two will catch the remaining surprises while there is still time to react.

When the line is already waiting

Everything above prevents the next shortage, but today's still needs a decision. The team lead can settle it in three questions.

  1. How long until it arrives? Get a time from the person who has the item, and write it next to the stop.
  2. Can a checked substitute run? Only use one that quality or engineering has already approved for this product.
  3. Is the wait longer than a job change? If so, run a job that has its material, and log the changeover with the shortage as its cause.

Example: a job change takes 25 minutes and the pallet is 90 minutes away, so switching saves about an hour of output. If the pallet is 20 minutes away, stay and use the crew for cleaning or the next kit check.

Shortages that hide in other numbers

Crews are good at keeping a line moving when material runs low, and that can hide the problem from your log. Look for three signs.

  • Stretching. The operator slows the line to make the last pallet last. The loss appears as speed loss, with no stop at all.
  • Early changeovers. The crew changes to another job because the current one has run out. The downtime gets logged as a changeover.
  • Moved crews. People go to another line while they wait. The stop then gets logged as no operator, or with no reason at all.

To check, compare the log with the planned job sequence for one week. Any job that ended before its planned quantity needs an explanation.

Why shortages keep coming back

  • One code for everything. A single "material" code hides the four different owners.
  • Logging at shift end. The missing item is forgotten by then. Tag it at the line, as described in operator downtime logging.
  • Treating it as outside the operators' scope, then ignoring it. Nobody on the line caused it, so it needs a named owner in logistics or planning.
  • Adding stock everywhere. More inventory may cover the symptom, yet the delivery fault stays and the floor space goes.

Your first five days

Add the four sub-codes and start logging the missing item today. After five working days, sort the minutes by sub-code and pick one item from the top bar.

If shortages keep repeating across several lines, draw the flow with a value stream map. It shows where material waits while your line waits for it.

See it live in Fabrico

A material shortage is easy to log when the stop is already on screen. Fabrico takes the stop live from the machine, and the operator tags the cause at the line, so the minutes sit in OEE per line and shift. See how Fabrico tracks stops.

What people ask next

Is waiting for material planned or unplanned downtime?

Unplanned, unless the wait was on the schedule before the shift began. The line had an order and a crew, so it counts against availability. See planned vs unplanned downtime for the full test.

Should waiting for material count against OEE if it is not the line's fault?

Yes. OEE measures what the line did with planned time, and it does not assign fault. Use reason codes to show the owner, and keep the minutes in the calculation.

What is the difference between starved and waiting for material?

Starved describes the machine state: nothing is arriving at the infeed. Waiting for material is one cause of that state, when the supply itself has run out. Blocked and starved shows how to separate them in your data.

How much material buffer should a line hold?

Enough to cover your longest usual delivery time plus a small margin, measured in minutes of running. Example: with a 25-minute delivery and a 10-minute margin, call with 35 minutes left. Measure the delivery time for a week before you choose.

Who should log a material shortage?

The operator at the line, because that person sees which item is missing. Keep it to one or two taps, or a single line on paper. Operator downtime logging has the rules that keep this honest.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

Related guides: OEE in a Labor Shortage: How to Count Short Crews · MES vs WMS: Line, Warehouse and the Handoff

← More OEE Lab guides · Waiting for operator downtime →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES