Security systems rarely fail because of bad hardware. They fail at the seams, where panels, sensors, access points, and networks are supposed to cooperate. I’ve walked into more retrofits than I can count where the devices looked premium, but the alarm integration wiring behind the faceplates told a different story: daisy-chained power that sagged under load, shield drains tied off randomly, Wiegand lines run alongside 24 VAC, and a single spaghetti bundle trying to be everything at once. The building owner blamed the “software.” The fix lived inside the walls.
This guide walks through how to wire and synchronize alarm panels, access control, cameras, intercoms, and electronic door locks so they operate as one system. Think of it as a field manual for networked security controls. It leans on practical trade-offs, field-tested cable choices, and small decisions that pay off when something misbehaves at 2 a.m.
What “integration” really means on the wire
Integration looks like software, but it starts in copper and fiber. You have four layers in play, and each layer can either reduce friction or create it:
- Signaling and power at the door: readers, REX devices, door contacts, electrified hardware. Field control: door controllers, input modules, relay boards, and the alarm control panel or intrusion system. Transport: IP-based surveillance setup, intercom and entry systems, and controllers riding your network. Management: the servers, cloud bridges, and operator consoles that stitch it together.
If the cabling and terminations underpinning those layers are noisy, underpowered, or mixed in a way that violates manufacturer guidance, software can only do so much. Good integration wiring does three things consistently: it delivers stable power with headroom, it preserves signal integrity, and it documents intent so a future tech doesn’t “fix” the wrong thing.
Planning the topology before you pull a single run
I start with a single-line diagram that maps every door, camera, sensor, and panel. Then I annotate it with voltage, current, protocol, and cable type. The act of writing “Door 03 - 24 VDC at 650 mA peak - PoE-powered controller - fail-secure strike 350 mA inrush” forces discipline. It also surfaces the quiet killers: voltage drop and shared grounds.
Two decisions shape everything downstream. First, whether door controllers are centralized in an IDF or distributed near each opening. Second, whether readers and locks are powered by local supplies or PoE access devices. A distributed model often reduces access control cabling per door and shortens lock power runs, which improves reliability during inrush. A centralized model can simplify maintenance but demands heavier gauge cabling and careful planning for voltage drop. There is no universal right answer. Buildings with thick cores and long pulls often do better with distributed controllers. Small suites and retrofits often favor centralized.
For video and intercom, IP-based systems sit naturally on structured cabling. Keep camera home runs to IDF switches, avoid unnecessary midspan injectors, and prefer PoE+ or higher for PTZ and heater loads. Intercom and entry systems are increasingly IP as well, but older sites still use analog or two-wire IP adaptors, which complicate everything. If you inherit one of those, do not assume the “IP” label means Ethernet. Check the interface.
Cabling choices that save you twice
I still meet access control runs done with doorbell wire. It works for a week, then the voltage drop shows up when the door strike pulls harder on a cold morning. For access control, card reader wiring, and door hardware, use twisted, shielded cable from a vendor who publishes capacitance and resistance per thousand feet. My default for readers is 22/6 or 22/8 stranded, shielded, with a separate 18/2 or 16/2 for lock power when not using PoE-powered controllers. If the reader also handles keypad and LED/buzzer lines, spare conductors give you room to map and supervise correctly. For door contacts and REX sensors, 22/2 or 22/4 stranded, shielded, usually suffices.
Security camera cabling deserves the same respect. Solid copper Cat6 or Cat6a with verified performance beats “CCA” cable every time. CCA, or copper-clad aluminum, is a false economy that sags under PoE loads and oxidizes at terminations. If the run is near the 100-meter limit or you have outdoor enclosures with heaters or IR arrays, plan for PoE+ or PoE++ and keep the sustained load under 70 percent of the injector or switch port rating. For long corridors or parking lots, fiber to a small hardened switch with short copper stubs is cleaner than exotic extenders.
For intercom and entry systems, modern IP stations ride standard Ethernet. Legacy two-wire systems can be bridged, but that usually creates a support burden. If you must bridge, isolate those segments, avoid mixing high-voltage with signal runs, and be mindful of shielding and polarity.
Biometric door systems like fingerprint readers or facial terminals tend to be pickier about power and line noise than simple card readers. Give them clean 12 VDC or 24 VDC from a regulated supply, isolate their data lines from high-current conductors, and respect the manufacturer’s maximum cable length. Some vendors specify tighter Wiegand or OSDP limits than you expect.
Wiegand, OSDP, and the noise you don’t see
Older readers often use Wiegand, a simple unidirectional interface that runs on two data lines plus ground. It is easy to wire, and it is equally easy to wire poorly. Wiegand tolerates noise badly, and long runs or shared grounds near lock power can create ghost reads or dropped bits. If you stick with Wiegand, keep runs short, use shielded twisted pairs, terminate shields at one end only, and avoid splicing.
OSDP rides RS-485, supports encryption, and lets you supervise readers as intelligent devices. It is more forgiving over distance and supports multi-drop. If you have a choice, standardize on OSDP. It reduces the unknowns, and you can push configuration and even firmware updates to readers, which matters when you manage dozens of doors. Still, RS-485 is not magic. Respect polarity, terminate properly, and keep your stubs short.
A recurring field problem: shield drains tied at both ends, which create ground loops. Tie the shield to earth at the controller end only, leave it floating at the reader end, and separate power return paths from data reference wherever practical. If your site has multiple power supplies feeding different parts of the same door, bond their negatives intentionally at a single point, usually near the controller or the lock power supply’s common bus.
Power budgets and the dull math that prevents service calls
I treat every access door like a small motor load with control circuits wrapped around it. Electronic door locks are simple devices in theory, but inrush current and voltage drop make them misbehave if you guess. A maglock rated 600 mA might jump near an amp on pull-in. A fail-secure electric strike at 12 VDC might work fine for 30 feet of 18 AWG, then chatter at 120 feet of 22 AWG when the line sags by a volt. The fix is always the same: size power correctly, shorten heavy current runs, and check actual current with a clamp meter during activation. Measure, do not assume.
PoE access devices look tidy on paper. A reader-controller at the door powered by the switch saves a power supply, supervision, and sometimes a backup battery. The details matter. If the door also runs a high-current strike at 24 VDC and the controller’s relay is only rated for 2 A, you still need local power and a proper relay interface, or a PoE splitter that supports the load. When in doubt, run lock power separately, use a dedicated access-rated power supply with battery backup, and keep PoE for the low-current electronics.
For cameras and intercom endpoints, budget the switch with at least 20 to 30 percent headroom across the PoE budget. One winter, a client added IR bullets that were rated 9 W typical, 13 W max. On a cold night, they all hit 13 W together and pushed the switch over budget. Half the cameras rebooted in a rolling wave. It looked like a software bug until we checked the switch logs. Headroom would have cost a few hundred dollars; the service visit cost more than that.
Door-by-door wiring that holds up
Take a single door. A proximity reader with keypad, a fail-secure strike, a door contact, and a PIR REX. The building has a distributed two-door controller in a ceiling can above the corridor, fed by PoE for the electronics and a local 24 VDC 4 A power supply for the locks. How to wire it so it stays quiet:
- Reader on 22/8 shielded, shield tied at the controller end only. Use OSDP if supported. If not, keep Wiegand runs under 500 feet, preferably far less. Lock power on 18/2, home run to the 24 VDC supply. The relay that switches the lock sits in the controller can, not at the door frame. Add a flyback diode across DC strikes, or a MOV for AC devices, as recommended by the hardware manufacturer. Door contact on 22/2 shielded, supervised at the controller input with end-of-line resistors per the controller’s spec. Put the resistor at the contact, not in the can. REX on 22/4 shielded. Wire supervision if available and map it to the access system, not just the alarm. If you need a request-to-exit that also trips the maglock directly for life safety, follow the local code and ensure relay logic is failsafe. Bond the negative of the lock power supply to the controller common at a single point in the can. Do not tie power returns at the door frame.
In high-traffic areas or doors with electrified hinges, protect the cabling from flex fatigue. Prewired door loops or power transfer hinges cost more than making your own, but they outlast improvised solutions. For storefront aluminum doors, account for the space inside narrow frames. I have seen strikes wired with lamp cord because the installer couldn’t fit 18 AWG with a sheath. That fix looks fine until the first service visit.
Bringing intrusion and access into one language
Alarm integration wiring often aims to make the intrusion panel aware of door state, access granted events, and forced entry. The cleanest path is a data-level integration over IP or serial, where the access control system publishes zone states to the panel and the panel sends arming states back. That reduces double wiring. But many sites still tie the two halves with hardwired inputs and relay outputs, especially during phased upgrades.
If you go hardwired, map and supervise those links correctly. Access controllers should present relay outputs for door forced, door held, and access granted. Feed those to zone inputs on the alarm panel with the proper end-of-line values. Conversely, intrusion arming states or alarm outputs can drive inputs on the access controller to lock down doors or change schedules.
Watch for one subtlety: latching alarms. If you bring a latching burglary alarm into an access controller input that expects momentary events, you can leave the access system in a permanent “alarm” state. Use pulse stretching or programmable relays to normalize the signal. And label the terminations, both ends. One day someone will ask, “What does Input 7 actually do?” Future you will thank present you for the label that says “Burg Zone 12 - North Storage.”
Cameras that cooperate with alarms instead of talking past them
Security camera cabling feels straightforward, then you try to synchronize video bookmarks with alarm events and discover the NVR and the access controller use different NTP sources. Get time right. Put all systems on the same NTP servers, ideally the same stratum on your network. A 5-second drift defeats forensic timelines.
On the wire, separate camera home runs from high-current lock bundles where you can. If a camera must share a conduit with lock power, spec shielded Cat6 and ground the shield properly. Ground loops can show up as flicker or hum bars on analog, but on IP they manifest as intermittent reboots when PoE power hiccups. For outdoor https://www.losangeleslowvoltagecompany.com/service-area/ cameras, terminate in weather-rated boxes, use gaskets, and dab dielectric grease on RJ-45s. Ugly? Maybe. But the first storm will vindicate you.
If you integrate video verification with intrusion, give the alarm panel a way to bookmark or trigger pre/post recording on the VMS. Most modern systems listen for simple TCP events, webhooks, or dry contact closures via an I/O module. Verify that alarm-triggered clips include a pre-buffer of at least 5 to 10 seconds. The moment of interest usually starts before the contact opens.
Intercom, visitor management, and the lonely relay that messes it up
Intercom and entry systems tie visitor flow to your access control. The misstep I see often is relying on a tiny onboard relay in the intercom station to switch lock power directly over a long run. That relay will weld sooner or later, or the voltage drop will grow as the contacts pit. Use the intercom’s relay to drive a properly rated door controller input, or drive a local relay located near the power supply. Keep high current off the device at the wall.
If you use SIP-based intercoms on the same VLAN as cameras, manage QoS and storm control. Multicast traffic for video or discovery can drown a small switch and make intercom audio stutter. Segmentation helps. So does a switch that can handle IGMP snooping. On the wiring side, treat intercom endpoints like cameras: solid copper Cat6, PoE budget with headroom, and respect distance.
Grounding, bonding, and the quiet system
Noise rides along poor bonds and shows up at the worst times. A clean approach looks like this: earth bond the metal can of each controller enclosure to the building ground at that closet, bond the negative of each DC power supply to that same point, and tie cable shields to ground at one end only. Where lock power supplies live in different closets, bond them to that closet’s ground. Do not daisy chain grounds between doors.
Beware of shared conduits with fluorescent or LED driver lines. The induced noise on long parallel runs can be enough to upset Wiegand or make an OSDP device drop offline. If you must share, keep separation and use shielded cable with the shield tied correctly. Better yet, ask for a dedicated pathway early in the project.
Testing that goes beyond “green lights”
I build a small acceptance ritual for each opening. It adds minutes and saves hours later. The sequence is simple and rarely followed unless you write it down.
- Verify voltage at the reader and at the lock under load. Record it on the label inside the can. Confirm reader protocol and address, then pull a long cable wiggle test while reading multiple cards to check for intermittent terminations. Trip door contact and REX, verify supervision fault detection by removing an end-of-line resistor. Cycle the lock 20 times while watching current with a clamp meter. Listen for chatter or lag. If timing drifts, measure voltage drop back to the power supply. Kill PoE or DC power, confirm batteries carry the door for the expected duration, and verify that the door fails as intended (fail safe or fail secure) when power is absent.
Once per closet, I also test the battery charger and log the float voltage. Batteries lie about their health until the first outage. Replace them proactively on a 3 to 5 year cycle depending on environment.
Documentation that speaks to the next tech
A neat can with unlabeled wires is a time bomb. Label both ends of every cable with a scheme that survives water and time, not just a Sharpie. Inside each enclosure, leave a wiring diagram printed and updated with any field deviations. For networked security controls, keep a simple IP plan: switch name, port, VLAN, PoE class, device MAC, and static or DHCP reservation. Time drift and addressing conflicts account for more “mystery” outages than any firmware bug.
At the door, label the reader model, protocol, and any special settings like keypad mode. On the lock, note voltage, current, and duty rating. The next person will hesitate before swapping a fail-safe maglock onto a supply designed for fail-secure strikes if your label tells the story.
Retrofits, old buildings, and the stubborn physics of copper
Older sites test your patience. Conduits are full, paths are indirect, and you find cloth-insulated cable right when you thought you were done. You have two honest options: reuse runs strategically or carve new paths. If you reuse, test the cable, not just for continuity, but for resistance end to end, and for insulation integrity to ground. A cable that “works” for a contact may not work for an OSDP reader. Use protocol converters sparingly. They are a bridge, not a foundation.
When you cannot get a new cable to the door, a PoE access device mounted above the ceiling can help. It lets you use Cat6 to the controller and short stubs down to the door for the strike and sensors. Just remember heat. Above-ceiling spaces can hit temperatures that push devices out of spec. Choose enclosures and equipment with margin, and avoid burying splice points you’ll need to revisit.
Cyber touches the wire more than people think
If your alarm and access share the enterprise network, the wiring and switch configuration are part of your security posture. Lock down unused switch ports, disable auto-negotiation games, and create a management VLAN for controllers and panels. For OSDP, prefer secure mode and cycle keys on a reasonable schedule. On the physical side, keep controller enclosures in secured closets. A jumper across a relay on a ceiling-mounted controller is a lot easier to pull than hacking a firewall.
Keep firmware aligned across the fleet, but do not roll updates to everything at once. Staggered updates and staged labs prevent site-wide surprises. And keep a console cable handy. When things go sideways, you will want serial access.
Practical cables and distances, without the marketing gloss
You’ll see glossy spec sheets claiming long-distance limits that assume perfect conditions. Field reality is less generous. Solid rules of thumb:
- Wiegand behaves best under 250 feet on good STP, longer only if power and noise are well controlled. It can work to 500 feet, but you inherit risk. OSDP on RS-485 can run 4,000 feet in theory. In practice, stick closer to 2,000 feet per segment with proper termination, and prefer daisy chain over star. 12 VDC lock power beyond about 100 to 150 feet on 18 AWG starts to sag with typical strikes. Go 24 VDC when you can, or upsize the conductor. PoE stays at 100 meters for copper. If you need more, use fiber to an extender switch, not passive extenders that create troubleshooting nightmares.
These are guidelines, not absolutes. Test your specific devices and measure under load.
Two simple checklists that catch most mistakes
Pre-wire planning checklist:
- Map every device with voltage, current, and protocol. Note cable types and estimated distances. Decide on centralized versus distributed controllers per area, then size power accordingly. Align on reader protocol, prefer OSDP secure mode if supported by both ends. Define network segments, NTP sources, and PoE budgets with 20 to 30 percent headroom. Reserve space in conduits and enclosures for one future device per door. You will need it.
Door commissioning checklist:
- Measure voltage at reader and lock under load, write it inside the can. Verify input supervision by removing the EOL briefly and confirming alarm. Exercise the lock 20 cycles while watching current, look for chatter or heat. Check event flow end to end: badge, controller log, alarm system, VMS bookmark. Pull power to simulate outage and confirm fail-safe or fail-secure behavior matches life safety plan.
When to embrace PoE at the door, and when to avoid it
PoE simplifies installations and often improves reliability when done right. A PoE door controller plus a PoE reader or combined unit keeps low-voltage power centralized at the network switch and battery plant. It shines in tenant build-outs and interior doors with modest hardware loads. If the door demands a hungry strike, a maglock shared by two doors, or an electrified exit device, local 24 VDC with a robust supply and battery usually wins.
One hybrid approach works well: PoE to the controller for logic and supervision, with a local access-rated 24 VDC supply for locks. The controller drives the lock via a relay rated for the load, and the supply carries the real current. You gain network supervision and avoid stressing the PoE budget.
Lessons from field failures and how to avoid them
A few patterns repeat across sites:
- Readers that stop responding every afternoon turned out to share conduit with an HVAC contactor circuit that spiked on cycle. Shielding at one end and rerouting the lock power resolved it. Cameras that reboot during storms sat on exterior runs with water-wicked patch cords. Gel-filled outdoor cable and proper drip loops fixed it. An entire access cluster offline each morning at 8 a.m. mapped to a PoE switch that hit budget when a new set of phones powered up on the same stack. Segmentation and a higher PoE budget cured it. Phantom alarms late at night were traced to shared negatives between two power supplies feeding different doors. A single-point bond removed the loop.
These stories are not exotic. They are the inevitable result of mixed voltages and data in the same ecosystem. Respect separation, supervise everything you can, and give yourself test points.
The human part: coordination and labels win projects
Integration wiring is a team sport. Coordinate with the electrician early about dedicated circuits for access power supplies, preferred conduit paths, and grounding points. Ask IT for managed switches with IGMP, LLDP, and proper PoE classes. Share the NTP plan. On mixed-use sites, bring life safety into the conversation for egress and fire panel interfaces. If the fire alarm must drop power to maglocks on alarm, design that path clearly with listed hardware, and test it with the fire inspector present.
Above all, label your work so the next person can maintain it without reverse engineering. Good wiring is quiet wiring, and quiet wiring is the kind you do not think about because it never calls you back.
Bringing it all together
When panels, sensors, and access points genuinely synchronize, the building feels calm. A badge read creates an event in the access controller, the camera bookmarks the clip, the intrusion panel stays quiet during the scheduled disarm, and the intercom routes a contractor to reception without someone sprinting to the front. That calm rides on predictable power, disciplined cable choices, clear separation of signals, and documentation that takes ambiguity off the table.
Treat every cable as part of a communication contract. Choose the right conductors, terminate with purpose, ground thoughtfully, and measure under real load. Do those plain things well, and your alarm integration wiring stops being a tangle behind pretty faceplates and becomes what it should be: the solid spine of a networked security system that does its job without drama.