Reliability = probability of running without failure over a period. Availability = the fraction of time the asset is actually up: A = MTBF/(MTBF+MTTR) = uptime/(uptime+downtime). The two levers are MTBF (fail less) and MTTR (repair faster).
Components in series multiply โ A = AโยทAโยทโฆ โ so more parts in a chain means lower availability (the weakest link rules). Redundancy (parallel) does the opposite: A = 1 โ (1โAโ)โฟ drives availability up fast.
Availability is counted in “nines”: 99% (two nines) โ 88 h/yr down; 99.9% โ 8.8 h/yr; 99.99% โ 53 min/yr. RAM modelling rolls reliability + maintainability across a whole plant to predict production availability.
1 · Reliability is not availability
The two words are used interchangeably in conversation and mean very different things in engineering:
- Reliability R(t) is the probability an item runs without failing over a stated period โ a forward-looking probability, the world of the Weibull curve. It says nothing about repair.
- Availability A is the long-run fraction of time the item is in a working state. It folds in both how often it fails and how long it’s down each time.
That difference is why a very reliable item can still have mediocre availability: if it only fails once a year but each failure means a two-week wait for a spare and a specialist, the downtime dominates. Conversely, something that fails often but is back in minutes can post excellent availability. The business feels availability; reliability is one of the two ingredients that produce it.
2 · The availability formula
Availability comes straight from the mean times between and to repair:
The two levers map onto the two halves of the Academy. Growing MTBF is the reliability agenda โ better design, RCM, precision maintenance, defect elimination via RCA. Shrinking MTTR is the maintainability agenda โ fast detection (condition monitoring), planned, kitted jobs, spares on the shelf, accessible design. RAM analysis is just doing this arithmetic across an entire plant.
3 · Three kinds of availability
“Availability” gets quoted at three levels, and the gaps between them are where money hides:
- Inherent availability (Aแตข) โ uses only active repair time. The designer’s best case:
MTBF/(MTBF+MTTR)with MTTR = hands-on repair only. - Operational availability (Aโ) โ uses mean down time, which adds detection delay, waiting for crew, spares logistics and admin. Always lower than inherent โ and the gap is almost entirely a maintenance management problem, not an equipment one.
- Production availability โ the plant view, weighting equipment downtime by its actual effect on throughput (a spared pump tripping may cost nothing; a single-train compressor stops everything). This is what RAM models predict and what the business cares about.
The lesson: chasing inherent availability through better hardware while ignoring the logistics-and-planning gap leaves most of the prize on the table.
4 · Combining systems: series vs redundancy
Real plant is many components together, and how they’re arranged in the reliability block diagram (RBD) changes everything:
Series is sobering: ten components each at 99% give a system at 0.99ยนโฐ โ 90% โ the chain is much weaker than any link. Redundancy is the cure: two parallel units each at 99% give 1 โ 0.01ยฒ = 99.99%, a hundred-fold cut in downtime. That is why critical duties run installed spares (2ร100%) or voting arrangements (2-out-of-3). The calculator shows both effects โ set the single-unit MTBF and MTTR, then add redundant units:
Interactive — Availability & redundancy
Live modelAnnual downtime vs repair time
Aโ = MTBF/(MTBF+MTTR); redundant A = 1โ(1โAโ)โฟ (active 1-of-n parallel); annual downtime = 8760ยท(1โA) h; nines = โlogโโ(1โA). Idealised: assumes independent failures, perfect switchover and unlimited repair crews. Real RAM models add common-cause failure, repair-resource limits, logistics delay and partial-capacity states via simulation.5 · The nines
Availability is so often near 100% that it’s spoken of in nines โ and each extra nine is a ten-fold cut in downtime, and usually a large step in cost:
| Availability | “Nines” | Downtime per year |
|---|---|---|
| 90% | one nine | ~36.5 days |
| 99% | two nines | ~3.65 days (88 h) |
| 99.9% | three nines | ~8.8 hours |
| 99.99% | four nines | ~53 minutes |
| 99.999% | five nines | ~5.3 minutes |
Two practical truths fall out. First, the cost of each extra nine climbs steeply โ pushing from two to three nines is usually achievable through better maintenance management; three to four often needs redundancy and design changes; five-nines is a deliberate, expensive architecture. Second, you should only buy the nines a duty actually needs: spend them where downtime is genuinely costly or unsafe, decided by the same criticality ranking that drives the rest of the strategy.
This is where reliability becomes a number the business buys. RAM modelling lets you compare options โ an extra spare pump vs faster spares logistics vs a more reliable seal โ on one currency: production availability, and therefore revenue. It draws its inputs from Weibull life data and OREDA/ISO 14224 failure rates, and its MTTR side from the planning and spares systems Bluestream implements in the CMMS.
Key takeaways
- Reliability โ availability. Availability = MTBF/(MTBF+MTTR) โ it folds in both failure frequency and repair speed.
- Two levers: grow MTBF (reliability) or shrink MTTR (maintainability) โ and most of the operational-availability gap is a planning/logistics problem.
- Series multiplies down, redundancy multiplies up โ a long chain is weak; parallel units crush downtime.
- Count the nines, and buy only what the duty needs โ each extra nine is 10ร less downtime and a step up in cost.