Preventive Maintenance Scheduling: Time-Based vs Usage-Based Automation and How to Choose the Right Trigger for Every Asset

PM scheduling is the systematic process of planning and triggering maintenance activities for physical assets before failure occurs, based on predetermined intervals of either elapsed time or accumulated usage. It answers three questions for every asset in the maintenance program: what maintenance is required, when is it due, and who is responsible for performing it.

The key word is predetermined. PM scheduling is the antithesis of reactive maintenance — it is the organisational commitment that maintenance will happen on a defined cadence regardless of whether the asset appears to need it. The value is not just in the maintenance tasks themselves. It is in the certainty they provide. An organisation with a running PM program knows which assets are due for maintenance in the next 30 days. It can plan labour, pre-kit parts, schedule production around maintenance windows and avoid the chaos of unplanned breakdowns. An organisation without a PM program knows only what broke last night.

Time-based PM scheduling triggers maintenance based on the passage of calendar time regardless of how much the asset was actually used during that period. Examples: oil change every 3 months, filter replacement every 6 weeks, annual statutory inspection on a fixed calendar date.

The EAM holds the last completion date for each PM task and the defined interval. It calculates the next due date automatically and generates a work order when the due date arrives or approaches within a configurable lead time window.

Advantages:

• Simple to set up and manage — no usage tracking infrastructure required
• Direct alignment with statutory and regulatory inspections which are always calendar-mandated
• Suitable for assets whose degradation is primarily time-driven: rubber seals, lubricants, calibration-sensitive instruments, safety equipment, outdoor structures

Limitations:

• Can lead to over-maintenance of low-utilization assets — a machine running 2 hours per day receives the same PM frequency as one running 20 hours per day, which is both financially inefficient and technically inaccurate
• For high-utilization assets, time-based PM may lead to under-maintenance if the asset accumulates usage faster than the calendar interval assumes

Usage-based PM scheduling triggers maintenance when an asset reaches a defined threshold of accumulated usage — measured in runtime hours, production cycles, kilometers driven, operating pressure cycles or any other quantifiable usage metric relevant to the asset class. Examples: bearing replacement every 8,000 runtime hours, vehicle service every 10,000 kilometers, pump seal inspection every 5,000 operating cycles.

The EAM tracks the current usage reading against the PM trigger threshold. When the reading approaches the threshold within a configurable alert margin the system generates an upcoming PM notification. When the threshold is reached a work order is automatically raised.

Advantages:

• Technically more accurate than time-based for most mechanical and rotating equipment — wear and degradation correlate with usage, not calendar time
• Eliminates over-maintenance of low-utilization assets and under-maintenance of high-utilization assets simultaneously

Requirements and limitations:

• Requires a reliable mechanism for capturing usage readings — manual meter entry, connected hour meters or IoT sensors
• Accuracy is entirely dependent on the frequency and reliability of usage data collection — an organisation logging runtime hours monthly will have PM triggers accurate to within one month; connected hour meters are accurate to the minute
• If reliable usage data cannot be collected, the theoretical advantage of usage-based PM collapses

Multi-trigger PM scheduling is the most accurate approach for critical assets. A multi-trigger PM fires on whichever threshold is reached first — either the time interval or the usage threshold.

Example: a vehicle service scheduled for every 6 months OR every 10,000 kilometers whichever comes first. If the vehicle covers 10,000 kilometers in 3 months the service is triggered at 3 months. If the vehicle covers only 4,000 kilometers in 6 months the service is triggered at the 6-month mark. Neither time-driven nor usage-driven degradation is left unaddressed regardless of how the asset is operated in any given period.

Multi-trigger PM is the standard approach for:

• Vehicles and mobile equipment
• Generators and standby power systems
• Compressors and pneumatic systems
• Any asset with both time-sensitive components (seals, lubricants) and usage-sensitive components (bearings, wear surfaces)

In Sapphire, multi-trigger PM schedules are configured with both a time interval and a usage threshold. The system monitors both simultaneously and raises the work order when either is reached first — no manual calculation or cross-checking required.

In a manual PM system the maintenance manager remembers which machines are due, calculates dates in his head or on a spreadsheet, calls the technician when he remembers and logs completion on a clipboard if it happens at all. This system works only as well as the individual and fails completely when that person is absent, distracted or overloaded with reactive work.

Automated PM scheduling in an EAM eliminates every human memory dependency in the PM process:

• The system knows every PM schedule for every asset and calculates due dates and usage thresholds continuously
• Work orders are generated automatically when triggers are reached
• The assigned technician receives the job instantly on their mobile device
• The supervisor is escalated to automatically if the work order is not accepted within the defined response window
• On completion, the next due date is recalculated automatically — no human calculation required

The maintenance manager's role shifts from remembering and chasing to reviewing compliance and resolving exceptions. PM compliance rate — the percentage of scheduled PM work orders completed on time within the defined window — becomes a measurable, manageable metric. A facility with manual PM typically has no idea what its PM compliance rate is. A facility with automated EAM scheduling knows it precisely and holds it above 85 percent as the operational target.

A well-configured PM schedule in Sapphire for a typical Indian manufacturing asset works like this:

• Asset is registered with its unique ID, manufacturer, model and commissioning date
• PM tasks are defined from manufacturer recommendations and historical maintenance data — each task specifying the activity, skill required, estimated duration and parts required
• Each task is assigned a time interval, a usage threshold or both
• The system begins tracking from the commissioning date or last completion date, whichever is more recent
• Upcoming PM work orders appear in the maintenance calendar with configurable advance notice — typically 3 to 7 days — allowing parts to be pre-kitted and labour to be scheduled
• On trigger, the work order is automatically raised, assigned to the designated technician and the parts list is generated
• The technician receives the job on their mobile app and can log execution, parts consumed and completion from the shop floor
• On close, the PM history is updated against the asset and the next due date is recalculated automatically

At no point does a human need to remember a date, calculate an interval or chase a technician manually. The process runs itself. The manager manages exceptions. This is what it means to move from a maintenance culture that reacts to one that plans. The PM schedule is the plan. The automation is what makes it happen every single time without fail.