Why generic maintenance intervals fail without local context

Even the severe schedule is generic

Picking the severe column is better, but it is still a national average of harshness. It does not know that your routes climb two thousand feet, that your water is hard, that your fuel supplier changed last year, or that one depot parks outside while the other parks under a roof. Local conditions compound in ways no printed schedule anticipates, and the only instrument that detects the compounding is a technician's attention over years: oil that keeps coming back dark early, belts that never make it to the interval, a bearing that wears on one route and not another.

That attention produces overrides. A veteran quietly moves a unit to a shorter oil interval after the second early failure. This is the mechanism by which a fleet's schedule slowly becomes correct, and it is a form of institutional knowledge, which means it has the same weakness as all institutional knowledge: it usually lives in one or two heads. Our article on what leaves when a veteran mechanic retires covers what happens next.

The failure mode: reverting to the book

When the person who held the overrides leaves, the fleet does not keep their schedule. It reverts to the printed one, because that is what is written down and defensible. The early failures that taught the original lesson return, and the tuition gets paid twice. Nobody decides this. It happens by default, the way an unwatered plant dies.

The overrides can also fail in the other direction. An adjustment made for a 2012 engine may be needless on the 2022 replacement, and a habit nobody can explain is hard to retire. An override without its reason attached cannot be audited, so it either ossifies or evaporates.

What a durable local schedule looks like

The fix is to treat interval adjustments as recorded, reasoned decisions instead of private habits. Each override should carry four things:

• What it applies to: which units, model years, or routes.
• The trigger conditions: climate, terrain, duty cycle, season.
• The adjustment itself, next to the manufacturer value it replaces.
• The reason, with the history: what failed, how often, what changed after the adjustment.

Written this way, an override is auditable. When the fleet buys the next generation of the vehicle, someone can ask whether the reason still applies instead of inheriting a rule blind. And when its author retires, the schedule survives them. Capturing the reasons is interview work, and we describe the method in how to run knowledge capture interviews. The wider practice sits in the pillar guide to preserving institutional fleet knowledge.

Start with the units that grumble

No fleet documents every interval at once. Start where the book and reality disagree loudest: the units with repeat early failures, the routes that eat consumables, the season that fills the bays. Ask the technicians which intervals they already ignore, because the informal schedule they are running is your first draft. The goal is not a perfect schedule. It is a schedule whose reasons are written down.

How YardWise fits

YardWise keeps manufacturer schedules and local overrides in the same searchable place. A veteran records an override with its conditions and its reason, a supervisor approves it, and from then on a technician who asks about an interval sees the book value and the local note together, each citing its source. See how it works. The practice of writing down the why does not need to wait for software.