OEE Lab / Tools / Uptime Calculator for Production Lines

Uptime Calculator for Production Lines

For a machine or line: uptime and downtime percent from your scheduled time and stops, the downtime hours your target allows, and what it takes to get there.

Your machine or line

Any period works, from one shift to a month.

h
Planned to run, net of breaks and time with no orders.
min
Add up every stop in the period.
Gives the average stop and the time between stops.
%
Your own goal for this machine.
Uptime
-%
(Scheduled time - stop time) / scheduled time
0%100% = no stops
Downtime
-
Downtime hours
-
Run hours
-
Hours target allows
-
Over or under target
-
Average stop
-
Run time between stops
-
Average stop for target
-

Want a second look at this result?

Leave your work email if you would like the OEE Lab team to get in touch about your numbers. To keep the result, use Copy link or Print above.

Thanks, we have your email.

No newsletter, no spam.

The downtime you type in is only the downtime someone wrote down.

Short stops rarely reach a paper log. Fabrico, a light MES for OEE, takes stops live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, operators tag the cause at the line, and you see OEE per line and shift. See it live in Fabrico.

See where your line loses this time: book a demo with a Fabrico consultant.

Request a demo Contact us
Our tools stay free either way.

Uptime and downtime, in hours and percent

It turns your stop time into uptime and downtime percent, and into hours. It also works backward from a target, so you can see how many stopped hours that target leaves you.

This is uptime for a production line, measured against the time the line was planned to run. For the method and how it differs from utilization, read how to calculate uptime.

Uptime and downtime formulas

Uptime % = (scheduled time - stop time) / scheduled time
Downtime % = 100 - uptime %
Hours allowed = scheduled hours × (100 - target %) / 100
Uptime and downtime always add up to 100% of scheduled time.

Example: a 120-hour week with 12 stops

Example: a line is scheduled for 120 hours in a week and logs 12 stops, totalling 540 minutes. Its target is 95% uptime.

  • Downtime hours = 540 / 60 = 9.0 hours, so the line ran for 111 hours.
  • Uptime = 111 / 120 = 92.5%, and downtime = 7.5%.
  • Hours the target allows = 120 × 5 / 100 = 6.0 hours, so the line is 3.0 hours over.
  • Average stop = 540 / 12 = 45 minutes.
  • Run time between stops = 111 / 12 = 9.25 hours.
Actual: 111 h run, 9 h stopped At 95%: 114 h run, 6 h stopped
Both bars are the same 120 scheduled hours. The target asks for 3 fewer stopped hours.

Two ways to reach the target

The 3 hours can come from shorter stops or from fewer stops. With 6 hours allowed, the line needs an average stop of 30 minutes at 12 stops, or 8 stops at the 45-minute average.

Which one is easier tells you where to work. Long stops point to repair time, parts and the first response to a stop, while many short ones point to the causes behind them.

What a target leaves you

This table is plain arithmetic, so read it as a guide to scale and not as a benchmark. Small changes in the percent make a large change in the minutes.

Uptime targetPer 450 min shiftPer 120 h week
99%4.5 min1.2 h
98%9 min2.4 h
95%22.5 min6 h
90%45 min12 h
80%90 min24 h
For a 450-minute shift and a 120-hour week.

MTTR and uptime

Uptime can also be written from the two averages. Here that gives 9.25 / (9.25 + 0.75) = 92.5%, the same answer as above.

Uptime = MTBF / (MTBF + MTTR)
9.25 h / (9.25 h + 0.75 h) = 92.5%
True MTTR counts repairs only, so use the average stop here only if your log holds failures alone.

The "average stop" in the tool covers every stop you enter. If you log only failures, it equals MTTR, and the MTBF and MTTR calculator takes it further.

Errors that bend the uptime figure

  • Dividing by the whole clock. That is utilization, a much lower number. Use the machine utilization calculator for that question.
  • Leaving out changeovers. They take away time the line was meant to run. See how to count changeovers.
  • Taking breaks twice. If scheduled time is already net of breaks, do not add them to the stops.
  • Borrowing targets from IT. Figures such as 99.9% come from server uptime, where they mean something different. A line that changes over every day cannot be judged by them.

Downtime hours questions

How do you calculate downtime hours?

Add up the minutes of every stop and divide by 60. 540 minutes is 9.0 downtime hours. To get the percent, divide by the scheduled hours, as shown in how to calculate downtime percentage.

How many hours of downtime does 95% uptime allow?

Multiply the scheduled hours by 5%. A 120-hour week allows 6 hours, and a 7.5-hour shift allows 22.5 minutes. Change the target above to see any other figure.

How do you calculate uptime from MTTR?

Use uptime = MTBF / (MTBF + MTTR). With 9.25 hours between stops and a 0.75-hour repair, uptime is 92.5%. It only sees the stops you count as failures, so it can read higher than production uptime.

Is uptime the same as availability?

On a production line, yes. Run time divided by scheduled time is the availability factor of OEE, and the availability calculator handles planned stops as well.

What should I use as scheduled time?

Use the time the line was planned to run, net of breaks and time with no orders. Keep the rule the same each period, or your trend will move for the wrong reason. See planned vs unplanned downtime.

What does the downtime cost me?

This page gives the hours, and the downtime cost calculator turns them into money. It adds lost production, idle labor and other costs for each stopped hour.

← All OEE Lab tools