Fire alarm panels do not like surprises. They expect known loads, supervised circuits, and conductors that behave themselves when a device fails or someone cuts a cable in a ceiling void. Security gear tends to do the opposite. It wants flexible triggers, programmable relays, and network links that take their own path. Getting those worlds to cooperate is what integration wiring is about, and the success or failure shows up when a fire marshal walks the site with a clipboard and a stopwatch.
I have spent long nights smoothing out alarm integrations that looked fine on a napkin but fell apart under actual smoke or a pulled station. The pattern is always the same: a small electrical choice early on ripples through permitting, inspections, and the calm of a building manager whose elevators won’t recall when they should. This piece covers what has earned its place in my notebook. It leans on U.S. code families, especially NFPA 70 and NFPA 72, but the principles travel well. If you work internationally, align with your local standards, then use this framework to ask better questions on site.
Where fire and security meet
Most integrations hang on a handful of functions. We tie the fire panel to security and building systems to do predictable things during an alarm:
- Drop power to electronic door locks for free egress, or energize door holders to release. Trigger an access control system to unlock designated doors or place panels in fail-safe modes. Fire alarm supervisory outputs that recall elevators, control smoke dampers, or signal HVAC to go to purge. Interface to intercom and entry systems for live instructions and to donor power where appropriate. Coordinate networked security controls, security camera cabling choices, and power budgets so video recording continues while egress doors fail safe.
The wiring methods differ for each, but the core rub is the same: the fire alarm system is the authority during an alarm, and it must maintain supervision and integrity even if the security side malfunctions. You design like gravity pulls in that direction.
The code backbone you must respect
Three code threads guide nearly every decision:
NFPA 72 defines signaling performance, circuit supervision, and the behavior of initiating and notification appliance circuits. It also clarifies what the fire alarm control unit may monitor and what constitutes a control function. NFPA 70, the National Electrical Code, prescribes wiring methods, conductor listings, separation, and power source rules. The building code, often IBC or a local variant, sets the egress and door hardware requirements, including when doors must unlock under alarm and how delayed egress works.
The cross references can be messy. As a field rule, I walk them in this order: start with the building code for operational outcomes like free egress and elevator recall, check NFPA 72 for the signaling behavior and supervision requirements, then verify conductor ratings and separation with NFPA 70. A designer who lumps those together risks, for example, running a control circuit in the wrong cable jacket inside a plenum or mixing power-limited and non power-limited circuits in a way that violates listing.
A quick anchoring principle helps: fire alarm control circuits that can affect life safety, like releasing magnetic locks or door holders, must be fail-safe and supervised to a degree that loss of power or an open conductor leads to a known safe state. Security convenience yields to life safety every time.
Relays, contacts, and who owns the circuit
Most interactions happen through relays, either built into the fire panel or on dedicated modules. The safest integration reaches for dry contacts that are fully isolated and listed for the current and voltage they will switch. If a control function needs to cut power to a door lock power supply, do that with a listed power transfer relay or a releasing control module, not by sharing the same DC output between the access control panel and the fire panel.
On a job in a mid-rise in Charlotte, the access control vendor had used a panel output to feed mag locks, then expected the fire alarm to “tell” the access system to drop them. The better approach was a fire alarm control module that opened the 24 VDC leg feeding a UL 294 listed lock power supply that then distributed to each mag lock. Open the fire relay, locks lose power, doors release. During inspection, when the fire marshal pulled a station, doors released instantly and did so even when I physically unplugged the access panel’s network connection. We did not rely on a software handshake, only on a hardwired, supervised control function.
The corollary: you do not pull the access panel’s common ground across the fire alarm relays unless the listing and design explicitly permit it. Keep grounds clean and separate to avoid creating inadvertent reference paths that haunt you with ghost voltages and false supervisory troubles.
Supervision: the heart of reliable control
Supervision, in this context, means the fire alarm panel must detect opens, shorts, and sometimes ground faults on control circuits that it relies on to perform a life safety action. End-of-line devices are the workhorse. On a supervised control module, an EOL resistor delivers a known resistance when the circuit is normal. If someone cuts the conductor or shorts it, the module reports a trouble condition. For negative-acting functions like lock power cut, you want an arrangement where a broken wire also leads to the safe state.
There are two classic topologies worth explaining. In a door holder circuit, a fire relay supplies 24 VDC to normally energized door magnets. The module supervises the load with an EOL resistor at the far end. During alarm, the relay opens, magnets de-energize, doors close. If a wire opens, the magnets lose power and the panel throws a trouble. The door behavior remains safe.
With fail-safe mag locks driven by an access control power supply, we often place a fire relay in series with the power supply’s lock output. Better, many lock power supplies include a fire alarm interface designed to accept a normally closed contact. When that contact opens, the power supply cuts voltage to all or designated lock outputs. This approach keeps power distribution inside a UL 294 power supply, reduces field splices, and centralizes supervision. Some units provide a supervised input that will generate its own trouble if the fire control wire is broken. When available, use that feature. It saves headaches when renovations happen later and someone slices a riser.
Wiring methods and separation
The NEC has a precise vocabulary for power-limited fire alarm circuits, non power-limited circuits, and Class 2 or 3 remote-control circuits. The detail matters for cable jacket ratings, how circuits share raceways, and which splices are allowed. For a simple mental model:
- Power-limited fire alarm circuits typically use FPL, FPLR, or FPLP cable, matched to the environmental need. Plenum spaces demand FPLP. Security control circuits like door lock triggers and intercom control lines often qualify as Class 2 unless they ride along with higher energy conductors. Treat them with the same care for listing and separation as fire circuits when they interact. Keep power-limited and non power-limited conductors in separate raceways unless a listed barrier or the cable listing explicitly allows mixing. That inch of laziness in a common sleeve is where many red tags begin.
In a recent university retrofit, the mechanical engineer wanted the fire alarm to drop power to a 120 VAC smoke fan starter through a small control relay. That is a code trap. You do not land fire alarm conductors directly on line-voltage control unless you use a listed interface device designed to bridge power-limited to non power-limited circuits. The correct fix used a control module to drive a listed interposing relay in a dedicated enclosure, with clear separation and labels that survived the next fifteen years of maintenance crews.
The special problem of electronic door locks
Electronic door locks test your discipline because the hardware choices and use cases get complicated fast. A school will want fail-safe perimeter doors, delayed egress in certain corridors, and secure staff doors that stay locked, except during a fire alarm when they must release for free egress. Each scenario wants its own path.
For mag locks that are fail-safe by nature, the fire alarm’s job is to ensure power is removed during an alarm and during any supervised fault that compromises the control circuit. For electrified strikes and latch retraction mortise locks, the lock’s default state matters. Many are fail-secure, which means they stay locked without power. If the path of egress goes through that door, building and life safety codes often require that the door hardware allows egress without special knowledge or power, even under normal conditions. If you rely on access control to allow egress, you are already in the wrong neighborhood. When in doubt, add mechanical egress hardware that is code approved, then use access control to decide who enters.
When designing the fire interface for electrified strikes, especially in stairwells, we often avoid switching the lock circuit directly. Instead we use door position monitoring with fire alarm mode logic in the access controller and a true fire-alarm relay that is wired to drop power to the strike power supply states as required. This approach aligns with the simple truth that an occupied stairwell is not a place to debug logic. During an alarm, the door must open from the egress side, and the lock should not rely on a software rule to allow that.
Access control cabling and card reader wiring within a fire ecosystem
Access control cabling planning goes smoother when you look at it from the fire panel back. What happens to the reader, request-to-exit sensor, and the lock power if the fire alarm engages? If the power supply that feeds the controller and readers is not part of the fire control tree, fine, as long as the lock power path is. For card reader wiring, a simple habit pays off: route reader conductors and lock power separately in the door loop and label them. If the door needs a UL 294 channel and a fire recall line, do not rely on the same sheath unless the cable is listed for all involved circuits. Shielded reader cable is common to manage noise on Wiegand or OSDP lines. Keep the shield drain bonded on one side only and away from the fire alarm ground unless the manufacturer states otherwise.
When a building adds biometric door systems, for example a fingerprint reader that controls a server room, integration does not change the fire logic. If the room is part of an egress path or must release under alarm, wire the lock power path through the same supervised fire relay as any other space. It does not matter how fancy the reader is. Life safety does not negotiate.
Security camera cabling and IP-based surveillance setup during alarm events
Cameras do not usually tie directly to the fire alarm panel, but they live nearby in risers and IDFs. Plant forethought into power. An IP-based surveillance setup relies on PoE switches with enough budget to feed cameras and intercom stations. During an alarm, those devices should keep recording and keep talking. That means Uninterruptible Power Supplies in IDFs sized for at least 15 to 30 minutes, longer for critical areas. Keep network switches and PoE access devices on conditioned power separate from fire alarm power. Maintain cable separation from notification appliance circuits to avoid induced noise in the network plant.
When a video intercom is part of an intercom and entry systems plan at a lobby, tie its door release function to the same lock power supply channel that the fire alarm can interrupt. The access controller may issue the normal commands to unlock a door when a receptionist presses release, but the fire relay still owns the veto. In other words, a single fire-controlled break should silence every other control on that lock circuit.
Releasing service modules and door holders
Door holders and magnetic catches appear simple, then show their teeth during inspection. A common error is to lump door holders with notification appliance circuits that serve horns or strobes. Treat them as separate. Door holder circuits are control functions supervised by a module. They should not ride the same conductor as a horn/strobe NAC unless the fire system is explicitly designed for that dual purpose. Dropping a https://www.losangeleslowvoltagecompany.com/services/ NAC to close doors would also silence audible alerts prematurely if a wire opens. Keep door control and notification cleanly separate.
For releasing service modules used on preaction sprinkler risers or clean agent systems, supervision becomes even more exacting. The modules must monitor their wiring to solenoids, and the conductors need protection consistent with the agent system’s listing. Do not mix those control lines in the same conduit with general security runs.
Ground faults and the art of clean panels
Ground faults are the gremlins. Add a poorly shielded reader cable and a metal door frame and you may chase a phantom ground for hours on a fire panel that logs random troubles. The fix starts with predictable cable routing and proper sleeves at door cores. On a hospital expansion, we cut our ground faults by half simply by standardizing metal flex whips with insulating bushings at every frame penetration for lock and reader conductors. We bonded the frames where required and avoided stray, paint-scraped contact points that turned into accidental references to building steel.
Inside the fire panel, keep integration leads tidy, landed on labeled terminal blocks or manufacturer modules, never on wire nuts hanging mid-air. Every splice in the fire ecosystem should be accessible and in a listed enclosure. That readability saves lives and shortens service calls because somebody can follow the circuit with a meter without guessing which red conductor is the right red conductor.
Testing that wins inspections
I have seen integrations that looked tight, then a simple sequence test exposed gaps. Build a habit of two rounds: a bench validation before the ceiling closes, and a witnessed test with the Authority Having Jurisdiction that walks through alarm, trouble, and restoration. You want to simulate alarm while:
- Door holders release and re-energize correctly, with the fire panel reporting normal when clear. Locks drop power, free egress is confirmed at each designated door, and access control logs show the expected state. Elevator recall triggers and resets, with signals taken from the correct initiating zones, not from a “general” alarm summary. HVAC and smoke dampers react in the correct order, with time delays aligned to the mechanical design intent. No camera or intercom power is lost unexpectedly, and networked security controls remain reachable during the event.
Do not skip the trouble scenarios. Induce an open on a supervised control wire at the last device and confirm the fire panel shows trouble, and that the downstream life safety behavior is still safe. Then short the line and confirm the panel indicates the fault and no unintended device energizes.
Labeling and documentation that hold up over time
Integration fails most often five years after commissioning, when a new contractor touches the building. Labels and as-builts are the antidote. On every control relay, print both the fire alarm circuit designation and the downstream effect. On the access control side, include a note near the power supply that states which fire alarm module controls power drop and which doors are affected. Inside the panel, stick a simple line diagram with wire colors and EOL resistor values. It should be the kind of drawing that someone can hold in one hand on a ladder and use a headlamp to trace.
Save final test logs. Many AHJs appreciate a packet that shows functional test steps and outcomes, plus photos of relay terminations. It makes future expansions smoother and reduces debates about how the original design intended to work.
Networked security controls and the role of software
Modern systems are networked, and there is real value in using software-based events to augment the experience during a fire. For example, the access control server can change door schedules, the VMS can call up preset camera views near egress routes, and an intercom platform can push audio messages to designated stations. All good, but none of those software layers should hold any responsibility for the underlying life safety action. Consider software an overlay for situational awareness, not a dependency. The hardwired, supervised control circuit still governs the lock power and door holders. That rule keeps liability clean and behavior predictable when network segments fail.
PoE access devices and power planning
We see more PoE-powered door controllers and even PoE door locks. These devices reduce local power supplies and simplify access control cabling, but they change fire integration tactics. If a lock is powered by PoE, your fire relay cannot just flip a 24 VDC pair. You must program the PoE switch or the access platform to de-energize the port during alarm, or better, you must ensure the lock hardware is fail-safe and that free egress does not rely on power at all. Reliable strategies include using request-to-exit hardware that mechanically provides egress regardless of PoE state and placing any door held locked by PoE on a path where building code allows it to stay secure during alarm. When in doubt, abandon the PoE lock for a traditional low-voltage lock fed by a fire-interruptible power supply. Fancy is fun until a plan reviewer asks for the listing that ties your PoE scheme to a life safety control.
Intercom and entry systems that play nicely
Intercoms often share door strikes and request-to-exit sensors. The integration trick is to prevent backfeed. If an intercom is wired to energize a door strike, route that function into the access control input instead of paralleling the strike directly. Then have the access controller issue the unlock, with the fire relay still placed to drop the lock power line upstream. When an alarm occurs, the intercom “unlock” does nothing because the power source is interrupted by the fire control. This keeps the intercom vendor from accidentally bypassing your fire governance with a jumper in a handset base station.
Audio during an emergency is another consideration. Some intercom platforms can act as auxiliary speakers, but they are not notification appliances unless listed as such. Do not overload your fire alarm notification circuits with third-party speakers to save a line item. Keep life safety audio separate and code compliant, then integrate intercom audio as an extra channel for instructions that are not life safety critical.
Common mistakes and how to avoid them
Three failures show up over and over. First, trying to share a common DC supply between access control and fire control of door hardware to save parts. Do not do it. Give the locks their own UL 294 power supply and use the fire alarm relay input it provides. Second, hiding splices above a ceiling without a junction box or label. Every service tech who comes after you will curse your name. Third, assuming software integration replaces hardwired control. The day the network is down is the day you will be glad you used a mechanical relay with supervised leads.
There is also a hidden trap in mixed-voltage doors. A reader powered by 12 VDC, a lock at 24 VDC, and a door holder at 24 VDC can create accidental ties if you pull a shared ground through a frame hinge. Keep conductors and references separate, and check with a meter before you tighten the last screw. If the frame reads anything more than a whisker of voltage to building ground, investigate before closing up.
A quick field checklist before you call for inspection
- Verify every fire-controlled output that affects egress is supervised to the end device with a proper EOL, and that a broken or shorted wire results in a panel trouble and a safe door state. Confirm lock power sources are listed, labeled, and have a dedicated fire alarm relay input that you have actually wired and tested. Check cable types and separation in risers and plenums, including sleeving at door frames. Match FPLP in plenum spaces, and do not mix non power-limited conductors with power-limited without barriers. Simulate alarm and trouble at least twice with different initiating devices and watch the whole building response: doors, dampers, elevators, intercom messaging, and camera recording. Document relay maps, resistor values, and terminal numbers on a one-page diagram and leave a copy in the fire panel and with the access control head-end.
What good looks like
A well-executed integration feels boring when you test it. Pull a station, strobes fire, horns sound, door holders release, mag locks drop, and the security system logs a fire mode without any drama. Cameras keep recording. The intercom announces evacuation instructions. After reset, the system comes back on its own, and you are not chasing a phantom ground or a stuck relay. When the AHJ asks how you supervise the lock control, you can point to the module, the wiring diagram, and the EOL at the far end of the circuit. When IT asks if the network is required for doors to release, you can say no and mean it.
That is the standard worth building toward. It respects the codes, the physics in the wire, and the people who will use these doors and systems when smoke is in the corridor. If you carry anything forward, make it this: give the fire alarm system the clean, supervised control of anything that touches egress, and let security ride alongside as a helpful companion rather than the driver. Everything else is craft and careful wire work.