System Integration, Testing, and Commissioning
System Integration, Testing, and Commissioning tests whether separate systems work together and whether documented evidence proves it. Expect questions on point-to-point checks, functional matrices, cause-and-effect testing, punch lists, as-builts, training, and warranty turnover.
Core rules
- Commission in layers: verify power and grounding, then point-to-point wiring, then subsystem operation, then integrated cause-and-effect.
- Use a written test matrix that lists each input, expected output, actual result, and pass or fail. Record device addresses and firmware versions.
- Integrated tests must include fire alarm interfaces, access control release, elevator recall, mass notification, and AV control where applicable.
- Maintain a punch list with owner, due date, and retest status. Retest after any change to wiring, firmware, or configuration.
- Turn over as-built drawings, test records, training records, warranties, and spare parts. Acceptance starts warranty terms.
Worked example
A card-reader door has a mag lock, request-to-exit sensor, door position switch, and fire alarm interface. The test matrix verifies a valid card unlocks, an invalid card denies, the request-to-exit sensor unlocks, the fire alarm releases the lock, power loss releases the lock, and a held-open door generates an alarm. Each result is recorded and signed. A single failed step keeps the door on the punch list.
Traps
Testing devices but not sequences; accepting verbal test results; omitting the fire alarm interface; failing to retest after firmware changes; and starting warranty before acceptance documents are complete.