A maintenance schedule is the distribution of the plan's tasks across the calendar, balanced against the team's capacity. It is the bridge between the maintenance plan, which defines what to do, and the weekly program, which closes who does it and when. A well-built schedule answers on the spot: what preventive load do we have in week 37, and does it fit?
The three horizons of the schedule
Annual: the 52-week plan
A view of the whole year, week by week, with every preventive and cyclic job plotted. It exists to spot collisions with the production calendar, concentrate same-asset jobs in the same window and anticipate long-lead material purchases.
Monthly: the fine adjustment
Four to five weeks ahead, with the month's reality: confirmed shutdowns, prioritized backlog filling the gaps, known team absences.
Weekly: the program
The closed agenda of the week, job by job, with a named technician. Here the schedule becomes commitment, and schedule adherence starts being measured.
How to build the 52-week plan
The method is direct: list the cyclic tasks with their frequencies; convert each into occurrences over the year (a monthly one becomes 12 marks, a quarterly one 4); add up the hours per week; and compare against the team's net capacity (total hours minus vacations, training and the corrective reserve, which in practice consumes 20 to 40% depending on plant maturity). Where the sum exceeds capacity, shift flexible-interval tasks into the empty weeks. The classic visual result is the assets-by-weeks matrix with intervention marks.
Balancing: the schedule's honesty test
A schedule that ignores capacity is fiction with dates. Three checks separate real from decorative: does the weekly load fit the net capacity (not the theoretical one)? Does the corrective reserve reflect the plant's history or a wish? Are the windows negotiated with production written down or in someone's memory? When the answers fail, the symptom shows in the indicator: schedule adherence collapsing and backlog silently growing, as the maintenance KPIs guide shows.
From spreadsheet to system
The spreadsheet solves year one and charges dearly afterwards: no automatic triggering, no real-time capacity view, no rescheduling trail. In the mature flow, orders are born from the plan in the system and the scheduler works the week on a Gantt with crew occupancy, dragging what needs to move; it is the scheduling routine described in the planning and control guide and what maintenance planning software delivers on top of SAP.
Frequently Asked Questions
What is a maintenance schedule?
It is the distribution of the maintenance plan's tasks across the calendar, on annual (52 weeks), monthly and weekly horizons, balanced against the team's real capacity.
What is the 52-week plan?
It is the annual maintenance schedule: every cyclic task plotted week by week across the year, with the hour totals compared to each week's capacity. It exposes overloads and production collisions before they become crises.
How much capacity should be reserved for corrective work?
It depends on maturity: reactive plants consume 40% or more of capacity on corrective work; mature operations run near 20%. The right number is your own recent history, revised quarterly.
What is the difference between schedule and weekly program?
The schedule distributes load across the calendar on medium and long horizons; the program closes the week's agenda with named technicians and agreed windows. Adherence is measured against the program.
