Code Adoption Progress in the South

Status
Not open for further replies.

peter d

Senior Member
Location
New England
I disagree, thats not the worst. He is on a CMP...

I was not aware of that. That is much worse then, and certainly no CMP member should be guilty of such outrageous conduct. It's highly unprofessional and as I said before, makes me all the more distrusting of manufacturers.
 

mbrooke

Batteries Included
Location
United States
Occupation
Technician
I was not aware of that. That is much worse then, and certainly no CMP member should be guilty of such outrageous conduct. It's highly unprofessional and as I said before, makes me all the more distrusting of manufacturers.

My issue is that anyone who does not agree with them is automatically an "idiot". Condemnation without investigation is the highest form of ignorance. So of course these people will reject electrical theory or anyone who disagrees with what they were told in the first place. The perfect psychological profile needed in order for people to push products into the code because nothing is their to restrain them in the first place.


As Ive said before: the vagaries of fate made the common man an authority himself, or in this case the average electrician a CMP member himself...
 

peter d

Senior Member
Location
New England
My issue is that anyone who does not agree with them is automatically an "idiot". Condemnation without investigation is the highest form of ignorance. So of course these people will reject electrical theory or anyone who disagrees with what they were told in the first place. The perfect psychological profile needed in order for people to push products into the code because nothing is their to restrain them in the first place.


As Ive said before: the vagaries of fate made the common man an authority himself, or in this case the average electrician a CMP member himself...

MasterTheNEC aka Paul is the epitome of ignorance.
 

bphgravity

Senior Member
Location
Florida
Florida code change proposals to the 2014 NEC / 2015 I-Codes are now available for review and comment. The deadline for making comment on the code change proposals is February 25, 2016 (the end of the first 45 day comment period).

There are (15) proposals that may be of interest to you:

1. Mod #6770 Sec 908.7 IBC relocates an AHCA exception for CO alarms to a more appropriate location
2. Mod #6782 Sec C405.6.3 IECC removes the requirement for 2% VD on feeders and 3% VD on branch circuit and adds a general requirement for 5% maximum VD
3. Mod #7078 Sec E3902.16 IRC deletes the expansion of AFCI protection to kitchens and laundry areas
4. Mod #6460 Sec 2703 IBC expands the requirements for lightning protection systems and surge protection devices in commercial occupancies
5. Mod #6458 Chapter 35 IBC updates the NFPA 780 reference to the current edition
6. Mod #6452 Sec 454.1.4.2.3 IBC restores the requirements for underwater luminaires in swimming pools to that as permitted in the 2014 NEC
7. Mod #6529 Sec 302.6 IEBC adds GFCI & bonding requirements to existing swimming pools
8. Mod #6530 Sec R4501.16 IRC adds GFCI requirements to new residential (private) swimming pools
9. Mod #6531 Sec 454.1.4.1 / 2.16 IBC adds GFCI requirement to new commercial (private and public) swimming pools
10. Mod #6498 Sec 110.9 IBC adds GFCI and bonding inspection requirements to existing swimming pools
11. Mod #6491 Sec E4203.1.3 IBC adds GFCI requirements to residential swimming pools
12. Mod #6492 Sec 680.21(C) NEC adds GFCI requirements to swimming pool branch circuits
13. Mod #6493 Sec 413.1 IEBC adds GFCI & bonding requirements to existing swimming pools
14. Mod #6494 Sec 709.1 IEBC adds GFCI & bonding requirement to existing swimming pools
15. Mod #6496 Sec 454.1.10.4 IBC adds GFCI requirements to commercial swimming pools

To review the proposed code changes or submit comment on a proposed code change, please visit the link below and then follow the following instructions:
http://www.floridabuilding.org/cm/cm_default.aspx

Submitting a comment on a Mod. One can submit either a general comment or an alternate language to the proposed code modification:

General comments are for any comment that doesn’t include alternate language. This section is a Text box for users to either cut and paste into or type live.
If you find a mod that you feel would be improved if it had different language you can submit an alternate language comment. Once you click on “submit a Comment on a Code Modification” select the Alternate language radio button. You will be taken to a search screen. Search for the Mod you wish to comment on and scroll to the bottom and click on “Submit Comment”. Here add the text of the Modification as the text of the Comment.

Searching for Mods: If you happen to not know the mod number you can search by other parameters. You can select the criteria by which you wish to search for mods. You can start as low as the mod number or go broader to search by TAC or search the widest by the 2017 code. In most cases selection is done by a group i.e. by TAC, by section of the code, proponent etc. These can greatly narrow down your results to just a few mods. If your search returns no results, remove some of your selected variables until you get the desired results.

1. From the homepage log in and then go to “Proposed Code Modifications”
2. Click on “Find a Proposed Code Modification”
3. Select the criteria by which you wish to select, in this case we will do by TAC, so select TAC > Code Administration from the dropdown.
4. Then click search
5. Once you have found the mod you want to comment on you can click on that mod and at the bottom of the mod page select “Submit Comment” make a note of the number and from the homepage select Proposed Code Modifications > Submit Comment On Proposed Code Modification
6. On the next screen should display a selection screen to whether you want an alternate language comment or just a general comment.
 

