technical committee on commissioning fire …...page 1 of 3 nfpa 3 technical committee on...

Technical Committee on Commissioning Fire Protection Systems

M E M O R A N D U M

DATE: October 8, 2010 TO: Principal and Alternate Members of the Technical Committee on

Commissioning Fire Protection Systems FROM: Matt Klaus, Senior Fire Protection Engineer/NFPA Staff Liaison SUBJECT: AGENDA PACKAGE – NFPA 3 A2011 ROC Meeting ________________________________________________________________________ Enclosed is the agenda for the Report on Comments (ROC) meeting for NFPA 3,

Recommended Practice for Commissioning and Integrated Testing of Fire Protection and

Life Safety Systems. It is imperative that you review the attached comments in advance,

with your ideas and substantiations for your views. 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 Matt Klaus at (617) 984-7448. You can

also reach me via e-mail at [email protected]. We look forward to meeting everyone in

Phoenix, AZ at The Embassy Suites Phoenix-Biltmore.

Table of Contents

Meeting Agenda 3 A2011 ROP Meeting Minutes 4 A2011 Key Dates 11 Staff Liaison Notice 12 A2011 ROP Ballot Statements 17 Public Comments 28 Attachment to ROC Log #3 (Figure A.3.3.16) 45 ROP Draft 48

Technical Committee on Commissioning Fire Protection Systems

ROC Meeting October 19-20, 2010

Embassy Suites Phoenix-Biltmore 2630 East Camelback Road

Phoenix, Arizona, 85016 - (704) 357-1414

AGENDA

Tuesday, October 19, 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 A2011 ROP Meeting Minutes 6. NFPA Staff Liaison Presentation

a. Review of Key Dates in A2011 Cycle b. ECommittee and Document Information Page (DocInfo Page) Tutorial c. ITM Summit Overview

7. Chairman Comments a. Discuss ROP Ballot Comments/Statements

8. Act on Public Comments (A2011 ROC) 9. Generate Committee Comments (if Necessary) 10. Adjourn – 5:00 PM

Wednesday, October 20, 2010

1. Call to Order – 8:30 AM 2. Generate Committee Comments (if Necessary) 3. Committee Discussion on Direction of Document

a. ITM Summit Discussion b. Discuss NFPA 3 vs. ITM vs. Acceptance Testing c. Next Cycle d. Task Group Development

4. Adjourn – 12:00 PM

of 3

NFPA 3 Technical Committee on Commissioning and Integrated Testing of Fire and

Life Safety Systems (CMF-AAA)

ROP Meeting – April 13-15, 2010 The Renaissance Charlotte Suites Hotel

Charlotte, NC 28217

Minutes of Meeting

1. Meeting was called to order at 8:30AM EDT, Tuesday April 13, 2010.

2. Self introductions were made. Scanned attendance list attached. Guests: a. Mark Conroy with Brooks Equipment Co., b. Jim Tidwell of Tidwell Consulting representing Fire Equipment Manufacturer’s

Association, c. Martin Anderson National Operations Siemens Industry, Fire Business Unit, and d. Dan Decker of Safety Systems, Inc. representing Fire Suppression Systems

Association.

3. Show of hands for voting members; 26 were counted.

4. A motion was made and seconded to approve minutes from the July 9-11, 2009 San Francisco, CA ROP meeting. Motion carried.

5. Jonathan Levin, Staff provided a brief presentation for meeting norms and fire evacuation exits.

6. Matthew Klaus, Staff reviewed possible agenda options for this meeting. Four options provided: 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)

7. Chair announced an ITM Summit at NFPA Headquarters in May 2010 that is scheduled and could also affect NFPA 3.

8. Chair invited committee and guests to share comments and discussion regarding the four options provided.

9. Chair noted that Nine members are not present and the ballot voting could change the status of the final votes from this meeting.

10. A motion was made and seconded for option B, Recommended Practice. Vote was taken with majority in favor of this option.

11. A motion was made and seconded for using the Task Group Draft from after the Boston meeting as the Recommended Practice. A motion was called to question. 2/3 vote obtained. Motion failed.

12. A motion was made and seconded for using the ROP Draft to begin agenda. Vote passed to continue with the ROP Draft.

13. Committee agenda set to continue to build the ROP Draft as committee proposals. Staff will backfill ROP and conduct a teleconference at a later date to discuss if committee statements are required.

of 3

14. Jonathan Levin, staff displayed the ROP Draft that was provided in e-mail 4/1/2010, ROP Draft.pdf (This is the Draft that was published AFTER the results of the ROP in San Francisco, CA. It is titled ‘Report on proposals F2010 – Copyright, NFPA’)

15. Motion was made and seconded to remove Units section 1.5. Motion carried.

16. A request was made to staff to make all definitions singular instead of plural.

17. A motion was made to delay Chapter 3 Definitions until late in this meeting and move to chapter 4. Seconded and so moved.

18. Motion made to adjourn at 5pm and seconded.

19. Chair requested to begin at 8am on Wednesday. No objections were made.

20. Wednesday, 4/14/2010. Staff reminded cell phones to be silent. Meeting called to order at 8:10 am.

21. Committee continued working to revise Chapter 4 Commissioning forward.

22. Guest, Mr. Mark Conroy requested the committee to consider ROP log #72, (A.1.3.1). Committee acknowledged the request and commented that the applicability section 1.3.4.1 and A.1.3.4 (future 1.3.5) addresses the issue that is noted in this comment. The smaller systems may not require commissioning, yet the larger installations would be recommended to be commissioned.

23. Committee continued review with Chapter 5. A request was made to separate Chapter 5 into two separate sections; Integrated System and Integrated System Testing Chapters. A task group was assigned to provide the suggested language and also looking at Chapter 6 elimination along with the Task Group report. Task group members consist of Mike DeVore, Craig Studer , Pat Cull, and Paul Dunphy.

24. Dave Boswell joined the committee at 10:40 AM.

25. Thomas Norton (alternate) left 11:30 AM.

26. John Kampmeyer left after lunch.

27. Chapter 9 Periodic Integrated Testing was discussed. Motion was requested and seconded to modify language for section 9.2.3. The committee spent 3 hours debating, thus a task group was created consisting of David Hague, Pascal Pfeiffer, and Rick Kabele to provide suggested text for Chapter 9.

28. Chapter 10. Discussion regarding removing section 10.2. David Lowrey volunteered to validate all text from 10.2 is supported in chapter 4.

29. Chapter 11 discussed, then Forms. Committee agreed to delete the Acceptance Test Checklist and Plan Review Checklist to prevent duplication of other Standards.

30. Task groups meeting tonight to begin tomorrow at 8AM; Agenda for Thursday for task group reviews, definitions, annex clean-up, review of action of committee. Tomorrow morning meeting convene at 8AM. Meeting adjourned Wednesday at 4:47PM.

31. Meeting called to order 8:00AM, Thursday 4/15/10.

32. Staff displayed possible ROC dates. A request was made for Phoenix, week of Sept. 20, several other dates were discussed. Week of October 18-22, 2010. Art Black offered Monterrey, CA as a venue. Denver was suggested. San Antonio was also suggested.

33. A request was made to review schedule. Staff will request use of TCC dates for Ballots. Ballots will be requested to go out April 23 and return by May 14, 2010. This will be a ballot of all the previous proposals (as we voted at this meeting to delay) and the vote of changing this Standard to a Recommended Practice. There are 33 current members and requires a 2/3 vote. A conference call will be held next week. There will be one proposal that includes the entire document as we modified at this meeting. Alternates encouraged to vote.

of 3

34. A review was made for the Annex, Warranty review addition.

35. Chapter 5,6 task group reported by Mike DeVore. Chapter 5 was suggested to be as Integrated Systems Commissioning followed by Chapter 6 Integrated System Testing.

36. A request was made to staff to send the committee the entire document with changes in a Word document. Staff prefers not to do this due to the possibility of copies being distributed.

37. Discussion regarding adding Integrated Testing Agent into the commissioning team in Chapter 4. It was added to the list with an annex note.

38. Chapter 6 review was completed.

39. Chapter 9 task group work was reported by David Hague. The committee coordinated this with Chapter 6 as well.

40. Chapter 10 was requested to move to after Chapter 3 and before Commissioning. Staff recommended strongly to double check cross references.

41. Definitions were then discussed. Added Integrated Testing Agent, Active Fire Protection Systems, Passive Fire Protection Systems, NFPA 3 definition is appropriate for Fire Protection System, modification of Integrated System, Integrated Testing. Created Installation Contractor, Stakeholder from NFPA preferred terms, Integrated Test Plan.

42. Annex A was discussed, A.4.1.1.1 matrix of Cx Roles and Responsibilities was modified. Figure A.4.1.3.A has an arrow in the incorrect direction between Design Reviews and Update OPR and BOD. Staff will review Annex A and suggested the committee to verify the relevance to the main body.

43. Annex B was determined to be removed.

44. Title of Annex C was revised.

45. Added introductory language for Annex D Sample forms.

46. Staff needs a couple of days to complete the document. Teleconference was suggested to go through the proposals review to correct any issues or create committee statements.

47. Motion to request chair to coordinate this work with staff. Motion was seconded and thus teleconference may not be required.

48. Ballots need to be issued by the 23rd, Return of Proposals required by Ballots due by May 14th.

49. The committee thanked and congratulated Jonathan Levin’s work with our committee.

50. Jonathon introduced the committee to Matthew Klaus and noted that he would be continuing as NFPA 3 staff representative.

51. Meeting adjourned 1:53 PM, Thursday 4/15/2010.

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

Note from the NFPA Staff

Dear Committee Members:

