14.1 Video Surveillance Systems: Camera Siting, Resolution, Lighting, and Retention Policies

14.1 Video Surveillance Systems: Camera Siting, Resolution, Lighting, and Retention Policies

In mission-critical data center engineering, a Video Surveillance System (VSS)—historically termed Closed-Circuit Television (CCTV)—serves as the primary visual sensing and forensic validation layer within a defense-in-depth physical security architecture. A video surveillance deployment does not merely record incidents after the fact; when properly integrated with electronic access control systems (ACS), perimeter intrusion detection systems (PIDS), and building automation systems (BAS), it provides real-time situational awareness, visual verification of alarm states, and legally defensible forensic evidence.

Modern data center video architectures have largely transitioned from legacy analog composite video baseband systems to high-definition, edge-intelligent Internet Protocol (IP) camera networks. These distributed systems rely on Network Video Recorders (NVRs), centralized or clustered Video Management Software (VMS), and dedicated storage area networks (SAN) or network-attached storage (NAS) fabrics. Designing a VSS that satisfies both stringent regulatory mandates and practical operational demands requires rigorous engineering: establishing exact field-of-view (FOV) criteria, calculating required pixel densities under international standards, eliminating physical sightline occlusions, engineering balanced illumination environments, and accurately dimensioning Petabyte-scale video storage arrays.

---

Video Surveillance Architecture: IP Cameras, NVRs, and VMS

An enterprise-class data center video surveillance topology is comprised of four interconnected functional tiers: the edge sensing layer, the transmission and transport layer, the processing and management layer, and the storage tier.

+---------------------------------------------------------------------------------------------------------+
|                                ENTERPRISE IP VIDEO SURVEILLANCE TOPOLOGY                                |
+---------------------------------------------------------------------------------------------------------+
|  [ EDGE SENSING ]               [ NETWORK TRANSPORT ]           [ MANAGEMENT ]        [ ARCHIVAL ]      |
|  • Fixed Interior Domes   -->   Dedicated Surveillance VLAN --> VMS Management    --> Enterprise SAN/   |
|  • Thermal Perimeter      -->   PoE+ Switches (802.3at/bt)  --> Recording Servers --> NAS Storage Array |
|  • PTZ Slew-to-Cue        -->   Dual Redundant Fiber Uplinks--> Analytics Engines --> (RAID 6 / Hot Sp) |
|  • 4K LPR Gate Cameras    -->   Multicast Traffic Isolation --> Client Consoles   --> 90+ Day Retention |
+---------------------------------------------------------------------------------------------------------+

1. IP Camera Technologies and Image Sensors

Modern surveillance cameras utilize progressive-scan Complementary Metal-Oxide-Semiconductor (CMOS) image sensors ranging in resolution from 1080p Full HD ($1920 \times 1080$ pixels, or $2.1\text{ MP}$) up to 4K Ultra HD ($3840 \times 2160$ pixels, or $8.3\text{ MP}$) and multi-sensor panoramic arrays ($12\text{ MP}$ to $32\text{ MP}$). Enterprise IP cameras incorporate:

• Open Network Video Interface Forum (ONVIF) Compliance: Native conformance to ONVIF Profile S (basic IP video streaming), Profile G (edge storage and retrieval), and Profile T (advanced video streaming and analytics metadata) ensures interoperability between disparate camera hardware and third-party VMS platforms.
• Power over Ethernet (PoE): Cameras are powered via IEEE 802.3af (PoE, up to $15.4\text{ W}$), IEEE 802.3at (PoE+, up to $30.0\text{ W}$), or IEEE 802.3bt (PoE++, up to $60\text{ W}$ to $90\text{ W}$). Outdoor pan-tilt-zoom (PTZ) cameras equipped with internal mechanical heaters, blowers, and high-output infrared illuminators routinely require IEEE 802.3bt.
• Edge Storage Buffering: High-end IP cameras feature onboard industrial-grade microSD/SDXC storage cards ($128\text{ GB}$ to $512\text{ GB}$) executing automatic network failover recording. If the primary IP network drops, the camera writes directly to local flash memory and automatically back-fills missing footage to the central VMS once connectivity is restored.

2. Transport Architecture: Multicast vs. Unicast

Surveillance video streams consume sustained, continuous network bandwidth. Transporting dozens or hundreds of high-bitrate video streams across an enterprise LAN without architectural segmentation can quickly cause network congestion and frame drops:

