How is this different from robot OEE?

OEE multiplies availability by performance and quality, so it sizes the output loss. This page stays with reliability: failures, repair time and the availability they imply.

Where do MTBF and MTTR come from?

From your maintenance log over the same period: total run hours divided by the number of failures for MTBF, total repair hours divided by failures for MTTR. Use at least a quarter of data.

Does planned maintenance count against availability?

Only when it sits inside the scheduled window and the robot was not free to run. Log planned stops separately so you can tell them from failures when reading the gap.

What does predicted downtime tell me?

It applies inherent availability to your scheduled hours: the repair hours the current MTBF and MTTR imply when every repair starts at once. Compare it with logged downtime to size the waiting.

Robotics & Automation calculator

Robot Availability Calculator

Separate the hours your robot actually ran from the availability its reliability allows. Enter run and scheduled hours for one period, then the MTBF and MTTR from the maintenance log.

What this calculator does

Run availability from your hours log plus inherent availability from MTBF and MTTR, with the downtime those repairs predict.

Formula used

Run availability (%) = available run hours ÷ scheduled cell hours × 100
Inherent availability (%) = MTBF ÷ (MTBF + MTTR) × 100
Reliability gap (points) = inherent availability − run availability
Predicted downtime (hr) = scheduled cell hours × (1 − inherent availability ÷ 100)
Gap to target (points) = target availability − run availability

Inputs explained

Available Run Hours: Hours the robot was available to run, from the cell log.
Scheduled Cell Hours: Scheduled production hours in the same period, after planned stops.
Mean Time Between Failures: Average run hours between failures, from the maintenance log.
Mean Time to Repair: Average hours to restore the robot after each failure.
Target Availability: Your reliability goal for run availability in this period.

How to use the result

Best suited to reporting cell reliability in a weekly review, comparing robot models on service data, deciding which spares to keep at the cell.
A handful of failures gives a noisy MTBF; use a quarter of logs or more. Inherent availability assumes repair starts at once, so it is a ceiling, not a forecast. Planned maintenance and tool changes can hide inside downtime; split the log first.

Current U.S. benchmarks

Global copper trades at $13,543 per tonne (IMF via FRED, Jul 2026), up 38.6% in a year, and U.S. industrial electricity averages 9.77 cents per kWh. Both feed electrified-hardware unit economics.

Common questions

How is this different from robot OEE? OEE multiplies availability by performance and quality, so it sizes the output loss. This page stays with reliability: failures, repair time and the availability they imply.
Where do MTBF and MTTR come from? From your maintenance log over the same period: total run hours divided by the number of failures for MTBF, total repair hours divided by failures for MTTR. Use at least a quarter of data.
Does planned maintenance count against availability? Only when it sits inside the scheduled window and the robot was not free to run. Log planned stops separately so you can tell them from failures when reading the gap.
What does predicted downtime tell me? It applies inherent availability to your scheduled hours: the repair hours the current MTBF and MTTR imply when every repair starts at once. Compare it with logged downtime to size the waiting.

Last reviewed 2026-10-01.