NOTE This Standard covers the design, furnishing, installation, configuration, testing, and commissioning of a complete IP-based video surveillance system (VSS). (1.1)

NOTE A video surveillance system is a network of digital cameras that capture, encode, transmit, record, and present moving imagery for the security, safety, and operational awareness of a facility. In contemporary construction the system is wholly IP-based: each camera is a network endpoint, video travels over structured cabling as Ethernet, recording is performed by software (a network video recorder or video management server), and operators view live and recorded video on networked workstations. The legacy analog "closed-circuit television" architecture of coaxial home-runs and discrete digital video recorders is obsolete for new work and is not addressed here. (1.2)

NOTE The VSS is an electronic safety and security system, classified by the National Electrical Code as power-limited (Class 2 or Class 3) signaling and communications wiring, not a power system. (1.2.1)

NOTE 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. (1.2.2)

NOTE Where this Standard references shared structured cabling, network backbone, or IT-managed patch fields, those elements are governed by Structured CablingStructured Cabling SystemsResolves to the current edition.sync/structured-cabling and the VSS design shall coordinate with, not duplicate, that infrastructure. (1.2.3)

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 Access Control SystemsAccess Control SystemsResolves to the current edition.sync/access-control-systems, alarm-triggered camera presets with Fire Alarm SystemsFire Alarm SystemsResolves to the current edition.sync/fire-alarm-systems, and shared monitoring displays with Mass Notification SystemsMass Notification SystemsResolves to the current edition.sync/mass-notification-systems. (1.2.4)

NOTE Acceptance and performance testing of the installed VSS shall be performed in accordance with the project's electrical acceptance program. (1.3)

NOTE Field acceptance, continuity-of-recording verification, and network commissioning shall follow Electrical Acceptance TestingElectrical Acceptance TestingResolves to the current edition.sync/electrical-acceptance-testing where a project-wide acceptance program is specified. (1.3.1)

NOTE ONVIF is an industry interoperability specification published by the Open Network Video Interface Forum, not an ANSI, IEEE, or UL consensus standard; it is cited by profile name because it is the dominant open-architecture compatibility benchmark for VSS equipment. (2.2.1)

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. (4.1)

NOTE 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. (4.2)

NOTE NDAA Section 889 prohibits the use of video surveillance and telecommunications equipment from designated manufacturers, whose components are widely redistributed under white-label and OEM brands; a clean-looking nameplate does not establish compliance, which is why a supply-chain attestation rather than a brand check is required. (4.3.1)

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. (5.1)

NOTE Camera selection drives every downstream parameter: power class, cable run, storage, bandwidth, VMS licensing, and mounting. The decision is made per coverage objective, not per catalog page. (6.1)

NOTE Camera technology types differ in coverage geometry, power draw, and license cost, and are selected by the surveillance objective of each location: (6.1.1)

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. (6.1.2)

NOTE A camera without adequate WDR at a backlit doorway produces a silhouetted, forensically useless image, so WDR is a mandatory selection parameter wherever a bright background sits behind the subject, not an optional upgrade. (6.1.5)

NOTE VSS cameras are powered over the same Ethernet cable that carries their video, by Power over Ethernet, eliminating a separate power circuit at most camera locations; the controlling design decision is matching the switch port power class to the worst-case camera load. (7.1)

NOTE The single most common VSS power failure is specifying an 802.3af (15.4 W) switch for a camera whose IR illuminator, heater, or blower briefly draws far more, so the port must be sized to worst-case draw — typically in cold-weather start-up — never to the camera's nominal rating. (7.1.1)

NOTE VSS camera cabling is a power-limited communications circuit governed by NEC Articles 725 and 800; it is frequently added to shared horizontal infrastructure, which makes coordination with the structured cabling design a recurring failure point. (8.1)

NOTE Failing to convert long or inter-building exterior runs to fiber is a classic latent defect: the copper link passes at install temperature, then drops frames or loses PoE at distance or under ground-potential stress months later. (8.1.4)

NOTE Recording is performed by software — a centralized video management server, a standalone network video recorder appliance, or a hybrid cloud-managed platform — and the storage it consumes is the parameter most often undersized in the field. (9.1)

NOTE 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. (9.1.2)

NOTE 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. (9.1.4)

NOTE 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. (9.1.7)

NOTE 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. (9.1.10)

NOTE Analytics turn raw video into events — motion, line crossing, loitering, crowd formation, plate reads — and shift processing load onto the camera edge or the VMS server, which must be sized for it. (10.1)

NOTE Operators view live and recorded video on networked workstations and wall monitors; the count and placement of viewing positions are a design decision coordinated with the security operations concept. (11.1)

NOTE A network camera is an unattended computer on the building network; an unhardened VSS is a documented intrusion path, so cybersecurity is a construction requirement, not an IT afterthought. (12.1)

NOTE Cameras ship with published default credentials, ship dates old enough that firmware is already out of date, and full IP reachability — each of which is a known attack vector that the commissioning steps below close before the system goes live. (12.1.1)

NOTE 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. (12.1.7)

NOTE The VSS rarely stands alone; its value multiplies when camera events link to access control, alarm, and notification systems, but those interfaces must be defined in the specification and confirmed in shop drawings before rough-in, not improvised at commissioning. (13.1)

NOTE Acceptance testing proves the installed system actually records usable, complete, recoverable video for the full retention period — the only outcome the Owner is buying — rather than merely confirming that cameras power on. (14.1)

NOTE Installation workmanship determines whether the design's coverage is actually achieved; a correctly specified camera aimed at the wrong height or backlit by an unanalyzed window still fails forensic review. (15.1)

NOTE Cameras, recorders, and storage drives are sensitive electronic and optical assemblies; field damage from improper handling appears as dropped pixels, fogged domes, and early drive failure long after the responsible party has left. (16.1)

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. (17.1)

NOTE A VSS is only useful while it is fully covering its scene; a stock of on-site spares lets the Owner restore a failed camera in hours rather than the weeks of a procurement cycle, during which that scene is unmonitored. (18.1)