Hour-Meter vs Calendar PM
Use hour-meter PM for wear tied to runtime, calendar PM for aging or compliance, and condition checks where degradation can be measured.
In this guide
Why does the failure mode choose the PM clock?
Use this guide when a planner has monthly tasks that do not match actual equipment use or when spare parts arrive too early or too late.
Runtime drives oils, belts, filters, liners, and bearings on operating assets. Calendar time drives inspections, aging materials, compliance checks, and seasonal readiness.
What should decide hour-meter vs calendar PM?
Choose interval from failure mode: age-related, run-hour related, condition detectable, safety required, or run-to-failure with spare on hand.
Start with what the task is trying to prevent. Runtime is the better clock when wear is created by operation: oil loading, belt flex, filter dirt, liner wear, bearing grease life, or production hours. Calendar time is the better clock when risk ages while parked, season changes matter, readiness matters, or inspections are required by safety, regulatory, warranty, or insurer rules.
The useful planner choice names the failure mode, consequence, measurable degradation signal, severity, lead time, spare strategy, and whether run-to-failure with a stocked part is actually acceptable. A monthly task that really means "we do not know the hours" should not pretend to be a maintenance strategy. Related GO4FORGE paths include maintenance PM schedules, planner, filters, lubricants, belts, bearings, wear parts, and critical spares.
What PM context should travel with parts planning?
Send asset type, hours per week, duty severity, environment, current interval, failure history, lead time, and parts consumed per service.
Send asset type, hours per week, duty severity, environment, current interval, failure history, condition signals, lead time, service kit contents, parts consumed per service, shelf-life concerns, and whether the task is OEM, safety, regulatory, calendar, runtime, or condition based.
Do not let the parts shelf become the only evidence for the interval. Boundary: Safety, OEM, warranty, regulatory, and insurer requirements may set mandatory intervals independent of local usage.
Which clock is the asset really using?
Runtime, calendar time, condition, season, and compliance can all be valid clocks, but they should not be mixed without naming why.
A monthly task may be perfect for an inspection and wrong for a filter. A 250-hour interval may be perfect for a hard-running asset and irrelevant to a machine that sat idle for six weeks. Calendar time catches aging, weather, readiness, and required checks. Hour-meter time catches wear created by operation. Condition monitoring catches degradation that neither clock sees cleanly.
The planner should name the clock behind the task. "Monthly because the permit requires it" is different from "monthly because nobody knows the runtime." "Every 500 hours" is different from "every 500 hours unless dust load doubles." Once the reason is visible, the PM can be tuned without becoming folklore.
How does interval choice affect stocked parts?
The wrong PM clock either starves the shelf before service or fills it with parts that age before use.
Parts planning follows the interval. Filters, belts, grease, liners, and bearings need to arrive before the service window, but not so early that shelf life, contamination, or obsolete stock becomes the new problem. The PM task should carry lead time, kit contents, quantity used per service, and the evidence that changed the interval.
When an asset suddenly runs more hours, the crib should feel it before the failure does. When an asset sits idle, the calendar may still matter for seals, batteries, corrosion, inspections, and readiness. A good guide teaches the planner to ask which risk is aging and which risk is working.
Frequently Asked Questions
What is the next useful move?
Choose interval from failure mode: age-related, run-hour related, condition detectable, safety required, or run-to-failure with spare on hand.
What makes a quote answerable?
Send asset type, hours per week, duty severity, environment, current interval, failure history, lead time, and parts consumed per service.
When does this leave the catalog lane?
Safety, OEM, warranty, regulatory, and insurer requirements may set mandatory intervals independent of local usage.
Sources and Review Boundaries
Published by GO4FORGE. Editorial method. These notes help narrow sourcing evidence and selection risk; they do not replace the responsible site authority, OEM procedure, code requirement, or qualified engineering/safety review.
- GO4FORGE product knowledge files Internal product-knowledge references distilled into public decision guides.
- GO4FORGE RFQ evidence model Shop-floor evidence patterns for quotes, substitutions, and sourcing review.