All articles

What a Maintenance Strategy Is and What a Maintenance Schedule Is Not

A maintenance schedule is the list of tasks and dates. The strategy is the reasoning that produces it. Most organisations hold the schedule, assume it contains the strategy, and let both stay fixed while the asset ages.

No. 33 · · Abhijit Dimble · maintenance governance through-life

Strategy comes first. A maintenance strategy is the reasoning about which failure modes matter, which consequences are unacceptable, which tasks address them, and why the intervals sit where they do. It starts from the evidence gathered when the equipment was selected: the margin against the design specification, the factory tests, the certification, and the installed trials. That evidence is the first data the strategy rests on.

What the schedule is

The schedule is what the strategy produces. It is a list of tasks and dates. It is an output. It follows the strategy and cannot replace it. A schedule without a strategy behind it is a list nobody can explain.

Why mixing them up is costly

A schedule carried without its reasoning cannot be questioned. It gets followed blindly, or it gets cut under pressure. When it is cut, nobody knows what the cut removes, because the reason each task existed was never kept with the task.

There is a simple way to tell which one an organisation holds. Ask why an interval is what it is. If the answer is that the manual says so, the organisation holds a schedule and not a strategy.

The schedule that never changes

Most schedules, once set, never change. The asset does. It ages under its operations and its working environment. Wear patterns shift. Duty changes. The failure behaviour moves while the intervals stay exactly where they were first written.

A schedule that was sensible on the day it was set drifts out of step with the asset it was written for. Nobody decided to let that happen. It happened because nothing in the process asked for the schedule to be revisited.

The strategy that never changes either

The strategy often stays fixed too. It should change when the routines change. How the asset is actually used is the signal. A new operating pattern, a different environment, or a change in how often the equipment is run all alter what the strategy was reasoning about.

Adjusting the intervals underneath is not enough when the reasoning above them has moved. The strategy itself needs to be revisited, and the record should say why.

Data that flows both ways

Operating data is rarely shared with the manufacturer, within the contractual and security arrangements that apply. That is a missed opportunity for both sides. The manufacturer learns how the equipment behaves in real service, which helps them improve it. The operator receives insight in return, which sharpens the strategy and the schedule.

A strategy fed only by the original datasheet and the operator’s own memory is working with less than it could have.

Three measures

A regime also has to earn confidence. Three measures show whether it does. The cost of the regime and what drives that cost. The time saved by it. The value gained from it. Together they let a company judge whether its maintenance is paying its way.

Cost has to be read carefully. It is measured against what the regime protects. It is never the reason to cut the regime. A strategy led by cost repeats a failure already described elsewhere, where cost leads and capability quietly erodes.

Why confidence depends on them

Without these measures, a company cannot tell whether its maintenance regime is working. It can only trust that it is. Trust is not confidence. Confidence comes from being able to show that the regime costs what it should, saves the time it should, and returns the value it should.

What confidence rests on

Confidence in a maintenance regime rests on four things. A strategy that leads. A schedule that moves with the asset. Data that flows in both directions. Measures that show the regime paying its way. An organisation missing any one of them holds a list of tasks and hopes it is enough.