14.2 Commissioning & Implementation-Phase Integration

A green LED on a reader is evidence that a circuit has voltage. It is not evidence that the facility can detect, delay, assess, and respond the way the design promised. Independent OpenExamPrep teaching for published PSP Domain 3 Task 3 knowledge treats commissioning as a planned, documented proof that installed systems operate together to the owner’s operational concept. Energizing is the earlier, narrower act of applying power, booting firmware, and confirming that devices talk. Exam stems that treat those words as synonyms are offering you a trap.

Energizing is not commissioning

Energizing answers: Did we wire it so it lives? Panels take DC, PoE switches light, cameras grab an address, locks cycle, a test badge opens Door 4 in isolation, and a technician smiles at a laptop. That work is necessary. It is also incomplete. A site can be fully energized and still have no usable alarm map, no camera call-up, clocks that disagree by seven minutes, badges encoded in the wrong format, and an elevator that ignores fire recall because a security override was left asserted.

Commissioning answers: Did we install the system the owner bought? It is a process with a plan, scripts, expected results, exceptions, and sign-off—not a Friday afternoon “we turned it on.” Commissioning walks the security operations center (SOC) workflow: an event appears, it has a priority, a map location, a camera or audio assessment path, an acknowledgment path, and a documented response. If the only person who can run that workflow is the integrator with a service laptop, you energized a product. You did not commission a program.

Write a commissioning plan before the first energize checklist is ticked. The plan names subsystems, interfaces, who witnesses, what “pass” means, and which failures stop occupancy. Energize checklists (polarity, communication, firmware load) feed that plan. They do not replace it.

Implementation-phase systems integration

Design promised interfaces. Implementation is where those interfaces either become muscle memory or become a binder nobody opens. Several integrations show up repeatedly on PSP-style items.

Maps. The SOC graphic must use the same device identifiers as the door and camera schedules, the labels in the ceiling, and the as-built later in this chapter. A beautiful 3-D map that calls Door 4 “Lobby Rear” while the panel says D-04-ACS is a training injury waiting for a forced-open at 02:10. Maps are not decorating. They are how an operator finds the portal without walking the building in the dark.

Alarm priorities. Forced-open, door-held, duress, tamper, communications loss, power supervisory, and video analytics are not equal. Commissioning assigns priority, color, sound, and required action. If every event screams at the same volume, operators learn to silence the queue. If held-open on a break-room leaf outranks a vault forced-open because someone copied a default template, the SOC will fail the first real incident. Priorities belong in the commissioning script, not in whichever panel was programmed last.

Camera call-up. When Door 4 forced-opens, the video management system (VMS) should present the assessment camera (and often a second context view) without the operator hunting a tree of folders. Call-up rules, dwell, and acknowledge behavior are integration, not a luxury codec feature. Analog-era matrix switchers did this with contact closures; modern VMS rules do it with events and camera IDs. If the access panel logs the alarm and the VMS is “working” on a separate wall, you have two products, not an assessment path.

Elevator recall versus security override. Fire-service Phase I recall sends cars to a designated landing when the fire alarm operates; Phase II gives firefighters in-car control. Security floor-restrict, after-hours card control, and “lockdown” outputs that inhibit landings must drop so recall can occur. A security override that traps occupants in a car during recall is a life-safety defect, not a tough-on-intruders feature. Commissioning must test the fire-alarm interface with the elevator contractor and the fire-protection engineer in the room—not a security-only badge test on a Saturday. If the owner wants a security hold on a car, document how that hold yields the instant recall asserts. Exam stems that offer lockdown as a reason to inhibit recall are offering an unsafe answer.

Time sync. Incident reconstruction is a timeline. Access grants, IDS events, and video frames that disagree by minutes are not a record; they are an argument. Network Time Protocol (NTP) (or a site time source feeding NTP) should serve the access control system (ACS), VMS, intrusion detection, and SOC wall. Commissioning checks that a known event—badge at Door 4, camera clip, panel log—shares a timestamp within the tolerance the specification named. Brand diversity is not an excuse for drift. “Close enough for government work” is how a termination investigation loses the clip that mattered.

Badge encoding. Encoding is not a warehouse task you postpone until occupancy. Facility codes, bit formats, smart-card applications versus raw card serial numbers, encoder privileges, and the physical control of the encoding station are implementation controls. A box of cards encoded on a vendor’s default facility code will open any sister site still using that default. Commissioning includes a sample encode, a read-back at a reader, a wrong-format reject, and a documented who-may-encode list. If HR is already badging people onto a construction core that the ACS does not know, you are commissioning a second, unofficial access system.

Phased occupancy and the SOC-workflow trap

Phased occupancy means people live or work in part of the site while other floors are still construction. It is common and it is dangerous when unexplained. Who holds construction cores versus production badges? Which doors are on the live ACS versus carpenter wedges? Is detection complete on the occupied floor, or is a fire watch and a written impairment in place? Commissioning in a phase is not “the east wing cameras have pictures.” It is a who-is-protected statement the owner’s representative signs: these portals are live, these are still construction, these life-safety interfaces are tested, and the SOC knows which alarms are real.

The signature trap of this section is quieter than a dark camera. Each subsystem “works.” Every door grants locally. Every camera records to a share. Every motion sensor trips a light on a keypad. The elevator contractor signed a recall test last month. And yet: the SOC map does not match labels, held-open outranks duress, Door 4 does not call a camera, video is seven minutes off the badge log, and the operator’s playbook still says “call the integrator.” That site was energized. It was not commissioned.

Worked warehouse: Door 4 grants, the dock camera records, the IDS zone on the man-door shows a green ready light. A forced-open at 02:10 prints on a local buffer. Nobody in the SOC sees a map flash, no camera pops, and the night operator is watching a different site’s wall. Investigators later stitch three timestamps by hand. Procurement will say the systems were accepted because “everything worked.” The exam answer is that the workflow was never commissioned.

Commissioning close-out is a signed package: scripts, exceptions, and a statement that the SOC can run the design. Power-on photos are exhibits. They are not that package.

Use the diagram when a stem says every vendor signed a start-up sheet. Start-up is the left side. The exam question is usually on the right: maps, priorities, call-up, recall, time, encoding, and a drill the operator can repeat without the integrator’s laptop. If phased occupancy is in the stem, ask who is actually protected tonight—not whether a camera on the construction floor has a picture.