Net operating time is the theoretical time it should have taken to make everything you actually produced, running at ideal speed. It sits below operating time in the OEE model, and the drop from one to the other is pure speed loss, isolated from every stoppage.
Net operating time is the least-known term in the OEE time model and the most useful one for a specific job: telling speed loss apart from stoppage loss. If your line is behind and you cannot tell whether it is because the machine keeps stopping or because it is quietly running slow, net operating time is the number that answers it. This guide places it exactly in the time waterfall, shows the two subtractions on either side of it, and works a hypothetical so you can compute it by hand. Then check your own line in the OEE calculator.
Where does net operating time sit in the OEE time model?
It sits one level below operating time and one level above valuable operating time. The OEE model is a descending stack of time buckets, each smaller than the last because a loss was removed:
- Planned production time the time you intended to run, after breaks and planned maintenance.
- Operating time planned production time minus all downtime and changeovers. Availability lives in this drop. Also called run time.
- Net operating time operating time minus speed loss (slow cycles and minor stops). Performance lives in this drop. This is our subject.
- Valuable operating time net operating time minus the time spent making rejects. Quality lives in this drop.
Put plainly: net operating time equals the total count of units you made, good and bad together, multiplied by the ideal cycle time. It is the time those units should have taken at full speed. Operating time is the time they actually occupied the machine while it was up. The difference between the two is speed loss and nothing else.
Why does isolating speed loss from stoppage loss matter?
Because the two failures have completely different cures, and a single "we're behind" number hides which one you have. Stoppage loss is time the machine was down, you fix it with faster changeovers, fewer breakdowns, better downtime tracking. Speed loss is time the machine was up but not producing at rate, you fix it by hunting slow cycles, worn tooling, conservative settings, and the minor stops and idling too short to log. Send a maintenance team to chase breakdowns on a line whose real problem is a de-rated conveyor, and you will spend a month improving the wrong number.
Net operating time is the wall between those two worlds. Once you know operating time (from the downtime log) and net operating time (from count × ideal cycle), the gap between them is speed loss with no ambiguity. A line can post decent availability, few long stops, and still bleed 20% of its output between operating time and net operating time, purely to slow running. That leak is invisible until you compute net operating time, which is why performance is the most commonly under-measured of the three OEE factors.
There is a reason the speed slice hides. Downtime is loud, the line is stopped, a light is red, someone is standing at the machine. Speed loss is silent: the line keeps moving, product keeps coming off the end, and everything looks fine except the count at the end of the shift is short. Nobody walks past a running machine and thinks "that's three percent slow." Net operating time is the arithmetic that catches what the eye cannot, converting a vague sense of "we should have made more" into a specific number of minutes with a specific owner.
How do you calculate net operating time?
You need two inputs: the total count of units produced in the period, and the ideal cycle time per unit. Multiply them. Here is the procedure with a hypothetical packaging line, illustrative numbers, not data from a real plant:
- Fix the ideal cycle time. Use the machine's true best repeatable rate. Say 1.0 second per unit (60 units/minute). This anchors everything; a soft ideal makes speed loss vanish.
- Establish operating time. Planned production time minus downtime. Say 450 planned minutes minus 63 minutes of stops and changeovers = 387 operating minutes.
- Count total units produced. Good plus bad, everything the machine actually made. Say 19,800 units.
- Compute net operating time. Total count × ideal cycle = 19,800 × 1.0 sec = 19,800 seconds = 330 minutes.
- Read the speed loss. Operating time minus net operating time = 387 − 330 = 57 minutes of pure speed loss. Performance = 330 ÷ 387 = 85.3%.
The 57 minutes is the machine being up but not making rate, not a single logged stop among them. That is the number a stoppage-only view would never surface.
How is net operating time different from run time and takt time?
They answer different questions, and the names get muddled constantly. The table sorts them out:
| Term | What it is | Question it answers |
|---|---|---|
| Operating time (run time) | Planned time minus downtime | How long was the machine up? |
| Net operating time | Total count × ideal cycle time | How long should the output have taken at speed? |
| Valuable operating time | Good count × ideal cycle time | How much of that was good? |
| Takt time | Available time ÷ customer demand | How fast must we go to meet demand? |
Run time is a clock measurement; net operating time is a calculation from output. Takt time is a demand target and has nothing to do with the machine's condition, it is the pace the customer sets. Confusing net operating time with takt is a common error: one describes how the machine actually performed, the other describes how fast it needs to go. And valuable operating time is simply net operating time with the rejects stripped out, the same logic as first pass yield.
Two anchors for why the speed slice deserves its own term:
- Net operating time and its neighbors come directly from the OEE loss model that traces to Seiichi Nakajima's TPM work, where speed loss (reduced speed plus minor stops) is separated from downtime as its own loss family, documented across the OEE literature at OEE.com's six big losses reference.
- The gap this term exposes is real at the macro scale too: the Federal Reserve's G.17 release put U.S. manufacturing capacity utilization at 75.7% in May 2026 a reminder that machines routinely run below their rated speed even while nominally "operating."
How do you use net operating time to improve a line?
You use it as a diagnostic split, not a scoreboard. On its own, net operating time is not a percentage anyone posts on a board; its value is entirely in the comparison it enables. Compute operating time and net operating time every shift for the constraint machine. When output misses, look at which gap widened: if the drop from planned to operating time grew, you have a stoppage problem and the fix lives in the downtime log; if the drop from operating to net operating time grew, you have a speed problem and the fix lives in cycle-level data. That single fork saves teams from chasing the loud failure while the quiet one does the damage. Over a few weeks the pattern of which gap widens becomes a habit-level signal: some lines are chronically stoppage-limited, others chronically speed-limited, and knowing which one a line is tells you where to point improvement effort before anything even breaks.
The hard part is getting an honest net operating time, because it depends on two things people fudge: an accurate total count and a defended ideal cycle time. Count from the machine, not a tally sheet, and anchor the ideal rate once so nobody can "adjust the standard" to make speed loss disappear, the collection question is covered in OEE data collection methods. Lines that read counts and cycle times straight from the equipment, the way Harmony computes true OEE from PLCs and sensors rather than end-of-shift estimates (see the platform), get net operating time for free and can watch speed loss separate from stoppage loss in real time. For the full arithmetic that wraps around this term, start with the OEE calculation and to judge the result, see what counts as a good OEE score.