Zum Inhalt springen
Anmelden
Alle Beiträge

Leitfäden · · 4 Min. Lesezeit

Preventive maintenance is a calendar problem

Recurring tickets, seasonal cadences, and per-visit budgets: a practical way to start fixing things before they break.

Bruegel's The Harvesters, field workers cutting, stacking and resting on a planned rotation
Pieter Bruegel the Elder, The Harvesters, 1565

Bruegel's harvesters are in no hurry. The wheat comes down in August because that is when wheat is ready, the stacks go up before the rain, and lunch happens under the tree because the afternoon is long. All of it is work arriving on time, painted in 1565.

Reactive is also a schedule

Skip the maintenance calendar and the equipment starts keeping one for you.

FEB 11 - boiler B down. no heat for two days. emergency callout, 4x rate JUN 3 - boiler B again. bearing seized, parts overnighted NOV 27 - boiler B. third time. same bearing.

Three emergencies, one calendar entry nobody made. A breakdown picks the coldest week of the year, bills at the callout premium, and takes the rest of your day hostage.

Reactive maintenance is still a schedule, just written by your equipment.

Move the work to your side of the calendar

Preventive maintenance is one decision, repeated: this asset, this task, every so many weeks. In fam. that decision becomes a planned ticket with a recurrence, and every visit lands on the calendar from day one. Each one arrives carrying what the job needs:

  • One owner per visit, so someone's name is on it before the day starts.
  • A checklist built for the task, so "checked the boiler" means twelve recorded answers.
  • A budget for what the visit uncovers: an allowance the technician can spend on what they find, with no second approval loop.
  • A record per visit, so February knows exactly what June found.

Plans meet reality, so the series bends without breaking: skip a date, move one visit, raise one visit's budget, and the rest of the schedule carries on as written.

Here is that shape as a worked example from the product demo:

Ticket #51247 is a working example from the product demo. Open the demo to work one.

Ticket #51247, a monthly food-safety audit as a planned ticket: twelve visits on the calendar from day one, each with an owner, a checklist and a budget. Open it to page through the visits.

Some cadences are seasonal

The Harvesters is one panel from a cycle; Bruegel painted the whole year, sowing to snow. Buildings run on the same mix of rhythms. Filters and greasing are monthly. The roof wants checking before the first storm, the chillers before the first heatwave, the gutters when the leaves come down. Wherever the interval comes from, write it into the system that generates the work, because the person who has done it longest will eventually change shifts.

Start with ten assets

Don't audit the whole building on day one. Pick the ten assets whose failure hurts most, give each a recurrence and a checklist, and let the first quarter of records tell you what the right intervals are. The calendar pays for itself the first time a bearing gets swapped in a planned Tuesday hour instead of a frozen February night.

Artwork: Pieter Bruegel the Elder, The Harvesters, 1565. The Metropolitan Museum of Art, New York. Public domain.

Als Nächstes lesen

Put the breakdowns out of business.

Kostenlose 30-minütige Tour

Wähle eine Zeit, die dir passt.

Ein 30-minütiger Rundgang mit einer echten Person. Zeiten in deiner Zeitzone, .

1 · Der Tag

Sprache auswählen