01 / 01
Case file
Annual Maintenance & Lifecycle Support.
Support that begins after handover.
Documented lifecycle support and AMC programmes for systems we built and systems we inherit — preventive and corrective work, periodic health checks, response targets documented in the AMC scope, and spares held against your active deployment. This is the Maintain stage of the lifecycle, distinct from turnkey delivery.
| Aspect | Invoice-only AMC | Documented programme |
|---|---|---|
| Coverage | A different vendor per system | CCTV, fire alarm, AV, BMS and UPS on one calendar |
| Scope | Unwritten, reactive | Written preventive and corrective schedule per system |
| Response | Best-effort | Targets documented in the AMC scope |
| Recovery readiness | None | Offline spares and firmware baseline held |
Educational comparison — not about any specific installer.
Lifecycle support
Keeping systems healthy after handover
An AMC is the lifecycle layer that begins once a system is live. It is not a second build — it is planned, recurring care: preventive health checks, corrective attention when something needs it, and a documented scope so everyone knows what is covered.
- Plan
- Design coordinate
- BOQ / scope align
- Supply
- Install
- Integrate
- Test
- Commission
- Handover
- Maintain
- Preventive, then corrective
- Scheduled health checks come first, so issues are caught before they interrupt operation; corrective work handles what the checks surface.
- What the scope covers
- Each AMC is written as a scope: which systems are included, what is checked, and how often. Response targets are documented in the AMC scope rather than promised in the abstract.
- What changes the AMC scope
- Adding systems, extending sites or raising the level of cover changes the scope — so the AMC is sized to the estate it actually supports, and revisited as that estate grows.
- Records that carry forward
- Visits and findings are logged, so the system's history travels with it and informs the next planning cycle.
/ The discipline, in detail
How we approach annual maintenance & lifecycle support.
Delivery ends at handover; reliability is everything after it. Most AMC contracts in this industry are an invoice in search of a service. We do this differently. Every AMC we sign carries a written schedule of preventive and corrective checks specific to the systems on site, response targets documented in the AMC scope, and a spares-and-firmware baseline stored offline so we can rebuild a controller from a clean slate if the worst happens. Inherited systems — installed by other integrators or by an in-house team that has since moved on — are audited, stabilised and brought onto the same programme. Coverage and response targets are matched to how critical each system is, subject to project scope.
On record
Every annual maintenance & lifecycle support engagement is documented end-to-end — design, programming, commissioning, calibration — and handed over with the files our successors would need if we were never to return.
/ Engineering rail
Concept through commissioning — and after
The lifecycle rail an AMC inherits — every stage before handover produces the documentation preventive maintenance runs on.
Diagrammatic view — a system planning illustration for design discussion, not a project drawing or live interface.
/ Three lenses on the same system
Read it the way you actually need it.
Three short readings of annual maintenance & lifecycle support — for a non-engineer who needs the picture, an engineer who needs the spec, and a buyer who needs to see the system in operation.
/ In simple terms
A multi-system AMC puts a building's technology — CCTV, fire alarm, AV, BMS, UPS and networking — under one maintenance contract with one accountable team, one preventive calendar and one report, instead of a different vendor per system. TechnoGuru runs these programmes from Guwahati across North-East India, for systems we installed and systems we inherit, with spares held against each site's actual equipment.
/ Technical explanation
An AMC programme is structured as an audited asset register, per-discipline preventive calendars derived from the engineering pack (IS 2189 cycles on fire alarm, storage and firmware rounds on CCTV, measured re-verification on AV, schedule and alarm reviews on BMS, battery state-of-health on UPS), criticality-tiered response targets documented in the AMC scope, a deployment-specific spares pool and versioned offline configuration baselines. Multi-system contracts additionally own the cross-system cause-and-effect seams — fire-to-PA priority, access release, BMS interlocks — that per-vendor contracts leave unowned.
/ Real project usage
The Tinsukia Medical College & Hospital estate has operated under our active AMC for over a year, with the clinical engineering team running the VMS day-to-day while our calendar covers the fire, surveillance and access layers; the Capital Cultural Hall, Kohima and Town Hall, Dimapur PA systems carry quarterly voice-evacuation priority tests under the same discipline. Commercial scope is always per estate — share your asset list or BOQ for a written AMC estimate after review.
/ System architecture
The layers, named.
Every layer below is engineered as one piece of the integrated stack. Each carries its own commissioning artefact and its own AMC inclusion.
- 01
Asset register and audit baseline — every AMC begins with a documented register of what is actually on site: every panel, camera, controller, amplifier, switch and UPS with its serial number, firmware version and configuration state. For inherited estates the register is built during a paid audit before the contract is signed, so neither side inherits silent surprises.
- 02
Per-discipline preventive calendars — each system class carries its own written calendar derived from the engineering pack and the manufacturer's maintenance data: fire alarm on quarterly cause-and-effect cycles, CCTV on monthly storage checks and quarterly firmware rounds, AV on measured re-verification against the commissioning report, BMS on schedule and alarm reviews, UPS on battery load-testing. The calendars are published to the client, not held privately.
- 03
Response-tier structure — faults are classified by criticality, with life-safety systems at the top of the hierarchy and response targets documented in the AMC scope per tier. A fire-panel fault and a boardroom display fault do not share a queue.
- 04
Deployment-specific spares pool — spares held in our Lachit Nagar, Guwahati office, sized against the site's actual equipment list and the manufacturer's MTBF data, so a failed controller is a swap rather than a procurement cycle.
- 05
Offline configuration baselines — every programmable device's configuration is captured to versioned, encrypted offline storage on each visit that changes it, so a corrupted panel or controller can be rebuilt from a clean slate in hours rather than days.
/ Design considerations
The decisions we take early.
- One multi-system contract versus per-vendor contracts is the first scoping decision. When CCTV, fire alarm, AV, BMS and UPS sit under one AMC, the integration seams between them — fire-to-PA priority, access-release on alarm, BMS interlocks — have a single accountable owner. Under per-vendor contracts those seams belong to nobody, and they are where buildings fail.
- Comprehensive versus non-comprehensive coverage is decided per system class, not per site: parts-inclusive coverage suits high-criticality systems whose downtime is expensive; labour-with-spares-billed suits stable, low-churn systems. We recommend a mix per estate and put it in writing rather than defaulting everything to one model.
- Criticality mapping drives everything else — which systems get after-hours cover, which fault classes reach an engineer's phone, which visits need the operations team present. The mapping is agreed with the client at contract stage and revisited at renewal.
- Inherited systems enter through an audit, never straight onto a calendar — an installed base from another integrator is documented, stabilised against a written plan and only then brought onto the preventive programme.
- Commercial scope is prepared per estate after review — TechnoGuru does not publish AMC rate figures; share your asset list or BOQ and the site's criticality expectations for a written AMC estimate after review.
/ Integration logic
How it talks to the rest.
- Cross-system cause-and-effect re-testing — the quarterly fire-alarm test exercises PA voice-evacuation priority, access-control release, AHU interlocks and BMS event reporting in the same visit, because the matrix spans systems and so must the test.
- One visit, many disciplines — a multi-system AMC visit is planned so the CCTV storage check, the fire battery load-test, the AV baseline verification and the BMS schedule review land in one coordinated window, with one consolidated report to the facilities team instead of four vendor PDFs.
- Escalation into lifecycle planning — recurring faults on an ageing system trigger a migration recommendation with staged options, so refresh becomes a planned capital decision rather than a forced one driven by failure.
- BMS as the health dashboard — where a BMS exists, AMC-relevant monitoring points (UPS state, pump status, panel faults) are surfaced onto the client's dashboard so the operations team sees between visits what we would see on one.
/ Failure scenarios
What goes wrong, in practice.
- Fragmented AMCs orphan the integration seams — the CCTV vendor maintains the cameras, the fire vendor maintains the panel, and nobody re-tests whether the fire alarm still bookmarks the cameras or releases the doors. The gap is found only when the seam is needed. A single multi-system contract exists precisely to own these seams.
- Preventive calendar drift — an AMC that started with quarterly visits quietly degrades into visit-on-complaint. Mitigated by a published calendar the client can audit, and renewal metrics that track calendar adherence rather than response speed alone.
- Battery fleets ageing in silence — fire-panel, access-controller and UPS batteries degrade on different curves; without scheduled load-testing the failures surface together during the first long outage. Load-tests and proactive replacement windows per battery class are written into the calendar.
- Configuration lost with vendor churn — the original installer holds the only copy of the panel or processor programming and exits the relationship. Mitigated by capturing offline configuration baselines during the inheritance audit, before any other work begins.
- Firmware frozen at commissioning — camera, controller and DSP estates run years-old firmware because nobody owns the update calendar, and vulnerabilities and incompatibilities accumulate. The AMC carries a per-estate firmware calendar with staged rollouts.
/ Maintenance expectations
What the AMC actually delivers.
- CCTV — monthly storage-consumption check against the retention model, quarterly firmware calendar, annual lens-and-housing cleaning, VMS database integrity checks and a per-camera health report.
- Fire alarm — quarterly panel battery load-test, manual call-point and sounder tests per zone, rotating cause-and-effect verification, annual full-matrix re-test with a signed record, and five-year detector sensitivity testing per IS 2189.
- AV and PA — DSP configuration baseline capture, amplifier and speaker-line checks, wireless-microphone spectrum review, and re-verification of measured room targets where the commissioning report set them.
- BMS — schedule review against actual occupancy, alarm-management review with the operations team, controller battery checks, and sub-meter calibration on the annual cycle.
- UPS and power — battery state-of-health per cabinet with replacement flagged at degradation thresholds, transfer testing, and environment checks on the rack and battery room.
- Every visit closes with a written service report; every quarter closes with a consolidated health report across the disciplines under contract — the document renewal decisions should be made on.
/ Where we deploy this
Active across 8 sectors.
Annual Maintenance & Lifecycle Support is rarely a standalone brief — it sits inside a wider sector practice with its own codes, expectations and operating rhythm.
Residential
The premium home, made quiet.
Hospitality
Guest experience, engineered.
Commercial & Corporate
Workplaces that begin meetings on time.
Education & Institutions
Schools, colleges and universities.
Healthcare
Hospitals where systems serve the patient.
Government & Public Safety
Mission-grade integration.
Retail & Malls
Footfall, loyalty, footprint.
Industrial & Warehousing
Operations that don't take a day off.
/ Integration with
How annual maintenance & lifecycle support talks to the rest.
A serious deployment of this system rarely operates in isolation. The disciplines below most commonly share its cabling pathways, its controller logic, and its cause-and-effect matrix.
Building Management System (BMS)
The building, on a single dashboard.
Open-protocol BMS frameworks — HVAC, lighting, fire and access integrated to a single graphical front-end with operator analytics and alarm escalation.Fire Extinguishers & Fire-Protection Goods
First response, within arm's reach.
Portable fire extinguishers — one of the three fire families (fire alarm, fire hydrant, fire extinguishers) — ABC dry powder, CO2, clean-agent, foam and water classes, with site-assessed placement, mounting, signage, refilling and AMC, along with related fire-protection goods and accessories.
/ Read deeper
The engineering, in long form.
Each article below goes deeper than this service page can — a full walk-through of the engineering decisions, written by the team that delivers this work.
- Method · 9 min
AMC strategy: how to scope a maintenance contract that genuinely keeps systems alive
An AMC is either the discipline that keeps a building's systems quietly working for fifteen years or a quarterly billing exercise that produces a dusty visit report and nothing else. The four-axis scoping framework — preventive calendar, response targets, parts inclusion, configuration discipline — that decides which kind you are buying.
Read article - Method · 6 min
What architects should ask their integrator before specifying anything
A short briefing for the architect's first meeting with a systems integrator — the questions that surface design intent, programming discipline, AMC structure, and the seams that decide whether the install respects the architecture.
Read article
Engineering toolkit
Tools to scope this work
Calculators and reference checkers we use ourselves to sense-check the engineering before any drawings change hands.
- ELV · Surveillance · Storage
CCTV Storage Retention Calculator
Multi-brand, codec-aware CCTV storage retention sizing across a verified, source-cited camera-profile catalogue including Hikvision, Dahua, Axis, Hanwha, Bosch, Honeywell, CP Plus, Ubiquiti, Verkada, Meraki, Avigilon, Pelco and more. Computes storage TB, HDD count plan, recorded bandwidth and an NVR/VMS class recommendation against camera count. Pairs with the CCTV Coverage Calculator.
50 brands · codec-awareOpen - Readiness
Access Control Readiness Checker
A readiness self-check before a door-access or attendance conversation — door-survey status, credential considerations, integrations, privacy-policy and operations readiness. No door counts, layouts or reader placement; statuses only.
Advisory · readinessOpen - Handover
System Handover Readiness Checker
Score a project's handover readiness across as-builts, test records, O&M manuals, warranties, spares, training, credential transfer and the AMC decision — and get the chase list to close the gaps. Statuses only; no credential capture.
Advisory · readinessOpen
/ Engineering concepts
Related engineering concepts
Concept
AMC Tier Model (Bronze · Silver · Gold · Mission-Critical)
Four-tier AMC framework — Bronze (annual PM), Silver (quarterly PM + remote diagnostics), Gold (monthly PM + documented support windows), Mission-Critical (contracted critical-hours support with on-site spares).
Concept
Design-for-Handover Discipline
The discipline of engineering systems from the perspective of the operator who will inherit them — labelled panels, archived configuration baselines, plain-language manuals and a documented schedule of every load.
Concept
Preventive Maintenance Rhythm
Scheduled checks against a documented baseline — filter cycles, firmware refresh, configuration backup, simulated cause-and-effect drills and a small parts pool held against the deployment's specific SKU set.
Concept
BACnet Protocol
ISO-standard data-communication protocol for building automation. The default language for modern HVAC, lighting and BMS controllers — enables multi-vendor integration.
/ Used alongside
Commonly deployed alongside
Service
Fire Alarm System
Detection that pinpoints. Response that is coordinated.
Service
CCTV & Surveillance
Coverage. Storage. Evidence.
Sector
Hospitality
Guest experience, engineered.
Service
Enterprise Network Design & Installation
Wires the building's nervous system.
Service
Building Management System (BMS)
The building, on a single dashboard.
Sector
Healthcare
Hospitals where systems serve the patient.
/ Plan it right
Annual Maintenance & Lifecycle Support — getting the brief right.
Common mistakes to avoid
- Signing an AMC on a price-per-visit basis instead of on response targets, spares and the systems actually covered.
- Letting configuration files, passwords and licence registers stay with the integrator instead of the owner.
- No preventive calendar, so systems are only touched once they have already failed.
- No deployment-specific spares, so a failure waits weeks for a part instead of hours.
- Inheriting a system without an audit and a written baseline, so faults later become disputes.
What to share before a quotation
- An inventory of the installed systems, brands and their current state.
- The handover / as-built documentation and any existing AMC history.
- Response and coverage expectations (hours, after-hours, criticality per system).
- Whether spares are to be held against the deployment.
- Whether TechnoGuru installed the systems or is inheriting them.
/ Frequently asked
Annual Maintenance & Lifecycle Support — what buyers ask first.
Will you AMC systems we did not install?
Yes — we AMC inherited systems on most platforms we have factory-trained engineers for. We open every inheritance with a paid audit, document the baseline state, and put a written stabilisation plan in place before signing the AMC so neither of us inherits silent surprises.
What does an AMC cost?
AMC scope is matched to your systems and support expectations rather than published as a fixed band. Specialist systems (Rako, addressable fire panels, hospital nurse-call) carry a heavier programme than standard active systems (CCTV, fire, BMS, automation). What it costs depends on response targets, after-hours coverage, parts inclusion and the number of disciplines under one umbrella — share your asset list or BOQ for a written AMC estimate after review.
Will you AMC systems we did not install?
Yes — for most platforms we have factory-trained engineers on. We open every inheritance with a paid audit so we document the baseline state, identify systems that need stabilisation before they fail, and quote the AMC against verified condition rather than wishful estimate. We will not take on inherited systems we cannot service safely.
How are response targets documented?
Within Guwahati metropolitan area, response targets are documented in the AMC scope, with critical-system escalation available for specific sites under premium AMC. Outside Guwahati, response is structured around scheduled rotations through the city plus emergency mobilisation where the criticality justifies it. Targets are written into the contract, not promised verbally.
How do firmware updates and configuration changes get managed?
Through our offline baseline system. Every active installation has its current configuration and firmware versions captured to encrypted, versioned storage on our infrastructure. Updates are tested against this baseline before being pushed to your site. If anything goes wrong, recovery is hours not days because the working configuration is always retrievable.
Can we change AMC scope mid-contract?
Yes — adding new equipment to the AMC, changing response-time tier, or adding after-hours coverage are common mid-contract changes. We document the variation, adjust the fee proportionally, and update the SLAs in writing. Reductions in scope are also possible at the next renewal.
· Begin
Begin a
annual maintenance & lifecycle support
brief.
Tell us about the building, the timeline, and what success looks like a year after handover. We will reply within two working days with a written response, not a sales pitch.