Running a Fleet Blade Maintenance Programme

Standardise the interface, then schedule the work — the blade takes care of itself

A fleet programme turns blade maintenance from a series of emergencies into a cost line with a forecast. The two levers are standardisation and scheduling, and both are cheap.

✓ Standardising mounting patterns across machines
✓ Setting a spares level from your own failure data
✓ Reporting blade life so the budget stops guessing

BACK TO MAINTENANCE HUB

Standardise the interface, not the blade

Getting the mounting pattern and edge dimensions consistent across machines lets you carry fewer part numbers without compromising on which edge each route needs.

Fewer part numbers, same performance

Fleets that standardise the mounting interface typically cut their blade part numbers substantially while still running two or three edge classes by route type. The saving is in stock, handling and the time lost hunting for the right part.

Specifying once and holding it

A written specification that survives supplier changes is what stops the fleet drifting back into mixed part numbers. It is the same document covered in the selection cluster, applied at fleet scale.

Schedule rotation, inspection and replacement together

One calendar with three entries per machine is enough: pre-season inspection, mid-season rotation and the service intervals in between.

The spares level that prevents emergencies

Set the spare level from your own replacement rate over the two busiest weeks of the season, plus one set for the highest-duty machine. Fleets that calculate this carry less stock than fleets that guess, and run out less often.

Reporting blade life

Record specification, fit date, removal date and hours per edge. At season end that data produces a cost per operating hour, a replacement forecast and an evidence base for the next specification change.

Downtime is the cost the programme is really managing

A blade change in the yard is a scheduled task. The same change on a route during a storm is a lost shift, an angry client and a safety exposure.

Why the programme pays for itself

The material saving from a good programme is real but modest. The larger saving is the shift that did not stop, and that is what makes the case to a finance review rather than the price difference on the blade.

What to do first

Start with the pre-season inspection, the measurement records and a defined spare level. Those three items are implementable in a fortnight and produce most of the benefit; the rest of the programme follows from the data they generate.

Fleet programme questions

What is the single highest-value change for a fleet?

Standardising the mounting interface across machines. It reduces part numbers, simplifies spares and makes every other part of the programme easier to run.

How many spare blades should we hold?

Enough to cover your replacement rate through the two busiest weeks of the season, plus one set for the highest-duty machine. Calculate it from your own records rather than from a rule of thumb.

How do we justify the programme internally?

On downtime avoided rather than on blade price. A shift lost to a mid-storm blade change usually costs more than the annual saving on the blades themselves.

Should different routes use different edges?

Yes, where the duty genuinely differs. Standardise the interface and keep separate edge classes for high-mileage and light residential work.

How long before the programme shows results?

The pre-season inspection and spares level show results in the first season. Cost-per-hour reporting takes a full season to produce a usable baseline.