Code Changes and Adoptions
Code Changes and Adoptions
(OP)
This week I spent some time looking at when all the updated codes would be out and am a bit frustrated with the code cycles. Take Oregon for instance:
Oregon plans to release the 2014 OSSC around July 1st. This edition will be based on the 2012 IBC, ASCE 7-10, ACI 318-11, ACI 530-11, 2012 NDS, etc. etc. etc. Looking at those codes (besides the NDS), most are slated for a new version this year, or early next year. Why in the world are states so far behind the code cycle? What if there are some major code changes in the 2015 IBC that aren't picked up in the 2014 OSSC, I will be referencing way outdated codes in Oregon for the next 4 years...doesn't make a bit of sense to me!
Question, if I purchase the latest codes, am I bound to follow the codes specified in the Oregon Structural Specialty Code, or can I use the most current version of whatever code is referenced (concrete, wood, steel, masonry)?
Also, from reading in ACI's webiste, the new edition of the ACI 318 looks to be a huge improvement.
Oregon plans to release the 2014 OSSC around July 1st. This edition will be based on the 2012 IBC, ASCE 7-10, ACI 318-11, ACI 530-11, 2012 NDS, etc. etc. etc. Looking at those codes (besides the NDS), most are slated for a new version this year, or early next year. Why in the world are states so far behind the code cycle? What if there are some major code changes in the 2015 IBC that aren't picked up in the 2014 OSSC, I will be referencing way outdated codes in Oregon for the next 4 years...doesn't make a bit of sense to me!
Question, if I purchase the latest codes, am I bound to follow the codes specified in the Oregon Structural Specialty Code, or can I use the most current version of whatever code is referenced (concrete, wood, steel, masonry)?
Also, from reading in ACI's webiste, the new edition of the ACI 318 looks to be a huge improvement.






RE: Code Changes and Adoptions
In Chapter 35 of the IBC they list these references and their specific years. Those are the documents that you should follow under that particular adopted IBC code.
If there are newer releases of, say, ASCE 7, it is up to your own prudence as to whether you would also choose to use the later version. However, technically, you still would have to meet the older, referenced version as well.
RE: Code Changes and Adoptions
In Florida, we have a thoroughly screwed up code cycle. The 2013 Florida Building Code, which is based on the 2012 IBC, is not out yet. We are statutorily under the 2010 Florida Building Code with amendments.
In most jurisdictions, there is either an ordinance or statute that adopts a certain version of the code. In Florida, state law dictates the adoption date through the Florida Administrative Code, Rules for the Florida Building Commission, such as:
61G20-1.001 Florida Building Code Adopted.
(1) The Florida Building Code, 2010 Edition, as updated by the Florida Building Commission on – August 9, 2011, and amended by the Commission on August 7, 2012, incorporated herein by reference is hereby adopted as the building code for the State of Florida.
The interesting part of this is that the foregoing statement was not effective until August 2013!
Further, reference standards, as JAE noted, are usually made a part of the code by reference but are often included in their entirety as if contained within the code itself. Look at Chapter 1 of the IBC/FBC/Other States of similar style codes, to see the administrative provisions of the code (we usually skip that boring chapter!). Such provisions are actually important in that they dictate the use and applicability of the code. As an example, the Residential Code usually only applies to 1 and 2 family dwellings....so apartments and condos are not under the residential code, but the main building code as they are deemed to be "commercial construction", not residential construction.
Also, the standards referenced in the Code (ASCE 7 is a prime example) does not follow the same update cycle of the primary building code, so you are often using older versions of the standard as required by the code. Be careful with this because you want to stay within the standard of care of your practice and to move up or down in time with a referenced standard can take you outside the standard of care.
RE: Code Changes and Adoptions
RE: Code Changes and Adoptions
RE: Code Changes and Adoptions
RE: Code Changes and Adoptions
RE: Code Changes and Adoptions
As I mentioned above - it's OK to use the newer codes if they offer you a more conservative approach compared with the adopted code. But if the newer code gives you a less conservative result you are technically violating the mandated code requirements.
One example of this is that some years ago California hesitated in adopting the "newer" UBC 1997 as the local SE's there had issues with the seismic provisions that ICBO had come up with. If an engineer had used the UBC 97 on a project where the local authorities hadn't yet agreed to adopt it - and something "fell down" then that engineer would have a hard time defending their decision. Just because a newer code is newer, doesn't mean it is acceptable, agreeable, or appropriate for every jurisdiction anywhere.
RE: Code Changes and Adoptions
Maine EIT, Civil/Structural.
RE: Code Changes and Adoptions
RE: Code Changes and Adoptions
Codes are minimum standards.