Showing posts with label ICS. Show all posts
Showing posts with label ICS. Show all posts

Friday, January 31, 2014

How Local Governments Hinder Our Response to Natural Disasters

Read this article: "How Local Governments Hinder Our Response to Natural Disasters" by Mr. David Wachsmuth; it could potentially be construed as heresy in some circles, but there is also a degree of truth in the observations he makes. Wachsmuth looks at the aftermath of Superstorm Sandy and talks about how the Mayor's office usurped the power to lead following landfall favoring improvisation instead of the plans the OEM had created.

One of the more interesting takeaways from the article is this:

"Collaborations need to be achievable to be useful. The sociologist Lee Clarke argues that disaster plans are "fantasy documents"—tools for building trust in an organization rather than actual, implementable plans. This was certainly true in the response to Sandy. More modest plans, which take account of political realities and power relations, are more likely to be useful than comprehensive but unachievable fantasy documents." 

A lot of time, effort, and money goes into disaster planning and yet I've seen firsthand, as I'm sure many of you have as well, the ad hoc nature of response environments. Even when the best curated plans are exercised ad nauseam, challenges remain. This is not to say that planning can account for every facet of a disaster, but it would seem that two opposing forces are being pushed simultaneously, the need for rigidity in planning that ICS and the command and control mentality require, and the push for greater community involvement to build resilience and self-reliance. 

How do you reconcile the rigidity that is often seen in municipal planning with the inherent ad hoc nature of grassroots community response? What does that look like in a plan for a city? As it stands many plans don't account for emergent response activities but with the role Occupy Sandy played following Sandy, that will hopefully change.

If the idea that the Mayor's office totally disregarded OEM's plans seems crazy...you can read about how Michael Brown, (you may remember him as "brownie"), disregarded the newly minted National Response Plan following Hurricane Katrina...plan-averse public officials it seems, are nothing new.
http://www.washingtonpost.com/wp-dyn/content/article/2006/03/15/AR2006031502320.html

Monday, June 10, 2013

The Languages of Disaster

A series of these maps are making the rounds on the internets illustrating the regional differences in vocabulary...the bottom line being, different parts of the country use different words for the same thing: soda = pop / hoagie = sub / sneaker = tennis shoe / etc...























The same can be said for how we talk about disasters, the nomenclature we use is as varied and idiosyncratic as the communities we help. The two camps that exist in the disaster world are those in the traditional emergency management infrastructure and those who are not.

Traditional emergency management is based on the tenants of the command and control structure of NIMS and ICS, and within that camp there's SEMS, the foundational "language" on which NIMS is based. Within this acronym-laden alphabet soup lives a language / structure with it's own HR procedures, protocols, ways of conducting field ops, and ways of requesting assistance from neighboring jurisdictions.

The other camp are the non-profit organizations and everyone else, including people holding positions within local gov't, all of whom speak their own language or are making it up as they go as it relates to response and recovery activities. This is not to say that some of the national organizations / city governments don't have personnel who aren't "versed" in NIMS/ICS, but it's usually only a small percentage and ends up reinforcing a divide between established response organizations and those emergent groups who only stand up after an event.

One of the hurdles that exists in bridging this gap is that a NIMS org chart looks like this:

Nice. Organized. Clear Delineation of Roles and Responsibilities
And a non-profit org chart is more like this:

Too many jobs for too few people
And the org chart for spontaneous groups look like this:









There isn't one

State and Local Emergency Management Agencies speak NIMS/ICS because there are funding strings attached, the non-profit world usually receives their funding from private sources and are beholden to a different set of requirements--none of which have anything to do with ensuring NIMS/ICS compliance.

When NIMS/ICS aren't part of the daily operational vernacular, there are going to be problems in level setting expectations and creating a common place to start from following an event, especially when trying to bring the various players together to create a unified and cohesive response effort.

To help create consistency in operations from a county, state, and federal perspective, a series of frameworks have been created: The National Prevention Framework, The National Mitigation Framework, The National Response Framework, and The National Disaster Recovery Framework. While the debate rages on about whether or not the federal gov't has too many or not enough frameworks, the fact remains that they exist and provide a roadmap in which roles and responsibilities are outlined.

If you turn to the non-profit sector or beyond you'll find that no such guidance exists. National VOAD has consensus and guidance documents but nothing that sets forth expectations around roles and responsibilities following an event, leaving the door open for a re-interpretation of how things should go every time disaster strikes.

The command and control mentality only works to a point, but if the whole of community and community resilience talk is to be anything more than words, a common language and common ground need to be found to bridge the gaps that currently exist. If we don't speak the same language, working together will continue to be a struggle fraught with the same mis-interpretations and mis-understandings that have plagued response for as long as I've been a part of it.