How to build a preventive maintenance schedule that holds

You set up recurring PM that actually gets done by giving each task an owner, a time estimate, a parts kit and a booked machine stop, then spreading the due dates so every week fits the hours your technicians have. A schedule breaks on load before it breaks on intent: forty tasks all due the first week of the month can’t be finished by two technicians, so they slip, and the slips pile up.

This guide is for maintenance leads building or rebuilding a calendar PM program. Tasks that should fall due on run hours or part counts have their own guide: usage-based maintenance.

What is a preventive maintenance schedule?#

NASA’s reliability-centered maintenance guide defines PM as regularly scheduled inspection, adjustment, cleaning, lubrication, parts replacement, calibration and repair, set at predefined intervals of time, operating hours or cycles, and done regardless of the equipment’s condition.^[1] In IoTFlows, preventive maintenance is that schedule stored as a recurrence rule on a work order.

PM pays when it’s done. The US Department of Energy’s O&M guide estimates that a preventive program saves 12% to 18% in cost over a purely reactive one, and lists its costs plainly: it’s labor intensive and includes maintenance the equipment didn’t need.^[2] A schedule that holds keeps the savings and trims the second list.

Build the task list from the machines#

A PM schedule starts as a list of machines, not a list of dates. Build it in this order.

1. List every machine by name and ID

   One row per machine, with the identifier the floor uses: CNC-04 Haas VF-2, PR-02 200-ton press. A task that names “the mills” has no single owner and gets done on none of them.

2. Rank each machine by what a failure costs

   Ask whether a failure stops shipments or the line’s slowest machine, creates a safety hazard, or leaves no backup to take the work. A press with no twin that feeds two assembly cells ranks above a third saw in a cell of three. Pricing an hour of downtime puts a number on each.

3. Pull tasks and intervals from the manual

   Copy each task and interval from the manufacturer’s maintenance section. NASA’s guide adds that intervals should reflect the machine’s location, application and operating environment, and that schedules need adjusting where parts and service are hard to get.^[1]

4. Add every task a regulation dates

   OSHA requires each mechanical power press the standard covers to be inspected and tested at least once a week for the condition of its clutch/brake mechanism, antirepeat feature and single-stroke mechanism, unless the press meets the standard’s control-reliability and brake-monitoring requirements. The standard also requires a record of each maintenance task, with its date, the signature of the person who did it and the press’s identifier.^[4]

5. Cut tasks that prevent nothing

   Delete tasks nobody can tie to a failure mode. NIST relays an estimate that preventive maintenance is applied unnecessarily up to 50% of the time in manufacturing.^[3]

Decide which machines get PM#

Not every machine needs a PM task. NASA’s guide reports that more than 90% of the hardware analyzed showed no adverse age-reliability relationship, and that an arbitrary preventive task often raises the failure rate by restarting early-life failures.^[1] The failure patterns behind each maintenance strategy explain why.

Write each task so anyone can do it#

A task that only its author can do gets skipped when the author is out. Write each one as a card, or as a work order in a CMMS, with these fields.

The estimate is the field most schedules leave blank, and it’s the one the rest of this guide depends on. Record it as minutes on the work order, as the time estimate field does, and correct it from what the job takes.

Size the workload before you set dates#

Before any task gets a date, add up how many technician hours the whole list needs in a year. Divide by 52 for the average week.

Take a hypothetical job shop with 10 CNC machines, 2 mechanical presses and 2 air compressors. Its PM list after the steps above looks like this.

The list needs 406 hours a year, or 406 ÷ 52 = 7.8 hours a week. Now compare that with the time you have. Two technicians give 80 hours a week, and if reactive work averaged 55 hours a week last quarter, 25 hours are left for planned work.

At 7.8 hours a week, the list fits with room to spare. It still fails if the hours land in the wrong weeks.

Level the load across the weeks#

The quickest way to build a PM schedule is to enter every task on the day you build it. Every interval then starts on the same date, and every task with a shared interval comes due together, forever.

Week 1 needs 20 hours more than the technicians have. Those 20 hours roll into weeks that are already full of reactive work, and by week 5 the next wave arrives on top of them. That’s how a schedule stops holding in its first month.

Three rules keep a schedule level:

