AMC strategy: how to scope a maintenance contract that genuinely keeps systems alive

An AMC is one of the most under-specified procurement lines in commercial-buildings work. The tender typically asks for an annual fee against a one-line scope ('annual maintenance of the installed systems'), and the cheapest credible bidder wins. The result is a contract where the practical content is the quarterly visit report, the supplier's response time is whatever they decide on the day, and the configuration discipline is whatever the original installer left behind.

An AMC that genuinely keeps a building's systems alive over fifteen years is scoped on four axes, not one. The four are: preventive calendar, documented response targets, parts inclusion, and configuration discipline. Each is a separate engineering question, and the answers separate a real maintenance discipline from a billing exercise.

## Axis 1 — preventive calendar

What gets checked, when, and against what test? A preventive calendar is a written schedule of inspections, tests and component replacements, sized against each system's manufacturer service-bulletin and the building's actual operational profile. A fire-alarm panel needs a quarterly battery test, an annual cause-and-effect re-validation, a five-year detector-sensitivity check; a BMS needs a monthly chiller-sequence verification, a quarterly damper-actuator test, an annual sub-metering calibration; a CCTV system needs a monthly storage-consumption check, a quarterly camera-firmware update calendar, an annual lens-and-housing cleaning.

We publish the calendar at AMC enrolment and we sign every visit against the calendar's specific tests. Visits that do not deliver against the calendar do not bill. The calendar is the contract, not the visit count.

## Axis 2 — documented response targets

Response targets document how fault reports are handled, what we aim to resolve in the first visit, and what the parts entitlement is. Standard AMC tiers carry business-hours support windows defined in the service scope. Premium AMC tiers add contracted critical-hours support for nominated critical systems (hospital nurse-call, hotel guest-room control, mission-critical UPS) with parts-on-site entitlement documented in the AMC scope.

Response targets are documented per-system, not per-AMC, because different systems have different criticality. A hospital nurse-call has a tighter escalation path than a hospital meeting-room AV. The contract carries the per-system response targets in writing, and our AMC log records compliance against every target over the contract term. Clients see the compliance number on every quarterly review.

## Axis 3 — parts inclusion

Most AMCs leave parts as a billable extra, which produces the predictable failure mode where every fault triggers a parts conversation that delays resolution by 3–10 days. The right scoping is a deployment-specific spares pool — the parts likely to fail, held in the integrator's office or warehouse against this specific deployment, included in the AMC fee.

We hold deployment-specific spares for every active AMC engagement, sized against the manufacturer's MTBF data and the deployment's actual age. A 5-year-old fire-alarm system has a different spares pool from a 5-month-old one. The spares are listed in the AMC enrolment document and replenished within 30 days of any consumption. Where a fault requires a part not in the pool, the procurement path is documented in the AMC scope.

## Axis 4 — configuration discipline

Configuration discipline is the part of an AMC most procurement teams do not even know to ask about. Every active deployment has its current configuration and firmware versions captured to encrypted, versioned, offline storage on our infrastructure. Updates are tested against this baseline before being pushed to the deployment. If anything goes wrong — a firmware update that misbehaves, a configuration change that breaks a cause-and-effect — recovery is hours not days, because the working configuration is always retrievable.

Without configuration discipline, an AMC is a maintenance contract for the hardware only. The software state of the system is a parallel risk that nobody owns. We treat configuration discipline as part of the AMC scope, with the offline baseline stored on enrolment and updated quarterly.

## Pricing — what each axis actually costs

Standard AMC for active systems (CCTV, fire alarm, BMS, automation) covers the four axes at standard depth. A premium AMC for specialist systems (Rako, addressable fire panels, hospital nurse-call) carries tighter documented response targets, larger spares pools and contracted critical-hours support. What the programme costs depends on the response-target tightness, the after-hours coverage, the parts-inclusion scope and the number of separate disciplines under one umbrella contract — so it is scoped per system and priced in writing after review, not published as a band.

Tendering only on annual fee — without specifying the four-axis content — produces an AMC that bids low because the bidder is scoping shallow. Specify the four axes in the tender, and the comparison becomes apples-to-apples. The cheapest bidder is rarely the right one once the axes are written down.

## Callout — what buyers most miss

**Configuration discipline is the axis nobody asks about and the one that decides recovery time at year five.** The hardware is reliable; the software state is the variable that decides whether a bad firmware update is hours of recovery or days. Ask the AMC bidder where the offline baseline is stored, how it is versioned, and how recovery is tested. The answer separates a serious maintenance discipline from a quarterly visit-and-bill cycle.

## Reference deployment context

We hold active AMC engagements on the Tinsukia Medical College & Hospital, the Capital Cultural Hall and the Town Hall Dimapur — each scoped on the four axes with deployment-specific spares pools, written response targets and offline configuration baselines stored at our Lachit Nagar office. The discipline is the same on every contract; only the response-target tier and the spares pool size scale with the engagement criticality.

## References

1. ISO 9001:2015 — Quality management systems requirements.

2. Manufacturer service bulletins — Honeywell, Siemens, Hikvision, Bosch, Rako, Fibaro, K-array.

3. NBC 2016 — periodic-inspection provisions for life-safety systems.

4. NABH 5th Edition Accreditation Standards for Hospitals — facility-management documentation.