Code Changes

The Big Vote, RB 64

by Michael O'Brian on September 21, 2008

Today the International Code Council continued to vote on proposals at the Final Action Hearings which will affect the 2009 series of Building Codes.  The hearings started on Wednesday and continue through Monday.  The series of votes which revolve around the installation of residential sprinklers drew the largest forum of governmental members the ICC has ever seen in its history.  Here is the voting as it happens.  You can view the web-cast here as well

{ 10 comments }

Code Changes Make it Big

by Michael O'Brian on September 16, 2008

The Final Action Hearings for the International Code Council begin on Wednesday September 17, 2008 in Minneapolis Minnesota.  There are hundreds of code changes up for debate and approval by the governmental members.  The interesting part is that the process has made the front page of many newspapers including the New York Times.

The New York Times is questioning why government agencies (GSA specifically) are questioning code changes that are based on the investigative findings born after the 9/11 tragedies.  These changes are not making airplane resistant buildings, but making the super tall buildings safer for occupants to egress during an emergency.

So why are code changes now making the buzz on covers of the New York Times and why is Hillary Clinton commenting on the ICC Changes as well?

I would like to hope that the code changes are become more important to our [click to continue…]

{ 4 comments }

Time for Proper Nourishment and Digestion

by Michael O'Brian on February 23, 2008

codes forumThe 2008 ICC Codes Forum is rocking and rolling in Sunny (and somewhat raining) Palm Springs California.  The codes forum is being cast via the web to provide access to anyone via the world wide web.  If you have been on site or viewed during the web you have some some unique things happen over the first six days.  There has been great code changes and some questionable ones.  If you are new to code development here’s how it works:

A code change is submitted to the ICC to add, delete, change, or modify the current code.  The code changes are listed in several manuals based on the document it will modify.  The changes area heard via the appropriate committee based on the posted schedule.  During the even two hearings are occurring at any given time. 

 If you tune into the hearings via the web-castyou can see several things occurring.  First the proponent of the code change will testify based on the proposed changes.  Others in support of the change will follow.  Then those against will do the same.  After a chance for rerebuttile, the committee will debate the change and recommend its final destination (approved, disapproved, or as-modified).  The last action is if any member of the ICC wishes for a floor vote.  At the codes forum anyone can vote that is an ICC member.  The process is different at the final action hearings (we will provide details in the future). 

The ICC process has been under much debate since over 2500 code changes were submitted.  The process is up to 2 weeks as currently posted.  With the amount of code change and discussion, the hearings have consistently ran long.  I know that the ICC board is looking for ways to optimize the code development process and streamline some of its process.  Regardless of what is happening, being a part of the process (live or via the web-cast) is a great way to understand the “intent” behind the code. 

We have serveral links to some the hotter code changes in our discussion forum.  Share your viewpoints for those who may vote in September.  What can the ICC do to make the code hearings more effective and accessible to its membership? 

{ 3 comments }

2008 ICC Code Forum, How Can I be Involved

by Michael O'Brian on February 18, 2008

The 2008 International Code Council (ICC) code forum runs from February 18, 2008 through March 1, 2008.  The ICC has published a schedule of the various hearings.  The hearings are broken down into two tracks which run simultaneously.  The ICC provides a great service where you can watch the hearings live from your computer (equipped with an Internet connection). 

 The committee hearings are based on the proposed 2007/2008 code changes.   The changes are broken down based on the proposed code the change will affect.  Some of the codes have dual impact and may be found in one section in lieu of the proposed code.  The hearings that are broadcast include many items.  You will notice a moderator who runs each code change.  The proposed change is assigned a number (letter abbreviation and number) which is then put for comment on the floor.  Any member of the ICC can voice their comments to the committee.  Once the comments are completed the moderator turns the change over to the code committee.

 The code committee will then debate the issue and provide a vote.  After the vote is complete the moderator will ask if the floor has any motions.  The ICC members can ask for a floor vote.  The floor vote does not have impact on the code change although it is reflected on the final action hearings (will take place in September 2008). 

So why should you (the inspector) attend or tune into the event?  This is a great chance to learn the “intent” behind the code.  It provides technical justification when you look towards enforcing the future code.  The process can seem overwhelming at first blush, just review the schedule and tune intothe code that you have a passion for.  If you have time follow along in the proposed changes and watch the fun!    

{ 0 comments }

What’s it Going to Take

by Michael O'Brian on January 17, 2008

Special Blog post by:

Azarang (Ozzie) Mirkhah, P.E., EFO, CBO

On December 4, 2006, International Association of Fire Chiefs (IAFC) issued a “Member Alert” notifying their membership about the hazards associated with the light-weight construction in residential occupancies. In that Member Alert titled “Caution Urged with Composite Floors” it was stated:

There have been several cases of firefighters falling through floors made of composite structural components and an even greater number of near-miss situations. This type of construction is being investigated as a contributing factor in a line-of-duty death. There is a proliferation of engineered floor systems in residential occupancies across the United States. Many newer residential occupancies incorporate lightweight, engineered wood or composite structural components, including trusses, wooden I-beams and lightweight flooring systems. In most cases, these systems are structurally sound and designed to support the appropriate loads under normal conditions; however, they are likely to fail very quickly under fire conditions.

These components and systems are most often found in situations where applicable codes do not require any rated fire resistance between floor levels. They have much less inherent fire resistance than conventional wood joist floor systems and conventional wood decking. Remember – many codes do not require any fire resistance in residential floors! In the several cases of firefighters falling through floors, those floors had been exposed to fire from below for relatively short periods.