• Stagger first due dates. Give each machine’s task a different first date. The interval carries the stagger forward on its own.
• Nest the intervals. Use intervals that are multiples of each other: 1, 4 and 12 weeks. Start a machine’s 12-week inspection in a week its 4-week task is due, and the two land together every time, so both happen in one stop.
• Cap the week, not the month. Check the busiest week against the hours left after reactive work, not the monthly total.

An annual task doesn’t nest into a 4-week cycle, so place it by hand. Ten 6-hour spindle checks in one week is 60 hours; one a month is 6.

Fixed or floating intervals?#

Every PM schedule makes one more choice, often without knowing it. A fixed interval counts each due date from the first one, so a late job doesn’t move the next. A floating interval counts the next due date from the day the last job was finished.

A fixed interval has a smaller cost: a job done a week late leaves only 3 weeks to the next one. The technician services a part that has worn less, and the year keeps all 13 services.

Choose fixed when a regulation or contract dates the task, when tasks share a stop, or when you book stops with production weeks ahead. Choose floating only when what matters is the time since the last service, such as a lubricant with a service life measured from the day it’s applied. When what matters is how much the machine ran, you don’t need either: put the task on a run-hour or part-count meter, which floats on usage by design.

Book the stop with production#

A PM that needs the machine stopped needs a slot on the production schedule. Without one, the technician arrives, finds a job running, and the task waits for a stop that never comes.

Book the stop when the machine is already down or lightly loaded:

• A planned changeover. A 3-hour inspection on a Haas VF-2 fits beside a fixture change that already stops the machine.
• An unscheduled shift. A machine that runs two shifts has a third with nobody waiting on it.
• The last hours before a weekend, when a missed restart costs the least.

Give the planner the dates a week or more ahead, with the estimate from each task card, so the production schedule loads around them. Then log the stop under a reason code marked as planned downtime, so the PM doesn’t show up as a breakdown in your downtime reports.

Measure PM compliance and adjust#

A schedule holds when you can see that it holds. The number that shows it is PM compliance.

Decide the window before you measure, and write it down. For example, a task every 4 weeks might allow 3 days either side of its due date. A regulation-dated task allows nothing past its date: a weekly press inspection is due within the week.

The 6 misses matter more than the percentage. Give each one a cause from a short list: no stop booked, part missing, estimate too short, technician pulled to a breakdown, or task not needed.

Each cause has a different owner. A missing part goes to whoever stocks the shelf, and a short estimate goes back onto the task card.

Adjust intervals from what you find#

The as-found field on each task card is the evidence for changing an interval. When three services in a row find the part like new, lengthen the interval one step. When one finds it worn past its limit, shorten it.

Don’t set an interval from MTBF. NASA’s guide notes that MTBF is often the starting point for PM intervals, but it gives only the average age at failure, not the most likely one, and says nothing about whether failures rise with age.^[1]

Schedule PM in IoTFlows#

In Maintain, a PM is a recurrence rule on a work order. The rule takes an interval, a weekday set, an optional end date and a timezone, and counts every date from the first due date, so intervals stay fixed.

Set the rule’s timezone to the plant’s, so a 6:00 AM Tuesday task lands on first shift wherever the planner sits. A weekday set lets one rule cover a Monday, Wednesday and Friday greasing round.

Each work order carries what this guide puts on a task card: the machine, an assignee, a time estimate, a checklist and required parts, which Inventory reserves when the work order is created. Usage-driven tasks go on a meter. Altium Packaging inspects its Slide Knife that way, every 100,000 bottles, with the work order opened automatically.

See how Maintain ties every PM to the machine it serves.

Before you call the schedule done#

• Every task names one machine, one owner, a time estimate, a parts kit and the machine state it needs.
• Every task traces to the manual, a regulation or a failure you have seen.
• The weekly PM hours fit inside the time left after reactive work, in the busiest week, not on average.
• First due dates are staggered, and intervals nest so tasks on one machine share a stop.
• Each task’s interval is fixed unless the time since the last service is what matters.
• Stops are booked with production at least a week ahead, under a planned reason code.
• PM compliance is measured against a written window, with a cause recorded for every miss.
• Intervals change only from as-found records, never from MTBF.