1 Technical Committee on Commissioning Fire Protection Systems M E M O R A N D U M DATE: March 30, 2010 TO: FROM: Principal and Alternate Members of the Technical Committee on Commissioning Fire Protection Systems Jonathan Levin, Associate Fire Protection Engineer/NFPA Staff Liaison Matt Klaus, Senior Fire Protection Engineer/NFPA Staff Liaison SUBJECT: AGENDA PACKAGE NFPA 3 A2011 ROP Meeting Enclosed is the agenda for the Report on Proposals (ROP) meeting for NFPA 3, Standard for Commissioning and Integrated Testing of Fire Protection and Life Safety Systems. This meeting was originally scheduled to be the Report on Comments (ROC) meeting for the Fall 2010 Revision Cycle; however, the committee voted to slip cycle during a teleconference on March 25, 2010. Therefore, NFPA 3 has entered the Annual 2011 revision cycle, and the meeting has been changed to an ROP meeting. It is imperative that you review the attached proposals in advance, with your ideas and substantiations for your views. Please note the previous actions and committee statements will appear with the attached proposals. If you have alternate suggestions for text changes, please come prepared with the words and respective substantiation. For administrative questions, please feel free to Contact Patti Mucci at (617) 984-7948. For technical questions, please feel free to contact Jonathan Levin at (617) 984-7245 or Matt Klaus at (617) 984-7448. You can also reach either of us via e-mail at JLevin@nfpa.org or MKlaus@nfpa.org. We look forward to meeting everyone in Charlotte, NC at The Renaissance Charlotte Suites Hotel.
2 Table of Contents Meeting Agenda 3 Committee Address List 4 Committee Distribution 10 F2010 ROP Meeting Minutes 12 A2011 Key Dates 14 Staff Liaison Notice 15 Standards Council Approval of Committee Scope 21 NIBS Letter to NFPA 22 Public Proposals 23
3 Technical Committee on Commissioning Fire Protection Systems ROP Meeting April 13 15, 2010 The Renaissance Charlotte Suites Hotel 2800 Coliseum Centre Drive Charlotte, North Carolina 28217 (704) 357-1414 AGENDA Tuesday, April 13, 2010 1. Call to Order 8:30 AM 2. Introductions 3. Proposed Agenda 4. Committee Member Status and Update of Membership Roster 5. Approval of F2010 ROP Meeting Minutes 6. Chairman Comments 7. NFPA Staff Liaison Presentation and Review of Key Dates in A2011 Cycle 8. Committee Discussion on Direction of Document a. Standard b. Recommended Practice c. Integrated Testing Standard w/ Commissioning in Annex (Task Group Draft) d. Split into Two Separate Documents i. Commissioning (Annual 2011) ii. Integrated Testing (Future Cycle) 9. Act on Public Proposals (F2010 ROP) No Later than 1:00 PM 10. Adjourn Wednesday, April 14, 2010 1. Call to Order 8:30 AM 2. Continue Action on Public Proposals (F2010 ROP) if Applicable 3. Generate Committee Proposals if Finished with Public Proposals 4. Adjourn Thursday, April 15, 2010 1. Call to Order 8:30 AM 2. Continue Generation of Committee Proposals if Applicable 3. Brief Review of Meeting Output (Unofficial Draft) 4. Discuss Old Business 5. Discuss New Business 6. Discuss Tentative Meeting Dates and Locations for A2011 ROC Meeting 7. Adjourn 5:00 PM
Distribution by % CMF-AAA Commissioning Fire Protection Systems Name Company Representation Class Office Art Black Carmel Fire Dept/Carmel Fire Prot Assoc. E Principal Rick Kabele Clark County Development Services E Principal David O. Lowrey City of Boulder Fire Rescue E Principal Robert J. Tabet US Department of the Navy E Principal Voting Number 4 Percent 12% Bruce H. Clarke XL Global Asset Protection, LLC XLGAPS I Principal Michael D. DeVore State Farm Insurance Company NFPA/IFPS I Principal 10 3/30/2010 Rockwood J. Edwards Aon/Schirmer Engineering Corporation AON I Principal David R. Hague Liberty Mutual Property PCIAA I Principal Robert Kasiski FM Global FM I Principal Pascal Pfeiffer AXA Insurance Company EFSN I Principal Voting Number 6 Percent 18% George L. Church, Jr. Rowe Sprinkler Systems, Inc. AFSA IM Principal Shane M. Clary Bay Alarm Company IM Principal James E. Deason Century Fire Protection, LLC IM Principal Norbert W. Makowka National Association of Fire Equipment Distributors NAFED IM Principal Michael Wade McDaniel F Tech NFPA/LAS IM Principal Voting Number 5 Percent 15% Joseph Duquet Sprinkler Fitters Local 704 UA L Principal Voting Number 1 Percent 3% Brian R. Foster Global Fire Engineering, Inc. AFAA M Principal Kimberly A. Gruner Fike Corporation M Principal John L. Hulett Western States Fire Protection Company NFSA M Principal Scott T. Martorano The Viking Corporation M Principal Rodger Reiswig Tyco/SimplexGrinnell TYCO M Principal
Distribution by % CMF-AAA Commissioning Fire Protection Systems Tuesday, March 30, 2010 Name Company Representation Class Office Voting Number 5 Percent 15% John F. Bender Underwriters Laboratories Inc. UL RT Principal Voting Number 1 Percent 3% Maurice M. Pilette Mechanical Designs Ltd. SE Chair David L. Boswell Hughes Associates, Inc. SE Principal Douglas W. Fisher Fisher Engineering, Inc. SE Principal Kenneth L. Gentile The RJA Group, Inc. RJA SE Principal 11 John E. Kampmeyer Triad Fire Protection Engineering Corporation SE Principal Voting Number 5 Percent 15% Pat Cull Lifespan U Principal Paul F. Dunphy, Jr. Harvard University U Principal David W. Frable US General Services Administration GSA U Principal Bill Fremis Defence Construction Canada U Principal Charles M. Kilfoil Bechtel National, Inc. U Principal Jeff Negley Webcor Builders U Principal Voting Number 6 Percent 18% Total Voting Number 33
12 NFPA 3 Technical Committee on Commissioning and Integrated Testing of Fire and Life Safety Systems (CMF-AAA) ROP Meeting July 9-11, 2009 Holiday Inn Golden Gateway, 1500 Van Ness Ave. San Francisco, CA Minutes of Meeting 1. Meeting was called to order at 8:00AM (PDT), Thursday July 9, 2009. 2. Self introductions were made. Committee members in attendance were Maurice Pilette- Chair, Timothy Hawthorne-Staff, John Bender, David Boswell, George Church, Bruce Clarke, Shane Clary, James Deason, Michael DeVore, Paul Dunphy, Rockwood Edwards, Brian Foster, David Frable, Bill Fremis, Kenneth Gentile, Kimberly Gruner, John Hulett, John Kampmeyer, Robert Kasiski, Charles Kilfoil, David Lowery, Norbert Makowka, Scott Martorano, Jeff Negley, Pascal Pfeiffer, Robert Tabet, Daniel Berkoski, Cecil Bilbo, Thomas Wellen, Martin Workman, and Art Black. 3. Guests were introduced Daniel P. Finnegan and Martin R. Anderson, both of Siemens Building Technologies, Inc. 4. Motion was made and seconded for approval of the meeting minutes from March 2009 Boston Meeting. Minutes were approved. 5. Staff reviewed procedures for ROP meeting and rules. Details included review of voting and action for each proposal is required, discussion on Definitions, use definition from Glossary of Terms. Staff noted the committee can use a new term, ask the council for a secondary definition, or ask council to re-assign term to your document. Fire Exit and safety rules were reviewed. Committee discussed the date and location change of this meeting. 6. The attendance list was distributed. 7. Chair asked for a list showing of hand where both Principles and Alternates are present. John Hulett requested that Cecil Bilbo be his principle vote for this meeting. 8. 23 voting members were determined by show of hands. A vote of quantity 12 is simple majority vote for this meeting. 9. Chair and staff noted the requirement of the voting again with the Ballot, after the completion of this meeting. The ballot has been changed recently. Now the ballot is e- mailed and committee is able to vote for all actions OR can individually vote on each. Simple majority of ballots need to be returned. The committee currently has 32 principle members. We will need 17 ballot votes to move document forward. Of 17, 2/3 of the log needs to pass. Chair stressed the importance of the ballot voting. 10. Staff reviewed the ability to generate comments on any proposals that have been generated. Comments must be detailed back to an existing proposal. The committee will meet again next spring for Comments and then an ROC will be documented. 11. Suggestion was made to attend the Committee Leadership conference at the annual NFPA meeting. 12. Chair noted that there are 49 proposals from outside the committee. 157 proposals were generated by committee members. 13. Chair suggested that the task group submitter of a proposal make the motion to the floor when moved to said log during this meeting. 14. 2/3 vote required to stop discussion if Call to Question. 15. A task group was assigned. Robert Tabet (lead) with Cecil Bilbo and John Hulett were requested to develop a committee proposal(s) to review document use of Functional Performance Test and report back on recommendations to provide consistency. Page 1 of 2
13 16. Chair requested a Task group for chapter 10 be gathered again to create comments See proposals 3-178 and 3-91. Doug Fisher should chair this group. Bruce Clarke requested involvement with this team. 17. The task group regarding Functional Performance Testing provided recommendations. Preliminary Testing was suggested to replace Pre-Functional Testing in five instances. The group that worked on this task consisted of Robert Tabet, Dan Berkoski, John Kampmeyer, and Bill Fremis. Chair requested that the group continue the work and Tim Hawthorne requested to be included in the involvement of this work Thursday evening to report back to the committee on Friday. 18. Staff noted that the committee can motion for a committee proposal to move the document forward. This can be done on a NEW document only. This allows any part of the document to be commented. Later in the meeting, a Committee Proposal was created, CP-15. 19. Staff noted that a PRE-ROC meeting can also be held to address any further issues. 20. Chair noted that this document will be printed in Spanish when released. 21. Robert Tabet provided task group report on Periodic Integrated Testing. The group suggested a definition change Pre-functional Performance Testing to Preliminary Testing (6 sections). Functional Performance testing changed to Integrated Testing (6 sections). Committee created CP-18 with the work provided. 22. Staff showed the committee the current document draft revision that he has available detailing what was changed and new material in one same document. He will make this available in a few weeks. A request was made to ask NFPA to provide this type of document to the public. Old Business 1. Reviewed a draft committee proposal regarding changes to the entire document. The major change was to change Authority Having Jurisdiction to AHJ After a discussion no action was taken. The submitter should address this subject in the Comments stage. 2. Discussion regarding a proposal NFPA 1 to mandate the use of NFPA 3. With NFPA 1 proposals due by 17:00 (EDT) on 24-July-09, there was not enough time for this to be balloted through the entire Technical Committee as a proposal from the Technical Committee. Next Meeting Dates and Location 1. Comment closing date is March 5, 2010. May 7 is the final date for the ROC. Meeting will need to be held between these dates. Chair requested possible meeting locations: a. Paris, France b. Toronto, Canada c. Halifax, N.S. d. Mexico City, Mexico Staff will poll the members of the Committee for the location that will result in best attendance. Week of March 22, 2010 was tentative date chosen. During the 3 rd day of meeting another review of when the closing dates for comments and the date for the ROC meeting. After a discussion, the date of the meeting was moved to the week of April 12 th, 2010. 23. The meeting adjourned at 11:41 (PDT), Saturday, July 11, 2009. Page 2 of 2
14 NFPA 3 Revision Cycle Annual 2011 Proposal Closing November 24, 2009 Final date for ROP Meeting February 26, 2010 Ballots Mailed to TC before March 19, 2010 ROP Published June 25, 2010 Comment Closing September 3, 2010 Final Date for ROC Meeting November 15, 2010 Ballots Mailed to TC before November 19, 2010 ROC Published February 25, 2011 Intent to Make a Motion Closing (NITMAM) April 8, 2011 Issuance of Consent Document (No NITMAMs) May 31, 2011 NFPA Annual Meeting Boston June 2011 Issuance of Document with NITMAM August 11, 2011
15 Note from the Staff Liaison Dear Committee Members: We are very pleased that you will be participating in the processing of the 2011 Edition of NFPA 3. Development of the Standard would not be possible without the participation of volunteers like you. Materials You Will Need to Have for the Committee Meeting Agenda with all attachments Committee Officers' Guide (Chairs) Roberts Rules of Order (Chairs abbreviated version may be found in the Committee Officer s Guide) "Nice to Have" Materials Unofficial NFPA 3 Task Group Report Dated February 11, 2010 Public Comments Submitted Under F2010 Cycle NFPA Annual Directory NFPA Manual of Style Prepared Committee Proposals (If applicable) Preparation Prepared actions and statements will clarify your position and provide the committee with a starting point. Prepared actions and statements really help expedite the progress of the meeting. Getting Things Done Proposals Only one posting of proposals will be made; it will be arranged in section/order and will be pre-numbered. This will be posted to the NFPA e-committee website and also attached
16 to this Agenda Package. If you have trouble accessing the website please contact Joanne Goyette at jgoyette@nfpa.org. Please bring the proposals to the committee meeting. The processing schedule to be followed by the committee is outlined in the schedule in this package. As the schedule is very tight, no extensions of the deadline for receipt of completed ballots or extensions of the period to change vote will be possible. It is therefore suggested that those of you who must consult with others regarding your ballot do so based on the material passed out at the meeting, and your meeting notes. Do not wait for receipt of the ballot materials from NFPA. Regulations and Operating Procedures All actions at, and following, the committee meetings will be governed in accordance with the NFPA Regulations Governing Committee Projects. The latest Regulations (as of this printing) appear on pages 10-28 of the 2010 NFPA Directory. All committee actions will be in accordance with the NFPA Regulations Governing Committee Projects. The style of NFPA 3 will comply with the Manual of Style for NFPA Technical Committee Documents. Failure to comply with these rules could result in challenges to the standards-making process. A successful challenge on procedural grounds could prevent or delay publication of NFPA 3. Consequently, committees must follow the regulations and procedures. Processing Proposals Proposals Requiring Committee Actions All public proposals must be acted upon. If a proposal does not comply with Section 4.3.3 of the NFPA Regulations Governing Committee Projects (an incomplete proposal), the committee may reject the proposal. However, any of the standard actions may be taken. Please make sure that the committee's action and the committee's statement result in a complete action that can be readily understood.
17 Committee Actions The following are the actions permitted by the Regulations Governing Committee Projects for disposition of proposals. Accept The committee accepts the proposal exactly as written. Only editorial changes such as paragraph and section numbering, and corrections to spelling, capitalization, and hyphenation may be made. If a proposal is accepted without a change of any kind, except for editorial changes, the committee can simply indicate acceptance. The committee should add a committee statement explaining the action if, for example the committee does not agree with all of the substantiation or supporting data or has a number of different reasons for acceptance than those stated in the substantiation or supporting data. The absence of such a statement could mislead the reader by giving the impression that the committee agreed with all of the substantiation for the proposal. Reject The proposal is rejected by the committee. If the principle or intent of the proposal is acceptable in whole or in part, the proposal should not be rejected, it should be accepted in principle or accepted in principle in part. A complete reason for rejection of the proposal must be supplied in the committee statement. Accept in Principle Accept the proposal with a change in wording. The committee action must indicate specifically what action was taken to revise the proposed wording, and where the wording being revised is located (i.e., in the proposed wording or in the document). If the details are in the action on another proposal, the committee action may simply indicate "Accept in Principle" but reference should then be made in the committee statement to the specific proposal detailing the action. Accept in Part If part of a proposal is accepted without change and the remainder is rejected, the proposal should be "Accepted in Part." The committee action must indicate what part was
18 accepted and what part was rejected and the committee statement must indicate its reasons for rejecting that portion. Accept in Principle in Part This is a combination of "Accept in Principle" and "Accept in Part" as shown above. Committee Statements Any proposal that is "Accepted in Principle", "Accepted in Part", "Accepted in Principle in Part" or "Rejected" must include a committee statement, preferably technical in nature that provides the reasons for the action. References to the requirements of other documents as a reason for rejection should be to the specific sections of the document including the requirements. If there is more than one such section, the reference should include a least one, identified as an example. It is a violation of the regulations for a committee to reject a proposal simply because it accepted a different proposal on the same subject. Reference in the committee statement to another committee action is inappropriate unless the referenced proposal contains all of the applicable technical justification for the action. If the rejection or change was for the same reason that another proposal was rejected or changed, the committee statement may refer to that proposal giving the same reason for rejection or change. Please verify that cross references to other propsals are correct. The committee statement should not refer to another committee statement which, in turn, refers to some other committee statement. There may be a situation where the committee will want to refer to two, three, or more committee statements if they are all appropriate. When the committee develops a committee action for a proposal that is accepted in principle, the rationale must indicate why the wording submitted was not accepted. This reason should be technical in nature, unless the committee has simply rewritten the submitter's text, in which case the committee can state that the proposed wording should meet the submitter's intent.
19 The committee statement on a proposal that is accepted in part should indicate specifically why that part of the proposal was not accepted. Easy Procedures for Handling a Motion NFPA Committee Meetings are conducted in accordance with Roberts' Rules of Order. In order for a proposal to be discussed, a motion must be made. A simplified procedure for discussion of motions is as follows: Member Member Addresses the Chair Receives Recognition from the Chair Introduces the Motion (Another Member) Seconds the Motion. Chair (Presiding Officer) States the Motion Calls for Discussion Takes the vote Announces the Result of the Vote It is imperative that you review the proposals before the meeting and develop proposed actions and statements. These prepared actions and statements will clarify your position and provide the committee with a starting point. Prepared actions and statements really help expedite the progress of the meeting. Balloting Dos and Don'ts Either fax or mail your ballot - Please do not do both. Don't return the entire package; just return the appropriate ballot page(s) and explanation of votes. Alternate Members At the end of each code cycle, the Standards Council reviews records of all members regarding their participation in the standards-making process. Therefore, it is important
20 for alternate members to remember that return of ballots is expected, even though they know that their principal member will be attending meetings and returning their ballots. General Procedures for Meetings Use of tape recorders or other means capable of producing verbatim transcriptions of any NFPA Committee Meeting is not permitted. Attendance at all NFPA Committee Meetings is open. All guests must sign in and identify their affiliation. Participation in NFPA Committee Meetings is generally limited to committee members and NFPA staff. Participation by guests is limited to individuals, who have previously requested of the chair time to address the committee on a particular item, or individuals who wish to speak regarding public proposals or comments that they submitted. The chairman reserves the right to limit the amount of time available for any presentation. No interviews will be allowed in the meeting room at any time, including breaks. All attendees are reminded that formal votes of committee members will be secured by letter ballot. Voting at this meeting is used to establish a sense of agreement, but only the results of the formal letter ballot will determine the official position of the committee on any proposal. Note to Special Experts: Particular attention is called to Section 3.3(e) of the NFPA Guide for the Conduct of Participants in the NFPA Codes and Standards Development Process in the NFPA Directory that directs committee members to declare their interest representation if it is other than their official designation as shown on the committee roster, such as when a special expert is retained and represents another interest category on a particular subject. If such a situation exists on a specific issue or issues, the committee member shall declare those interests to the committee, and refrain from voting on any proposal, comment, or other matter relating to those issues. Smoking is not permitted at NFPA Committee Meetings.
21
22
23 2010 Fall Revision Cycle Report on Proposals A compilation of NFPA Technical Committee Reports on Proposals for public review and comment Public Comment Deadline: March 5, 2010 NOTE: The proposed NFPA documents addressed in this Report on Proposals (ROP) and in a follow-up Report on Comments (ROC) will only be presented for action at the NFPA June 2011 Association Technical Meeting to be held June 12 15, 2011, at Boston Convention and Exhibition Center in Boston, MA, when proper Amending Motions have been submitted to the NFPA by the deadline of October 22, 2010. Documents that receive no motions will not be presented at the meeting and instead will be forwarded directly to the Standards Council for action on issuance. For more information on the rules and for up-to-date information on schedules and deadlines for processing NFPA documents, check the NFPA website (www. nfpa.org) or contact NFPA Standards Administration. National Fire Protection Association 1 BATTERYMARCH PARK, QUINCY, MA 02169-7471 ISSN 1079-5332 Copyright 2009 All Rights Reserved NFPA and National Fire Protection Association are registered trademarks of the National Fire Protection Association, Quincy, MA 02169.
Information on NFPA Codes and Standards Development 24 I. Applicable Regulations. The primary rules governing the processing of NFPA documents (codes, standards, recommended practices, and guides) are the NFPA Regulations Governing Committee Projects (Regs). Other applicable rules include NFPA Bylaws, NFPA Technical Meeting Convention Rules, NFPA Guide for the Conduct of Participants in the NFPA Standards Development Process, and the NFPA Regulations Governing Petitions to the Board of Directors from Decisions of the Standards Council. Most of these rules and regulations are contained in the NFPA Directory. For copies of the Directory, contact Codes and Standards Administration at NFPA Headquarters; all these documents are also available on the NFPA website at www.nfpa.org. The following is general information on the NFPA process. All participants, however, should refer to the actual rules and regulations for a full understanding of this process and for the criteria that govern participation. II. Technical Committee Report. The Technical Committee Report is defined as the Report of the Technical Committee and Technical Correlating Committee (if any) on a document. A Technical Committee Report consists of the Report on Proposals (ROP), as modified by the Report on Comments (ROC), published by the Association. III. Step 1: Report on Proposals (ROP). The ROP is defined as a report to the Association on the actions taken by Technical Committees and/or Technical Correlating Committees, accompanied by a ballot statement and one or more proposals on text for a new document or to amend an existing document. Any objection to an action in the ROP must be raised through the filing of an appropriate Comment for consideration in the ROC or the objection will be considered resolved. IV. Step 2: Report on Comments (ROC). The ROC is defined as a report to the Association on the actions taken by Technical Committees and/or Technical Correlating Committees accompanied by a ballot statement and one or more comments resulting from public review of the Report on Proposals (ROP). The ROP and the ROC together constitute the Technical Committee Report. Any outstanding objection following the ROC must be raised through an appropriate Amending Motion at the Association Technical Meeting or the objection will be considered resolved. V. Step 3a: Action at Association Technical Meeting. Following the publication of the ROC, there is a period during which those wishing to make proper Amending Motions on the Technical Committee Reports must signal their intention by submitting a Notice of Intent to Make a Motion. Documents that receive notice of proper Amending Motions (Certified Amending Motions) will be presented for action at the annual June Association Technical Meeting. At the meeting, the NFPA membership can consider and act on these Certified Amending Motions as well as Follow-up Amending Motions, that is, motions that become necessary as a result of a previous successful Amending Motion. (See 4.6.2 through 4.6.9 of Regs for a summary of the available Amending Motions and who may make them.) Any outstanding objection following action at an Association Technical Meeting (and any further Technical Committee consideration following successful Amending Motions, see Regs at 4.7) must be raised through an appeal to the Standards Council or it will be considered to be resolved. VI. Step 3b: Documents Forwarded Directly to the Council. Where no Notice of Intent to Make a Motion (NITMAM) is received and certified in accordance with the Technical Meeting Convention Rules, the document is forwarded directly to the Standards Council for action on issuance. Objections are deemed to be resolved for these documents. VII. Step 4a: Council Appeals. Anyone can appeal to the Standards Council concerning procedural or substantive matters related to the development, content, or issuance of any document of the Association or on matters within the purview of the authority of the Council, as established by the Bylaws and as determined by the Board of Directors. Such appeals must be in written form and filed with the Secretary of the Standards Council (see 1.6 of Regs). Time constraints for filing an appeal must be in accordance with 1.6.2 of the Regs. Objections are deemed to be resolved if not pursued at this level. VIII. Step 4b: Document Issuance. The Standards Council is the issuer of all documents (see Article 8 of Bylaws). The Council acts on the issuance of a document presented for action at an Association Technical Meeting within 75 days from the date of the recommendation from the Association Technical Meeting, unless this period is extended by the Council (see 4.8 of Regs). For documents forwarded directly to the Standards Council, the Council acts on the issuance of the document at its next scheduled meeting, or at such other meeting as the Council may determine (see 4.5.6 and 4.8 of Regs). IX. Petitions to the Board of Directors. The Standards Council has been delegated the responsibility for the administration of the codes and standards development process and the issuance of documents. However, where extraordinary circumstances requiring the intervention of the Board of Directors exist, the Board of Directors may take any action necessary to fulfill its obligations to preserve the integrity of the codes and standards development process and to protect the interests of the Association. The rules for petitioning the Board of Directors can be found in the Regulations Governing Petitions to the Board of Directors from Decisions of the Standards Council and in 1.7 of the Regs. X. For More Information. The program for the Association Technical Meeting (as well as the NFPA website as information becomes available) should be consulted for the date on which each report scheduled for consideration at the meeting will be presented. For copies of the ROP and ROC as well as more information on NFPA rules and for up-to-date information on schedules and deadlines for processing NFPA documents, check the NFPA website (www.nfpa.org) or contact NFPA Codes & Standards Administration at 617-984-7246.
25 2010 Fall Revision Cycle ROP Contents by NFPA Numerical Designation Note: Documents appear in numerical order. NFPA No. Type Action Title Page No. 2 N Hydrogen Technologies Code... 2-1 3 N Standard on the Commissioning and Integrated Testing of Fire Protection and Life Safety Systems... 3-1 12 P Standard on Carbon Dioxide Extinguishing Systems... 12-1 16 P Standard for the Installation of Foam-Water Sprinkler and Foam-Water Spray Systems... 16-1 18A P Standard on Water Additives for Fire Control and Vapor Mitigation....18A-1 31 P Standard for the Installation of Oil-Burning Equipment... 31-1 32 P Standard for Drycleaning Plants... 32-1 35 P Standard for the Manufacture of Organic Coatings... 35-1 51A P Standard for Acetylene Cylinder Charging Plants... 51A-1 79 P Electrical Standard for Industrial Machinery... 79-1 85 P Boiler and Combustion Systems Hazards Code... 85-1 102 P Standard for Grandstands, Folding and Telescopic Seating, Tents, and Membrane Structures... 102-1 251 W Standard Methods of Tests of Fire Resistance of Building Construction and Materials... 251-1 253 P Standard Method of Test for Critical Radiant Flux of Floor Covering Systems Using a Radiant Heat Energy Source... 253-1 262 P Standard Method of Test for Flame Travel and Smoke of Wires and Cables for Use in Air-Handling Spaces... 262-1 265 P Standard Methods of Fire Tests for Evaluating Room Fire Growth Contribution of Textile Coverings on Full Height Panels and Walls... 265-1 (To be Retitled as Standard Methods of Fire Tests for Evaluating Room Fire Growth Contribution of Textile or Expanded Vinyl Wall Coverings on Full Height Panels and Walls) 285 P Standard Fire Test Method for Evaluation of Fire Propagation Characteristics of Exterior Non-Load-Bearing Wall Assemblies Containing Combustible Components... 285-1 286 P Standard Methods of Fire Tests for Evaluating Contribution of Wall and Ceiling Interior Finish to Room Fire Growth... 286-1 418 P Standard for Heliports... 418-1 730 P Guide for Premises Security... 730-1 731 P Standard for the Installation of Electronic Premises Security Systems... 731-1 901 R Standard Classifications for Incident Reporting and Fire Protection Data... 901-1 921 P Guide for Fire and Explosion Investigations... 921-1 1192 P Standard on Recreational Vehicles... 1192-1 1194 P Standard for Recreational Vehicle Parks and Campgrounds... 1194-1
26 1405 P Guide for Land-Based Fire Fighters Who Respond to Marine Vessel Fires... 1405-1 (To be Retitled as Guide for Land-Based Fire Departments that Respond to Marine Vessel Fires) 1906 C Standard for Wildland Fire Apparatus... 1906-1 1912 P Standard for Fire Apparatus Refurbishing... 1912-1 1977 C Standard on Protective Clothing and Equipment for Wildland Fire Fighting... 1977-1 1984 N Standard on Respirators for Wildland Fire-Fighting Operations... 1984-1 2001 P Standard on Clean Agent Fire Extinguishing Systems... 2001-1 TYPES OF ACTION P Partial Revision C Complete Revision N New Document R Reconfirmation W Withdrawal
27 2010 Fall Revision Cycle ROP Committees Reporting Type Action Page No. Automatic Sprinkler Systems Foam-Water Sprinklers 16 Standard for the Installation of Foam-Water Sprinkler and Foam-Water Spray Systems P 16-1 Boiler Combustion System Hazards 85 Boiler and Combustion Systems Hazards Code P 85-1 Commissioning Fire Protection Systems 3 Standard on Commissioning and Integrated Testing of Fire Protection and Life Safety Systems N 3-1 Fire and Emergency Services Protective Clothing and Equipment Respiratory Protection Equipment 1984 Standard on Respirators for Wildland Fire-Fighting Operations N 1984-1 Wildland Fire Fighting Protective Clothing and Equipment 1977 Standard on Protective Clothing and Equipment for Wildland Fire Fighting C 1977-1 Fire Department Apparatus 1906 Standard for Wildland Fire Apparatus C 1906-1 1912 Standard for Fire Apparatus Refurbishing P 1912-1 Fire Investigations 921 Guide for Fire and Explosion Investigations P 921-1 Fire Reporting 901 Standard Classifications for Incident Reporting and Fire Protection Data R 901-1 Fire Service Training 1405 Guide for Land-Based Fire Fighters Who Respond to Marine Vessel Fires P 1405-1 Fire Tests 251 Standard Methods of Tests of Fire Resistance of Building Construction and Materials W 251-1 253 Standard Method of Test for Critical Radiant Flux of Floor Covering Systems P 253-1 Using a Radiant Heat Energy Source 262 Standard Method of Test for Flame Travel and Smoke of Wires and Cables P 262-1 for Use in Air-Handling Spaces 265 Standard Methods of Fire Tests for Evaluating Room Fire Growth Contribution of P 265-1 Textile Coverings on Full Height Panels and Walls 285 Standard Fire Test Method for Evaluation of Fire Propagation Characteristics of P 285-1 Exterior Non-Load-Bearing Wall Assemblies Containing Combustible Components 286 Standard Methods of Fire Tests for Evaluating Contribution of Wall and Ceiling Interior Finish to Room Fire Growth P 286-1 Gaseous Fire Extinguishing Systems 12 Standard on Carbon Dioxide Extinguishing Systems P 12-1 2001 Standard on Clean Agent Fire Extinguishing Systems P 2001-1 Helicopter Facilities 418 Standard for Heliports P 418-1 Hydrogen Technology 2 Hydrogen Technologies Code N 2-1 Industrial and Medical Gases 51A Standard for Acetylene Cylinder Charging Plants P 51A-1 Liquid Fuel Burning Equipment 31 Standard for the Installation of Oil-Burning Equipment P 31-1 Manufacture of Organic Coatings 35 Standard for the Manufacture of Organic Coatings P 35-1 National Electrical Code Electrical Equipment of Industrial Machinery 79 Electrical Standard for Industrial Machinery P 79-1
28 Premises Security 730 Guide for Premises Security P 730-1 731 Standard for the Installation of Electronic Premises Security Systems P 731-1 Recreational Vehicles 1192 Standard on Recreational Vehicles P 1192-1 1194 Standard for Recreational Vehicle Parks and Campgrounds P 1194-1 Safety to Life Assembly Occupancies and Membrane Structures 102 Standard for Grandstands, Folding and Telescopic Seating, Tents, and Membrane Structures P 102-1 Textile and Garment Care Processes 32 Standard for Drycleaning Plants P 32-1 Water Additives for Fire Control and Vapor Mitigation 18A Standard on Water Additives for Fire Control and Vapor Mitigation P 18A-1
29 COMMITTEE MEMBER CLASSIFICATIONS 1,2,3,4 The following classifications apply to Committee members and represent their principal interest in the activity of the Committee. 1. M Manufacturer: A representative of a maker or marketer of a product, assembly, or system, or portion thereof, that is affected by the standard. 2. U User: A representative of an entity that is subject to the provisions of the standard or that voluntarily uses the standard. 3. IM Installer/Maintainer: A representative of an entity that is in the business of installing or maintaining a product, assembly, or system affected by the standard. 4. L Labor: A labor representative or employee concerned with safety in the workplace. 5. RT Applied Research/Testing Laboratory: A representative of an independent testing laboratory or independent applied research organization that promulgates and/or enforces standards. 6. E Enforcing Authority: A representative of an agency or an organization that promulgates and/or enforces standards. 7. I Insurance: A representative of an insurance company, broker, agent, bureau, or inspection agency. 8. C Consumer: A person who is or represents the ultimate purchaser of a product, system, or service affected by the standard, but who is not included in (2). 9. SE Special Expert: A person not representing (1) through (8) and who has special expertise in the scope of the standard or portion thereof. NOTE 1: Standard connotes code, standard, recommended practice, or guide. NOTE 2: A representative includes an employee. NOTE 3: While these classifications will be used by the Standards Council to achieve a balance for Technical Committees, the Standards Council may determine that new classifications of member or unique interests need representation in order to foster the best possible Committee deliberations on any project. In this connection, the Standards Council may make such appointments as it deems appropriate in the public interest, such as the classification of Utilities in the National Electrical Code Committee. NOTE 4: Representatives of subsidiaries of any group are generally considered to have the same classification as the parent organization.
FORM FOR COMMENT ON NFPA REPORT ON PROPOSALS 2010 FALL REVISION CYCLE FINAL DATE FOR RECEIPT OF COMMENTS: 5:00 pm EDST, March 5, 2010 For further information on the standards-making process, please contact the Codes and Standards Administration at 617-984-7249 or visit www.nfpa.org/codes. For technical assistance, please call NFPA at 1-800-344-3555. FOR OFFICE USE ONLY Log #: Date Rec d: Please indicate in which format you wish to receive your ROP/ROC electronic paper download (Note: If choosing the download option, you must view the ROP/ROC from our website; no copy will be sent to you.) Date 8/1/200X Name John B. Smith Tel. No. 253-555-1234 Company Street Address 9 Seattle St. City Tacoma State WA Zip 98402 ***If you wish to receive a hard copy, a street address MUST be provided. Deliveries cannot be made to PO boxes. Please indicate organization represented (if any) Fire Marshals Assn. of North America 1. (a) NFPA Document Title National Fire Alarm Code NFPA No. & Year NFPA 72, 200X ed. (b) Section/Paragraph 4.4.1.1 2. Comment on Proposal No. (from ROP): 72-7 3. Comment Recommends (check one): new text revised text deleted text 4. Comment (include proposed new or revised wording, or identification of wording to be deleted): [Note: Proposed text should be in legislative format; i.e., use underscore to denote wording to be inserted (inserted wording) and strike-through to denote wording to be deleted (deleted wording).] Delete exception. 30 Email 5. Statement of Problem and Substantiation for Comment: (Note: State the problem that would be resolved by your recommendation; give the specific reason for your Comment, including copies of tests, research papers, fire experience, etc. If more than 200 words, it may be abstracted for publication.) A properly installed and maintained system should be free of ground faults. The occurrence of one or more ground faults should be required to cause a trouble signal because it indicates a condition that could contribute to future malfunction of the system. Ground fault protection has been widely available on these systems for years and its cost is negligible. Requiring it on all systems will promote better installations, maintenance and reliability. 6. Copyright Assignment (a) I am the author of the text or other material (such as illustrations, graphs) proposed in the Comment. (b) Some or all of the text or other material proposed in this Comment was not authored by me. Its source is as follows: (please identify which material and provide complete information on its source) I hereby grant and assign to the NFPA all and full rights in copyright in this Comment and understand that I acquire no rights in any publication of NFPA in which this Comment in this or another similar or analogous form is used. Except to the extent that I do not have authority to make an assignment in materials that I have identified in (b) above, I hereby warrant that I am the author of this Comment and that I have full power and authority to enter into this assignment. Signature (Required) PLEASE USE SEPARATE FORM FOR EACH COMMENT Mail to: Secretary, Standards Council National Fire Protection Association 1 Batterymarch Park Quincy, MA 02169-7471 OR Fax to: (617) 770-3500 OR Email to: proposals_comments@nfpa.org 11/2/2009
FORM FOR COMMENT ON NFPA REPORT ON PROPOSALS 2010 FALL REVISION CYCLE FINAL DATE FOR RECEIPT OF COMMENTS: 5:00 pm EDST, March 5, 2010 For further information on the standards-making process, please contact the Codes and Standards Administration at 617-984-7249 or visit www.nfpa.org/codes. For technical assistance, please call NFPA at 1-800-344-3555. FOR OFFICE USE ONLY Log #: Date Rec d: Please indicate in which format you wish to receive your ROP/ROC electronic paper download (Note: If choosing the download option, you must view the ROP/ROC from our website; no copy will be sent to you.) Date Name Tel. No. Company Email Street Address City State Zip ***If you wish to receive a hard copy, a street address MUST be provided. Deliveries cannot be made to PO boxes. Please indicate organization represented (if any) 1. (a) NFPA Document Title NFPA No. & Year (b) Section/Paragraph 2. Comment on Proposal No. (from ROP): 3. Comment Recommends (check one): new text revised text deleted text 4. Comment (include proposed new or revised wording, or identification of wording to be deleted): [Note: Proposed text should be in legislative format; i.e., use underscore to denote wording to be inserted (inserted wording) and strike-through to denote wording to be deleted (deleted wording).] 31 5. Statement of Problem and Substantiation for Comment: (Note: State the problem that would be resolved by your recommendation; give the specific reason for your Comment, including copies of tests, research papers, fire experience, etc. If more than 200 words, it may be abstracted for publication.) 6. Copyright Assignment (a) I am the author of the text or other material (such as illustrations, graphs) proposed in the Comment. (b) Some or all of the text or other material proposed in this Comment was not authored by me. Its source is as follows: (please identify which material and provide complete information on its source) I hereby grant and assign to the NFPA all and full rights in copyright in this Comment and understand that I acquire no rights in any publication of NFPA in which this Comment in this or another similar or analogous form is used. Except to the extent that I do not have authority to make an assignment in materials that I have identified in (b) above, I hereby warrant that I am the author of this Comment and that I have full power and authority to enter into this assignment. Signature (Required) PLEASE USE SEPARATE FORM FOR EACH COMMENT Mail to: Secretary, Standards Council National Fire Protection Association 1 Batterymarch Park Quincy, MA 02169-7471 OR Fax to: (617) 770-3500 OR Email to: proposals_comments@nfpa.org 11/2/2009
32 Sequence of Events Leading to Issuance of an NFPA Committee Document Step 1 Call for Proposals Proposed new document or new edition of an existing document is entered into one of two yearly revision cycles, and a Call for Proposals is published. Step 2 Report on Proposals (ROP) Committee meets to act on Proposals, to develop its own Proposals, and to prepare its Report. Committee votes by written ballot on Proposals. If two-thirds approve, Report goes forward. Lacking twothirds approval, Report returns to Committee. Step 3 Report on Proposals (ROP) is published for public review and comment. Report on Comments (ROC) Committee meets to act on Public Comments to develop its own Comments, and to prepare its report. Committee votes by written ballot on Comments. If two-thirds approve, Report goes forward. Lacking twothirds approval, Report returns to Committee. Step 4 Report on Comments (ROC) is published for public review. Association Technical Meeting Notices of intent to make a motion are filed, are reviewed, and valid motions are certified for presentation at the Association Technical Meeting. ( Consent Documents that have no certified motions bypass the Association Technical Meeting and proceed to the Standards Council for issuance.) NFPA membership meets each June at the Association Technical Meeting and acts on Technical Committee Reports (ROP and ROC) for documents with certified amending motions. Step 5 Committee(s) vote on any amendments to Report approved at NFPA Annual Membership Meeting. Standards Council Issuance Notification of intent to file an appeal to the Standards Council on Association action must be filed within 20 days of the NFPA Annual Membership Meeting. Standards Council decides, based on all evidence, whether or not to issue document or to take other action, including hearing any appeals.
33 The Association Technical Meeting The process of public input and review does not end with the publication of the ROP and ROC. Following the completion of the Proposal and Comment periods, there is yet a further opportunity for debate and discussion through the Association Technical Meeting that takes place at the NFPA Annual Meeting. The Association Technical Meeting provides an opportunity for the final Technical Committee Report (i.e., the ROP and ROC) on each proposed new or revised code or standard to be presented to the NFPA membership for the debate and consideration of motions to amend the Report. The specific rules for the types of motions that can be made and who can make them are set forth in NFPA s rules, which should always be consulted by those wishing to bring an issue before the membership at an Association Technical Meeting. The following presents some of the main features of how a Report is handled. The Filing of a Notice of Intent to Make a Motion. Before making an allowable motion at an Association Technical Meeting, the intended maker of the motion must file, in advance of the session, and within the published deadline, a Notice of Intent to Make a Motion. A Motions Committee appointed by the Standards Council then reviews all notices and certifies all amending motions that are proper. The Motions Committee can also, in consultation with the makers of the motions, clarify the intent of the motions and, in certain circumstances, combine motions that are dependent on each other together so that they can be made in one single motion. A Motions Committee report is then made available in advance of the meeting listing all certified motions. Only these Certified Amending Motions, together with certain allowable Follow-Up Motions (that is, motions that have become necessary as a result of previous successful amending motions) will be allowed at the Association Technical Meeting. Consent Documents. Often there are codes and standards up for consideration by the membership that will be noncontroversial and no proper Notices of Intent to Make a Motion will be filed. These Consent Documents will bypass the Association Technical Meeting and head straight to the Standards Council for issuance. The remaining documents are then forwarded to the Association Technical Meeting for consideration of the NFPA membership. What Amending Motions Are Allowed. The Technical Committee Reports contain many Proposals and Comments that the Technical Committee has rejected or revised in whole or in part. Actions of the Technical Committee published in the ROP may also eventually be rejected or revised by the Technical Committee during the development of its ROC. The motions allowed by NFPA rules provide the opportunity to propose amendments to the text of a proposed code or standard based on these published Proposals, Comments, and Committee actions. Thus, the list of allowable motions include motions to accept Proposals and Comments in whole or in part as submitted or as modified by a Technical Committee action. Motions are also available to reject an accepted Comment in whole or part. In addition, Motions can be made to return an entire Technical Committee Report or a portion of the Report to the Technical Committee for further study. The NFPA Annual Meeting, also known as the NFPA Conference & Expo, takes place in June of each year. A second Fall membership meeting was discontinued in 2004, so the NFPA Technical Committee Report Session now runs once each year at the Annual Meeting in June. Who Can Make Amending Motions. NFPA rules also define those authorized to make amending motions. In many cases, the maker of the motion is limited by NFPA rules to the original submitter of the Proposal or Comment or his or her duly authorized representative. In other cases, such as a Motion to Reject an accepted Comment, or to Return a Technical Committee Report or a portion of a Technical Committee Report for Further Study, anyone can make these motions. For a complete explanation, the NFPA Regs should be consulted.