Choosing crisp 4 K cameras is exciting, but they are only half the story. Every frame those cameras capture must travel across your building’s data network, squeeze through a switch port, stay powered 24 × 7 and land safely on a recorder. Ignore any link in that chain and even the best camera turns into a frozen thumbnail.

Fortunately, building a CCTV-ready network is more “steady plumbing” than dark art. This guide breaks the job into four areas (structured cabling, PoE power, switching capacity and logical design), using everyday language and real figures from ACCL projects. By the end you will know what to check, what to upgrade and where you can safely re-use what you already own.

Why Network Planning Matters More Than Ever

Old analogue CCTV lived on its own coax island; power came from a wall wart, and pictures never touched the LAN. Modern IP cameras deliver 4 K video, AI analytics and cloud dashboards. All of that is welcome, but it leans heavily on your Ethernet plant. If you underestimate bandwidth or power draw, the first sign of trouble may be jerky footage during a break-in. Getting the groundwork right avoids that cliff-edge and gives room to grow.

Structured Cabling: The Physical Highway

Cable Classes and Distances

Cat 5e still supports 1 Gb/s, but its tighter twist and thinner conductor struggle with PoE on long runs.
Cat 6 is fine for most indoor drops up to 55 m.
Cat 6A (our current default) handles 10 Gb/s and high-power PoE across the full 90 m permanent link, ideal for future-proofing.
Fibre becomes cost-effective once copper would need more than two switches or where lightning or EMI risk exists (external poles, heavy machinery halls).

A quick survey with a Fluke DSX or similar will confirm whether existing copper passes Class EA tests. If it does, keep it and spend the budget elsewhere; if not, new pulls often pay back through reduced troubleshooting later.

Internal link: See our Office Cabling service for cabling grades and certification details.

Patch-Panel Labelling

Clear labelling sounds dull; it saves lives at 2 a.m. when an engineer needs to power-cycle “Camera-B03” and not the VoIP gateway. Add CCTV labels during installation, not “later”. Later never comes.

Power over Ethernet (PoE): Fuel for the Cameras

Understanding PoE Types

PoE Standard	Power at Device	Typical Use
IEEE 802.3af (PoE)	12 to 15 W	Small domes, indoor fisheyes
IEEE 802.3at (PoE +)	25 to 30 W	4 K bullets with IR, basic PTZ
IEEE 802.3bt (PoE ++)	60 to 90 W	Full-size PTZ, heaters, multi-sensor units

Most business cameras sit comfortably under 15 W; allocate 20 W per port to stay safe. A 24-port PoE+ switch with a 370 W budget supports roughly eighteen 20 W loads. Allow headroom for night-time IR peaks.

Quick tip: Check total and per-port budgets: two switches may claim the same wattage but differ wildly once all ports run at PoE ++.

Mid-Span Injectors vs New Switches

Injectors add power to individual links when switch upgrades are not yet budget-friendly. They work, but multiply wall-warts and make fault-finding harder. When more than eight injectors crop up in one rack, replacing the switch is usually cheaper and neater.

Switching Capacity: Moving the Megabits

Bandwidth Maths: The Friendly Version

A single 4 MP camera at 15 fps, H.265 compression, streams roughly 4 Mb/s. Ten such cameras peak at 40 Mb/s: comfortable on any 1 Gb uplink. Trouble starts when dozens of UHD channels share the same path as Wi-Fi, Teams calls and backup jobs.

Plan for peaks: shift changes, sports events on the office TV, anything pushing more traffic. If CCTV alone exceeds 60 % of a gigabit uplink, step up to 10 Gb/s on the core or ring in an extra aggregation switch.

For detailed number-crunching, our 4 K Storage and Bandwidth Guide includes a hands-on formula.

Uplink and Stack Design

Star-topology works for small offices: each access-layer switch trunks to the core. Larger estates gain resilience by stacking access switches (one virtual chassis) then dual-homing to a pair of core switches. If one link fails, cameras stay online.

Switch vendors sell licencing tiers; make sure multicast and QoS features are enabled in your SKU or you may pay later to unlock them.

Logical Network Design: Keeping Traffic Clean and Secure

Dedicated CCTV VLAN

Segregating video traffic prevents camera chatter eating office bandwidth and adds a firewall point. The CCTV VLAN needs to talk to:

The recorder or VMS server
Time servers (NTP)
VPN gateway if remote viewing is required

Block everything else. If cameras integrate with access control or alarms, permit only those specific IPs and ports.

IP Addressing and Naming

Static IPs beat DHCP for cameras: you always know where to find “Main-Lobby-Cam”. Reserve a tidy block (e.g., 10.10.50.0/24) and document in a spreadsheet or IPAM tool.

Quality of Service (QoS)

Most networks cope without fancy QoS; just put CCTV on its own VLAN. If WAN back-haul is tight, set video to a lower priority than VoIP but higher than guest Wi-Fi. Simple, readable rules beat default factory settings you never verify.

Future-Proofing: What About Wi-Fi 6 and IoT Cameras?

Wi-Fi cameras exist but rarely suit business-grade security: power sockets, interference and WPA3 management overheads introduce more risk than they solve indoors. Outdoors, point-to-point wireless bridges excel for remote gates or listed facades; treat them like wired links and budget 20 Mb/s per 4 K stream.

When Wi-Fi 6 APs share switches with CCTV, watch PoE headroom. A single tri-band AP can draw 25 W; four APs may tip an already busy 370 W switch into power-policing mode.

Our piece on Wired vs Wireless CCTV explores the trade-offs in more detail.

Testing Before You Go Live

Link Fluke Test: prove copper channels pass Cat 6 or Cat 6A spec.
PoE Load Test: power every camera plus 10 % extra dummy loads and watch the switch GUI for brown-outs.
Bandwidth Soak: record all cameras for an hour at peak settings; packet-capture the uplink to confirm headroom.
Fail-Safe Check: pull one uplink and one power feed. Does recording continue?

Running these checks before handover catches most of the surprises that would otherwise show up later as a frozen image or a failed recording.

Budgeting Without Tears

Re-use certified Cat 6 runs where tests pass; upgrade only the worst offenders.
Consolidate switch refreshes with Wi-Fi or VoIP projects; buying PoE in bulk saves pounds.
Lease core switches if cashflow is tight; opex beats capex shock, and you stay on supported firmware.

For a macro-view of total costs, revisit our CCTV Installation Cost Guide.

Next Steps: Turning Theory into Action

Audit your cabling: pull five random links, Fluke them; multiply findings by total link count.
List planned camera wattage: add 20 % margin, compare to switch spec.
Sketch VLANs on one sheet: if the diagram looks messy, so will troubleshooting. Simplify.
Book a bandwidth soak test: better an hour of packet capture now than lost frames later.

If any step raises more questions than answers, call ACCL on 0333 900 0101 or send a quick note via our contact page. An ACCL network engineer, never a commission-hunting salesperson, will walk your site, run the numbers and leave you with a clear, vendor-neutral roadmap.

Written by

Wayne Connors

Founder & Managing Director, ACCL

Wayne founded ACCL in 1997 and has led more than 28 years of project delivery, helping organisations design, install and modernise the network infrastructure behind reliable connectivity, office moves and refurbishments. His experience spans copper cabling, fibre backbones, data centre infrastructure, Wi-Fi, CCTV and access control. About ACCL