<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>LifeSafety Magazine &#187; NFPA</title>
	<atom:link href="http://www.systemsensor.com/lifesafety/category/firelife-safety-codes/nfpa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.systemsensor.com/lifesafety</link>
	<description>quarterly information from the leader in notification and detection</description>
	<lastBuildDate>Tue, 24 Jan 2012 16:39:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>State and Municipal Code Adoption Update</title>
		<link>http://www.systemsensor.com/lifesafety/2011/11/codes-and-legislation-state-and-municipal-code-adoption-update/</link>
		<comments>http://www.systemsensor.com/lifesafety/2011/11/codes-and-legislation-state-and-municipal-code-adoption-update/#comments</comments>
		<pubDate>Thu, 17 Nov 2011 19:02:28 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[Carbon Monoxide Detection]]></category>
		<category><![CDATA[Legislation]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Winter 2011]]></category>
		<category><![CDATA[Carbon monoxide]]></category>
		<category><![CDATA[codes]]></category>
		<category><![CDATA[legislation]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/lifesafety/?p=2815</guid>
		<description><![CDATA[The New Mexico Construction Industries Division (CID) has adopted the 2009 International Residential Code (IRC) without amendments to the CO and smoke detection sections.]]></description>
			<content:encoded><![CDATA[<p>The <strong>New Mexico</strong> Construction Industries Division (CID) has adopted the 2009 International Residential Code (IRC) without amendments to the CO and smoke detection sections. That means CO detection is required to be installed in newly constructed one- and two-family dwellings and townhouses not more than three stories that contain a fuel-fire appliance or an attached garage. The CO alarms shall be installed outside of each separate sleeping area in the immediate vicinity of the bedrooms. In addition, the <strong>West Virginia</strong> State Fire Commission has adopted the 2009 IRC without amendments to the smoke detection section.</p>
<p>With New Mexico and West Virginia adopting the 2009 IRC, household fire alarm systems using system-connected smoke detectors will be permitted to be installed as a primary form of smoke protection if the system is owned by the homeowner as a permanent fixture and installed in accordance with NFPA 72<sup>®</sup>. In the previous edition (2006) of the IRC, a provision prohibited system-connected smoke detectors from being installed as a primary form of smoke protection.</p>
<p>The state of <strong>Oklahoma</strong> has required CO detection to be installed in child day-care occupancies since 2000. In July, the Uniform Building Code Commission officially adopted the 2009 IRC with modifications. The modifications are:</p>
<ul>
<li>CO detection is not required within the dwelling unit if the attached garage has a sealed door between the residence and the garage and no fuel-burning appliances are in the residence.</li>
<li>The household fire alarm system requirements in R313.2 and R313.2.1 were moved from the body of the code to the annex.</li>
</ul>
<p>In <strong>Massachusetts</strong>, the Board of Fire Prevention Regulations (BFPR) has suspended all current fire code (527 CMR) committee meetings, including 527 CMR 31, because it is in the process of adopting NFPA 1, Fire Code, for the next edition of the state fire code.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2011/11/codes-and-legislation-state-and-municipal-code-adoption-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Code Speaks Louder About Intelligibility</title>
		<link>http://www.systemsensor.com/lifesafety/2011/05/code-speaks-louder-about-intelligibility/</link>
		<comments>http://www.systemsensor.com/lifesafety/2011/05/code-speaks-louder-about-intelligibility/#comments</comments>
		<pubDate>Thu, 19 May 2011 17:18:33 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[FIRE/LIFE SAFETY CODES]]></category>
		<category><![CDATA[Intelligent Detection]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Summer 2011]]></category>
		<category><![CDATA[A/V Notification]]></category>
		<category><![CDATA[intelligibility]]></category>
		<category><![CDATA[Speakers and Strobes]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/lifesafety/?p=2516</guid>
		<description><![CDATA[NFPA 72-2010 refines and more carefully defines the concept of intelligibility.]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.systemsensor.com/lifesafety/wp-content/uploads/2011/05/codes.png" alt="" title="NFPA 72-2010 refines and more carefully defines the concept of intelligibility." width="355" height="273" class="alignright size-full wp-image-2571" /><em>NFPA 72-2010 refines and more carefully defines the concept of intelligibility.</em></p>
<p>NFPA 72-2010 code focuses on intelligibility and the need for voice evacuation systems to provide alerts with information that is audible and understandable. It defines <em>intelligibility</em> as the quality or condition of being intelligible (3.3.124) and <em>intelligible </em>as capable of being understood, comprehensible, clear (3.3.126). The code also adds a key term, ADS, that helps to clarify intelligibility requirements.</p>
<p>Acoustically Distinguishable Space (ADS) is an emergency communication system (ECS) notification zone, or subdivision thereof, that might be an enclosed or otherwise physically defined space, or that might be distinguished from other spaces due to acoustical, environmental, or use characteristics, such as reverberation time and ambient sound pressure level (3.3.2).</p>
<p>Establishing ADSs is foundational to planning an intelligible system. An ADS is any space that can or cannot have intelligibility. The ADS needs to be determined at the beginning of the project.</p>
<p>In Chapter 18 – Notification Appliances, NFPA 72-2010 states that within the ADS, where intelligibility is required, voice systems shall reproduce prerecorded, synthesized, or live messages with voice intelligibility (18.4.10). In each of these spaces, measuring for intelligibility may or may not be required.</p>
<p>ADSs shall be determined by the designer during the planning and design of all ECS (18.4.10.1). Each ADS shall be identified as requiring or not requiring intelligibility (18.4.10.2). Where an ADS is required by the authority having jurisdiction, ADS assignments shall be submitted for review and approval (18.4.10.3).</p>
<p>Chapter 24 – Emergency Communication System provides requirements for designing an intelligible voice evacuation system for an ECS. The speaker layout of the system shall be designed to ensure intelligibility and audibility; intelligibility shall first be determined by ensuring that all areas in the building have the required level of audibility; and the design shall incorporate speaker placement to provide intelligibility (24.4.1.2.2.1).</p>
<p>To meet NFPA requirements, the following is needed: the average ambient background noise level of the area; room characteristics such as length, width, and height of the ceiling and reflectivity of the surfaces in the room; and the coverage angle or polar plot of the speaker.</p>
<p>Annex D provides guidance on the planning, design, installation, and testing of voice systems. The annex also contains recommendations for testing intelligibility methods and requirements for testing.</p>
<p>When testing intelligibility, Annex D.2.4.1 recommends that 90 percent of all measurements in an ADS meet required intelligibility scores to be considered acceptable. These scores fall on the lower end of the intelligibility scale: a measured Speech Transmission Index scale (STI) of not less than 0.45 (0.65 CIS – Common Intelligibility Scale) or an average STI of not less than 0.50 (0.70 CIS).</p>
<p>Designing a system to meet current intelligibility requirements can be challenging because of the many factors that influence intelligibility, such as room dimensions, building materials, ambient sound, and usage. However, the NFPA code has been designed to limit the complexity of these systems by minimizing the potential for over-design. Therefore, the best approach is to be familiar with NFPA requirements and definitions before attempting to design a voice evacuation system for intelligibility.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2011/05/code-speaks-louder-about-intelligibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NFPA Standards Specifically Cover IT Equipment, Telecom</title>
		<link>http://www.systemsensor.com/lifesafety/2011/05/nfpa-standards-specifically-cover-it-equipment-telecom/</link>
		<comments>http://www.systemsensor.com/lifesafety/2011/05/nfpa-standards-specifically-cover-it-equipment-telecom/#comments</comments>
		<pubDate>Thu, 19 May 2011 17:18:27 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[Mission Critical]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Q & A : Ask the Expert]]></category>
		<category><![CDATA[Summer 2011]]></category>
		<category><![CDATA[fire safety]]></category>
		<category><![CDATA[mission critical]]></category>
		<category><![CDATA[Q&A]]></category>
		<category><![CDATA[telecom]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/lifesafety/?p=2505</guid>
		<description><![CDATA[Jonathan R. Hart, Associate Fire Protection Engineer with the National Fire Protection Association, is responsible for documents addressing information technology equipment, telecommunication facilities, wet and dry chemical extinguishing systems, explosion protection, commercial cooking systems, fire safety and emergency symbols, and water mist fire protection systems. Hart holds a B.S. degree in Mechanical Engineering from Worcester Polytechnic Institute (WPI) and is finishing work toward an M.S. degree in Fire Protection Engineering.]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.systemsensor.com/lifesafety/wp-content/uploads/2011/05/ask.jpg" alt="" title="ASK THE EXPERT By Jonathan R. Hart" width="454" height="537" class="alignright size-full wp-image-2576" /><strong>ASK THE</strong> EXPERT <strong>By Jonathan</strong> R. Hart</p>
<p>Jonathan R. Hart, Associate Fire Protection Engineer with the National Fire Protection Association, is responsible for documents addressing information technology equipment, telecommunication facilities, wet and dry chemical extinguishing systems, explosion protection, commercial cooking systems, fire safety and emergency symbols, and water mist fire protection systems. Hart holds a B.S. degree in Mechanical Engineering from Worcester Polytechnic Institute (WPI) and is finishing work toward an M.S. degree in Fire Protection Engineering.</p>
<p><strong>What fire and life safety codes relate to a mission-critical facility?</strong></p>
<p>NFPA 75, <em>Standard for the Protection of Information Technology (IT) Information Equipment</em>, and NFPA 76, <em>Standard for the Fire Protection of Telecommunications Facilities</em>, are the standards that pertain specifically to the protection of IT equipment, IT equipment areas, and telecom facilities. The rest of the facility will be designed to the applicable codes and standards for hazards other than fire and life safety.</p>
<p>The purpose of NFPA 75 is to set forth the minimum requirements for the protection of IT equipment and IT equipment areas from damage by fire or its associated effects, namely smoke corrosion, heat, and water.</p>
<p>Chapter 4 of the standard addresses Risk Consideration. It states in section 4.1 that “the following factors shall be considered in determination of the need for protecting the environment, equipment, function, programming, records, and supplies: (1) Life safety aspects of the function (e.g., process controls, air traffic controls), (2) Fire threat of the installation to occupants or exposed property, (3) Economic loss from the loss of function or loss of records, (4) Economic loss from value of the equipment, (5) Regulatory impact, and (6) Reputation impact.”</p>
<p>The following chapters address building construction, materials and equipment permitted in the IT equipment area, the construction of IT equipment, fire protection and detection equipment, records kept or stored in IT equipment rooms, utilities, and finally, emergency and recovery procedures.</p>
<p>NFPA 76 provides the requirements for fire protection of telecom facilities where telecom services such as telephone (landline, wireless) transmission, data transmission, voice-over Internet protocol (VoIP) transmission, and video transmission are rendered to the public. Telecom facilities include signal-processing equipment areas, cable entrance facility areas, power areas, main distribution frame areas, standby engine areas used to run standby power, technical support areas, administrative areas, and building services and support areas occupied by a telecom service provider.</p>
<p>The purpose of the standard is to provide a reasonable level of fire protection in telecom facilities, to provide a reasonable level of life safety for the occupants, and to protect equipment and service continuity. NFPA 76 is intended to avoid requirements that could involve unnecessary complications for or interference with the normal use, occupancy, and operations of telecom facilities and equipment.</p>
<p>Chapter 4 of this standard also addresses Risk Considerations. Section 4.1 Risk Factors reads:</p>
<p><em>Fire protection programs for telecommunications facilities shall be determined based on an evaluation of the risks and hazards associated with the site and services provided from the facility and the business continuity planning and disaster restoration capabilities of the telecommunications service provider specific to the site.</em></p>
<p><em>4.1.1 Fire protection programs shall be established with consideration given to the following factors:</em></p>
<p><em>(1) Exposure threat to facility occupants, the general public, and exposed property from a fire occurring at, adjacent to, or within the facility.</em></p>
<p><em>(2) The importance of telecommunications service continuity in supporting public safety through emergency communications (such as 911), national defense communications requirements, video transmission of critical medical operations, and other vital data.</em></p>
<p><em>(3) Methods employed by a service provider, as part of a risk management or business continuity strategy, that allow service to remain viable during and after an event or to be replaced or restored within a reasonable period post-event.</em></p>
<p><em>(4) The potential for a given protection strategy to result in a service disruption or inhibit the ability of the service provider to restore service in a timely manner post-event.</em></p>
<p>Section 4.2 of the standard continues with this method of characterizing the risk considerations in order to provide the most suitable design.</p>
<p>The following three chapters address performance-based design approaches, prescriptive-based design approaches, and redundant-or-replacement-based design approaches, respectively. The subsequent chapters detail the requirements for fire protection elements, fire prevention, pre-fire planning, damage control, and emergency recovery.</p>
<blockquote><p>“If you think of how many of our <strong>work and personal records, everyday use files and information</strong> are accessible online through centralized data repositories, you can quickly see the importance of NFPA 75.”<br /> <small>— <strong>Jonathan R. Hart</strong>, Associate Fire Protection Engineer, NFPA</small></p></blockquote>
<p><strong>Please explain the significance of NFPA 75 and 76.</strong></p>
<p>These documents have and continue to become more and more important as society grows reliant on what these documents are designed to protect. If you think of how many of our work and personal records, everyday use files and information are accessible online through centralized data repositories, you can quickly see the importance of NFPA 75. Likewise, information sent via telephone, Internet and similar transmission methods bring to bear the need to keep the routes that information travels up and running, which is a main goal of NFPA 76.</p>
<p>A small sampling of what is protected by NFPA 75 and NFPA 76 includes data storage/retrieval systems, ranging from criminal and medical records, financial records and transactions, insurance and legal records, and registration databases. Data processing systems are protected, including background checks, prescription compatibility, weather modeling, and defense systems, among other critical information. Data communications that are protected include wired-line, wireless (GSM, WiFi, etc.), satellite, radio, Internet, cable, and air traffic control.</p>
<p><strong>What are common elements of these standards that overlap with mission-critical facilities?</strong></p>
<p>Both NFPA 75 and 76 contain a Chapter 4 titled “Risk Considerations,” as stated above. These risk considerations employ an analysis of the risk factors involved both from a fire as well as from an accidental failure of the protection strategies. The overall design of these facilities is required to consider such risks and the total impact of downtime.</p>
<p>In addition, each of these standards requires the facilities to have an emergency fire plan, a damage control plan, and emergency recovery procedures.</p>
<p><strong>How do the standards apply to different areas within a mission-critical facility?</strong></p>
<p>NFPA 75 only applies to the protection of IT equipment and IT equipment areas. The rest of the facility will be designed to the applicable codes and standards.</p>
<p>NFPA 76 simply requires that telecom facilities be separated from the rest of the building by two-hour fire resistance-rated partitions. The standard contains additional conditions for telecom facilities housed in multiple tenant buildings that require either specific building construction types AND require automatic suppression, or limit them to one story.</p>
<p><strong>How do the standards address instances that go beyond traditional fire detection?</strong></p>
<p>NFPA 75 requires the installation of automatic detection equipment to provide early warning of fire. This needs to be a listed smoke detection-type system installed and maintained in accordance with NFPA 72<sup>&reg;</sup>, National Fire Alarm and Signaling Code. The automatic detection systems are required to be located at ceiling level throughout the IT equipment area, below raised floors containing cables, and above suspended ceilings that recirculate air.</p>
<p>NFPA 76 requires Very Early Warning Fire Detection (VEWFD) for rooms containing over 2,500 square feet of signal-processing equipment areas and Early Warning Fire Detection (EWFD) systems for facilities containing less than 2,500 square feet of signal-processing equipment. Raised floors require fire detection depending on their use and the detection used in the area above them. The standard requires that EWFD and VEWFD use sensors or ports with spacing that is less than normally required by NFPA 72. Specific requirements for each type of detector are contained in Section 8.5 of the standard.</p>
<p><strong>Which emerging topics affect safety considerations in these facilities?</strong></p>
<p>Trends that are driving some of the changes that occur in NFPA 75 and NFPA 76 protected facilities include increasing power densities, which produce greater amounts of heat and therefore require increased amounts of airflow through these areas for cooling. The movement toward making buildings more environmentally friendly is leading to innovative HVAC solutions to increase system energy efficiencies. A demand for faster speed of product from concept to market creates issues in keeping on top of the newest technologies. In general, information technology equipment and telecommunication facilities change at a very fast rate. This creates some challenging issues in determining exactly what is being used, what arrangements are being used, and how these can be protected.</p>
<p>The nature of electronic data and the potential for the important use of that data leads to an ever increasing “critical” nature of these services. The need for some combination of physical protection, detection and alarm, use of appropriate suppression systems, redundancy and a higher-than-average level of reliability for system performance results in improved chances of continuity of operations when something goes wrong and access to important data when it is needed.<br />
<em><br />
For more information on NFPA Codes and Standards, including NFPA 72<sup>&reg;</sup>, NFPA 75<sup>&reg;</sup> and NFPA 76<sup>&reg;</sup>, visit <a href="http://www.nfpa.org/codes">www.nfpa.org/codes</a>.</em></p>
<p><em>NFPA 72<sup>&reg;</sup>, NFPA 75<sup>&reg;</sup> &amp; NFPA 76<sup>&reg;</sup> are registered trademarks of the National Fire Protection Association.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2011/05/nfpa-standards-specifically-cover-it-equipment-telecom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New White Paper Clarifies NFPA 72-2010 and DOD Intelligibility Requirements</title>
		<link>http://www.systemsensor.com/lifesafety/2011/02/new-white-paper-clarifies-nfpa-72-2010-and-dod-intelligibility-requirements/</link>
		<comments>http://www.systemsensor.com/lifesafety/2011/02/new-white-paper-clarifies-nfpa-72-2010-and-dod-intelligibility-requirements/#comments</comments>
		<pubDate>Thu, 24 Feb 2011 20:50:58 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[Audible/Visible Notification]]></category>
		<category><![CDATA[FIRE/LIFE SAFETY CODES]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Spring 2011]]></category>
		<category><![CDATA[A/V Notification]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[intelligibility]]></category>
		<category><![CDATA[Speakers and Strobes]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/lifesafety/?p=2392</guid>
		<description><![CDATA[As a relatively new concept to fire and life safety systems, intelligibility requirements will change how these systems are designed and installed. Designing for intelligibility can be complicated by a variety of factors. While the properties of the speaker have some impact on the intelligibility of a system, most factors have to do with the occupancy itself. So while important, speaker choice will not always ensure intelligibility.]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.systemsensor.com/lifesafety/wp-content/uploads/2011/02/NFPA-72-2010-and-DOD.png" alt="New White Paper Clarifies NFPA 72-2010 and DOD Intelligibility Requirements" title="New White Paper Clarifies NFPA 72-2010 and DOD Intelligibility Requirements" width="227" height="219" class="alignright size-full wp-image-2459" />As a relatively new concept to fire and life safety systems, intelligibility requirements will change how these systems are designed and installed. Designing for intelligibility can be complicated by a variety of factors. While the properties of the speaker have some impact on the intelligibility of a system, most factors have to do with the occupancy itself. So while important, speaker choice will not always ensure intelligibility.</p>
<p>System Sensor has posted a free whitepaper online, <em>Guidelines: Meeting NFPA 72-2010 and DOD Intelligibility Requirements</em>. This whitepaper helps designers and installers understand the concept of intelligibility, new terminology included in the code, how to determine which spaces must meet intelligibility requirements and factors that affect intelligibility.</p>
<p>NFPA 72-2010 includes a new section with intelligibility requirements for voice evacuation systems. The inclusion of these requirements will necessitate changes in how these systems are designed and installed. The whitepaper features an overview of the code and some best practices to ensure voice evacuation systems meet the latest intelligibility requirements.</p>
<p>If you are installing, designing or approving voice evacuation systems, the information in this paper can help you understand the new requirements. Download a free copy of this whitepaper at <strong><a href="http://www.systemsensor.com/av/">systemsensor.com/av</a></strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2011/02/new-white-paper-clarifies-nfpa-72-2010-and-dod-intelligibility-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Codes Address Aspirating Smoke Detection</title>
		<link>http://www.systemsensor.com/lifesafety/2010/08/codes-address-aspirating-smoke-detection/</link>
		<comments>http://www.systemsensor.com/lifesafety/2010/08/codes-address-aspirating-smoke-detection/#comments</comments>
		<pubDate>Wed, 11 Aug 2010 19:01:04 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[Fall 2010]]></category>
		<category><![CDATA[FIRE/LIFE SAFETY CODES]]></category>
		<category><![CDATA[Intelligent Detection]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[aspiration]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[Smoke detection]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/ls/?p=2172</guid>
		<description><![CDATA[Aspiration detection systems must comply with the state, local, federal and National Fire Protection Association (NFPA) codes and standards, specifically, the NFPA 72 (National Fire Alarm Code), NFPA 75 “Standard for Protection of Computer and Data Processing Equipment,” and NFPA 76 “Standard for the Fire Protection of Telecommunications Facilities.” Ultimately, the Authority Having Jurisdiction (AHJ) will dictate fire protection requirements. Although aspiration systems must comply with codes, they are not required by code.]]></description>
			<content:encoded><![CDATA[<p>Aspiration detection systems must comply with the state, local, federal and National Fire Protection Association (NFPA) codes and standards, specifically, the NFPA 72 (National Fire Alarm Code), NFPA 75 “Standard for Protection of Computer and Data Processing Equipment,” and NFPA 76 “Standard for the Fire Protection of Telecommunications Facilities.” Ultimately, the Authority Having Jurisdiction (AHJ) will dictate fire protection requirements. Although aspiration systems must comply with codes, they are not required by code.</p>
<p>First, NFPA 72 requires smoke detector spacing in areas of high air movement to be reduced. This reduction is dependent on the rate at which air is circulated in the space.</p>
<p>If the aspiration detection system will be used to protect data processing equipment, NFPA 75 guidelines must be followed. NFPA 75 uses a prescriptive and performance-based approach that requires a server room to have a sprinkler system, fire detection and alarm, portable fire extinguishers and Emergency Power Off. Any other form of fire protection, such as a clean agent suppression system, is classified as an add-on.</p>
<p>NFPA 75 (8.2 Automatic Detection Systems) states that automatic detection equipment shall be installed to provide early warning of fire. The equipment used shall be a listed smoke detection-type system and shall be installed and maintained in accordance with NFPA 72.</p>
<p>The NFPA 76 “Standard for the Protection of Telecommunication Facilities” also uses a prescriptive and performance-based approach for protecting telecommunication facilities, where telephone, data, cellular, Internet and video services are rendered. The standard defines three levels of protection: (1) Very Early Warning Fire Detection; (2) Early Warning Fire Detection, which usually incorporates conventional spot-type detectors (ionization or photoelectric type); and (3) Standard Fire Detection.</p>
<p>This section also provides suggested design and installation requirements. Early and Very Early Warning detection systems, for example, can use sensors or ports with less spacing than normally required by NFPA 72.</p>
<p>This code specifies both the area coverage as well as the sensitivity of the detector. Presently, NFPA 76 requires that “every type of sensor and port installed in a space shall be limited to a maximum coverage area of 200 sq.ft. The exception is when two levels (high and low) of ports or sensors are provided; each level shall be limited to coverage of 400 sq.ft. or less per port or sensor.”</p>
]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2010/08/codes-address-aspirating-smoke-detection/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Q&amp;A: Inspection, Testing and Maintenance of Fire- and Life-Safety Systems</title>
		<link>http://www.systemsensor.com/lifesafety/2009/11/qa-inspection-testing-and-maintenance-of-fire-and-life-safety-systems/</link>
		<comments>http://www.systemsensor.com/lifesafety/2009/11/qa-inspection-testing-and-maintenance-of-fire-and-life-safety-systems/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 18:33:14 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[Audible/Visible Notification]]></category>
		<category><![CDATA[Commercial]]></category>
		<category><![CDATA[Fall 2007]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Q & A : Ask the Expert]]></category>
		<category><![CDATA[Sprinkler Systems Monitoring]]></category>
		<category><![CDATA[A/V Notification]]></category>
		<category><![CDATA[Fire sprinklers]]></category>
		<category><![CDATA[Q&A]]></category>
		<category><![CDATA[Smoke detection]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/ls/?p=1282</guid>
		<description><![CDATA[Scott Bailey is the senior vice president of Koorsen Fire &#38; Security, an installation and service company that has been privately held since 1946. The company focuses on inspection, testing and maintenance of fire alarm, fire sprinkler, fire suppression, fire extinguishers, access control and video surveillance systems, as well as monitoring of residential and commercial [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.systemsensor.com/ls/wp-content/uploads/2009/10/scott-bailey.jpg" alt="Scott Bailey, senior vice president of Koorsen Fire &amp; Security" title="Scott Bailey, senior vice president of Koorsen Fire &amp; Security" width="114" height="143" class="alignright size-full wp-image-1396" /><em>Scott Bailey is the senior vice president of Koorsen Fire &amp; Security, an installation and service company that has been privately held since 1946. The company focuses on inspection, testing and maintenance of fire alarm, fire sprinkler, fire suppression, fire extinguishers, access control and video surveillance systems, as well as monitoring of residential and commercial facilities. The company recently developed a training center and provides training in the above-mentioned product categories.</em><br />
<img src="http://www.systemsensor.com/ls/wp-content/uploads/2009/10/inspection-testing-maintenance.jpg" alt="Inspection, Testing and Maintenance of Fire- and Life-Safety Systems" title="Inspection, Testing and Maintenance of Fire- and Life-Safety Systems" width="340" height="475" class="alignleft size-full wp-image-1395" /><br />
<strong>Q. Would someone who has completed your training courses be qualified to inspect his own facility to determine if it satisfies NFPA requirements?</strong></p>
<p><strong>A.</strong> Yes. We cover the NFPA requirements and how they relate to real-life situations, and we discuss how to interpret or understand what the NFPA says.</p>
<p><strong>Q. What is new and what has changed over the past 5, 10 and 20 years?</strong></p>
<p><strong>A.</strong> Going back a little bit further, I would say 30 years ago, sprinkler protection was installed primarily to protect the property with no expectations or thoughts about life safety. In the ’80s with the adoption of ADA, the industry began to focus more on life safety in more applications. Ten years ago, sprinklers became important for protection of life and property. Smoke detection and fire alarms became more of a design criteria, specifically for evacuation.</p>
<p>Within the past five years, I think most of the building standards have been written with the assumption that fire sprinklers are in place. With fire sprinklers, you reduce the requirements for wider corridors and the number and size of exits. A fully sprinkled building is much different than one that is not, which is good and bad alike, in my opinion.</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.systemsensor.com%2Flifesafety%2F2009%2F11%2Fqa-inspection-testing-and-maintenance-of-fire-and-life-safety-systems%2F&amp;title=Q%26%23038%3BA%3A%20Inspection%2C%20Testing%20and%20Maintenance%20of%20Fire-%20and%20Life-Safety%20Systems" id="wpa2a_2"><img src="http://www.systemsensor.com/lifesafety/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2009/11/qa-inspection-testing-and-maintenance-of-fire-and-life-safety-systems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Factors to Address in Fire- and Life-Safety Design</title>
		<link>http://www.systemsensor.com/lifesafety/2009/11/factors-to-address-in-fire-and-life-safety-design/</link>
		<comments>http://www.systemsensor.com/lifesafety/2009/11/factors-to-address-in-fire-and-life-safety-design/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 18:33:07 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[Audible/Visible Notification]]></category>
		<category><![CDATA[Carbon Monoxide Detection]]></category>
		<category><![CDATA[Commercial]]></category>
		<category><![CDATA[Cover Features]]></category>
		<category><![CDATA[Education]]></category>
		<category><![CDATA[Fall 2007]]></category>
		<category><![CDATA[Hospitality]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Residential]]></category>
		<category><![CDATA[A/V Notification]]></category>
		<category><![CDATA[Carbon monoxide]]></category>
		<category><![CDATA[Smoke detection]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/ls/?p=1280</guid>
		<description><![CDATA[Robert E. Solomon, P.E., National Fire Protection Association, tells how identifying building use, occupancy and other factors impacts planning for an appropriate system. A comprehensive fire- and life-safety design requires a cohesive blend of alarm/detection capabilities, an appropriate suppression system and a number of other building construction features that depend on occupancy, type of facility [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.systemsensor.com/ls/wp-content/uploads/2009/10/cover-factors-to-address.jpg" alt="Factors to Address in Fire- and Life-Safety Design" title="Factors to Address in Fire- and Life-Safety Design" width="227" height="326" class="alignright size-full wp-image-1405" /><em>Robert E. Solomon, P.E., National Fire Protection Association, tells how identifying building use, occupancy and other factors impacts planning for an appropriate system.</em></p>
<p>A comprehensive fire- and life-safety design requires a cohesive blend of alarm/detection capabilities, an appropriate suppression system and a number of other building construction features that depend on occupancy, type of facility and use of space. An often overlooked component — planning — is integral to keeping occupants safe.</p>
<p>In buildings, like an apartment complex, the alarm and detection system is a critical component because occupants may be asleep. Alarm and detection features can provide functions such as early warning for occupants, fire department notification and unlocking of doors. In large public venues, like a shopping mall or arena, the notification system may integrate a voice-communication function to give emergency instruction.</p>
<p>For healthcare occupancies, correctional facilities, high-rise buildings or other places where evacuation would cause considerable disturbance or not be a desired option, suppression becomes the focus of the system.</p>
<p>“An automatic fire sprinkler system has the ability to control the situation, thereby limiting the effects of the fire, the generation of products of combustion, and in general, allowing additional time for occupants to move to a safe area,” said Solomon.“Of course, the presence of a well-thought-out means of egress, with adequate exits, stairs and doors, is also crucially important.”</p>
<p>In general terms, the means of egress should also be thought of as a “system,” as well. The number, type and arrangement of the egress components are important factors to consider.</p>
<p>Some construction options may require the integration of firewalls, fire barrier walls and smoke compartments, as well as protection schemes for vertical openings between floors.</p>
<p>“There are even criteria for interior finish materials such as floor, wall and ceiling coverings,” explained Solomon.“Each of these building construction features can be specified to achieve the desired level of fire resistance, which is usually measured in hours for a firewall based on the building’s structural system, or for flame spread and smoke-developed characteristics for an interior wall finish. The level of fire-safety performance intended for the building is contingent upon the use of the occupancy.”<br />
<img src="http://www.systemsensor.com/ls/wp-content/uploads/2009/10/cover-devices.jpg" alt="Devices" title="Devices" width="710" height="193" class="alignnone size-full wp-image-1406" /></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.systemsensor.com%2Flifesafety%2F2009%2F11%2Ffactors-to-address-in-fire-and-life-safety-design%2F&amp;title=Factors%20to%20Address%20in%20Fire-%20and%20Life-Safety%20Design" id="wpa2a_4"><img src="http://www.systemsensor.com/lifesafety/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2009/11/factors-to-address-in-fire-and-life-safety-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Exclusive &#8211; NFPA 720-2009 and UL 2705 Take Action</title>
		<link>http://www.systemsensor.com/lifesafety/2009/05/web-exclusive-nfpa-720-2009-and-ul-2705-take-action/</link>
		<comments>http://www.systemsensor.com/lifesafety/2009/05/web-exclusive-nfpa-720-2009-and-ul-2705-take-action/#comments</comments>
		<pubDate>Mon, 18 May 2009 14:28:00 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[Building Codes]]></category>
		<category><![CDATA[Carbon Monoxide Detection]]></category>
		<category><![CDATA[Commercial]]></category>
		<category><![CDATA[Education]]></category>
		<category><![CDATA[Hospitality]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Summer 2009]]></category>
		<category><![CDATA[UL]]></category>
		<category><![CDATA[Carbon monoxide]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/lifesafety/?p=814</guid>
		<description><![CDATA[<p><em>Are You Installing the Right Carbon Monoxide Detector?</em></p>
<p>When security dealers, installers and distributors are evaluating which carbon monoxide (CO) detector to purchase, they should look for a product that is listed for the intended use and features that comply with the industry's most recent product standards. Every alarm professional should understand the differences between American National Standards Institute (ANSI) and Underwriters Laboratories (UL) standards ANSI/UL 2034 and ANSI/UL 2075 and be aware of the new requirements of the third edition of ANSI/UL 2075 that become effective later in 2009.</p>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.systemsensor.com/co/"><img src="http://www.systemsensor.com/ls/wp-content/uploads/2009/05/co1224tbanner_300x2501.gif" alt="CO1224T Banner" title="CO1224T Banner" class="alignright size-full wp-image-974" /></a></p>
<p><em>Are You Installing the Right Carbon Monoxide Detector?</em></p>
<p>When security dealers, installers and distributors are evaluating which carbon monoxide (CO) detector to purchase, they should look for a product that is listed for the intended use and features that comply with the industry&#8217;s most recent product standards. Every alarm professional should understand the differences between American National Standards Institute (ANSI) and Underwriters Laboratories (UL) standards ANSI/UL 2034 and ANSI/UL 2075 and be aware of the new requirements of the third edition of ANSI/UL 2075 that become effective later in 2009.</p>
<p>The CO detection market has seen significant growth in the last few years driven by legislation requiring the installation of CO detectors in single/two-family dwellings and commercial occupancies such as hotels, child and adult day care and university dormitories. Currently, there are 21 states and many major municipalities that have CO regulations.</p>
<p>ANSI/UL 2034, <em>Single and Multiple Station Carbon Monoxide Alarms</em>, is the product standard for self-contained CO alarms. These alarms are not designed nor are they listed to be connected to an alarm control panel. They receive their primary operating power from: a battery in the unit, a plug-in unit that uses a two- or three-prong attachment plug or a unit that is wired into the dwelling&#8217;s AC power line with secondary power backup.</p>
<p>ANSI/UL 2075, <em>Gas and Vapor Detectors and Sensors</em>, is the product standard for CO detectors that are designed and listed to be connected to an alarm control panel (system-connected) via conductors extending from the detector to the control panel or low-power radio frequency signal. It is important to note that even though there are two standards for CO detection devices they both have the same alarm thresholds. ANSI/UL 2075 requires detectors to operate within the sensitivity parameters defined in ANSI/UL 2034. The alarm thresholds are:</p>
<ul type="disc">
<li>70 ppm 1 to 4 hours (but not less than 1 hour)</li>
<li>150 ppm 10 to 50 minutes</li>
<li>400 ppm 4 to 15 minutes</li>
</ul>
<p>All system-connected CO detectors manufactured after September 1, 2009, will be required to meet the new requirements of the Third edition ANSI/UL 2075. Therefore, hardwired CO detectors that have the UL 2075 mark and are manufactured prior to September 1, 2009, may not be compliant with the new product standard.</p>
<p>Several new requirements of ANSI/UL 2075 mandate critical life safety supervision features that will prevent a failed detector from going undetected. These new requirements are fundamental concepts of all life safety products, such as fire alarm system devices and central station service.</p>
<p>There are currently three different gas sensing technologies on the market: biomimetic, metal oxide semiconductor (MOS) and electrochemical. All three gas sensing technologies have a limited life, therefore, it is imperative that the gas sensing element be supervised in order to ensure continuous operation. The new ANSI/UL 2075 mandates the detector to electrically supervise the gas sensing element so that when the sensor reaches its end-of-life (EOL), the detector will send a trouble signal to the control panel. This new electrical supervision requirement of the carbon monoxide sensing element is vital for safe and effective performance of the detector. To be compliant with ANSI/UL 2075, life-safety professionals should ensure their chosen system-connected CO detectors incorporate an integral trouble relay that sends a trouble signal to the control panel when the CO sensor has reached its EOL.</p>
<p>After September 1, 2009, the terminal screws of a system-connected CO detector must facilitate the required wiring supervision provisions of the UL standard. ANSI/UL 2075 requires the terminal screws to consist of binding screws with terminal plates having upturned lugs (see diagram). This method prevents the conductor from being wrapped around the terminal screw and requires the interruption of the wiring continuity when connection to the detector is lost. CO detectors that have pigtails are not acceptable.</p>
<p><img src="http://www.systemsensor.com/ls/wp-content/uploads/2009/05/814-diagram.gif" alt="Diagram" title="Diagram" class="size-full wp-image-928" /></p>
<p>The new requirements will benefit the alarm industry by improving the performance of detectors but more importantly will enhance life safety for the public in the years to come.</p>
<table bgcolor="#c3cfd9" width="100%">
<tr>
<td>
<h3>Carbon Monoxide Deaths Lead to Legislative Action</h3>
<p>The investigation of the deaths of the Lofgren family vacationing in Aspen, Colo., in 2008 due to carbon monoxide (CO) poisoning have come to a close, according to a recent report from the Aspen Daily News Online.  District Attorney Martin Beeson filed a motion on April 1st to convene a special grand jury to decide who, if anyone, will be prosecuted for the CO poisoning death of a vacationing family in an Aspen area home in November. A faulty pipe in the heating and snow melt system leaked CO and killed the family while they slept, according to investigators.</p>
<p>In other headlines, two men and a 13-year-old boy in Minneapolis died from CO poisoning when they used a gas-powered generator in their basement after their power was shut off. In addition, a mother and two teens in Paramount, California, suffered CO poisoning in November when they heated their home with a charcoal grill.</p>
<p>CO detection is now more important then ever, as The Centers for Disease Control reports that cases of CO poisoning have been on the rise in recent years, climbing 36 percent between 2001 and 2006. A key cause is most evident in the winter months, when many families cannot afford to pay for electricity and eventually get their heating turned off. Using other sources of heat, families don&#8217;t realize the increased dangers of CO poisoning.</p>
<p>Thanks to the National Fire Protection Association (NFPA), the new edition, NFPA 720-2009 standard will be issued in October and will be the standard for the Installation of CO detection and warning equipment. It is the first CO standard to address CO devices in non-residential buildings and also mandates the placement of CO detectors/alarms on every level of a residence. The standard has been completely rewritten to encompass more types of occupancies and to specifically define CO detection usage.</p>
</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2009/05/web-exclusive-nfpa-720-2009-and-ul-2705-take-action/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Guidelines &#8211; Demystifying NFPA Code and Standard Development</title>
		<link>http://www.systemsensor.com/lifesafety/2009/05/guidelines-demystifying-nfpa-code-and-standard-development/</link>
		<comments>http://www.systemsensor.com/lifesafety/2009/05/guidelines-demystifying-nfpa-code-and-standard-development/#comments</comments>
		<pubDate>Mon, 18 May 2009 13:27:58 +0000</pubDate>
		<dc:creator>maria</dc:creator>
				<category><![CDATA[Building Codes]]></category>
		<category><![CDATA[Guidelines]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Summer 2009]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/lifesafety/?p=791</guid>
		<description><![CDATA[<p><em>Ever wonder how changes to NFPA codes and standards are made? Here's a quick guide.</em></p>
<p>The National Fire Protection Association (NFPA) encourages public participation in its code and standards development. Codes and standards are revised every three to five years in a systematic and inclusive process that provides an opportunity for all stakeholders to submit input through key points in the development cycle.</p>]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-864" title="NFPA Code" src="http://www.systemsensor.com/ls/wp-content/uploads/2009/05/791-corner.jpg" alt="NFPA Code" /><br />
<em>Ever wonder how changes to NFPA codes and standards are made? Here&#8217;s a quick guide.</em></p>
<p>The National Fire Protection Association (NFPA) encourages public participation in its code and standards development. Codes and standards are revised every three to five years in a systematic and inclusive process that provides an opportunity for all stakeholders to submit input through key points in the development cycle.</p>
<p><strong>Responding to the Call</strong></p>
<p>The cycle begins with a call for input from a wide range of stakeholders.</p>
<p>NFPA will publicize calls for proposal submissions through <em>NFPA Journal</em> magazine and the NFPA Web site, as well as other standards-related media. The NFPA Web site also has links (see Table) to all the forms needed for drafting and submitting a proposal, such as the Online Submission Form for revisions to existing codes or standards.</p>
<table border="1" width="100%" bgcolor="#c3cfd9" align="center">
<tbody>
<tr>
<th colspan="3" align="center">
<h3>Table: The NFPA Standard and Code Revision Process and Useful Links</h3>
</th>
</tr>
<tr>
<td width="150"><strong style="display: block; width: 150px;">STEP</strong></td>
<td width="150"><strong style="display: block; width: 150px;">DESCRIPTION</strong></td>
<td><strong>DOCUMENTS AND LINKS</strong></td>
</tr>
<tr>
<td>Call for Proposals</td>
<td>Public call through NFPA and other standards-related media for standard and code revision proposals.</td>
<td><strong><a href="http://www.nfpa.org/assets/files/PDF/CodesStandards/NFPAProposalForm.doc">Proposal Form</a></strong></p>
<p>http://www.nfpa.org/assets/files/PDF/Codes</p>
<p>Standards/NFPAProposalForm.doc<strong><a href="http://submissions.nfpa.org/onlinesub/onsubmain.php">Online Submission Form</a></strong></p>
<p>http://submissions.nfpa.org/onlinesub/</p>
<p>onsubmain.php</td>
</tr>
<tr>
<td>Report on Proposals (ROP)</td>
<td>Committee meets to approve or reject submitted proposals and develop new proposals.</td>
<td><strong><a href="http://www.nfpa.org/categoryList.asp?categoryID=817">ROP Download Page</a></strong><br />
http://www.nfpa.org/categoryList.asp?categoryID=817<strong><a href="http://www.nfpa.org/assets/files/PDF/CodesStandards/NFPACommentForm.doc">Comment Form</a></strong></p>
<p>http://www.nfpa.org/assets/files/PDF/</p>
<p>CodesStandards/NFPACommentForm.doc</td>
</tr>
<tr>
<td>Report on Comments (ROC)</td>
<td>60 days from submittal of ROP, Committee reconvenes to approve or reject public comments and develop new comments.</td>
<td rowspan="3" valign="top"><strong><a href="http://www.nfpa.org/categoryList.asp?categoryID=817&amp;cookie_test=1">ROC Download Page</a></strong></p>
<p>http://www.nfpa.org/categoryList.asp?</p>
<p>categoryID=817&amp;cookie_test=1<strong><a href="http://www.nfpa.org/assets/files/PDF/CodesStandards/NITMAMFormGeneric.doc">NITMAM Form</a></strong></p>
<p>http://www.nfpa.org/assets/files/</p>
<p>PDF/CodesStandards/NITMAMForm<br />
Generic.doc</td>
</tr>
<tr>
<td>Association Technical Meeting</td>
<td>NFPA membership votes on certified amending motions.</td>
</tr>
<tr>
<td>Standards Council Issuance</td>
<td>Standards Council holds hearings to consider process appeals. New and revised standards are issued.</td>
</tr>
</tbody>
</table>
<p>A completed proposal must be submitted by 5 p.m. EST of the proposal closing date to be considered. When drafting a code revision, remember: Don&#8217;t propose a revision simply because it will mandate one of your products or services. Biased, special interest group proposals will be rejected.</p>
<p><strong>Report on Proposals: The First Review</strong></p>
<p>Once submitted, the proposal will be routed for review by a Technical Committee. An NFPA Technical Committee is a group of technical individuals, selected and appointed by the NFPA Standards Council, who comprise a cross section of the stakeholders for the particular standard. Individual members are appointed on the basis of technical knowledge as well as to maintain a balance of interest groups. For example, members might be drawn from such diverse areas as installing companies, product manufacturers and suppliers, trade associations and government agencies.</p>
<p>The product of this initial review is a report that is published and made available to the general public, called the Report on Proposals (ROP). This initial report represents the findings and decisions of the Technical Committee on each proposal.</p>
<p>Committee findings can be in agreement or disagreement — or anything in between — for each proposal. At this point, the findings of the committee are far from the final word. In fact, the ROP is circulated for a 60-day public review and comment period, which enables stakeholders to review the findings of the Technical Committee and submit comments on those findings; again, with proposed language and technical justification.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2009/05/guidelines-demystifying-nfpa-code-and-standard-development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Eight Points to Know About NFPA 720-2009 Changes</title>
		<link>http://www.systemsensor.com/lifesafety/2008/08/guidelines-eight-points-to-know-about-nfpa-720-2009-changes/</link>
		<comments>http://www.systemsensor.com/lifesafety/2008/08/guidelines-eight-points-to-know-about-nfpa-720-2009-changes/#comments</comments>
		<pubDate>Thu, 28 Aug 2008 12:43:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Carbon Monoxide Detection]]></category>
		<category><![CDATA[Commercial]]></category>
		<category><![CDATA[Fall 2008]]></category>
		<category><![CDATA[Guidelines]]></category>
		<category><![CDATA[NFPA]]></category>
		<category><![CDATA[Carbon monoxide]]></category>

		<guid isPermaLink="false">http://www.systemsensor.com/lifesafety/?p=86</guid>
		<description><![CDATA[Prior to 2005, NFPA 720, the carbon monoxide (CO) detection standard set by the National Fire Protection Association, was little more than a recommendation. In 2005, in reaction to greater public awareness of CO poisoning and local CO detection legislation, NFPA 720 was changed from a recommended practice to an installation standard with teeth.]]></description>
			<content:encoded><![CDATA[<h3><em>NFPA 720-2009 is a complete rewrite of the CO detection standard, which now covers commercial occupancies and impacts CO detector development, installation, testing and off-premise signal transmission.</em></h3>
<p>Prior to 2005, NFPA 720, the carbon monoxide (CO) detection standard set by the National Fire Protection Association, was little more than a recommendation. In 2005, in reaction to greater public awareness of CO poisoning and local CO detection legislation, NFPA 720 was changed from a recommended practice to an installation standard with teeth.</p>
<p>The new edition, NFPA 720-2009, will be issued in October and will be the <em>Standard for the Installation of Carbon Monoxide (CO) Detection and Warning Equipment</em>. The standard has been completely rewritten to encompass more types of occupancies and to more specifically define CO detection system usage.</p>
<p>There are eight main changes and additions to NFPA 720 that will affect you:</p>
<h4>1) NFPA 720 nationally standardizes CO detection for all buildings, not just residences. This includes schools, hotels, nursing homes and other commercial structures.</h4>
<p>The 2005 edition of NFPA 720 addressed only dwelling units. Since then, the number of states requiring the installation of CO detection in residential, and in some cases commercial buildings, has more than doubled. Commercial occupancies where CO detection is required include hotels, rooming houses, dormitories, day care centers, schools, hospitals, assisted-living facilities and nursing homes.</p>
<p>In the absence of a national installation standard, each jurisdiction has developed its own requirements. This has resulted in considerable confusion in the industry. Several key areas of concern are installation, testing and off-premise signal transmission to the supervising station. NFPA 720-2009 is a huge step toward minimizing these concerns.</p>
<p>The new commercial installation requirements in NFPA 720-2009 contain extracts from NFPA 72<sup>®</sup>: National Fire Alarm Code<sup>®</sup>, and can be found in chapters 1 through 8. Chapter 9 covers households.</p>
<h4>2) CO alarm signals need to be distinct from other signals and indicate sensor failure or end of life.</h4>
<p>In the 2005 edition of NFPA 720, CO detectors were required to be connected to a control panel via a supervisory circuit only. NFPA 720-2009 requires CO alarm signals to be distinct and “descriptively annunciated” from fire alarm, CO supervisory and CO trouble signals. Furthermore, the CO alarm signal should take precedence over supervisory or trouble signals. The actuation of a CO detector or system should be distinctly indicated as a CO alarm signal.</p>
<p>CO detector trouble signals must be indicated visually and audibly at the control panel and supervising station. Therefore, the CO detector must have an integral trouble relay that will send trouble conditions to the control panel, such as a sensor failure or sensor end-of-life signal.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.systemsensor.com/lifesafety/2008/08/guidelines-eight-points-to-know-about-nfpa-720-2009-changes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

