Security Systems โ†’ CCTV System โ†’ System Design
๐Ÿ› ๏ธ CCTV Knowledge Hub

CCTV System Design for Buildings โ€” A Step-by-Step Guide with Calculations

From requirement gathering and site survey through camera placement, bandwidth calculations, switch sizing, server specification, storage planning, and commissioning โ€” a complete design methodology that enables any facility manager to plan a professional IP CCTV system.

Designing a CCTV system is both an engineering discipline and a practical art. A well-designed system delivers precisely the right coverage, image quality, and retention โ€” without over-engineering the network, over-specifying storage, or overspending on unnecessary equipment. This guide walks through the complete design process with worked calculations, so that a facility manager, consultant, or procurement officer can independently verify vendor proposals or design a system from scratch.

1. The CCTV System Design Process

Professional CCTV system design follows a structured, sequential process. Skipping any stage โ€” particularly the requirement gathering and site survey โ€” invariably leads to a system that fails to meet expectations.

Phase 1 โ€” Understand Requirements

Define objectives, identify stakeholders, establish budget, determine regulatory requirements, and agree on retention period and integration needs.

Phase 2 โ€” Site Survey

Physical inspection of the building: entry/exit points, critical zones, lighting conditions, cable route feasibility, existing infrastructure, and environmental factors.

Phase 3 โ€” Camera Placement

Determine camera locations, types, lens selections, mounting heights, and fields of view. Create the camera schedule document.

Phase 4 โ€” Network Design

Calculate bandwidth, size PoE switches, design VLANs, plan cable routes, and specify core switch and uplink requirements.

Phase 5 โ€” Server & Storage

Calculate storage capacity, specify recording servers, determine RAID configuration, and plan for failover and redundancy.

Phase 6 โ€” Documentation & Procurement

Prepare system drawings, BOQ, tender specifications, evaluate proposals, and manage installation and commissioning.

2. Understanding Requirements

Before selecting any equipment, the designer must answer these critical questions โ€” ideally in consultation with the building owner, facility manager, and security team:

Purpose of the CCTV System

  • Detection: Detecting that someone or something is present in the scene. Requires lower resolution; wider fields of view are acceptable.
  • Recognition: Determining that the person seen is the same person seen previously (but not necessarily identifying who they are). Requires moderate resolution.
  • Identification: Positively identifying a specific individual โ€” typically requiring a face capture that fills at least 120 pixels per metre of height in the image (as per the international standard EN 62676-4). Requires higher resolution, appropriate lens selection, and correct camera positioning.

Different locations within the same building may have different objectives. An entrance face-capture camera needs identification-level quality. A corridor camera may need only recognition. A perimeter camera may need only detection.

Key Questions to Answer

  • What is the primary purpose โ€” deterrence, evidence, real-time monitoring, or all three?
  • Who will operate the system โ€” dedicated 24-hour security, part-time operators, or remote monitoring?
  • What is the retention period โ€” 30 days (commercial), 60 days (PSU), 90+ days (banks)?
  • Is integration with other systems required โ€” access control, fire alarm, BMS, visitor management?
  • What are the regulatory requirements โ€” RBI guidelines (banks), BIS/STQC compliance, CVC procurement rules?
  • What is the realistic budget โ€” and does it include 5-year AMC and storage expansion costs?

3. Site Survey

The site survey is a physical inspection that converts the abstract requirements into concrete design inputs. It cannot be done remotely from floor plans alone โ€” the designer must physically walk every area of the building, at different times of day if possible, to understand lighting conditions and activity patterns.

Site Survey Checklist

