Corpus sync: neutrality remakes, note hygiene, datasheet relocation, transformer-split cross-refs
---
title: Video Surveillance Systems
…26 unchanged lines
### The system comprises cameras, the video management software (VMS) or network video recorder (NVR), video storage, the dedicated network switching that powers and connects the cameras, viewing workstations and monitors, video analytics, and all VSS-dedicated cabling and pathways. {note}
−### Where this Standard references shared structured cabling, network backbone, or IT-managed patch fields, those elements are governed by [[sync/structured-cabling]] and the VSS design shall coordinate with, not duplicate, that infrastructure. {note}
+### Where this Standard references shared structured cabling, network backbone, or IT-managed patch fields, those elements are governed by [[sync/structured-cabling]] and the VSS design shall coordinate with, not duplicate, that infrastructure.
−### Tie-ins between the VSS and other electronic safety and security systems shall be defined here and coordinated with the owning standard: door-event video verification with [[sync/access-control-systems]], alarm-triggered camera presets with [[sync/fire-alarm-systems]], and shared monitoring displays with [[sync/mass-notification-systems]]. {note}
+### Tie-ins between the VSS and other electronic safety and security systems shall be defined here and coordinated with the owning standard: door-event video verification with [[sync/access-control-systems]], alarm-triggered camera presets with [[sync/fire-alarm-systems]], and shared monitoring displays with [[sync/mass-notification-systems]].
−## Acceptance and performance testing of the installed VSS shall be performed in accordance with the project's electrical acceptance program. {note}
+## Acceptance and performance testing of the installed VSS shall be performed in accordance with the project's electrical acceptance program.
### Field acceptance, continuity-of-recording verification, and network commissioning shall follow [[sync/electrical-acceptance-testing]] where a project-wide acceptance program is specified. {note}
…110 unchanged lines
# Quality Assurance {toc}
−## The installing contractor shall be a licensed low-voltage electronic security contractor regularly engaged in IP video surveillance work and certified by the manufacturer of the specified VMS or NVR platform. {note}
+## The installing contractor shall be a licensed low-voltage electronic security contractor regularly engaged in IP video surveillance work and certified by the manufacturer of the specified VMS or NVR platform.
## A surveillance system that records unusable imagery is worse than no system at all, because the Owner believes an event is covered when it is not. Quality assurance for a VSS is therefore less about the components, which are commodity network devices, and more about the design judgment that places, aims, powers, and sizes them. The clauses below place that judgment on a responsible, qualified party and require it to be demonstrated before, not after, the work is buried. {note}
…26 unchanged lines
# Environmental and Service Conditions {toc}
−## Each camera shall be selected and rated for the environment of its mounting location; an indoor-rated camera in an exterior or washdown location will fail prematurely, and an under-rated enclosure is the most common avoidable VSS field failure. {note}
+## Each camera shall be selected and rated for the environment of its mounting location; an indoor-rated camera in an exterior or washdown location will fail prematurely, and an under-rated enclosure is the most common avoidable VSS field failure.
### Exterior cameras shall be rated NEMA 4X or IP66 minimum and shall include an integral or accessory housing heater and blower where the design ambient falls below the camera's rated operating temperature.
…37 unchanged lines
- License plate recognition (LPR) cameras use a specialized lens, shutter, and integral IR to capture plates reliably and require dedicated VMS analytics licensing.
−### Camera resolution shall be selected to the surveillance objective; higher resolution improves forensic detail but multiplies storage and bandwidth, so it is specified per zone, not maximized blanket-wide. {note}
+### Camera resolution shall be selected to the surveillance objective; higher resolution improves forensic detail but multiplies storage and bandwidth, so it is specified per zone, not maximized blanket-wide.
### The default resolution for general interior surveillance shall be 4 MP; 2 MP (1080p) is the minimum acceptable for any new camera, and 8 MP (4K) shall be used for wide-area and forensic-critical zones.
…124 unchanged lines
### The VMS or NVR platform shall be ONVIF-conformant and shall support, at minimum, ONVIF Profile T for advanced streaming and H.265, so that cameras from more than one manufacturer interoperate without lock-in.
−### Specifying no minimum ONVIF profile is what produces single-vendor lock-in: a mixed-manufacturer camera fleet will not stream, control, or record through the VMS unless a verified profile is required up front. {note}
−
−### Video shall be compressed using H.265 (HEVC) by default, with H.264 used only where legacy VMS compatibility requires it, and shall use variable bit rate with a maximum bitrate cap.
−
−### Compression codec choice is the largest single lever on storage and bandwidth: H.265 cuts both roughly in half versus H.264, but only if every recording device in the path supports it, which is why the codec is verified at the VMS, not assumed from the camera. {note}
−
−### Frame rate shall be specified at the recorder for each camera: 5 fps minimum for archival and low-motion zones, 15 fps default for general interior, and 30 fps for cashier, turnstile, entry, and forensic zones.
−
−### Video retention shall meet the Owner's policy: 7 days minimum for low-risk zones, 30 days default for commercial and institutional facilities, and 60 to 90 days for financial, healthcare, and critical-infrastructure facilities.
−
−### Recording-mode selection — continuous, motion-triggered, scheduled, or hybrid — drives storage, and continuous recording at full frame rate roughly doubles motion-triggered storage; the chosen mode shall be reflected in the storage calculation. {note}
−
−### Network video recorder storage shall be configured with RAID-5 redundancy at minimum, with hot-swappable drives, so that a single drive failure does not interrupt recording.
−
−### Storage shall be sized using realistic average bitrate for active, high-motion scenes, not the manufacturer's best-case calculator figure, and shall include a headroom factor of at least 1.5.
−
−### A storage array sized from the calculator's minimum-bitrate, low-motion assumption routinely runs out two to three times early on busy scenes, silently shortening the retention the Owner was promised; the 1.5 headroom factor exists to absorb that gap. {note}
−
```datasheet
label: VMS / NVR platform architecture
…16 unchanged lines
```
+### Specifying no minimum ONVIF profile is what produces single-vendor lock-in: a mixed-manufacturer camera fleet will not stream, control, or record through the VMS unless a verified profile is required up front. {note}
+
+### Video shall be compressed using H.265 (HEVC) by default, with H.264 used only where legacy VMS compatibility requires it, and shall use variable bit rate with a maximum bitrate cap.
+
```datasheet
label: Compression codec
…5 unchanged lines
```
+### Compression codec choice is the largest single lever on storage and bandwidth: H.265 cuts both roughly in half versus H.264, but only if every recording device in the path supports it, which is why the codec is verified at the VMS, not assumed from the camera. {note}
+
+### Frame rate shall be specified at the recorder for each camera: 5 fps minimum for archival and low-motion zones, 15 fps default for general interior, and 30 fps for cashier, turnstile, entry, and forensic zones.
+
```datasheet
label: Recording frame rate
…7 unchanged lines
```
+### Video retention shall meet the Owner's policy: 7 days minimum for low-risk zones, 30 days default for commercial and institutional facilities, and 60 to 90 days for financial, healthcare, and critical-infrastructure facilities.
+
```datasheet
label: Video retention period
…8 unchanged lines
```
+### Recording-mode selection — continuous, motion-triggered, scheduled, or hybrid — drives storage, and continuous recording at full frame rate roughly doubles motion-triggered storage; the chosen mode shall be reflected in the storage calculation.
+
```datasheet
label: Recording mode
…7 unchanged lines
```
+### Network video recorder storage shall be configured with RAID-5 redundancy at minimum, with hot-swappable drives, so that a single drive failure does not interrupt recording.
+
```datasheet
label: Storage redundancy (RAID level)
…6 unchanged lines
```
+### Storage shall be sized using realistic average bitrate for active, high-motion scenes, not the manufacturer's best-case calculator figure, and shall include a headroom factor of at least 1.5.
+
```datasheet
label: Storage headroom factor (over calculated)
…6 unchanged lines
```
+### A storage array sized from the calculator's minimum-bitrate, low-motion assumption routinely runs out two to three times early on busy scenes, silently shortening the retention the Owner was promised; the 1.5 headroom factor exists to absorb that gap. {note}
+
+### Edge-storage failover shall be specified for each camera based on the criticality of maintaining recorded video during a network loss.
+
```datasheet
label: Edge-storage failover (microSD) on network loss
…72 unchanged lines
### All VSS cameras and recorders shall reside on an isolated, dedicated surveillance VLAN segmented from the general building network.
−### Video streams and management traffic shall be encrypted using TLS 1.2 at minimum.
−
−### Firewall rules permitting only the required VSS traffic shall be configured by the Owner's IT representative before acceptance testing begins, and remote VMS access shall be permitted only through approved, encrypted channels.
−
−### VLAN configuration, IP address allocation, and firewall rules are owned by the IT and network contractor, not the security contractor, so the coordination meeting and a written cutover of these items shall precede any connection of cameras to the live network. {note}
−
```datasheet
label: Network segmentation
…6 unchanged lines
```
+### Video streams and management traffic shall be encrypted using TLS 1.2 at minimum.
+
```datasheet
label: Minimum stream encryption
…5 unchanged lines
```
+### Firewall rules permitting only the required VSS traffic shall be configured by the Owner's IT representative before acceptance testing begins, and remote VMS access shall be permitted only through approved, encrypted channels.
+
+### VLAN configuration, IP address allocation, and firewall rules are owned by the IT and network contractor, not the security contractor, so the coordination meeting and a written cutover of these items shall precede any connection of cameras to the live network. {note}
+
# Integration Interfaces {toc}
…89 unchanged lines
# Warranty {toc}
−## The warranty shall cover the assembled, configured system — not just the boxes — because a VSS failure is usually a configuration, integration, or storage-sizing defect rather than a dead component. {note}
+## The warranty shall cover the assembled, configured system — not just the boxes — because a VSS failure is usually a configuration, integration, or storage-sizing defect rather than a dead component.
### The Contractor shall warrant all materials, software, and workmanship against defects for the period specified below from the date of Owner acceptance.
…44 unchanged lines
default: 1
```