Preventive maintenance that follows how your machines actually run.
Schedule every PM on the trigger that matches its wear: calendar days, real run-hours, cycle counts or machine condition. Checklists at the machine, live overdue countdowns on the floor and the evidence your auditors ask for, on the same platform that measures your OEE.
A PM schedule on paper is a list of good intentions.
The calendar doesn't know the shift pattern
A 30-day PM is late on a machine running three shifts and early on one running one. Same task, same calendar, opposite mistakes.
Skipped PMs vanish until they break something
Nobody decides to skip a PM. It slides behind production, then disappears. A live overdue count makes skipping a visible decision.
“Done” means a tick, not a record
What was checked, which readings, what was found. Without that, PM compliance is a guess and an audit finding waiting to happen.
Match each task to what actually wears it out.
Lubrication wears with running time, dies wear with strokes, calibration drifts with the calendar and bearings wear on their own schedule. One machine can carry all four.
Every N days, weeks or months
For tasks that age with time rather than use: electrical panel and earthing checks, safety devices, calibration and statutory inspections. The machine does not need to run for these to fall due.
Every 6 months
Every month
Every quarter
Every N hours of actual running
Counted from the machine's real on-time as recorded by monitoring, not assumed from the shift pattern. A machine running three shifts reaches its service point three times sooner than one running one, and the schedule moves with it automatically.
Every 500 run-hours
Every 250 run-hours
Every 100 run-hours
Every N cycles, parts, strokes or shots
For wear that follows work done: press clutches and dies, mould ejectors, chucks, fixtures and gripper mechanisms. Counts come from the machine automatically, so nobody reads a counter at shift end.
Every 50,000 strokes
Every 100,000 shots
Every 20,000 parts
Raised when the machine asks for it
A task created automatically when vibration, temperature or the machine's health score crosses a limit you set. This is where preventive meets predictive: the PM appears because the data says the component needs attention now.
Health score below 70
Oil temperature above limit for 3 days
2× running-speed vibration rising
Is your calendar PM early or late on this machine?
Set the service interval the manufacturer gives in run-hours and the calendar interval you use today, then move the utilisation. The same calendar is wrong in opposite directions on busy and quiet machines.
From task library to closed loop, without a register.
A task library per machine
Checklists by machine and machine type, with the steps, safety isolation, tools and spares each task needs.
Due on the right signal
Calendar, run-hours, counts or condition. Tasks fall due by themselves; nobody maintains a spreadsheet of due dates.
The right person knows
Assigned technicians are alerted on WhatsApp or email, and overdue tasks escalate automatically.
Done at the machine
Step-by-step checklist with readings, notes and photos. The machine's PM time is recorded as planned maintenance, not a breakdown.
Signed off, not ticked
Supervisor sign-off closes the task. Every record is kept per machine and searchable for the audit.
Learn which PMs work
Compliance by machine and technician, MTBF and MTTR, and breakdowns that followed a PM, so intervals can be tuned.
PM plans that fit the machine, not a template.
Typical tasks and the trigger each one runs on. Your library starts from your own checklists and is tuned from there.
CNC machining centres
- HRSSpindle and way lubrication
- HRSChiller and coolant filters
- CYCTool changer gripper check
- CBMSpindle bearings on health score
Power presses
- CYCClutch-brake inspection by strokes
- CYCDie sharpening and inspection
- CALSafety light-curtain test
- HRSFlywheel bearing lubrication
Injection moulding
- CYCMould and ejector service by shots
- HRSHydraulic filter change
- CBMOil temperature trigger
- CALHeater band and thermocouple check
Furnaces
- CALThermocouple calibration
- HRSCirculation fan bearings
- CBMRecovery-time creep trigger
- CALRefractory inspection
Air compressors
- HRSAir and oil filter change
- HRSOil change and separator
- CBMDischarge temperature trigger
- CALSafety valve test
Gearboxes and drives
- HRSOil change by operating hours
- CALBreather and seal inspection
- CBMGear-mesh sideband trigger
- CBMBearing temperature trigger
PM compliance becomes a number, not an opinion.
Share of PMs completed on time, per machine, line and technician. The first number an auditor asks for.
How long each overdue task has been waiting, counted live, so the most exposed machine is obvious.
Planned maintenance hours as a share of all maintenance hours. It rises as breakdowns give way to PMs.
Mean time between failures per machine, computed from real breakdown records rather than estimates.
Mean time to repair, from stop to running again, including the wait for parts.
Failures that followed a completed PM point to a checklist or interval that needs changing.
Why PM on a monitoring platform beats PM on a clipboard.
| Paper or Excel | Standalone CMMS | MachineWise | |
|---|---|---|---|
| Knows real run-hours | No · assumed from shifts | Manual meter readings typed in | Yes · measured by monitoring |
| Counts cycles, strokes, shots | No | Manual or via integration | Automatic |
| Condition-triggered tasks | No | Rarely · separate system | Built in · same platform |
| Overdue visibility | At the audit | Inside the app | Live countdown on floor screens, plus alerts |
| Evidence of work done | A signature | Varies | Notes, readings, photos and sign-off per task |
| Linked to OEE and breakdowns | No | Separate data | Same data · PM time is planned, not a breakdown |
The evidence is created by doing the work.
Auto-component suppliers are asked for total productive maintenance evidence under IATF 16949 (clause 8.5.1.5): planned maintenance objectives, their results, and records that the plan was followed. ISO 9001 (clause 7.1.3) asks for maintained infrastructure.
With MachineWise every PM carries who, when, what was checked, the readings and the photos, and compliance, MTBF and MTTR are already calculated. The audit pack comes from records that already exist, not a week of chasing signatures.
Five ways to maintain a machine. One platform runs all of them.
Most plants run all five at once on different machines, and that is correct. A spare-rich pump can run to failure; a constraint CNC cannot. MachineWise lets each machine sit on the stage its cost of failure justifies.
Straight answers.
What is preventive maintenance software?
What is the difference between preventive and predictive maintenance?
Can preventive maintenance be scheduled on run-hours instead of the calendar?
Do we need sensors for preventive maintenance?
Does it help with IATF 16949 and ISO 9001 audits?
Can we start from our existing PM checklists?
Does preventive maintenance work without internet?
Is preventive maintenance priced separately?
Where this connects to the rest of the platform.
Put your PM schedule on real run-hours this month.
A 30-minute walkthrough with your own checklists, then a free 2-machine pilot. Your data stays on-premises throughout.