We are very pleased that you will be participating in the processing of the first edition of NFPA 3. Development of the document 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 Public Comments Submitted Under A2011 Cycle NFPA Annual Directory NFPA Manual of Style Prepared Committee Comments (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 Comments Only one posting of comments 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 to this Agenda Package. If you have trouble accessing the website please contact Patti Mucci at [email protected]. Please bring the comments 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 Comments Comments Requiring Committee Actions All public comment must be acted upon. If a comment does not comply with Section 4.4.5 of the NFPA Regulations Governing Committee Projects (an incomplete comment), 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.

Committee Actions The following are the actions permitted by the Regulations Governing Committee Projects for disposition of comments.

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 comment is rejected by the committee. If the principle or intent of the comment is acceptable in whole or in part, the comment should not be rejected, it should be accepted in principle or accepted in principle in part. A complete reason for rejection of the comment must be supplied in the committee statement.

Accept in Principle Accept the comment 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 comment, the committee action may simply indicate "Accept in Principle" but reference should then be made in the committee statement to the specific comment detailing the action.

Accept in Part If part of a comment is accepted without change and the remainder is rejected, the comment should be "Accepted in Part." The committee action must indicate what part was 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 comment 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 comment simply because it accepted a different comment on the same subject. Reference in the committee statement to another committee action is inappropriate unless the referenced comment contains all of the applicable technical justification for the action. If the rejection or change was for the same reason that another comment was rejected or changed, the committee statement may refer to that comment giving the same reason for rejection or change. Please verify that cross references to other comments 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 comment 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. The committee statement on a comment that is accepted in part should indicate specifically why that part of the comment 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 comment 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 comments 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 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.

Circulation Explanation Report for CMF-AAA Proposals Monday, October 4, 2010Document # 3

3-1 Entire Document (Log # CP20 )

Negative

Fremis, B. Although I agree somewhat with the Committee's intent of making the NFPA 3 document a"Recommended Practice" rather then a "Standard", we are dealing with 2 completely different subject matterswithin this document (i.e. Commissioning versus Integrated Systems Testing). I recommend that the NFPA 3Chair ask the NFPA Standards Council to allow the NFPA 3 Committee to create 2 separate documents. Thefirst document would be a Standard on Integrated Systems Testing. The second document would be aRecommended Practice on Commissioning.

Gentile, K. The language requirements of the manual of style for a "recommended practice" result in thefollowing three critical deficiencies in the document:1. The original committee direction was to provide a document to be use with other building systemcommissioning requirements. The required text would make all fire and life safety system commissioningrequirements optional and unenforceable. The other building system commissioning documents requireactions to be performed and are enforceable.2. The required text for a "recommended practice" would permit commissioning performed on an item by itembasis selected by the commissioning agent.3. The "recommend practice" does not address the need and request of many jurisdictional authorities for anenforceable standard that is suitable for jurisdictional adoption.A final two points,a. I do not agree that a vote for a "standard" would necessarily delay completion by a cycle and if it should, theresulting document would be subject to further review and improvement.b. By my count, this is the fourth vote on this issue and the previous three were for a standard. If thecommittee is to maintain credibility, procedural decisions should be recognized.

Pfeiffer, P. As a recommended practice, the document is not enforceable. As a consequence, the integratedtesting part becomes a recommendation. The draft for the integrated testing issued at Boston (a.k.a. option C)is in my opinion a better option for the first release of this document.

Affirmative with Comment

Clarke, B. After significant review, I have voted to approve the committee proposal to change the NFPA 3document from a standard to a recommended practice. However, I do not feel this document, as such, will bestserve the fire protection community we all proudly work to improve until converted back to a standard (whichI will vigorously pursue in the next cycle after initial release). I understand, with so much apparent industryconcern over this documents intent and impact, the “path of least resistance” to publication is conversion to arecommended practice. However, I do not feel the majority of these concerns are justified and, many are basedon misinformation about NFPA 3's true intent and flexibility in real application. And, while first publicationsof NFPA documents as recommended practices may be customary to allow time for “industry evaluation,” Istrongly feel the release of NFPA 3 as a recommended practice will only deliver a universally unenforceddocument that is primarily ignored in the public sector but that is clearly needed for adoption and enforcementin our industry today.

1


Edwards, R. I was sincerely disappointed that the full committee was not present to vote the issue of standardversus recommended practice. Once the new document has been published, I hope the committee willimmediately embark upon creating two documents: one standard with enforceable language addressingintegrated testing and a recommended practice addressing the commissioning process. Although I disagreewith the vote for recommended practice, this position is without the knowledge from the meeting where thediscussions and arguments regarding the matter occurred; therefore, I am voting in the affirmative because Ibelieve in the process and the work this committee has done.

3-4 Entire Document (Log # 100 )

Negative

Fremis, B. The term "Fire Commissioning Agent" should be replaced with "Fire Commissioning Authority".The use of the term "agent" has a legal context to it and should not be used in this document. OtherCommissioning documents, such as ASHRAE Guideline 0, have already come to this realization and havechanged the term "agent" to "authority" throughout all their documents.

3-5 Title (Log # 105 )

Negative

Fremis, B. Although I agree somewhat with the Committee's intent of making the NFPA 3 document a "Recommended Practice"rather then a "Standard", we are dealing with 2 completely different subject matters within this document (i.e. Commissioning versusIntegrated Systems Testing). I recommend that the NFPA 3 Chair ask the NFPA Standards Council to allow the NFPA 3 Committeeto create 2 separate documents. The first document would be a Standard on Integrated Systems Testing. The second documentwould be a Recommended Practice on Commissioning.

Gentile, K. Refer to Rationale for proposal 3-1.

3-6 Title (Log # 155 )


Hulett, J. Mr. Bilbo recommended this document to be a guide instead of a standard. By committee voteproposal 3-1 (Log #CP20) changed the document to recommended practice. I recommend this proposal beaccepted in principal.

3-7 Chapter 1 (Log # CP21 )

Negative


Gentile, K. The proposal is predicated upon approval as a "recommended practice". If the document status ofa standard is retained, the proposal must be rejected.

Pfeiffer, P. See my Explanation of Negative Vote on Proposal 3-1 (Log #CP1).

3-10 1.3.1, C.2.4, and D.2 (Log # 106 )

Negative

Gentile, K. NFPA 10 includes references to fire extinguisher tamper monitoring devices which should beconsidered in commissioning.

2


Tabet, R. While manual fire extinguishers are not "systems", they are "equipment" typically specified andinstalled when required by other standards. The process of commissioning ensures and documents the correctinstallation of such equipment. (e.g. The correct number, type and location.)

3-14 1.3.1(6) and A.1.3.1(6) (Log # 166 )

Negative

DeVore, M. The action of the committee on Annex 1.3.1(6) changed the submittal from being technicallycorrect to technically incorrect. The systems mentioned in the annex are powered by emergency systems andnot standby systems.

3-17 1.3.1(9) (Log # 107 )

Negative

Tabet, R. It is beyond the scope of this document to assess cooking operations. This document would pertainto the commissioning and integrated testing of fire protection systems associated with cooking equipment.Language should read as follows:(9) Systems associated with commercial cooking equipment.

3-22 1.6 (Log # 69 )

Negative

Kasiski, R. New Technology should be included even though a Recommended Practice. Guidance is neededfor those areas for which there are no NFPA Standards. As example, currently there is a listed fire protectionsystem which is a uses a combination of water vapor and inert gas (hybrid fire ext. system) for fireextinguishment. It is neither covered by NFPA 750 or NFPA 2001. The inclusion of guidance for NewTechnology would address this deficiency for an individual fire protection system included as part of aCommissioning Plan. A Comment will be submitted during the ROC phase.

3-24 Chapter 3 Definitions (Log # CP22 )

Negative

Frable, D. I cannot support the Technical Committee actions regarding the proposed definitions specified in3.3.21 (i.e., acceptance testing, integrated testing, pre-functional testing, and preliminary testing). I believe theproposed 4 new "testing" terms and associated definitions have complicated the subject matter and will lead toconfusion in the field when performing Cx. For example, the proposed new terms "pre-functional testing" and"preliminary testing" are defined similar in nature and probably will be used interchangeably in the field whichmay possibly lead to duplicate testing without benefit. In addition, it appears the intent of the proposeddefinition for "integrated testing" is to assess whether the fire and life safety systems function and operate perthe design and code requirements when interconnected to other systems; however, it uses the terms"conformance with the fire protection and life safety objectives". It is recommended that the TechnicalCommittee re-evaluate the subject defined "testing" terms and possibly use NFPA 72 for guidance.



3-39 3.3.17 Registered Design Professional (RDP) (Log # 32 )

3



Tabet, R. The language modification incorporated in CP22 replaced the word "his" with "their" to make thestatement gender neutral. The Committee statement is inaccurate with respect to the text edits made.

3-41 3.3.17.1 Integrated System (Log # 41 )


Fremis, B. Although the proposed definition is adequate, I would have preferred that the definition of"Integrated System" that was created during the "unofficial NFPA 3 Meeting" held in February 2010 was usedinstead. The definition of "Integrated System" proposed at the February 2010 meeting was as follows, "Acombination or group of systems that are either physically connected or separate from one another but that arerequired to operate together as a whole to achieve overall fire protection and life safety objectives.

Tabet, R. The text edits made modify the submitter's proposal. The committee action should reflect "Acceptin Principle" or the text edits should read "A combination or group of systems that ..."

3-43 3.3.18.2 Fire Protection System and 3.3.18.3 Life Safety System (Log # 38 )

Tabet, R. Editorial change necessary to correct numbering.

3-44 3.3.19.2 Interconnected System and Chapter 6 (Log # 83 )

Negative

Fremis, B. I don't quite understand why the term "Interconnected" still needs to be used. My interpretation ofthe definition of "Integrated System" within Proposal 3-41 implies that systems can be either physically ornon-physically connected to one another.


Negative


The term "Integrated Testing Agent" should be replaced with "Integrated Testing Coordinator". The use of theterm "agent" has a legal context to it and should not be used in this document.

Furthermore, I do not see the need to include any references or requirements within this section for "Third-party test entities".



Tabet, R. Editorial errors in Section 4.1 need to be corrected.

3-57 Figure 4.1.3(a) and (c) (Log # 2 )


Tabet, R. The Committee's proposed actions reflected in the Committee Statement were not incorporated intothe document edits. Corrective changes relative to direction of arrows in flow diagram were not made.

3-58 4.2.2 (Log # 96 )

4


Negative

Fremis, B. The term "Fire Commissioning Agent" should be replaced with "Fire Commissioning Authority".The use of the term "agent" has a legal context to it and should not be used in this document. OtherCommissioning documents, such as ASHRAE Guideline 0, have already come to this realization and havechanged the term "agent" to "authority" throughout all their documents.Furthermore, I do not see the need to include any references or requirements within this section for "Third-party test entities".

Pfeiffer, P. I believe qualifications for third parties need clarifications to cope with international situations andregulations (10.2.6.2). Third parties should have understanding for each individual systems as well as theintegrated system (10.2.6.1).

3-59 4.2.2 and A.4.2.2 (Log # 179 )

Negative

Frable, D. Though similar language is included in A.5.2.1.2, I believe it also belongs in A.4.2.2 since the 4.2.2 discusses theinstallation contractor. In addition, it should be noted that A.5.2.1.2 isn't the right place anyway, as A.5.2.2.1 discusses contractorsand manufacturer's reps.

3-62 4.2.2.3 (Log # 97 )



3-63 4.2.2.3 (Log # 120 )



3-66 4.2.2.4 (Log # 98 )

Negative

Fremis, B. I do not see the need to include any references or requirements within this section for "Third-partytest entities".

3-71 4.2.2.5 (Log # 124 )

Abstain

Pfeiffer, P. Factory test documentation may still be necessary. This material should be moved to annexsections

3-82 4.2.2.9 (New) (Log # 91 )

Negative

Fremis, B. I do not see the need to include any references or requirements within this section for "InsuranceRepresentatives".

Pfeiffer, P. I believe the proposal should be rewritten to include the property insurer of owner and review anypossible issues coping with international practice as well.

5


3-85 4.2.2(2) and (10) (Log # 178 )

Negative

Frable, D. It is our belief that the Committee's action on proposal 3-85 should have been "accept in principal"and not "reject". The only reason submitter requested the terms be deleted was because they were notaddressed elsewhere in the chapter. The new proposed language addresses the submitter's request.

3-86 4.2.3.3 and 9.2.3 (Log # 11 )

Negative


3-102 4.3.2.2 (Log # 162 )

Negative

Fremis, B. Firstly, the text within 4.3.2.2 (2) needs to be modified for possible use by other jurisdictions otherthen the U.S. Secondly, having a sustainable design should never affect fire and life safety systems and Irecommend that 4.3.2.2 (4) be removed.


Negative


3-141 Chapter 6 (Log # 85 )

Negative

Fremis, B. I don't quite understand why we still need Chapter 6. My interpretation of the definition of"Integrated System" within Proposal 3-41 implies that systems can be either physically or non-physicallyconnected to one another.


Negative

Frable, D. Overall, I have no problems with the intent of the actions taken by the Technical Committee inProposal 3-142. However, as currently proposed in 6.2.2.2 (9), 6.4.1 (1), 6.4.1 (9), 6.4.1 (13), the term "test"has not be specified as to which type of "test" is required (e.g., acceptance test, integrated test, pre-functionaltest, or preliminary test). Therefore, it is recommended that the Technical Committee re-valuate this sectionand make the appropriate revisions to ensure clarity in the field.

Fremis, B. Although I agree somewhat with the Committee's intent of including an Integrated Systems chapterwithin the NFPA 3 document, we are dealing with 2 completely different subject matters within this document(i.e. Commissioning versus Integrated Systems Testing). I recommend that the NFPA 3 Chair ask the NFPAStandards Council to allow the NFPA 3 Committee to create 2 separate documents. The first document wouldbe a Standard on Integrated Systems Testing. The second document would be a Recommended Practice onCommissioning.

6



3-143 Chapter 7 (Log # 23 )

Abstain

Pfeiffer, P. The deleted material by the proposal should be moved to annex material to better state what is theintention of the committee when considering passive systems.


Negative

Frable, D. For consistency, it is recommended that the Technical Committee revise 7.4.2 to reflect the actionsthey took in Proposal 3-131.

Fremis, B. Although I agree somewhat with the Committee's intent of including an Integrated Systems chapterwithin the NFPA 3 document, we are dealing with 2 completely different subject matters within this document(i.e. Commissioning versus Integrated Systems Testing). I recommend that the NFPA 3 Chair ask the NFPAStandards Council to allow the NFPA 3 Committee to create 2 separate documents. The first document wouldbe a Standard on Integrated Systems Testing. The second document would be a Recommended Practice onCommissioning.


3-146 7.1 (Log # 33 )


Pfeiffer, P. Smoke vents should be included in the passive systems to be considered in integrated testingespecially in those areas sich as Europe where smoke vents are massively used and prescribed by AHJ andwhich might interact with other fire protection systems such as sprinkler systems.


Negative



Negative

DeVore, M. The committee has not considered any evidence that the period of time specified in section 9.3.3 correlateswith the performance or reliability of integrated systems. The only stated reason for the 5 year test requirement isbecause some committee members think 5 years is a long time, but it is not a long time in the life of most fire protectionsystems. As proposed section 9.3.3 would apply to integrated systems including everything from an automatic sprinklersystem or kitchen hood system monitored by a fire alarm system to a complicated system that would need retro-commissioning to determine the design intent and create test requirements. If not retro-commissioning an integratedsystem, then NFPA 3 is either redundant or in conflict with the document where the requirement resides.

7


Frable, D. I cannot support the Technical Committee action. For example, 9.3.1 appears to be in conflict with9.3.1.1, 9.3.2 (4) and 9.3.3. Paragraph 9.3.1 states that the intervals for all integrated testing should beapproved by the AHJ; Paragraph 9.3.1.1 states the interval for integrated testing should be completed inaccordance with the Cx plan (which has been approved by AHJ); Paragraph 9.3.2 (4) for systems not Cx'd,intervals for integrated testing should be approved by AHJ (see 9.3.1); and Paragraph 9.3.3 where integratedtests are not performed, the intervals for integrated testing should not exceed 5 years (see 9.3.1). In addition,referenced paragraphs 9.4.1 and 9.4.2 do not exist. Also, the current proposed prescriptive requirement for theintervals for integrated testing has not been technically justified or shown that they are equivalent in attemptingto achieve the same objective stated in the Cx plan. Lastly, based on the actions the Technical Committee tookon Proposals 3-167 and 3-170, paragraph 9.3.3 should be deleted.

Fremis, B. Although I agree somewhat with the Committee's intent of including an Integrated TestingFrequency chapter within the NFPA 3 document, we are dealing with 2 completely different subject matterswithin this document (i.e. Commissioning versus Integrated Systems Testing). I recommend that the NFPA 3Chair ask the NFPA Standards Council to allow the NFPA 3 Committee to create 2 separate documents. Thefirst document would be a Standard on Integrated Systems Testing. The second document would be aRecommended Practice on Commissioning.



Kabele, R. 9.3.1.1 incorrectly references ". . . the commissioning process of Chapter 4 . . ." whereas this reference should be statedas ". . . the commissioning processes Chapter 5 and Chapter 6 . . ."9.3.3 incorrectly references sections 9.4.1 and 9.4.2 that do not exist in this version. The correct references should be to sections9.3.1 and 9.3.2 respectively.9.3.5 incorrectly references Chapter 6, whereas that reference should be to Chapter 7.9.4 incorrectly references Chapter 6, whereas that reference should also be to Chapter 7.

Pfeiffer, P. Editorial change. 9.3.3* should read as follows : 9.3.3* Where integrated tests are not performed in accordance with9.4.19.3.1 or 9.4.29.3.2, the integrated test interval should not exceed five years.

3-164 9.1.1 (Log # 29 )

Negative

Fremis, B. Refer to my comment regarding Proposal 3-163.

3-165 9.2.2 (Log # 37 )

Negative

Kampmeyer, J. The justification of the rejection read "Operational and maintenance manuals also deal with individual systemsnot just interconnected and integrated systems." However, the scope of NFPA 3 covers commissioning and integrated testing ofsystems. We discussed that the testing of independent system should be covered in the standards for those systems. Therefore theO&M manuals covered in NFPA 3 should cover the documentation of the individulal systems only to the extent that they are part ofthe integrated system.

3-166 9.2.3 (Log # 57 )

Negative

Frable, D. Based on the actions the Technical Committee has taken on Proposal 3-163; the final action shouldbe "Reject" since it appears the action taken by the Technical Committee does not meet the intent of thesubmitter.

Fremis, B. See my Explanation of Negative on Proposal 3-164 (Log #29).

3-167 9.2.3 (Log # 171 )

8


Negative

Frable, D. Based on the actions the Technical Committee has taken on Proposal 3-163; the final action shouldbe "Accept in Principal in Part" since it appears the action taken by the Technical Committee does not meet theintent of the submitter. Also, Paragraph 9.3.1.10 is referenced but does not exist.


3-168 9.2.3, 9.2.4, A.9.2.3, and A.9.2.4 (Log # 35 )

Negative


3-169 9.2.4 (Log # 56 )

Negative


3-170 9.2.4(4) (Log # 170 )

Negative

Frable, D. See comment on Proposal 3-167.


3-171 9.6 (Log # 169 )

Negative


3-174 10.2 (Log # 102 )

Negative

Frable, D. See comment on Proposal 3-144.



3-181 Annex A (Log # CP30 )

Negative

Gruner, K. A.4.2.1.1 still has text referring to 'business relationships' whereas the committee accepted inprinciple 3-204, where the submitter requested replacement of 'business relationships' with 'financial interest'.


9


McDaniel, M. Revise A.3.3.19.2 to read: A.3.3.19.1 Integrated System. An integrated system containssystems that are physically connected and others that are not. An integrated system can contain a combinationof fire protection and life safety systems and non-fire protection and life safety systems (i.e. building systemssuch as elevators, HVAC systems, automatic door closures, etc.) that may or may not be physically connected,but that are required to operate together as a whole to achieve overall fire protection and life safety objectives.For example, a smoke control system is often activated by water flow in a sprinkler system but the sprinkler

system is not physically connected to the HVAC system. The physical connection is from the sprinkler systemto the fire alarm system and then to the building automation system.Further examples of integrated systems include is are the need for wall integrity when using total flooding

suppression agents or the need for automatic door closures that are to close upon activation of smoke controlsystems or stair pressurization systems.

3-183 A.3.3.3.2 (Log # 55 )



3-202 A.9.1.2 (Log # 168 )

Negative

Frable, D. I cannot support the Technical Committee action. We believe based on the proposed new definitionfor "integrated testing" that the intent of integrated testing is to assess whether the fire safety systems functionand operate per the design and code requirements when interconnected to other building systems. In otherwords, ensuring "the conformance with the fire protection and life safety objectives" means the same thing as"function and operate per the design and code requirements when interconnected to other building systems."

3-203 A.10.2.1.1 (Log # 36 )

Negative

Gruner, K. The key to the commissioning agent responsibility is to remain impartial and unbiased. Abusiness relationship does not have to prevent the commissioning agent from being impartial/unbiased. In fact,they could be MORE knowledgeable of specific operations/capabilities. I don't agree that a 3rd party should berecommended for a smaller installation. I prefer/encourage use of one of the equipment supplier's ascommissioning agent if they are experienced in this process. This would not add as must cost and could stillaccomplish an integrated testing or periodic testing to meet the requirements.

3-204 A.10.2.1.1 (Log # 50 )

Negative

Fremis, B. Firstly, the term "Fire Commissioning Agent" should be replaced with "Fire CommissioningAuthority". The use of the term "agent" has a legal context to it and should not be used in this document.Other Commissioning documents, such as ASHRAE Guideline 0, have already come to this realization andhave changed the term "agent" to "authority" throughout all their documents.Furthermore, although this is Annex material I do not believe that we should be stipulating how many yearsexperience that the Fire Commissioning Authority must have in the body of the Annex material.


10


Gruner, K. It appears that the committee Accepted in Principal, but did not implement the suggested 'financialinterest' wording in proposal 3-181, log CP30.

11

Report on Comments – June 2011 NFPA 3_______________________________________________________________________________________________3- Log #1

_______________________________________________________________________________________________David R. Hague, Liberty Mutual Property

3-16Revise Section 1.3.1(8) and related annex material to read as follows:

This recommended practice applies to passive and active fire protection and life safety equipment and systemsincluding, but not limited to, the following:(1)* Infrastructure supporting the building fire protection and life safety systems within the boundaries of the project(2) Fixed fire suppression and control systems(3) Fire alarm systems(4) Emergency communications systems (ECS)(5) Smoke control and management systems(6)* Normal, emergency, and standby power systems(7) Explosion prevention and control systems(8)* Fire-resistant and smoke-resistant assemblies including firestopping(9) Commercial cooking operations(10) Elevator systems(11)* Means of egress systems and components(12) Other systems or installations integrated or connected to a fire or life safety system, such as, but not limited to,

access control, critical processes, and hazardous operationsExamples include, but are not limited to, floor ceilings and roof decks, doors, windows, barriers, walls,

protection by a firestop system or device for through-penetrations and membrane penetrations, and other fire andsmoke control assemblies.

Firestopping should be included because it is a frequently over-looked aspect of rated assemblies.

_______________________________________________________________________________________________3- Log #2


3-172Remove reference to Chapter 11 (reserved).

Text for chapter 11 can be added in subsequent revision cycles, there is no need to reserve a chapterthat is not mandatory as required from the NFPA Manual of Style. Chapters such as Chapters 2 ReferencedPublications or Chapter 3 definitions may be reserved if no referenced publications or definitions are included in theproposed document. Since there is no title for Chapter 11 in addition to no content a reserved chapter is not needed.

1Printed on 9/13/2010



3-24Add a new form "A.3.3.16(b) Sequence of Operation test Form".

***Insert Figure A.3.3.16(b) Here***

A test form to document the interoperations established in the Sequence of Operations or systemmatrix is needed.

_______________________________________________________________________________________________3- Log #4


3-129In Figure A.5.1.2(a) add the word “NO” between “Acceptance” and “Develop Owners Project

Requirements” and reverse the arrow between “Update OPR and BOD” and “Design Reviews”.In Figure A.5.1.2(c) Under Ongoing Commissioning Process, under UpdateOPR and BOD, the task should be stated as “Conduct Training”, not “Accomplish Training”.

In the figure, non-acceptance should result in a return to the predesign phase. In the design phase,when the OPR and BOD are updated, a design review should follow. The proposed text for Figure 4.1.3(c) is editorial.




3-158Revise text as follows:

The integrated testing should be considered as a coordination of the required annual or other periodic fireprotection and life safety systems testing with each other and with those interconnected fire protection and life safetysystems for which no testing is required by other standards. Intervals for integrated testing can be phased or adjustedbased upon the building size and complexity.Re-commissioning should be conducted only if design or installation flaws or other operational issues are revealed

through either the normal inspection, testing and maintenance process or following a design review by a registereddesign professional. Re-commissioning may also be required by the AHJ if changes to the building structure haveoccurred such as expansions, improvements or additions or the building occupancy has changed since the system wasfirst placed into service. Re-commissioning is only performed on systems that were previously commissioned.

Retro-commissioning could be required by the adopted building or fire code, not this recommended practice.The scope is clear that when commissioning is required, this recommended practice should be followed. When thecommissioning process is not required by the AHJ then compliance with this document could be as simple as followingthe inspection testing and maintenance standard for the system installed. On-site surveys should determine if or hownew modifications and repairs reprogram have impacted existing systems or functions and should include thecommissioning process tasks addressed in Section 5.3.Retro-commissioning should be conducted only if design or installation flaws or other operational issues are revealed

through either the normal inspection, testing and maintenance process or following a design review by a registereddesign professional. Retro-commissioning may also be required by the AHJ if changes to the building structure haveoccurred such as expansions, improvements or additions or the building occupancy has changed since the system wasfirst placed into service. Retro-commissioning is only performed on systems that were not previously commissioned.

Guidance on when re-commissioning and retro-commissioning is necessary is needed. These annexsections should be revised to provide that guidance and to specifically point out that re-commissioning andretro-commissioning is not needed unless design or installation flaws are revealed or if changes to the building structureor occupancy occur.

_______________________________________________________________________________________________3- Log #6

_______________________________________________________________________________________________Michael D. DeVore, State Farm Insurance Company

3-7Delete text to read as follows:

1.3.3 Integrated testing should verify and document the following:(1) Performance in accordance with applicable codes and standards(2) Compliance with BOD and OPR(3)* Sequence of operation(4) Installation in accordance with manufacturers’ published instructions(5) Accuracy of diagrams of system interconnections and device locations prior to final acceptance.

The words “prior to final acceptance” appear to be a requirement, which should not appear in theadministrative chapter. Also it makes no difference to the verification and documentation at this point when it is done.The time reference does not match the rest of the list.




3-142Revise text to read as follows:

Construction documents should include a narrative report of the system interactions includingbut not limited to:6.2.1.1 (1) The narrative report should include the sSequence of operations of integrated fire protection or life safety

systems.6.2.1.2 (2) The narrative report should include the pPerformance objectives of system interactions.6.2.1.3 (3) The narrative report should include an aAnalysis of the impact theat interactions will have on the proper

operation of each independent fire protection or life safety system.6.2.1.4* (4) The narrative report in the basis of design should include the oOwners’ expectation of how fire protection or

life safety systems work together.Editorial to eliminate repeat of the same language in every paragraph and to meet the manual of style.

Since 6.2.2 is a heading, then 6.2.1 must have a heading as well.

_______________________________________________________________________________________________3- Log #8



3.3.3.1* Commissioning (Cx). A systematic process that provides documented confirmation that specific andinterconnected fire and life safety building systems function according to the intended design criteria set forth in theproject documents and satisfy the owner’s operational needs, including compliance requirements of anywith applicablelaws, regulations, codes, and standards requiring fire and life safety systems.

Deleted specific and interconnected because including both of these just means “all”. The nextdefinition is commissioning agent who controls the entire commissioning process for the building. Thus commissioning isfor building systems and our piece is fire and life safety. It is not necessary to put “fire and life safety systems” herebecause it is clear from Chapter 1 what this document is about. It doesn’t need to be repeated in the definitions.

_______________________________________________________________________________________________3- Log #9


3-129Delete text as follows:

3.3.3.8 Total Building Commissioning Process. A systematic process, beginning at project inception and extendingthrough the expected life of the building, that provides documented confirmation that all building systems functionaccording to the intended design criteria set forth in the project documents and satisfy the owner’s operational needs,including compliance requirements of any applicable laws, regulations, codes and standards requiring fire and life safetysystems.

Delete definition because it is a duplicate of 3.3.3.1 Commissioning.





5.2.2.5 * The CxA should be responsible for coordinating between the FCxA and the remainder of the total buildingcommissioning team, when applicable.

There is a building commissioning team and the fire protection and life safety commissioning team.The word “total” doesn’t add anything to the meaning of the paragraph.

_______________________________________________________________________________________________3- Log #11


3-24, 3-181, 3-142, 3-144Delete text to read as follows:

3.3.21.3* Pre-Functional Testing. Tests performed prior to acceptance testing to confirm compliance withmanufacturers’ specifications, applicable codes and standards, and the project BODs and OPRs.A.3.3.21.3 Pre-Functional Testing. Such testing should follow the original acceptance test at intervals specified in the

applicable installation or maintenance standard, and may include procedures recommended by the manufacturer’spublished documentation. Pre-functional testing is conducted in preparation for other types of testing. A pre-functionaltesting checklist is often incorporated into the startup process. This testing is typically conducted according to a checklistdeveloped by the FCxA that incorporates manufacturers’ requirements and insures objectives prior to final acceptancetesting. These tests can be complete or partial. In many cases such as with fire pumps per NFPA 20 this is requiredprior to acceptance testing as the coordination of attendance by multiple AHJs can be required.6.2.2.3 The methods for pre-functional and integrated testing should be documented.7.2.1 (3) Completion of pre-functional preliminary tests of integrated systems.

Preliminary testing can occur before acceptance testing or integrated testing. The definition ofpre-functional testing is the same as the definition for acceptance testing. A search of the document shows thatpre-functional testing only occurred twice. In the first instance, it was not needed and in the second case, preliminarytesting fits the meaning of the paragraph.

_______________________________________________________________________________________________3- Log #12



A.1.3.1 This standard recommended practice is not intended to be applied where not unless required by applicablecodes or standards, or other requirements of the owners’ project requirements (OPR) or an AHJ.

Delete “standard” and replace with “recommended practice”, which was missed during the ROPmeeting. Eliminate the double negative, which obscured the meaning of the paragraph. Cleaned up the list of when thisdocument might apply.





A.1.3.1(6) Examples of standby power would include power to Emergency power supply systems to be commissionedinclude but are not limited to those powering the following:(1) smoke control systems(2) stair pressurization systems(3) smoke-proof enclosure ventilation systems(4) electric driven fire pumps(5) fire service access elevators(6) fire suppression system controllers, and so forth.

NFPA 110, Standard for Emergency and Standby Power Systems, 2010 Edition, specifies therequirements for emergency power supply systems (EPSS). EPSS include both emergency and standby system (SeeNFPA 110, A.4.1, for further explanation of why standby systems are EPSS). Changing the term eliminates anydiscrepancy between whether these systems are powered from emergency or standby systems. Also EPSS is thecorrect term as used in NFPA 110.

_______________________________________________________________________________________________3- Log #14



A.1.3.5 In order for all of the requirements of NFPA 13 to apply to a project, the specifications need to require the entirecommissioning process rather than just referencing NFPA 3. For many simple buildings, the integrated testing of NFPA3 can be considered is not needed because the testing is satisfied by performing the acceptance tests and theinspection, testing, and maintenance required by the appropriate NFPA standards for the systems in a building. Forexample, a building with an automatic simple sprinkler system and fire alarm system can meet NFPA 3 integratedtesting requirements by meeting complying with the requirements of NFPA 13, NFPA 25, and NFPA 72.A.1.3.4 In order to invoke the rest of the requirements of NFPA 3, the specifications need to reference 1.3.5. For

example, in order to invoke the requirements in the rest of NFPA 3, To require commissioning, specifications shouldread, “The building fire protection systems shall be designed, installed, tested, commissioned, and maintained inaccordance with commissioning process of NFPA 3, Recommended Practice on Commissioning and Integrated Testingof Fire Protection and Life Safety Systems.” Without this specific language, only 1.3.5 of NFPA 3 would apply.

The annex was confusing and the two paragraphs did not both go with 1.3.5. Changed the secondparagraph to be an annex section to 1.3.4. Deleted text that was confusing, had unclear meaning, or was not defined(such as simple building or simple system).





A.5.2.1.1 The fire protection and life safety commissioning team can be part of a larger total building fire protection andlife safety commissioning team with team members whose focus is on commissioning electrical, mechanical, plumbing,and electronics systems. The overall team can be led by a commissioning authority whose responsibility is defined inASHRAE Guideline 0. The individuals and entities listed are not all inclusive and should be modified on a project byproject basis. If the entity listed is not part of the project, it is not the intent of this standard to require those entities tobecome part of the project fire protection and life safety commissioning team. The number of members of the fireprotection and life safety commissioning team should be determined by project type, size, and complexity. For example,a multiple building project can require more than one FCxA, all of which are overseen by a single FCxA.

Deleted the words in the first sentence to clarify the intent that the fire and life safety team can be partof a building commissioning team. The example in the last sentence doesn’t help to clarify the sentence before it.

_______________________________________________________________________________________________3- Log #16



A.5.2.3.3 The OPR documentation should include concept architectural documentation with a focus on fire and lifesafety. The applicable codes and standards must recognize any state, county, city, or local amendments to the codesand standards. The AHJ should be included in the development of the OPR as early as possible in the processrecognizing project confidentiality. The OPR can also incorporate budget and schedule issues. The OPR format shouldinclude the following sections: Introduction, Owners Key Project Requirements (i.e., insurance underwriter’s standards),General Project Description, Project Objectives, Functional Uses, Occupancy Requirements, Budget Considerationsand Limitations, Performance Criteria, and Project History. This The fire and life safety OPR can be a portion of theoverall total building commissioning OPR. See Annex C for a sample OPR. The OPR is intended to be a livingdocument that is regularly updated and modified. During the design phase the OPR can change significantly based onthe needs of the proposed design. Variances to code requirements can be sought in order to meet project needs andwill need to be appropriately documented in the OPR. The construction phase will include record drawings of theinstalled conditions of the fire and life safety systems. The OPR will then have the base documentation necessary to aidthe building operators in any upgrades or changes to the building fire and life safety systems.

The first and fourth sentences were redundant with the content of the fifth sentence. The secondsentence is not needed as a law adopting a code or standard always supersedes the base document. The AHJ shouldbe included in the Basis of Design (BOD) not the OPR. It is the fire and life safety OPR that is the subject of thissentence and “total” doesn’t add anything to building OPR. The final deletion pertains to information that is in the BOD.





A.6.2.1 Interactions include physical interconnections and impacts between systems that are not physically connected.Passive fire protection features can be impacted by active systems.A.6.2.1.4 A.6.2.2.2(4) For individual systems to work together there must be consideration of the various

interconnections that can occur. Some interconnections can be directly connected and others can be more remotelyinvolved. An example of the first is an emergency power off (EPO) system that in its operation causes loss of power to afire protection system or the EPO system itself. An example of the second is an atrium smoke control system thatfunctions correctly mechanically, but the air movement prevents the automatic doors from closing.

Delete duplicate annex paragraph. Move annex paragraph to appropriate section of Chapter 6.

_______________________________________________________________________________________________3- Log #18


3-181Delete text as follows:

A.3.3.19.2 Interconnected System. Interconnected systems are connected so that a binary output from one systemcauses a binary input in another system or systems. One example is a waterflow switch that is either open or closed(binary output) which when connected to the input of a fire alarm system can cause multiple outputs in the fire alarmsystem including sounding the waterflow bell and notification appliances, starting smoke control systems, and so forth.Combined systems are connected so that data from one component system is shared with other component systems,which then make independent decisions to achieve a desired result. The communication can be one-way or two-way,serial or parallel. A combined system can have components that are interconnected too. An integrated system is one inwhich the components communicate between multiple data processing units. Interconnected systems consist ofelectrically, optically, or wireless transmissions, normal/not-normal connections, or data transfer protocols such asBACnet and LonWorks.

This paragraph duplicates A.3.3.19.2.1, A.3.3.19.2.2, and A.3.3.19.3 and is not needed.





Chapter 9 Integrated Testing Frequency9.1* This chapter establishes responsibilities and recommendations for the frequency of integrated testing of existing

integrated fire protection and life safety systems.9.2* The testing recommended by this chapter should apply to all buildings and facilities.9.3 Integrated Systems Testing7.2.2 Integrated testing of eExisting fire protection and life safety systems should have periodic integrated testing occur

when recommended in Chapter 9. 9.3.1 An integrated testing plan. specifying the interval for integrated testing shouldbe submitted and approved where required by the AHJ.9.3.1.17.2.2.1 SIntegrated systems that have beenwere commissioned upon installation in accordance with the

commissioning process of Chapter 4 6 of this document should have integrated testing completed at the intervalspecified in accordance with the commissioning plan.9.3.27.2.2.2 For integrated systems that have not been were not commissioned upon installation, integrated testing

should be performed on a periodic basis at intervals specified in an integrated testing plan approved by the AHJ.inaccordance with one7.2.3 In addition to periodic integrated testing, integrated system testing should be done when any of the following

events occurs.(1) Where nNew component fire protection and or life safety systems are installed and integrated interconnected to

existing fire protection and life safety systems.(2) Where eExisting fire protection and or life safety systems are modified to become components of interconnected

systems.(3) Where the iInterconnections or sequence of operations of existing integrated fire protection and life safety systems

are modified.(4) At intervals specified in an integrated testing plan as approved by the AHJ.9.3.3* Where integrated tests are not performed in accordance with 9.4.1 or 9.4.2, the integrated test interval should

not exceed five years.9.3.4(4) SIntegrated systems that exhibit faults, failures, or indications of such faults or failures in the interconnections,

or those found to have deficiencies in the interconnections upon inspection, should be cause for an AHJ to recommendintegrated testing as specified in this chapter.9.3.5 Integrated systems testing should be performed as recommended in Chapter 6.9.3.67.2.4 Phased sequencing of integrated testing should be permitted subject to the approval of the AHJ.9.4 Documentation See Chapter 6 for documentation recommendations.A.9.1 The purpose of integrated fire protection and life safety systems testing is to verify that the existing systems

provided in a building or facility function together as originally intended.A.9.2 The recommended testing of fire protection and life safety systems should apply, but not be limited, to the items

listed in Section 1.3.A.9.3.3 It is not the intent to prescribe a periodic five-year integrated testing interval if the recommendations of 9.3.1 or

9.3.2 are met.The integrated testing frequency does not need to be in a separate chapter. It was that way only

because two task groups worked on the various parts of integrated testing. It makes logical sense to merge it directlyinto Chapter 7 and delete Chapter 9. Much of the text in Chapter 9 duplicates the intent of Chapter 7.This proposal puts integrated testing of existing systems into 3 parts; periodic testing, changes to systems, and

systems exhibiting problems. Under periodic testing, the period is as specified in the commissioning plan or if no plan,then an integrated testing plan is required. This is stronger than the default 5 year period in the ROP since all systemsmust have an integrated testing plan.The committee has not considered any evidence that the period of time specified in section 9.3.3 correlates with the

performance or reliability of integrated systems. The only stated reason for the 5 year test requirement is because somecommittee members think 5 years is a long time, but it is not a long time in the life of most fire protection systems. Asproposed, section 9.3.3 would apply to integrated systems including everything from an automatic sprinkler system orkitchen hood system monitored by a fire alarm system to a complicated system that would need retro-commissioning to


Report on Comments – June 2011 NFPA 3determine the design intent and create test requirements. The 5 year default may contradict the requirements of otherstandards such as NFPA 72 or NFPA 25.



_______________________________________________________________________________________________Robert Kasiski, FM Global


New technology acceptable to the AHJ, proposed for installation, with for which there is nopublished product instruction or installation standard, shall should function as intended throughout its life cycle inaccordance with the Owners Project Requirements, Basis of Design, or and requirements of the AHJ.

Designs using new technology shall should be submitted to the authority havingjurisdiction for review and approval.

Submittals shall should include documentation, in an approved format, of each performance objective andapplicable scenario, together with any calculations, modeling, or other technical substantiation used to establish the fireprotection and life safety performance of the design.

Tests submitted in support of an application shall should be performed by an agency approved by theauthority having jurisdiction.

The authority having jurisdiction shall should be permitted to require the submission of additional informationand data necessary to assist in the determination of equivalency.

The AHJ shall should be authorized to engage such expert opinion as deemed necessary to evaluate the newtechnology at no expense to the jurisdiction.

Upon completion of the installation, functional and interoperability testing shallshould be conducted demonstrating performance consistent with the OPR and the BOD in a method acceptable to theauthority having jurisdiction.

Final documentation shall should contain required inspection, maintenance, andtesting methods and intervals.

This section provides guidance for new technologies or alternate materials, devices, methods or arrangementsthat are not covered by other sections of this document. standard. The purpose of this section is to ensure newtechnology proposed for installation with no or limited performance history will function as intended throughout its lifecycle in accordance with the owner’s project requirements.New technology designs submitted to the authority having jurisdiction for review and approval should include

documentation, in an approved format, of each performance objective and applicable scenario, together with anycalculations, modeling, or other technical substantiation used in establishing the proposed design’s fire protection andlife safety performance.

The burden of proof of equivalency lies with the applicant who proposes the use ofalternative materials or methods. The authority having jurisdiction should determine whether identified performanceobjectives of the proposed new technology are appropriate and have met the intent of the performance objectives of thisdocument Standard, the OPR, BOD, and applicable codes and ordinances of the jurisdiction. The type of informationrequired includes test data in accordance with referenced standards, evidence of compliance with the referencedstandard specifications and design calculations.

Supporting data and tests, where necessary to assist in the approval of materials or assemblies notspecifically provided for in this Standard, should consist of valid research reports from approved sources. A researchreport issued by an authoritative agency is particularly useful in providing the authority having jurisdiction with thetechnical basis for evaluation and approval of new and innovative materials and methods of construction.Any tests submitted in support of an application must have been performed by an agency approved by the building

official Sufficient technical data, test reports and documentation should be provided for the AHJ to make a decision as tothe appropriateness of an alternative material or method. Reports providing evidence of this equivalency should berequired to be supplied by an approved source, meaning a source that the AHJ confirms is considered to be reliable andaccurate.

Approval should be based on evidence that the agency has the technical expertise, test equipment andquality assurance to properly conduct and report the necessary testing. To provide the basis on which the AHJ canmake a decision regarding an alternative material or method, sufficient technical data, test reports and documentationmust be provided for evaluation. In the absence of recognized and accepted test methods, the AHJ should can approvethe tests methods required. in this section. Methods of testing should be preapproved by the authority havingjurisdiction.The burden of proof of equivalency lies with the applicant who proposes the use of alternative materials or methods.


Report on Comments – June 2011 NFPA 3The authority having jurisdiction should be permitted to require the submission of any additional information and data toassist in the determination of equivalency consistent with this section.The authority having jurisdiction should determine whether identified performance objectives of the proposed new

technology are appropriate and have met the intent of the performance objectives of this Standard, the OPR, BOD, andapplicable codes and ordinances of the jurisdiction. Reports providing evidence of this equivalency should be required tobe supplied by an approved source, meaning a source that the AHJ confirms is considered to be reliable and accurate.The AHJ should make the final determination as to whether the provisions of the OPR and BOD have been met.

The AHJ should be authorized to can require design submittals for new technologies to bear a third partyreview and approval when the complexity of the design exceeds the capabilities of the AHJ to determine whether theappropriateness of the proposed design, operation, process, or interoperability. has met the Code requirements. Thetype of information required includes test data in accordance with referenced standards, evidence of compliance withthe referenced standard specifications and design calculations. A research report issued by an authoritative agency isparticularly useful in providing the building official with the technical basis for evaluation and approval of new andinnovative materials and methods of construction.

Upon completion of the installation, functional and interoperability testing should beconducted demonstrating performance consistent with the OPR and the BOD in a method acceptable to the authorityhaving jurisdiction. Acceptable methods of testing should be preapproved by the authority having jurisdiction prior totesting.

The applicant should provide system design and operational documentation.The applicant should provide a detailed document containing inspection, maintenance, t Testing methods and intervalsto assist in the continued operation and interoperability of system components and associated equipment.

This text was proposed by Michael DeVore of State Farm from his ROP submission. Text for body ofthe document has been revised based upon inclusion in a Recommended Practice. This Comment is submitted to theTechnical Committee for reconsideration to “Accept” including from their ROP Final Action to “Reject”,thus deleting it from the proposed Recommended Practice. Guidance is needed for those fire protection and life safetyareas for which there are no NFPA Standards. As example, currently there is a listed fire protection system which is auses a combination of water vapor and inert gas (hybrid fire ext. system) for fire extinguishment. It is neither covered byNFPA 750 or NFPA 2001. Or in the past, with clean agent fire extinguishing systems and water mist systems before anNFPA standard was developed. The inclusion of this guidance (1.6) for would address this deficiencyof a fire protection system or life safety system which could be included as part of a Commissioning Plan.

_______________________________________________________________________________________________3- Log #21

_______________________________________________________________________________________________Terry L. Victor, Tyco/SimplexGrinnell

3-24Remove references to acronyms (BOD), (Cx), (CxA), (FCxA), (Re-Cx), (RCx), (ITA), (OPR) and

(RDP) from Chapter 3 Definitions.Remove the acronyms BOD, Cx, CxA, FCxA, Re-Cx, RCx, ITA, OPR, and RDP from the text throughout the entire

document and replace with the whole words used in Chapter 3 Definitions.These acronyms make the document very difficult to read and understand. The user has to constantly

refer back to the definitions to understand the text. Acronyms are used sparingly in other NFPA documents when theyare known and commonly used throughout the industry, and when they help to clarify the text Acronyms should only beused to help clarify the text and should not be used when they cause confusion or when they cause the user toconstantly reference back and forth to the definitions section.




3-53Revise the qualifications for the installing contractor and revise the annex note as follows:

The installation contractor should submit to the FCxA evidence of required any licenses or certifications to theFCxA required by the federal, state, and/or local AHJ.

In some jurisdictions installation contractors or their personnel are required to hold a license or certification toperform such tasks as layout, inspection and testing, and/or installation. should be certified by an organizationresponsible for certification of technical installation personnel When required, the license or certification organization isidentified and approved by the AHJ.

Not every jurisdiction requires licensing or certification of companies or technical installation personnel.When a license or certification is required, it may not be the technical installation personnel that are licensed or certified.The current language is not clear whether the intent is that all installation contractors have either a license orcertification. It is not appropriate for this document to impose a license or certification on the installation contractor whenone in not required by the AHJ.

_______________________________________________________________________________________________3- Log #23


3-129Add a new item (7) and renumber as follows:

(7) Include all commissioning and integrated test recommendations in the Construction Document.(7) (8) Initiate the commissioning plan.

It's important that the Construction Document through the contract specifications include all thecommissioning and integrated testing requirements so the Installation Contractors know their responsibilities and pricetheir work accordingly.

_______________________________________________________________________________________________3- Log #24


3-24Modify the existing definition as follows:

3.3.5 Construction Document. The contract plans, contract specifications, and other documents that describe theconstruction project.

It's important that all commissioning and integrated test recommendations be communicated to theInstallation Contractors through the Construction Document. The Construction Document should be used as the basisfor the contract agreement between the owner or Construction Manager/General Contractor and the InstallationContractors and therefore the terms contract plans & contract specifications become important to both. Without thisdirect reference to these contract documents, commissioning and integrated testing may get excluded from the contract.




3-24Add a new definition as follows and renumber the remaining definitions in 3.3 as needed:

3.3.6 Construction Manager/General Contractor. A Construction Manager is a company that has a written agreementbetween the owner of a project (client) and a firm of professionals for planning, design, construction, and commissioningof a construction project. A General Contractor is a company that performs a contract all by itself, or through the use ofsubcontractors whose activities it supervises and coordinates.

These terms are used throughout the document but are not defined. Definitions for ConstructionManager and General Manager were not found either in the NFPA Glossary of Terms or in Merriam-Webster'sCollegiate Dictionary, 11th edition. The definitions provided were paraphrased and/or copied from definitions ofconstruction management contract and general contractor found in the online source BusinessDictionary.com.

_______________________________________________________________________________________________3- Log #26


3-53Revise the text for 4.2.4 and A.4.2.4 as follows:

4.2.4* Construction Manager/General Contractor. Construction managers and/or general contractors should beknowledgeable and experienced in the field of construction project management.A.4.2.4 Construction managers and/or general contractors should possess skills in the following categories of

construction management:(the rest of A.4.2.4 to remain as is)

The term that's used in other areas of the document lumps the construction manager and the generalcontractor together. For consistency keep these terms together. Both are capable of performing the work described andshould have the same qualifications.

_______________________________________________________________________________________________3- Log #27


Remove asterisk from 5.2.1.2, add asterisk to 5.2.2.1, and renumber and change A.5.2.1.2 asfollows:A.5.2.1.2.2.1 Fire protection and life safety commissioning team members should be selected as their role in the

project is established. For example, manufacturer's representatives cannot be identified until the design phase andtherefore cannot participate during the planning phase, and typically the installation contractor isn't identified until theconstruction phase and therefore cannot participate during the planning or design phases.

The annex reference should be on the section describing who the commissioning team members areand not on what the commissioning team does. Expanding the example to include reference to the installing contractorgives another level of identifying team members as the process moves forward.




3-129Add new (6) to the list of owner responsibilities and renumber the remaining items on the list as

follows:(6) Soliciting prices and contracting with construction manager/general contractor.(6) (7) Reviewing...(the rest of the text remains the same)(7) (8) Reviewing...(the rest of the text remains the same)

Nowhere in the process does the document recommend when to do the hiring of the projectmanager/general contractor. The logical pint where that should occur is after the construction documents are complete.

_______________________________________________________________________________________________3- Log #29


3-129Add new (2) to the list of construction manager/general contractor responsibilities and renumber

the remaining items on the list as follows:(2) Solicit prices and contract with installation contractors.(2) (3) Obtain cooperation...(each subsequent number changes and the rest of the text remains the same)

Nowhere in the process does the document recommend when to do the hiring of the installationcontractors. The logical point where that should occur is after the construction documents are complete, the projectmanager/general contractor has been hired, and all of the contracts include the commissioning process requirementsand activities.

_______________________________________________________________________________________________3- Log #30


3-129Revise the text in 5.2.2.7(1) as follows:

(1) Include all commissioning process requirements and activities as specified in the construction document in thescope of services.

The current wording leaves the door open for the installation contractor to be contractually responsiblefor additional commissioning process requirements discovered or added after the initial construction document isdeveloped. By referencing the construction document the recommendation ties the scope of services to that documentand the version of that document that was included in the contract.




3-129Add new (3) to the list of responsibilities of the AHJ and renumber the remaining items on the list

as follows:(3) Approve the basis of design at the end of the design phase, and before the construction phase begins.(3) (4) Witness...(the rest of the text remains the same)(4) (5) Identify...(the rest of the text remains the same).

One of the most important responsibilities of the AHJ has been overlooked in this list. Before theconstruction document can be complete, the AHJ must approve the basis of design. To go forward with the constructionof a project or the commissioning plan for one without first receiving approval from the AHJ on all of the protectioncriteria, is poor planning and irresponsible management. By adding this text it is clear that a viable commissioning planincludes this approval at this stage of the process.

_______________________________________________________________________________________________3- Log #32


3-142Add new (7) with annex language to the list of recommendations for design consideration of

integrated systems commissioning and renumber the remaining items on the lsit as follows:(7)* The limits of integrated testing by system and/or componentA.6.2.2.2(7) Each individual system or in some cases component of a system should have the limits of integrated

testing described for clarity and to define the integrated testing responsibilities of the installation contractor. Forinstance, a sprinkler flow switch is to initiate an alarm condition on the fire alarm control panel, which in turn is to initiatean alarm condition on the fire alarm control panel, which in turn is to initiate the elevator recall sequence. When the flowswitch is integrated tested, does the testing stop at the fire alarm control panel, or does it include the elevator recall? It'simportant that all involved understand the limits of integrated testing.(7) (8) Procedures for...(each subsequent number changes and the rest of the text remains the same)

Most of the confusion about integrated testing is a result of all entities involved not knowing where thetesting of individual systems and/or components begins and ends. It must be clearly defined in the commissioningdocuments as well as in the integrated test documents what the limits of the integrated testing are. Diagrams would bebest to describe these limits.

_______________________________________________________________________________________________3- Log #33


3-144Add a new 7.3.2 and renumber all other sections in 7.3 as follows:

7.3.2 Integrated testing for individual systems and/or components is to begin and end at the limiting points described inthe design documents.

Most of the confusion about integrated testing is a result of all entities involved not knowing where thetesting of individual systems and/or components begins and ends. It must be clearly defined in the commissioningdocuments as well as in the integrated test documents what the limits of the integrated testing are. Once these limits areestablished and the test points defined that bound those limits the integrating testing procedure should verify the testwas successful between those points.




3-142Revise 6.2.2.3 as follows:

6.2.2.3 The methods for pre-functional and integrated testing should be documented included in the constructiondocument.

Unless these methods are included in the construction documents and made available to theinstallation contractors in their contracts, disagreements will be inevitable. All testing requirements should be clearlyspelled out in all applicable documents so the commissioning team can work in unison and not in opposition to eachother.


NFPA 3 A2011 ROP Draft 4/27/10 A2011 ROP 1

Recommended Practice for Commissioning and

Integrated Testing of Fire Protection and Life Safety Systems

Chapter 1 Administration

1.1 Scope. This recommended practice provides the recommended procedures, methods, and documentation for commissioning and integrated testing of active and passive fire protection and life safety systems and their interconnections with other building systems. 1.2* Purpose. The purpose of this recommended practice is to describe the commissioning process and integrated testing that will ensure fire protection and life safety systems perform in conformity with the design intent. 1.3* Application. 1.3.1* This recommended practice applies to passive and active fire protection and life safety equipment and systems including, but not limited to, the following: (1)* Infrastructure supporting the building fire protection and life safety systems within the

boundaries of the project (2) Fixed fire suppression and control systems (3) Fire alarm systems (4) Emergency communications systems (ECS) (5) Smoke control and management systems (6)* Normal, emergency and standby power systems (7) Explosion prevention and control systems (8)* Fire-resistant and smoke-resistant assemblies (9) Commercial cooking operations (10) Elevator systems (11)* Means of egress systems and components (12) Other systems or installations integrated or connected to a fire or life safety system, such

as, but not limited to, access control, critical processes, and hazardous operations 1.3.2* Commissioning should achieve the following: (1) Documentation of the owner’s project requirements (OPR) and the basis of design (BOD)

provided (2) Equipment and systems installed as required (3) Integrated testing for all integrated fire and life safety systems performed and

documented (4) Delivery of operation and maintenance (O&M) documentation (5)* Training of facility operating and maintenance staff (6) Identification and documentation of the requirements for maintaining system

performance to meet the original design intent during the occupancy phase 1.3.3 Integrated testing should verify and document the following: (1) Performance in accordance with applicable codes and standards (2) Compliance with BOD and OPR (3)* Sequence of operation (4) Installation in accordance with manufacturers’ published instructions


(5) Accuracy of diagrams of system interconnections and device locations prior to final acceptance

. 1.3.4The recommendations for the commissioning of fire protection and life safety systems and

equipment in this document should apply when required by the project specifications. 1.3.5* The recommendations for the integrated testing of fire protection and life safety systems

and equipment in this document should apply when required by applicable codes or standards or the project specifications.

Chapter 2 Referenced Publications

2.1 General. The documents or portions thereof listed in this chapter are referenced within this recommended practice and should be considered part of the recommendations of this document. 2.2 NFPA Publications. National Fire Protection Association, 1 Batterymarch Park, Quincy, MA 02169-7471. NFPA 1031, Standard for Professional Qualifications for Fire Inspector and Plan Examiner, 2009 edition. NFPA 5000, Building Construction and Safety Code, 2009 edition. 2.3 Other Publications. CSI Master Format

Chapter 3 Definitions

3.1 General. The definitions contained in this chapter should apply to the terms used in this recommended practice. Where terms are not defined in this chapter or within another chapter, they should be defined using their ordinarily accepted meanings within the context in which they are used. Merriam-Webster’s Collegiate Dictionary, 11th edition, should be the source for the ordinarily accepted meaning. 3.2 NFPA Official Definitions. 3.2.1* Approved. Acceptable to the authority having jurisdiction. 3.2.2* Authority Having Jurisdiction (AHJ). An organization, office, or individual responsible for enforcing the requirements of a code or standard, or for approving equipment, materials, an installation, or a procedure. 3.2.3* Listed. Equipment, materials, or services included in a list published by an organization that is acceptable to the authority having jurisdiction and concerned with evaluation of products or services, that maintains periodic inspection of production of listed equipment or materials or periodic evaluation of services, and whose listing states that either the equipment, material, or service meets appropriate designated standards or has been tested and found suitable for a specified purpose. 3.2.4* Recommended Practice. A document that is similar in content and structure to a code or standard but that contains only non-mandatory provision using the word ―should‖ to indicate recommendations in the body of the text. 3.2.5 Should. Indicates a recommendation or that which is advised but not required. 3.3 General Definitions. 3.3.1* Basis of Design (BOD). A document that shows the concepts and decisions used to meet the owner’s project requirements and applicable standards, laws, and regulations.


3.3.2* Building. Any structure used or intended for supporting or sheltering any use or occupancy. [101, 2009] 3.3.3 Commissioning. 3.3.3.1* Commissioning (Cx). A systematic process that provides documented confirmation that specific and interconnected fire and life safety systems function according to the intended design criteria set forth in the project documents and satisfy the owner’s operational needs, including compliance requirements of any applicable laws, regulations, codes and standards requiring fire and life safety systems. 3.3.3.2* Commissioning Authority (CxA). The qualified person, company, or agency that plans, coordinates, and oversees the entire commissioning process. 3.3.3.3* Commissioning Plan. The document prepared for each project that identifies the processes and procedures necessary for a successful commissioning process. 3.3.3.4 Commissioning Record. The complete set of commissioning documentation for the project that is turned over to the owner at the end of the construction phase. 3.3.3.5 Fire Commissioning Agent. (FCxA). A person or entity identified by the owner, who leads, plans, schedules, documents, coordinates the fire protection and life safety commissioning team, and implements the commissioning process and integrated testing of fire and life safety systems. 3.3.3.6* Re-commissioning (Re-Cx). The process of verifying the performance of existing fire protection and life safety systems that have been previously commissioned to ensure that the systems continue to operate according to the design intent or current operating needs. 3.3.3.7* Retro-commissioning (RCx). The process of commissioning existing fire protection and life safety systems that were not commissioned when originally installed. 3.3.3.8 Total Building Commissioning Process. A systematic process, beginning at project inception and extending through the expected life of the building, that provides documented confirmation that all building systems function according to the intended design criteria set forth in the project documents and satisfy the owner’s operational needs, including compliance requirements of any applicable laws, regulations, codes and standards requiring fire and life safety systems. 3.3.4 Component. A part or element of an architectural, electrical, mechanical, or structural system. [5000, 2009] 3.3.5 Construction Document. The plans, specifications, and other documents that describe the construction project. 3.3.6 Drawings. 3.3.6.1 Coordination Drawing. Reproducible drawings showing work with horizontal and vertical dimensions to avoid interference with structural framing, ceilings, partitions, equipment, lights, mechanical, electrical, conveying systems, and other services. 3.3.6.2 Record (Plan) Drawing. A design, working drawing, or as-built drawing that is submitted as the final record of documentation for the project. A drawing is also referred to as a plan. 3.3.6.3 Shop Drawing. Scaled working drawings, equipment cutsheets, and design calculation. [1031, 2009] 3.3.6.4 Working (Plan) Drawing. Those approved plans and drawings that are used for construction of the project. 3.3.7 Inspection. A visual examination of a system or portion thereof to verify that it appears to be in operating condition and is free of physical damage. [820, 2008]


3.3.8 Installation Contractor. A company that provides labor and materials to install systems and equipment. 3.3.9 Integrated Testing Agent (ITA). A person or entity identified by the owner, who, plans, schedules, documents, coordinates, and implements the integrated testing of the fire protection and life safety systems and their associated sub-systems. 3.3.10 Issues Log. A formal and ongoing record of failures, deficiencies, or concerns, as well as associated priorities, implications, and resolutions. 3.3.11* Narrative. A written summary description of the building(s) or structure(s), including exterior property boundaries and all applicable fire protection and life safety systems and related integrated operational features. 3.3.12 Operation and Maintenance Manual. A system-focused composite document that includes the operation and maintenance requirements and additional information of use to the owner during the occupancy and operations phase. 3.3.13 Owner’s Project Requirements (OPR). The documentation that provides the owner’s vision for the planned facility, integrated requirements, expectations for how it will be used and operated, and benchmarks and criteria for performance. 3.3.14 Phase. 3.3.14.1 Construction Phase. The phase during which the systems and materials are fabricated and installed, tested, and accepted. 3.3.14.2 Design Phase. The phase during which the basis of design is produced, and drawings and calculations, including those for design and fabrication, are produced, and testing procedures are developed. 3.3.14.3 Occupancy Phase. The phase during which the training and periodic inspection, testing, and maintenance is scheduled and performed. 3.3.14.4 Planning Phase. The phase during which the fire protection and life safety commissioning team is formed and initial project concepts and the owner’s project requirements are developed. 3.3.15 Registered Design Professional (RDP). In commissioning, an individual who is registered or licensed to practice their respective design profession as defined by the statutory requirements of the professional registration laws of the jurisdiction in which the project is to be constructed, or other professional with qualifications or credentials acceptable to the jurisdiction in which the project is to be constructed. 3.3.16* Sequence of Operation. A matrix, narrative, or table of system inputs and outputs that can be used to illustrate the interactions of interconnected fire protection systems. 3.3.17 Stakeholder. Any individual, group, or organization that might affect, be affected by, or perceive itself to be affected by the risk. 3.3.18 System. 3.3.18.1* Active Fire Protection System. A system that uses moving mechanical or electrical parts to achieve a fire protection goal. 3.3.18.3 Fire Protection System. Systems, devices, and equipment used to detect a fire and its by-products, actuate an alarm, or suppress or control a fire and its byproducts, or any combination thereof. [1031, 2009] 3.3.18.4* Life Safety System. Those systems that enhance or facilitate evacuation, smoke control, compartmentalization, and/or isolation. [1031, 2009] 3.3.18.5* Passive Fire Protection System. Any portion of a building or structure that provides protection from fire or smoke without any type of system activation or movement.


3.3.19 System Connection. 3.3.19.1 * Integrated System. A combination of systems that are required to operate together as a whole to achievethe fire protection and life safety objectives. 3.3.19.2 * Interconnected System. An integrated system that has component systems or devices connected to achieve fire protection and life safety objectives. 3.3.19.2.1* Switch Connection. A subset of interconnected systems in which one system monitors a switch or relay in another system for either normal or not-normal condition. 3.3.19.2.2* Data Sharing System. A subset of interconnected systems in which data streams are transferred between two or more control units. 3.3.19.3* Interconnection. The physical connections between interconnected systems. 3.3.20 Systems Manual. A compilation of all operational and maintenance manuals, and description of the integrated fire protection and life safety systems. 3.3.21 Testing. 3.3.21.1 Acceptance Testing. Tests performed at the completion of installation to confirm compliance with applicable manufacturers' installation specifications, applicable codes and standards, and the project BOD and OPR. 3.3.21.2 Integrated Testing. An assessment of fire protection and life safety systems function and operation using direct observation or other monitoring methods to verify the correct interaction and coordination of multiple systems in conformance with the fire protection and life safety objectives. 3.3.21.3* Pre-Functional Testing. Tests performed prior to acceptance testing to confirm compliance with manufacturers’ specifications, applicable codes and standards, and the project BODs and OPRs. 3.3.21.4 * Preliminary Testing. Testing that is done according to a checklist (generally developed by the FCxA) that verifies that new equipment and all its components are functioning as intended.

Chapter 4 Qualifications of Commissioning Personnel 4.1 Applicability. Members of the fire protection and life safety commissioning team should meet the requirements of this chapter. planning 4.2 Qualifications. .4.2.1 Fire Commissioning Agent (FCxA). 4.2.1.1* General. 4.2.1.1.1 The FCxA should be knowledgeable and experienced in the proper application of commissioning recommendations of this recommended practice and general industry practices. 4.2.1.1.2 The FCxA should be individually identified on the specifications or other enabling documentation. 4.2.1.1.3 The FCxA should provide an objective and unbiased point of view. 4.2.1.2 Requisite Knowledge. A qualified FCxA should have an advanced understanding of the installation, operation and maintenance of all fire protection and life safety systems proposed to be installed, with particular emphasis on system integrated testing. 4.2.1.3 Requisite Skills. An FCxA should have the ability to do the following: (1) Read and interpret drawings and specifications for the purpose of understanding system

installation, testing, operation, and maintenance.


(2) Analyze and facilitate resolution of issues related to failures in fire protection and life safety systems.

(3) Provide clear, concise written reports and verbal communication, and have the ability to resolve conflicts.

4.2.2 Installation Contractor. 4.2.2.1 Installation contractors should be knowledgeable and experienced in the installation of the type of system proposed to be installed. 4.2.2.2* The installation contractor should submit evidence of required license or certification to the FCxA. 4.2.3 Registered Design Professional (RDP). 4.2.3.1 The RDP should be individually identified in the specifications or other enabling documentation. 4.2.3.2 Requisite Knowledge. A qualified RDP should have comprehensive knowledge of the following: (1) The design, installation, operation, and maintenance of all systems proposed to be

installed (2) How individual and integrated systems operate during a fire or other emergency .4.2.4* Construction Manager. Construction managers should be knowledgeable and experienced in the field of construction project management. 4.2.5 Facilities Management Personnel. Facilities management personnel should include building maintenance and service personnel, building engineering personnel, and similar job functions. 4.2.5.1 Facilities management personnel should have the ability to perform the following: (1) Assess a facility’s need for building systems and recommend building systems (2) Oversee the operation of building systems (3) Establish practices and procedures (4) Administer the allocation of building systems resources (5) Monitor and evaluate how well building systems perform (6) Manage corrective, preventative, and predictive maintenance of building systems (7) Develop and implement emergency procedures and disaster recovery plans. 4.2.5.2 Facilities management personnel should be knowledgeable and qualified in the operation and maintenance of the fire protection and life safety systems installed in their facility. 4.2.5.3 Facilities management personnel who perform the on-going system operation, inspection, testing, and maintenance should be thoroughly familiar with the required and recommended operation and maintenance tasks. 4.2.5.4 Facilities management personnel who will be responsible for management of a contract for system operation, inspection, testing, and maintenance should be thoroughly familiar with the tasks to be performed and the frequency of such tasks, but not necessarily the implementation of those tasks. 4.2.6* Third-Party Test Entity. 4.2.6.1 Third-party test entities should have an advanced understanding of the installation, operation, and maintenance of all fire protection and life safety systems proposed to be tested, with particular emphasis on system integrated testing. 4.2.6.2* Third-party test entities should be licensed or certified where required by the AHJ and/or codes and standards. 4.2.6.3 The third-party test entities should have the ability to do the following:


(1) Read and interpret drawings and specifications for the purpose of understanding system installation, testing, operation, and maintenance

(2) Provide good written, verbal, conflict resolution, and organizational skills 4.2.7* Authority Having Jurisdiction. 4.2.7.1 The AHJ should be knowledgeable in the applicable codes, ordinances, and standards as they relate to the fire protection and life safety systems installed. 4.2.7.2 The AHJ should have the ability to interface with the RDP and the commissioning authority in all phases of the commissioning process. 4.2.7.3 The AHJ should have the ability to determine the operational readiness of the fire protection and life safety systems installed. 4.2.7.4 The AHJ should have the ability to interface with the fire protection and life safety commissioning team in order to verify completion of integrated testing for the purpose of system acceptance. 4.2.8 Integrated Testing Agent (ITa) 4.2.8.1 The ITa should have an understanding of the design, installation, and operation and maintenance of the type of fire protection and life safety systems installed. 4.2.8.2 The ITa should demonstrate experience and knowledge of performance verification methods to validate functionality of integrated systems and components. 4.2.8.3 The ITa should demonstrate knowledge, experience and understanding of the operating components of all systems and subsystems to the extent they affect the installation and operation of the fire protection and life safety systems in accordance with the approved design. 4.2.9 Insurance Representative. Insurance representative should be knowledgeable and experienced in property loss prevention and life safety to mitigate possible risk.

Chapter 5 Commissioning 5.1 General. 5.1.1* This chapter provides the recommendations for commissioning fire protection and life safety systems. 5.1.2* Commissioning of fire protection and life safety systems should include, but not be limited to, the planning phase, design phase, construction phase, and occupancy phase. [See Figure A.5.1.2(a), Figure A.5.1.2(b), and Figure A.5.1.2(c).] 5.2 Planning Phase. 5.2.1 Activities. 5.2.1.1* The fire protection and life safety commissioning team should be established during the planning phase. 5.2.1.2* During the planning phase of the project, the fire protection and life safety commissioning team should do the following: (1) Develop the OPR in accordance with Section 5.2. (2) Select the FCxA. (3) Identify the commissioning scope. (4) Develop the preliminary commissioning plan in accordance with Section 5.2. (5) Review the planning documents in accordance with Section 5.2. (6)* Develop regulatory code analysis. (7) Initiate the commissioning plan.


5.2.2 Fire Protection and Life Safety Commissioning Team. The fire protection and life safety commissioning team should be identified and documented. 5.2.2.1 The exact size and members of the fire protection and life safety commissioning team can vary depending on project type, size and complexity, and could include the following members: (1) Owner (2) Commissioning authority (3) FCxA (4) Installation contractor(s) (5) Manufacturer’s representatives (6) RDP(s) (7) Construction manager/general contractor (8) Owner’s technical support personnel (9) Facility manager or operations personnel (10) Insurance representative (11) Third party test entity (12)* AHJ (13)* Integrated Testing agent (ITa) 5.2.2.2* Entities listed in 5.2.2 not included as part of the project should not be required to be part of the fire protection and life safety commissioning team. 5.2.2.3 The fire protection and life safety commissioning team members should meet the requirements of Chapter 4. 5.2.2.4 Owner. 5.2.2.4.1 The owner should be responsible for the commissioning of all fire and life safety systems. 5.2.2.4.2* The owner should be permitted to delegate the responsibility for commissioning to a designated representative. 5.2.2.4.3 The owner responsibilities should include the following: (1) Contracting and delegating the commissioning process (2) Assisting in the development of and approval of the OPR (3) Assigning operations and maintenance personnel to participate in the commissioning

process (4) Reviewing and approving any changes to the OPR (5) Reviewing and approving the construction documents (6) Reviewing and approving commissioning process progress reports (7) Reviewing and approving the fire protection and life safety commissioning team progress reports (8) Review and approving the final commissioning report 5.2.2.5 Commissioning Authority (CxA). 5.2.2.5.1 * The CxA should be responsible for coordinating between the FCxA and the remainder of the total building commissioning team, when applicable. 5.2.2.6 Fire Commissioning Agent (FCxA). The FCxA responsibilities should include the following: (1) Organize and lead the fire protection and life safety commissioning team. (2) Coordinate and attend fire protection and life safety commissioning team meetings. (3) Facilitate the development of and document the OPR. (4) Verify that commissioning process activities are clearly stated in all scopes of work.


(5) Identify and integrate the commissioning process activities into the project schedule. (6) Prepare the commissioning plan. (7) Prepare the commissioning process activities to be included in the project specifications. (8) Execute the commissioning process. (9) Review the plans and specifications during the planning and design phases. (10) Attend pre-bid meeting to detail the commissioning contractor requirements. (11) Review and approve the O&Ms to compile the systems manual. (12) Track and document issues and deviations to the OPR and log resolutions in the issues

log. (13) Write and review commissioning process progress reports. (14) Organize and coordinate system testing. (15) Witness system testing. (16) Review installation and record documents. (17) Recommend acceptance of the systems to the owner. (18) Track development, accuracy, and compliance with sequence of operation. (19) Compile and submit the final fire protection and life safety commissioning team report to

the owner. (20) Compile and submit to owner all fire protection and life safety systems commissioning

documents required by the AHJ. 5.2.2.7 Installation Contractor. The installation contractor responsibilities should include the following: (1) Include all commissioning process requirements and activities in the scope of services. (2) Attend required fire protection and life safety commissioning team meetings. (3) Include or comply with commissioning process milestones in the project schedule. (4) Implement the training program as required by the contract documents. (5) Provide submittals to the RDP, owner, and fire protection and life safety commissioning

team. (6) Develop individual system test plan, including acceptance and integrated testing. (7) Notify the general contractor, third-party test entity, and FCxA when systems are ready

for testing. (8) Demonstrate the performance of the systems, including integration. (9) Complete the construction checklists as the work is accomplished. (10) Continuously maintain the record drawings as required by the construction documents. 5.2.2.8 Manufacturer’s Representatives. The manufacturer’s representative responsibilities should include the following: (1) Provide technical support to the installation contractor. (2) Provide all information required for the operation and maintenance of the system. (3) Provide the requirements to maintain the warranty as part of the initial submittal. (4) Assist the installation contractor in the development of the individual systems test plans. (5) Assist the installation contractor and fire protection and life safety commissioning team

with installation verification and testing. (6) Assist in development and implementation of system training. 5.2.2.9 RDP. The RDP responsibilities should include the following: (1) Participate and assist in the development of the OPR. (2) Create and document the basis of design. (3) Prepare contract documents.


(4) Respond to the fire protection and life safety commissioning team’s design submission review comments.

(5) Specify operation and maintenance of systems in the project specifications. (6) Review and incorporate the fire protection and life safety commissioning team’s

comments, as appropriate. (7) Review test procedures submitted by the installation contractor. (8) Review and comment on the commissioning record. (9) Review and accept record documents as required by the contract documents. (10) Review and comment on the final commissioning record. (11) Recommend final acceptance of the systems to the owner. 5.2.2.10 Construction Manager/General Contractor. The construction manager’s/general contractor’s responsibilities should include the following: (1) Include commissioning process requirements and activities in all contracts. (2) Obtain cooperation and participation of all subcontractors and manufacturers’

represetatives. (3) Attend required fire protection and life safety commissioning team meetings. (4) Include commissioning process milestones in the project schedule. (5) Notify the FCxA when systems are ready for testing. (6) Certify that all work has been completed and the facility is operational in accordance with

the contract documents. (7) Remedy deficiencies identified by the fire protection and life safety commissioning team

during installation verification or testing. (8) Review and comment on the final commissioning record. 5.2.2.11* Insurance Representative. The Insurance Representative(s) responsibilities should include the following services, as contracted with the owner: (1) Provide fire protection recommendations to RDP for inclusion in the Basis of Design and

other construction documents. (2) Review the construction documents during the Planning and Design Phases to evaluate

alignment with insurance risk management recommendations. (3) Participate in CxT meetings, as necessary, to ensure scope of project, responsibilities and

project timeline (including Commissioning) is established/agreed to. (4) Visit project site during installation phase to review physical/actual installation is

consistent with reviewed/accepted construction documents, as necessary. (5) Review and approve proposed inspection, testing, performance criteria and

documentation recommended for acceptance of commissioning. (6) Witness installation verification and system testing in conjunction with the CxT, as

necessary. (7) Verify any issues detected during commissioning are resolved in timely and appropriate

manner. (8)* Verify adequate training and documentation is provided for onsite personnel, (9) Review final commissioning documentation. 5.2.2.12 Owner’s Technical Support Personnel. The owner’s technical support personnel’s responsibilities should include the following: (1) Review and comment on the OPR. (2) Provide technical assistance to the fire protection and life safety commissioning team,

RDP, and installation contractor.


(3) Review any changes to the OPR. (4) Review the construction documents. (5) Review the fire protection and life safety commissioning team’s commissioning process

progress reports. (6) Review the fire protection and life safety commissioning team’s progress reports. (7) Review the fire protection and life safety commissioning team’s commissioning record. (8) Review the systems manual. 5.2.2.13 Third-Party Test Entity: The third-party test entity's responsibilities should include the following: (1) Include all commissioning process requirements and activities in the scope of services. (2) Attend required fire protection and life safety commissioning team meetings. (3) Include commissioning process milestones in the project schedule. (4) Develop individual system test plan, including acceptance and integrated testing. (5) Demonstrate the performance of the systems, including integration. (6) Complete the construction checklists as the work is accomplished. (7) Develop and submit final testing documentation. 5.2.2.14 Facility Manager or Operations Personnel. The facility manager or operations personnel’s responsibilities should include the following: (1) Attend systems training sessions. (2) Review and comment on the OPR. (3) Review and comment on the systems manuals. (4) Organize, coordinate, and implement system inspection, testing, and maintenance as

required by the systems manuals. 5.2.2.15 AHJ. The AHJ’s responsibilities should include the following: (1) Participate in fire protection and life safety commissioning team meetings as necessary. (2) Provide all inspection, testing and performance criteria required for acceptance and

issuance of certificate of occupancy to be included in the commissioning plan. (3) Witness installation verification and system testing in conjunction with the fire protection

and life safety commissioning team, as necessary. (4) Identify AHJ personnel to attend training. 5.2.3 Owner’s Project Requirements (OPR). 5.2.3.1 The OPR should form the basis from which all design, construction, acceptance, and operational decisions are made. 5.2.3.2* The OPR should be developed with input from the owner and all key facility users and operators. 5.2.3.3* The OPR should be documented at the planning stage of the project. 5.2.3.3.1 Each item of the OPR should have defined performance and acceptance criteria. 5.2.3.3.2 The OPR should include, but is not limited to, the following: (1) Infrastructure requirements (utilities, roads, site access) (2) Facility type, size, height (3) Intended use (4) Occupancy classification, number of occupant, number and hours of operation (5) Future expansion requirements (6) Applicable codes and standards (7) Specific user requirements (8) Training requirements


(9) Warranty, operations and maintenance requirements (10) Integrated system requirements in accordance with Chapter 5 (11) Specific performance criteria (12) Third-party requirements 5.2.3.4 The OPR should be updated as required by the fire protection and life safety commissioning team throughout the planning, design, construction, and occupancy phases of the building life cycle. 5.2.4 Commissioning Plan. 5.2.4.1 The commissioning plan should be continuously updated by the fire protection and life safety commissioning team throughout the planning, design, construction, and occupancy phases of the building life cycle. 5.2.4.2* The commissioning plan should contain the following information: (1) Commissioning scope and overview specific to the project (2) General project information (3) Fire protection and life safety commissioning team members, roles, and responsibilities (4) General communication plan and protocol (5) Commissioning process tasks and activities through all phases (6) Commissioning schedule (7) Commissioning process documentation and deliverables (8) Testing procedures, including integrated testing (9) Recommended training (10) Establishment of a integrated testing frequency, as applicable 5.2.4.3 The following materials should be added as annex sections of the completed commissioning plan: (1) A — Owner’s project requirements (2) B — Basis of design (3) C — Commissioning specifications (4) D — Design review (5) E — Submittal review (6) F — Issues log (7) G — Construction checklists (8) H — Site visit and commissioning meeting minutes (9) I — Systems manual review (10) J — Training (11) K — Integrated testing procedures (12)* L — Warranty review (13) M — Test data reports (14) N — Sequence of operation 5.2.4.4 The commissioning plan, including all annexes, should form the commissioning record at the end of the construction phase. 5.2.4.5 A current copy of the commissioning record should be presented to the owner at the end of the construction phase. 5.2.5 Planning Review. 5.2.5.1 The FCxA should review the planning documentation to compare the design concept with the interests and needs of the owner as defined in the OPR.


5.2.5.2 The FCxA should identify required changes and improvements affecting operations and maintenance. 5.2.5.3 It should not be the intent of the planning review to verify compliance with local, state and federal codes, unless specifically identified in the commissioning scope. 5.2.6 Planning Approval Documentation. 5.2.6.1 The FCxA should submit documentation stating completion and recommending acceptance of the planning requirements to the owner or other designated individual. 5.2.6.2 The documentation should include, but is not limited to, the following information. (1) Receipt, review, and approval of planning submittal (2) Updates to the commissioning plan, as applicable (3) Any additional comments or requests for information considered by the FCxA to be

appropriate to the commissioning process (4) Preliminary sequence of operation 5.3* Design Phase. 5.3.1* Design phase activities should include, but not be limited to, the following: (1) Developing the BOD (2) Review and approval of the sequence of operation (3) Review of project drawings and calculations affecting fire protection and life safety

systems (4) Documentation of the scope for commissioning activities (see annex for scope document

example) (5) Documentation of the commissioning procedures (6) Developing a commissioning schedule (7) Verifying that the construction documents comply with the requirements of the BOD (8) Identifying qualified specialists in accordance with Chapter 4 and their responsibilities (9) Coordinating and documenting fire protection and life safety commissioning team

meetings and progress reports (10)* Documenting issues and changes (11) Updating the commissioning plan (12)* Developing construction checklists 5.3.2 Basis of Design. 5.3.2.1 General 5.3.2.1.1 The basis of design should be the documentation describing the initial design decision making process and description of systems. 5.3.2.1.2 This document should be in the form of a narrative report and shall be submitted for review prior to the installation of any system. 5.3.2.1.3 The basis of design should include but not be limited to the following: (1) A description of the building or structure (2) A description of fire protection or life safety systems and components (3) Performance objectives and criteria (4) Referenced codes and standards (5) Alternative means and methods incorporated into the original design (6) Testing and start-up requirements (7) Inspection, testing, and maintenance requirements 5.3.2.1.4 The BOD should be included with other required submittals to facilitate plan review


and approval by the authority having jurisdiction prior to the issuance of a permit to install the system. 5.3.2.1.5 The BOD should be updated in accordance with the recommendations for OPR in 5.2.3 after every revision of the design documents. 5.3.2.1.6 The outline for the BOD should include the items in 5.3.2.2 through 5.3.2.8. 5.3.2.2* Applicable Standards, Laws, and Regulations. This section should identify the codes and standards that apply to the design, plan review, installation, testing, acceptance, inspection, and maintenance of the proposed fire protection and life safety systems. 5.3.2.2.1 All codes and standards should be referenced as they apply, including, but not limited to, the following: (1) NFPA standards including edition used for the design of each fire protection/life safety

system (2) Applicable local, state, and federal laws and regulations (OSHA, ADA, etc.) (3) Specialized codes and standards (HVAC, plumbing, etc.) (4) Green building design considerations that affect fire and life safety systems 5.3.2.3 Building Description. This section outlines the specific features of the fire protection and life safety systems that should be identified in the BOD: (1) Building use group or occupancy classification (2) Total area of the building (3) Building height (4) Number of floors above grade (5) Number of floors below grade (6) Area per floor (7) Type(s) of hazardous areas within buildings (8) Type(s) of construction (9) Site access arrangement for emergency response vehicles (10) Descriptions of fire protection and life safety systems 5.3.2.4 Fire Protection and Life Safety System Objectives and Decisions. 5.3.2.4.1 The BOD should describe the performance objectives of each fire protection and life safety system including, but not limited to, the following: (1) Whether each system is required by code or installed voluntarily (2) Whether it is a complete or partial installation (3) Whether it is an addition or modification to an existing system 5.3.2.4.2 The BOD should describe the decisions made and the criteria established to achieve the performance objectives including, but not limited to, the following: (1) Building occupant notification and evacuation procedures (2) Emergency personnel response (3) Site and systems features (4) Safeguards during construction, including fire prevention and emergency procedures (5) Impairment plans when modifying existing systems (6) Methods for inspection, test and, maintenance of systems 5.3.2.5 Consideration and Description of Alternative Means and Methods. This section should identify the design intent of any alternatives to prescriptive requirements of the codes and standards, including, but not limited to, the following: (1) Interpretations and clarifications (2) Waiver or variance sought through the regulatory appeal process


5.3.2.6 Testing Criteria. 5.3.2.6.1 The FCxA should be responsible for all items listed in 5.2.2.4. 5.3.2.6.2 Testing criteria should be established and documented. 5.3.2.6.3 The methods for preliminary and integrated testing should be documented. 5.3.2.7* Equipment and Tools. The FCxA should identify and document the tools and equipment necessary for testing. 5.3.3 Operation and Maintenance Manuals. 5.3.3.1 Operation and maintenance manuals (O&Ms) should be provided. 5.3.3.2 O&Ms should contain, but not be limited to, the following information: (1) Project name and address (2) Discipline (i.e., fire protection) (3) Specification section number (4) Volume number 5.3.3.3* The RDP should review and approve the O&Ms for conformance with the OPR. 5.3.4 Training of Operations Personnel. The content, duration, and learning outcomes of training for operations personnel should be provided in the design documentation in accordance with Section 5.4. 5.3.5 Design Methodology. 5.3.5.1* The design should take into consideration the final commissioning of the active and passive fire protection systems. 5.3.5.2 The recommendations for design consideration should include, but not be limited to, the following: (1) Materials and equipment applied in such a manner that will not affect their listing or their

intended use where applicable (2) Materials and equipment have the capacity to perform their intended use (3) Design documents or details to demonstrate how the systems operate and communicate to

attain the desired outcome (4) Design documents and/or details to demonstrate the application of fire protection systems

in the construction (5) Locations of fire protection systems (6) The procedures for verification of fire protection systems (7) Assignment of responsibility for the testing and inspection of the fire protection systems

during the construction phase (8) Specification of the deliverables, including final documentation for the conclusion of the

project (9) Specification of the format of the deliverables 5.4 Construction Phase. During the construction phase the systems should be delivered, installed, and tested in accordance with the OPR, construction documents, shop drawings, and coordination drawings. 5.4.1 Construction Phase Commissioning Activities. 5.4.1.1 The fire protection and life safety commissioning team should complete the following: (1) Confirm that the commissioning schedule is still valid, and update if required. (2) Verify that submittals, including, but not limited to, working plans and product data

sheets are in conformance with the BOD and have been reviewed. (3) Verify that materials, construction, and installation are in conformance with the BOD. (4) Confirm qualified specialists are performing commissioning activities per CP.


(5) Coordinate and document fire protection and life safety commissioning team meetings and progress reports.

(6) Document any issues and changes to the project and update the CP. (7) Complete Cx (QC) construction checklists. (8) Perform required observation procedures or cause them to be performed by the

responsible party. (9) Update related documents to record and adjust for any revisions and/or changes. (10) Verify and document testing performed in the construction phase. 5.4.1.2 Construction should take into consideration the final commissioning of the passive fire protection systems. 5.4.1.3 The recommendations for installation should include but not be limited to the following: (1) Conformance to the approved drawings and specifications (2) Compliance with the manufacturers’ published instructions (3) Compliance with applicable codes and standards (4) Materials and equipment of proper rating for the use 5.4.2 Construction Inspections. 5.4.2.1 Pre-Installation or Preconstruction. 5.4.2.1.1 A preconstruction conference should be held to ensure the fire protection and life safety commissioning team and those performing the work all understand the schedule, procedures, and process. 5.4.2.1.2 Schedule commissioning process activities should include the following: (1) Address any outstanding issues that are best resolved in this venue. (2) Verify coordination has taken place amongst trades. (3) Identify and establish benchmarks to be met during the construction phase. (4) Verify submittals are in accordance with design intent documents and approvals and

permits are secured. (5) Confirm integrated testing requirements are being addressed. (6) Develop test data records. (7) Confirm compliance with sequence of operation. 5.4.2.2 Rough-In Phase. The following tasks should be performed prior to concealment of the installed material: (1) Inspect and verify delivered materials meet requirements. (2) Verify installation is proceeding in accordance with coordinated, approved shop

drawings. (3) Complete periodic site visits to verify compliance with the owner’s commissioning plan. (4) Inspect installation as outlined in the commissioning plan. (5) Perform testing as applicable. (6) Update owner project requirements and address any outstanding issues. (7) Update commissioning plan as needed. (8) Issue rough-in phase commissioning progress report. 5.4.2.3 Finish Phase. The following tasks should be performed after the rough-in phase is complete: (1) Inspect and verify delivered materials meet requirements. (2) Verify installation is proceeding in accordance with coordinated, approved shop drawings. (3) Complete periodic site visits to verify compliance with OPR.


(4) Inspect installation as outlined in the commissioning plan. (5) Perform testing as applicable (post concealment). (6) Update owner project requirements (OPR) and address any outstanding issues. (7) Update commissioning plan. (8) Issue finish phase commissioning progress report. 5.4.3 Testing and Inspection. 5.4.3.1 Testing and inspection should include passive fire protection systems. 5.4.3.2 The recommendations for testing and inspection should include but not be limited to the recommendations of Chapters 7 and 9. 5.4.3.2.1 Fire protection systems that have no operating components should be inspected to verify conformance with the BOD. 5.4.3.2.2 Fire protection systems that have operating components should have their functionality tested to demonstrate compliance with the BOD. 5.4.3.2.3 Written documentation of the testing and inspection should be provided. 5.4.3.2.4 Inspection and testing should be repeated if changes are made to systems. 5.4.3.3 Testing and inspection of passive fire protection systems should be completed as required during construction. 5.4.4 Completion and Acceptance Testing. The following tasks should be performed as part of the acceptance of the fire protection and life safety systems: (1) Verify installation is in accordance with coordinated, approved shop drawings. (2) Inspect overall installation as outlined in the commissioning plan. (3) Perform preliminary testing of all systems to provide proper functionality and to ensure

interoperability. (4) Perform and document testing of all systems to provide proper functionality, to ensure

integration, and to ensure the systems were left in a state of operational readiness. (5) Update owner project requirements and address any outstanding issues. (6) Update commissioning plan/record. (7) Issue completion/acceptance phase commissioning progress report. (8) Verify compliance and accuracy of sequence of operation. 5.4.5* Owner Training. Training should be permitted to take place in the construction phase. 5.4.6* Closeout Documents. Closeout documents should include but not limited to the following: (1) Compiled list of all deficiencies and resolutions; and verify resolution achieved. (2) Operations and maintenance manuals (3) Compile test results and certificate (4) As-built drawings (5) Warranty and extended warranties (6) Spare parts list and supplier listings (7) Re-commissioning plan (integrated testing) (8) Sequence of operation 5.5 Occupancy Phase. 5.5.1 Occupancy phase should be the final stage of the commissioning process for the fire protection or life safety systems. 5.5.2 The recommendations for occupancy phase should include but not be limited to the following:


(1) Documentation and completion of remaining acceptance testing and inspections (2) Testing conducted for modifications made during the construction phase commissioning (3)* Perform deferred testing for seasonal conditions (4) Submission of the system manual, operation and maintenance manuals, and vendor

emergency contact list (5) Training on the use and operation of the fire protection and life safety systems (6) Delivery of the record set drawings and documents (7) Delivery of the test and inspection records for the fire protection and life safety systems (8)* Delivery of a digital copy of site-specific software for fire protection and life safety

systems that is current with the installed system (9)* Delivery of warranties for the systems and equipment (10) Submission of recommended preventative maintenance program for fire protection and

life safety systems (11) Delivery of a list of required inspections, tests, and maintenance for fire protection and

life safety systems 5.5.3 Administrative Controls. The owner should be responsible for the continued performance of fire protection and life safety systems. 5.5.3.1* Applicable inspection and testing should be performed when modifications are made. 5.5.3.2* When changes are made to the use of the facility, the OPR should be re-evaluated. 5.5.3.3* The design documents should be maintained for future reference.5.5.3.4 Inspection, testing, and maintenance should be performed as specified in the installation standard or manufacturer’s instructions. 5.5.3.5 Integrated systems should be inspected, tested and maintained in accordance with the commissioning plan. 5.5.4 Training. 5.5.4.1* The training should include, but not be limited to, the following: (1) The systems, component systems, and devices for which training will be required (2) The capabilities and knowledge of the occupants and maintenance personnel (3) The number and type of training sessions (4) The location and organization of operation and maintenance manuals 5.5.4.2* Systems training should be scheduled to be completed at or as close to final systems acceptance as possible. 5.5.4.3* Training session scope and attendees should be documented as part of the commissioning record. 5.5.4.4* Facilities personnel or their designated representatives should receive periodic re-training as determined by the commissioning agent.

Chapter 6 Integrated Systems Commissioning 6.1 General. This chapter should apply to the functions of integrated systems provided for fire protection or life safety in the design phase, construction phase, and occupancy phase of the commissioning process of Chapter 5. 6.2 Design Phase. 6.2.1* Construction documents should include a narrative report of the system interactions.


6.2.1.1 The narrative report should include the sequence of operations of integrated fire protection or life safety systems. 6.2.1.2 The narrative report should include the performance objectives of system interactions. 6.2.1.3 The narrative report should include an analysis of the impact the interactions will have on the proper operation of each independent fire protection or life safety system. 6.2.1.4* The narrative report in the basis of design should include the owners’ expectation of how fire protection or life safety systems work together. 6.2.2 Design Methodology. 6.2.2.1 The design should take into consideration the interconnections of the fire protection or life safety systems. 6.2.2.2 The recommendations for design consideration should include but not be limited to the following: (1) Materials and equipment interconnected in such a manner that will not affect their listing

or their intended use where applicable (2)* Materials and equipment have the capacity to perform their intended use (3)* Design documents or details to demonstrate how the systems operate and communicate to

attain the desired outcome (4) Design documents or details to demonstrate how operations of integrated systems do not

impair the functionality of other component systems, unless designed to impair another system

(5)* Sequence of operation for integrated systems (6)* Locations of interconnections (7) Procedures for integrated testing (8)* Required frequency for integrated testing (9) Assignment of responsibility for the testing and inspection of the systems and

interconnections during the construction phase (10) Specification of the deliverables, including final documentation for the conclusion of the

project (11)* Specification of the format of the deliverables 6.2.2.3 The methods for pre-functional and integrated testing should be documented. 6.3 Construction Phase. 6.3.1 The recommendations for installation of integrated systems should include but not be limited to the following:

(1) Conformance to the approved drawings and specifications (2) Compliance with the manufactures’ published instructions (3) Compliance with applicable codes and standards (4) Review of material and equipment submittals of proper rating for the use (5) Coordination of all contractors’ submittal drawings, sequence of operation, and procedures

6.4 Occupancy Phase. 6.4.1 The recommendations for occupancy consideration should include but not be limited to the following:

(1) Verification that individual system testing and inspection is complete and documented in accordance with applicable codes and standards and the design specifications for the project.


(2) Verification that integrated system testing and inspection is complete and documented in accordance with the design specifications and the commissioning plan for the project. (3) Approval of modifications made to the system or interconnections by the design professional. (4) Retested as determined by the Integrated Testing agent (ITa). (5) Interconnections documented in operation and owner manuals. (6) Training as recommended in 5.3.4, 5.4.5, and 5.5.4 on the use and operation of the systems and interconnections. (7) The vendor emergency contact list (8) The as-built documents for the systems and interconnections. (9) A copy of test and inspection records of the systems and interconnections. (10) A copy of site-specific software of the systems and interconnections that is current with the installed system. (11) A copy of warranties for the systems and interconnections. (12) A copy of a recommended preventative maintenance program for the systems and interconnections. (13) A list of recommended periodic inspections and tests for the systems.

6.4.2* The design documents should be maintained for future reference. 6.5 Data Sharing Systems. During the design phase, the fire protection and life safety commissioning team should document the following:

(1) Where data sharing systems occur in the project (2) Compatibility of data sharing systems (3) Where gateways or interfaces are recommended between data sharing systems (4) The responsible parties for each portion of the interconnection (5) Degrade mode for each data sharing system upon loss of communication

Chapter 7 Integrated System Testing 7.1 General. 7.1.1 This Chapter applies to the testing of integrated systems provided for fire protection or life safety. 7.1.2 Personnel responsible for integrated testing should meet the qualifications listed in Section 4.2.8 for Integrated Testing agent (ITa). 7.2 Test Frequency. 7.2.1* In new construction, integrated testing of fire protection and life safety systems should occur following:

(1) Verification of completeness and integrity of building construction. (2)* Individual system functional operation and acceptance as required in applicable

installation standards tests. (3) Completion of pre-functional tests of integrated systems.

7.2.2 Integrated testing of existing fire protection and life safety systems should occur when recommended in Chapter 9. 7.3 Test Method. 7.3.1* Integrated testing should demonstrate that the final integrated system installation complies with the specific design objectives for the project and applicable codes and standards


7.3.2* Integrated testing of fire protection and life safety systems should verify the interconnections function properly. 7.3.3* During integrated testing, equipment should be tested in accordance with the applicable installation standard to verify systems perform according to their design function. . 7.3.4 Written documentation of the testing and inspection should be provided. 7.3.5* Testing should be repeated if changes are made to systems. 7.3.6. Switch connections to fire alarm systems should be tested in accordance with NFPA 72. 7.3.7 Control circuits requiring electrical power shall be tested for presence of operating voltage. 7.3.7.1 Loss of power to monitored circuits should be tested to confirm signal receipt at one of the following:

(1) A constantly attended location at the premises (2) A monitoring station as described in NFPA 731, Chapter 9 (3) A supervising station as described in NFPA 72

7.3.8 Integrated testing of data sharing systems should document the following: (1) Completion of acceptance testing for each component system (2) Verification of data transfer between component systems (3) Test of visual and audible signal upon loss of communication (4) Test of degrade mode for each component system (5) Proper function of integrated data sharing systems

7.4 Testing Responsibility 7.4.1 The owner should be responsible for integrated testing of fire and life safety systems. 7.4.2 The owner should be permitted to delegate the authority and responsibility for integrated testing of the fire protection and life safety systems to the management firm or managing individual through specific provisions in the lease, written use agreement, or management contract. 7.4.3* The ITa should be responsible for planning, scheduling, documenting, coordinating and implementing the integrated testing of the fire protection and life safety systems and their associated sub-systems. 7.4.4 Where a commissioning plan does not exist, the ITA should prepare a test plan providing, but not limited to, the following information: (1) A comprehensive functional matrix depicting all system inputs and associated output

functions. (2) The extent of systems to be tested under the direct supervision of the ITA.

(3) The testing of component systems required by associated NFPA Standards conducted separately under contract to the owner. (4) Test processes to be incorporated.

(5) Test scenarios developed to verify appropriate system responses to the functional matrix.

(6) A test event schedule with the applicable stakeholders. 7.4.5* Documentation 7.4.5.1 The ITA should maintain a record of faults, failures, and discrepancies discovered through the testing process in an official Issues Log. 7.4.5.1.1. The Issues Log should list each separate finding and its corresponding resolution, including dates of discovery and resolution. 7.4.5.2 Corrective Action Reports should provide a specific and detailed description of actions taken to remediate faults, failures, and discrepancies discovered during the testing process.


7.4.5.3 Upon completion of testing, the ITA should submit a Final Test Report to the owner and other stakeholders as requested. 7.4.5.4 The Final Test Report should summarize the results of the integrated testing and should include Issues Logs (IL) and Corrective Action Reports (CAR).

Chapter 8 Re-commissioning (Re-Cx) and Retro-commissioning (RCx) of Fire Protection and Life Safety Systems.

8.1* General This chapter provides recommendations for the re-commissioning and retro-commissioning recommendations of active and passive fire protection and life safety systems where installed in existing structures. 8.2 Re-Commissioning. 8.2.1* Fire protection and life safety systems that have been commissioned upon installation in accordance with the commissioning process of Chapter 5 of this standard should be re-commissioned as specified by a re-commissioning plan. 8.2.2 Recommendations for Re-Commissioning. The following should be achieved during re-commissioning. 8.2.2.1 A fire protection and life safety commissioning team should be established and responsibilities shall be assigned in accordance with 5.2.2 8.2.2.2 The fire protection and life safety commissioning team should complete the applicable recommendations of 5.2.1.2, 5.3.1, 5.4.1, and 5.5.2. 8.3 Retro-Commissioning. 8.3.1* Where testing of existing fire protection and life safety systems has not been conducted in accordance with the commissioning process of Chapter 5 of this standard, retro-commissioning should only be specified by a retro-commissioning plan. 8.3.1.1 A fire protection and life safety commissioning team should be established. 8.3.1.2 The responsibilities of the fire protection and life safety commissioning team should be assigned in accordance with 5.2.2. 8.3.1.3 The fire protection and life safety commissioning team should complete the applicable recommendations of sections 5.2.1.2, 5.3.1, 5.4.1, and 5.5.2. 8.3.2 The retro-commissioning plan should be developed from a survey and evaluation of installed fire protection and life safety systems design and existing conditions. 8.3.3 Integrated testing of fire protection and life safety systems should be performed in accordance with Chapter 6.

Chapter 9 Integrated Testing Frequency

9.1* This chapter establishes responsibilities and recommendations for the frequency of integrated testing of existing integrated fire protection and life safety systems. 9.2* The testing recommended by this chapter should apply to all buildings and facilities. 9.3 Integrated Systems Testing 9.3.1 An integrated testing plan specifying the interval for integrated testing should be submitted and approved where required by the AHJ.


9.3.1.1 Systems that have been commissioned upon installation in accordance with the commissioning process of Chapter 4 of this document should have integrated testing completed in accordance with the commissioning plan. 9.3.2 For systems that have not been commissioned, integrated testing should be performed on a periodic basis in accordance with one of the following events: (1) Where new component fire protection and life safety systems are installed and integrated

to existing fire protection and life safety systems. (2) Where existing fire protection and life safety systems are modified to become

component, interconnected systems. (3) Where the interconnections or sequence of operations of existing integrated fire

protection and life safety systems are modified. (4) At intervals specified in an integrated testing plan as approved by the AHJ. 9.3.3* Where integrated tests are not performed in accordance with 9.4.1 or 9.4.2, the integrated test interval should not exceed five years. 9.3.4 Systems that exhibit faults, failures, or indications of such faults or failures in the interconnection, or those found to have deficiencies in the interconnection upon inspection, should be cause for an AHJ to recommend integrated testing as specified in this chapter. 9.3.5 Integrated systems testing should be performed as recommended in Chapter 6. 9.3.6 Phased sequencing of integrated testing should be permitted subject to the approval of the AHJ. 9.4 Documentation See Chapter 6 for documentation recommendations.

Chapter 10 Commissioning Documentation and Forms 10.1* Approved commissioning documents and forms should be used to record commissioning and integrated testing of fire and life safety systems. 10.2 Documents from NFPA and other approved installation standards referenced in the BOD should be utilized. 10.3 Where no form or checklist exists, specific forms or checklists should be developed to document successful testing of systems and components. 10.4* Test documents should be retained by the owner for the life of the system.

Chapter 11 (Reserved)

Annex A Explanatory Material

Annex A is not a part of the requirements of this NFPA document but is included for informational purposes only. This annex contains explanatory material, numbered to correspond with the applicable text paragraphs.

A.1.2 System commissioning and integrated testing is critical to ascertain that systems are installed and function in accordance with the BOD and OPR and that testing is documented. It is not the intent of this standard to supplant the existing requirements of other codes and standards, but this standard can provide the appropriate guidance for a specific system or component where


testing is not otherwise addressed. Such guidance should be developed by the fire protection and life safety commissioning team. A.1.3 Planning for fire protection and life safety in and around a building or structure involves an integrated system approach that enables the system designer to analyze all of the components as a total fire safety system package. A.1.3.1 This standard is not intended to be applied where not required by applicable codes or other requirements of the owners’ project requirements (OPR) or AHJ. A.1.3.1(1) Project infrastructure should include those systems and utilities necessary for the support and operation of the fire protection and life safety systems of the proposed project. These infrastructure items can include the following:

(1) Access roadways for general ingress and egress and those necessary for fire department access in accordance with local codes, standards, and policies

(2) Utility systems for the provisions of electric power, fuel gas, water, and waste water; communication systems, and any other utility system deemed essential for the support of project operations

(3) On-site combined heat and power generation systems, electric power generation plants or systems, fuel gas storage facilities, water supply and storage facilities, and environmental or waste management systems

A.1.3.1(6) Examples of standby power would include power to smoke control systems, stair pressurization systems, smoke-proof enclosure ventilation systems, electric driven fire pumps, fire service access elevators, fire suppression system controllers, and so forth. A.1.3.1(8) Examples include, but are not limited to, floor ceilings and roof decks, doors, windows, barriers, walls, and other fire and smoke control assemblies.

A.1.3.1 (11) Egress system and egress components should include the following: (1) Emergency lighting and exit signs (2) Egress components (e.g., corridors, stairs) (3) Major egress components, such as corridors, stairs, ramps, and so forth (4) Exit path marking systems

A.1.3.2 Fire and life safety systems can have problems during startup and installation. When implemented correctly, a realistic commissioning plan minimizes startup and long-term problems, reduces operational costs, and minimizes future maintenance requirements. A.1.3.2(5) Consideration should be given to providing training for emergency response personnel. A.1.3.3(3) See Figure A.3.3.16 for a sample fire alarm system.


A.1.3.4 5 In order for all of the requirements of NFPA 13 to apply to a project, the specifications need to require the entire commissioning process rather than just referencing NFPA 3. For many simple buildings, NFPA 3 can be considered satisfied by performing the acceptance tests and the inspection, testing, and maintenance required by the NFPA standards for the systems in a building. For example, a building with a simple sprinkler system and alarm system can meet NFPA 3 by meeting the requirements of NFPA 13, NFPA 25, and NFPA 72. In order to invoke the rest of the requirements of NFPA 3, the specifications need to reference 1.3.45. For example, in order to invoke the requirements in the rest of NFPA 3, specifications should read, ―The building fire protection systems shall be designed, installed, tested, commissioned, and maintained in accordance with commissioning process of NFPA 3, Commissioning and Integrated Testing of Fire Protection and Life Safety Systems.‖ Without this specific language, only 1.3.5 of NFPA 3 would apply. A.3.2.1 Approved. The National Fire Protection Association does not approve, inspect, or certify any installations, procedures, equipment, or materials; nor does it approve or evaluate testing laboratories. In determining the acceptability of installations, procedures, equipment, or materials, the authority having jurisdiction may base acceptance on compliance with NFPA or other appropriate standards. In the absence of such standards, said authority may require evidence of proper installation, procedure, or use. The authority having jurisdiction may also refer to the listings or labeling practices of an organization that is concerned with product evaluations and is thus in a position to determine compliance with appropriate standards for the current production of listed items. A.3.2.2 Authority Having Jurisdiction. The phrase ―authority having jurisdiction,‖ or its acronym AHJ, is used in NFPA documents in a broad manner, since jurisdictions and approval agencies vary, as do their responsibilities. Where public safety is primary, the authority having jurisdiction may be a federal, state, local, or other regional department or individual such as a fire chief; fire marshal; chief of a fire prevention bureau, labor department, or health department; building official; electrical inspector; or others having statutory authority. For insurance purposes, an insurance inspection department, rating bureau, or other insurance company representative may be the authority having jurisdiction. In many circumstances, the property owner or his or her designated agent assumes the role of the authority having jurisdiction; at government installations, the commanding officer or departmental official may be the authority having jurisdiction. A.3.2.3 Listed. The means for identifying listed equipment may vary for each organization concerned with product evaluation; some organizations do not recognize equipment as listed unless it is also labeled. The authority having jurisdiction should utilize the system employed by the listing organization to identify a listed product. A.3.2.4 Recommended Practice. There are other standards-making bodies that define the term recommended practice differently. A.3.3.1 Basis of Design (BOD). The basis of design is normally used to assist the commissioning authority and the authority having jurisdiction in the plan review, inspection, and acceptance process. A.3.3.2 Building. The term building is to be understood as if followed by the words ―or portions thereof‖. The intent is to also apply this standard to structures such as roadway and transit tunnels, bridges, towers, fuel storage facilities, and other structures in so far as this document applies.


A.3.3.3.1 Commissioning (Cx). Commissioning is achieved in the design phase by documenting the design intent and continuing throughout construction, acceptance, and the warrantee period with actual verification of performance, operation and maintenance (O&M) documentation verification, and the training of operating personnel. A.3.3.3.2 Commissioning Authority (Cx). A commissioning authority is typically provided and leads the overall fire protection and life safety commissioning team when the commissioning process is applied to more than one building system — that is, total building commissioning. When the commissioning process is only applied to fire and life safety systems, the FCxA can assume the role of the commissioning authority. A.3.3.3.3 Commissioning Plan. The commissioning plan establishes the framework for how commissioning will be handled and managed on a given project. A.3.3.3.6 Re-commissioning (Re-Cx). Re-commissioning can be initiated periodically or in response to building renovation or a change in building use. A.3.3.3.7 Retro-commissioning (RCx). Retro-commissioning is a process that ensures that building systems perform interactively according to the design intent and/or to meet the owner’s current operational needs. This is achieved by documenting the design intent where possible and the current operational needs, measuring the existing performance, implementing necessary operational and/or system modifications, followed by actual verification of performance, verification of operation and maintenance (O&M) documentation, and the training of operating personnel. Retro-commissioning explains the analogy and methodology used by the designers in the design of the systems for the protection of the building, occupants, and emergency response personnel. A.3.3.8 Installation Contractor. Installation contractors often provide shop drawings, working plans, and other related documents. A.3.3.11 Narrative. The narrative is written to assist and expedite the plan review and inspection process by the AHJ. It is maintained on file for use at the time of final inspection and for periodic reviews during future field inspections. It is referenced by the building owner and authority having jurisdiction to insure that all future modifications, alterations, additions, or deletions to the original systems are current and that the original system’s protection and required system performance are not compromised or have not been altered without building or fire official prior review. The narrative should be recognized by all entities that it is one of the key documents associated with the commissioning process. Building owners benefit by knowing how their building’s fire protection and life safety systems work. The narrative provides a procedure including methods for testing and maintenance. A copy of the narrative report should be kept on the premises and should be available for review prior to testing and proposed modifications to any portion of the building’s fire protection and life safety systems. Development Format. The narrative is prepared by a qualified, identified individual who has ―taken charge‖ in the development of an entire coordinated narrative that includes all information regarding the design basis, sequence of operation, and testing criteria associated with all required or non-required fire protection systems set forth by applicable laws, codes, regulations, and local ordinances of the jurisdiction and applicable national and or international standards. The narrative should be submitted with plans and specifications for review and approval by the AHJ prior to the issuance of a building permit. The narrative should be written in a clear conversational format. The construction specifications should not be considered a narrative,


however some applicable portions of the construction specifications could be included to support or clarify the intent of the narrative. The narrative is a stand-alone document, it should be 8-1/2 in. x 11 in. for filing and ease of use by the AHJ and building owners including an administrative cover page identifying the project name, building address, name, address, and phone number of the individual who has ―taken charge‖ in the preparation of the narrative. Commentary. Codes and standards are written in a way to require uniformity in design and construction for all buildings and structures. The codes and standards can be subjective and are subject to interpretation by building owners, designers, and the AHJ; uniformity is not always necessarily achieved. The narrative should attempt to clarify to the AHJ the designer’s intent and interpretation of the code and standards. The AHJ can agree or disagree with the designer’s interpretation. Historically, the requirements for fire protection and life safety systems have become site specific and building code requirements are not uniformly enforced. The size of the community, fire department staffing, fire department equipment availability, and suppression tactics established by the local fire department have affected the uniformity of enforcement. Site specific requirements more or less than that of the building code can have reasonable intent, however this type of enforcement in some cases has proven to be controversial in the applicability of code uniformity. The narrative can be and should be a valuable instrument when accurately prepared, and it will establish a line of communication between the designer and the Authority Having Jurisdiction, resulting in what the building codes and standards mandate, which is uniformity and consensus in the interpretation of the codes and standards. The narrative should be written in a three sectional format and subsections as necessary (methodology, sequence of operation, and testing criteria sections) for clarity and should be limited to a summary. A sample narrative outline can be found in Annex B. A.3.3.16 Sequence of Operation. See Figure A.3.3.16.


Figure A.3.3.16 Sequence of Operation.

A.3.3.18.2 Active Fire Protection System. Examples of active systems include but are not limited to gaseous extinguishing systems, sprinklers, standpipes, dampers or fire alarm systems. A.3.3.18.4 Life Safety System. These can include both active and passive fire protection systems, devices, or assemblies; several items of equipment, processes, actions, or behaviors, grouped or interconnected so as to reduce injuries or death from fire or other life-threatening event. A.3.3.18.5 Passive Fire Protection System. Examples of passive systems include but are not limited to floor-ceilings and roof, door, window, and wall assemblies, spray-applied fire-resistant materials and other fire and smoke control assemblies. Passive fire protection systems can include active components and may be impacted by active systems, such as fire dampers. A.3.3.19.1 Integrated System. An integrated system contains systems that are physically connected and others that are not. An integrated system can contain a combination of fire protection and life safety systems and non-fire protection and life safety systems (i.e. building systems such as elevators, HVAC systems, automatic door closures, etc.) that may or may not be physically connected, but that are required to operate together as a whole to achieve overall fire protection and life safety objectives.

For example, a smoke control system is often activated by water flow in a sprinkler system but the sprinkler system is not physically connected to the HVAC system. The physical connection is

from the sprinkler system to the fire alarm system and then to the building automation system.


Further examples of integrated systems include is the need for wall integrity when using total flooding suppression agents or automatic door closures that are to close upon activation of smoke control systems or stair pressurization systems. See Figure A.3.3.19.1 for examples of integrated

systems.

Figure A.3.3.19.1 Integrated System.

A.3.3.19.2 Interconnected System. Interconnected systems are connected so that a binary output from one system causes a binary input in another system or systems. One example is a waterflow switch that is either open or closed (binary output) which when connected to the input of a fire alarm system can cause multiple outputs in the fire alarm system including sounding the waterflow bell and notification appliances, starting smoke control systems, and so forth. Combined systems are connected so that data from one component system is shared with other component systems, which then make independent decisions to achieve a desired result. The communication can be one-way or two-way, serial or parallel. A combined system can have components that are interconnected too. An integrated system is one in which the components communicate between multiple data processing units. Interconnected systems consist of electrically, optically, or wireless transmissions, normal/not-normal connections, or data transfer protocols such as BACnet and LonWorks. A.3.3.19.2.1 Switch Connections. For purposes of this definition a relay is an electrically controlled switch. An example of a monitored switch is a waterflow switch that is either open or closed (normal/not-normal output) which when connected to the input of a fire alarm system can cause multiple outputs in the fire alarm system including sounding the waterflow bell and notification appliances, starting smoke control systems, and so forth. An example of a relay as a switch connection is for elevator control when a fire alarm relay controls when the fire fighters’ recall occurs through the elevator control monitoring the status of the fire alarm relay. A.3.3.19.2.2 Data Sharing Systems. Data sharing systems are connected such that data from one component system is shared with other component systems, which then make independent


decisions to achieve a desired result. The communication can be one-way or two-way, serial or parallel. A data sharing system can have components that are switch connections too. A.3.3.19.3 Interconnections. Interconnections could consist of electrical binary connections or data transfer protocols. Example of data transfers are BACnet or other data exchange protocols. A.3.3.21.2 Integrated Testing. Integrated testing can include other building systems integrated to fire and life safety systems such as elevator recall or HVAC control. A.3.3.21.3 Pre-Functional Testing. Such testing should follow the original acceptance test at intervals specified in the applicable installation or maintenance standard, and may include procedures recommended by the manufacturer’s published documentation. Pre-functional testing is conducted in preparation for other types of testing. A pre-functional testing checklist is often incorporated into the startup process. This testing is typically conducted according to a checklist developed by the FCxA that incorporates manufacturers’ requirements and insures objectives prior to final acceptance testing. These tests can be complete or partial. In many cases such as with fire pumps per NFPA 20 this is required prior to acceptance testing as the coordination of attendance by multiple AHJs can be required. A.3.3.21.4 Preliminary Testing. Preliminary testing is conducted in preparation for other types of testing. A preliminary testing checklist is often incorporated into the startup process. A.4.2.1.1 Examples of individuals qualified to provide FCxA services can include, but are not limited to, those individuals who are as follows: (1) Registered professional fire protection engineers (2) Registered professional engineers in other disciplines with sufficient knowledge in the applicable fire protection and life safety systems (3) Professionals experienced in the design, operation, or construction of the type of

facility to be commissioned (4) Professionals experienced in the design, operation, or installation of the type of fire

and life safety systems installed The FCxA should have no business relationships (owner, division or subsidiary, partner, operating officer, distributor, salesman, or technical representative) with any fire protection or life safety equipment manufacturers, suppliers, or installers for any such equipment provided as part of this project. As such, qualified independent third-party firms or individuals should be considered for designation as the FCxA. The FCxA should have a minimum of five years experience in facility construction, inspection, acceptance testing, or commissioning as it relates to fire protection and life safety. A.4.2.2.2 Installation contractors should be certified by an organization responsible for certification of technical installation personnel and approved by the AHJ. A.4.2.4 Construction managers should possess skills in the following categories of construction management: (1) Project management planning (2) Cost management (3) Time management (4) Quality management (5) Contract administration (6) Safety management (7) Professional practice This should include specific activities such as defining the responsibilities and management structure of the project management team, organizing and leading by implementing project


controls, defining roles and responsibilities and developing communication protocols, and identifying elements of project design and construction likely to give rise to disputes and claims. A.4.2.5.2 The level of knowledge required should be commensurate with the level of interaction with the systems. A.4.2.6 Governmental AHJs (fire inspection personnel) should have the ability to determine the operational readiness of fire detection and alarm systems and fire suppression systems, given test documentation and field observations, so that systems are in an operational state. Fire inspection personnel should be able to verify code compliance of heating, ventilating, and air conditioning (HVAC) equipment and operations so that the systems and other equipment are maintained in accordance with applicable codes and standards. In addition, fire inspection personnel involved in fire protection system commissioning should be able to witness an acceptance test for integrated fire protection systems so that the test is conducted in accordance with the approved design and applicable codes and standards, and the system performance can be evaluated for compliance. Individuals should be able to demonstrate knowledge of the codes and standards related to the installation and operational requirements of integrated fire and life safety systems, such as elevator recall or operation of a smoke removal system upon activation of fire detection devices, or other integrated operations of fire protection systems in a structure in accordance with the applicable building, mechanical, and/or fire codes of the jurisdiction. A.4.2.7 Governmental AHJs (fire inspection personnel) should have the ability to determine the operational readiness of fire detection and alarm systems and fire suppression systems, given test documentation and field observations, so that systems are in an operational state. Fire inspection personnel should be able to verify code compliance of heating, ventilating and air conditioning (HVAC) equipment and operations so that the systems and other equipment are maintained in accordance with applicable codes and standards. In addition, fire inspection personnel involved in fire protection system commissioning should be able to witness an acceptance test for integrated fire protection systems so that the test is conducted in accordance with the approved design, applicable codes and standards and the system performance can be evaluated for compliance. Individuals should be able to demonstrate knowledge of the codes and standards related to the installation and operational requirements of integrated fire and life safety systems, such as elevator recall or operation of a smoke removal system upon activation of fire detection devices, or other integrated operations of fire protection systems in a structure in accordance with the applicable building, mechanical and/or fire codes of the jurisdiction. A.4.2.6.2 License and/or certification requirements can be provided by the AHJ or other applicable NFPA or industry standards. A.5.1.1 The fire protection and life safety commissioning team should review with the owner and AHJ to determine the systems that should be subject to commissioning. Commissioning might not be required for all facilities, systems, or components. However, acceptance and integrated testing should still be performed. A reasonable degree of protection for life and property can be provided by acceptance and integrated testing for small systems or those integrated systems having simple logic. For examples of roles and responsibilities, see Table A.5.1.1.

Table A.5.1.1


Legend L = Lead P = Participate S = Support I = Inform A = Accept V = Verify

Owner

Facility Manager or Operations Personnel

Insurance Rep

Owner Technical Support

Construction Manager

Installation Contractor

CX Agent

RDP

Planning Stage Identify Commissioning Team

L/A S S P/S

Develop Owner’s Project Requirements

L/A S S S

Develop preliminary commissioning scope

L S S P/S

Develop Preliminary Commissioning Plan

L S S S

Establish budget for all Cx work & integrate costs for commissioning into project budget

L S S

Include time for Cx in initial project schedule

L I I I

Include Cx responsibilities in A/E & CM scope of services

L/A S S

Design Stage Contract for Commissioning Agent Services

L/A P P L

Hold Design Stage Cx meetings

P P P P P L P

Identify project specific responsibilities

L L S S P P

Review Owner’s Project Requirements documentation for completeness & clarity

S S I I L I

Develop Basis of Design

A P P S/A I I L

Perform focused Cx reviews of design drawings & specifications

P P P P S L S

Perform project constructability

P I/P L I/S S


reviews Incorporate appropriate changes to contract documents based upon design reviews

A P I I I L

Refine Owner’s Project Requirements based upon Design Stage Decisions

A P S I L S

Create Cx specifications including testing protocols for all commissioned equip./systems

I I I P/S S L S

Integrate Cx activities into project schedule

A I I L S I

Coordinate integration issues & responsibilities between equipment, systems & disciplines

A I P/S S V L

Update Commissioning Plan

A I I I S L I

Incorporate commissioning requirements into Construction Contractor’s Scope of Work

A I L S S

Construction Stage Revise Commissioning Plan as necessary

A I I I S I L

Review submittals applicable to equipment/systems being commissioned

I A P A S S L

Review project submittals for construction quality control & specification conformance

I I/P A L S V

Develop functional test procedures and documentation formats for all commissioned

A I I S/A S S I L


equipment & assemblies Include Cx requirements and activities in each purchase order and subcontract written

A A L V

Develop construction checklists for equipment/systems to be commissioned

A P I I I L

Install components & systems

I I A A L V

Review RFIs and changes for impacts on Cx

A I I/S S L S V

Demonstrate operation of systems

I P/I I P L V

Complete construction checklists as the work is accomplished

I I I I S L A

Continuously maintain the record drawings and submit as detailed in the contract documents

A S I S L V

Coordinate functional testing for all commissioned systems & assemblies

I I P/A I S S L/A

Perform quality control inspections

I I I/P L S P/I

Maintain record of functional testing

I I I I/P I S S L

Prepare Cx Progress Reports

A I I/P I P S L

Hold Construction Phase Cx meetings

P P P P P P P L

Maintain master Issues Log

I I I I S I L

Review equipment warranties to ensure owner responsibilities are clearly defined

I I S S L

Implement training program for Operating Personnel

I P P I/S P S S L


Compile and deliver Turnover Package

A A S S L S/V

Deliver Commissioning Record

A P I S S S L

Occupancy Stage Coordinate & supervise deficiency corrections

A P I I/S L S I

Coordinate & supervise deferred & seasonal testing

A P I S I

Review & address outstanding issues

A P I I I/S S S I

Review current building operation at 10 months into 12 month warranty period

A P I I S S I

Address concerns with operating facility as intended

A P I I S S S S

Complete Final Commissioning Report

A P I/P I I

Perform Final Satisfaction Review with Customer Agency 12 months after occupancy

A S I S S S

The following definitions apply to the Roles & Responsibilities Matrix Lead (L) = Direct and take overall responsibility for accomplishment Support (S) = Provide assistance Accept (A) = Formally accept either in writing or verbal communication depending on the situation Participate (P) = Take part in the activity (i.e, attend meetings, etc.) Inform (I) = Make the party aware of the activity or result or provide a copy of the deliverable Verify (V) = Confirm the accuracy or completeness of the task A.5.1.2 Figures A.5.1.2(a), A.5.1.2(b), and A.5.1.2(c) are offered to provide an example of how to perform a commissioning plan.


Figure A.5.1.2(a) The Commissioning Process. Figure A.5.1.2(b) The Commissioning Process. Figure A.5.1.2(c) The Commissioning Process.

A.5.2.1.1 The fire protection and life safety commissioning team can be part of a larger total building fire protection and life safety commissioning team with team members whose focus is on commissioning electrical, mechanical, plumbing, and electronics systems. The overall team can be led by a commissioning authority whose responsibility is defined in ASHRAE Guideline 0. The individuals and entities listed are not all inclusive and should be modified on a project by project basis. If the entity listed is not part of the project, it is not the intent of this standard to require those entities to become part of the project fire protection and life safety commissioning team. The number of members of the fire protection and life safety commissioning team should be determined by project type, size, and complexity. For example, a multiple building project can require more than one FCxA, all of which are overseen by a single FCxA. A.52.1.2 Fire protection and life safety commissioning team members should be selected as their role in the project is established. For example, manufacturer’s representatives can not be identified until the design phase and therefore cannot participate during the planning phase. A.5.2.1.2(6) This analysis should involve making direct contact with the various federal, state, and local regulatory agencies to verify what laws, rules, regulations, codes, standards, policies, and practices are in force and applicable to the project. A.5.2.2.1(13) See Section 7.4.3 for the responsibilities of the ITa. The responsibilities of an ITa may be fulfilled by the FCxA. A.5.2.2(12) The definition of AHJ as set forth in 3.2.2 and A.3.2.2 provide information as to the large range of entities and individuals that can be an AHJ. Any and all AHJs should be included as part of the fire protection and life safety commissioning team to the extent they are deemed to need to be involved. A.5.2.2.2 The owner, FCxA, and RDP should be part of the fire protection and life safety commissioning team at this phase. Other key team members will be identified and selected as the project progresses and as their roles and responsibilities require their participation. A.5.2.2.4.2 Examples of a designated representative include the occupant, management firm, or managing individual. Delegation can be through specific provisions in a lease, written use agreement, or management contract. A.5.2.2.5.1 A CxA will only be part of the fire protection and life safety commissioning team when the fire protection and life safety systems are included in a larger building commissioning process. If the scope of the project includes fire protection and life safety systems only, then a CxA will not be present nor part of the fire protection and life safety commissioning team. A.5.2.2.11. Discussions should be performed between insurance representatives and the fire protection and life safety commissioning team during the planning phase to determine the overall scope of services to be provided by the insurance representative. A.5.2.2.11(8). This includes adequate signage on equipment for operation of a fire protection system and complete record drawings. A.5.2.3.2 The OPR development should include the AHJ in order to provide input regarding issues of fire department operations and access to the site and facility. Other appropriate issues for review might include emergency medical response and police issues. A.5.2.3.3 The OPR documentation should include concept architectural documentation with a focus on fire and life safety. The applicable codes and standards must recognize any state,

DRAFT


Figure 4.1.3(b) The Commissioning Process

DRAFT


Figure 4.1.3(c) The Commissioning Process

4.2 Pre-Design Phase.


county, city, or local amendments to the codes and standards. The AHJ should be included in the development of the OPR as early as possible in the process recognizing project confidentiality. The OPR can also incorporate budget and schedule issues. The OPR format should include the following sections: Introduction, Owners Key Project Requirements (i.e., insurance underwriter’s standards), General Project Description, Project Objectives, Functional Uses, Occupancy Requirements, Budget Considerations and Limitations, Performance Criteria, and Project History. This OPR can be a portion of the overall total building commissioning OPR. See Annex C for a sample OPR. The OPR is intended to be a living document that is regularly updated and modified. During the design phase the OPR can change significantly based on the needs of the proposed design. Variances to code requirements can be sought in order to meet project needs and will need to be appropriately documented in the OPR. The construction phase will include record drawings of the installed conditions of the fire and life safety systems. The OPR will then have the base documentation necessary to aid the building operators in any upgrades or changes to the building fire and life safety systems. A.5.2.4.2 All information in the commissioning plan must be project specific. The suggested structure of the commissioning plan is as follows. (1) Introduction — purpose and general summary of the plan (2) Commissioning scope — identifies which building assemblies, systems, subsystems, and

equipment will be subjected to the commissioning processes identified in Chapter 4 (3) General project information — overview of the project, emphasizing key project

information and delivery method characteristics, including the OPR and project BOD (4) Team Contacts — project-specific fire protection and life safety commissioning team

members and contact information (5) Communication plan and protocols — documentation of the communication channels to

be used throughout the project. (6) Commissioning process — detailed description of the project specific tasks to be

accomplished during the planning, design, construction, and tenant occupancy stages with associated roles and responsibilities

(7) Commissioning documentation — list of commissioning documents required to identify expectations, track conditions and decisions, and validate/certify performance

(8) Commissioning schedule — specific sequences of operation of events and relative timeframes, dates, and durations

A.5.2.4.3(12). Warranty review includes a review of all documentation relating to inspection, testing, maintenance, repair, and/or inadvertent system activation that occurred during the warranty period. The purpose of the warranty review is to determine if any modifications or adjustments to the system(s) are required. A.5.3 Construction phase documents can be started during the design phase. These documents are intended to include working plans, shop drawings or fabrication drawings, as well as operations and maintenance manuals. These documents can be created during the design or construction phases of a project without changing the responsibilities of those charged with creating these documents. A.5.3.1 If commissioning starts later in the design or construction process, the requirements of the previous commissioning phases should be reviewed and implemented to the extent practical. A.5.3.1(10) The issues and changes should be included in a log which documents the date the issue was raised, the responsibility for resolution of the issue, the resolution of the issue, and the date the issue was resolved.


A.5.3.1(12) Include checklists requiring when AHJs and Cx Team members are to be present during acceptance testing. A.5.3.2.2 Editions referenced in this document are the latest available during the development of this standard. The user should always consult the AHJ to ensure compliance with local requirements. A.5.3.2.7 FCxA should review manuals, standards, manufacturers’ documents and other sources to determine the equipment and tools necessary for each phase of testing. FCxA should also confirm which contractors or other appropriate parties should calibrate and schedule the availability of the tools and equipment for the testing dates. A.5.3.3.3 O&Ms should be organized and written in a complete and concise manner to improve the ability of the building operator or maintenance technician to fully understand the performance characteristics of the system and the maintenance requirements necessary to achieve the intended performance. O&Ms should be of durable materials and contain complete project identification including, but not limited to, the following: (1) Title sheet including the complete name and address of the project, complete name and address of the installing contractor (including telephone number for emergency service) (2) Complete table of contents (3) Systems design intent documentation (4) Complete list of equipment (5) List of equipment suppliers and/or manufacturers (6) Operation and maintenance instructions for major components (7) Inspection and test reports (8) Recommended spare parts (9) Riser diagrams or schematic drawings (10) "As-built" drawings and calculations (11) Warranty (12) Other special requirements of the installation specification or installation standard such as valve tags and charts, hydraulic data nameplate information (for sprinkler systems), and so forth A.5.3.5.1 Passive fire protection systems include but are not limited to the following: (1) Fire and Smoke Dampers (2) Fire and Smoke Doors (3) Through Penetration Fire Stops (4) Smoke vents (5) Smoke drafts (6) Smoke and fire assemblies A.5.4.3.2.1 Examples of fire protection systems with no operating components include, but are not limited to: (1) Through-penetration fire-stop systems (2) Rated fire and smoke assemblies (3) Spray-applied fire-resistant material A.5.4.5 Training often needs to begin in the construction phase; however, some systems may require ongoing training during the occupancy and post-construction phases. A.5.4.6 This can include documents required by other codes and standards or by authorities having jurisdiction.


A.5.5.2(3) For example, it can be appropriate to test stair-pressurization in both winter and summer conditions. A.5.5.2(8) This would include a digital copy of site-specific software for building automation or other integrated systems. A.5.5.2(9) The building owner or their designated representative should place the building systems through inspection, testing, and maintenance prior to the expiration of the warranty. This helps identify needed repairs. A.5.5.3.1 Additions, modifications, or alterations to systems can cause unintended consequences. The testing procedure should be re-evaluated to make sure that the repeat testing is adequate to determine the correctness of the revision. A.5.5.3.2 Significant changes to the OPR can precipitate a need to do a re-commission process. A.5.5.3.3 Design documents should be kept for the life of the facility. When there is a change in ownership the documents should be transferred to the new owner. A.5.5.4.1 A quality training session for system operation and maintenance will generally include the following components:

(1) Practical examples and hands-on operation of the system (2) A course agenda (3) The expected system performance (4) Problems or modifications encountered during construction (5) Routine testing and maintenance requirements (6) Operation and maintenance manuals

Additional training should be conducted after several years. This will allow the facility staff to be trained on system upgrades or modifications. This can be accomplished in conjunction with lesson-learned workshops. A.5.5.4.2 An appropriate time to schedule the initial training is at system acceptance in order to maximize its value to the participants. Secondary systems training should be held after integrated testing has been completed to allow follow-up questions and the opportunity to ask questions about situations and problems that have occurred after final acceptance. A.5.5.4.3 Sign-in sheets are useful for the contractor and fire protection and life safety commissioning team to demonstrate that training was conducted. Training sessions can be recorded to allow for future reference of the material and training for new employees. A.5.5.4.4 Continuous training can ensure the systems are maintained and tested properly and the building or structure operates successfully. A.6.2.1 Interactions include physical interconnections and impacts between systems that are not physically connected. Passive fire protection features can be impacted by active systems. A.6.2.1.4 For individual systems to work together there must be consideration of the various interconnections that can occur. Some interconnections can be directly connected and others can be more remotely involved. An example of the first is an emergency power off (EPO) system that in its operation causes loss of power to a fire protection system or the EPO system itself. An example of the second is an atrium smoke control system that functions correctly mechanically, but the air movement prevents the automatic doors from closing. A.6.2.2.2(2) Examples of equipment capacity ratings are as follows:

(1) Electrical: amperage, voltage, wattage, and so forth

(2) Strength: working pressure, tensile, structural, and so forth

(3) Life expectancy: years, number of cycles, and so forth


A.6.2.2.2(3) A system description should be produced as an engineering document to describe system integration and functions. Each component system within the integrated system should be defined. Each interconnection should be defined. A fire hazard analysis should be produced to describe active and passive fire protection features and describe the interactions between the fire protection features of the building. A.6.2.2.2(5) This is often done by using a sequence of operation to plot inputs and outputs. A.6.2.2.2(6) In addition to noting the location of the interconnection on the drawing, it is helpful to have a labeling system to identify the interconnections in the installation. A.6.2.2.2(8) The interactions within integrated systems need to be tested often enough to ensure reliability. A.6.2.2.2(11) Examples of formats for deliverables are as follows:

(1) Drawings on paper or electronic format (2) Electronic format such as PDF or DWG (3) Media format such as floppy disk, flash drive, CD, or FTP (4) Owner’s manuals on paper, accessible from Internet hyperlink, and so forth

A.6.4.2 It is recommended that design documents be retained for the life of the appropriate systems. A.7.2.1 Interconnected systems have component systems that can operate alone for a specific purpose and can be independent of other systems. Integrated systems contain multiple systems that must work in concert to achieve the fire protection and life safety goals. These interconnections need to be tested for proper operation in addition to the acceptance testing of the individual components.

A.7.2.1(2) Components of interconnected systems should be installed, maintained and tested in accordance with the applicable codes and standards. Examples include but are not limited to those systems listed in Section 1.3 A.7.3.1 The goal of integrated testing is to verify that fire protection and life safety systems operate as designed and as required by codes and standards. The scope of work can include, but not be limited to, the following: (1) Review of building plans and specifications (2) Review of applicable codes and standards (3) Review of one line riser diagram of smoke control and exhaust systems, schedules for

ducts, fans, dampers, and submittals for damper operators and sequence of operation. Each piece of equipment should be numbered and identified.

(4) Review of system testing matrices and as-built drawings. (5) Provide a testing matrix checklist of integrated systems. (6) Review final Testing and Balancing (TAB) reports. (7) Review one line riser of emergency electric system. (8) Review equipment software submittals. (9) Establish a team of testing participants and assign duties. (10) Coordinate pre-test meetings with stakeholders. (11) Implement integrated testing by appropriate methods, verify and document operation of

interface equipment under normal and emergency power after all trades complete their work.

(12) Correct problems and retest.


(13) Submit final report and documentation. A.7.3.2 The following are examples of subsystems that may be interconnected in integrated systems. (1) Fire alarm system (2) Emergency communication systems (ECS) (3) Building automation management system (4) Means of egress systems and components (5) Heating, ventilating, and air conditioning (HVAC) system (6) Gas detection system (7) Normal, emergency and standby power systems (8) Automatic sprinkler system (9) Fixed fire suppression and control systems (10) Automatic operating doors and closures (11) Smoke control and management systems (12) Explosion prevention and control systems (13) Elevator and pedestrian movement systems (14) Security systems (15) Commercial cooking operations A.7.3.3 Fire protection or life safety systems can operate equipment that is not necessarily part of the fire protection or life safety system. One such example is shunt trip breakers that should be tested for proper operation. A.7.3.5 Additions, modifications, or alterations to systems can cause unintended consequences of operation to the interactions of integrated systems. The testing procedure should be re-evaluated to ensure repeat testing is adequate to determine the correctness of the revision. A.7.4.3 Examples of the responsibilities of an ITa are: (1) Review the installation contractor requirements. (2) Review the design and construction documents and specifications for each fire protection

and life safety system and their associated subsystems. (3) Develop the integrated systems testing plan. (4) Document integrated test performance (5) Coordinate the scheduling of trades to perform integrated testing of systems and sub-

systems.

A.7.4.5 Refer to Annex C for sample forms. A.8.1 Re-commissioning and retro-commissioning should be considered where expansions, improvements, or additions to existing structures require commissioning of the new fire protection and life safety systems in accordance with the commissioning process of Chapter 5 of this standard. Integrated testing should be considered at intervals appropriate to the structure and systems present. A.8.2.1 The integrated testing should be considered as a coordination of the required annual or other periodic fire protection and life safety systems testing with each other and with those interconnected fire protection and life safety systems for which no testing is required by other standards. Intervals for integrated testing can be phased or adjusted based upon the building size and complexity. A.8.3.1 Retro-commissioning could be required by the adopted building or fire code, not this standard. The scope is clear that when commissioning is required, this standard should be


followed. When the commissioning process is not required by the AHJ then compliance with this document could be as simple as following the inspection testing and maintenance standard for the system installed. On-site surveys should determine if or how new modifications, repairs reprogram have impacted existing systems or functions and should include the commissioning process tasks of 5.3.2.2.4, 5.3.5, and 5.3.5.4. A.9.1 The purpose of integrated fire protection and life safety systems testing is to verify that the existing systems provided in a building or facility function together as originally intended. A.9.2 The recommended testing of fire protection and life safety systems should apply, but not be limited, to the items listed in Section 1.3. A.9.3.3 It is not the intent to prescribe a periodic five-year integrated testing interval if the recommendations of 9.3.1 or 9.3.2 are met. A.10.1 The forms shown in Annex D are examples of the documentation required by this standard. A.10.4 The documents should be maintained at the site, but this might not always be practical. If the test documents are kept somewhere other than on-site, then the owner should be knowledgeable of the storage method and location of the records.

Annex B Sample Basis of Design Narrative Report

This annex is not a part of the requirements of this NFPA document but is included for informational purposes only. B.1 The narrative should be written in a three-section format including subsections as necessary (methodology, sequence of operation, and testing criteria sections) for clarity and should be limited to a summary. This annex presents a sample format for a narrative report.

B.2 Methodology Section.

B.2.1 Subsection 1: Description. This section should identify specific features of a building that contributes to the overall understanding of the fire protection and life safety systems and features to be provided as part of the design and construction.

(1) Building and/or structure use group classification in accordance with applicable building code of the jurisdiction

(2) Total aggregate square footage of building (3) Building height (4) Number of floors above grade (5) Number of floors below grade (6) Square footage per floor (7) Type(s) of occupancies, hazard classifications, processes (8) Type(s) of construction (9) Hazardous material usage and storage (10) Method of storage arrangements of commodities (11) Site access arrangement for emergency response vehicles

B.2.2 Subsection 2: Applicable laws, regulations, codes, ordinances, and standards. This section identifies regulatory requirements of the jurisdiction that have or can have an impact in


the design and approval of fire protection and life safety systems. This section requires the preparer of the narrative to conduct a comprehensive regulatory research such as the following:

(1) Building code fire protection and life safety system requirements (2) NFPA standards or other applicable recognized standards and edition used for design and

or installation of each specific fire protection system (3) Applicability of any special laws of the jurisdiction that can supersede a code or standard (4) Applicability of local by-laws or ordinances of the jurisdiction (5) Applicability of other codes such as plumbing, elevator, electrical codes that can have an

impact on the design, installation, and testing of the fire protection and life safety systems (6) Applicability of any federal laws such as OSHA, ADA, or other governmental entity

B.2.3 Subsection 3: Design responsibility for fire protection and life safety systems. This section identifies the accountability (required by the jurisdiction) for a specific fire protection and life safety system design and the accountability for the integration of the fire protection systems constituting a building or structures fire protection and life of safety system(s). There could be options permitted by the jurisdiction.

(1) The RDP fully designs (complete layout and calculation) and specifies the fire protection and life safety system or systems to be installed, reviews and approves the installing contractor’s shop drawings, and certifies system installation (s) for code compliance at completion. There could be multiple RDP associated with a project and should be identified as appropriate.

(2) The RDP provides a partial design and specifies the design criteria to be used by the installing contractor(s), who finalizes the system layout and provides calculations to confirm the design criteria. The RDP certifies system installation for code compliance at completion.

(3) Design-build, the installing contractor for a specific fire protection and life safety system completely designs and specifies if permitted by the governmental jurisdiction (develops a full system layout, design criteria, and calculations) installs the system, and certifies system installation for regulatory and applicable standard compliance at completion. There can be a RDP involved but not necessarily.

Whichever above method is selected, the project requires a qualified person to assume responsibility for the coordination of fire protection and life safety systems requiring integration, forming an entire building fire protection and life safety system.

B.2.4 Subsection 4: Fire protection and life safety systems to be installed. This section should identify key performance design criteria and features for each specific fire protection system.

(1) Water supply system such as municipal or private systems, fire mains and hydrants, storage tanks, and fire pumps (2) Automatic sprinkler systems, such as wet, dry, pre-action (3) Standpipe systems, such as wet, dry, and classification (4) Fire alarm systems, such as manual, automatic detection, evacuation signals (5) Automatic fire extinguishing systems, such as dry chemical, clean agent


(6) Manual suppression systems (7) Smoke control/management systems, such as automatic smoke exhaust, stair pressurization (8) Commercial cooking equipment and exhaust system fire suppression system(s), such as wet chemical or automatic sprinklers (9) Emergency power systems, such as applicability to fire protection and life safety systems (10) Hazardous material and process protection, special protection (11) System supervision, such as method of 24 monitoring conditions of fire protection and life safety systems (12) Passive systems including doors, walls, floors, ceilings, and roof decks The description (specific features) for the above fire protection systems should also indicate if the system(s) are as follows:

(1) Required by laws, codes, standards, ordinance, and so forth

(2) Non-required, building owner provides voluntarily and/or requirement of insurance entity

(3) A complete new system (4) An addition or expansion to existing system (5) A modification/repair to existing system (6) Level of protection to be provided, 100 percent or partial protection or exempt by

regulatory code B.2.5 Subsection 5: Consideration used in the design methodology. This section identifies the designer’s intent in the overall design and criteria development of the fire protection and life safety systems.

(1) Building occupant notification and evacuation procedures (2) Emergency response personnel, site, and systems features (3) Safeguards, fire prevention, and emergency procedures during new construction and

impairment plans associated with new and/or existing system modifications (4) Method for future testing and maintenance of systems and documentation (5) Special requirements or request of the authority having jurisdiction

B.2.6 Subsection 6: Alternatives. This section identifies the designer’s intent to deviate from prescriptive requirements of regulatory codes and standards with alternative methods.

(1) Application of performance-based design in lieu of prescriptive code requirement (2) Interpretation/clarification between designer and authority having jurisdiction (3) Waiver or variance sought and or required by the authority having jurisdiction

through the regulatory appeal process B.3 Sequence of Operation Section. This portion of the narrative is generally a difficult section to write as it entails the specific operation of the fire protection and life safety systems, system devices and equipment and their related integration depending on the complexity of the systems installed. The preparer of the narrative should have an overall understanding and knowledge of how all the fire protection and life safety systems should function when integrated together.


B.3.1 Subsection 1

(1) An operational description of either a system or specific devices within a system and the resulting action associated with the operation of the system or specific devices.

(2) The operational description should include all interconnected (integrated) fire protection and life safety systems and devices required or non-required forming an entire building fire protection and life safety system.

(3) All signage indicating equipment location, operational and design features, and certified documents attesting to system installation integrity.

(4) The narrative sequence of operation description should be specifically coordinated with the input and output sequence of operation developed for the systems operation.

This section of the narrative report can be brief as in a simple system such as a one-story 15,000 ft2 mercantile building with only a sprinkler system and manual fire alarm pull boxes, notification devices and system supervision, or complex, such as in a 25-story high-rise with fire pumps, emergency generator, fire alarm and sprinkler zones, automatic standpipes, automatic voice and manual evacuation signals, smoke management system, automatic elevator recall, special extinguishing systems, remote annunciation, automatic locking devices, alarm retransmission methods, and emergency response procedures.

The sequence of operation of a building fire protection and life safety system, particularly with complicated systems, must be reviewed and understood by the building owner, the authority having jurisdiction and the entities responsible for installation (generally the fire alarm and building automated systems programming technicians) and future testing and maintenance after the building has been issued a certificate of occupancy. A team approach should be used by developers, designers, equipment suppliers, contractors including the authority having jurisdiction (more specifically emergency response personnel, such as the local fire department) to clearly describe and understand the proper operation and use of the integrated fire protection and life safety systems.

When a complex system is proposed, the initial narrative report of the sequence of operation should be viewed as a draft. At various stages of system installation(s), modifications could be made due to design changes, equipment changes, new technology availability, and/or changes to codes and standards that would require system modifications. The preparer of the narrative should be familiar with any and all changes to the systems and submit a final accurate narrative for approval and/or acceptance by the authority having jurisdiction, building owner, and other entities prior to witnessing system(s) operational acceptance and commissioning testing.

Communication between the building owner, designers, builders, and the authority having jurisdiction is an important element particularly in this phase, as the codes and the standards tend to be flexible and interpretative relative to sequences of operation of the integrated fire protection and life safety systems.

B.4 Testing Criteria Section. This section of the narrative report should be broken down into the following three sections.

B.4.1 Subsection 1:Testing Criteria. This section identifies the individual in charge who will coordinate the final acceptance testing and witnessing by the authority having jurisdiction.


Personnel

(1) Identification of qualified person(s) in charge (should be the FCxA and/or multiple agents if applicable) for setting up and coordinating all preliminary testing and final testing.

(2) Method of verification and confirmation by the qualified person(s) in charge that all fire protection systems, equipment, and devices have been individually tested and tested as an entire system when specific systems are integrated to form a building fire protection and life safety system.

(3) Method of coordination by qualified person in charge of all designers, contractors, equipment distributors, owners representatives, and the authority having jurisdiction required to perform and/or witness all testing, testing dates and times, notification to public utilities, and personnel required to perform all required testing as a system or individual system component testing.

B.4.2 Subsection 2: Equipment and Tools. This section will identify the necessary equipment available on site at time of witnessing the operational features and/or integrated performance of the fire protection and life safety systems that require validation by the owner and/or the authority having jurisdiction to expedite the acceptance and commissioning testing.

(1) Identification of equipment, documents, and procedures to be used to verify system performance and confirm design methodology and specifications, code and standards compliance, and accuracy of fire protection and life safety system(s) sequence of operation.

(2) Examples include but are not limited to the following:

(a) Manufacturer’s instructions

(b) Specification instructions

(c) Requirements of the authority having jurisdiction

(d) Narrative, sequence of operation section

(e) Smoke machines, smoke candles

(f) Sound meters

(g) Fire hoses, nozzles

(h) Flow measuring devices

(i) Gauges

(j) Air balancing and air measuring meters

(k) Door force closing and opening measuring devices

(l) Voltage meters


(m) Magnets

(n) Communication radios

(o) Fire department equipment

(p) Special tools, keys

(q) Ladders

(r) Safety equipment

(s) Notifications announcements

(t) Signs

(u) Charts, forms, checklist, logs

(v) Acceptance test forms

B.4.3 Subsection 3: Approval Requirements. This section identifies all the close out documents required by the owner and the authority having jurisdiction as part of the overall commissioning process.

(1) Identify method of approval (acceptance) required (verbal or written) from the owner and the authority having jurisdiction if system satisfied all applicable code and standards compliance requirements

(2) Identify method of remedial action when a system or portion of a system fails to operate as specified and or as required by codes and standards or the sequence of operations

(3) Documentation to be submitted at completion verifying that systems are in compliance with all applicable codes and standards, requirements of the authority having jurisdiction, narrative, design and specifications, and sequence of operations

(4) Documentation to be submitted to the authority having jurisdiction listing names, addresses, and telephone numbers of personnel for emergency notification

Annex C Sample Commissioning Documentation

C.1 The forms listed in this annex are recommended as useful tools to document critical path activities related to systems commissioning and project management,. It is not the intent of this standard to mandate the use of these forms. The user is encouraged to modify the forms or use other documentation to capture and document pertinent commissioning related activities.

C. 1.1 Basis of Design. Figure C.1.1 can be used to capture the OPR as required by Section 4.3.2. (See Figure C.1.1 Basis of Design).

C.1.2 Equipment Scope and Responsible Parties. Figure C.1.2 is intended to identify the area and application of each fire and life safety system. The form can be used in conjunction with the BOD (See Figure C.1.2).


C.1.3 Project Schedule. The project schedule can be any adaptation of a spreadsheet. The example shown in Figure C.1.3 should be modified to suit the specific parameters of each project.

C.1.4 Project Management Forms. Figures C.1.4 through C.1.12 are examples of project management documentation that should be used on most projects where commissioning is required. Any adaptation of these forms should be permitted to document appropriate commissioning activities.

C.1 Sample Project Information Sheet.

C.2 Sample Project Schedule.

C.3 Sample Pre-Installation Checklist.

C.4 Sample Basis of Design (BOD).

C.5 Sample Training Plan.

Annex D Additional Publications

This annex is not a part of the requirements of this NFPA document but is included for informational purposes only. D.1 General. The documents or portions thereof listed in this Annex are referenced within this standard and should be considered for use in the commissioning process. D.2 NFPA Publications. National Fire Protection Association, 1 Batterymarch Park, Quincy, MA 02169-7471.

NFPA 11, Standard for Low-, Medium-, and High-Expansion Foam, 2005 edition. NFPA 12, Standard on Carbon Dioxide Extinguishing Systems, 2008 edition. NFPA 12A, Standard on Halon 1301 Fire Extinguishing Systems, 2004 edition. NFPA 13, Standard for the Installation of Sprinkler Systems, 2007 edition. NFPA 13D, Standard for the Installation of Sprinkler Systems in One- and Two-Family Dwellings and Manufactured Homes, 2007 edition. NFPA 13R, Standard for the Installation of Sprinkler Systems in Residential Occupancies up to and Including Four Stories in Height, 2007 edition. NFPA 14, Standard for the Installation of Standpipe and Hose Systems, 2007 edition. NFPA 15, Standard for Water Spray Fixed Systems for Fire Protection, 2007 edition. NFPA 16, Standard for the Installation of Foam-Water Sprinkler and Foam-Water Spray Systems, 2007 edition. NFPA 17, Standard for Dry Chemical Extinguishing Systems, 2008 edition. NFPA 17A, Standard for Wet Chemical Extinguishing Systems, 2008 edition. NFPA 20, Standard for the Installation of Stationary Pumps for Fire Protection, 2007 edition. NFPA 22, Standard for Water Tanks for Private Fire Protection, 2008 edition. NFPA 24, Standard for the Installation of Private Fire Service Mains and Their Appurtenances, 2007 edition.


NFPA 25 Standard for the Inspection, Testing and Maintenance of Water Based Fire Protection Systems, 2008 edition. NFPA 69, Standard on Explosion Prevention Systems, 2008 edition. NFPA 72®, National Fire Alarm Code®, 2007 edition. NFPA 80, Standard for Fire Doors and Fire Windows, 2007 edition. NFPA 90A Standard for the Installation of Air-Conditioning and Ventilating Systems, 2002 Edition NFPA 90B Standard for the Installation of Warm Air Heating and Air-Conditioning Systems, 2006 Edition NFPA 92A, Standard for Smoke-Control Systems Utilizing Barriers and Pressure Differences, 2006 edition. NFPA 92B, Standard for Smoke Management Systems in Malls, Atria, and Large Spaces, 2005 edition. NFPA 96, Standard for Ventilation Control and Fire Protection of Commercial Cooking Operations, 2008 edition. NFPA 101®, Life Safety Code®, 2006 edition. NFPA 101A Guide on Alternative Approaches to Life Safety 2007 edition NFPA 105, Standard for the Installation of Smoke Door Assemblies and Other Opening Protectives, 2007 edition. NFPA 110, Standard for Emergency and Standby Power Systems, 2005 edition. NFPA 111, Standard on Stored Electrical Energy Emergency and Standby Power Systems, 2005 edition. NFPA 115 Standard for Laser Fire Protection, 2003 edition NFPA 221, Standard for High Challenge Fire Walls, Fire Walls, and Fire Barrier Walls, 2009 edition. NFPA 720 Standard for the Installation of Carbon Monoxide (CO) Warning Equipment in Dwelling Units, 2005 edition NFPA 731, Standard for the Installation of Electronic Premises Security Systems, 2006 edition. NFPA 750, Standard on Water Mist Fire Protection Systems, 2006 edition. NFPA 780, Standard for the Installation of Lightning Protection systems, 2008 edition. NFPA 820, Standard for Fire Protection in Wastewater Treatment and Collection Facilities NFPA 1221, Standard for the Installation, Maintenance, and Use of Emergency Services Communications Systems, 2007 edition. NFPA 2001, Standard on Clean Agent Fire Extinguishing Systems, 2008 edition. NFPA 2010 Standard for Fixed Aerosol Fire-Extinguishing Systems, 2006 edition. NFPA 5000 Building Construction and Safety Code, 2006 edition.

D.3 Other Publications. D.3.1 ASHRAE Publications. American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. 1791 Tullie Circle NE, Atlanta, GA 30329

ASHRAE Guideline 0 The Commissioning Process, 2005 D.3.2 ASME Publications. American Society of Mechanical Engineers, Three Park Avenue, New York, NY 10016-5990.

ANSI/ASME A17.1 Safety Code for Elevators and Escalators, 2000.


D.3.3 CEN Publications. European Committee for Standardization, 36 rue de Stassart, B-1050, Brussels.

EN12845. D.3.4 NIBS Publications. National Institute of Building Sciences, 1090 Vermont Avenue, NW, Suite 700, Washington, DC 20005-4905

Using the Commissioning Process Guidelines (NIBS) D.3.5 Standards Australia Publications. Standards Australia, Level 10 The Exchange centre, 20 Bridge St., Sydney / GPO Box 476. Sydney, NSW 2001.

AS 1670.1-2004 Fire Detection, Warning, Control and Intercom Systems – System Design, Installation and Commissioning.

AS 2419.1-2005 Fire Hydrant Installations – System Design, Installation and Commissioning.

AS 2665-2001 Smoke/Heat Venting Systems – Design, Installation and Commissioning. AS 4528.1-1999 Water Mist Fire Protection Systems – System Design, Installation and Commissioning.

D.3.6 ULC Publications. Underwriters’ Laboratories of Canada, 7 Underwriters’ RD., Toronto, ON M1R3B4

ULCS537 Verification of Fire Alarm Systems CAN/ULC-S575 Commissioning of Life Safety and Fire Protection Systems