With the 2025 edition of NFPA 72 set to take effect in many jurisdictions starting January 2026, contractors are inquiring about how the updates relate to NFPA 1225, the main standard for Emergency Responder Communication Enhancement Systems (ERCES).
Because ERCES sits at the intersection of fire alarm, electrical, and RF engineering, the two standards are designed to work together—each covering different parts of the system.
This blog offers a technically neutral overview of how NFPA 72–2025 and NFPA 1225 align, what the updates mean for supervision, survivability, cybersecurity, and documentation, and how these expectations may impact project coordination moving forward.
1. Understanding the Two Standards: Different Roles, One System
NFPA 1225 (Current ERCES Standard) Covers:
- RF design and engineering
- signal strength and DAQ requirements
- antenna placement and donor link parameters
- pathway isolation
- system performance testing and acceptance
- ERCES equipment, enclosures, power, and RF performance metrics
In short, NFPA 1225 defines how the ERCES must function as a radio system.
NFPA 72 Covers:
- how ERCES interfaces with the fire alarm system
- supervision and annunciation rules
- pathway survivability and protection
- control, reset, and override functions
- circuit integrity and fault monitoring
- cybersecurity and remote access requirements
- documentation and integrated system testing
In short, NFPA 72 defines how ERCES must be supervised, monitored, and controlled within the life-safety system.
And most importantly: NFPA 1225 explicitly defers supervision and fault reporting to NFPA 72. This is written directly into Section 18.14 of 1225–2025.
2. Supervision Requirements: Where NFPA 1225 Points Directly to NFPA 72
NFPA 1225 requires ERCES fault supervision to be performed according to NFPA 72 rules. Two key excerpts:
NFPA 1225–2025, 18.14.1.1:
“Supervisory signals… shall be annunciated by the fire alarm system in accordance with NFPA 72.”
NFPA 1225–2025, 18.14.1.2(1):
“Monitoring for integrity of the system shall comply with Chapter 10 of NFPA 72.”
This means AHJs may begin expecting:
- supervised inputs for fault conditions
- ≤200-second fault notification
- UL 864–listed interface devices
- clear labeling (“ERCES Fault,” “Donor Antenna Fault,” etc.)
Practical effect: NFPA 72–2025 clarifies and strengthens what NFPA 1225 already requires.
3. Survivability: Aligning ERCES Pathways With NFPA 72 Chapter 10
NFPA 1225 defines survivability concepts for ERCES equipment, but NFPA 72 governs the survivability of the pathways connecting ERCES to the FACP.
NFPA 72–2025 clarifies:
- when Class A or Class B pathways are needed
- how risers and horizontal runs must be protected
- labeling and documentation requirements
While some AHJs already enforced these principles, the revised 72 edition provides them with clearer authority to implement survivability rules for ERCES interfaces.
4. Cybersecurity: NFPA 72–2025 Makes Enforcement Possible
NFPA 1225 references operational security, but NFPA 72–2025 is where cybersecurity becomes enforceable.
For ERCES systems with remote access, the standard now requires:
- unique credentials (no default logins)
- role-based access
- network separation from public/LAN networks
- audit logging of system access
- secure methods for remote reset (VPN, firewall, etc.)
Most modern BDAs support these features, but NFPA 72–2025 now formalizes what AHJs can request during review.
5. Reset & Control Functions: Where 1225 and 72 Intersect
If an ERCES system provides:
- remote reset
- remote status
- web dashboard access
…then NFPA 72 Chapter 11 applies, and NFPA 1225 requires compliance with it.
This means:
- secure, authenticated access
- no open public network connections
- documented control functions
- coordination with the fire alarm contractor
6. Documentation, Testing, and Coordination Expectations
NFPA 1225 outlines ERCES testing and acceptance criteria.
NFPA 72 outlines documentation, supervised testing, and integrated system tests.
Together, they imply coordinated responsibilities among:
- ERCES integrators
- fire alarm contractors
- GCs/electrical contractors
- AHJs
Expect AHJs to increasingly demand:
- clear interface diagrams
- wiring schematics
- survivability routing
- sequence-of-operations documentation
- joint acceptance testing
These are not new concepts—NFPA 72–2025 makes them more explicit.
What Contractors Should Expect Going Forward
While enforcement varies by jurisdiction, the standards continue to tighten their alignment.
Contractors should expect:
- more consistent supervision and survivability requests
- clearer expectations on ERCES-to-FACP interfaces
- increasing emphasis on secure remote access
- better-defined project documentation requirements
- more coordination between fire alarm contractors & ERCES installers
This is evolutionary, not revolutionary—but understanding the relationship between NFPA 72 and NFPA 1225 will reduce rework and help projects pass review smoothly.
How We Support ERCES Integration
Our firm specializes exclusively in ERCES system design, testing, and documentation.
We assist with:
- NFPA 1225-compliant RF system design
- NFPA 72-compliant interface drawings
- survivability and pathway routing
- AHJ plan-review support
- acceptance testing and documentation
📞 415-738-6895
🌐 www.in-buildingwireless.com
📧 [email protected]