Preventive maintenance contracts — when they're worth it and when they're not

A preventive-maintenance proposal can sound reasonable while leaving the owner unable to compare it with ordinary service calls. “Annual system check” does not identify the devices tested, the measurements saved, or the failures included in the price. For Atlanta and Southeast facilities, the useful decision starts with a system inventory and a maintenance scope, not a percentage of original installation cost.

Separate three purchases: scheduled maintenance, required inspection and testing, and response to failures. They can share one agreement, but they are different work. The warranty terms discussion explains another distinction: a parts warranty does not automatically pay for diagnosis, access equipment, labor, or an urgent visit.

Establish the work that cannot be optional

List the applicable inspection, testing, and maintenance obligations for each system. For fire alarms, use the adopted NFPA 72 edition, local requirements, approved system documents, and manufacturer instructions. NFPA explains that NFPA 72 covers inspection, testing, and maintenance throughout the system’s life. The procurement method does not remove those obligations.

Then identify operational tasks outside that required baseline. Examples include confirming that selected cameras produce usable recorded images, checking an access-control battery under the prescribed test conditions, and exercising an AV room’s normal workflow. Match each task to a failure mode and a documented procedure. A visual glance at a controller cannot establish battery capacity or successful event reporting.

The fire-alarm service scope should distinguish required testing from corrective work and identify how impairments are coordinated. Do not compare a quote containing all scheduled testing with another quote that excludes it. Normalize the obligations first, then compare the optional coverage.

Build failure rates from usable records

There is no defensible universal failure rate for “low voltage.” A door strike cycles mechanically, a camera depends on its environment and network, and a passive cable generally has different failure causes. Model age, usage, temperature, workmanship, firmware, and power quality all influence the result. Published product reliability estimates are not a substitute for installed-system service history.

Build a register by device class, installation date, and location. Record confirmed failures separately from duplicate tickets, operator mistakes, planned changes, and upstream outages. Divide confirmed failures by an appropriate exposure measure, such as device-years, and show the observation period. Twenty tickets for the same unresolved door are not twenty independent hardware failures.

Compare costs with explicit assumptions

Calculate the annual cost of the agreement, excluded repairs, consumables, and owner coordination. Compare it with scheduled work purchased separately plus expected reactive service and downtime. Keep required work in both alternatives. Otherwise the cheaper option may simply omit tasks that the owner still has to procure.

Consider an illustrative building where required and planned visits cost $2,400 annually and four expected reactive incidents cost $600 each. The cash-service estimate is $4,800 before downtime. A $6,000 agreement costs $1,200 more if it truly includes those visits and incidents. That arithmetic does not establish that the agreement prevents failures; it shows the premium the owner must justify through measurable scope or response value.

If the contract excludes replacement parts, lift rental, after-hours labor, or network diagnosis, add those costs back into the comparison. If it includes a service credit, determine what triggers the credit and how it is claimed. Avoid counting both an assumed reduction in incidents and a full avoided downtime allowance without evidence supporting each effect.

Match the agreement to the building

A high-use facility with many controlled doors, limited onsite expertise, and expensive access restrictions may benefit from scheduled work and reserved support capacity. A small office with a simple AV installation and competent local support may get better value from a documented inspection schedule and time-and-materials repairs. These are planning profiles, not guarantees based on building type alone.

For access-control operations, include mechanical-door responsibility and the handoff to the locksmith or door vendor. Electronic service cannot compensate for a dragging door that never latches. State who owns the complete functional result and how cross-trade faults are diagnosed without repeated billable visits.

For video-system maintenance, specify recorded playback checks, retention verification against the configured policy, clock checks, and escalation of storage warnings. A camera ping proves network reachability at that moment. It does not establish that the required scene was recorded and can be retrieved.

Review outcomes before renewal

The commissioning and testing article explains why component results need operational context. Use the same principle in maintenance: retain the readings, failed functions, corrective actions, and repeat-test evidence. A signed attendance sheet alone provides little support for the next budget decision.

At renewal, compare completed tasks, confirmed incidents, restoration times, repeat calls, and exclusions paid outside the agreement. Adjust for changes in device count and operating hours. One quiet year is not proof that preventive visits caused the improvement, especially when the original failure count was small.

Choose the purchasing model that supports the documented obligations and the owner’s operational tolerance. A good agreement makes the work visible and the response predictable. Time-and-materials can also be appropriate when the owner retains a complete schedule and accountable service records. Either model should leave the building with known conditions and a practical way to close deficiencies.