Why Preventive Maintenance Deserves a Playbook, Not a Checklist
Every property operator knows the compounding cost of reactive maintenance: a missed filter change becomes a failed air handler; a skipped pump inspection becomes a flooded basement. The difference between portfolios that absorb these shocks and portfolios that eliminate them is rarely effort — it is structure. A preventive maintenance (PM) program only works when scheduling, asset data, and field execution operate as one system.
This playbook outlines how to design a PM program inside ArkanPM so that schedules generate on time, the right technicians see the right work, and data flows back into asset condition scoring automatically.
Step 1: Build the Systems Registry Before You Schedule Anything
PM programs fail when they are grafted onto incomplete asset data. Before you write a single schedule, inventory your building systems — HVAC, electrical, plumbing, fire safety, elevators, and security — with manufacturer, model, installation date, and next service date populated. ArkanPM treats building systems as first-class entities that tie directly into scheduling, so a weakly described system becomes a weakly scheduled system.
Within each system, decompose assets hierarchically. An HVAC system contains chillers; chillers contain compressors and fans. Parent-child asset relationships let you schedule maintenance at the right altitude — weekly filter checks on air handlers, quarterly refrigerant analysis on the chiller itself.
Data Fields That Drive Good Schedules
- Criticality (low, medium, high, critical) — drives priority and stocking decisions
- Installation date — anchors age-based intervals
- Useful life and salvage value — supports replacement planning
- Warranty coverage — prevents unnecessary spend on covered work
Step 2: Choose the Right Frequency Model
ArkanPM supports nine frequency options on every PM schedule: daily, weekly, biweekly, monthly, quarterly, semi-annual, annual, and custom interval (in days). The temptation is to default to monthly for everything. Resist it. Over-scheduling wastes technician hours and desensitizes teams to real issues; under-scheduling invites failure.
A defensible cadence looks like this:
| Asset Class | Typical Cadence | Rationale |
|---|---|---|
| Fire safety equipment | Monthly + annual | Statutory checks plus deeper inspection |
| HVAC filters | Monthly or biweekly | Function of runtime and air quality |
| Elevator systems | Monthly + annual | Combination of operational and certification needs |
| Water pumps | Quarterly | Balances wear monitoring with technician load |
| Backup generators | Weekly run, quarterly load | Run-time verification plus performance test |
Custom interval (in days) handles the edge cases — a 45-day cleaning cycle or a 100-day calibration.
Step 3: Use Multi-Trigger Scheduling Where It Matters
Time-based triggers are the baseline. They are not always the right answer. ArkanPM supports three trigger types on a single schedule:
- Time-based — calendar-driven, the default
- Meter-based — generated when a runtime-hour, cycle, or consumption meter crosses a threshold
- Condition-based — generated when a condition assessment score drops below a threshold
Meter-based triggers are the difference between servicing a generator every six months (whether it ran or not) and servicing it every 250 runtime hours. Condition-based triggers catch the assets that age faster than your calendar assumed — a chiller flagged "fair" at its last assessment deserves an earlier intervention than one still scored "excellent."
Combine triggers on a single schedule for critical equipment: time OR meter OR condition, whichever fires first.
Step 4: Use Templates to Standardize Execution
Each PM schedule generates work orders from a template. Templates carry pre-filled checklists, default assignments, and estimated hours. When a generated work order inherits a standardized checklist with five response types — checkbox, text, number, photo, and select — field execution stops depending on tribal knowledge.
Required checklist items should be non-negotiable for close-out. A PM work order cannot be closed until the required items are complete. This is how you enforce quality without micromanaging technicians.
Step 5: Align PM with SLA Tiers
Preventive work does not live outside your SLA framework — it lives alongside it. PM-generated work orders inherit priority from the template, which in turn drives SLA targets. The default structure looks like:
- Emergency — 1-hour response
- Urgent — 4-hour response
- High — 8-hour response
- Medium — 24-hour response
- Low — 48-hour response
Most PM is Medium or Low. That is appropriate — it means your reactive backlog does not get starved when the PM generator releases a batch of scheduled work. Escalation rules should still apply: if a PM work order sits unacknowledged past its response window, the escalation engine bumps it automatically.
Step 6: Let the Background Processor Do the Work
The PM generator is a background process. It checks active schedules, evaluates triggers, and creates work orders ahead of the due date by the schedule's configured lead days. Lead days matter: generating a quarterly PM the morning it is due gives your team no planning window; generating it seven days early lets the work be assigned, parts reserved, and residents notified.
Pause and resume controls exist for a reason. During a building shutdown or a major renovation, pause the affected schedules rather than deleting them. When you resume, the schedule's generation context is preserved — no reconstruction required.
Step 7: Measure Two Things Relentlessly
- Generation adherence — Did the scheduled work orders actually generate and get completed on time? The schedule tracks last-generated, total-generated, and next-due, giving you the data directly.
- Post-PM condition trend — Are condition scores stable or improving on assets under active PM? If they are trending down, the interval is wrong or the checklist is wrong.
A mature PM program is not one that generates the most work orders. It is one that generates the right work at the right time, backed by asset data that earns its place in every decision. Build the foundation first, then let the scheduler do its job.