· Engineering / AMC intelligence
The AMC,
as an engineering posture.
An AMC contract on paper is a calendar event. An AMC as an engineering posture is the asset register, the configuration baseline, the inspection cadence keyed to the actual decay driver, the documented escalation path and the disciplined preventive-versus-reactive judgment that compounds over the building's operational decade.
What AMC intelligence actually is
A repeatable, defensible service posture, keyed to the criticality of the deployment. Inspection cadences sourced from IS 2189, IS 15105, IS 16242, NFPA 72 and vendor service envelopes — never from arbitrary calendar slots. Each discipline carries its own scope, blind spots and baseline-export discipline.
When to use
When you are scoping an AMC for a deployment that has to perform at year three and year seven.
When not to use
As a substitute for site-specific risk analysis. Every building's escalation paths, vendor relationships and team capacity bend the AMC into its actual shape.
8
Cadences
4
AMC tiers
8
Blind spots
7
Baselines
7
Handover items
8
Checklist
4
Escalation
5
P/R decisions
· Inspection cadence by discipline
What gets inspected, and how often.
Fire alarm and life-safety
Reference: IS 2189 / IS 15105 / NFPA 72 service envelope
| Tier | Cadence |
|---|---|
| bronze | Semi-annual with annual cause-and-effect verification |
| silver | Quarterly with cause-and-effect verification each half-year |
| gold | Monthly with cause-and-effect verification each quarter |
| mission-critical | Monthly with cause-and-effect test rehearsal; weekly sounder/visual circuit-walk |
Scope
- Loop-fault audit and isolator function test
- Detector sensitivity verification (sample basis)
- Manual call-point activation test
- Sounder / visual indicator audibility test
- Battery standby capacity test
- Cause-and-effect matrix walkthrough against current occupancy
CCTV and video management
Reference: Vendor service envelopes; IS 18116 design alignment
| Tier | Cadence |
|---|---|
| bronze | Semi-annual camera audit and annual NVR audit |
| silver | Quarterly camera audit and semi-annual NVR review |
| gold | Monthly camera-by-camera audit and quarterly NVR firmware review |
| mission-critical | Monthly with quarterly analytics rule review and forensic-grade PPM audit |
Scope
- Lens-face clean and IR illuminator alignment
- Per-camera live-view test against the design PPM
- NVR storage health audit (RAID status, retention compliance)
- Analytics rule false-positive rate review
- PoE budget audit on each switch
- VLAN and QoS posture verification
Access control and intrusion
| Tier | Cadence |
|---|---|
| bronze | Semi-annual per-reader test |
| silver | Quarterly per-reader test |
| gold | Monthly per-reader test and quarterly card-database audit |
| mission-critical | Monthly with weekly card-reader walkthrough |
Scope
- Reader-by-reader card-swipe test
- Magnetic-lock and strike-lock function test
- Anti-passback and tailgating logic verification
- Card-database audit (active vs orphaned credentials)
- Event-log integrity check against CCTV bus
- Battery / UPS test on each door-controller
UPS and battery storage
Reference: IS 16242 UPS; vendor cycle-life envelope
| Tier | Cadence |
|---|---|
| bronze | Semi-annual load-bank test |
| silver | Quarterly load-bank test |
| gold | Monthly visual and quarterly load-bank test |
| mission-critical | Weekly visual; monthly load-bank test; quarterly battery-bank cell-resistance survey |
Scope
- Per-cell voltage measurement and outlier flagging
- Internal-resistance trend audit against commissioning baseline
- Load-bank discharge test on a controlled duty cycle
- Inverter thermal scan under load
- Bypass switch function test
- Ambient-temperature compliance review
Audio-visual and conferencing
| Tier | Cadence |
|---|---|
| bronze | Semi-annual room audit |
| silver | Quarterly per-room audit |
| gold | Monthly per-room calibration audit |
| mission-critical | Pre-event check + monthly preventive + post-event review |
Scope
- Per-room calibration verification (SPL, RT60 spot-check, STI)
- Speaker impedance sweep and amplifier output check
- Microphone bus and DSP path verification
- Display panel uptime and colour calibration spot-check
- Conferencing platform certification refresh
Lighting automation
| Tier | Cadence |
|---|---|
| bronze | Semi-annual scene audit |
| silver | Quarterly scene audit |
| gold | Monthly scene audit and quarterly per-zone driver health audit |
| mission-critical | Monthly scene audit and per-zone DALI driver check |
Scope
- Scene-by-scene visual verification against the commissioning baseline
- DALI driver fault-log review
- KNX bus health audit
- Configuration-baseline export and offline storage
- Override-keypad and wall-station verification
Networking and structured cabling
Reference: IS 11500 building structured cabling baseline
| Tier | Cadence |
|---|---|
| bronze | Annual link audit |
| silver | Quarterly link audit |
| gold | Monthly link audit and quarterly switch-stack firmware review |
| mission-critical | Weekly link-health audit; monthly switch-stack firmware review |
Scope
- Per-switch CPU / memory / temperature audit
- Trunk and uplink utilisation review
- PoE budget audit by switch
- Patch-panel labelling against architectural drawing
- Spare-port availability audit
- Switch-stack firmware baseline review
BMS / BACnet building bus
| Tier | Cadence |
|---|---|
| bronze | Semi-annual schedule audit |
| silver | Quarterly schedule audit |
| gold | Monthly schedule audit and quarterly point-by-point trend review |
| mission-critical | Monthly schedule audit + weekly alarm-routing test |
Scope
- Schedule (occupancy, set-point) compliance audit
- Trend-data integrity verification
- Field-sensor calibration check (sample basis)
- Alarm-routing function test
- Server-platform firmware and license audit
- Configuration-baseline export
· Common service blind spots
The failures the schedule misses.
A calendar-driven AMC catches the failures aligned to its calendar. The failures that hide between calendar slots are the ones below. We surface them explicitly so the AMC scope is written to catch them.
Fire-alarm cause-and-effect
Blind spot: The signed C&E table goes stale when occupancy changes (a department moves, a suite is reallocated, a tenant is added).
Why missed: The fire-alarm panel still functions; the matrix on file no longer reflects the building. Operations teams assume the panel programming is the truth.
Fix: Annual C&E review against the architect-of-record floor plan; any layout change triggers an out-of-cadence review. The signed paper table is the truth, not the panel programming.
NVR storage growth
Blind spot: Retention duration drifts down as camera count grows or resolution increases without an NVR upgrade.
Why missed: The NVR keeps recording; the older footage silently rolls off. The shortfall is only visible when a forensic request returns nothing.
Fix: Quarterly retention audit against the design specification; per-camera and per-RAID volume utilisation tracked monthly.
Spare-parts shelf life
Blind spot: Electrolytic capacitors in spare PSUs and amplifiers age on the shelf; a 'new' spare may have a degraded service life by year three.
Why missed: Spare parts inventory tracking captures presence, not age. Shelf rotation is rarely managed.
Fix: Spares register tracks manufacture date; spares older than 24 months are bench-tested before being put into service.
Configuration baseline drift
Blind spot: Field changes (a moved camera, a re-zoned scene, a new BMS point) accumulate without being captured in the offline baseline.
Why missed: Baseline exports happen on a schedule; ad-hoc changes happen between schedule slots and accumulate silently.
Fix: Every field change ends with an offline baseline export. A controller failure two months later restores to the post-change state, not the pre-change state.
PoE budget headroom
Blind spot: Camera-by-camera additions consume the switch's PoE budget; PoE+ allocations get trimmed silently until a high-draw device degrades.
Why missed: The switch keeps supplying power; PoE allocation is dynamic. Failures appear randomly until a budget audit identifies the cause.
Fix: Quarterly PoE budget audit per switch; switches running above 75% PoE utilisation flagged for headroom planning.
Battery ambient temperature
Blind spot: Battery cabinet ambient creeps above 30 °C when the cooling shifts (a new server load, a blocked vent, a failed cabinet fan).
Why missed: Batteries operate apparently normally until capacity drops below the runtime requirement on a real event.
Fix: Battery cabinet ambient logged at every preventive visit; >30 °C ambient triggers a cooling review, not just a battery review.
Firmware-licence drift
Blind spot: Vendor licenses expire silently or shift to a subscription model the AMC budget didn't anticipate.
Why missed: Many features keep working with an expired license; advanced features (analytics, integration, support) stop without an obvious alarm.
Fix: Per-vendor license tracker; license expiry dates carried in the AMC calendar alongside the visit schedule.
Outdoor enclosure seals
Blind spot: Camera enclosure and pole-base seals degrade silently on monsoon-belt sites; water ingress fails the enclosure before it fails the camera.
Why missed: The camera image stays clean while the seal degrades. Failure is sudden and seasonal.
Fix: Pre-monsoon and post-monsoon enclosure-seal inspections written into the AMC; suspect seals re-sealed rather than waiting for ingress.
· Configuration-baseline discipline
What gets exported, when, where it lives.
| Controller | Baseline format | Export cadence | Storage | Recovery rehearsal |
|---|---|---|---|---|
| Fire-alarm panel | Panel programming export (.csv / vendor binary); signed C&E table (.pdf). | At commissioning; after every C&E review; after every firmware refresh. | Offline encrypted archive plus paper hard-copy in the panel cabinet. | Annual restore-to-spare-panel rehearsal during the gold AMC visit. |
| UPS / BESS controller | Inverter parameter sheet, battery-string configuration, dispatcher schedule export. | At commissioning; after every parameter change; after every battery refresh. | Offline encrypted archive; printed configuration sheet inside the UPS cabinet door. | Semi-annual parameter-restore rehearsal on the bench. |
| VMS / NVR | Camera definitions, analytics rules, user permissions, storage retention rules — vendor export. | Monthly on gold; weekly on mission-critical; after every camera addition. | Offline encrypted archive plus a second copy at the integrator's central repository. | Annual restore-to-spare-NVR rehearsal. |
| Network switch stack | Running-config and startup-config dump per switch; trunking and VLAN map; PoE allocation table. | Monthly; after every config change. | Offline encrypted archive plus version-controlled team repository. | Annual cold-restore rehearsal on at least one spare switch. |
| Wi-Fi controller | Controller config export, AP group definitions, RF profile, guest portal config, authentication settings. | Monthly; after every RF change. | Offline encrypted archive. | Annual rebuild rehearsal from baseline on a controller in lab. |
| BMS server | Schedule export, point definitions, alarm-routing config, license keys, database snapshot. | Monthly; after every schedule or point change. | Offline encrypted archive; vendor portal backup as secondary. | Annual restore to spare server. |
| KNX / DALI lighting controller | ETS .knxproj file (KNX); DALI bus map and scene tables. | After every commissioning or scene change. | Offline encrypted archive; copy held by the resident / facility manager. | Bench-test of restore process on a spare actuator annually. |
· Documentation handover discipline
The seven artefacts that decide year-three usability.
As-built drawings
Floor-by-floor cable routing, panel positions, device positions, conduit paths and termination boxes as actually installed (not as designed).
Why it matters: Future expansion, fault tracing and refurbishment all begin with the as-built. Without it, every change is an exploratory exercise.
Asset register
Every active node — make, model, serial number, firmware version, install date, location, MAC/IP, default credentials cycled, AMC tier.
Why it matters: The basis of every AMC visit and every refresh budget. Without it, the AMC is a calendar event, not an operational contract.
Commissioning report
Measured values at handover — SPL, STI, RT60, lux, link speeds, PoE allocations, runtime curves, NBC compliance witness tests.
Why it matters: Year-three performance is benchmarked against year-zero numbers. Without the commissioning report, drift is invisible.
O&M manual
Per-discipline operating procedures, preventive cadence, escalation contacts, vendor support pathways, spares posture.
Why it matters: Operations team hand-over is procedural; the manual is what makes the operation portable across team changes.
Configuration baselines
Offline exports of every controller — see the baseline discipline matrix.
Why it matters: A controller failure is a same-day exercise against the saved baseline rather than a multi-day reprogramming.
Warranty + licence matrix
Per-asset warranty period, support level, vendor licence end-dates, renewal path.
Why it matters: License lapses are invisible until a feature stops working. The matrix turns lifecycle into a budgeting exercise.
Training records
Who has been trained on what, by whom, when. Trained-operator handover certification.
Why it matters: Operations posture depends on trained operators. The record is part of the audit trail.
· Site-serviceability checklist
Walk-through questions before signing the contract.
- 01 · Access
Can every device be reached from a single ladder position or a single basket lift?
Why: Hard-to-reach devices age on a different curve than reachable ones — preventive visits skip them, and they fail without warning.
- 02 · Labelling
Is every patch panel, every conduit, every device labelled against the architectural drawing?
Why: Unlabelled installations turn every maintenance visit into a tracing exercise; the AMC cost multiplies and the response window degrades.
- 03 · Cooling
Is the head-end rack's cooling sized for the actual heat load plus 20% headroom?
Why: Under-sized cooling shows up as elevated rack ambient, accelerating component aging and triggering thermal throttling under load.
- 04 · Power
Are critical loads on dedicated UPS rails independent of comfort loads?
Why: Shared UPS rails cascade non-critical faults into critical loads. Critical-load isolation is a power-topology decision, not a software one.
- 05 · Containment
Is there spare conduit capacity (≥ 30%) for foreseeable expansion?
Why: Phase-2 expansion that has to be retrofit into a full conduit is the most expensive expansion. Design-stage headroom is nearly free.
- 06 · Spares
Is there a documented on-site spares location and inventory for critical components?
Why: Spares without a documented location may as well be off-site. The escalation window depends on the spare being findable.
- 07 · Documentation
Are the as-built drawings, asset register and configuration baselines stored offline on site?
Why: Cloud-only documentation fails when the building's network is the failure surface. Offline storage is a hedge against the dependency.
- 08 · Escalation
Is the named on-call engineer and the vendor support pathway documented and posted at the head-end rack?
Why: The first hour of an incident is when escalation paths matter most. Searching for them costs that hour.
· Escalation path
Four levels, with named authority at each.
- L1
On-site duty engineer
Who: AMC engineer scheduled on site for the day; site facility duty engineer for owner-operated sites.
Authority: Triage; first-line restore from documented procedures; cosmetic remediation; non-disruptive replacement.
Engages immediately on incident notification.
- L2
Discipline lead
Who: Named discipline lead in the AMC contract — fire, networking, AV, automation, BMS.
Authority: Configuration changes; controlled reset of critical controllers; firmware rollback; coordination with vendor TAC.
Engages within 30–60 min if level-1 cannot restore.
- L3
Project engineer / studio principal
Who: Originally accountable project engineer; for high-impact incidents, the studio principal.
Authority: Cross-discipline coordination; budget approval for emergency parts dispatch; client communication during prolonged outage.
Engages within 2 h of incident if level-2 cannot restore, or immediately for safety-critical incidents.
- L4
Vendor TAC + emergency dispatch
Who: Brand technical assistance centre; emergency replacement-pack dispatch.
Authority: Vendor-level diagnosis; out-of-warranty parts dispatch; firmware engineering support.
Engaged in parallel with level-3 for vendor-rooted failures; otherwise within 4 h if internal escalation cannot resolve.
· Preventive vs reactive maintenance — judgment matrix
The judgment that costs more if it's wrong.
Not every issue is worth preventive action; not every issue is safely reactive. The matrix below captures the discipline by scenario.
VRLA battery bank approaching 30 months of service
Recommendation: preventive action
Preventive response: Capacity test under load; replace the bank at the next scheduled AMC if capacity falls below 85% of commissioning baseline.
Reactive cost: Unplanned outage during a real load event; emergency procurement of the replacement bank at 1.5–2× cost; potential collateral damage to the UPS itself from a deeply-discharged failing bank.
Rationale: Battery decay is predictable; the cost of preventive replacement is well below the cost of failure on a real event.
Fine-pitch LED module showing colour drift
Recommendation: preventive action
Preventive response: Per-module calibration during a planned dark window; replace the affected drivers if calibration cannot recover uniformity.
Reactive cost: Audience-visible defect during a ceremonial event; emergency vendor visit; potential need to swap multiple modules simultaneously.
Rationale: Visual defects accumulate; once visible to the audience, they become a brand event for the building.
Switch port intermittent on a non-critical edge link
Recommendation: reactive with monitoring
Preventive response: Move the link to a spare port; flag the failing port at next AMC visit; replace the switch on the next scheduled refresh window.
Reactive cost: User complaints; intermittent loss of service on a non-critical device; minimal forensic risk.
Rationale: Edge links carry redundant or non-critical loads; preventive switch replacement adds capex faster than the risk justifies.
Firmware end-of-life notice on a deployed VMS
Recommendation: preventive action
Preventive response: Schedule the major-version upgrade in a sandbox; pilot on a single recorder; roll out cluster-wide during a planned maintenance window.
Reactive cost: Vendor support withdraws at the EOL date; a security vulnerability in the deprecated firmware becomes unpatched; the deployment ages outside vendor coverage.
Rationale: Firmware EOL is a known-date event. The migration is a managed scope item; reactive migration after a vulnerability is published is panic-mode procurement.
BMS field-sensor reading slightly out of expected range
Recommendation: preventive action
Preventive response: Calibration verification at next AMC visit; replace the sensor if it cannot be calibrated.
Reactive cost: Control loops use a slightly-wrong sensor reading; energy waste accumulates silently; eventual occupant complaint or audit catches the drift.
Rationale: Sensor drift compounds. The AMC visit cost is constant; the lost-energy cost grows monthly.
· Where to go next
The AMC posture, in the rest of the engineering map.
Engineering
Tools