• Surveillance VLAN Segmentation: Video streams must be isolated on dedicated physical switches or logically isolated Virtual LANs (surveillance VLANs) equipped with Quality of Service (QoS) markings prioritizing video traffic (commonly DSCP AF41).
• Multicast Streaming: When multiple security monitoring consoles, video wall decoders, and redundant recording servers view the same camera stream simultaneously, unicast transmission creates duplicate bandwidth-heavy streams per client ($N \times \text{Bitrate}$). System designers deploy IP Multicast (utilizing Internet Group Management Protocol, IGMPv2/v3, and Protocol Independent Multicast, PIM) to transmit a single video stream across the core network, allowing multiple client endpoints to subscribe to the stream without multiplying network consumption.

3. VMS vs. Standalone NVRs

While small commercial facilities often rely on standalone appliance-based Network Video Recorders (NVRs), enterprise data centers typically use distributed Video Management Software (VMS) architectures. An enterprise VMS decouples the management database, analytics engines, recording daemons, and client display interfaces across virtualized or clustered server nodes. This modular architecture supports $N+1$ recording server failover, centralized Active Directory / LDAP authentication, cryptographic evidence hashing, and centralized health telemetry via SNMP or REST APIs.

---

Camera Siting and Field of View: The IEC 62676-4 DORI Framework

A frequent design mistake in data center physical security is deploying high-resolution cameras without establishing the required optical field of view (FOV) and target pixel density. Simply having a "4K camera" does not guarantee an investigator can identify a trespasser if the camera is equipped with an ultra-wide lens positioned $30\text{ meters}$ away.

To set measurable optical criteria, designers widely use IEC 62676-4 (Video surveillance systems for use in security applications – Part 4: Application guidelines). The standard defines pixel-density levels for viewing objectives (it also lists lower "monitor" and higher "inspect" levels); the four most used are known as the DORI framework:

+---------------------------------------------------------------------------------------------------------+
|                                 IEC 62676-4 DORI PERFORMANCE FRAMEWORK                                  |
+---------------+--------------------+-------------------+------------------------------------------------+
| DORI LEVEL    | MINIMUM PIXEL      | IMPERIAL          | OPERATIONAL & FORENSIC CAPABILITY              |
|               | DENSITY (px/m)     | EQUIVALENT (px/ft)|                                                |
+---------------+--------------------+-------------------+------------------------------------------------+
| 1. Detection  | ≥ 25 px/m          | ≥ 7.6 px/ft       | Enables an operator to reliably determine      |
|               |                    | (approx. 8 px/ft) | whether a human or vehicle is present in FOV.  |
+---------------+--------------------+-------------------+------------------------------------------------+
| 2. Observation| ≥ 62.5 px/m        | ≥ 19 px/ft        | Enables viewing of characteristic details,     |
|               |                    |                   | such as clothing color or general activities.  |
+---------------+--------------------+-------------------+------------------------------------------------+
| 3. Recognition| ≥ 125 px/m         | ≥ 38.1 px/ft      | Enables an operator to determine with a high   |
|               |                    | (approx. 38 px/ft)| degree of certainty whether an individual is   |
|               |                    |                   | the same person seen previously (badge photo). |
+---------------+--------------------+-------------------+------------------------------------------------+
| 4. Identifi-  | ≥ 250 px/m         | ≥ 76.2 px/ft      | Enables positive personal identification       |
|    cation     |                    | (approx. 76 px/ft)| beyond a reasonable doubt; suitable for facial |
|               |                    |                   | recognition and evidential review.             |
+---------------+--------------------+-------------------+------------------------------------------------+

Calculating Pixel Density (PPM)

Pixel density—expressed in Pixels Per Meter (PPM) or Pixels Per Foot (PPF)—is determined by dividing the camera's horizontal sensor resolution by the horizontal field of view width at the target distance:

$\text{PPM} = \frac{\text{Horizontal Resolution } (\text{pixels})}{\text{Horizontal Field of View Width } (\text{meters})}$

$\text{PPF} = \frac{\text{Horizontal Resolution } (\text{pixels})}{\text{Horizontal Field of View Width } (\text{feet})}$

