Preventive maintenance that schedules itself
Set the interval once and let the system raise the work. Fewer breakdowns, fewer emergency call-outs, and a plan your team can actually keep to.
Preventive Schedule
This week- Tomorrow
Chiller inspection
CH-02 · Roof plant · Every 30 days
Triggered byCalendarLast completed14 MayChecklist9 checks · 2 readings - In 6 days
Belt & filter change
AHU-14 · Block B · Every 90 days
Triggered byRuntime hoursLast completed22 MarChecklist6 checks · 1 part - Scheduled
Fire panel test
FP-01 · Lobby · Every 7 days
Triggered byCalendarLast completed11 JunChecklist4 checks · signature
Raises its own work orders — nobody has to remember.
Nobody has to remember
Schedules run on time, usage or condition, and raise their own work orders before something fails.
Fewer emergencies
Planned work displaces reactive work. The shift shows up in your downtime and overtime figures.
Consistent every time
The same checklist, the same required steps, whoever is on shift — so quality does not depend on who turned up.
Schedule on time, usage or condition
Not every asset should be serviced by the calendar. Choose the trigger that suits the machine.
- Fixed intervals for statutory and routine servicing
- Meter-based triggers for run hours, cycles or distance
- Raise work automatically when a reading crosses a threshold
What raises the work
3 trigger types- Day 27 of 30
Calendar
Every 30 days
CH-02 · Chiller
Runs whether or not the unit was used — right for statutory and seasonal work.
- 412 of 500 hrs
Runtime
Every 500 hours
GEN-01 · Generator
Counts actual hours run, so a standby unit is not serviced as if it ran all year.
- Reading 3.9 mm/s
Condition
Vibration above 4.5 mm/s
PUMP-07 · Booster
Raises work when a reading crosses the threshold, not on a date someone guessed.
Checklists that leave nothing out
A PM is only as good as the steps behind it. Build them once and they run every time.
- Step-by-step instructions with photos and required readings
- Mark steps mandatory so the job cannot be closed half-done
- Attach the parts a PM consumes so stock updates itself
Checklist template
Belt & filter changeWritten once, attached to every occurrence of this PM.
Visual inspection, casing and mountsCheck
Pass or fail, with a note if failed.
Belt tensionReading
Accept 8–12 mm deflection at mid-span.
Filter differential pressureReading
Accept 60–180 Pa. Above that, raise a filter change.
Bearing temperatureReading
Accept below 70 °C after 20 minutes running.
Photograph the completed workPhoto
Required. The job cannot close without it.
Technician signatureSign
Names the person accountable for the work.
Enforced at close
Watch reactive work fall away
The point of a PM programme is the trend line, not the individual job.
- Track planned versus reactive work week over week
- See PM completion rate by site, team or asset class
- Spot the assets still failing despite being on a schedule
Reactive share of all work
12 months31%
from 68%What moved it
Ready to simplify your maintenance operations?
Book a personalized demo and see how NeoGen CMMS fits the way your team already works.
Preventive Maintenance questions
We are entirely reactive today. Where do we start?
Start with your most critical assets — the ones whose failure stops work. Put those on a schedule first, then widen the programme as the reactive load drops and your team has room.
What happens if a PM is missed?
It stays open and visible rather than quietly disappearing, and overdue PMs surface in reporting so the backlog is never a surprise.
Can schedules follow run hours instead of dates?
Yes. Meter-based triggers raise work on run hours, cycles or any counter you record, which suits equipment used unevenly across the year.
Can different sites run different schedules?
Yes. Schedules can be standardised across the estate or varied per site, so a shared template does not stop a location handling its own equipment differently.