Maintenance planning and scheduling software is two jobs in one product, and the two are different. Planning is deciding what a job needs before it is done: the procedure, the parts, the permit, the hours. Scheduling is deciding when it is done and by whom, against the hours the team has. A maintenance planner software product holds the first; a maintenance schedule program raises the second each week. This page says what each half has to hold, and what a small team, which usually has one person doing both in spare moments, needs from either.
Planning: what a job needs
For each preventive task and each corrective work order above routine: the procedure or checklist, the parts and whether they are on the shelf, the tools, the permit and isolation steps, the estimated hours, and any contractor or access needed. Planned jobs take fewer hours because the technician arrives with everything; this site's worked example prices the same work at 1.1 hours planned against 3.4 as a breakdown, and part of that difference is planning. Planner software holds the job plan against the task so that it arrives with every work order.
Scheduling: when and by whom
Each week, the schedule takes the work orders due, the corrective work by priority, and the estimated hours, and fits them to the technicians available after the expected reactive load. The output is a weekly plan by person and by day, with slack for breakdowns. The schedule program raises the preventive work orders from their triggers, shows the overdue list, and lets the supervisor move jobs. A schedule that is levelled to the hours available is one the team can comply with; one that is not produces deferral.
What a small team needs
One person plans and schedules, and the software has to make that an hour a week rather than a day. A job plan attached to each task once, so it is not rewritten. The weekly list by priority with hours, produced by the system. A drag of jobs between days. And the overdue list on the first screen. The planning and scheduling modules of a mid-market CMMS do this; a small team rarely needs the standalone planning products built for plants with a planning department.
Without the software
The maintenance log worksheet on this site holds the tasks with their estimated hours and due dates, which is enough to level a month's load by hand and to see what slipped. A team that has done that for a quarter knows its preventive hours and its reactive load, and it is those two numbers that the scheduling software is bought to balance.
Questions people ask about maintenance planning and scheduling software
Is a maintenance planner the same as a scheduler?
No. The planner prepares jobs; the scheduler places them in the week. Large plants employ both; small teams have a supervisor doing both.
Does scheduling software need estimated hours?
Yes, or it cannot level the load. Estimates improve as actual hours are recorded on closed work orders.
How much slack should the weekly schedule keep for breakdowns?
The reactive share of last month's hours, roughly. This site's example runs 35% reactive, so a third of the week is slack until the share falls.