the word Code

[mshields]

Can anybody tell me why NFPA 99 went to the trouble of changing their name such that it was identified as a code and no longer a standard. The change took place with the 2012 edition. It strikes me as meaningless; As I understand it, a Standard only becomes a code when a state adopts it either in part or in its entirety. By that reasoning, while we're on the subject, The National Electrical Code isn't even a code.

Is there a guideline that the NFPA goes by in determining which document is a standard and which is a code or is this a case of individual code boards deciding they want to be taken more seriously by changing the name of the document for which they have responsibility from Standard to Code. Does it mean anything or is it mere semantics?

 

[jumper]

This kinda explains it, but the difference can be vague IMO.

http://www.nfpa.org/news-and-resear...de-to-fire-and-nfpa/about-codes-and-standards

 

[JFletcher]

After reading that, Im still lost. How many states have adopted the 2014 NEC in entirety, w/o amendment? I wanna say like 34 use it, tho Ive no idea how many have their own subset of rules that override, rewrite, or impose harsher limits. Didnt MN throw a big middle finger to AFCI? I think MA has its own code amendments (I believe iwire has posted some of them). PA is on the 2008 NEC. Here, we're on the 2012 IRC (with amendments) and 2011 NEC. What is CODE to many (mainly AFCI in 120V residential) is a good way to go broke here, where they are only required on bedroom receps (VA is basically on the 2002 NEC when it comes to AFCI).

It's actually pretty amazing that not every answer on this forum is "check with your AHJ" since CODE varies so much from place to place.

Istm that implemented standards can be stricter than code. If any of you have done a chapter 7/8 install to TDMM standards taken as code/job spec, you know what I mean.

 

[mshields]

agree - that it's vague

agree - that it's vague

By the authors definition, The National Electrical Code is a standard; i.e. it's pretty "nut and bolty" if you ask me.

He seems to be saying that a Code gives you Performance where as a standard gives you Installation. But of course, we talk about Performance vs Installation codes all the time? Or are we talking about standards

Sounds like this is the best we're going to do.

I was particularly interested relevant to the NFPA 99 change (from a standard to a code). I know that there is some serious head knocking between the NEC code committee's and the NFPA 99 committee's. I wonder if NFPA 99 simply wanted the same amount of respect. I know a guy on the committee who has assured me that NFPA 99 prevails over the NEC in hospitals. I don't think so. True, for DPH certification you need to meet NFPA 99. But if the NEC requirement is more stringent, I think you're operating at your own peril with the AHJ not follow it unless you can show a clear path to how your state fire or building code references that specific requirement from NFPA 99.

 

[kwired]

After reading that, Im still lost. How many states have adopted the 2014 NEC in entirety, w/o amendment? I wanna say like 34 use it, tho Ive no idea how many have their own subset of rules that override, rewrite, or impose harsher limits. Didnt MN throw a big middle finger to AFCI? I think MA has its own code amendments (I believe iwire has posted some of them). PA is on the 2008 NEC. Here, we're on the 2012 IRC (with amendments) and 2011 NEC. What is CODE to many (mainly AFCI in 120V residential) is a good way to go broke here, where they are only required on bedroom receps (VA is basically on the 2002 NEC when it comes to AFCI).

It's actually pretty amazing that not every answer on this forum is "check with your AHJ" since CODE varies so much from place to place.

Istm that implemented standards can be stricter than code. If any of you have done a chapter 7/8 install to TDMM standards taken as code/job spec, you know what I mean.

I think it was Michigan that gave AFCI the middle finger not Minnesota.


Doesn't most of NFPA publications have "code" in the title? Maybe this was one of a few that didn't, and NFPA wants it to be a "code".

 

[david luchini]

I think it was Michigan that gave AFCI the middle finger not Minnesota.


Doesn't most of NFPA publications have "code" in the title? Maybe this was one of a few that didn't, and NFPA wants it to be a "code".

Relatively few NFPA publications have "Code" in the title. Only 36 of approx 370 publications, I think.