For example, if a 1080p camera ($1920 \times 1080$) has a horizontal field of view width of $7.68\text{ meters}$ ($25.2\text{ feet}$) at a target security portal: $\text{PPM} = \frac{1920\text{ pixels}}{7.68\text{ m}} = 250\text{ px/m}$ $\text{PPF} = \frac{1920\text{ pixels}}{25.2\text{ ft}} \approx 76.2\text{ px/ft}$

This deployment precisely achieves the IEC 62676-4 Identification threshold. If the camera lens were zoomed out to encompass a $16\text{ meter}$ wide courtyard, the resolution would drop to $120\text{ px/m}$, demoting the camera to the Observation level, so it no longer supports positive facial identification.

---

Critical Camera Deployment Zones in Data Centers

Data center security demands targeted optical engineering across five distinct physical zones:

+---------------------------------------------------------------------------------------------------------+
|                                DATA CENTER CAMERA DEPLOYMENT ZONES                                      |
+----------------------------+-----------------------+---------------------+------------------------------+
| FACILITY ZONE              | PRIMARY CAMERA TYPE   | MINIMUM DORI TARGET | CRITICAL DESIGN REQUIREMENT  |
+----------------------------+-----------------------+---------------------+------------------------------+
| 1. Perimeter Fence Line    | Thermal + High-Speed  | Detection (25 px/m) | Virtual tripwires; PIDS slew-|
|                            | Optical PTZ           | to Recog (125 px/m) | to-cue; zero foliage blinders|
+----------------------------+-----------------------+---------------------+------------------------------+
| 2. Vehicular Gates & Lot   | License Plate Recog.  | Identification      | Fast shutter (>1/1000s);     |
|                            | (LPR) + Fixed 4K      | (250 px/m on plate) | retroreflective IR; anti-glare|
+----------------------------+-----------------------+---------------------+------------------------------+
| 3. Entrances & Loading Dock| Wide Dynamic Range    | Identification      | Bi-directional facial capture;|
|                            | (WDR) Minidomes       | (250 px/m at portal)| overhead roll-up door coverage|
+----------------------------+-----------------------+---------------------+------------------------------+
| 4. Corridors & Mantraps    | 180°/360° Fisheye +   | Identification      | Complete anti-tailgating view;|
|                            | High-Res Eye-Level    | (250 px/m at badge) | vandal-resistant IK10 rating |
+----------------------------+-----------------------+---------------------+------------------------------+
| 5. Computer Room Aisles    | Fixed Telephoto Domes | Recognition (125) / | Cross-coverage both ends;    |
|    (White Space)           | at aisle ends         | Ident (250 px/m)    | mounted below cable trays    |
+----------------------------+-----------------------+---------------------+------------------------------+

1. Perimeter Fence Line: Thermal and Slew-to-Cue PTZ

Perimeter boundaries are susceptible to atmospheric obscuration (fog, rain, direct sun glare) and vast distances. A best-practice perimeter design pairs uncooled thermal imaging cameras with high-speed optical PTZ cameras:

• Thermal cameras detect minute differences in emitted infrared heat ($8\mu\text{m}$ to $14\mu\text{m}$ spectral band), easily identifying human intruders breaching a fence line in total darkness, driving rain, or through dense camouflage at distances exceeding $300\text{ meters}$.
• Video analytics detect the fence-line intrusion vector and instantly command the co-located high-speed PTZ camera to perform an automated slew-to-cue maneuver, zooming in on the target coordinates at the Recognition or Identification level while tracking the intruder across the facility grounds.

2. Vehicular Gates and Parking Facilities: License Plate Recognition (LPR)

Standard surveillance cameras fail at capturing vehicle license plates due to headlight glare, rapid vehicle motion, and sharp reflective angles. Dedicated License Plate Recognition (LPR / ANPR) cameras must be deployed:

• High Shutter Speeds: Configured with electronic shutter speeds between $1/1,000\text{ s}$ and $1/2,000\text{ s}$ to completely eliminate vehicle motion blur.
• Optical Bandpass Filters & Infrared: Incorporating high-intensity pulsed $850\text{ nm}$ infrared illumination and optical bandpass filters that reject visible spectrum light, cutting through high-beam headlight glare and capturing retroreflective license plate characters with extreme contrast.
• Geometric Placement: Cameras must be mounted at an angle of incidence no greater than $30^\circ$ horizontally and $30^\circ$ vertically relative to approaching vehicle bumpers.

3. Entrances, Egress Doors, and Loading Docks

All pedestrian exterior entryways and loading docks represent critical containment barriers:

