Why the slow adoption of NFPA 72?

[jmbelectrical]

Upon receiving an RFI from a contractor regarding Class A, Style 7 wiring requirements for a particular fire protection device, I researched NFPA 72 (2013 edition) and discovered that, much to my surprise, circuit styles have been completely eliminated. Fire alarm circuits are now defined by class only. For example, what was Class A, Style 6 is now simply Class A. What was Class A, Style 7 is now Class X. I immediately jumped to the conclusion that we needed to update our fire alarm specifications to reflect this change. Another engineer in my office was quick to point out that our state is still under NFPA 72, 2007 edition. In fact, only a very small number of states and cities have adopted the 2010 edition or newer.

Is this typical in the United States or does NFPA 72, 2010 edition, introduce some other, significant, new changes that states are just hesitant to enforce?

 

[cdafd]

States are slow

I know mine is, I think they are looking at the 2013 this year

Which is currently under 2007

 

[stookeyfpe]

Adoptions take time. It has to go through the legislative process and inevitably, a unique or special interest will want something more restrictive or want to eliminate a requirement (because it costs them money). Then the jurisdiction must justify why the provision should or should not be added.

Once the new standard becomes adopted, staff hopefully attends some formal training and that's when the fun begins because I reject your plan because you submitted it to the 2013 edition of NFPA 72. I reject your plan because you din't know about a new requirement, or you don't agree with my interpretation. So then we have more telephone calls and meetings and being reasonable engineers, hopefully resolve the problem in a timely manner that meets the requirement or our collective interpretation.

Or my favorite is you and I both contact a a committee expert who tells us we're both wrong, and the intent of Section x.x.xxx.x is. We both look at each other and simultaneously state "that may be your intent but it damn sure doesn't match the code text in the standard."

From the time we make the business decision in my jurisdiction to adopt new codes and standards until its effective date of enforcement can take 9 to 12 months. In every adoption process we meet with the Building and Fire Code Board of Appeals (2 to 4 times), Planning Commission in some cases, and the Environmental Board because they are concerned about hazardous materials. All of these meetings are subject to Open Meetings laws which require (you guessed it) time to schedule, post notice, and find a venue. Finally, City Council typically has one to two readings because the special interest folks show up and announce they were not invited to the process.

That's my experience on why adoptions take time.