Operating Time: Definition, Formula & OEE Link

What is operating time?

Operating time is the net duration during which a machine, line or system is actively producing output. Not powered on, not scheduled, not theoretically available. Actively producing. It feeds directly into the availability factor of OEE, serves as the divisor in the hourly machine rate, and is the single most overstated number on almost every production dashboard I have audited in 25 years.

The honest version of this metric is almost always 10 to 20 percentage points below the reported one. Not because plants cheat, but because short stops, unreported setup overruns and quiet idling fall below the threshold that operators manually log. The moment a plant switches on automatic capture, the number drops and the real improvement work can finally begin. That is the subject I wrote a book about in 2025, and it starts with operating time.

Operating time vs. the terms it gets confused with

Five closely related time concepts show up in every manufacturing conversation. Mixing them up is the most common reason production and controlling never agree on the same number.

Operating time sits in the middle of this hierarchy. It is tighter than running time, because idling does not count. It is also different from productive time, which counts only output that passed quality. Operating time is the raw production duration, independent of yield.

The formula

Operating Time = Planned Production Time − (Unplanned Downtime + Micro-Stops + Setup Overruns)

And the ratio used in OEE and reporting:

Operating Time Rate (%) = Operating Time ÷ Planned Production Time × 100

Worked example. A line is scheduled 480 minutes per shift with 30 minutes of planned breaks, giving 450 minutes of planned production time. Unplanned breakdowns account for 45 minutes, micro-stops another 18 minutes, a setup overrun 12 minutes. Operating time is 375 minutes. The operating time rate is 83.3 percent.

In most plants running on manual data, the same shift reports 420 to 430 minutes and an operating time rate of 93 to 95 percent. The 40 to 60 minute gap is not fraud. It is 20 short stops that nobody logged because they took less than two minutes each.

Where the reported number goes wrong

Four systematic biases inflate self-reported operating time in almost every plant I have audited across automotive, FMCG, pharma packaging and metal forming.

1. Micro-stops disappear. Any stop under roughly two minutes falls below the manual reporting threshold. The operator fixes it and moves on. Twenty events per shift at 90 seconds each is half an hour of invisible downtime.

2. Setup overruns get reclassified. The plan says 12 minutes for a changeover; reality is 18. The extra 6 minutes often get booked under the prior order or under no category at all.

3. Idling counts as running. A machine powered on with no parts moving is often recorded as running, because the light is still on. Strict operating time capture only counts cycles where output is actually produced.

4. The end-of-shift round-up. When manual logs are filled in at shift end, the numbers get smoothed. Human memory favours the clean story over the messy truth.

Realistic operating time rates by process

Benchmarks vary widely by process type. A 70 percent operating time rate is poor in one industry and excellent in another. Rough ranges from real installations:

Why operating time matters for costing

Operating time is also the divisor in the hourly machine rate calculation. If the divisor is inflated by 20 percent, the hourly rate is understated by 20 percent. Every product cost computed against that rate is wrong, and every make-or-buy decision based on that cost is biased toward making in-house parts that are actually unprofitable. I have sat in more than one costing meeting where the finance team defended an hourly rate derived from operating times that production could not reproduce. Both sides were using the same ERP field with different interpretations.

How to improve it

Three levers, in the order they pay off:

1. Measure automatically first. Without continuous PLC-level state capture, every improvement project aims at a moving target. Most plants recover 5 to 8 percentage points of operating time just by making the losses visible, before changing anything else. The Meleghy rollout across six plants produced a 5 percent availability gain and 7 percent higher output in six months, driven primarily by honest measurement.
2. Attack micro-stops. A Pareto of stops from one week of automatic data typically shows the top three causes account for 60 percent of lost minutes. Fixing those recovers 10 to 15 percent of operating time. This is the highest-ROI intervention in almost every plant.
3. Structured SMED on changeovers. The Klocke pharma rollout saved seven hours of production per line per week within three weeks, almost entirely through measured changeover reduction.

FAQ

Is operating time the same as uptime?
No. Uptime is the raw powered-on clock value. Operating time excludes idle periods. A machine can be up for 8 hours and only producing for 6, giving 100 percent uptime but 75 percent operating time rate.

Does changeover count as operating time?
By the standard OEE convention, no. Changeover is a stop. Some plants book it as planned, some as unplanned, but either way it is outside operating time. The definition needs to be fixed once and held consistent across sites, otherwise cross-plant benchmarking is meaningless.

How accurate is manually recorded operating time?
Typically 70 to 85 percent accurate, with a systematic upward bias. Sub-two-minute stops almost never get logged. Automated capture closes the gap on day one.

What is a realistic target?
Do not set a target before measuring honestly for one quarter. The baseline that comes out of automatic capture is always more useful than a target imported from a benchmark sheet.

How fine should the resolution be?
Sub-second state capture at the machine, aggregated to shift or daily reports. Anything slower misses the micro-stops that dominate real loss.

What software captures operating time automatically?
A modern MES or dedicated OEE platform reading PLC states over OPC UA for modern controls, or digital I/O gateways for brownfield machines. SYMESTIC's Production Metrics module handles this as a day-one capability, with typical rollout times measured in hours per machine.

Related: OEE · Machine Availability · Machine Runtime · Production Time · Machine Data Capture · MES · SYMESTIC Production Metrics

About the author

Christian Fieg

Head of Sales at SYMESTIC. 25+ years in manufacturing including Johnson Controls, Visteon, iTAC and Dürr. Six Sigma Black Belt. Led global MES rollouts across 900+ machines in China, Mexico, USA, France, Tunisia and Russia. Author of OEE: Eine Zahl, viele Lügen (2025). · LinkedIn