• Cameras must be sited at eye-level ($1.5\text{ m}$ to $1.7\text{ m}$ above finished floor) or downward angles $\le 15^\circ$ to capture frontal facial features rather than the tops of hats or foreheads.
• Loading docks require wide-angle coverage of vehicle bays, overhead roll-up doors, hydraulic dock levelers, and interior staging areas to ensure uninspected freight or unauthorized personnel cannot enter during cargo transfers.

4. Interior Corridors, Mantraps, and Security Vestibules

Security vestibules (mantraps) and access control portals require continuous, uncompromised visual recording:

• In access control vestibules, cameras must achieve the Identification ($\ge 250\text{ px/m}$) threshold directly at the badge reader and biometric scanning interfaces.
• Overhead 360-degree fisheye cameras or dual-lens stereo analytics cameras must be installed inside the mantrap ceiling to provide anti-tailgating verification, confirming that only one individual occupies the chamber between interlocked door cycles.

5. Computer Room White Space Aisles: Mitigating Obstructions

Deploying cameras within data center white space involves unique physical constraints:

• Overlapping Cross-Coverage: Fixed mini-dome cameras must be installed at both ends of every hot aisle and cold aisle. Siting a camera at only one end of a $20\text{ meter}$ row creates severe blind spots behind technicians working on open server racks or standing on ladders.
• Pathways and Containment Occlusion: Overhead multi-tiered cable trays, structured cabling pathways, fiber raceways, overhead power busways, and containment baffles routinely block camera sightlines. Cameras must be mounted to unistrut drops or structural ceiling stanchions positioned below the lowest plane of overhead cable pathways and ductwork.

---

Lighting, Illumination, and Dynamic Range

A camera sensor can only process the photons reflected into its lens. Poor illumination is a common reason recorded video proves useless in investigations.

+---------------------------------------------------------------------------------------------------------+
|                                 SURVEILLANCE ILLUMINATION GUIDELINES                                    |
+-----------------------+--------------------+-------------------+----------------------------------------+
| ENVIRONMENT           | MINIMUM LUX LEVEL  | LIGHTING TYPE     | SPECIAL SENSOR REQUIREMENTS            |
+-----------------------+--------------------+-------------------+----------------------------------------+
| Exterior Perimeter    | 0.0 to 1.0 lux     | 850 nm IR LED     | True Day/Night Mechanical Cut Filter   |
| Parking & Gateways    | 15 to 30 lux       | 4000K-5000K LED   | Minimum CRI ≥ 70; LPR IR assist        |
| Glazed Vestibules     | 50 to 2,000+ lux   | Natural + LED     | True WDR ≥ 120 dB (Multi-exposure)     |
| Corridors & Offices   | 150 to 250 lux     | 4000K LED         | Uniform illumination; Low glare rating |
| White Space Aisles    | 500 horiz/200 vert | Overhead LED Rows | TIA-942/BICSI level at 1 m in aisles   |
+-----------------------+--------------------+-------------------+----------------------------------------+

1. Minimum Illumination and True Day/Night Cameras

• Color Imaging: Many surveillance cameras need roughly $10\text{ to }20\text{ lux}$ or more of ambient light to maintain good color fidelity (sensitivity varies by model). Below this threshold, electronic sensor noise (chroma noise) degrades image sharpness.
• True Day/Night (TDN) Operation: TDN cameras utilize a physical, motorized Infrared Cut Filter (ICR). During daylight hours, the ICR covers the sensor to block infrared light and ensure accurate color reproduction. When ambient light drops below a pre-set threshold (typically $1\text{ to }5\text{ lux}$), the mechanical filter swings away from the sensor, and the camera switches to high-sensitivity monochrome (black-and-white) mode, capturing the near-infrared spectrum.
• Infrared Illuminators: In unlit exterior perimeters, optical cameras need supplemental IR illumination (thermal cameras do not):
  • 850 nm Infrared: Emits a faint, semi-covert red glow at the LED source; highly efficient and matched to standard silicon CMOS sensor sensitivity curves.
  • 940 nm Infrared: Completely covert (invisible to the human eye); needs noticeably more illuminator power (roughly 40% to 50% in typical comparisons) for equivalent images because silicon sensors are less sensitive at $940\text{ nm}$.

2. Wide Dynamic Range (WDR)

