<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Our Building Codes Are Broken</title>
	<atom:link href="http://www.constructioncalc.com/blog/structural-design/our-building-codes-are-broken/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.constructioncalc.com/blog/structural-design/our-building-codes-are-broken/</link>
	<description>We Empower the Building Industry</description>
	<lastBuildDate>Tue, 08 Nov 2011 17:00:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Rick V</title>
		<link>http://www.constructioncalc.com/blog/structural-design/our-building-codes-are-broken/comment-page-1/#comment-19</link>
		<dc:creator>Rick V</dc:creator>
		<pubDate>Wed, 03 Mar 2010 18:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.constructioncalc.com/blog/?p=487#comment-19</guid>
		<description>Mr. Garrison,

I appreciated this article and the comments.

As a practicing PE, you are clearly focused on actual solutions and getting from point A to point B. Unfortunately, that is not the case with the regulatory entities.

As a building designer, I not only deal with the IBC and IRC, but also state (Oregon) adjustments to the IBC and IRC (they call them &quot;blended codes&quot; whatever that means), the NFPA (they are willing to accept me as a member for only $150 per year and promise to help me navigate their codes... what a great deal), local codes and last, but not least, local land use ordinances for the various jurisdictions in which I work. Each of these entities is constantly busy churning out new regulations in order to keep us safer, better, or whatever.

As a small child playing with blocks, one of the first things I learned was - don&#039;t put a lot of weight up high. It seems that things can become somewhat unstable. Unfortunately, we have yet to learn that as a society. As regulations and regulators multiply, navigation (successful application of the regulations) becomes increasingly difficult. The people at the top, the regulators, are able to exist and thrive in a myopic world, focused on their particular set of rules or concerns. Unfortunately, most of them do not get to experience the broader spectrum of attempting to navigate the entire system. There is simply no motive for them to consider the larger regulatory picture.

I&#039;m not saying anybody is bad, the regulators are simply doing what most lifeforms do, exist and thrive in their environment.

I do not hate the codes, but I think it is important to understand the actual reasons they have grown from a useful tool, into a monster. All one has to do is follow the money. The code industry has grown into a huge self-perpetuating business, one rationalization at a time. I think the theory is, don&#039;t mind the big picture, it&#039;ll take care of itself. I would agree. I believe we call it natural selection.

We do have some code competition between the ICC and NFPA, but that doesn&#039;t seem to help... maybe they&#039;ve worked something out, I don&#039;t know. What I do know, after over 40 years in this industry (the first 20 with a hammer), is that we are quickly reaching a point where the complexity of the regulatory system will override the larger concern, which is quality of the structure.

I would like to see us start over with a clear destination (other than perpetual employment) in mind. I would like to see a component of that destination be a clear navigable code where components actually relate to one another and work together (like a building). It should be a tool rather than a burden.

