Not only do states adopt specific versions, they often adopt just parts of specific versions. And unless they put specific language in the adoption law to allow newer or older sections, they are usually bound by what exactly was adopted.
On Jul 26, 2016 12:28 PM, "Joe Randolph" <j...@randolph-telecom.com> wrote: > Hi Pete: > > > > Here’s my experience with keeping track of upcoming changes in NFPA 70. > > > > For the last two years I have been following the development of the 2017 > edition of NFPA 70 because of some changes that it makes to Article 840, > “Premises Powered Broadband Equipment.” In order to see the current draft > of the 2017 edition and the committee comments, I had to join the NFPA for > $175, but it was worth it to me because the changes in Article 840 directly > affected a project I was working on. > > > > While joining the NFPA allowed me to view the current draft on my computer > screen, there was no way to download the document or even copy anything > more than what is on the screen. > > > > In summary, it **is** possible to see the draft version as it develops, > but it requires some effort. This may have changed recently because I > believe the final draft has been officially voted on and adopted. > > > > On a related note, I have found that when each state or jurisdiction > adopts NPFA 70 into their local laws, the legislation often specifies a > specific edition of NFPA 70. For example, as of last year when I was > looking at this, the state of Connecticut’s law still called out the 2005 > edition of NFPA 70. This seems problematic for dealing with changes in > the NEC over time. > > > > I’m not sure what happens when a revised requirement appears in an edition > of NFPA 70 that is newer than the edition called out by the laws of the > local jurisdiction. Two types of situation can occur: > > > > 1) The new requirement is MORE restrictive than the version in the > edition called out in the legislation > > 2) The new requirement is LESS restrictive than the version in the > edition called out in the legislation > > > > Does anyone in this group know how that works? My impression that the > specific individual doing the inspection (the AHJ) has wide latitude to > pick and choose from both editions, but this may be a mistaken impression. > It certainly would create a lot of uncertainly for a company that is trying > to deploy a single product throughout the USA. > > > > > > Joe Randolph > > Telecom Design Consultant > > Randolph Telecom, Inc. > > 781-721-2848 (USA) > > j...@randolph-telecom.com > > http://www.randolph-telecom.com > > > > *From:* Pete Perkins [mailto:00000061f3f32d0c-dmarc-requ...@ieee.org] > *Sent:* Tuesday, July 26, 2016 12:36 PM > *To:* EMC-PSTC@LISTSERV.IEEE.ORG > *Subject:* Re: [PSES] NEC 2017 > > > > Doug, et al, > > > > If you were really interested you would be involved in the > committee that revises the NEC every 3 years and have already read the > pertinent changes in which you are interested. > > > > All of these changes are done in an open forum and the > documents seem available; I don’t follow them, however. > > > > :>) br, Pete > > > > Peter E Perkins, PE > > Principal Product Safety & Regulatory Affairs Consultant > > PO Box 23427 > > Tigard, ORe 97281-3427 > > > > 503/452-1201 > > > > p.perk...@ieee.org > > > > *From:* Doug Powell [mailto:doug...@gmail.com <doug...@gmail.com>] > *Sent:* Friday, July 22, 2016 3:13 PM > *To:* EMC-PSTC@LISTSERV.IEEE.ORG > *Subject:* Re: [PSES] NEC 2017 > > > > Have we established that the 2017 edition actually has NRTL vs Listed? > > > > I would like to hear some clause references since it is nearly 600 pages. > > > > Thanks, Doug > > > > > > Douglas E Powell > > Colorado USA > > doug...@gmail.com > > http://www.linkedin.com/in/dougp01 > > > > On Fri, Jul 22, 2016 at 3:20 PM, Richard Nute <ri...@ieee.org> wrote: > > > > > > The NEC is a model standard and intended to be adopted by local and state > AHJs. In doing so, the AHJs often take exception to some requirements, and > add some requirements. In adopting the NEC, the AHJs must specify what > “listing” means – what third-party certifiers are acceptable to the local > or state AHJ. The NEC has not mentioned or specified by name a third-party > certifier. > > > > AHJs accept third-party certifications according to their local or state > rules. A specific NRTL certification may or may not be currently > acceptable. > > > > Now that the 2017 NEC specifies NRTL, it will be interesting to see how > the local and state AHJs accept specific NRTLs, or NRTLs by standards (as > does OSHA), or blanket all NRTLs. Note that AHJs have different objectives > than OSHA, who runs the NRTL program. > > > > > > Rich > > > > > > - > ---------------------------------------------------------------- > > This message is from the IEEE Product Safety Engineering Society emc-pstc > discussion list. To post a message to the list, send your e-mail to < > emc-p...@ieee.org> > > All emc-pstc postings are archived and searchable on the web at: > http://www.ieee-pses.org/emc-pstc.html > > Attachments are not permitted but the IEEE PSES Online Communities site at > http://product-compliance.oc.ieee.org/ can be used for graphics (in > well-used formats), large files, etc. > > Website: http://www.ieee-pses.org/ > Instructions: http://www.ieee-pses.org/list.html (including how to > unsubscribe) <http://www.ieee-pses.org/list.html> > List rules: http://www.ieee-pses.org/listrules.html > > For help, send mail to the list administrators: > Scott Douglas <sdoug...@ieee.org> > Mike Cantwell <mcantw...@ieee.org> > > For policy questions, send mail to: > Jim Bacher <j.bac...@ieee.org> > David Heald <dhe...@gmail.com> > > > > > > -- > > > > Douglas E Powell > > doug...@gmail.com > http://www.linkedin.com/in/dougp01 > > - > ---------------------------------------------------------------- > > This message is from the IEEE Product Safety Engineering Society emc-pstc > discussion list. To post a message to the list, send your e-mail to < > emc-p...@ieee.org> > > All emc-pstc postings are archived and searchable on the web at: > http://www.ieee-pses.org/emc-pstc.html > > Attachments are not permitted but the IEEE PSES Online Communities site at > http://product-compliance.oc.ieee.org/ can be used for graphics (in > well-used formats), large files, etc. > > Website: http://www.ieee-pses.org/ > Instructions: http://www.ieee-pses.org/list.html (including how to > unsubscribe) <http://www.ieee-pses.org/list.html> > List rules: http://www.ieee-pses.org/listrules.html > > For help, send mail to the list administrators: > Scott Douglas <sdoug...@ieee.org> > Mike Cantwell <mcantw...@ieee.org> > > For policy questions, send mail to: > Jim Bacher <j.bac...@ieee.org> > David Heald <dhe...@gmail.com> > > - > ---------------------------------------------------------------- > > This message is from the IEEE Product Safety Engineering Society emc-pstc > discussion list. To post a message to the list, send your e-mail to < > emc-p...@ieee.org> > > All emc-pstc postings are archived and searchable on the web at: > http://www.ieee-pses.org/emc-pstc.html > > Attachments are not permitted but the IEEE PSES Online Communities site at > http://product-compliance.oc.ieee.org/ can be used for graphics (in > well-used formats), large files, etc. > > Website: http://www.ieee-pses.org/ > Instructions: http://www.ieee-pses.org/list.html (including how to > unsubscribe) <http://www.ieee-pses.org/list.html> > List rules: http://www.ieee-pses.org/listrules.html > > For help, send mail to the list administrators: > Scott Douglas <sdoug...@ieee.org> > Mike Cantwell <mcantw...@ieee.org> > > For policy questions, send mail to: > Jim Bacher <j.bac...@ieee.org> > David Heald <dhe...@gmail.com> > - > ---------------------------------------------------------------- > > This message is from the IEEE Product Safety Engineering Society emc-pstc > discussion list. To post a message to the list, send your e-mail to < > emc-p...@ieee.org> > > All emc-pstc postings are archived and searchable on the web at: > http://www.ieee-pses.org/emc-pstc.html > > Attachments are not permitted but the IEEE PSES Online Communities site at > http://product-compliance.oc.ieee.org/ can be used for graphics (in > well-used formats), large files, etc. > > Website: http://www.ieee-pses.org/ > Instructions: http://www.ieee-pses.org/list.html (including how to > unsubscribe) <http://www.ieee-pses.org/list.html> > List rules: http://www.ieee-pses.org/listrules.html > > For help, send mail to the list administrators: > Scott Douglas <sdoug...@ieee.org> > Mike Cantwell <mcantw...@ieee.org> > > For policy questions, send mail to: > Jim Bacher <j.bac...@ieee.org> > David Heald <dhe...@gmail.com> > - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <emc-p...@ieee.org> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <sdoug...@ieee.org> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <dhe...@gmail.com>
