Deciding to do preventive maintenance is one thing; deciding exactly which tasks happen on which assets at which intervals is another, and that second decision lives in the PM schedule. It is the working plan that turns a maintenance philosophy into dated, assignable work. This guide explains how a PM schedule assigns tasks to assets, how intervals are chosen and adjusted, how compliance is measured, and how live runtime and condition data can make the schedule react to the process rather than to the calendar alone.
Preventive Maintenance (PM) Schedule in one line: A preventive maintenance (PM) schedule is the structured plan that assigns recurring maintenance tasks - calibrations, inspections, lubrication, filter changes - to specific assets on defined intervals, whether measured in calendar time, equipment runtime, or cycle counts. It is normally held in a CMMS, which generates work orders automatically as each interval comes due and tracks whether the work was completed on time. The schedule is the difference between an intention to maintain and an actual, auditable cadence of maintenance activity.
Building a PM schedule starts with the asset register: every pump, separator, transmitter, valve, and compressor that warrants recurring attention. Each asset is given one or more PM tasks, and each task is given a trigger. Some triggers are calendar-based - inspect a relief valve every twelve months, replace a filter every ninety days - and are easy to plan because they fall on predictable dates. Others are runtime-based, such as changing compressor oil every so many operating hours, or cycle-based, such as servicing a valve after a set number of strokes. Runtime and cycle triggers matter because two identical pumps that run very different duty cycles should not be maintained on the same clock.
The interval itself is where judgement enters. A first pass usually comes from the manufacturer's recommendation, an applicable code or company standard, or the interval inherited from similar equipment. That starting point is deliberately conservative, because an interval that is too long risks a failure while an interval that is too short only wastes labor. Over time the interval should be revisited using real evidence - inspection findings, calibration as-found results, failure history - so that assets that keep passing early can have their frequency relaxed and assets that keep drifting or failing can be caught more often. A good schedule is never frozen; it is a set of hypotheses about how often each thing needs attention, refined as data accumulates.
Each PM task also needs a defined procedure, an estimated duration, the trade or crew that performs it, and any parts or standards required. Without that detail the schedule produces a due date but no way to actually execute the work efficiently. Mature schedules group tasks sensibly too, so that a technician visiting a remote well pad performs every task due there in one trip rather than making separate journeys for a lubrication route and an inspection route that happen to fall in the same week.
A schedule only delivers value if the work actually happens near its due date, and that is what PM compliance measures. The common form is the ratio of PM tasks completed within their allowed window to the total PM tasks that came due in a period. A high compliance figure means the plan is being executed as designed; a low one means work is slipping, which erodes the whole premise of preventive maintenance because deferred tasks let the very failures the schedule was meant to prevent creep back in.
Compliance is usually judged against a grace window rather than an exact date, since a task due on a weekend or during a shutdown reasonably lands a few days later. What matters is that the window is defined and honored, not that every task hits its nominal date. Tracking compliance by asset criticality is more revealing than a single plant-wide number, because slipping the annual inspection on a critical custody meter is not the same as deferring a lubrication route on a spare pump. A schedule that reports strong overall compliance while quietly deferring its most important tasks is telling a comforting but misleading story.
Compliance data also feeds back into interval decisions. If a task is consistently completed but its findings are always clean, that is evidence the interval could be lengthened. If tasks are chronically late because the workload exceeds available labor, the honest response may be to re-scope the schedule - eliminating low-value PMs, extending intervals where reliability data supports it, or moving suitable assets to condition-based triggers - rather than pretending a plan will be executed that the crew has no capacity to execute.
A traditional PM schedule runs on the calendar and on manually entered runtime readings, which means the plan reacts slowly and only to information someone remembers to record. When the schedule is fed by live SCADA data, it can react to how equipment is actually being used. A cloud SCADA such as Merobix continuously reads runtime hours, start-stop counts, flow, temperature, and vibration-related tags from field devices, and those values can drive runtime- and cycle-based PM triggers automatically, so a compressor that ran hard all month comes due sooner than one that idled, without anyone transcribing an hour meter.
Condition data pushes this further toward dynamic scheduling. Instead of servicing on a fixed interval regardless of state, the schedule can watch a measured indicator - a rising bearing temperature, a widening filter differential pressure, a calibration reading trending toward tolerance - and raise the maintenance need when the evidence warrants it. This blends preventive and condition-based approaches: fixed-interval tasks remain the backbone, but the interval flexes when the data says an asset is degrading faster or slower than assumed. The schedule stops being a pure calendar and becomes a plan that listens to the process.
For oil and gas operators watching many dispersed sites, this coupling of SCADA to the schedule is what makes a large PM program manageable. Real-time runtime and condition tags flow from remote wells, tank batteries, and gathering systems into the platform, which can raise a work order the moment a runtime threshold is crossed or a condition drifts, and route it to the right technician. The result is fewer wasted trips servicing equipment that did not need it and fewer surprises from equipment that quietly aged past its assumed interval.
Preventive maintenance is the overall strategy of servicing equipment before it fails, while a PM schedule is the concrete plan that puts that strategy into practice. The schedule names the specific tasks, the assets they apply to, and the intervals on which they recur, then drives work orders as each interval comes due. In short, the strategy decides why you maintain proactively and the schedule decides exactly what, where, and when.
Intervals usually start from a manufacturer recommendation, an applicable standard, or the interval used on similar equipment, chosen conservatively so a failure is unlikely before the next task. Over time they should be adjusted using real evidence such as inspection findings, calibration as-found results, and failure history. Assets that consistently pass early can have their frequency relaxed, while assets that keep drifting or failing are serviced more often.
PM compliance is the share of due tasks completed within their allowed window, and a higher figure means the schedule is being executed as designed. Rather than fixate on a single target number, it is more useful to track compliance by asset criticality, since deferring an inspection on a critical custody meter is far more serious than deferring a lubrication route on a spare pump. Chronic non-compliance is a signal to re-scope the schedule to match available labor.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.