Security Technology Integration and Maintenance
What this domain covers
Security Technology Integration and Maintenance tests the project lifecycle from site survey through closeout, plus the routine work that keeps systems reliable: acceptance testing, battery calculations, preventive maintenance, troubleshooting, network hygiene, and documentation.
Core rules
- Sequence: survey, design, submittals and approvals, rough-in, cable installation, termination, programming, acceptance test, training, and closeout with as-built drawings.
- Acceptance testing is witnessed and recorded. Fire alarm work follows the NFPA 72 record of completion; intrusion and access control are tested device by device against the design intent.
- Battery calculation for fire systems: (standby current × standby hours) + (alarm current × alarm minutes ÷ 60), then multiply by 1.25 for aging and temperature. Commercial fire systems commonly use 24 hours standby plus 5 minutes alarm.
- Preventive maintenance includes cleaning detectors, load-testing batteries, verifying communications paths, checking logs, testing locks and REX devices, and reviewing firmware.
- Network integration: separate VLANs for cameras and access control, static addressing for recorders, NTP for consistent timestamps, and no default credentials. Remote access through VPN, not port forwarding.
- Troubleshooting order: power, then communications, then device. Substitute a known-good device to isolate faults; do not reprogram a working system to chase a wiring fault.
- Closeout documents: as-builts, cable schedules, IP matrix, device list, test results, warranties, and secure password records.
Worked example
A fire panel has 0.45 A standby and 1.8 A alarm current. Standby: 0.45 × 24 = 10.8 Ah. Alarm: 1.8 × (5 ÷ 60) = 0.15 Ah. Total is 10.95 Ah; multiply by 1.25 to get 13.69 Ah. Select the next standard size above that, such as 18 Ah, rather than a 14 Ah battery that leaves no margin for a cold room or an aging battery.
Traps that cost marks
Applying the 1.25 factor twice, or forgetting it; testing a battery without a load; handing over as-designed drawings instead of as-builts; and disabling updates or security software to make a device work. Also watch for acceptance tests signed without a single device actually being operated.