CategoryWhat to Document
Entry/Exit PointsMain entrance, side doors, fire exits, loading dock, basement access, roof access, emergency exits. Note direction of foot traffic and lighting at each.
PerimeterCompound wall height and condition, fence line, vehicle gates, pedestrian gates, perimeter lighting. Note distances and line-of-sight obstructions (trees, signboards).
Interior Critical ZonesCash counters, server rooms, vaults, reception, executive areas, document storage, pharmacy (hospital). Note access control points already in place.
Common AreasCorridors, stairwells, lift lobbies, cafeteria, meeting rooms, parking levels. Note corridor widths and ceiling heights.
Lighting ConditionsEast-west building orientation (sun position), glass facades causing backlight, areas with mixed indoor/outdoor light, poorly lit zones, 24-hour lighting areas vs areas dark at night.
Cable Route FeasibilityExisting cable trays, conduit paths, risers between floors, distance from camera positions to nearest network cabinet. Note maximum cable run lengths.
Network InfrastructureLocation of existing network rooms/cabinets on each floor, available rack space, UPS capacity, cooling, power outlets. Can CCTV share existing cabinets?
Environmental FactorsTemperature extremes, humidity, coastal salt air, dust, vibration from machinery, vandalism risk, heritage building restrictions.
๐Ÿ’ก Best Practice โ€” Lighting Survey: Visit the building at night (or simulate night conditions) to assess low-light areas that will require cameras with starlight sensors or supplemental IR illumination. Many CCTV systems fail at night precisely because the site survey was conducted only during daytime working hours.

4. Camera Placement Design

Camera placement is the most critical design decision. Every camera must have a clearly defined purpose, a calculated field of view, and an achievable cable route back to the nearest network switch.

Pixel Density โ€” The Key Metric

The international standard EN 62676-4 defines surveillance quality in terms of pixels per metre (PPM) โ€” the number of image pixels that represent one metre of real-world height at the target distance. This is the most objective way to determine whether a camera will deliver the required level of detail:

PurposeRequired PPMWhat It Means
Monitor / Detect25 PPMDetermine whether a person is present. Cannot recognise or identify.
Observe62 PPMSee some characteristic details (clothing type, general build).
Recognise125 PPMDetermine with high confidence that this is the same person seen before.
Identify250 PPMPositively identify an individual beyond reasonable doubt. Face fills a significant portion of the image.

How to Calculate Pixel Density

PPM = Camera Horizontal Resolution รท Horizontal Field of View (metres)

Example: A 4MP camera (2560 ร— 1440) with a 2.8mm lens covers approximately 6 metres width at 4 metres distance.
PPM = 2560 รท 6 = 427 PPM โ†’ Excellent for identification at this distance.

The same 4MP camera with a 2.8mm lens at 15 metres distance covers approximately 22 metres width.
PPM = 2560 รท 22 = 116 PPM โ†’ Adequate for recognition but NOT identification.
๐Ÿ’ก Practical Rule of Thumb: For identification-level face capture (entrance cameras, cash counters), the person's face should fill at least 10% of the image width. For a 4MP camera, this means the scene width at the target distance should be no more than 3โ€“4 metres. Use a narrower lens or higher resolution for wider areas requiring identification.

Camera Mounting Heights

  • Face capture at entrances: 2.2โ€“2.5 metres height, tilted slightly downward, with a narrow field of view focused on the doorway. The goal is to capture every face at roughly the same angle.
  • Indoor general surveillance: 2.8โ€“3.5 metres (standard ceiling height). Higher mounting gives a wider overview but reduces facial detail.
  • Corridors: 2.5โ€“3.0 metres. Consider corridor mode (rotating the camera 90ยฐ for a 9:16 aspect ratio) to maximise coverage of long, narrow spaces.
  • Outdoor perimeter: 3.5โ€“5.0 metres to prevent tampering and provide a commanding view.
  • PTZ cameras: 5โ€“8 metres for maximum pan range and stability.

5. Bandwidth Calculation

Every IP camera continuously transmits video data over the network. Accurate bandwidth calculation is essential for sizing switches, uplinks, and recording server network interfaces.

