Planning a Small Business CCTV System: Cameras, Storage, and PoE

Physical security and asset protection represent essential operational responsibilities for commercial enterprises [3]. Whether protecting retail inventory, auditing warehouse logistics, or securing data center facilities, an Internet Protocol (IP) Closed-Circuit Television (CCTV) surveillance system provides real-time situational awareness and verifiable forensic records [1, 3].

However, naive CCTV installations frequently suffer from poor low-light imaging, inadequate storage capacity, unmanaged network broadcast storms, and power budget failures on network switches [1, 2]. In this technical engineering guide, we examine camera selection parameters, calculate video storage capacity using H.265 compression, analyze Power over Ethernet (PoE) budgeting, and review network segmentation best practices [1, 2, 3].

1. Camera Selection: Optics, Resolution, and Sensor Physics

Designing an effective surveillance system begins with selecting the correct optical characteristics for each monitoring zone [3]:

Focal Length and Field of View (FOV)

Camera lenses govern the Field of View and optical magnification:

• Wide Angle (2.8 mm lens): Delivers a wide horizontal field of view (~105°). Ideal for general overview monitoring of small offices, retail sales floors, and reception lobbies.
• Medium Standard (4.0 mm lens): Delivers ~85° FOV with higher pixel density at distance. Best for hallways, warehouse aisles, and parking bays.
• Narrow Telephoto / Varifocal (6.0 mm – 12.0 mm): Delivers a narrow FOV (~30° – 50°). Necessary for identifying vehicle license plates at entry gates or capturing facial details at cash registers.

The Megapixel Myth and Low-Light Sensitivity

Higher resolution does not always equate to better security footage:

• A 4K (8 Megapixel) camera contains smaller physical photodiodes on its silicon sensor compared to a 1080p (2 Megapixel) camera of identical sensor size (e.g., 1/2.8-inch sensor).
• In low-light or nighttime conditions, smaller pixels capture fewer photons, generating substantial digital sensor noise and motion blur unless paired with powerful infrared (IR) or white-light illumination.
• For most commercial indoor surveillance, high-sensitivity 4 Megapixel (1440p) cameras offer the optimal engineering balance of sharp detail, low-light SNR, and manageable network bandwidth [1].

2. Storage Calculation: H.264 vs H.265 Compression

Surveillance video generates continuous, high-volume data streams that must be stored on dedicated Network Video Recorder (NVR) hard drives [1]:

The Advantage of H.265 (HEVC - ITU-T H.265)

The ITU-T H.265 video coding standard utilizes advanced motion compensation and variable block sizes (up to 64x64 pixel Coding Tree Units) [1]:

• Compared to legacy H.264, H.265 reduces required video bitrate and storage consumption by 40% to 50% while preserving identical image resolution and frame fidelity [1].
• Proprietary extensions (such as Smart H.265+) dynamically lower bitrates during static scenes, increasing bitrate only when motion occurs [1].

Calculating Required NVR Storage Capacity

To calculate total hard drive capacity for an NVR: $$\text{Storage (Bytes)} = \frac{\text{Bitrate (bps)} \times 3600\text{ sec/hr} \times \text{Hours/Day} \times \text{Days} \times \text{Cameras}}{8\text{ bits/byte}}$$

Engineering Example:
- Cameras: 8 IP Cameras (4 MP, 15 FPS, H.265 encoding)
- Average Bitrate: 3,000 kbps (3 Mbps) per camera
- Retention Requirement: 30 Days continuous recording (24/7)

Daily Storage per Camera:
(3,000,000 bps * 86,400 sec) / (8 * 10^9) = 32.4 GB / day

Total Storage for 8 Cameras for 30 Days:
32.4 GB * 8 cameras * 30 days = 7,776 GB (~7.8 Terabytes)
Adding a 20% engineering safety margin: 10 Terabytes of dedicated surveillance storage.

Enterprise NVRs must utilize dedicated surveillance-grade hard drives (such as Western Digital Purple or Seagate SkyHawk), which feature specialized firmware tuned for 24/7 continuous sequential write streams rather than random workstation read operations [1].

3. Power over Ethernet (PoE) Infrastructure Planning

IP cameras receive operating power and data transmission over a single standard Cat6 Ethernet cable via Power over Ethernet (IEEE 802.3) [2]:

Calculating the Switch PoE Power Budget

A common installation failure occurs when a 16-port switch has a total internal power budget of only 120 Watts:

• If 16 cameras each draw 12 Watts with night-vision IR illuminated ($16 \times 12\text{W} = 192\text{W}$), the switch will exhaust its power supply, causing cameras to randomly reboot or drop offline at dusk when infrared LEDs activate [2].
• Always verify the total PoE power budget of the switch against the sum of all camera maximum wattage ratings plus a 20% overhead margin [2].

4. Surveillance Network Architecture & Isolation

IP cameras are specialized Linux-based embedded computers that represent notorious cybersecurity vulnerabilities if connected directly to the corporate LAN [3]:

+-------------------------------------------------------------+
|                      Core Switch / Router                   |
+-------------------------------------------------------------+
         |                                           |
         v (VLAN 10: Staff Subnet)                   v (VLAN 30: Quarantined CCTV)
+-----------------------+                   +-----------------------+
| Corporate Computers   |                   | PoE Surveillance      |
| & Accounting Servers  |                   | Switch & IP Cameras   |
+-----------------------+                   +-----------------------+
                                                       |
                                            +-----------------------+
                                            | Network Video         |
                                            | Recorder (NVR)        |
                                            +-----------------------+

• Quarantine on an Isolated VLAN (VLAN 30): Surveillance cameras must be segregated on a dedicated, non-routable VLAN with zero direct communication to corporate workstations or database servers [3].
• Block Outbound Internet Egress: Cameras require no direct connection to the public internet. Block all outbound internet access at the firewall for the camera subnet. Remote viewing must be mediated securely through the NVR or a secure corporate VPN tunnel [3].

For customized commercial CCTV layout design, NVR storage sizing, and PoE infrastructure deployment, visit our IT Infrastructure & System Integration page.

Key Takeaways

• Optical focal length determines Field of View; 2.8 mm provides wide coverage, while 4–6 mm delivers facial detail.
• H.265 compression reduces video bandwidth and storage requirements by up to 50% compared to legacy H.264.
• Calculate total switch PoE power budgets with a 20% margin to prevent camera brownouts when nighttime IR activates.
• IP cameras must be quarantined on an isolated VLAN with outbound internet access strictly blocked at the firewall.

Need help with this? Contact us.

Sources

[1] International Telecommunication Union (ITU), "Recommendation ITU-T H.265: High efficiency video coding", 2019. URL: https://www.itu.int/rec/T-REC-H.265 (International standard defining video compression algorithms, macroblocks, and bit-rate reduction).

[2] IEEE Standards Association, "IEEE Standard 802.3bt: Physical Layer and Management Parameters for Power over Ethernet over 4 Pairs", 2018. URL: https://standards.ieee.org/ieee/802.3bt/6829/ (Standard governing PoE, PoE+, and PoE++ electrical power delivery over structured Ethernet cabling).

[3] National Institute of Standards and Technology (NIST), "NIST SP 800-53 Rev. 5: Security and Privacy Controls for Information Systems and Organizations", 2020. URL: https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final (Federal standard specifying physical access monitoring controls, surveillance architecture, and data isolation).

Last reviewed: October 2026