Data center entryways, loading dock roll-up doors, and glazed lobbies present extreme light contrast: bright outdoor sunlight ($10,000\text{ to }100,000\text{ lux}$) streaming through an opening while the interior corridor sits at $100\text{ lux}$. A standard camera will either expose for the bright exterior (plunging the intruder's face into complete shadow) or expose for the interior (blowing out the exterior into a washed-out white blur).

• True WDR (Multi-Exposure): Cameras for sunlit portals should feature multi-exposure True WDR, commonly rated about $120\text{ dB}$ (decibels). The sensor captures multiple sequential frames at varying shutter speeds (a short exposure for highlights, a medium exposure for midtones, and a long exposure for shadows) and merges them into a single, perfectly balanced composite frame inside the camera's Digital Signal Processor (DSP).
• Digital WDR (D-WDR): D-WDR is a software gamma adjustment that merely brightens dark pixels digitally, introducing massive sensor noise. D-WDR is not suitable for high-contrast security portals.

---

Video Storage, Codecs, Frame Rates, and Retention Sizing

Video data represents the single largest storage consumer in data center physical security. Sizing storage requires balancing regulatory compliance mandates against network bandwidth and drive array capacities.

1. Compression Codecs: H.264 vs. H.265 (HEVC)

Video compression operates on spatial compression (within a single frame, intra-frame) and temporal compression (between successive frames, inter-frame):

• H.264 (Advanced Video Coding - AVC): Uses macroblocks up to $16 \times 16$ pixels. Standard industry baseline.
• H.265 (High Efficiency Video Coding - HEVC): Employs Coding Tree Units (CTUs) supporting block structures up to $64 \times 64$ pixels. H.265 achieves up to about $50\%$ bandwidth and storage reduction compared to H.264 at similar visual quality and resolution (real savings depend on the scene and encoder).
• Smart Codecs & Dynamic GOP: Enterprise cameras utilize vendor dynamic Group of Pictures (GOP) algorithms. In a static data hall corridor where nothing moves, the camera extends the I-frame (keyframe) interval and drops bitrate down to under $500\text{ kbps}$. The instant an access door opens or motion is sensed, the camera dynamically shortens the GOP interval and increases bitrate to preserve full forensic motion detail.

2. Frame Rate Guidelines

While commercial entertainment operates at $30\text{ to }60\text{ fps}$, human security surveillance operates efficiently at lower frame rates:

• Perimeter & General Hallways: $15\text{ fps}$ provides smooth human motion tracking with half the frames of $30\text{ fps}$; with inter-frame compression, the bitrate saving is usually somewhat less than 50%.
• High-Risk Portals & Mantraps: $20\text{ to }30\text{ fps}$ is deployed at biometric turnstiles, mantraps, and loading dock cash/pallet exchanges to prevent rapid hand sleight-of-hand or credential swapping from evading detection.

3. Compliance Retention Mandates

Data centers retain recorded (compressed) footage for periods set by policy, contracts, and applicable standards:

• Baseline Enterprise Policy: Minimum $30\text{ days}$ of continuous recording.
• SOC 2 Type II: Sets no fixed retention period; auditors test the retention the organization commits to (commonly about 90 days) and need footage available for audit sampling.
• PCI DSS v4.0.1 Requirement 9.2.1.1: Individual physical access to sensitive areas within the cardholder data environment must be monitored with video cameras or physical access control mechanisms (or both), and that data must be stored for at least three months (about 90 days), unless otherwise restricted by law. (In PCI DSS v3.2.1 this was Requirement 9.1.1.)
• Customer Contracts and Government Work: Colocation contracts and some government or healthcare customers specify 90 to 180 days. HIPAA and FedRAMP do not themselves set a video retention period; they require appropriate physical access monitoring.

---

Engineering Calculations: Video Bandwidth and Storage Dimensioning

The Video Storage Equation

Calculating total raw video storage capacity is governed by the continuous bit-rate formula:

$\text{Total Storage (Bytes)} = \frac{\text{Bitrate (bits/second)} \times \text{Time (seconds)}}{8\text{ bits/Byte}}$

$\text{Total Storage (Terabytes)} = \frac{\text{Bitrate (Mbps)} \times 3,600\text{ s/h} \times 24\text{ h/day} \times \text{Retention (days)}}{8 \times 10^6\text{ MB/TB}}$

$\text{Total Storage (TB)} = \text{Bitrate (Mbps)} \times 0.0108 \times \text{Retention (days)}$

(Note: $0.0108 = 86,400\text{ seconds/day} / (8 \times 10^6\text{ Mbits/TB})$ under standard decimal Terabyte formatting).

Practical Design Scenario: Enterprise Colocation Facility Sizing

An engineer is tasked with dimensioning the centralized SAN storage array for an enterprise colocation facility with the following design parameters:

• Camera Inventory:
  • $64$ interior cameras: $1080\text{p}$ ($1920 \times 1080$), $15\text{ fps}$, H.265 compression, continuous bitrate = $2.0\text{ Mbps}$ each.
  • $16$ exterior perimeter & gate cameras: $4\text{K}$ UHD ($3840 \times 2160$), $20\text{ fps}$, H.265 compression, continuous bitrate = $6.0\text{ Mbps}$ each.
• Retention Requirement: PCI DSS (at least three months) and customer contracts, set as continuous retention for $90\text{ days}$.
• Array Architecture: Hardware RAID 6 array ($N+2$ parity) with a requirement for $15\%$ filesystem/formatting overhead and one global hot spare drive per 16-drive shelf.

Step 1: Calculate Total Ingest Bandwidth

$\text{Bandwidth}_{interior} = 64 \times 2.0\text{ Mbps} = 128\text{ Mbps}$ $\text{Bandwidth}_{exterior} = 16 \times 6.0\text{ Mbps} = 96\text{ Mbps}$ $\text{Total Ingest Bandwidth} = 128\text{ Mbps} + 96\text{ Mbps} = 224\text{ Mbps} = 28\text{ MB/s}$

Step 2: Calculate Usable Net Storage for 90 Days

$\text{Storage (TB)} = \text{Total Bitrate (Mbps)} \times 0.0108 \times 90\text{ days}$ $\text{Storage (TB)} = 224 \times 0.0108 \times 90 = 217.728\text{ TB usable}$

Step 3: Account for Filesystem Overhead and RAID Parity

To guarantee $217.73\text{ TB}$ of usable storage across a multi-month period without filesystem saturation:

1. Filesystem Overhead (+15%): $\text{Required Usable Space} = 217.728\text{ TB} \times 1.15 = 250.39\text{ TB}$
2. Drive Selection & RAID 6 Parity: Utilizing enterprise $18\text{ TB}$ SAS hard disk drives ($18\text{ TB}$ nominal $\approx 16.37\text{ TiB}$ usable). In a RAID 6 configuration ($N+2$ drives per array group), an array of sixteen $18\text{ TB}$ drives yields: $\text{Usable Drives} = 16 - 2\text{ (parity)} = 14\text{ data drives}$ $\text{Array Usable Capacity} = 14 \times 18\text{ TB} = 252\text{ TB}$
3. The 16-drive RAID 6 group (14 data + 2 parity) plus one global hot spare needs 17 drive bays. Its 252 TB just covers the 250.39 TB requirement (about 1.6 TB margin), so a prudent design adds another drive group or larger drives for camera growth.

---

Common Exam Traps & DCDC Pitfalls

• Conflating Recognition with Identification: In IEC 62676-4, Recognition requires $\ge 125\text{ px/m}$ (verifying if a person matches a known record), whereas Identification requires $\ge 250\text{ px/m}$ (establishing positive forensic proof beyond a reasonable doubt). Designing an access control mantrap to Recognition level falls short of the Identification level normally specified for portals.
• Ignoring Overhead Pathways: Siting cameras directly on structural ceilings above dense overhead fiber trays or hot-aisle containment baffles can block much of the field of view. Cameras must be specified with pendant or unistrut drops bringing the lens below all utility pathways.
• Neglecting RAID Parity and Filesystem Formatting in Storage Sizing: Sizing video storage strictly by multiplying raw bitrate times days results in severe storage deficits. System designers must include RAID parity loss (e.g., 2 parity drives in RAID 6), filesystem overhead ($10\%$ to $15\%$), and hot-spare reserves.
• Unicast Overload: Streaming 100+ high-definition IP cameras to multiple monitoring stations using unicast transmission saturates switch backplanes. Core surveillance networks must be engineered for IP Multicast with IGMP snooping.
• Digital WDR vs. True Optical WDR: Relying on software-based Digital WDR (D-WDR) for sunlit glass vestibules yields noisy, washed-out images that fail facial capture. Specify Multi-Exposure True WDR (commonly about $120\text{ dB}$).