Planned production time is the time you scheduled a machine to make product, after subtracting planned non-production events such as breaks, scheduled maintenance, and periods with no demand. It is the denominator of the OEE calculation the clock every OEE factor is measured against, and the number that decides how honest the whole score is.
Most arguments about OEE are really arguments about this one number. Two plants can log identical downtime and identical output and report OEE ten points apart, purely because they drew the top of the time model in different places. This guide defines planned production time inside the OEE time model, lists exactly what belongs in it and what doesn't, and explains why the “no demand” exclusion is the lever most likely to make a bad line look good. If you want the arithmetic done for you, the free OEE calculator uses this exact denominator.
What is planned production time in OEE?
Planned production time is scheduled time minus planned non-production events. In the vocabulary of the international standard for manufacturing KPIs, ISO 22400-2, this is the planned busy time (PBT): the time the production unit is planned to produce. It is also the number older TPM texts call loading time. Whatever you call it, it is the same idea, the window in which you intended the equipment to run and expected it to make good parts.
Everything in OEE hangs off it. Availability is run time divided by planned production time. Performance and Quality trim what is left. The equivalent single-line form of OEE, good units × ideal cycle time, all divided by planned production time, makes it explicit: this number is the denominator of the entire metric. Move it, and OEE moves without anything changing on the floor.
What belongs in planned production time and what doesn't?
What belongs is any time you intended to produce; what doesn't is time you deliberately set aside. The line between the two is where discipline lives. The table below sorts the common cases the way ISO 22400 and classic TPM would.
| Event | In planned production time? | Why |
|---|---|---|
| Running production | Yes | The core of the window |
| Unplanned breakdowns | Yes | Time you meant to run, counts as availability loss |
| Changeovers / setup | Yes | Planned to produce, didn't, an availability loss, not an exclusion |
| Minor stops and slow cycles | Yes | Loss inside run time, caught by Performance |
| Scheduled breaks & meetings | No | Planned non-production |
| Planned maintenance window | No (usually) | Deliberately not producing, but see the caveat below |
| Unscheduled shift (dark plant) | No | Removed one cut earlier, at scheduled time |
| No orders / no demand | No (conventionally) | The most abused exclusion, see below |
The changeover row is the one plants get wrong most often. A setup is not an exclusion; it is time the line was scheduled to make product and instead spent switching over. It stays inside planned production time and shows up as an availability loss, one of the six big losses and it belongs in the downtime log, not among the exclusions. Handling the maintenance and no-demand rows correctly is the subject of the rest of this post and of the companion piece on planned downtime in OEE.
Why is the “no demand” exclusion the most abused lever?
Because it is the one exclusion that lets you raise OEE without touching the equipment. Every other honest improvement, fewer breakdowns, faster changeovers, less scrap, requires the floor to actually change. Shrinking planned production time does not. Pull two idle, no-order hours out of the denominator and Availability jumps, OEE climbs, and not a single additional unit ships.
Here is the mechanism in numbers. A shift plans 450 minutes of production, loses 63 minutes to downtime, and runs 387, Availability of 86.0%. Now suppose 90 of those minutes had no orders behind them and get excluded as “no demand.” The denominator falls to 360, the same run time now covers less lost time, and Availability reads higher. The line did exactly the same work. The score went up. That is the trap.
The conventional rule keeps you honest: OEE measures how well you used the time you planned to produce and no-demand time is time you planned not to produce, so it comes out at the scheduled-time cut, one step above planned production time, not quietly out of the denominator afterward. The metric built to catch this game is TEEP, which refuses every exclusion and grades against all calendar time. If your OEE is strong but your TEEP is weak the gap is usually unsold capacity, and no amount of denominator-trimming makes that capacity productive.
Does planned maintenance always come out of the denominator?
Traditionally yes, but this is a genuine judgment call rather than a rule handed down from a standard. Seiichi Nakajima's original TPM framing kept planned maintenance and planned changeovers out of loading time, treating maintenance as time you chose not to produce. Many modern shops disagree on maintenance: if a machine is down for scheduled PM during a window you would otherwise have been running orders, that lost output is real, and burying it as an exclusion hides an availability problem TPM is supposed to attack.
The workable answer is to decide once, write it down, and apply it everywhere. Whichever convention you pick, the two failure modes are the same: never let the same event be an exclusion in one report and a loss in another, and never quietly reclassify a bad month's breakdowns as “planned” maintenance. Consistency beats theoretical purity. A denominator you can defend to a skeptical operations review is worth more than one that is technically ideal and privately negotiable.
How do you set planned production time step by step?
Fix it once per line, in writing, and change it only through a documented review. The sequence:
- Start from scheduled time, not calendar time. Decide which shifts the line is actually staffed and intended to run. Shifts you never schedule are removed here, one cut above the OEE denominator.
- List every recurring planned non-production event. Breaks, shift meetings, sanitation windows, and, if your convention excludes it, planned maintenance. Put the list on paper with durations.
- Decide the no-demand rule explicitly. State whether no-order time is removed at scheduled time or kept in and reported separately. The one thing you must not do is remove it silently from the OEE denominator.
- Write the exclusion rules into a one-page definition. Anyone should be able to reconstruct planned production time for any shift from this page alone. Ambiguity here is where OEE numbers quietly diverge.
- Apply the same rules to every line and every shift. A denominator that varies by supervisor makes cross-line comparison meaningless, the classic reason a plant roll-up misleads, covered in plant-wide OEE vs machine OEE.
- Re-check the definition whenever the schedule changes. Adding a shift, moving sanitation, or taking on seasonal demand all shift the boundaries. Update the page, don't improvise at month-end.
How is planned production time different from TEEP's clock?
They start from different places on purpose. Planned production time removes both unscheduled shifts and planned non-production before the clock starts, so OEE answers a narrow question: of the time you meant to run, how much was truly productive? TEEP (Total Effective Equipment Performance) removes nothing, it grades against all calendar hours and asks how much of your total capacity you converted to good product.
Neither clock is more correct; they answer different questions. OEE is the operator-and-maintenance scoreboard for the running window. TEEP is the capital-and-capacity number for the plant. The danger is mixing them: quoting a high OEE as if it were capacity utilization when the line runs one shift a day. If you want the fuller comparison, see OEE vs TEEP; for the macro backdrop, U.S. capacity utilization data shows real plants run well below their theoretical ceilings by any measure. The same denominator discipline also shapes how you sequence production scheduling and campaign runs, where planned changeovers and no-demand gaps have to be booked consistently or every line's OEE drifts apart.
What do the standards actually say?
Two reference points are worth stating with their provenance, because planned production time is exactly where OEE numbers become negotiable:
- The international standard ISO 22400-2:2014 “Key performance indicators for manufacturing operations management,” defines OEE as Availability × Performance × Quality and anchors Availability to planned busy time the standard's name for planned production time. Because every input has a precise definition, two plants applying it cannot disagree on what belongs in the denominator. See the ISO 22400-2 catalog entry.
- The “loading time” convention and the exclusion of planned maintenance trace to Seiichi Nakajima's original TPM work in the 1980s. It is the source of the vocabulary, not a modern audited rule, which is why the maintenance and no-demand treatments are still legitimately debated shop to shop.
The practical takeaway sits underneath both references: the denominator is only trustworthy if it is fixed and applied consistently, and it is only accurate if the underlying time is measured rather than remembered. Plants that compute OEE from machine signals at the source, the way Harmony reads run state from PLCs and sensors instead of end-of-shift estimates (see the platform), take the denominator games off the table, because the clock is recorded, not reconstructed. To see what that shift looked like on a real floor, read how one specialty manufacturer replaced paper production logging with real-time visibility. Then put your own numbers, and your own honest denominator, through the OEE calculator.