|
Business Continuity Disaster Recovery COOP Crisis Management John Glenn CRP MBCI
March 16, 2009
NIST WTC findingsJohn Glenn, MBCI The blurb, at http://www.nist.gov/public_affairs/releases/wtc_100108.html, lists NIST "23 major and far-reaching building and fire code changes approved recently by the International Code Council (ICC) for incorporation into the 2009 edition of the ICC's I-Codes (specifically the International Building Code, or IBC, and the International Fire Code, or IFC), that are used as the basis for building and fire regulations promulgated and enforced by U.S. state and local jurisdictions. Those jurisdictions have the option of incorporating some or all of the code's provisions but generally adopt most provisions." Several of the changes, and a number of the "rejected for 2009" recommendations caught my attention.
From the document
The following are the 23 model building and fire code changes consistent with the NIST WTC investigation recommendations now required by the I-Codes (changes displayed in italics are ones that were approved at previous ICC hearings and incorporated at the Minneapolis hearing into the 2009 I-Codes):
Not ready for prime time?
The following are the nine model building and fire code change proposals consistent with the NIST WTC investigation recommendations that were not approved for the 2009 edition of the I-Codes but will be considered for resubmission at a later date after being amended:
Simple, low-cost options rejectedAs an Enterprise Risk Management practitioner I consider some of the recommendations to be in the "Duh!" category - "Isn't it OBVIOUS?" As an Enterprise Risk Management practitioner, I have to wonder how some very simple, very low cost recommendations were rejected for inclusion in the 2009 code update. You already may have guessed, by the red characters above which omissions I find particularly upsetting. I am not a structural engineer and, frankly, I would never volunteer to work more than three or four stories above ground level, so I am not qualified to comment on the structural considerations. We have discussed use of elevators as evacuation vehicles in the past and, with air pressure controlled to prevent fire and fumes from entering the elevator shaft - as they are prevented from entering the emergency stairwells - their time has arrived. But to exclude
Requiring fire safety and evacuation plans for all occupancies and buildings where required by the International Fire Code (the International Building Code is more widely adopted across the country than the IFC; this would ensure all situations are covered) and
seems, well, foolish. Why would anyone put off creation of "a risk assessment and acceptable mitigation of risks" for buildings of ANY size unless of course the people pushing back (a) don't work/visit the structure or (b) consider human life a "replaceable commodity." As an Enterprise Risk Management practitioner I never would limit the risk assessment to only those structures of a certain size or capacity. I particularly am bothered two words in the fire safety and evacuation plans statement: "where required" - I don't care what organization does or does not require these plans; the plans are needed to protect personnel in the building, both tenants and visitors. I rant and rave, froth at the mouth and roll around on the floor because fire safety and evacuation plans aren't posted all over the floor - near every exit and every congregation point (e.g., break room, water cooler). All things considered, how much can it cost vs. loss of life or cost of the structure, to post fire safety and evacuation plans - essentially evacuation maps - around the structure? As far as requiring detailed schematic building plans, including an approved Building Information Card, to be located in fire command centers to show the type of construction, stairway access and pressurization, fuel oil tank and hazardous materials locations, standpipe availability and locations, in addition to typical floor plan and details of the building core, means of egress, elevator locations, fire protection systems, firefighting equipment and fire department access, this information should be available from the architects in the first place; I fail to see why anyone would push back on this recommendation. I confess there are a "few" more items I would like NIST to include in its list, things such as tornado and earthquake-proof construction - tornado-proof in all locations, earthquake proof in most locations (check your local fault map; chances are, your building is close to a fault). I once worked as a business continuity consultant for a pretty progressive company. But as progressive as it was, it failed to include a business continuity person when it went looking for a new building and later when it positioned the critical functions in that building. Turns out the building was in a flood plain and the critical business function was on the building's first floor. That was the first time I realized if might be a good idea to include someone "risk conscious" in more than simply "business continuity" planning. But, neither my progressive client nor NIST asked me for my two cents.
John Glenn, MBCI, has been helping organizations of all types avoid or mitigate risks to their operations since 1994. Comments about this article, or others at http://JohnGlennMBCI.com/ may be sent to Planner @ JohnGlennMBCI. com.
|