Availability Calculator
The formula
What the availability tells you
The share of planned production time the asset was actually running — the downtime dimension of OEE and the home turf of maintenance strategy.
Calculation: Availability = run time ÷ planned time. Enter your inputs and every substitution is shown below the result.
Reading the result
Below 85% and the conversation is failure frequency versus repair speed; both halves need MTBF and MTTR evidence, which this framing invites.
Rules of thumb: 85–95% normal; >95% usually means generous planned-time definitions
Limitations and best practice
Changing overalls and short stops hide in the average — run-size assumptions distort it; count stoppages, not just minutes.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Do scheduled maintenance days count against availability?
Availability vs uptime?
Source & methodology
TPM availability standard.
Availability: what this tool answers
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. There are plenty of pages about Availability; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
Most confusion about Availability comes from mixing up the input you control with the input you merely observe. The formula treats them identically, but your decisions should not: one deserves measurement, the other deserves a defensible estimate.
A calculation like this one is worth roughly as much as a careful sentence: it forces several vague considerations into one comparable quantity. Once Availability is on the table, the argument can stop being about impressions.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to availability = 88.2 % on the default inputs, and the sensitivity section ranks the inputs that move the result — Planned production time first, at ≈11.1 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.
The Availability formula, explained
The engine implements a single stated model: Availability = run time ÷ planned time. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Planned production time (min) (example value 510) is a quantity rather than a category — precision here is cheap and worth having. If the period is partial, decide whether you mean elapsed or planned time and keep that meaning across every field.
Actual run time (min) (example value 450) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Use the value as of today, not as of the last time you looked — time fields drift silently.
Mean time between failures (min) (example value 180) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Use the value as of today, not as of the last time you looked — time fields drift silently.
The default Availability calculation, written out in full
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Planned production time (min), Actual run time (min), Mean time between failures (min). The computed availability comes out at 88.2 %, which the interpretation band labels “Downtime 60 min — 0.3 failure-equivalents lost”.
- A = 450 ÷ 510 = 88.2%
- Split planned downtime into unplanned vs planned stops to know whether the lever is maintenance or scheduling
Downtime minutes — 60.0 min. This is the number experienced users quote when the headline alone would mislead.
Run hours achieved — 7.50 h. This is the number experienced users quote when the headline alone would mislead.
Planned hours — 8.50 h. This is the number experienced users quote when the headline alone would mislead.
Re-running with your own figures is instant; re-running by hand once is the best way to know the tool is telling you the truth.
The Availability corridor: your result across a realistic band
The honest version of any estimate is a corridor, and this one is cheap to produce: Availability was recomputed at 5 points along the dominant input, with every other field left untouched.
| Planned production time setting | Availability |
|---|---|
| 80 % of the example value | 110.3 % |
| 90 % of the example value | 98.0 % |
| example inputs | 88.2 % |
| 110 % of the example value | 80.2 % |
| 120 % of the example value | 73.5 % |
Across 5 settings of Planned production time, the result spans 73.5 % to 110.3 %. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing Planned production time alone; the substitution steps will follow your figures exactly.
Sensitivity: which inputs change Availability the most
This list was computed for this specific engine just now: each numeric input was nudged ±10 % while every other field held its example value, and the availability was recalculated from scratch. For Availability the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Planned production time: ten percent up gives 80.2 %, ten percent down gives 98.0 % — ≈11.1 % of the availability either way
- Actual run time: ten percent up gives 97.1 %, ten percent down gives 79.4 % — ≈10.0 % of the availability either way
Planned production time is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 80.2 % to 98.0 %. That is where a careless figure does the most damage, so check it against a source, and treat Actual run time as the second priority (≈10.0 % per ten percent). The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
Interpreting the Availability verdict
The value above only becomes useful the moment you know what it is being measured against. The default case lands in the “Downtime 60 min — 0.3 failure-equivalents lost” band, and bands are deliberately wide because real situations overlap. The sensitivity list shows how far a modest input error moves you along that ladder: for Planned production time, ±10 % covers 80.2 % to 98.0 %. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
Where Availability sits next to similar measures: this tool answers “how much is the Availability”, while the related calculators answer “what do I do about it”. Reading the result alone tends to over-weight a single snapshot; pairing it with the companion tools above turns the number into a decision.
Common mistakes with Availability (and the fix)
Changing overalls and short stops hide in the average — run-size assumptions distort it; count stoppages, not just minutes. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Using stale inputs. Availability is only as current as the numbers behind it — an estimate carried over from a previous season, rate table or report quietly biases every output. Re-measure the inputs first; that single habit fixes more bad Availability figures than any formula change.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Planned production time dominating — a careful figure there beats false precision everywhere else.
Another is comparing across contexts: an Availability computed with one set of conventions should never be lined up against a figure computed with another. Check the inputs behind both before ranking them.
Availability verification checklist
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Re-verify Planned production time against a source document — ten percent of error there moves the headline by ≈11.1 %.
- Verify each input against its original source document, not memory.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
How to use the Availability tool properly
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for Availability takes a minute to learn and applies to every input above.
Step 1 — one document, one pass. Open the statement, label or record that holds planned production time (min), actual run time (min), mean time between failures (min) and transcribe straight into the form. Transcription from a single source removes the mismatch errors that appear when figures are assembled from three different places. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
Step 2 — baseline before exploration. Get one defensible Availability on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
Step 3 — play with the inputs on purpose. Ten percent up, ten percent down, one field at a time. Within a few minutes you will know this calculation better than most people who quote its results. The input you reach for first is usually the one you measured longest ago.
Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
Step 5 — record the context, not just the number. Note today’s date and the inputs alongside the 88.2 % output. Six months from now the context is what turns this figure into a trend. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
The real-world conversations Availability settles
Numbers earn their keep in conversations, and Availability is no exception. In Business & Entrepreneurship discussions around Operations, this figure decides whether an option stays on the table: it converts an opinionated debate into an arithmetic one, and arithmetic is the only referee both sides accept. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
The audience for this page is people who need one trustworthy number before their next decision. In professional Operations practice the pattern is always the same — screen with Availability, then invest slow analysis only in whatever survives the screen. Most surprises in numbers are surprises about inputs, not about formulas.
Re-running this page costs nothing and catches the slow drifts that never announce themselves. In Business & Entrepreneurship the expensive mistakes are rarely sudden; they are small changes in Planned production time (min) that nobody recalculated for a year. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.
People also ask about Availability
What affects Availability the most?
Availability is driven above all by Planned production time. Perturbing only that field by ten percent either way produced 80.2 % against the 88.2 % baseline — a ≈11.1 % response, while Actual run time manages ≈10.0 %.
Which matters more: actual run time or planned production time?
For Availability, Planned production time wins the head-to-head (≈11.1 % against ≈10.0 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Availability?
On the worked example above Availability comes out at 88.2 %. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate Availability by hand?
Availability = run time ÷ planned time is the entire method. Work the inputs in that order — A = 450 ÷ 510 = 88.2% — and you will reach 88.2 % on the default figures, the same number this tool prints.
What happens to Availability if planned production time changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 80.2 % to 98.0 % across the ten-percent probe, i.e. ≈11.1 % sensitivity on the availability.
Is the Availability result of 88.2 % good or bad?
Neither, on its own — the label “Downtime 60 min — 0.3 failure-equivalents lost” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in Planned production time alone moves it by ≈11.1 %.
How do I calculate Availability manually?
Write down the inputs, then follow the printed steps in order — Availability = run time ÷ planned time. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
Should I use Availability before launching?
Yes — an Availability run on honest inputs before spending is the cheapest consulting an entrepreneur can buy. Re-run at every pricing change; the number moves more often than founders expect.
Do scheduled maintenance days count against availability?
Standard practice: planned PM time is excluded from planned production time (it is not a loss), but the debate itself is the real warning — set the definition before measuring.
Availability vs uptime?
Uptime is a binary status; availability is time-weighted production loss — the metric that belongs in an OEE program.
Can this tool see the numbers I type?
It cannot. There is no submission step: the calculation happens in your browser and the result disappears when you close the page. Treat the fields above as a scratchpad rather than a form.
Key terms on this page
- Downtime minutes
- 60.0 min in the default Availability calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Run hours achieved
- 7.50 h for the Availability worked case; it sits next to the main result because it carries context the headline leaves out.
- Planned hours
- 8.50 h in the default Availability calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Availability
- The primary output of this tool: 88.2 % for the default inputs, computed exactly from Availability = run time ÷ planned time.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The interpretation attached to a result (“Downtime 60 min — 0.3 failure-equivalents lost” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Availability moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Method, sources and what this tool cannot tell you
Everything above runs on one stated formula, applied without hidden coefficients: Availability = run time ÷ planned time. Source of record: TPM availability standard. Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The sensitivity table above is part of that promise rather than a bonus: it lets you see how much of the result depends on how carefully you measured.
Turning this Availability into a decision
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
The audience here is people who need one trustworthy number before their next decision. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.