Then, on October 1, 2007, [click to continue…]

{ 7 comments }

Does the Building Official Get Up at 2am

by Michael O'Brian on January 10, 2008

Those that participate in the ICC’s code hearings may have noticed subtle changes in the past few years. Changes that have fire officials in the building code committees and vice versa. I see great cooperation between the two in the national code arena. However, locally we still see the division between the two. In the world of building and fire officials, there has been a long silence between the two parties. Or shall I say, turf battle, to clear this up. Building officials will say this is mine and fire will say no that is ours, whether it is fire alarms, fire sprinklers, dampers, etc. These latter items are both in the building and fire code, so why the battle? Why can’t both departments put forth a joint effort to benefit the community? Worst of all, contractors are stuck in the middle while the turf wars are settled. To answer the quote above, cooperation between the two isn’t being said or preached enough.

I’ve been in the building official and plan examiner business since 1995. By far, I’m no expert, but I’ve made mistakes and fortunately have learned from them to make relationships between departments and contractors work for me. I’ve worked in jurisdictions where no fire marshal was present and in others that the fire marshal played a major role in new and existing buildings. In areas that a fire marshal wasn’t present, I was constantly consulted in the Fire Code by local fire chiefs and asked for an opinion whether it was outdoor storage, setbacks to LPG tanks, FDC locations, etc. We worked well with our local fire departments and lend them our code knowledge.

Most people outside the code business find code books confusing and intimidating, and my experience with the local fire departments were the same, and they were glad for us looking into the issues and relaying the code language back to them in “English”.

We operated on the philosophy that we could sleep through the night, didn’t have to get up at 2:00 am in the middle of winter to put a fire out. Later on, I was with a building department in a city that had a full time fire marshal and two fire inspectors. Not only were they grateful for a building official that shared plans for them to review, they were taken back on my knowledge in the fire code and the building code. Both parties learned so much from each other. While I learned more into the fire service, i.e.: how engines and ladder trucks approach a fire, standard operation procedures, the effectiveness of different nozzles, sprinkler operations, etc, they learned building construction from the ground up, formal plan review procedures, and where the building code played in and where they could step in be more a team.

A team of the building and fire department in plan review, inspections and enforcement is the best defense for the city or municipality. Our team was faced with many challenges in a highly politicized town. However, after the first few battles, opinions changed. They changed because we were fair, we were proactive, and we didn’t come on site with any last minute surprises. We did our reviews in conjunction, shared our comments, and sent them out as one. We both felt we had jurisdiction over new and existing sprinkler systems. Did we confuse our contractors with our differences? No, we got together and did the underground, above ground, rough piping, and final inspections as a team. We got to the point as a team that if an inspector that had to be there, couldn’t be there, he or she could trust the others to make their inspection report complete. Instead of forcing the contractor to be perform the tests again. We were not perfect, if you were getting that picture, but we built a good reputation, and if we had sprung a violation on a contractor that we missed in the past, our reputation smoothed the way. Instead of the contractor beating a path to the city manager, they, after a while knew we weren’t out to get them. If you’re a building department or fire department at odds with the other, you’re missing out on great knowledge and lack the total team experience all contractors are expecting. Extend the olive branch, at least from 8am to 5pm.

Some of the Expert of the Day (EOD) questions we get floor me. I or we get numerous questions or situation where the contractor is asked to install sprinklers on the balconies and decks of the residential project they are working on from the local AHJ…at the final inspection, when residents are waiting to move in. Internally I get angry, not at the contractor asking the question or looking for a solution, but at the local AHJ’s. Why? Something went wrong inside City Hall or at the Fire Department most likely. I am one of those pesky building or fire officials, and I expect more professionalism from my fellow reviewers and inspectors. Many times, I’ll ask, “Why wasn’t this caught at plan review”? Many times the exasperated contractor says, “I don’t know”, or “Well, it’s not done yet”. Cough, if the plan review is not done by the time the Certificate of Occupancy is requested there is a problem(s). Tell me this AHJ’s, how can you inspect a project without approved plans? Plans that contain the hydraulic calculations, the cut sheets of all the installed equipment, and the proposed locations of the entire pipe.

How can you arrive on site, walk through and give the thumbs up, when you haven’t got the ok from the plan reviewer and have those plans on site to double check? I’ve got a member contractor on the phone, saying, “Is this true? Do sprinklers have to be out on the balconies?” “Yes, it’s in the building code and has been since 2003”. I’m not put out by the contractor; I’m outraged by the fire and building department. Why, do we have to put contractor who buys the permit, which pays our salaries in such turmoil?

Bottom line, we at NFSA want our contractor’s plans reviewed for compliance, and we want them reviewed under the guidelines of the ICC and NFPA in a timely manner. We expect the best out of our contractors, and personally coming from both sides, I see great efforts and practices from our contractors, and great efforts from the plan reviewers. Fire sprinkler contractors usually are behind to start, and we always stress to them, get them to the AHJ as soon as they are done.

I know local AHJ’s and the budgets they face, and I don’t blame them personally, but something has to change. Both professions, the sprinkler and the AHJ, need to communicate to come to solution. The contractor can’t afford the last minute changes, and the AHJ can’t afford the extra time for paperwork, time taken away from other projects, and the “black eye” anymore to their profession. We are proud to represent both the sprinkler contractors and the AHJ’s and stand by as professionals of the industry to help out.

Jeff Hugo is the Manager of codes for NFSA and a registered builidng official in Michigan.

{ 0 comments }