Availability, Maintainability, and Downtime Budget Calculator
Connect failure intervals and restoration time to steady-state availability, required maintainability, and period downtime budgets.
Engineering screening tool—verify inputs and results independently. Use at your own risk.
Reliability and restoration inputs
Availability result
How to use
- Select whether MTBF and MTTR are known, or solve the missing active MTTR/MTBF for a target.
- Enter positive times in hours. Add nonnegative planned-maintenance and logistics delay per renewal when operational availability is needed; leave both zero for inherent availability.
- Select Calculate. Reset restores the worked example and known-times mode.
- Read availability first, then the uptime/downtime budget and rate metrics. Correct every red warning before use.
- Do not use this steady-state screen for nonrenewable items, wear-out, clustered failures, time-varying repair resources, safety claims, or contractual guarantees without a validated stochastic model and field data.
Worked example
For MTBF = 1000 h, active MTTR = 10 h, no added delays, and a 8760 h year, A = 99.010%, expected downtime = 86.733 h/year, λ = 0.001 h⁻¹, and μ = 0.1 h⁻¹. This means the renewal-average model expects about 99.01% uptime, not a guarantee for any individual year.
Equations used
MRT = MTTR + MDP + MLDTA = MTBF / (MTBF + MRT)U = 1 − Aλ = 1 / MTBF; μ = 1 / MTTRTd = UTp; Tu = ATpMTTR = MTBF(1/A − 1) − MDP − MLDTMTBF = A·MRT / (1 − A)MTBF is mean operating time between failures; MTTR is active repair time; MDP and MLDT are average planned and logistics delay per renewal; MRT is total mean restoration time; A and U are dimensionless availability and unavailability; λ and μ use h⁻¹; Tp, Tu, and Td use hours. All times are nonnegative magnitudes; no signed convention applies.
Theory and method
The calculator applies renewal-reward steady-state availability: each representative cycle contains MTBF hours operating and MRT hours unavailable. Setting delays to zero gives inherent availability. Adding planned and logistics delays provides a simplified operational-availability screen. Reciprocal λ and μ values are constant-rate summaries, not proof that exponential failure and repair distributions fit the asset.
Assumptions include repairable renewal behavior, statistically representative means, one consistent boundary for uptime/downtime, and stable support conditions. It excludes preventive-maintenance frequency modeling, redundant-system logic, common-cause failures, queueing, spare shortages beyond the entered mean delay, and confidence intervals. References: IEC 60050-192 dependability terminology; Reliability Analytics Toolkit, System Availability Calculator; ReliabilityCalc Availability Calculator. For event-driven repair-resource and reliability refinement, continue with an appropriate TriboSolver reliability workflow.