A maintenance schedule turns a preventive maintenance plan into dates. For each asset (or asset class) it lists the tasks, their interval — every 3 months, every 1,000 hours — and the next due date, which moves forward each time the task is completed.
Fixed vs floating schedules
A fixed schedule keeps the calendar (due every 1 January, 1 April…) even if a job is done late. A floating schedule counts from the last completion (due 90 days after it was actually done). Fixed schedules suit compliance inspections; floating schedules keep intervals consistent.
Why it matters
A schedule makes preventive maintenance visible: everyone can see what is due this week, what is overdue, and whether the team has the capacity to do it. Without one, PM depends on memory and slips as soon as the team gets busy.
In Asetavo
Recurring PM schedules sit on each asset and produce due lists. Automatically generating work orders from schedules, and maintenance-due alerts, are on the roadmap.