bphgravity

Senior Member
Location
Florida
The Virginia Department of Housing and Community Development has begun the triennial code update process with the issuance of a Notice of Intended Regulatory Action to be published in the Virginia Register next month. Please see an outline of the process below and an initial schedule for code review workgroups to begin meeting in March.

1. A Notice of Intended Regulatory Action (NOIRA) is the first step in the regulatory update process. When published in the Virginia Register, a 30 day period is established for the submittal of comments concerning the Board of Housing and Community Development’s intent to update the building and fire codes. Approval for publishing the NOIRA has to be obtained through the Executive Branch of the state government (the Department of Planning and Budget, the Secretary of Commerce and Trade and the Governor’s Office). The NOIRAs are published in the Virginia Register. The Virginia Register is a publication of the Virginia Code Commission used as a clearinghouse for viewing changes to any state agency’s regulations. The Virginia Register may be viewed at http://legis.state.va.us/codecomm/register/REGINDEX.HTM.

2. The next step in the code change process is the formulation and publishing of proposed regulations. The Board of Housing and Community Development approves proposed regulations for the Uniform Statewide Building Code (USBC), Statewide Fire Prevention Code (SFPC), Virginia Certification Standards (VCS), Virginia Manufactured Home Safety Regulations (MHSR) and the Virginia Amusement Device Regulations (VADR). Those proposed regulations are considered for approval through the Executive Branch agencies and are published in the Virginia Register once authorized.

3. Once the proposed regulations are published, a 60-day public comment period for the submittal of any code change proposals to change the proposed regulations will be observed. The Virginia Department of Housing and Community Development (DHCD) accept code change proposals which have been submitted by various work groups and committees and by individuals or organizations. The last day for the acceptance of code change proposals is, based on when the proposed regulations are published. If the deadline changes, it will be announced on this Web page. Any proposals received after the deadline will be held over for the next code change process.

4. During the 60-day comment period, the Board of Housing and Community Development is will also conduct a public hearing to permit oral comment to accompany the submittal of code change proposals. The time and location of the hearing will be contained in the notice of public hearing found in the Virginia Register with the proposed regulations.

5. After the 60-day comment period ends and the public hearing has been held, DHCD staff will compile public comment and code change proposals. A staff evaluation will be done for each proposal and then a compilation document will be developed. This compilation document will contain all the code change proposals, testimony of the public hearing and the staff evaluations.

6. Once the compilation document is available, a second comment period will be established. This comment period provides the opportunity for all interested parties to review all proposals submitted and to review the staff evaluations for all proposals. The Board will accept comments during this period on any proposals and on the staff evaluations. In other words, if you or your group wishes to argue against a proposal, you may submit comments requesting the Board to reject the proposal providing any necessary substantiation. If you or your group disagrees with a staff evaluation, then you may submit comments to that effect. You may also submit comment supporting a particular proposal.

7. At the end of the second comment period, all comments will be compiled and the Board will consider each proposal. Once the Board’s decisions are made, staff will prepare the final regulations for submittal through the Executive Branch agencies and for final publication in the Virginia Register.
 

Attachments

  • Tentative workgroup dates - stakeholder memo.pdf
    108.8 KB · Views: 0

bphgravity

Senior Member
Location
Florida
Final Post

Final Post

For those with continued interest in receiving updates to state and local code adoption activity, please consider subscribing to NEMA's Code Alerts. It's easy and it's free. Go Here: http://www.nema.org/Technical/Code-Alerts/Pages/default.aspx

You can also view a map of NEC adoption status in all 50 states or download a detailed NEC adoption spreadsheet that is updated regularly. An updated map & spreadsheet will be posted February 1st. Go Here: http://www.nema.org/Technical/FieldReps/Pages/National-Electrical-Code.aspx

Additional information on NEC adoption activity is available from the Electrical Code Coalition. The mission of the Electrical Code Coalition is to increase focus and emphasis on electrical safety for persons and property through direct and full adoption, application and uniform enforcement of the latest edition of the NEC as the standard for safe electrical installations. Go Here: http://www.electricalcodecoalition.org/

Keep in touch:

Follow NEMA on Twitter @NEMAupdates
Follow me on Twitter @HollandNEMA
Follow ESFI on Twitter @ESFIdotorg

Follow NEMA on Facebook: https://www.facebook.com/pages/National-Electrical-Manufacturers-Association/132533056815384
Follow the NEMA Field Reps on Facebook: https://www.facebook.com/National-E...ssociation-Field-Reps-908459845836945/?ref=hl
Follow ESFI on Facebook: https://www.facebook.com/ESFI.org
 
Status
Not open for further replies.
Top