Factors That Determine Bandwidth

  • Resolution: Higher resolution = more pixels = more data per frame
  • Frame Rate (FPS): More frames per second = more data. 15 fps is standard for surveillance; 25โ€“30 fps for high-security areas
  • Compression Codec: H.265 reduces bandwidth by ~30โ€“50% vs H.264; Smart Codec variants reduce further
  • Scene Complexity: A busy parking lot generates more data than a static corridor because the compression algorithm must encode more changes between frames

Typical Bitrate Reference Table

ResolutionH.264 @ 15 fpsH.265 @ 15 fpsH.265+ / Smart @ 15 fps
2MP (1080p)3โ€“4 Mbps1.5โ€“2.5 Mbps0.5โ€“1.5 Mbps
4MP (2K)5โ€“8 Mbps3โ€“5 Mbps1โ€“3 Mbps
5MP6โ€“10 Mbps4โ€“6 Mbps1.5โ€“3.5 Mbps
4K / 8MP12โ€“20 Mbps8โ€“12 Mbps3โ€“6 Mbps
โš ๏ธ Important: Always use the higher end of the bitrate range for design calculations. Real-world bitrates exceed datasheet values in complex scenes (heavy traffic, mixed lighting, rain). A safety margin of 20โ€“30% on top of calculated bandwidth prevents network congestion during peak activity.

๐Ÿงฎ Bandwidth Calculator

Bandwidth Results

Bitrate per cameraโ€”
Total bandwidth (all cameras)โ€”
+ 25% safety marginโ€”
Design Bandwidth Requiredโ€”

6. Network Switch Sizing

IP CCTV systems require two tiers of switches: edge switches (PoE switches on each floor that connect cameras) and core switches (that aggregate all edge switch uplinks and connect to servers).

Edge Switch (PoE) Sizing

For each floor or zone, calculate:

  1. Port count: Number of cameras on that floor + 1โ€“2 spare ports for future expansion
  2. PoE budget: Sum of power requirements of all connected cameras (typically 12โ€“15W per fixed camera, 30โ€“60W per PTZ)
  3. Uplink bandwidth: Sum of all camera bitrates on that switch must not exceed the uplink speed
PoE Budget Required = (No. of fixed cameras ร— 15W) + (No. of PTZ cameras ร— 60W)

Example: A floor with 20 fixed cameras and 1 PTZ camera:
PoE Budget = (20 ร— 15W) + (1 ร— 60W) = 300 + 60 = 360W
Select a switch with PoE budget โ‰ฅ 360W ร— 1.2 (20% margin) = 432W minimum

Edge Switch Selection Guide

Cameras per SwitchRecommended SwitchPoE BudgetUplink
1โ€“8 cameras8-port PoE+ managed switch120โ€“150W1 ร— 1GbE (SFP or RJ45)
9โ€“16 cameras16-port PoE+ managed switch240โ€“380W2 ร— 1GbE (SFP)
17โ€“24 cameras24-port PoE+ managed switch370โ€“500W2 ร— 10GbE (SFP+) or 4 ร— 1GbE LAG
25โ€“48 cameras48-port PoE+ managed switch500โ€“740W2 ร— 10GbE (SFP+)
๐Ÿ’ก Key Principles: Always use managed switches (not unmanaged) โ€” you need VLAN support, QoS, port monitoring, and IGMP snooping. Specify Layer 2+ or Layer 3 switches. Use SFP fibre uplinks for runs between floors or buildings โ€” not copper โ€” as fibre is immune to electromagnetic interference and supports distances up to 10 km.

Core Switch Sizing

The core switch aggregates all edge switch uplinks and connects to recording servers, VMS servers, and operator workstations. Key requirements:

  • Port count: Number of edge switch uplinks + server ports + management ports + spare capacity
  • Switching capacity: Must be non-blocking โ€” the total switching fabric must handle all ports at full line rate simultaneously
  • Redundancy: For mission-critical deployments (banks, PSU HQ), use redundant core switches in a stacked or failover configuration
  • 10GbE uplinks: Connections from core switch to recording servers should be 10GbE (SFP+) to handle the aggregate bandwidth of all cameras being written to storage simultaneously

