A security system gets commissioned on a Friday. Everyone signs. Six weeks later half the analytics are switched off, two cameras point at a wall and the control room has gone back to watching a live wall nobody records from.
Nothing broke. The handover did.
Operate is a phase, not a formality
Most contracts end at practical completion. The scope covers design, supply, install and commission. Operation sits outside the fence, owned by a client team who joined the project at the training session.
Treat operation as the final phase with its own budget, its own milestones and its own acceptance. The project ends when the site runs the system unaided for a defined period, not when the last invoice clears.
A system nobody operates correctly is an expense with a warranty.
Train on the real system, in the real room
Classroom training on a demo rig teaches the menu structure. It does not teach the shift supervisor what to do at 02:00 when the perimeter analytic fires on the third rainy night in a row.
Run training on the live system, in the control room, on the shift patterns people work. Build the scenarios from the site risk register. Then test them.
- Verify an alarm and dispatch a response
- Export evidence for an incident, correctly and defensibly
- Add and remove an access credential
- Check recording health and act on a failure
- Escalate a fault to support with the right information
Train the relief staff as well. A control room with one trained operator has no capability, it has a person.
Documentation people open
The as-built file matters, and it is not the operating manual. Two different documents serve two different readers.
The technical file holds drawings, cable schedules, IP schedules, configuration exports and test results. The operating file holds one page per routine task, written in the words the operators use, with screenshots from the site's own system.
Put the operating pages in the control room, laminated. Put the technical file where the maintenance contractor finds it without phoning the project manager who left the company.
Plan the first year before go-live
Decide these before commissioning, not after the first failure.
- Spares holding. Which items sit on site, which sit with the supplier
- Response times. Written per fault class, with an escalation path
- Preventative visits. Cleaning, focus checks, firmware, storage health
- Performance reporting. Uptime, alarm volumes, false alarm rate, response times
- Change control. Who is allowed to alter a rule, and who signs it off
Change control is the one teams skip. Six months of undocumented tweaks turns a designed system into a configuration nobody understands.
Accept on operation, not on installation
Write two acceptance gates into the contract. The first covers installation and commissioning against the design. The second, thirty to sixty days later, covers operation.
The second gate asks different questions. Are the analytics still enabled. Is the false alarm rate inside the agreed band. Did the operators handle the last five real events correctly. Is recording retention holding at the specified days.
Hold a portion of the payment against the second gate and the whole project team stays interested in the site working, rather than in the site being finished.
The measure of a delivered project
A project is delivered when the client's own people run it, understand it and trust it. Everything before it is construction. Build the operate phase into the plan from day one and the handover stops being the point where value leaks away.