Maintenance & Reliability worked example

Planned Downtime Percentage at 9.2% planned downtime target: a worked example

What does the result look like when planned downtime target reaches 9.2%? The full calculation is worked below with real intermediate numbers. Use it when balancing PM discipline against capacity expectations and shutdown planning targets.

The inputs for this scenario

Planned maintenance hours: 48 hr (unchanged)
Total available hours: 720 hr (unchanged)
Planned downtime target: 9.2 % (raised for this scenario; the documented default is 8)

Working through the calculation

Applying the documented formula (Planned downtime percentage = planned maintenance hours ÷ total available hours × 100) to the inputs above produces each figure below.
At this operating point the engine returns 6.67 % for planned downtime share, the number this scenario is built around.
At this operating point the engine returns 2.53 points for gap to planned downtime target.
At this operating point the engine returns 48 count for planned maintenance hours.
At this operating point the engine returns 720 count for available hours.

How this compares with the baseline

Against the tool's baseline example, where planned downtime target sits at 8% and the headline result is 6.67 %, this scenario lands almost exactly on the baseline at 6.67 %.
A figure at this level is achievable when planned downtime target is genuinely sustained, not just peaked for a shift. It treats all planned hours as equal — it does not distinguish high-value predictive work from low-value calendar-based PMs that may not be needed.

Results at a glance

Planned Downtime Share: 6.67 % (headline result)
Gap to Planned Downtime Target: 2.53 points
Planned Maintenance Hours: 48 count
Available Hours: 720 count

Run it with your numbers

Every input above is editable in the live Planned Downtime Percentage calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.