Key takeaways
Short answer: Uptime and availability are related but not interchangeable. Uptime is a quantity of time — the hours equipment was actually running or ready to run. Availability is a ratio — uptime divided by the time the equipment was supposed to be available, expressed as a percentage. The crucial subtlety is the denominator: availability depends entirely on what you compare uptime against, and different bases (calendar time, scheduled time, planned production time) give very different numbers. In OEE specifically, the Availability factor measures run time against planned production time, excluding planned downtime — a stricter and more useful figure than raw uptime. It is closely tied to availability vs reliability.
Uptime is the simplest of the two ideas: the amount of time a piece of equipment is running, or available and able to run, over some period. Its complement is downtime — the time the equipment is stopped, whether for a breakdown, a changeover, planned maintenance, or lack of work. Uptime is a raw duration, measured in hours or minutes: "the line had 100 hours of uptime this week." It is intuitive and easy to record, and it is the headline figure in many simple monitoring systems and IT contexts ("the server had 99.9% uptime"). But on its own, uptime as a bare number of hours is incomplete, because it means nothing without a reference: 100 hours of uptime is excellent if the machine was only meant to run 110 hours and poor if it was meant to run 160. Uptime tells you how long the equipment ran; it does not, by itself, tell you how good that is. To turn it into a judgement, you have to compare it to something — and that comparison is where availability comes in.
Availability is a ratio: uptime divided by some reference period, expressed as a percentage. It converts the raw duration of uptime into a proportion that can be judged and compared. In reliability engineering, availability is classically defined as uptime divided by the sum of uptime and downtime — the fraction of the total considered period that the equipment was up. The general form is always uptime over some base time. Because it is a percentage, availability lets you compare equipment of different scheduled hours, track a trend, and set targets in a way that raw uptime hours cannot. But that convenience comes with a catch that uptime does not have: the value of availability depends entirely on what you choose as the denominator. The same uptime can yield very different availability percentages depending on whether you divide by calendar time, scheduled time, or planned production time. So while availability is the more useful figure, it is also the more easily manipulated or misunderstood one — its meaning lives in its denominator.
The first-order difference is simply that uptime is a duration and availability is a ratio. Uptime answers "how many hours?"; availability answers "what fraction of the time it should have been running?". Uptime is an absolute quantity; availability is relative to a reference. This makes uptime an input to availability rather than a competitor to it — you cannot compute availability without an uptime figure, and you cannot interpret an uptime figure without the reference that turns it into availability. People often use the words loosely and interchangeably, especially the percentages ("uptime of 95%" usually means availability), and in casual use that is harmless. But precision matters when the numbers drive decisions, because conflating a raw duration with a ratio — or quoting an availability percentage without stating its base — hides exactly the information that makes the number meaningful. The discipline is to treat uptime as the measured hours and availability as the deliberately-defined ratio built from them, and always to be explicit about the denominator.
Everything that makes availability tricky lives in the denominator. Divide the same uptime by different reference times and you get wildly different availabilities, each technically correct but meaning something different. Divide by calendar time (all 168 hours in a week) and you get a number dragged down by every hour the plant was legitimately closed — rarely useful for equipment performance. Divide by scheduled time (the hours the equipment was meant to be staffed and running) and you get a figure about how well the scheduled time was used. Divide by planned production time (scheduled time minus planned, unavoidable stops like breaks and planned maintenance) and you get the stricter figure used in OEE. Reliability engineers further distinguish inherent availability (counting only repair time) from operational availability (counting all downtime including logistics and waiting). None of these is "wrong," but they are not comparable, and quoting an availability without stating its base is meaningless at best and misleading at worst. The first question to ask of any availability number is always: divided by what?
A machine runs for 100 hours during one week. How available was it? It depends entirely on the base. Against the full calendar week of 168 hours, availability is 100/168, about 60% — but that punishes the machine for the nights and weekend it was never meant to run, so it is not a fair performance measure. The plant actually scheduled the machine for two shifts, 120 hours; against scheduled time, availability is 100/120, about 83%. But of those 120 scheduled hours, 10 were planned downtime — scheduled maintenance, breaks, and a planned changeover window — leaving 110 hours of planned production time; against that, the OEE-style availability is 100/110, about 91%. One machine, one uptime figure of 100 hours, and three defensible availabilities: 60%, 83%, and 91%. The differences are not errors; they are different questions. The 60% answers "of all clock time," the 83% answers "of time we staffed it," and the 91% answers "of time it was actually supposed to be producing." The denominator is not a detail — it is the whole meaning of the number.
OEE resolves the denominator question with a specific, deliberate choice: the Availability factor is run time divided by planned production time, where planned production time is the scheduled time minus planned downtime. This means OEE availability counts only the losses that are arguably avoidable — unplanned breakdowns and the time lost to changeovers — and excludes planned downtime such as breaks, scheduled maintenance, and periods of no demand, which are not failures of the equipment to perform when it was supposed to. This is what makes OEE availability more meaningful for improvement than a raw uptime percentage: it isolates the downtime you can actually attack. It is also why OEE availability is usually lower than a casually-quoted "uptime" — it uses a stricter base and refuses to give credit for time the equipment was legitimately not producing. The distinction between which stops count is exactly the subject of planned vs unplanned downtime, and getting that classification right is what makes the Availability factor trustworthy.
Availability is the first of the three factors in OEE, multiplied with Performance and Quality to give the overall figure. Because OEE defines availability against planned production time and excludes planned downtime, it captures exactly the unplanned and changeover losses that erode productive time — which is why conflating a loose uptime percentage with OEE availability overstates true performance. The Availability factor is where breakdowns, minor unplanned stops that cross the downtime threshold, and changeover time land, making it the natural home for maintenance and setup-reduction efforts. Improving it means attacking those specific losses — fewer breakdowns through better maintenance strategy, faster changeovers, quicker response to stops — rather than simply running more calendar hours. And because availability is about whether the equipment runs when it is supposed to, it connects directly to equipment reliability: more reliable equipment fails less, so it is available more.
Fabrico measures the Availability factor properly by tracking run time against planned production time and capturing downtime with reason codes — so you see not just an uptime percentage but where availability is actually being lost and why. By separating unplanned breakdowns and changeovers from planned downtime, it gives you the stricter, more honest availability number that points to the losses worth attacking. Book a demo to see your real availability and what is eroding it.
Uptime is the amount of time equipment is running — a raw duration in hours. Availability is a ratio: uptime divided by the time the equipment was supposed to run, expressed as a percentage. Uptime is an input to availability, and availability's meaning depends entirely on the reference time you divide by.
It depends on the question. Calendar time includes hours the plant was closed; scheduled time covers staffed hours; planned production time (scheduled minus planned downtime) is what OEE uses. Always state the base, because the same uptime gives very different availability percentages against different denominators.
OEE availability is run time divided by planned production time, where planned production time is scheduled time minus planned downtime such as breaks and scheduled maintenance. It counts only unplanned breakdowns and changeover losses, making it stricter and more useful for improvement than a raw uptime percentage.
Because OEE uses a stricter base (planned production time) and refuses credit for legitimately non-producing time, while only counting avoidable losses. A casually quoted uptime percentage often uses a more generous denominator, so it looks higher without reflecting the avoidable downtime OEE isolates.
Not necessarily. The figures are only equal if they use the same denominator. An IT-style 99% uptime against calendar time is a different measure from an OEE availability of 99% against planned production time. Always check what each percentage was divided by before comparing them.
Login
Blog
