Preventive maintenance that schedules itself
Preventive maintenance fails for one reason far more often than any other: it depends on somebody remembering. MaintPro removes the remembering. Work is generated from rules you set once, routed to an owner automatically, and escalated when a window is about to be missed — so PM compliance stops being a number you reconstruct and becomes a number you manage.
- 42%
- less unplanned downtime
- 3
- trigger types: time, usage, condition
- 40+
- IoT & telematics platforms
Three ways to trigger preventive maintenance
Different assets fail on different clocks. Scheduling everything by calendar is the most common reason PM programmes over-service some assets while under-servicing the ones that matter.
Time-based — the calendar trigger
Fixed intervals: quarterly inspections, annual statutory checks, monthly filter changes. Simple, predictable, and correct for assets whose wear tracks elapsed time or whose interval is set by regulation rather than by condition.
Usage-based — the meter trigger
Work raised on runtime hours, cycles, kilometres, or units produced. A compressor that ran double shifts last month needs service sooner than the calendar suggests; a line that sat idle does not need servicing at all.
Condition-based — the sensor trigger
Work raised when a live reading crosses a threshold: vibration, temperature, pressure, current draw. MaintPro connects to 40+ IoT and telematics platforms, so a rising trace generates a work order before the failure it predicts.
Choosing between them
Start time-based on everything, move critical assets to usage-based once you have runtime data, and reserve condition-based for assets whose failure actually stops production. Trying to instrument everything at once is how PM programmes stall.
Building a PM programme that survives a busy quarter
The software schedules the work. These are the decisions that determine whether the schedule holds when the week goes badly.
Rank assets by criticality first
Not every asset deserves a PM. Score by what failure actually costs — lost output, safety exposure, regulatory consequence — and concentrate the programme on the top tier. A PM plan that covers everything equally gets abandoned equally.
Set the interval from evidence, not habit
Inherited intervals are usually a manufacturer's conservative default multiplied by someone's caution. Use failure history and runtime data to lengthen intervals where nothing is being found, and shorten them where failures still land between services.
Write checklists a technician can finish
A PM task with fourteen vague steps gets signed off without being done. Specific, ordered, verifiable steps with somewhere to record readings turn a signature into evidence.
Escalate before the window closes, not after
A missed PM discovered at month end is a reporting problem. An escalation raised while the window is still open is an operational one, and it can still be fixed. MaintPro escalates automatically on the schedule you configure.
Stage the parts with the schedule
Preventive work that arrives without its consumables becomes deferred work. Because MaintPro links PM tasks to the parts they consume, the storeroom sees demand before the technician does.
The KPIs that prove the programme is working
Four numbers separate a PM programme that is genuinely reducing failures from one that is generating paperwork.
PM compliance
The share of scheduled preventive work completed inside its window. The single most diagnostic maintenance metric: if this is low, every other improvement effort is being applied on top of work that is not happening.
MTBF — mean time between failures
Average operating time between unplanned failures on an asset. Rising MTBF is the clearest evidence that preventive work is displacing breakdowns rather than merely accompanying them.
MTTR — mean time to repair
Average time from failure to restored service. Falling MTTR usually reflects better diagnosis, staged parts, and clearer work instructions rather than faster technicians.
Planned vs unplanned ratio
The proportion of total maintenance hours spent on scheduled work. Mature programmes trend heavily toward planned; a ratio stuck near even means the team is still being driven by the assets rather than driving them.
Common questions
More on pricing, security, and implementation in the main FAQ.
See it against your own assets
Book a demo and we will set up your free 14-day trial — every feature, no user limit, no credit card. An implementation specialist replies within one business day.