Security Sales & Integration

November 2012

SSI serves security installing contractors providing systems and services; surveillance, access control, biometrics, fire alarm and home control/automation. Coverage in commercial and residential product applications, designs, techniques, operations.

Issue link: https://securitysales.epubxp.com/i/90752

Contents of this Issue

Navigation

Page 27 of 83

Fire Side Chat STEPS SET STAGE FOR STANDARD SIGN-OFF by Shane Clary Shane Clary, Ph.D., has more than 37 years of security and fi re alarm industry experience. He serves on a number of NFPA technical committees, and is Vice President of Codes and Standards Compliance for Pacheco, Calif.-headquartered Bay Alarm Co. smclary@bayalarm.com Fire/Lif Fire/Life-Safety standards endure much analysis and scrutiny by a number fe-Saafety t standards d endur e and u e much analysi As these decisions affect installing professionals, it is wise to be familiar with the number of committees and interested parties en route to ratifi cation.o . As these dec sions affe h process and e of committees n intter e is n participate W ect insttalliing pro e ested parties en route to ra ofess atifi cation sionaalsl , it is wiise to be familiar with the process and participate where and when appropriate. t where and when appropriate. elcome to the second and concluding dis- cussion on the code and standards-making process within the National Fire Protection Association (NFPA). Part 1 covered the fi rst- and second-draft meetings, which we will now expand upon and get into how the cycle resolves itself. If there is a particular document proposal you are interested in, I urge you to follow it through the entire standards process. T is is especially important because even if you have no changes to send in others may have done so. It is also vital to review the First Draft Report (Report of Proposals for those documents that are still on the old format). Let's probe deeper and demystify this process. HAVING YOUR SAY IN THE PROCESS T e NFPA Standards Council will no longer accept a Notice of Intent to Make a Motion (NITMAM) if one has not submitted a Second Draft comment. T ere is one exception we will look at in a moment. Simply stated, one cannot wait for an association meeting to address a change in a document. T us, if in the First Draft Report an item has been changed from "red" to "green" and you feel that the item should still be "red," a Second Draft comment needs to be submitted for the corresponding Technical Committee's consideration. If they do not 26 / SECURITYSALES.COM / NOVEMBER 2013 accept "red," then you may fi le a NITMAM. T e exception noted above involves acceptance of a First Draft proposal. In this case, let's say it was you who submitted a change from "red" to "green." If the Technical Committee accepted this change, you would not need to submit a Second Draft commit. But if someone else did, or if the Technical Committee through its own actions changed "green" back to "red," then you could fi le a NITMAM. Part 1 of this subject also discussed Technical Committees (TCs), but did not cover Correlating Committees (formerly called Technical Correlating Committees). T eir purpose is to provide correlation between chapters of a large document WHO MAY SUBMIT A NOTICE OF INTENT TO MAKE A MOTION (NITMAM) The original submitter of a proposal or comment (note that the submitter must follow the process through if their proposal was not accepted during the First Draft Meeting). A member of the Technical Committee, if there was a change during the Second Draft Meeting. If there was a change during the First Draft Meeting the committee member would fi rst have to submit a Second Draft Comment. Anyone (if there was a change made during the Second Draft Meeting by the TC). PHOTOGRAPHY ©ISTOCKPHOTO.COM/ANDREYPOPOV, NSJ-IMAGES s s an nd scruti t ny by a

Articles in this issue

Links on this page

Archives of this issue

view archives of Security Sales & Integration - November 2012