If the line is planned to stop for a break, with no relief crew, the break comes off scheduled time and does not lower OEE. If the line runs through the break or was meant to, those minutes stay in, and any stop in them is a loss. Practice varies between plants, so write your rule down and use it on every line.
The question that settles most arguments
Ask one thing: did the plan say this line would make product during those minutes? The answer decides everything, and the break itself is not the point.
In Overall Equipment Effectiveness (R. C. Hansen, 2001), time planned as not for production is excluded time. A planned break with no relief crew fits that box, though practice does vary, so we cover the other view further down.
The picture below shows the same 8-hour shift on two lines. One stops for its breaks, and the other keeps running with relief people.
Every break situation, and where it goes
| What happens | Where it goes |
|---|---|
| Line stops for a planned break, no relief planned | Excluded time. Not in OEE |
| Relief crew keeps the line running | Scheduled, normal run time |
| Relief was planned, but nobody came | Stop, no people (ST Induced) |
| Break runs 10 minutes over | 10-minute stop, no people (ST Induced) |
| Line stops 5 minutes early to clean up for the break | 5-minute stop, unless the plan includes it |
| One of three operators is away, so the line runs slower | Speed loss, in performance |
| Automatic machine runs alone, and faults during the break | Scheduled. The wait until someone returns is a stop |
A worked example with real effects
Example: a filling line has a 480-minute shift with 60 minutes of breaks. It has an ideal rate of 30 units per minute, 42 minutes of other stops, 10,200 units made and 9,900 good.
The good units are worth 9,900 ÷ 30 = 330 minutes at the ideal rate. Everything now depends on what you divide that by.
Take the first two bars. Nothing changed on the floor, yet the second reading is almost 10 points lower, so a comparison between plants with different rules means very little.
Now the third bar. A relief crew runs 438 minutes at the same pace and makes 11,819 units, with 11,471 good, which is 16% more good product.
OEE hardly moved, because OEE judges how well you use the time you planned. The extra output shows up on the shipping dock and in TEEP, which measures against all time.
Against the full 480-minute shift, good minutes go from 68.8% to 79.7%.
Staffed lines vs stopped lines
A line that stops for breaks has a fair OEE, but it may hide capacity. If a plant is sold out, those 60 minutes per shift are worth a look even though OEE never shows them.
A line that runs through breaks needs the break plan on the shop floor to be real. Every relief that is late is a loss in scheduled time, and it belongs in your reason codes as no people.
When you need the people side of the picture, track overall labor effectiveness beside OEE. Long stops of this kind are covered in waiting for operator downtime.
Break creep: the loss that hides in plain sight
The plan says 60 minutes of breaks. The machine records show 78, because people stop a little early and restart a little late.
Only the planned 60 are excluded. The extra 18 minutes are a stop, and in the example that is 18 ÷ 420 = 4.3 points of availability on every shift.
Look at the first minutes after each restart too, since slow starts after breaks repeat many times a week. First hour of shift losses and end of shift losses show the same pattern at the edges of a shift.
The other view: keep breaks in the denominator
Some plants leave breaks inside planned time on purpose. Their reasoning is that a stopped line during a break is real lost capacity, and they want the pressure to staff relief.
That number is closer to a staffed-time measure, and it is a fair thing to track. We would call it what it is and keep it apart from OEE, as OEE vs TEEP vs OOE explains.
Whichever you pick, write it down and apply it to every line. A rule that varies by plant makes the numbers useless for comparison.
How to set this up on the floor
- Write a shift pattern for each line. Start, end, each break, and whether relief is planned.
- Use the pattern as the schedule. Excluded minutes come from the plan and never from what happened on the day.
- Keep the real times. Compare the machine's stop and restart with the plan each week to catch creep.
- Treat changes as changes. If the plan moves to staggered breaks, the scheduled time goes up from that date.
If shift length is the issue, see OEE on 12-hour shifts. For a quick check of the sum, use the OEE calculator with the scheduled minutes from your pattern.
Where plants slip up
- Excluding a break after the fact because the line happened to be quiet.
- Excluding breaks while the line kept running, which can push readings over 100%. See OEE over 100 percent.
- Excluding one shift's breaks and not another's, which is a common cause of OEE gaps between shifts.
- Comparing OEE across plants without asking how each one treats breaks.
Break creep only shows when the real stop and restart times are recorded. Fabrico takes stops live from the machine, and operators tag the cause at the line, so a late restart is a tagged minute in OEE per line and shift. See how Fabrico tracks stops.
What people ask next
Is lunch part of planned production time?
Not if the line is planned to stop for lunch with no relief crew. Then lunch is excluded, and planned production time is the rest of the shift. If people cover and the line runs, lunch stays in.
Do breaks count as downtime?
A planned break on a stopped line is not downtime in OEE, because it is outside scheduled time. An overrun, or a break that stops a line planned to run, is a stop. See planned vs unplanned downtime.
What about meetings and team huddles?
Use the same test. A planned meeting with the line stopped is excluded time, while an unplanned one stops a scheduled line and counts as a loss.
Does excluding breaks make OEE look better than it is?
It gives a higher number than leaving them in, but it is still fair if the stop was really planned. The capacity question moves to TEEP, which counts all time. The TEEP calculator shows the difference.
How do I count breaks on a machine that runs by itself?
If it is planned to run alone, those minutes are scheduled time. A fault that waits for someone to come back is a stop, however long the wait, so unattended running only helps if the machine really keeps going.
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.
Related guides: OEE vs OOE: The Difference and When to Use Each · Units Per Labor Hour: Formula and Use With OEE · OEE in a Labor Shortage: How to Count Short Crews · Machine Downtime Categories for OEE Reporting