Thanks for letting me rant,
Rick</description>
		<content:encoded><![CDATA[<p>Mr. Garrison,</p>
<p>I appreciated this article and the comments.</p>
<p>As a practicing PE, you are clearly focused on actual solutions and getting from point A to point B. Unfortunately, that is not the case with the regulatory entities.</p>
<p>As a building designer, I not only deal with the IBC and IRC, but also state (Oregon) adjustments to the IBC and IRC (they call them &#8220;blended codes&#8221; whatever that means), the NFPA (they are willing to accept me as a member for only $150 per year and promise to help me navigate their codes&#8230; what a great deal), local codes and last, but not least, local land use ordinances for the various jurisdictions in which I work. Each of these entities is constantly busy churning out new regulations in order to keep us safer, better, or whatever.</p>
<p>As a small child playing with blocks, one of the first things I learned was &#8211; don&#8217;t put a lot of weight up high. It seems that things can become somewhat unstable. Unfortunately, we have yet to learn that as a society. As regulations and regulators multiply, navigation (successful application of the regulations) becomes increasingly difficult. The people at the top, the regulators, are able to exist and thrive in a myopic world, focused on their particular set of rules or concerns. Unfortunately, most of them do not get to experience the broader spectrum of attempting to navigate the entire system. There is simply no motive for them to consider the larger regulatory picture.</p>
<p>I&#8217;m not saying anybody is bad, the regulators are simply doing what most lifeforms do, exist and thrive in their environment.</p>
<p>I do not hate the codes, but I think it is important to understand the actual reasons they have grown from a useful tool, into a monster. All one has to do is follow the money. The code industry has grown into a huge self-perpetuating business, one rationalization at a time. I think the theory is, don&#8217;t mind the big picture, it&#8217;ll take care of itself. I would agree. I believe we call it natural selection.</p>
<p>We do have some code competition between the ICC and NFPA, but that doesn&#8217;t seem to help&#8230; maybe they&#8217;ve worked something out, I don&#8217;t know. What I do know, after over 40 years in this industry (the first 20 with a hammer), is that we are quickly reaching a point where the complexity of the regulatory system will override the larger concern, which is quality of the structure.</p>
<p>I would like to see us start over with a clear destination (other than perpetual employment) in mind. I would like to see a component of that destination be a clear navigable code where components actually relate to one another and work together (like a building). It should be a tool rather than a burden.</p>
<p>Thanks for letting me rant,<br />
Rick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markg</title>
		<link>http://www.constructioncalc.com/blog/structural-design/our-building-codes-are-broken/comment-page-1/#comment-4</link>
		<dc:creator>markg</dc:creator>
		<pubDate>Fri, 05 Jun 2009 16:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.constructioncalc.com/blog/?p=487#comment-4</guid>
		<description>Mulch,

Your piece on &quot;Broken Building Codes&quot; is shear (Sic) genius!

I don&#039;t have the time (translation: economic woes) to research such a writing, but if I could, I would.

Your writing hits the nail on the head and countersinks it.  As a competent engineering and building contractor building to code daily, I see first hand the discrepancy in current code continuously.  To try to keep up with them is ludicrous.  What I have chosen to do is keep up with a smaller section of the code, and be competent at it: concrete and structures.  That in itself is a menagerie of confusion, and I find few who have close to real competency in them - thus, I make a living.  

In our world, the building department and reality are our two checkpoints.  The first, are usually a group of well meaning government employees who cannot possibly keep up the the myriad of changes, and vast knowledge required to know all code, so they rely on either outside plan check companies (that cash in on the amount of minutiae in the building code, so they can charge hourly to review and make comments on drawings), or two, the same format of review with a few exceptions from the previous 20 years or so.  The second is less cunning, and more direct - mother nature herself.  That&#039;s where the rubber meets the road.  We don&#039;t get call backs on previous work for code violations, but we do get call backs on water leaks, wind damage, and my favorite topic &quot;doughnut construction modifications&quot;.  The first category usually are related to poor existing materials, ie bad substrate, corroded or weak surfaces to apply membranes, sealers and hardware to etc.  The second is the weekend warrior that invites his buddies over to help him &quot;remodel&quot;, and pays them in Schlitz Malt Liquor, or worse yet, the low bidder, who does slipshod work, blames the previous company, charges extensively and splits the scene never to be seen again.  The honest tax paying contractor that did work two years ago, and still has his phone number, is the obvious candidate for blame for repair.

The overhaul you recommend will be instantaneously fixed, by having the ICC code folks attempt to competitively design a structure or two, and realize that it (Code) needs &quot;mayor suryery&quot;.  Then develop a team consisting of the aforementioned groups of active design professionals, builders and architects, and offer them a royalty based on a percentage of their volumes and copies downloaded or purchased, and liable for any failures inherent in their design criteria.

At any rate, it&#039;s refreshing reading your well thought out information, but the likely hood of getting any change without championing a campaign is nil.  However, I will be the first in line to be a staunch supporter and leader in the effort!

If you don&#039;t mind, I think I&#039;ll retire, and pull down a Schlitz myself.

Reg

Mark Garrison MG Constructors &amp; Engineers Inc. 15650 Vineyard Blvd. , Suite A, #232 Morgan Hill , CA 95037 (408)842-5599 Office (408)590-7737 Cell (888)234-8057 Fax</description>
		<content:encoded><![CDATA[<p>Mulch,</p>
<p>Your piece on &#8220;Broken Building Codes&#8221; is shear (Sic) genius!</p>
<p>I don&#8217;t have the time (translation: economic woes) to research such a writing, but if I could, I would.</p>
<p>Your writing hits the nail on the head and countersinks it.  As a competent engineering and building contractor building to code daily, I see first hand the discrepancy in current code continuously.  To try to keep up with them is ludicrous.  What I have chosen to do is keep up with a smaller section of the code, and be competent at it: concrete and structures.  That in itself is a menagerie of confusion, and I find few who have close to real competency in them &#8211; thus, I make a living.  </p>
<p>In our world, the building department and reality are our two checkpoints.  The first, are usually a group of well meaning government employees who cannot possibly keep up the the myriad of changes, and vast knowledge required to know all code, so they rely on either outside plan check companies (that cash in on the amount of minutiae in the building code, so they can charge hourly to review and make comments on drawings), or two, the same format of review with a few exceptions from the previous 20 years or so.  The second is less cunning, and more direct &#8211; mother nature herself.  That&#8217;s where the rubber meets the road.  We don&#8217;t get call backs on previous work for code violations, but we do get call backs on water leaks, wind damage, and my favorite topic &#8220;doughnut construction modifications&#8221;.  The first category usually are related to poor existing materials, ie bad substrate, corroded or weak surfaces to apply membranes, sealers and hardware to etc.  The second is the weekend warrior that invites his buddies over to help him &#8220;remodel&#8221;, and pays them in Schlitz Malt Liquor, or worse yet, the low bidder, who does slipshod work, blames the previous company, charges extensively and splits the scene never to be seen again.  The honest tax paying contractor that did work two years ago, and still has his phone number, is the obvious candidate for blame for repair.</p>
<p>The overhaul you recommend will be instantaneously fixed, by having the ICC code folks attempt to competitively design a structure or two, and realize that it (Code) needs &#8220;mayor suryery&#8221;.  Then develop a team consisting of the aforementioned groups of active design professionals, builders and architects, and offer them a royalty based on a percentage of their volumes and copies downloaded or purchased, and liable for any failures inherent in their design criteria.</p>
<p>At any rate, it&#8217;s refreshing reading your well thought out information, but the likely hood of getting any change without championing a campaign is nil.  However, I will be the first in line to be a staunch supporter and leader in the effort!</p>
<p>If you don&#8217;t mind, I think I&#8217;ll retire, and pull down a Schlitz myself.</p>
<p>Reg</p>
<p>Mark Garrison MG Constructors &amp; Engineers Inc. 15650 Vineyard Blvd. , Suite A, #232 Morgan Hill , CA 95037 (408)842-5599 Office (408)590-7737 Cell (888)234-8057 Fax</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sdaggers@iccsafe.org</title>
		<link>http://www.constructioncalc.com/blog/structural-design/our-building-codes-are-broken/comment-page-1/#comment-3</link>
		<dc:creator>sdaggers@iccsafe.org</dc:creator>
		<pubDate>Thu, 04 Jun 2009 22:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.constructioncalc.com/blog/?p=487#comment-3</guid>
		<description>If our building codes are broken as you suggest, and we strongly disagree with that assumption, you can be part of the solution by participating in the code development process. In that arena, you can object to what you see as an “agglomeration of gobbledygook,” propose changes to clarify, and discuss your issues with professional colleagues and peers. Code content is the result of input from code officials, architects, engineers, designers and many others from inside and outside of the construction industry.

As you may know, the International Code Council uses the governmental consensus process to develop its building safety and fire prevention codes. It is an open, inclusive process that allows input from all individuals and groups. Committees hear all code change proposals. Final decisions are made by International Code Council voting members—code enforcement and fire officials who, with no vested interests beyond public safety, represent the public’s best interest. An appeals process allows anyone to appeal an action or inaction relating to a code change.

For more information about the Council’s Code Development Process and how you can be a part of it, visit  www.iccsafe.org/cs/codes.

Steve Daggers
VP Communications
International Code Council</description>
		<content:encoded><![CDATA[<p>If our building codes are broken as you suggest, and we strongly disagree with that assumption, you can be part of the solution by participating in the code development process. In that arena, you can object to what you see as an “agglomeration of gobbledygook,” propose changes to clarify, and discuss your issues with professional colleagues and peers. Code content is the result of input from code officials, architects, engineers, designers and many others from inside and outside of the construction industry.</p>
<p>As you may know, the International Code Council uses the governmental consensus process to develop its building safety and fire prevention codes. It is an open, inclusive process that allows input from all individuals and groups. Committees hear all code change proposals. Final decisions are made by International Code Council voting members—code enforcement and fire officials who, with no vested interests beyond public safety, represent the public’s best interest. An appeals process allows anyone to appeal an action or inaction relating to a code change.</p>
<p>For more information about the Council’s Code Development Process and how you can be a part of it, visit  <a href="http://www.iccsafe.org/cs/codes" rel="nofollow">http://www.iccsafe.org/cs/codes</a>.</p>
<p>Steve Daggers<br />
VP Communications<br />
International Code Council</p>
]]></content:encoded>
	</item>
</channel>
</rss>

