Net operating time is the run time that is left after short stops and slow running are taken out, and it usually equals total units × ideal cycle time. Run time is what the clock says, while net operating time is what the output says the clock was worth.
Run time is what you think you got
Picture a line that shows as up all morning. Nobody logged a stop, the run light was on, and the operator was busy.
Then the count comes in low. Run time cannot explain that, and net operating time is the number that shows the gap.
A shift, split open
Example: a labelling line has 480 scheduled minutes and 40 minutes of logged stops, so run time is 440 minutes. It makes 7,200 labelled units, and its ideal cycle time is 3.0 seconds per unit.
At the ideal rate, 7,200 units need 7,200 × 3.0 s = 360 minutes. So the line was up for 440 minutes and delivered 360 minutes' worth of output.
Performance is the same split as a percentage: 360 ÷ 440 = 81.8%. If you want the full formula, go to how to calculate OEE performance.
Net operating time vs run time
| Level, this shift | Comes from | Takes out |
|---|---|---|
| Run time: 440 min | Clock, stop log | Logged stops |
| Net operating time: 360 min | Total count, ideal rate | Also slow running and short stops |
| Fully productive time: 351 min | Good count, ideal rate | Also bad units |
Run time can be read off a clock or an hour meter, while net operating time has to be worked out. So if someone quotes it from a meter, they mean something else.
The level below this one has its own page: fully productive time, with the whole waterfall.
Two definitions, and how to tell which you have
The term is used in two ways, and both are in circulation. This is the main source of confusion.
Modern use: net operating time, or net run time, is total units × ideal cycle time. It takes out all speed loss, so here it is 360 minutes, and this is the one we use on this site.
Classic TPM use: Nakajima's formulas split performance in two, into a net operating rate and a speed rate. Net operating time here uses the actual cycle time, so it takes out the short stops only.
That split is useful, since it separates 44 minutes of short stops from 36 minutes of slow running, and those two have different fixes. Overall Equipment Effectiveness (R. C. Hansen, 2001) sets the net operating rate to 1.0, so speed rate there is the whole performance factor.
When a report gives you a figure, look at the numerator. Ideal cycle time means the modern version, and actual cycle time means the classic one.
How to measure it on the floor
- Modern version. Take total units from a counter at the output, then multiply by the ideal cycle time for that product.
- Classic version. Also time about 20 clean cycles in a row, with no stops in the sample, to get the actual cycle time. Repeat at other times of day.
- Several products. Work out units × cycle time for each product, then add them up.
- Short stops. The classic gap (run time − units × actual cycle) estimates them with no stop log at all.
A cycle time calculator helps with the sums. Cycle time variation shows why one sample is not enough.
What the gap tells you
Look at run time minus net operating time, as a share of run time. Here that is 80 of 440 minutes, or 18.2% of the time the line looked busy.
- Large gap, flat hourly rate. The line runs slowly all the time. See speed losses.
- Large gap, jumpy hourly rate. The line is stopping often for short periods. See micro-stops.
- Gap close to zero. Good news, or a soft ideal rate. Check the ideal cycle time.
- Gap below zero. Net operating time is longer than run time, so a figure is wrong. See performance over 100%.
Two lines with the same run time
Example: a second labelling line also runs 440 minutes on the same product, so both lines show 91.7% availability. It makes 8,360 units, and at 20 per minute its net operating time is 418 minutes.
The gap between the two lines is 58 minutes a shift, or 1,160 units. A report built on run time alone calls them equal, so copy what the better line does before you buy anything.
The number that a logging rule cannot move
Log more of the short stops and run time goes down. Net operating time does not change at all, because it comes from the count and the ideal rate.
So it is a stable reference when you change how stops are logged, and the stop threshold guide shows this with numbers. Mean time between stops adds how often the line halts, and the OEE loss tree shows where this level sits.
Mistakes to avoid
- Using good units. That removes the quality loss too and gives fully productive time.
- Using the nameplate speed. A rate the line never reached makes the gap look larger than it is.
- Reading it from an hour meter. The meter gives run time.
- Mixing the two definitions in one report. Choose one and label it.
The gap between run time and net operating time is often short stops that nobody logged. Fabrico takes speed and counts live from the machine, and where cameras are fitted, it shows video of each stop, streamed on request next to its machine data. See how Fabrico uses cameras for OEE.
What people ask next
Is net operating time the same as uptime?
No. Uptime is the clock time the machine was running, which is close to run time. Net operating time also removes slow running and short stops. See how to calculate uptime.
What is the net operating rate?
In the classic TPM formulas, it is actual cycle time × units, divided by operating time. It shows how steadily the machine ran, apart from how fast. In the example, that gives 90%.
Is net operating time the same as net run time?
In most modern use, yes: both mean total units × ideal cycle time. Check the formula in the report, since older TPM books use actual cycle time.
How do I find the short stops with no sensor?
Time clean cycles to get the actual cycle time, then subtract units × actual cycle time from run time. What remains is an estimate of the short stops. How to reduce micro-stops shows the next steps.
Why do bad units count in net operating time?
Because the machine spent time making them at whatever speed it ran. Their loss is taken one level down, in quality. See good count.
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: Gross OEE vs Net OEE: What the Terms Really Mean · History of OEE: From Nakajima to Hansen and ISO