/ Engineering · Operations
The day-two discipline,
made operational.
AMC cadence, incident response, preventive replacement, firmware governance — the operational artefacts that turn a handed-over system into a system the operations team actually owns.
- Operations workflows
- 2
- Operations principles
- 4
- Total planner stages
- 22
- Day-two artefacts
- AMC pack · Trend baseline · Firmware register
/ maintenance
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 24/7 incident response.
operations
Scheduled site inspection
Walk the building against the AMC checklist — visual, electrical and integration spot checks.
- · Inspection record
- · Updated punch list
Duration · 1 day (quarterly cadence)
operations
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.
- · Replacement record
- · Updated component lifecycle register
Duration · 2–5 days (annual)
operations
Firmware review window
Review device firmware against the manufacturer release notes — patch security advisories, defer feature-only releases.
- · Patch decision log
- · Updated device firmware register
Duration · 1 day (semi-annual)
operations
Incident response
Respond to incidents within the AMC tier SLA. Each incident produces a closure note that updates the trend report.
- · Incident closure note
- · Updated trend report
Duration · Per AMC SLA
/ lifecycle
Lifecycle planner — the 10-year operational window
The decade-long planning view that takes a system from handover through expansion and into retrofit / refresh.
A building system lives for a decade or more. The lifecycle planner is the view that takes the system from handover (year zero) through expansion (years one to four) and into retrofit / refresh (years five to ten). The planner does not predict the future; it documents the decision points where the next reinvestment is expected, so the client can budget against them. The discipline is the decision point — when is the battery string due, when is the BMS supervisory layer due for a major upgrade, when does the addressable fire panel reach end-of-line. Surfacing these in year zero is what distinguishes a 7-stage handover from a 7-stage handover plus a lifecycle plan.
lifecycle
Year zero — stabilisation
First-year stabilisation — snag list closure, trend baseline, first AMC cycle.
- · Stabilisation report (year one)
- · Trend baseline
Duration · 12 months
lifecycle
Years one–four — expansion & incremental upgrade
The incremental expansion window — added zones, added cameras, added scenes. Each expansion produces a mini-commissioning.
- · Expansion design pack
- · Mini-commissioning record
Duration · Across years 1–4
lifecycle
Year five — mid-life review
A formal review of the system against the original requirements pack and the current operational reality.
- · Mid-life review report
- · Refresh recommendation
Duration · 1–3 months
lifecycle
Years six–ten — refresh or retrofit
Roll the system through a refresh (firmware, point devices, ballasts) or a retrofit (panel, supervisory layer, BESS).
- · Refresh / retrofit design pack
- · Migration plan (where applicable)
Duration · Across years 6–10
/ Operations principles
The principles that govern the operational discipline
operations
Graceful degradation over heroic recovery
A system that fails gracefully — fails one zone, not the whole building — is more valuable than a system that promises five-nines.
Read in methodology →maintenance
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 →governance
Operational continuity through documented runbooks
Runbooks turn senior knowledge into operational repeatability. Without them, the FM team improvises every incident.
Read in methodology →governance
Single-point accountability across system seams
Multi-vendor systems integrate at the seams; someone has to own the seams.
Read in methodology →· Operations · The system the operations team owns