How do you calculate a preventive maintenance interval?

Divide the historical hours between service-triggering failures by average run hours per day to get a calendar interval, then divide by a safety multiplier. With 3,200 failure hours, 20 run hours/day, and a 1.25x multiplier, that is 160 days historical, giving a recommended PM interval of 128 days.

What is a good PM safety multiplier?

Most teams use 1.2 to 1.5. A 1.25x multiplier means you service at 80% of the historical failure interval, a reasonable buffer for a known wear pattern. Critical or hard-to-access assets justify 1.4 to 1.5; well-instrumented, low-consequence assets can run closer to 1.1.

Why divide by a safety multiplier instead of using the historical interval directly?

The historical interval is the average point at which failures occur, meaning roughly half of failures happen before it. Dividing by the multiplier pulls the PM forward so you intervene before that average, catching most failures while they are still preventable.

Preventive maintenance interval vs MTBF, what is the difference?

MTBF (mean time between failures) is a measured reliability statistic in hours. The PM interval is an actionable schedule in days derived from MTBF, run hours, and a safety factor. MTBF tells you how the asset behaves; the PM interval tells you when to put a wrench on it.

Should I use run hours or calendar time for PM scheduling?

If the asset only degrades while running, run-hour-based PM is more accurate. This calculator bridges the two: it uses run hours to find the failure interval, then expresses the schedule in calendar days so it slots cleanly into a weekly planning board.

How often should I recalculate the interval?

Recalculate whenever you log a new service-triggering failure or change the asset's duty cycle. As failure history grows, your MTBF estimate tightens, and a shift in average run hours per day directly moves the recommended interval.

Maintenance & Reliability calculator

Preventive Maintenance Interval Calculator

The preventive maintenance interval is the number of calendar days you should wait between scheduled PM tasks before failure risk climbs unacceptably. Reliability engineers and maintenance planners derive it by converting historical mean time between failures into calendar days, then pulling the interval in by a safety factor so PM lands before the asset reaches its wear-out zone. It matters because servicing too late invites unplanned downtime, while servicing too early wastes labor, parts, and machine availability. On a CMMS-driven shop floor, this single number drives the frequency field on every time-based PM work order.

What this calculator does

Estimate a protected PM interval in days from historical failure spacing, average daily run time, and a safety multiplier.
Use it when setting inspection or replacement frequency for failure-prone components without overmaintaining them.
It converts historical hours between service-triggering failures into a calendar-day interval, then divides by a safety multiplier to schedule maintenance before the typical failure point.

Formula used

Historical interval in days = historical hours between service-triggering failures ÷ average run hours per day
Recommended PM interval = historical interval in days ÷ PM safety multiplier

Inputs explained

Historical hours between service-triggering failures: Use the average run hours observed before failures or condition findings required service.
Average run hours per day: Use actual average daily operating hours for the asset or asset class.
PM safety multiplier: Use a value above 1 to shorten the protected interval and add conservatism.

How to use the result

Use it when setting or revising the frequency of a time-based PM in your CMMS, especially once you have enough failure history to know the real mean time between failures.
It assumes failures are time- or run-hour-driven and roughly consistent; for assets that fail on cycles, load, or random infant-mortality patterns, calendar-based intervals mislead and condition-based monitoring is the better tool.

Current U.S. benchmarks

U.S. manufacturing runs at 75.6% of capacity (Federal Reserve, May 2026). New factory orders are up 2.3% year over year (Census).

Common questions

How do you calculate a preventive maintenance interval? Divide the historical hours between service-triggering failures by average run hours per day to get a calendar interval, then divide by a safety multiplier. With 3,200 failure hours, 20 run hours/day, and a 1.25x multiplier, that is 160 days historical, giving a recommended PM interval of 128 days.
What is a good PM safety multiplier? Most teams use 1.2 to 1.5. A 1.25x multiplier means you service at 80% of the historical failure interval, a reasonable buffer for a known wear pattern. Critical or hard-to-access assets justify 1.4 to 1.5; well-instrumented, low-consequence assets can run closer to 1.1.
Why divide by a safety multiplier instead of using the historical interval directly? The historical interval is the average point at which failures occur, meaning roughly half of failures happen before it. Dividing by the multiplier pulls the PM forward so you intervene before that average, catching most failures while they are still preventable.
Preventive maintenance interval vs MTBF, what is the difference? MTBF (mean time between failures) is a measured reliability statistic in hours. The PM interval is an actionable schedule in days derived from MTBF, run hours, and a safety factor. MTBF tells you how the asset behaves; the PM interval tells you when to put a wrench on it.
Should I use run hours or calendar time for PM scheduling? If the asset only degrades while running, run-hour-based PM is more accurate. This calculator bridges the two: it uses run hours to find the failure interval, then expresses the schedule in calendar days so it slots cleanly into a weekly planning board.

Last reviewed 2026-05-12.