During a Q&A at a recent conference, I was asked, “Is the NFPA 72, National Fire Alarm and Signaling Code, more difficult to use today than when it was first introduced in 1993?”
For context, in 1993, all the NFPA 72 related standards were combined into one “code.” The technical committee felt that by combining the various standards booklets, it would be easier to use.
NFPA membership voted in June on whether to adopt the proposed 2025 edition of NFPA 72.
Pages and pages
The question of how to make it easier for users certainly is valid. The number of pages from the seven earlier standards combined increased from approximately 120 to 420 pages!
With every edition, each technical committee tries to ensure its chapter is up to date and user-friendly.
Based on the number of pages alone, the proposed 2025 edition of the code has become more difficult to use. But the code should be judged by its content.
Each edition has included guidance on new technology and how to integrate existing systems with it.
By participating in the code development process, I realized we have not done a good job of keeping the requirements in a simple format to read and understand the reasoning behind them.
What should a user know?
Picking up a copy of NFPA 72 can be overwhelming. You can’t just read one chapter and know everything you have to do to ensure a code-compliant installation. Obviously, the code book is not an exciting spy novel. However, if you expect to design, install or approve a fire alarm system, you must have a good working knowledge of the requirements outlined in each chapter.
Each chapter references requirements from other chapters. But it will also be apparent that for some installations, only one or two chapters will top the list of what will be needed.
For example, if you only work on one- and two-family residential projects, focus on Chapter 29, Single - and Multiple-Station Alarms and Household Signaling Systems. Rarely does a homeowner ask you to install a complete commercial fire alarm system. So, the requirements for these occupancies are the easiest to comply with. Section 29.1.3 shows how specialized this chapter is: “The requirements of chapters 7, 10, 12, 14, 17, 18, 21, 23, 24, 26, and 27 shall not apply unless otherwise noted.”
Whatever your specialty, you need a working knowledge of the relevant chapters as they apply.
Where to start
Here is a simple chapter checklist for a code-compliant, nonvoice and nonhigh-rise “plain vanilla” fire alarm system:
- Chapter 23, Protected Premises Alarm and Signaling Systems
- Chapter 10, Fundamentals
- Chapter 12, Circuits and Pathways
- Chapter 17, Initiating Devices
- Chapter 18, Notification Appliances
- Chapter 21, Emergency Control Function Interfaces
- Chapter 7, Documentation
- Chapter 14, Inspection, Testing, and Maintenance
An asterisk next to a code requirement takes you to Annex A, which has informational material providing further guidance for compliance.
Starting in the order above will “walk” you through the requirements needed for a simple fire alarm system.
Chapter 10, in Section 10.2, spells out what we expect the fire alarm system to do: “The purpose of fire alarm and signaling systems shall be primarily to provide notification of alarm, supervisory, and trouble conditions; to alert the occupants; to summon aid; and [where applicable] to control emergency control functions.”
Obviously, if there are no emergency control function interfaces, then skip Chapter 21.
Complying with the NFPA 72 requirements for a fire alarm system design or installation is not optional. The requirements contained in the code are to help ensure an acceptable level of reliability for all fire alarm systems. Consistent compliance will help to ensure your installations also are profitable. Don’t let the increased number of pages in the code deter you from using it.
stock.adobe.com / chaynam
About The Author
MOORE, a licensed fire protection engineer, was a principal member and chair of NFPA 72, Chapter 24, NFPA 909 and NFPA 914. He is president of the Fire Protection Alliance in Jamestown, R.I. Reach him at [email protected].