Time with no orders stays out of OEE when the line was not scheduled to run, so it costs no availability, though it still shows up in TEEP and loading. The test is simple: if the plan had product to run in that time and the line did not run it, the time is a loss.
The rule in one question
Ask this: did the plan have product scheduled for this time? If not, the time is excluded, and if so, a gap is a loss whatever caused it.
This follows the time model in Overall Equipment Effectiveness (R. C. Hansen, 2001), which leaves these outside OEE as excluded time:
- time with no product scheduled
- weekends and holidays
- shutdowns planned well ahead
The reason is what OEE is for. It judges how well a line ran when it was asked to run, and a line cannot be good or bad at making orders that do not exist.
A real shift, counted two ways
Example: a shift is staffed for 480 minutes. The only order on the plan finishes at minute 360, and the line then sits idle.
In those 360 minutes the line made 300 minutes' worth of good output at its ideal rate.
The second row is right. If the first were used, a crew that finished early would be punished for it, and they would learn to run slower.
The principle is that good performance must never hurt OEE. Finishing early belongs in excluded time, as OEE calculation mistakes also notes.
Sort every case
"No orders" covers several different situations on the floor. Only some of them leave OEE.
| Situation | In OEE? | Why |
|---|---|---|
| Nothing on the plan for this shift | Excluded | Not scheduled to run |
| Order done early, nothing planned next | Excluded | Good work must not hurt OEE |
| Product scheduled, material late | Loss | The plan had work |
| Next order planned, not released in time | Loss | The plan had work, and the delay was ours |
| Order cancelled on the day | Loss, then excluded | Practice varies; see below |
| Running for stock | Normal OEE | Scheduled, so it counts in full |
Late material is easy to code wrongly, because the line looks idle. Waiting for material shows how to log it.
The cancelled order is where honest plants differ, and we know of no rule that settles it. Some exclude the time from the moment the order is cancelled.
Our advice: count the time as a stop until a named planner changes the plan and logs the time, then exclude what is left.
That gives a small cost to late changes, and it stops the shift from excluding its own stops after the fact. Whatever you choose, write it down and use the same rule on every line.
Where idle time goes instead
Excluded does not mean invisible. It still needs a code and a place in a report, because idle capacity is a business fact.
Example: a line has 2,400 staffed minutes a week and holds 70% OEE in both weeks below. Only the time excluded for no orders is different.
| Week A | Week B | |
|---|---|---|
| No-order minutes | 120 | 720 |
| Scheduled minutes | 2,280 | 1,680 |
| OEE | 70% | 70% |
| Good minutes | 1,596 | 1,176 |
| Good minutes ÷ 2,400 staffed | 66.5% | 49.0% |
| TEEP: good minutes ÷ 10,080 calendar | 15.8% | 11.7% |
TEEP is measured against all calendar time, so no-order time counts against it in full, along with every other hour the line stands. That is why the two weeks read the same on OEE and differ on TEEP.
So put no-order hours beside OEE on the same page. The TEEP calculator folds them into one number, and OEE vs TEEP explains which number suits which decision.
Low demand is a sales or planning question. Keep it out of the line's score, and take it to the people who can act on it, with the hours written down.
Stop the code from becoming a hiding place
Any code that removes time from OEE will get used too often. That is how a line reports 80% while shipping less each month.
If it was not on the plan before the time began, it is a stop until someone changes the plan.
A planner or supervisor sets the code. The crew tagging its own stops should not.
Gaps of a few minutes between orders stay as stops. Our suggestion: 30 minutes or more to exclude.
Report no-order minutes as a share of staffed time. A sudden rise needs an explanation.
Automatic monitoring needs help here. A sensor sees a stopped machine and cannot tell whether anyone wanted it to run, so the shift calendar or plan must supply that fact.
Give no-demand its own entry in your reason codes, and report it apart from planned and unplanned stops.
How to record it on a shift sheet
Keep one line per shift that adds up, so nobody can lose time between the columns. Staffed time = scheduled time + excluded time, and every excluded minute carries a code.
Set the scheduled figure when the plan changes, not at the end of the shift. A figure chosen after the shift is over can be made to give any score you like.
What not to do
- Do not run product nobody ordered to keep OEE and the crew busy. The score rises and you pay for stock, one of the 8 wastes of lean.
- Do not stretch the run. Slowing down to fill the shift is a speed loss in OEE, and it hides how much spare time you really have.
- Do not lump all idle time together. Late material and no orders have different owners.
- Do not leave crews idle by default. Planned training, cleaning or changeover practice is a better use of the time, and it stays excluded when planned ahead.
If the idle time follows a season, OEE and seasonal demand shows how to plan around it. For the day-to-day logging itself, see how to track downtime.
Telling a no-order gap from a real stop takes a live record of every stop and its cause. Fabrico takes stops live 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. See how Fabrico tracks stops.
What people ask next
Does idle time count as downtime in OEE?
It depends on the plan. Idle time with nothing scheduled is excluded and is not downtime for OEE, but idle time with product on the plan is. Planned vs unplanned downtime sorts the other stop types.
Should I still track time with no orders?
Yes, with its own code. It belongs in loading and TEEP, where it shows unused capacity. Try the machine utilization calculator to size it.
What about a line waiting for the next order to be released?
If that order was planned for now, the wait is a stop and counts against availability. Treat it like other induced stops, as in blocked and starved.
Can a crew's OEE rise just because orders fell?
Fewer hours do not raise OEE by themselves. It can rise if the weak hours go first, such as hard products or short runs, so compare the loss split as well. OEE and seasonal demand shows how.
Should paid idle labour count anywhere?
Yes, though not in OEE. It belongs in a labour measure such as overall labor effectiveness, or in OOE if you measure against staffed time.
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 · Does Planned Maintenance Count in OEE or TEEP? · Why OEE Drops After You Add a New Machine