7. Data Flow in an IP CCTV Network

The following diagram illustrates how video data flows from cameras through the network infrastructure to the recording servers and operator workstations. The animated data packets show the continuous flow of video streams through each network layer.

IP CCTV Network Data Flow FLOOR 1 CAMERAS CAM 1 CAM 2 ... CAM 24 FLOOR 2 CAMERAS CAM 25 CAM 26 ... CAM 48 PERIMETER & GATE PTZ 1 ANPR ... CAM 64 Cat6 + PoE LAYER 2 โ€” PoE EDGE SWITCHES 24-Port PoE+ SW 24-Port PoE+ SW 16-Port PoE+ SW Fibre SFP+ 10GbE Uplinks LAYER 3 โ€” CORE SWITCH (Redundant Pair) L3 Core Switch โ€” 10GbE DEDICATED CCTV VLAN Isolated from corporate LAN 10GbE to Servers RECORDING, STORAGE & MANAGEMENT Recording Server(s) Xeon / 32GB / RAID / 10GbE NIC SAN / NAS Storage RAID 5/6 ยท Surveillance-Grade HDDs VMS Server + Workstations Management ยท Live View ยท Playback Control Room Monitors / Video Wall ๐Ÿ“ฑ Remote / Mobile Access LEGEND Cat6 / PoE Fibre 10GbE Server link

8. Storage Calculation

Storage is the most expensive recurring cost in a CCTV system and the component most frequently underestimated. A rigorous calculation prevents both under-provisioning (losing footage before the retention period expires) and over-provisioning (wasting budget on unnecessary hard drives).

Storage Calculation Formula

Daily Storage per Camera (GB) = Bitrate (Mbps) ร— 3,600 ร— 24 รท 8 รท 1,000
Simplified: Daily Storage (GB) = Bitrate (Mbps) ร— 10.8

Total Raw Storage (TB) = Daily Storage per Camera ร— Number of Cameras ร— Retention Days รท 1,000

Usable Storage Required (TB) = Raw Storage รท RAID Efficiency Factor
RAID 5 efficiency โ‰ˆ 0.75 (25% lost to parity) ยท RAID 6 โ‰ˆ 0.67 ยท RAID 10 โ‰ˆ 0.50

Worked Example

64 cameras, 4MP resolution, H.265 at 15 fps (average 4 Mbps per camera), 60-day retention, RAID 6:

  • Daily per camera: 4 Mbps ร— 10.8 = 43.2 GB/day
  • Total daily: 43.2 ร— 64 = 2,765 GB/day (2.77 TB/day)
  • 60-day raw: 2.77 ร— 60 = 166.1 TB raw storage
  • RAID 6 usable: 166.1 รท 0.67 = 247.9 TB physical disks required
  • Add 10% file system overhead: 247.9 ร— 1.1 = ~273 TB total disk capacity

๐Ÿงฎ Storage Calculator

Storage Results

Daily storage per cameraโ€”
Total daily storage (all cameras)โ€”
Raw storage for retention periodโ€”
After RAID + 10% overheadโ€”
Total Disk Capacity Requiredโ€”
Equivalent in HDDsโ€”

9. Recording Server Sizing

The recording server receives video streams from cameras (via the network), processes them, and writes them to storage. Correct server sizing ensures smooth recording without dropped frames or performance degradation.

Server Sizing Guidelines

