/ Engineering · Maintenance
The AMC cadence,
documented and tiered.
Maintenance is not a phone number; it is a documented cadence of inspections, preventive replacements, firmware reviews and incident response.
- Cadence stages
- 4
- Principles
- 1
- Reviewed
- 2026-05-17
- Artefact
- AMC pack
/ Maintenance workflow
Maintenance workflow — AMC tier cadence
The annual maintenance cadence we run against an AMC contract — scheduled inspections, preventive replacements, firmware reviews and incident response.
Maintenance is the day-two discipline of the practice. An AMC contract is not a phone number; it is a documented cadence of scheduled inspections, preventive replacements and firmware reviews, with a clear incident-response tier behind it. The discipline is the cadence — when did we last test the battery autonomy on the BESS, when did we last sweep the Cat6A channels, when did we last walk the addressable loop. The workflow below is the tier-1 cadence; tiered upgrades shorten the inspection interval and add contracted critical-hours support.
Stage 1
Scheduled site inspection
Walk the building against the AMC checklist — visual, electrical and integration spot checks.
- Outputs
- Inspection record · Updated punch list
- Gates
- Inspection record acknowledged by FM team
- Duration
- 1 day (quarterly cadence)
Stage 2
Preventive replacement window
Replace components that are at the end of their wear-life — UPS batteries, smoke detectors past EOL, sealed-bearing fans, gateway flash memory.
- Outputs
- Replacement record · Updated component lifecycle register
- Gates
- Replacement record acknowledged by FM team
- Duration
- 2–5 days (annual)
Stage 3
Firmware review window
Review device firmware against the manufacturer release notes — patch security advisories, defer feature-only releases.
- Outputs
- Patch decision log · Updated device firmware register
- Gates
- Patch decision log acknowledged by lead engineer
- Duration
- 1 day (semi-annual)
Stage 4
Incident response
Respond to incidents within the AMC tier's documented response targets. Each incident produces a closure note that updates the trend report.
- Outputs
- Incident closure note · Updated trend report
- Gates
- Incident closure acknowledged by FM team
- Duration
- Per AMC response-target tier
/ Maintenance principles
The principles behind the AMC discipline
Preventive maintenance over reactive response
An AMC measured by ticket-close-time is failing; an AMC measured by preventive-event-cadence is working.
Read in methodology →Key engineering takeaways
- AMC cadence is sector-bound, not catalogue-driven. A clinical-care AMC carries quarterly preventive checks; a retail-mall BMS AMC carries half-yearly checks; a residential cinema AMC carries half-yearly calibration and annual driver-compliance review.
- Preventive replacement intervals are scored against operating context — ambient temperature, duty cycle, dust load, RH — not against catalogue averages. The interval for a UPS bank in a 35°C electrical room is different from the same bank in a 22°C data centre.
- Spares discipline is the AMC's competitive moat. Named-pack inventory keyed to each deployment's BOQ — not a generic vendor pool — is what decides whether a Saturday failure is a same-day fix or a multi-day outage.
- Configuration baseline export is a per-visit deliverable. Every controller, panel, NVR and DSP baseline is exported offline after every configuration change so a controller swap is a same-day commission against the saved baseline.
- Incident response is rehearsed at every AMC visit, not invoked on the day. The top five failure scenarios for each deployment are walked end-to-end with the building's day-two engineer; the procedure lives in muscle memory, not on paper.
Common mistakes
What we see go wrong
- AMC visit scheduled but not executed against the documented checklist.
- Why it fails — An AMC visit that ends with a signed paper but no checklist sign-off is paperwork, not maintenance. The next failure surfaces a discipline gap the AMC paperwork cannot answer for.
- What we do instead — Every AMC visit ends with a per-deployment checklist signed against measured values — battery internal resistance, capacitor ESR, torque-check readings, configuration-baseline checksum — held in the AMC visit log.
- Spares drawn from a vendor's central pool rather than named-pack inventory.
- Why it fails — On a Saturday with three deployments needing the same panel, the deployment that pays first wins; the others wait against a procurement cycle that does not honour operational urgency. Pool spares fail at the moment they are needed.
- What we do instead — Named-pack inventory held against each deployment's BOQ, with support windows specified against the contract — not against the spares pool's availability.
- Preventive replacement deferred until the first failure shows.
- Why it fails — A reactive replacement is multiple times the cost of a preventive one — emergency procurement premium, downtime, escalation, weekend labour — and the failure typically takes other components with it.
- What we do instead — Preventive replacement intervals scored against operating context and held on the AMC calendar; the calendar is the contract, not the suggestion.
- Configuration baselines stored only on the controller, never exported.
- Why it fails — A controller fault destroys the configuration; the recovery becomes a forensic rebuild from memory across a sub-contractor who no longer holds the original toolchain. A same-day fix becomes a multi-day forensic exercise.
- What we do instead — Every configuration change is followed by an offline baseline export to the AMC archive; recovery procedure is rehearsed against the offline baseline at every AMC visit.
What ages poorly
Lifecycle weak points to plan around
UPS battery banks under daily duty
VRLA banks on 3–4 year refresh; LFP banks on 7–10 year refresh. Battery internal resistance and capacity test on every quarterly visit catches degradation before it shows on the ride-through measurement.
Fire-detector ionisation chambers
Smoke detectors drift on a 8–10 year horizon under continuous duty; IS-2189-mandated sensitivity testing on every annual visit catches drift before it shows in operational behaviour.
Mechanical pan/tilt assemblies
PTZ assemblies show wear at 7–9 years of weekly duty; preset-library export and rehearsed swap-and-load discipline keep the replacement a same-day exercise.
Cable terminations under thermal cycling
Crimped and screw terminations creep on a 12–15 year horizon under daily thermal cycling; AMC torque-check discipline catches creep before it shows on a measurable voltage drop.
Capacitor ESR drift on amplifier output stages
Pro-audio amplifier capacitors drift on a 10–12 year horizon under daily duty; annual ESR measurement catches drift before it shows on the amplifier's THD measurement.
· Where to go next
The maintenance authority graph.
Engineering discipline
Read further