Fully productive time is the time you would have needed to make only the good units, at the ideal rate, with no stops: good count × ideal cycle time. Divide it by planned production time and you get OEE.
Not a clock reading
You cannot put a stopwatch on fully productive time. It is worked out after the fact from the good count, and it tells you what the shift was truly worth in minutes.
That is what makes it handy: a whole week of machine trouble reduces to one honest number you can compare with the schedule.
A line that was scheduled for 112 hours and has 84.7 fully productive hours has used 75.6% of its schedule. It really made what a perfect line would make in 84.7 hours.
The waterfall, from all time down
Example: a packaging line in one calendar week. Each row takes away one kind of time until only the fully productive time remains.
Every minute of the week is in exactly one box. That is the idea behind the OEE loss tree, which goes deeper into each loss code.
Read the factors off the waterfall
Each OEE factor is simply one level divided by the level above it. This line has an ideal rate of 30 units per minute, makes 158,760 units and has 152,400 good ones.
And the shortcut gives the same answer: 152,400 good units ÷ 30 per minute = 5,080 minutes. That shortcut is proven in time-based vs count-based OEE.
So the two bottom levels are close in meaning but not in input. Net run time uses all units, as explained in net operating time, while fully productive time uses only the good ones.
Same idea, different names
People get lost here, since the term is not used in every book. If you read older TPM material, you will see the same levels under other labels.
| Level in this guide | Also called | Removed before this level |
|---|---|---|
| Scheduled time | Planned production time, loading time | Excluded time |
| Run time | Operating time, runtime | Stops |
| Net run time | Net operating time | Slow running, short stops |
| Fully productive time | Theoretical run time, valuable operating time | Bad units |
Overall Equipment Effectiveness (R. C. Hansen, 2001) uses scheduled time and theoretical run time. The method is the same.
How to calculate it for a real run
You need just two numbers from the floor: the good count and the ideal cycle time for that product. Take care with both, as they drive the result directly.
- Good count. Units right the first time, from one counting point. See what counts as a good part.
- Ideal cycle time. The accredited rate for the format and not last month's average. See ideal cycle time.
- Same units. Parts and seconds, or units and minutes. Do not mix them.
With several products, work them out one at a time and add them up. If this week was two products, 120,000 good at 40 per minute is 3,000 minutes, 62,400 good at 30 per minute is 2,080 minutes, and the total is 5,080.
Why minutes beat units
Units cannot be added across products that run at different speeds. A run of 1,000 units at an ideal 10 per minute is 100 minutes of work, while 1,000 units at 60 per minute is under 17.
A report in units calls those two runs equal, and a report in fully productive minutes does not. That makes it a fair way to compare shifts with a different product mix, as long as every rate is right.
What to do with the number
See the lost time as hours
The gap from scheduled time to fully productive time is the sum of all your OEE losses. Here it is 6,720 − 5,080 = 1,640 minutes, or 27.3 hours in a week.
An OEE of 75.6% is abstract, and 27.3 lost hours is something a plant manager feels. The hidden factory calculator takes that further.
Check the data
Fully productive time can never be longer than scheduled time. If your sum says it is, then the rate, the count or the schedule is wrong, and OEE over 100 percent shows how to find which.
The losses must also close. Here 840 + 588 + 212 + 5,080 = 6,720, which is exactly the scheduled time.
Plan capacity
It gives you a clean way to think about how much more a line can make. Good units per week = fully productive minutes × ideal rate, so every minute won back adds 30 units on this line.
For planning on real numbers, use the production capacity calculator. For what lies beyond the schedule, see OEE vs TEEP.
Easy errors with this number
- Using total units. That gives net run time and leaves the quality loss in.
- Calling run time productive. In this example, 800 minutes of "running" produced nothing of value.
- Using a soft ideal rate. A rate set too low makes the good minutes look larger than they were.
- Comparing it across products with no rates. The minutes are comparable only when each product has its own proper rate.
To shrink the gap, start with the biggest bar. How to improve OEE gives the order of attack, and the six big losses split it further.
A waterfall is only as good as the stops and counts behind it. Fabrico is a light MES for OEE that takes stops, speed and counts live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, so each shift's OEE per line starts from machine data. See how Fabrico shows OEE per line.
What people ask next
Is fully productive time the same as OEE?
Almost. OEE is fully productive time divided by planned production time, so one is minutes and the other is a percentage. In the example, 5,080 minutes out of 6,720 is 75.6%.
What is the difference between run time and fully productive time?
Run time is the clock time the machine was up. Fully productive time removes slow running, short stops and bad units from it, so it is shorter on any real shift. See how to calculate uptime for the clock side.
What is the difference between net run time and fully productive time?
Net run time counts all units at the ideal rate, and fully productive time counts only good units. The gap between them is the quality loss in minutes. See net operating time.
Can a machine reach 100% fully productive time?
Only in theory, because it would mean full speed, no stops and no bad units for the whole schedule. A sensible aim comes from your own loss split, as covered in how to set OEE targets.
Should I use planned time or all time as the base?
Use planned time for OEE and all time for TEEP. The bottom bar stays the same in both, and only the base changes. See the TEEP calculator.
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: How to Explain OEE in Plain Words to Any Team