System SizeCPURAMNetworkServer Type
Up to 32 cameras
4MP H.265
Intel Core i5 (12th Gen+)
or Xeon E-2300
16 GB DDR41 ร— 1GbE dedicatedDesktop workstation or
embedded NVR
32โ€“64 cameras
4MP H.265
Intel Xeon E-2300 series
or Core i7 (12th Gen+)
32 GB DDR41 ร— 10GbE (SFP+)1U/2U rackmount server
64โ€“128 cameras
Mixed 4MP/4K
Intel Xeon Silver 4300
(8โ€“16 cores)
32โ€“64 GB DDR42 ร— 10GbE (SFP+)2U rackmount server
+ external SAN storage
128โ€“256 cameras
Enterprise
Dual Xeon Silver/Gold
or split across 2 servers
64โ€“128 GB DDR42 ร— 10GbE per serverMultiple 2U servers
+ SAN/NAS storage
๐Ÿ’ก Key Points for Server Specification:
  • Recording is mainly an I/O task, not a CPU task. The server receives compressed streams and writes them to disk โ€” it does not decode the video. CPU demand is moderate. High disk write throughput and network throughput are more important than raw CPU speed.
  • Viewing/playback is CPU-intensive. If the same server serves live viewing clients, it must decode multiple streams simultaneously. This is where GPU acceleration (Intel Quick Sync or dedicated GPU) helps significantly.
  • Use surveillance-grade hard drives (WD Purple, Seagate SkyHawk) designed for continuous 24/7 write operations. Standard desktop drives fail prematurely under CCTV workloads.
  • Two 10GbE NICs for systems above 64 cameras โ€” one for camera traffic, one for client viewing and management.
  • UPS is mandatory. An unclean shutdown during recording can corrupt the video database. Size UPS for at least 15 minutes of runtime to allow graceful shutdown.

Failover Server

For mission-critical installations (banks, PSU headquarters, data centres), a failover recording server provides automatic takeover when the primary server fails. The failover server monitors the primary server's heartbeat and, upon detecting a failure, immediately begins recording from the same cameras. When the primary is restored, recordings are automatically merged. Major VMS platforms (Milestone, Genetec, NUUO) support this natively.

10. Complete Design Example โ€” 8-Storey Office Building

To bring all the calculations together, here is a complete worked example for a typical 8-storey commercial office building with a basement car park, ground floor reception, and perimeter security.

Requirement Summary

ParameterValue
Building type8-storey PSU/corporate office + basement parking
Total cameras96 (12 per floor avg ร— 8 floors + 16 basement + 16 perimeter/gate)
Camera mix80 ร— 4MP fixed (H.265), 8 ร— 4K entrance face-capture, 4 ร— PTZ, 4 ร— ANPR
Frame rate15 fps (all cameras)
Retention60 days continuous
Monitoring24/7 control room + remote mobile access

Bandwidth Calculation

  • 80 ร— 4MP H.265 @ 4 Mbps = 320 Mbps
  • 8 ร— 4K H.265 @ 10 Mbps = 80 Mbps
  • 4 ร— PTZ 4MP H.265 @ 6 Mbps = 24 Mbps
  • 4 ร— ANPR 2MP H.265 @ 3 Mbps = 12 Mbps
  • Total: 436 Mbps + 25% margin = 545 Mbps design bandwidth

Switch Sizing

  • Edge switches: 6 ร— 24-port PoE+ managed switches (one per two floors + one for basement + one for perimeter) โ€” each with 2 ร— 10GbE SFP+ uplinks
  • Core switch: 1 ร— 24-port Layer 3 managed switch with 10GbE SFP+ ports โ€” provides VLAN segmentation, QoS, and connects to all edge switches and servers
  • Total PoE budget: (88 fixed ร— 15W) + (4 PTZ ร— 60W) + (4 ANPR ร— 15W) = 1,320 + 240 + 60 = 1,620W across all edge switches

Storage Calculation

  • Total daily: (80 ร— 4 + 8 ร— 10 + 4 ร— 6 + 4 ร— 3) ร— 10.8 = (320 + 80 + 24 + 12) ร— 10.8 = 436 ร— 10.8 = 4,709 GB/day (4.71 TB/day)
  • 60-day raw: 4.71 ร— 60 = 282.5 TB
  • RAID 6 + 10% overhead: 282.5 รท 0.67 ร— 1.1 = ~464 TB physical capacity
  • Equivalent: approximately 29 ร— 16TB surveillance-grade HDDs (in RAID 6 across 2 storage shelves) or 24 ร— 20TB HDDs

