A practical, AHJ-friendly deep dive for designers, installers, NICET candidates, and plan reviewers.
Covers platform fit, integrated hardware, listings framework, UL 864 9th Edition architecture impacts, commissioning,
troubleshooting, and EDGE-CU programming workflow.
Primary: Edwards Edge vs EST4, UL 864 9th EditionSecondary: Edge vs IO Series, CSFM listed panel, FDNY COAAudience: contractors, engineers, AHJs, NICET
Submittal reality check: verify listings and approvals (UL/ULC/CSFM/FDNY COA/FM) by exact model number,
configuration, accessories, compatible devices, and any listed limitations. This guide provides the framework and field logic.
The Edwards Edge is Edwards’ new small-to-medium addressable fire alarm control panel platform and is positioned as a
direct replacement for the IO Series. It is designed to reduce install complexity, provide more onboard capability,
and modernize daily operations for technicians and inspectors.
Practical takeaway: Edge is the “modern IO replacement lane.” EST4 remains the “large scale and deeper ecosystem lane.”
Edge Panel Architecture and Onboard Capabilities
Internal architecture of the Edwards Edge addressable fire alarm control panel showing integrated power supply, NAC circuits, battery capacity, and onboard relays.
Edge ships as an integrated assembly (CPU side and power supply side together), which reduces field assembly and speeds installs.
The platform also adds meaningful onboard capability compared to many legacy small/medium systems.
Onboard Feature
What You Get
Why It Matters
Integrated SLC
Onboard SLC loop
Fewer expansion parts for many projects.
4 NACs
Four onboard NAC circuits
Common small/mid notification loads stay in one cabinet.
NAC as AUX
NACs can be configured as 24V AUX (resettable/non)
Cleaner power strategy when you need 24V field power.
3 Relays
Alarm, Supervisory, Trouble relays
Direct interface for common outputs and building functions.
10-inch Display
Large display for visibility
Better field usability, faster event review.
Battery Support
Up to 65Ah batteries (larger cabinet may be required)
More standby headroom when required by design.
Inner Door Options
Up to 72 switches/LEDs on inner door expansion slots
Strong annunciation and control options when required.
Full Edge vs IO Series Comparison (retrofit reality)
Feature comparison between Edwards Edge, Edwards IO Series, and Edwards EST4 fire alarm control panels highlighting architecture, NAC capacity, and system capabilities.
Edge is intended to replace the IO Series, but retrofits require smart planning. Some IO items transfer cleanly and others do not.
The key is aligning the proposed Edge model with the existing IO footprint and migration goals.
Category
Edwards Edge
Edwards IO Series
Platform Role
New small/medium platform, IO replacement
Legacy small/medium platform
SLC Strategy
Integrated onboard SLC
Often required loop expanders
NAC/AUX
4 NACs, convertible to 24V AUX
More reliance on add-on NAC modules
Retrofit Models
EDGE-ML-R/G (new installs + IO-64 replacements) and EDGE-ML-RRK (IO-500/IO-1000 retrofit kit)
Existing installed base
Program Migration
IO-1000 programs may be importable (version dependent); IO-64 must be rebuilt
IO-CU programming environment
Compatibility Watchouts
IO loop expanders not compatible; Edge uses Edge-specific cards
Legacy expanders and accessories
Retrofit planning tip: Quote labor differently for IO-64 (rebuild) vs IO-1000 (potential migration).
Edge vs EST4: Pros/Cons and “When to Choose Which”
Edwards Edge: Pros
Integrated capability tuned for small to mid-size installations and IO replacements.
Cleaner commissioning workflow centered around EDGE-CU and modern diagnostics.
Better field usability through a larger interface and clearer event handling.
Edwards Edge: Cons
Market familiarity varies by AHJ and region (verify acceptance expectations early).
Retrofit compatibility must be confirmed before assuming reuse of legacy hardware.
Edwards EST4: Pros
Enterprise-scale ecosystem and established deployments for large, accessory-rich projects.
High AHJ familiarity in many jurisdictions due to broad install base.
Edwards EST4: Cons
More complexity depending on module selection and project scope.
Overkill risk on smaller projects where Edge fits better.
Rule of thumb:
Choose Edge for IO replacements and small/mid new installs. Choose EST4 for large-scale applications and deep expansion needs.
Listings and Approvals Framework (UL, ULC, CSFM, FDNY, FM)
Plan review success comes down to documentation. Use this framework in your submittal package and always verify approvals by exact model number.
Listing / Approval
Where It Typically Matters
What to Include in Submittal
UL 864
Most US jurisdictions
Exact control unit and accessory listing references.
ULC
Canada (or specs requiring ULC)
ULC listing confirmation for panel + accessories.
CSFM
California
CSFM listing number and scope/limitations for configured equipment.
FDNY COA
New York City
FDNY acceptance documentation for the exact configured system.
FM Approval
Industrial or insurer-driven specs
FM approval scope and applicability to your configuration.
Best practice: Add a dedicated “Listings/Approvals Appendix” page in your submittal. Reviewers love tidy packages.
UL 864 9th Edition Impact on Panel Architecture
UL 864 9th Edition is an equipment standard that influences how modern panels are engineered internally.
In the field, it typically shows up as more deterministic event handling, stronger software integrity behavior, and clearer supervision and timing discipline.
Deterministic response behavior: faster event processing and prioritization when multiple events occur.
Software integrity: stronger watchdog and controlled-state fault handling.
Communications supervision: more formalized “path health” logic for IP and network reporting.
Noise immunity: better resilience through design discipline (filtering/layout/shielding).
Output timing: more disciplined NAC behavior and synchronization expectations.
Spec language starter:
“Provide a UL 864 listed control unit and accessories capable of deterministic event processing and supervised communications, installed per NFPA 72.”
Edge Commissioning Workflow (step-by-step)
Commissioning workflow for the Edwards Edge fire alarm control panel including firmware loading, EDGE-CU programming, device configuration, and system verification.
Install and power the panel (verify AC, batteries, and field wiring).
Load firmware (download separately and update as required).
Launch EDGE-CU and connect to the panel.
Import IO programs if applicable, otherwise build the configuration.
Configure devices and addresses (labels, descriptions, points).
Set central station reporting (CID assignments and communication path tests).
Find Device diagnostics to speed device-level troubleshooting.
Edge Panel Troubleshooting and Diagnostics Guide
Start with event priority
Before resetting anything, review current events and event history. Prioritize alarms first, then supervisory, then trouble conditions.
Use Find Device before you go hunting
The Find Device function helps locate devices by address and quickly confirms device type, label, and status.
This reduces “walk-the-building” time during inspections and service calls.
Verify EOL, polarity, terminations, and removed/failed appliances.
Battery Trouble
Low voltage, end-of-life, charger issue
Load test batteries, confirm charger output and battery wiring.
Ground Fault
Conductor contacting ground
Isolate circuits one-by-one to identify the grounded path.
Comm Trouble
Dialer/IP path issue or config mismatch
Verify account setup, CID mapping, supervision, and test signals end-to-end.
Access levels and service login
User ID: 00#
Password: 1234
Best practice: Document what you see before clearing. Event history is how you prove cause and prevent repeats.
EDGE-CU Programming Guide
Edge programming is performed using EDGE-CU. Your goal is a clean database: clear device labels, predictable logic, and correct CID mapping.
That’s what makes future service calls fast and painless.
Programming checklist
Create a new project and select the correct panel model.
Configure NACs (notification mode or AUX power mode as required).
Confirm relay behaviors (alarm/supervisory/trouble and any project interfaces).
Assign unique CID codes as required for central station reporting.
Upload configuration, test, then save a backup of the final configuration file.
IO migration notes
Some IO configurations may be importable (version dependent).
Plan IO-64 replacements as “rebuild from scratch.”
Plan IO-1000 replacements as “verify migration path.”
Programming best practice: Labels and CID mapping are not paperwork, they are service speed.
Spec Comparison Charts (embeddable)
A) Spec-Sheet Chart (checkbox placeholders)
Spec Category
Edwards Edge
EST4
UL 864
☐ Verified per exact model
☐ Verified per exact model
ULC (Canada)
☐ If applicable
☐ If applicable
CSFM (California)
☐ Verify listing number
☐ Verify listing number
FDNY COA (NYC)
☐ Verify COA number
☐ Verify COA number
FM Approval
☐ If required by spec
☐ If required by spec
Commissioning speed
Streamlined onboarding
Mature but configuration-dependent
Ecosystem depth
Growing
Extensive
B) UL 864 9th Edition architecture impact chart
Impact Area
Edge trend
EST4 consideration
Event response behavior
Modern deterministic handling
Verify configuration and revision alignment
Software integrity
Guarded logic and fault behavior
Depends on configured components
Communications supervision
Formal path health logic
Often modular, confirm supervision method
Noise immunity
Design discipline for harsh environments
Confirm revision level where needed
NAC timing/sync
Disciplined output timing
Confirm compatibility matrix
FAQ
Is the Edwards Edge panel listed and approved everywhere?
Listings/approvals are configuration-specific. Verify UL/ULC/CSFM/FDNY COA/FM by exact model and accessories for your submittal package.
Can I reuse IO loop expanders on Edge?
Plan for replacement and verify compatibility early. Loop expander assumptions are a common retrofit pitfall.
Can I import existing IO programming?
Some IO programming may be importable (version dependent). Treat IO-64 replacements as rebuilds and IO-1000 replacements as potential migration candidates.
Fire Alarms Online: code-driven fire alarm design guidance, install workflows, and NICET study resources.
The 2025 California Building Standards Code (Title 24) updates include important clarifications and enforcement emphasis for carbon monoxide (CO) alarms and detection systems.
This article breaks down:
When CO alarms/detection are required under 2025 CBC Section 915 and 2025 CFC Section 915
How the IFC Section 915 model requirements (the backbone of many state fire codes) broaden the “when required” scope beyond just dwelling units
Power and interconnection rules
Enclosed parking garage CO sensor requirements and how California coordinates to CMC 403.7.2
How NFPA 72 (2022) applies for inspection, testing, and maintenance where applicable
When Are Carbon Monoxide Alarms / Detection Required? (Two-Lane Approach)
CO requirements get mis-described a lot because designers mix “dwelling unit alarm rules” with “broader building CO detection rules.” To keep your plans plan-check-proof, think in two lanes:
Lane 1: Dwelling Units & Sleeping Units (CBC 915 focus)
Under 2025 CBC Section 915, CO alarms are commonly required in dwelling units/sleeping units when CO exposure risk sources are present, such as fuel-burning appliances and attached garages communicating with the dwelling unit. (CBC 915 framework.)
Common residential triggers include:
Fuel-fired appliances
Gas fireplaces
Fuel-burning forced-air furnaces
Attached garages that communicate with the dwelling unit
Listed combination smoke and carbon monoxide alarms are permitted when installed in accordance with CBC 915 and CFC 915 requirements.
Important: The IFC Section 915 (model code basis for many state fire codes, including California’s structure) is broader than only dwelling-unit triggers. It addresses CO detection requirements for new and existing buildings where interior spaces are exposed to CO sources (direct sources, adjacent spaces with communicating openings, and forced-air-related source conditions). In other words: your project may require CO detection even when it doesn’t look like a classic “residential attached garage” situation.
Plan-review tip: On commercial/mixed-use jobs, describe CO detection requirements as:
“Provide CO detection where required by CFC 915 for interior spaces exposed to CO sources, and provide CO alarms where required by CBC 915 for dwelling/sleeping units.”
Adjacent spaces with communicating openings where CO could migrate
Forced-air pathways that can distribute CO to other areas
Always coordinate exact device placement with manufacturer instructions, the adopted code language, and AHJ expectations.
Power & Interconnection (CFC 915.4 + CBC 915 structure)
Power Source (CFC 915.4.1)
CO alarms shall receive primary power from building wiring where such wiring is served from a commercial source, with battery backup where required.
Interconnection (CFC 915.4.4 / CBC 915 framework)
Where more than one CO alarm is required, alarms must be interconnected so activation of one activates all required alarms within the applicable unit/area. California’s 2025 cycle specifically retains clarifying language around interconnection implementation.
Combination Smoke/CO Devices
Combination smoke/CO alarms are permitted where properly listed/approved and installed per manufacturer instructions and adopted code requirements.
Enclosed Parking Garages – CO Sensors and Ventilation Control (CFC 915.6.1 + CMC 403.7.2)
Carbon monoxide sensors installed in enclosed parking garages to control ventilation systems in coordination with CFC 915.6.1 and CMC 403.7.2.
This is where a lot of projects get tripped up.
Model code note: The IFC framework ties enclosed garage gas detection to mechanical ventilation code references (model mechanical code structure).
California note: In the 2025 cycle, California explicitly coordinates enclosed garage detector maintenance expectations through CFC 915.6.1 with reference to CMC 403.7.2.
Key takeaway: Treat enclosed garage CO sensors primarily as a mechanical ventilation control / IAQ scope unless the AHJ/EOR requires FACU integration. If integrated into the fire alarm system, document supervision, pathway, and point type clearly.
NFPA 72 (2022) – How to Reference It Without Getting Burned
Older references commonly point to NFPA 720 for CO detection. NFPA has stated that NFPA 720 requirements were incorporated into NFPA 72.
Safe spec language:
Install per the adopted California codes (CBC/CFC) and manufacturer instructions.
Where CO detection/notification equipment is part of a signaling system, perform inspection/testing/maintenance per NFPA 72 (2022) as applicable.
2022 vs 2025 Code Comparison (CBC/CFC CO Requirements)
Topic
2022 Cycle (General)
2025 Cycle (What to watch)
Plan-Check Proof Note
Scope / “When Required”
Commonly described as dwelling-unit driven in many field guides.
Must describe both: dwelling/sleeping units (CBC) AND broader interior-space CO exposure conditions (CFC/IFC framework).
Write the “two-lane” note on the cover sheet.
Power
Hardwired where served by commercial power; battery backup where required.
Same concept; cite CFC 915.4.1 explicitly for reviewer confidence.
Call out power method and any remodel constraints.
Interconnection
Interconnect multiple required alarms.
California emphasizes implementation clarity; cite CFC 915.4.4 for consistency.
State “hardwired or listed wireless” and show it on plans.
Enclosed Parking Garages
Often treated as mechanical/energy controls work, coordinated across disciplines.
CFC 915.6.1 coordinates maintenance expectations to CMC 403.7.2 in California.
Add a garage SOO and fail-safe behavior.
NFPA Reference
NFPA 720 often cited historically.
NFPA states CO requirements are incorporated into NFPA 72; cite NFPA generally unless quoting licensed text.
Write “NFPA 72 (2022) where applicable + manufacturer instructions.”
Plan Review Notes (Copy Into Drawings)
CARBON MONOXIDE (CO) – 2025 CBC / 2025 CFC GENERAL NOTES
1. Provide CO alarms and/or CO detection where required by the adopted codes:
• 2025 CBC Section 915 for dwelling units and sleeping units (life-safety CO alarms).
• 2025 CFC Section 915 for interior spaces exposed to CO sources (CO detection scope).
Reference IFC Section 915 as the model basis for broader CFC 915 scope where applicable.
2. Power: CO alarms shall receive primary power from building wiring where served by a commercial source, with required secondary power/battery backup. (CFC 915.4.1)
3. Interconnection: Where multiple CO alarms are required, alarms shall be interconnected so that activation of one activates all required alarms within the applicable unit/area. (CFC 915.4.4 / CBC 915 framework)
4. Combination Smoke/CO Alarms: Combination devices shall be listed/approved and installed in accordance with adopted code requirements and manufacturer instructions.
5. Enclosed parking garages (where applicable):
CO/NO2 detectors used for ventilation control shall be coordinated with mechanical design.
In California, detector maintenance expectations coordinate through CFC 915.6.1 with CMC 403.7.2.
6. Inspection, testing, and maintenance:
Perform per adopted code requirements, manufacturer instructions, and NFPA 72 (2022) where applicable.
Note: NFPA states NFPA 720 requirements were incorporated into NFPA 72.
Garage CO Sensor Sequence of Operations (Typical)
ENCLOSED PARKING GARAGE – CO SENSOR CONTROL (TYPICAL)
GENERAL
- Provide CO (and where applicable NO2) sensors for ventilation control.
- Coordinate with mechanical ventilation controls per CMC 403.7.2.
- Maintain per CFC 915.6.1 and manufacturer requirements.
CONTROL LEVELS (VERIFY WITH EOR / MECH DESIGN)
Low CO Setpoint (typical 25–35 ppm; adjustable):
- Enable exhaust fans at LOW SPEED (Stage 1).
- Enable supply/make-up air as required.
- Send RUN status to BAS if provided.
High CO Setpoint (typical 50–100 ppm; adjustable):
- Enable exhaust fans at HIGH SPEED (Stage 2).
- Flag high-level condition to BAS (supervisory/trend).
- Continue ventilation until levels fall below reset threshold.
RESET / PURGE DELAY
- After CO drops below LOW setpoint, continue fans for timed purge (typical 5–15 minutes) then return to standby.
FAIL-SAFE
- On sensor fault, power loss, or communications loss, command minimum fan operation (Stage 1) and report TROUBLE/FAULT to BAS.
MAINTENANCE
- Test/calibrate per manufacturer interval.
- Maintain per adopted code requirements and NFPA 72 (2022) where applicable.
When a building emergency happens—fire, smoke, power outage, earthquake—some people can’t use stairs safely. That’s where accessible means of egress planning steps in. The idea is simple: if someone needs help getting out, the building must give them a safe place to wait and a reliable way to call for rescue assistance.
In the International Building Code (IBC), one of the most important “call for help” tools is the two-way communication system at elevator landings. This is not the phone inside the elevator car. It’s a system located at the elevator landing on certain floors so a person who needs help can quickly reach a fire command center or approved central control point. (Corada IBC/CBC excerpt reference)
An elevator landing two-way communication system is a code-required rescue assistance communications point placed at the elevator landing on certain accessible floors. It must provide two-way voice communication (and have audible and visible signals) and, when the central point isn’t always staffed, it must be able to dial out to a monitoring location or 9-1-1. (Corada IBC/CBC excerpt reference)
How it ties to accessible means of egress and rescue assistance
In IBC terms, this requirement is tied to Accessible Means of Egress (Section 1009). Elevator landings are treated as key wayfinding and assistance locations—especially in multi-story buildings—because they’re often the most intuitive place someone will go if they can’t use stairs.
Where the IBC Actually Requires Elevator Landing Two-Way Communication
IBC Section 1009.8: the core trigger and where it applies
The core IBC rule is straightforward:
A two-way communication system (meeting IBC 1009.8.1 and 1009.8.2) must be provided at the landing serving each elevator or bank of elevators on each accessible floor that is one or more stories above or below the level of exit discharge. (Corada IBC/CBC excerpt reference)
“Each accessible floor” explained
This doesn’t mean every floor in every building. It means floors that are accessible (think: part of the accessible route and occupied/served spaces that must be accessible under the code). If a floor isn’t an accessible floor in the first place, it typically doesn’t trigger this specific landing requirement.
“One or more stories above or below exit discharge” explained
Exit discharge is the level where occupants exit to the exterior and reach a public way. If you have occupied accessible floors above that level—or below it (like a basement level)—IBC 1009.8 is trying to ensure that people who can’t use stairs still have a reliable way to call for help.
IBC 1009.8.1: what the system must do
IBC requires the system to connect each required location to a fire command center or central control point approved by the fire department. If that central point is not constantly attended, the system must have timed, automatic telephone dial-out that provides two-way communication with an approved supervising station or 9-1-1. The system must also include audible and visible signals. (Corada IBC/CBC excerpt reference)
IBC 1009.8.2: directions and location ID
IBC also requires posted directions adjacent to the system: how to use it, how to summon assistance, and written identification of the location. (Corada IBC/CBC excerpt reference)
How Areas of Refuge and Elevator Landings Interact (Avoiding Double-Coverage)
IBC 1009.6.5: areas of refuge two-way communication
IBC states that areas of refuge must have a two-way communication system that complies with the same requirements (1009.8.1 and 1009.8.2). (Corada IBC/CBC excerpt reference)
Design choice: landings vs. areas of refuge—what AHJs often expect
In real projects, designers often choose a strategy: put communications at elevator landings (where required), or place communications within designated areas of refuge (which can sometimes remove the need for elevator-landing devices via an exception—see Exception 1). The key is to avoid gaps. If you “trade” landing devices for area-of-refuge devices, make sure the areas of refuge are actually provided and located correctly.
NFPA 72 Deep Dive: Where the Fire Alarm/Signaling Rules Come In
NFPA 72 includes Emergency Communications Systems in Chapter 24, and the 2022 edition lists Section 24.10: Two-Way Emergency Communications Systems for Rescue Assistance. This matters because elevator landing communication for rescue assistance is increasingly treated as a two-way emergency communications system, not a generic convenience intercom. (NFPA 72 (2022) product page / contents)
Listing/performance expectations (UL 2525) and why it matters
Industry guidance highlights that NFPA 72 (2022) requires systems used for area of refuge, stairway, elevator landing, and occupant evacuation elevator lobby rescue assistance communications to be listed to UL 2525 (or equivalent). (UL guidance on Area of Refuge Communication Systems)
Pathway survivability: when designers must think beyond “just an intercom”
Some jurisdictions and submittal documents call out survivability expectations alongside NFPA 72 emergency communications requirements, which can influence wiring methods and pathway design. (Example AHJ guidance document)
The Six IBC Exceptions—Fully Explained with Practical Scenarios
IBC 1009.8 includes six exceptions where elevator landing two-way communication systems are not required. (Corada IBC/CBC excerpt reference)
Exception 1: Communication is provided within areas of refuge (IBC 1009.6.5)
Code concept: If the two-way communication system is provided within areas of refuge per 1009.6.5, then it’s not required at the elevator landing.
Scenario: A high-rise office tower provides areas of refuge at each exit stair enclosure landing with compliant two-way rescue assistance call stations tied to the fire command center (or dial-out if not constantly attended). If those areas are properly designed and accepted, elevator-landing stations can be omitted.
Pitfall: Teams sometimes assume “the stair landing is an area of refuge” without documenting it. If the AHJ doesn’t accept the area-of-refuge layout, the exception may be denied.
Exception 2: Floors provided with ramps conforming to Section 1012
Code concept: If a floor is served by compliant ramps, the elevator landing two-way communication system is not required on that floor.
Scenario: A museum mezzanine is accessible via an interior ramp system meeting Section 1012. Because a ramp provides a non-elevator accessible means of egress, the landing two-way device may be unnecessary for that level.
Pitfall: If the “ramp solution” is not a true accessible means of egress (or doesn’t comply), the exception won’t hold.
Exception 3: Service elevators not part of the accessible means of egress (and not part of the required accessible route into the facility)
Code concept: Two-way communication isn’t required at landings serving only service elevators that are not designated as part of accessible means of egress and are not part of the required accessible route into the facility.
Scenario: A locked staff-only service elevator moves supplies between loading and storage, with no public or patient accessible route dependence. The landing two-way device can be excluded if documentation proves it’s not part of accessible egress/route.
Pitfall: If occupants commonly use it (even informally), plan review may reject the exception.
Exception 4: Freight elevators only
Code concept: Two-way communication is not required at landings serving only freight elevators.
Scenario: A warehouse freight elevator is intended solely for pallets/equipment and is not used as an occupant elevator. Landing communication points can be omitted.
Pitfall: If the “freight” elevator is actually used by people or resembles passenger service, the AHJ may treat it as serving occupants.
Exception 5: Private residence elevator
Code concept: Two-way communication is not required at landings serving a private residence elevator.
Scenario: A private multi-level dwelling includes a private elevator inside the unit, not serving the public. Landing devices aren’t required by this section.
Pitfall: A shared elevator in a multi-family building is typically not a “private residence elevator.”
Exception 6: Group I-2 or I-3 facilities
Code concept: Two-way communication at elevator landings is not required in Group I-2 or I-3 facilities.
Scenario (I-2): Hospitals often use defend-in-place and staff-assisted relocation protocols; communications and evacuation are managed differently.
Scenario (I-3): Detention/correctional occupancies require controlled movement and security-managed evacuation, making public call stations at landings less compatible with operations.
Common Design Pitfalls (and How to Avoid Plan Review Rejections)
Mixing up elevator car emergency communication with landing communication: the elevator cab phone is not automatically the same as the required landing rescue assistance station.
Forgetting the “central control point approved by the fire department” requirement: if the point isn’t constantly attended, dial-out becomes critical.
Using non-listed equipment when the jurisdiction expects UL 2525 listing: many AHJs expect rescue assistance systems aligned with NFPA 72 Chapter 24 / 24.10.
Documentation Checklist for Permits and Inspections
Identify locations at each elevator landing where required by IBC 1009.8 (or clearly document the exception used).
Show audible + visible signaling behavior and posted directions/location identification adjacent to the device.
Show the central control point and attendance status; if not constantly attended, specify timed automatic dial-out.
Coordinate NFPA 72 emergency communications approach (commonly Chapter 24 / 24.10) and any local survivability requirements.
FAQs (Code-Practical Answers)
1) What IBC section requires elevator landing two-way communication systems?
IBC Section 1009.8 requires a two-way communication system at the landing serving each elevator or bank of elevators on each accessible floor one or more stories above or below exit discharge, unless an exception applies.
2) If we provide areas of refuge call boxes, do we still need elevator landing stations?
Often no—Exception 1 allows omitting landing stations if compliant two-way communication is provided within areas of refuge per 1009.6.5.
3) Does a ramp remove the need for elevator landing communication on that floor?
It can. Exception 2 says two-way communication systems aren’t required on floors provided with ramps conforming to Section 1012.
4) Are service or freight elevators exempt?
Sometimes. Exception 3 can apply to certain service elevators not part of accessible egress/route, and Exception 4 applies to landings serving only freight elevators.
5) How does NFPA 72 relate to these systems?
IBC sets the building requirement; NFPA 72 provides the emergency communications framework. NFPA 72 (2022) includes Chapter 24 and Section 24.10 for two-way rescue assistance ECS.
6) What’s the biggest reason these systems fail plan review?
Two common causes are misapplying exceptions without documentation and using intercom-like hardware that doesn’t meet AHJ expectations for rescue assistance system performance and listing.
Conclusion: A Simple Compliance Strategy That Holds Up
If you want a clean path to approval, start with IBC 1009.8 and map every accessible floor above/below exit discharge to an elevator landing (or bank) location. Then decide whether you’ll cover rescue assistance communication at the elevator landing or at areas of refuge—but don’t leave gaps. Finally, coordinate early with the AHJ on the central control point, monitoring/dial-out, and NFPA 72 expectations for rescue assistance two-way ECS (often aligned with Chapter 24 / 24.10 and UL 2525 listing).
DAS/ERRCS basics are now required knowledge for fire/life-safety teams because modern buildings can seriously attenuate public safety radio signals. Concrete, steel, low-E glazing, underground parking, stairwells, and elevator cores routinely create “RF dead zones” where responders lose reliable radio comms right when coordination matters most.
This is a code-heavy, field-practical guide focused on what actually passes plan review and acceptance tests. We’ll break down the IFC Section 510 framework, how NFPA 1225IFC editions commonly reference NFPA 1221; NFPA 1221 has since been consolidated into NFPA 1225 (verify which standard your AHJ adopted) impacts design and documentation, how acceptance testing is commonly performed, how to plan 2-hour survivability for backbone pathways, how to handle grounding/bonding and rooftop donor antenna best practices using NEC concepts (Article 810), and how the top public-safety BDA/ERRCS manufacturers compare on reliability, cost, frequencies, support, and install complexity.
1) What ERRCS Must Do (Beyond “DAS in a Building”)
An Emergency Responder Radio Communication System (ERRCS) (also called ERCES, “public safety DAS,” or “BDA system”) is installed when in-building radio coverage is inadequate and the AHJ requires enhancement. A Distributed Antenna System (DAS) is a method for distributing RF throughout a structure. In the public-safety context, most implementations boil down to:
Donor antenna capturing the jurisdiction’s public-safety signal
BDA (bi-directional amplifier) amplifying uplink and downlink
Backbone distribution (coax and/or fiber with remotes)
Interior antennas delivering coverage to critical and general areas
Power + battery standby sized to code/AHJ
Monitoring/supervision to the fire alarm system
Two important “real life” points:
Coverage is not just a number. Some jurisdictions care only about signal strength; others care about intelligibility metrics (e.g., DAQ) or operational radios at specific frequencies/bands.
ERRCS is treated like life-safety infrastructure. It must be supervised, documented, and tested/maintained after turnover (IFC 510.4.2.5 Monitoring, IFC 510.7 Testing, IFC 510.6 Maintenance).
2) Code Framework: Where Requirements Come From
Important: Code section numbering and exact language can vary by edition and local amendments. Always verify your adopted edition (2015/2018/2021/2024/2025, etc.) and any city/county amendments. That said, the “core shape” of enforcement is widely consistent.
2.1 International Fire Code (IFC) Section 510
Most AHJ requirements stem from IFC Section 510, which establishes that buildings must have approved radio coverage for emergency responders within the building. When that coverage is not adequate, the AHJ can require an enhancement system (IFC 510.1 General, IFC 510.4 Coverage, IFC 510.4.2 System Design, IFC 510.4.2.5 Monitoring, IFC 510.5.4 Acceptance Testing, IFC 510.6 Maintenance).
Coverage targets commonly include:
95% coverage in general building areas (IFC 510.4.1 typically addresses minimum signal strength/coverage criteria)
99% coverage in critical areas designated by the fire code official (IFC 510.4.2 commonly addresses critical areas)
Critical areas vary by AHJ but often include stairwells, fire command/communications spaces, fire pump rooms, generator rooms, underground parking, and other spaces deemed essential for incident operations (IFC 510.4.2 Critical Areas).
2.2 International Building Code (IBC) cross-reference (varies by edition)
Many jurisdictions cross-reference emergency responder radio coverage in the building code, often pointing back to the fire code requirements. Depending on edition, you may see references like IBC 916.1 or similar language: emergency responder radio coverage shall be provided in accordance with the fire code requirements (IBC 916.1 General in editions where applicable).
2.3 NFPA 1225 (2022): Design, Records, and Testing Concepts
NFPA 1225 is widely referenced as the standard that addresses in-building emergency responder communications enhancement systems and related inspection/testing concepts. Many AHJs use it as the “how” behind the fire code “what,” particularly around documentation, inspection cadence, and system integrity (NFPA 1225, ERCES-related chapters; also see NFPA guidance discussing testing requirements and when systems are needed).
2.4 Fire Alarm Integration and Supervision
ERRCS supervision is routinely enforced as a life-safety function. IFC calls out monitoring requirements (IFC 510.4.2.5 Monitoring) including conditions that must annunciate trouble/supervisory. The AHJ often expects these to report through the building’s fire alarm system or an approved supervising station arrangement.
3) Diagram: End-to-End ERRCS Signal Path
Typical ERRCS signal flow from rooftop donor antenna through BDA and backbone distribution to interior antennas.
This is embedded SVG so it shows up in Blogger preview without any uploads.
4) Design Deep Dive: 2-Hour Survivability, Pathways, and “What AHJs Actually Mean”
One of the most common sources of rework is survivability. Many AHJs interpret survivability as: the backbone pathway must remain operational during the fire event long enough to support responder comms. This is commonly implemented as a 2-hour rated survivability strategy applied to key portions of the system (especially donor-to-headend and backbone risers).
4.1 Backbone vs Distribution (Design the “Trunk” Like Life Safety)
Backbone / Riser: the trunk feeding multiple floors or major zones. If this fails, large areas lose coverage.
Distribution: branch lines feeding local antenna groups. If one branch fails, the outage is localized.
Many AHJs focus survivability requirements more heavily on the backbone (and donor path) because it represents the highest-impact single points of failure.
4.2 Practical 2-Hour Survivability Methods
Always confirm what your AHJ accepts, but common accepted methods include:
Listed 2-hour fire-rated coax for donor and/or backbone paths
Routing backbone within a 2-hour rated shaft/enclosure consistent with building rating
Approved equivalent protection method (e.g., specific rated assemblies) where permitted
Design detail that matters: survivability is more than a note. You typically must show route, rated boundaries, penetrations, firestopping, and transition points (splices, splitters, remotes) and how each remains protected.
4.3 Where to Apply 2-Hour Protection (Most Common Pattern)
Donor antenna to head-end/BDA room pathway (high exposure + high criticality)
Vertical backbone risers feeding multiple floors
Backbone transition points (where trunk becomes branches) in rated enclosures if required
Power pathway survivability if locally required (some AHJs treat power similarly to backbone)
4.4 Survivability Checklist (Plan-Set Ready)
Label BACKBONE and DISTRIBUTION on drawings.
Show a 2-hour method per backbone segment (rated cable vs rated shaft route).
Detail firestopping at each penetration of rated barriers.
Show equipment room constraints (clearance, ventilation, labeling; and rating if required).
Show spare capacity and expansion approach where AHJ expects future frequency additions (IFC commonly anticipates modification/expansion language in some editions).
5) Grounding, Bonding, and Rooftop Donor Antenna Best Practices (NEC Article 810 Concepts)
Rooftop donor antennas introduce lightning exposure and potential differences across the coax shield, mounting hardware, and building grounding system. While your AHJ may not “inspect NEC Article 810” by name for ERRCS, your electrical inspector and best practice absolutely care. NEC Article 810 provides widely used grounding/bonding concepts for radio and television equipment and outdoor antennas (NEC 810.21 Bonding/Grounding Conductor concepts).
5.1 Donor Antenna Installation Best Practices
Mounting & wind loading: Use rated mounting hardware and verify structural attachment points.
Weatherproofing: Use drip loops, sealed connectors, and UV-rated materials. Corrosion and water ingress are silent performance killers.
Coax routing: Avoid sharp bends, maintain minimum bend radius, protect from abrasion, and label the donor feed clearly.
Lightning/surge protection: Use manufacturer-recommended protectors where applicable and coordinate grounding/bonding to avoid “floating” protection devices.
Bond the mast/mount to the building grounding electrode system using listed methods and appropriate conductor sizing practices (NEC 810.21 concepts).
Bond the coax shield at the building entry using a grounding block/entry panel approach, tied to the building grounding electrode system (NEC 810.21 concepts).
Keep bonds short and direct to reduce impedance. Long looping bonds behave badly during surges.
Avoid isolated grounds that create dangerous potential differences.
5.3 RF Best Practice: Donor Placement and Oscillation Avoidance
Oscillation is a frequent commissioning problem and is commonly called out as a monitored condition (IFC 510.4.2.5 Monitoring commonly lists oscillation for active RF devices). Design to prevent it by:
Maximizing physical separation between donor antenna and interior antennas
Using directional donor antennas when appropriate
Planning antenna patterns and attenuation to maintain isolation margins
Balancing amplifier gain conservatively and validating with field measurements
6) Monitoring & Fire Alarm Interface: What Needs to Annunciate
Monitoring is one of the most inspected elements because it’s easy to verify and directly tied to life safety. IFC 510.4.2.5 (Monitoring) commonly requires annunciation of multiple system trouble/supervisory conditions.
6.1 Commonly Required Supervisory Conditions
Exact lists vary by edition and AHJ, but a common enforcement set includes:
Active device failure (BDA, remotes) (IFC 510.4.2.5 Monitoring)
Low battery capacity threshold signaling (IFC 510.4.2.5 Monitoring commonly references 70% reduction threshold language in some editions)
Oscillation detection (IFC 510.4.2.5 Monitoring)
Failure of monitoring link to FACP (IFC 510.4.2.5 Monitoring)
6.2 Annunciation Labeling Best Practice (Make the Inspector Smile)
ERRCS AC Power Loss
ERRCS Battery/Charger Trouble
ERRCS Donor Antenna Fault
ERRCS BDA/Remote Fault
ERRCS Oscillation
ERRCS Supervisory Link Fault
Tip: Put a monitoring matrix in the plan set and the turnover binder: “ERRCS Trouble Point → Fire Alarm Input → Annunciation Text.” It prevents “we’ll label it later” chaos during acceptance.
Pre-Design Signal Strength Survey and Sweep Testing (Do We Need ERRCS?)
Before anyone specifies equipment or draws antenna dots, the first step is a baseline in-building radio coverage survey. This is often called a signal strength survey, RF sweep, or coverage walk test. The purpose is simple: determine whether the building already meets the AHJ’s radio coverage criteria or whether an enhancement system is required (IFC 510.4 Coverage; IFC 510.5.4 Acceptance Testing).
Important: Exact thresholds and test method vary by jurisdiction and code edition. Some AHJs focus on received signal strength (RSSI) in dBm; others use intelligibility measures (DAQ) and require agency radios or specific test equipment. Always obtain the AHJ’s test criteria in writing before final conclusions.
1) What Equipment Is Typically Used
Public safety test radio(s) or AHJ-approved subscriber units on the required bands (VHF, UHF, 700/800, etc.)
RF measurement tool (depends on AHJ): spectrum analyzer, scanning receiver, or radio service monitor capable of logging RSSI
Directional antenna (optional) for troubleshooting interference/weak donor signal
Floor plans (PDF or printed) to overlay grid boxes and note readings
Documentation template for grid readings, time stamps, frequency/band, and notes
2) Up-Front Survey Workflow (Step-by-Step)
The following approach is widely used because it produces defensible documentation and mirrors how many acceptance tests are structured.
Step A: Confirm test bands/frequencies. Obtain the public safety band(s) required by the AHJ and which agencies must be supported. Document them in the test header.
Step B: Establish a grid method. Overlay a grid on each floor plan. Grid size is AHJ-dependent. For a conceptual example, this article uses 20 grids on one floor.
Step C: Define test points in each grid. Most teams test at the approximate center of each grid box (or the AHJ-defined point). Keep the test height consistent (for example, handheld radio height at ~3–5 feet above finished floor). Document what you used.
Step D: Measure downlink and uplink (if required).
Downlink = signal received inside the building from the public safety system (what the responder hears).
Uplink = signal transmitted from inside the building back to the public safety system (what the dispatcher/helicopter/tower receives).
Some AHJs require both directions to pass; others focus on downlink plus functional talk-back validation.
Step E: Capture readings and notes. For each grid, record:
Step F: Identify critical areas separately. Stairwells, pump rooms, generator rooms, fire command centers, and other AHJ-defined critical areas often have higher compliance expectations (IFC 510.4.2 Critical Areas). Treat these as their own “mini test plans” even if they overlap grids.
Step G: Summarize results. Provide a pass-rate summary by floor and identify the failing zones. If failures exist, the survey results become the foundation for ERRCS design assumptions (IFC 510.4 Coverage).
3) Practical Tips That Prevent Bad Data
Pick consistent test conditions. Avoid “one reading in the hallway and the next behind a stair door.” Stay consistent or you’ll create false failures (or false passes).
Document the radio orientation and body position. Human bodies attenuate RF. If you test with the radio against your chest in one grid and overhead in another, your dataset becomes noisy.
Time-stamp your survey. If the AHJ asks later “when was this measured,” you have it.
Note construction status. Partitions, doors, and ceiling grid changes can dramatically affect results. “Shell only” testing can differ from final build-out.
Example: 20-Grid Sweep Test Documentation (With Sample Readings)
Below is a sample 20-grid floor plan overlay showing how readings can be documented. This is a visual example only. Your AHJ may require a different grid size, different metrics, or specific radio models (IFC 510.5.4 Acceptance Testing).
How to read this example: Each box is a grid area. The value shown is an example downlink reading in dBm. “PASS/FAIL” in this example is based on an illustrative threshold. Use your AHJ’s actual threshold and method.
Example of a 20-grid sweep test used to document in-building radio signal strength before ERRCS design.
Example Documentation Table (20 Grids)
This optional table format helps readers understand what the final survey log looks like.
Grid
Band/Freq
Reading (dBm)
Pass/Fail
Notes
A1
UHF Ch X
-68
PASS
Open office
A2
UHF Ch X
-72
PASS
Corridor
A3
UHF Ch X
-79
PASS
Near lobby
A4
UHF Ch X
-92
FAIL
Near stairwell door
A5
UHF Ch X
-96
FAIL
Behind elevator core
B1
UHF Ch X
-70
PASS
Tenant space
B2
UHF Ch X
-75
PASS
Tenant space
B3
UHF Ch X
-90
FAIL
Mechanical closet wall
B4
UHF Ch X
-94
FAIL
Deep interior core
B5
UHF Ch X
-98
FAIL
Rear storage area
C1
UHF Ch X
-73
PASS
Open office
C2
UHF Ch X
-77
PASS
Open office
C3
UHF Ch X
-82
PASS
Conference rooms
C4
UHF Ch X
-91
FAIL
Core wall shadow
C5
UHF Ch X
-95
FAIL
Near stairwell
D1
UHF Ch X
-69
PASS
Lobby edge
D2
UHF Ch X
-74
PASS
Corridor
D3
UHF Ch X
-80
PASS
Tenant space
D4
UHF Ch X
-84
PASS
Tenant space
D5
UHF Ch X
-93
FAIL
Deep interior corner
How readers should use this: This is exactly how sweep testing results are commonly presented: a floor plan grid overlay with values, plus a log table. If enough grids fail to meet the AHJ’s criteria, the building is a strong candidate for ERRCS requirements and design (IFC 510.4 Coverage; IFC 510.5.4 Acceptance Testing).
7) Acceptance Testing: Grid Testing, Critical Areas, and Documentation
Acceptance testing is where systems pass or fail publicly. IFC 510.5.3 (Acceptance Testing) commonly requires verification that the installed system meets coverage and performance targets. NFPA guidance also emphasizes that testing is used to determine whether a system is needed and whether it performs after installation.
7.1 Grid Testing: Typical Workflow
Divide each floor into test grids (size and method vary by AHJ).
Test at grid points using AHJ-approved radios and frequencies.
Confirm general area pass rate (commonly 95% target) (IFC 510.4 Coverage).
Verify labeling: donor feed, backbone riser, zone splitters, antenna IDs.
Verify equipment room ventilation/clearance and signage.
9.3 Acceptance Test Checklist
Perform grid testing per AHJ process and verify pass rates (IFC 510.5.4 Acceptance Testing).
Test critical areas separately and document results (IFC 510.4.2).
Demonstrate supervision points to the fire alarm annunciation (IFC 510.4.2.5 Monitoring).
Turn over full documentation package: as-builts, test report, maintenance plan (IFC 510.6 Maintenance).
9.4 Annual Inspection Checklist
Verify supervision signals function and annunciation matches plan (IFC 510.6).
Inspect donor antenna integrity, mounts, weatherproofing, and coax entry bonding.
Verify battery/charger condition and standby expectations per AHJ.
Perform coverage verification as required (IFC 510.6 Maintenance; AHJ requirements).
Update records and keep them available for inspection.
10) Top 3 Public Safety BDA / UHF-VHF / 700-800 ERRCS Manufacturers (Pros & Cons)
Reality check: “Best” depends on your jurisdiction’s frequency bands, AHJ familiarity, and the quality of the integrator. A great product poorly commissioned will fail; a mid-tier product expertly designed can pass consistently.
10.1 Honeywell (including Fiplex portfolio in many markets)
Reliability: Often regarded as strong in life-safety ecosystems with good AHJ recognition in many regions.
Customer support: Typically solid documentation and channel support through established distribution networks.
Ease of installation: Generally straightforward, but still requires RF engineering discipline for gain structure and isolation.
Frequencies/bands: Common public safety band support is available by model; confirm your VHF/UHF/700/800 needs before spec.
Cost: Often higher upfront, sometimes justified by ecosystem maturity and documentation quality.
10.2 Westell
Reliability: Widely deployed in public safety BDA applications; model selection and proper commissioning are key.
Customer support: Generally good, but “how good” can be region/distributor dependent.
Ease of installation: Often considered installer-friendly for common deployments.
Frequencies/bands: Model dependent; verify exact band plan (UHF vs 700/800 vs multi-band solutions).
Cost: Often competitive mid-market.
10.3 ADRF (public safety portfolio) or Comba Telecom (market-dependent)
Pick based on what your local ecosystem supports. Some markets lean ADRF; others lean Comba, depending on integrator certifications and AHJ familiarity.
Reliability: Strong track record when properly designed and tuned.
Customer support: Can be excellent, especially when paired with trained integrators.
Ease of installation: Solid hardware, but commissioning discipline matters more (gain, isolation, oscillation avoidance).
Frequencies/bands: Often flexible configurations; confirm exact requirements and future expandability.
Cost: Often attractive for scalable designs and multi-zone architecture.
Selection tip: If your AHJ is strict on monitoring and documentation, prioritize the vendor with the clearest monitoring outputs and the best “acceptance-ready” paperwork alignment to IFC 510.4.2.5 and IFC 510.5.3.
11) Common Failure Modes and How to Engineer Them Out
11.1 Oscillation and Feedback
Oscillation is a top commissioning failure. It can occur when donor and interior antenna systems couple and create a feedback loop. Design for isolation margins, use directional antennas appropriately, and commission conservatively (IFC 510.4.2.5 Monitoring often requires oscillation supervision).
11.2 “Survivability by Note” (Not by Design)
Plan notes alone don’t pass scrutiny. Survivability needs route clarity, rated boundary coordination, penetration/firestopping details, and transition point protection. If it’s not on the drawings, it tends to become “field improvisation,” and that’s where systems fail.
11.3 Supervision That’s Incomplete or Poorly Labeled
Another common fail: you have the dry contacts, but they’re not mapped, labeled, or demonstrated. Build the monitoring matrix early and test the exact annunciation text during acceptance (IFC 510.4.2.5 Monitoring).
12) FAQ (5)
12.1 When is an ERRCS required?
Typically when AHJ testing shows the building does not meet required in-building emergency responder radio coverage per the adopted code (commonly IFC 510.4 Coverage, IFC 510.5.4 Acceptance Testing).
12.2 Do stairwells always have to pass at a higher rate?
Many AHJs treat stairwells as critical areas and require higher pass rates (IFC 510.4.2 Critical Areas). Confirm the AHJ’s critical-area list.
12.3 What does “2-hour survivability” mean for ERRCS?
In many jurisdictions, it means key backbone pathways (and often donor-to-headend) must remain operational during a fire exposure period. Implementation methods vary and must be AHJ-approved.
12.4 Why is donor antenna grounding/bonding such a focus?
Because rooftop antennas are lightning-exposed and can create dangerous potential differences if not bonded correctly. NEC Article 810 provides grounding/bonding concepts commonly applied to antenna systems (NEC 810.21).
12.5 Can systems be expanded later if frequencies change?
Many code frameworks and AHJ policies expect systems to be capable of modification/expansion when agencies add/change frequencies. This is a design consideration for equipment selection and architecture.
Conclusion
DAS/ERRCS basics are not “just add antennas.” They are supervised, documented, and performance-verified life-safety systems. If you design from the code outward (IFC 510.4 Coverage, IFC 510.4.2.5 Monitoring, IFC 510.5.4 Acceptance Testing, IFC 510.6 Maintenance), engineer survivable backbone pathways, install and bond rooftop donor antennas using NEC Article 810 concepts, and deliver clean acceptance documentation, you dramatically increase the likelihood of first-pass approval and long-term reliability.
Next step: get the AHJ’s acceptance test method and required frequency list, then build your design around survivability + supervision from day one. That’s how you avoid expensive RF rework late in the project.
References (for Readers and Plan-Set Validation)
IFC Section 510 resources and excerpts (example PDF): https://callmc.com/wp-content/uploads/2021/10/IFC_510_Sheet-1.pdf
NFPA guidance on when ERCES is needed and testing concepts: https://www.nfpa.org/news-blogs-and-articles/blogs/2024/03/04/when-emergency-responder-communication-enhancement-systems-are-needed
NFPA 1225 overview (standard development page): https://www.nfpa.org/codes-and-standards/nfpa-1225-standard-development/1225
NFPA 1225 Chapter excerpt example (publicly posted): https://oci.georgia.gov/document/document/nfpa-1225-chapter-18/download
NEC Article 810 grounding concepts (summary/education): https://www.ecmweb.com/national-electrical-code/code-basics/article/20891084/article-810-radio-and-television-equipment
NEC Article 810.21 bonding/grounding conductor excerpt example: https://www.mikeholt.com/files/PDF/20BG_810.21.pdf
Example jurisdiction code library referencing NFPA 1225 for ERRCS: https://codelibrary.amlegal.com/codes/san_francisco/latest/sf_fire/0-0-0-48210
