I learned to respect cable the hard way, kneeling on a steel mezzanine in August heat while a dome camera blinked at me like it knew I had mis-crimped the BNC. Since then I’ve wired everything from small retail shops to sprawling warehouses, and the pattern is the same: most “camera problems” are cable problems dressed in different clothes. The path from coax to IP over Ethernet has opened up huge capability, yet it also raised the stakes on how we design, pull, and terminate. This is a field guide to doing it right, with practical notes from job sites where ceiling tiles fight back and conduit bends are never as generous as the drawing promised.
Where we came from: analog coax and its stubborn longevity
Analog CCTV over coax still exists, and not just in dusty basements. If a site has dozens of working analog cameras, a thoughtful retrofit may keep some coax runs in service using HD over coax standards like TVI, CVI, or AHD. They push 1080p and beyond over RG59 or RG6 and keep latency near zero. That can be attractive for casinos or manufacturing lines where a half second lag changes outcomes.
Coax thrives on simple point to point runs. Power usually arrives over separate 18/2 or 16/2 cable. On larger campuses you’ll often find siamese cable, RG59 with a bonded power pair. If the homerun is clean, the connectors are crimped properly, and the power supply is local, analog can be extremely stable. The downsides are obvious: no native scaling, limited analytics, and cabling that does not help you with anything IP. When a property wants to unify security camera cabling with networked security controls, intercom and entry systems, or IP-based surveillance setup across multiple buildings, coax becomes a cul-de-sac.
Still, coax can bridge a gap in phased upgrades. I’ve run hybrid sites that kept their parking lot cameras on existing RG6 runs with HD-TVI while moving all interior positions to IP. That year of in-between saved budget without compromising coverage.
The Ethernet era and why cable category choice matters
Pulling Cat6 for IP cameras feels almost routine until it isn’t. The camera drops every afternoon? The cable runs parallel to a 480V feeder for 120 feet. The PoE switch keeps rebooting ports? A 92 meter run was measured “as the crow flies” but the actual pull zigzagged through three closets and two ceiling paths. Category cable is a system, not just copper.
A few ground rules that have saved me countless tickets:
- Cat5e is adequate for 1 Gbps at 100 meters and supports most PoE loads for typical cameras. If the site expects basic 1080p streams with modest analytics, and the environment is clean, Cat5e is fine. Cat6 buys headroom. Better crosstalk performance and slightly larger conductor gauge reduce voltage drop under PoE. I default to Cat6 for new installs, especially where cameras draw 12 to 25 watts. For industrial or high EMI areas, shielded twisted pair with proper bonding can help, but shielding done poorly causes more problems than it solves. If you go shielded, bond once at the telecom end, follow manufacturer guidance, and mind continuity across couplers. Plenum rated cable (CMP) in air return spaces is not optional. AHJ inspectors are not sympathetic after the fact.
I rarely promise “future proof,” yet I do plan for bandwidth beyond the day one camera profile. 4K cameras with H.265 and smart codecs can still spike throughput under certain scenes. If you design the cable plant and switching for a comfortable margin, you won’t dread the day marketing asks for 30 days of higher frame rate storage from the lobby cameras.
Power matters: PoE is wonderful until it isn’t
Power over Ethernet simplified everything, then introduced new failure modes. A PoE camera is happiest when it gets stable voltage with a cushion. The three practical constraints are budget, power class, and distance.
Switch budget trips up many deployments. A 24 port switch with 370 W sounds generous, but once you add motorized varifocals at 12 to 14 W, a couple of PTZs at 25 to 30 W, and an outdoor heater at 15 W, the math tightens. I build a table per switch, listing each camera’s worst case draw, then reserve 15 to 20 percent margin. That margin absorbs cold starts and unplanned adds. If budget is tight, midspans or PoE injectors can rescue a few runs, but over time they complicate troubleshooting.
Beyond 100 meters, PoE gets tricky. You can insert PoE extenders, but each hop adds points of failure. I prefer placing a small PoE switch in a weatherproof or IDF enclosure fed by fiber, then fanning out short copper runs. It scales better, supports higher camera counts, and gives you a routed demarc to isolate broadcast storms.
For outdoor runs, I pair industrial midspans with surge protection on both data and power lines, especially in lightning prone regions. The $40 you save by skipping surge protection tends to reappear as a $400 lift rental and downtime during a thunderstorm week.
Connectors and terminations: the unglamorous truth
I can tell within a minute if a team owns quality tools. A good compression tool for BNCs, a PoE compatible cable verifier, and a punchdown that isn’t bent all signal fewer callbacks. For RJ45 terminations, pass-through connectors are forgiving on job sites, but use a ratcheting crimper that cuts cleanly and test for split pairs. If a camera negotiates at 100 Mbps instead of 1 Gbps on a short run, suspect a termination error before you blame the camera.
For coax, compression fittings are worth it. Crimped BNCs can work, yet they are more sensitive to technique. On legacy sites I sometimes replace only the connectors, not the entire run, then retest return loss. That modest refresh cures many “fuzzy” channels.
Keep a labeler in your pouch. Matching camera names to ports is not a favor to your future self, it’s free time you get back every time a switch port goes red.
Distance is ruthless: plan your topology around it
The 100 meter Ethernet limit has shaped more facility designs than most architects realize. In open warehouses, it tempts you to push runs farther than you planned because a ceiling path looks short on paper. Measure pathways, then add the real world: up and over, around obstructions, through firestops, down walls. That 70 meter point to point becomes 110 meters without blinking.
When a camera must be far, consider a fiber backbone to a closet within range, then copper the last 30 to 60 meters. Pre-terminated fiber jumpers save time, and modern SFPs are inexpensive. Ruggedized PoE switches in NEMA enclosures work well on perimeter poles. If you must go copper‑to‑copper long distance, EoC adapters over existing coax can be surprisingly reliable for parking garages or historic buildings where pulling new cable is painful. I’ve hit 300 to 500 meters over good RG6 with Ethernet over Coax kits, powering a single camera with PoE injected locally.
Environmental realities: temperature, vibration, moisture
Cameras live in places that cabling dislikes. Freezers, rooftops, car washes, loading docks. For cold rooms, select cameras and PoE budgets that account for heaters, then use low temperature rated jacket cable and grommet every penetration. For rooftops, UV rated cable and drip loops keep water from wicking into enclosures. I once traced intermittent faults to a conduit stub that filled during rain then wicked through poorly sealed knockouts into a midspan. Silicone and cord grips cost little, save weekends.
Vibration on metal buildings can loosen RJ45s over time. Latching keystone couplers in secure boxes with strain relief relieve tension. On conveyors or cranes, use flex rated cable and support it every meter or two. Where conduit runs near high voltage, maintain separation and cross at right angles. The standard recommends 12 inches or more of separation for parallel runs with power, more for higher voltages and longer parallels.
From single cameras to networked security controls
Security rarely lives alone. The cable you pull for cameras often shares spaces with access control cabling, card reader wiring, and intercom and entry systems. Coordination pays. If a door frame needs electronic door locks and a PoE access device for the controller, run spare Cat6. That same drop may support a camera overlooking the door, an intercom station, or an IP speaker later.
Access controllers vary. Some modern panels are PoE powered and distribute power to readers and strikes via local power supplies or PoE++ ports. Others require dedicated 18/2 for locks and 22/6 for readers. If you plan a biometrics-enabled lobby with biometric door systems, read the current draw and cabling spec carefully: some devices want shielded cable for Wiegand or OSDP, others run natively over Ethernet and power via PoE. Mixing traditional alarm integration wiring with IP gear in the same enclosure can work as long as you respect grounding, separation, and surge protection.
When you design the low voltage backplane, give each system a neat zone: camera PoE switches, access control panels, alarm terminations, and intercom gateways. It pays dividends during service when an after-hours call lands and the onsite staff needs to reset a specific device without guessing.
Alarm integration wiring without the noise
Alarm panels still lean on traditional 22 gauge conductors for zones and outputs. When you tie cameras to alarms for event-based recording or to trigger strobe lights, isolate relay power from the camera PoE. I keep relays on their own fused DC supply with common ground only where required by the integration device. Dry contact outputs from cameras are convenient but limited. If you need reliable long run signaling, use supervised loops on the alarm side and translate signals at the head end. The extra relay board costs less than a truck roll.
For long door contact runs in noisy environments, twisted, shielded 22/2 prevents false alarms. Terminate the shield at one end only to avoid ground loops. If a site insists on mixing shielded and unshielded pairs in the same bundle, document it clearly. The next tech will thank you.
Migrating a site: practical phasing from coax to IP
I’ve done many live upgrades while the DVR kept recording. The rhythm usually looks like this. Identify critical cameras that must not go dark, keep their coax intact, and map them to an encoder with IP output to the new VMS. In parallel, you begin pulling Cat6 for the new IP cameras. The encoder acts as a bridge so the control room uses one client. Over weeks, swap noncritical positions first, verify retention and analytics, then move the high value areas. When you reach the outdoor runs, decide case by case whether to convert the coax with EoC adapters or pull new fiber to poles. That choice depends on the conduit condition, rust, water ingress, and the cost of lift time.
Cabling tools that help during phasing include handheld testers that validate PoE class and draw, coax mappers for splitters you forgot were there, and a laptop with both copper and fiber adapters. The worst delays during a cutover come from misidentified cable paths and unpowered closets. Walk them before you announce dates.
PoE, analytics, and bandwidth reality checks
IP-based surveillance setup is not just frames per second and resolution. The analytics you enable change CPU load on the camera and, sometimes, power consumption. A camera running onboard people counting or object classification may draw a few extra watts. Multiply that across dozens of cameras and your PoE budget margin evaporates. If the plan is to ship raw frames to a server for heavy analytics, the network uplinks from the access switches need room. I like to size uplinks so average utilization sits below 40 percent with peaks below 70. That way a burst from a firmware update or a failover does not choke.
Speaking of firmware, plan for it. IP cameras, PoE access devices, intercoms, and NVRs all want updates. If a site forbids internet access from the security VLAN, stage updates internally and schedule windows. Keep a serialized list of device models and current versions. The day you face a CVE that affects a model fleetwide, you’ll move faster.
Intercom and entry systems: cabling that earns double duty
Modern intercoms have become little SIP video stations with door release control. Many run on PoE and happily share the structured cabling plant. At entry points, I bring two Cat6 to the intercom backbox when possible. One services the intercom, the other is reserve for a small camera, a reader, or future expansion. If the intercom needs to actuate an electronic door lock directly, verify power. Many intercom relays are dry contact only and need an external power supply to drive a strike or maglock. Keep power and signalling tidy, and test for REX and door position with independent circuits if your access control platform supervises them.
Outdoor gate pedestals are different beasts. Conduit fills with water, ground potential shifts during storms, and gate operators generate noise. Bond all metallic parts properly, use surge arrestors rated for PoE, and run a separate ground conductor when specified. If the site adds license plate capture later, https://manuelgaly964.bearsfanteamshop.com/designing-robust-network-and-power-distribution-for-mixed-use-facilities you’ll be glad you pulled extra fiber or copper in that trench.
Choosing between home runs, daisy chains, and spurs
Cameras rarely daisy chain in the classic sense, but you can architect spurs off small PoE switches in ceilings or risers. The tradeoff is serviceability. A ceiling switch above a conference room is invisible until it fails during a board meeting. If you go that route, install access panels, label them, and power the switch from a circuit you can reach. In warehouses, a small PoE switch on a column feeding nearby cameras shortens copper runs and reduces voltage drop. In offices with finished ceilings, home runs to an IDF keep maintenance predictable.
For access control cabling, daisy chaining readers is generally a no go unless the protocol supports it and the manufacturer approves. OSDP chaining exists, but it needs proper termination and is sensitive to bad splices. Most of the time, homeruns to a controller or to distributed door interface modules produce cleaner results.
Testing and documentation: the habits that keep you out of attics
I test each run for wiremap and length after termination, then again with PoE applied. A cheap inline meter that shows voltage and current draw catches cable defects that a basic wiremap misses. For larger projects, certifying Cat6 runs provides a baseline the client can use years later when someone changes a patch cord and breaks a link.
Photos help. Snap the inside of every enclosure and rack after dressing cables and before you close it up. Store them with drawings. When you or the next technician returns, knowing how a cable exited a conduit or which gland it used can shave hours off a diagnostics call.
Lastly, label both ends with a logical scheme that maps to drawings. Port 15 on Switch A in IDF 2 should be discoverable in the ceiling tile above Corridor B by anyone who can read. It sounds simple, yet it is the most consistent time saver in the trade.
Edge cases worth planning for
There are a few situations that deserve special mention.
- Historic buildings: you often cannot alter surfaces, and existing conduits may be the only option. Ethernet over coax or single pair Ethernet extenders can preserve finishes while modernizing. Explosive environments: use intrinsically safe barriers and certified devices. Even cable jackets matter. Ordinary PoE switches do not belong in classified areas. Massive campuses: fiber is your friend. Star topologies from core to distribution, then short copper to endpoints keeps loops at bay. Spanning Tree is a safety net, not a design tool. Remote power dependency: during outages, PoE switches on UPS extend recording time, while individually powered cameras do not. Prioritize which closets get battery and how much runtime you truly need.
Bringing it all together: one security network with room to grow
A well planned cable plant turns a collection of devices into a cohesive system. Cameras ride the same structured cabling as intercoms and access control panels, yet each has the room it needs. Door frames get the right mix of card reader wiring or OSDP, power for electronic door locks, and a spare Ethernet drop for a future PoE access device. Corridor ceilings host cameras that share IDF switches with voice and data, but on segmented VLANs with appropriate QoS. Alarm integration wiring stays orderly in its own zone, interfacing neatly with video and access at the software layer.
On larger builds, I design in service loops at the camera end, just enough slack to reterminate once or relocate a few feet without tearing up ceilings. Where vandalism is a risk, I use metal camera boxes with conduit sweeps and avoid exposed RJ45s. In harsh climates, I overrate PoE budgets in winter and summer and choose housings that can handle both extremes with honest datasheets.
That camera that blinked at me on the steel mezzanine taught me one more thing: never fear spending five extra minutes on a termination and twenty extra minutes on a path that honors distance, separation, and future access. Cable is the quiet backbone of every IP-based surveillance setup. When it is solid, the fancy parts do their job. When it isn’t, you end up in the ceiling at 2 a.m. with a flashlight and a promise you wish you hadn’t made.
A compact field checklist for dependable pulls
- Verify pathway and measure true length, including verticals and detours, before you cut. Match cable type to environment: plenum where required, UV rated outdoors, shielded only when needed and properly bonded. Plan PoE budgets with worst case draw and margin, and choose switch locations that keep runs under 100 meters. Label, document, and photograph terminations and enclosures; store maps where the client can find them. Test every run under load, not just with a wiremap, and record results with port and location.
Final thoughts from the ladder
Security work sits at the intersection of hardware and human expectation. People want clear images, doors that unlock every time, intercoms that just connect, and alarms that signal only when they should. None of that happens without disciplined cabling. Whether you are nursing coax into one more year of service or pulling bright blue Cat6 through a brand new riser to support networked security controls, the craft is the same. Respect distance, power, and environment. Keep things tidy and documented. Use your judgment when the drawing meets the wall. Do that, and your cameras won’t blink at you anymore. They will simply work.