Preventive maintenance software
Do the PM when the machine needs it, and see what is overdue before the shift.
MaintenanceIQ is preventive maintenance software that turns recurring schedules into planned jobs on a month calendar, triggered by date, by machine usage or by whichever comes first. It helps your maintenance planner keep PMs on time and your plant head see which machines are covered and which are not.
The problem
Why PMs slip even when everyone means well
Your planner knows the compressor needs an oil change every so often. The question is when. A spreadsheet says every three months, but the compressor ran double shifts all quarter and is well past its hours. Another machine sat idle for weeks and is serviced on the date anyway.
Meanwhile the due list lives in one person's head or one file. When that person is on leave, PMs slip quietly, and the first anyone hears of it is a breakdown.
Preventive maintenance only reduces downtime when the work is due at the right point in the machine's life and the overdue jobs are visible before the shift, not after the failure.
What preventive maintenance software should do for your planner
You define a recurring schedule once for a machine. MaintenanceIQ spawns each PM instance, with its own task checklist, and places it on a month calendar. Your planner sees due, overdue and upcoming work in one view at the start of the shift.
Each schedule carries its own preventive maintenance checklist, so the person doing the job sees exactly which checks to run and records the readings on the record.
- Recurring schedules that spawn PM instances
- A per-instance task checklist on every PM
- A month calendar of due, overdue and upcoming work
- Digests and My Tasks so each person sees their own PMs
Three ways to set a preventive maintenance schedule
Pick the trigger that matches how the machine actually wears.
| Trigger | When the PM falls due | Good fit for |
|---|---|---|
| Calendar | On a fixed calendar interval | Statutory checks, seasonal work, assets that run steadily |
| Usage | When a per-asset meter crosses an interval, for example every 500 operating hours or cycles | Presses, compressors, pumps whose load varies |
| Whichever comes first | On the calendar date or at the usage interval, whichever is reached first | Machines that can sit idle for weeks and then run hard |
Usage PMs project a due date from recent usage and alert when the meter crosses its interval.
Meters that keep themselves up to date
A usage PM is only as good as its meter. MaintenanceIQ gives you three ways to feed it.
Entered by hand
Your operator or technician logs the hour meter or cycle count on the machine. Simple, and enough for many assets.
How: Meter readings logged against the asset.
Fed from condition monitoring
If a sensor already reports running hours or cycles, the PM meter follows it and the PM advances itself.
How: A condition monitoring parameter, fed by hand, by CSV or Excel import, or from a PLC, SCADA or IoT gateway through the token-secured ingest API.
Learn moreFed from OEE run-hours
Plants already logging OEE shifts can drive usage PMs from the run-hours those logs produce.
How: OEE run-hours from per-asset shift logs, where availability comes from logged breakdowns.
Learn moreWhichever comes first on a hydraulic press
Worked example (illustrative)
The HP-11 press (illustrative machine) has a filter and oil check set to every 90 days or every 500 run-hours, whichever comes first. The last PM was done at 12,000 run-hours. Recently the press has been running about 10 hours a day.
At that rate the usage interval is reached long before the calendar one, so the PM falls due on usage.
| Step | Arithmetic | Result |
|---|---|---|
| Usage due at | 12,000 + 500 | 12,500 run-hours |
| Days to reach it | 500 ÷ 10 hours a day | 50 days |
| Calendar due | Fixed interval | Day 90 |
| Which comes first | 50 days is earlier than 90 days | Usage, around day 50 |
Your planner sees the projected date weeks ahead and books the job into a planned stop. If the press slows to 4 hours a day, 500 ÷ 4 is 125 days, so the 90 day calendar date wins instead and the PM still happens on time.
Know which machines are covered, and which are not
Not every machine deserves a PM program. Each asset carries a maintenance strategy: preventive, or run to failure on purpose. That lets you run PM on every machine or only on the critical ones, and filter the asset list by it.
A PM coverage rollup on the PM page shows, by A, B and C criticality, which machines are covered, which are deliberately run to failure, and which are gaps: in the PM program but with no active schedule. That is the list your reliability engineer works from.
PM compliance, measured and provable
PM compliance, the share of PMs done on time, sits in reliability analytics next to MTBF, MTTR and planned versus reactive work, and is a leading sign of where breakdowns are likely to rise. The report builder has a PM Compliance dataset you can filter, export to CSV and schedule. The compliance evidence pack has a PM Compliance section where every row carries who, when and status.
If you use Asset Risk (Beta), an overdue PM is one of the factors in an asset's risk score, linked to its evidence.
Frequently asked questions
Can a PM be triggered by running hours instead of a date?
Yes. A usage PM runs on a per-asset meter, such as every 500 operating hours or cycles. You can also set a PM to fall due on the calendar date or the usage interval, whichever comes first.
Do I have to type meter readings in by hand?
No. Readings can be entered by hand, or fed automatically from a condition monitoring sensor parameter or from OEE run-hours, and the PM advances itself. Condition monitoring is a licensed add-on.
Can each PM have its own checklist?
Yes. Every PM instance carries its own typed task checklist with checkbox, text or number, slider, range, photo and file tasks. Completed runs are frozen.
How do I see which machines have no PM?
Each asset is marked preventive or run to failure. The PM coverage rollup shows, by criticality, which machines are covered, which run to failure on purpose and which are in the program with no active schedule.