Server Specification

  • 2 ร— Recording Servers (48 cameras each): Intel Xeon Silver 4310 (12-core), 32GB DDR4, 2 ร— 10GbE SFP+ NIC, 2U rackmount
  • 1 ร— Failover Server: Same specification as recording servers โ€” activates automatically if either primary fails
  • 1 ร— VMS Management Server: Intel Xeon E-2388G, 32GB DDR4, 1 ร— 10GbE โ€” handles VMS licensing, system health, user management
  • SAN Storage: 2 ร— 24-bay storage shelves with 16TB surveillance HDDs, RAID 6 configuration, iSCSI or Fibre Channel connectivity to recording servers
  • UPS: 6 kVA online UPS with 15-minute battery runtime for all servers and core switch

Estimated Bill of Quantities (BOQ) Summary

ItemQuantityPurpose
4MP Turret/Dome cameras (H.265, IR, PoE)80Indoor corridors, lobbies, offices, parking
4K Face-capture cameras (WDR, starlight)8Building entrances, main gate pedestrian
4MP PTZ cameras (30ร— zoom, PoE+)4Perimeter corners, large parking area
ANPR cameras4Vehicle entry/exit gates
24-port PoE+ managed switches6Edge / floor switches
Layer 3 core switch (10GbE)1Core aggregation
Recording servers (2U rackmount)2 + 1 failoverVideo recording
VMS management server1System management
SAN storage shelves (24-bay)2Video archive
16TB surveillance HDDs30RAID 6 storage
6 kVA Online UPS1Server/core switch power backup
Cat6A cable (305m boxes)Estimated 40Camera-to-switch cabling
Fibre patch cables (LC-LC)24Switch uplinks
Control room workstations2Live monitoring, playback
55" monitors4Video wall display

11. Documentation, Installation & Commissioning

Design Documentation Package

A complete CCTV design should include the following documents before procurement:

  • Camera Schedule: Tabulated list of every camera โ€” location name, camera type/model, resolution, lens, mounting type, PoE requirement, and zone/purpose.
  • Floor Layout Drawings: Architectural floor plans with camera positions marked, showing fields of view (coverage cones), cable routes, and switch/cabinet locations.
  • Network Single-Line Diagram: Complete network topology showing cameras, edge switches, core switch, servers, storage, and workstations with port assignments, VLAN configuration, and IP address allocation.
  • Storage Calculation Sheet: Detailed calculation showing bitrate assumptions, daily storage, retention period, RAID configuration, and total disk capacity required.
  • Bill of Quantities (BOQ): Complete list of all equipment, cabling, accessories, and installation materials with quantities.
  • Technical Specifications: Detailed specifications for each equipment category for inclusion in the tender document.

Commissioning Checklist

After installation, systematic commissioning ensures every component functions correctly:

  • Every camera image verified: correct coverage, focus, day and night quality
  • Every recording channel confirmed: continuous recording, correct retention
  • PoE delivery verified on every switch port
  • Network performance tested: no packet loss, acceptable latency
  • Analytics (if configured) validated under real conditions
  • Remote access tested from outside the building network
  • UPS tested: simulate power failure, verify graceful shutdown/switchover
  • Failover server tested: simulate primary failure, verify automatic takeover
  • Operator training delivered and documented
  • As-built drawings and documentation handed over

Need Help Designing Your CCTV System?

Whether you need a complete system design from scratch, an independent review of a vendor's proposal, or help with tender specifications and procurement governance โ€” BuildingInfra brings 34 years of experience managing security across 35 RBI buildings.

Request a Free Consultation
๐Ÿ“ž +91-9619111731  |  โœ‰๏ธ ashok8076@gmail.com  |  ๐Ÿ’ฌ WhatsApp
โ† Back to CCTV System โ€” Complete Guide
Index