Use case
PPM cycles that run on schedule, not on memory
Preventive maintenance — lift servicing, pest control, water tank cleaning, fire system checks — is only preventive if it actually happens on schedule. Meridian runs PPM cycles from configurable templates instead of a calendar reminder someone has to notice.
The problem
PPM schedules tracked in a calendar or a spreadsheet column rely on someone checking it regularly — and a missed cycle usually isn't noticed until the next compliance review.
Why it matters
Several PPM areas (fire, lift, water hygiene, pest) are also compliance controls — a missed preventive cycle isn't just a maintenance gap, it's a compliance gap too.
How Meridian helps
- PPM templates configurable per building type, applied consistently across a portfolio
- Scheduled cycles generate maintenance tickets automatically when due, not on manual trigger
- PPM completion feeds directly into the same compliance controls it supports — fire, lift, water hygiene, pest
- Vendor dispatch and SLA timers run on PPM tickets the same way they do on reactive requests
FAQ
Is PPM different from reactive maintenance tickets?
PPM tickets are generated on a schedule rather than from a tenant report, but they run through the same triage, dispatch and sign-off workflow.
Can PPM templates differ by building?
Yes — templates are configured per building type, so an older tower and a newer villa community can run different PPM cycles within the same portfolio.