Print Page   |   Contact Us   |   Your Cart   |   Sign In   |   Register
Community Search
Sign In to Your Profile


Forgot your password?

Haven't registered yet?

Latest News
Calendar

10/3/2016
ESA of Virginia (ESA of VA) Golf Tournament

10/5/2016
WAESA Fire & Security Alarm Symposium

10/7/2016 » 10/8/2016
First Annual ESA of Missouri Conference

10/8/2016
ESA of Missouri Annual Meeting

ESA News
Blog Home All Blogs
Search all posts for:   

 

View all (364) posts »
 

Standards Update: NITMAM Submittal Deadline for NFPA 731 is Aug. 23

Posted By Administration, Tuesday, August 13, 2013
Updated: Monday, August 12, 2013
The ESA Standards and Fire/Life Safety Committee has had a busy year ensuring that the electronic security industry’s interests are represented in the various standard and code-making engines. In an effort to keep the membership informed, below is a list of areas we are focused on and need your help with.

NFPA 731: Deadline for NITMAM Submittal is Aug. 23

The committee is currently keeping an eye on NFPA 731 – Premise Security, regarding battery backup for burglary systems. The minimum backup requirement is being changed from 4 hours to 24 hours. Based on UL requirements, commercial systems need to have 4 hour battery backups. Currently the committee recommends keeping with the UL requirement.

IMPORTANT: Document 731 is going to close for NITMAM submittal on Friday, Aug. 23, 2013. If you have any concerns you want to be addressed by the Technical Committee, you will need to submit a Public Input/Comment before that deadline.

To submit a Public Input/Public Comment, please log in at www.NFPA.org; select the Document Information Page for which you wish to submit Public Input/Public Comment; and click "Submit Public Input online" or 'Submit Public Comment online."

If you have any additional questions regarding NFPA 731, please contact Michelle Yungblut at Michelle.Yungblut@ESAweb.org.

Volunteers Needed for NFPA Technical Committees

We need volunteers to represent ESA as a primary or alternate on the following NFPA technical Committees:

  • NFPA 70 - NEC-P03 — Code-Making Panel 03
  • NFPA 101 - SAF-AAC — Technical Correlating Committee on Safety of Life
  • NFPA 72 - SIG-AAC — Signaling Systems for the Protection of Life and Property
  • NFPA 720 - SIG-CAR — Carbon Monoxide Detection
  • NFPA 72 - SIG-ECS — Emergency Communication Systems
  • NFPA 72 - SIG-FUN — Fundamentals of Fire Alarm Systems
  • NFPA 72 - SIG-HOU — Single and Multiple Station Alarms and Household Fire Alarm Systems
  • NFPA 72 - SIG-IDS — Initiating Devices for Fire Alarm Systems
  • NFPA 72 - SIG-NAS — Notification Appliances for Fire Alarm Systems
  • NFPA 72 - SIG-PRO — Protected Premises Fire Alarm Systems
  • NFPA 72 - SIG-SSS — Supervising Station Fire Alarm Systems
  • NFPA 72 - SIG-TMS — Testing and Maintenance of Fire Alarm Systems

If you are interested in serving as an ESA representative, please contact Vice President of Training & Certification Michelle Yungblut at Michelle.Yungblut@ESAweb.org.

Update on the Status of NFPA 730

For now, NFPA 730 will remain a guide. Thanks to everyone for your support; we will continue to monitor this.

Other Issues Currently Being Monitored

The committee is keeping watch on proposals that involve wireless devices being able to send panics to 911 dispatches. If there is going to be code developed, we will ensure we are involved to ensure they do not have adverse effects on the industry or the safety of the public

Also, the committee is monitoring the progress of NFPA 72 Chapter 26 – Supervising Station Fire Alarm Systems. The proposal was made for dialer timer test moving from every 24 hours to every 6 hours. We do not think this is a good idea for the industry, since it will cause undue burdens and provide few benefits. We have representatives on the committee, and are keeping an eye on this and have representatives on the committee. We do not think this is a good idea for the industry as it will cause undue burdens with little benefits.

Tags:  code  NFPA 731  standards 

Permalink | Comments (0)