10 Strategies for Improving Emergency Management

I recently listened to an interview with author and professor Sean McFate.  In the interview he discusses the changing landscape of warfare and what the US must do to keep up, particularly since we are still largely stuck in a mindset of conventional warfare.  For those interested in this very insightful interview, it was on The Security Studies Podcast.

Obviously, a great deal has changed over the decades in warfare, but many philosophies and perspectives have remained the same.  As I listened to the interview, I found McFate’s words to ring true for emergency management as well.  We have had some changes in focus from civil defense, to natural hazards, to terrorism, and now toward what seems to be the most comprehensive all-hazards perspective we’ve ever had.  We’ve also had changes in technology and methodologies, but we still seem stuck in a lot of old ways of thinking.  Emergency management isn’t linear.  In fact the lines are blurred so much that it’s hardly cyclical (another old way of thinking).

McFate espoused that high-level warfare strategies should span administrations and leadership changes.  They should be durable and adaptable.  In the interview he discussed 10 new rule of war, which were summarized from his new book.  As such, I offer 10 strategies for improving emergency management.  You will see that most of these items aren’t radical.  The fundamentals of what we do in emergency management must certainly persist, but some perspectives do need to change.  Here’s what I have to offer:

  1. More incentivization for data-driven hazard mitigation and resilience

There are a few items to unpack in this one.  First of all, fully bringing the concept of resilience on board and marrying it up hazard mitigation.  Where there is some overlap in the two, there are also distinct differences.  Ultimately, however, the ideal end state for the two is the same: eliminate or significantly reduce hazards and impacts from those hazards.  The more we start discussing hazard mitigation and resilience together, the more we will see the linkages between the two.  Hazard mitigation funding, likewise, needs to be broadened to incorporate concepts of resilience.

Another key item here is making these projects data-driven.  Let’s do a better job of quantifying risk in relatable terms.  Risk needs to include not only immediate potential impacts, but also cascading effects.  Once we have that impact data, then root cause analysis is important.  Some of this is regulation, some engineering, some human behavior.  Also keep in mind that this needs to truly be all-hazards.

Lastly, incentivization.  Incentivization isn’t just funding, and gold stickers are not tangible incentives.  Make it meaningful.  Also make these incentives more immediate.  It’s great that mitigation measures can result in a locality paying a lower percentage in the event of a future public assistance declaration, but that could happen years from now, or it might not.  That’s still good to include, but let’s be real – tax payers and law makers don’t just want to dream about the reward, they want to enjoy it now.

  1. Ground preparedness in reality

I’ve seen a lot of preparedness activities (planning, organizing, equipping, training, and exercises) based on someone’s “good ideas” instead of actual data and needs.  It’s no coincidence that I just mentioned data in the previous point.  How many jurisdictions actually use all that data from their hazard mitigation plan, generally synthesized at significant expense, for other emergency management needs?  It’s quite a rare occasion.  Why?  Most practitioners view hazard mitigation to be a totally different animal.  It’s not sexy response stuff, so they don’t see a need to pay attention to it.  Instead, they fully dismiss what was done for hazard mitigation planning and do their own hazard analysis.  It seems to be a no-brainer that we should do better at developing one system to meet both needs.

Needs assessments take time and that has a cost, but leadership should be making informed decisions about what preparedness needs exist.  Absent conducting a needs assessment, the wrong decisions can easily be made, which results in a waste of time and money.  Most every emergency management agency has a story of time and money wasted on knee-jerk reactions.

Needs assessments should be applied to every aspects of preparedness.  In planning, we want to minimize assumptions and maximize data.  If an incident of the type you are looking at has never happened in your jurisdiction, make comparisons other similar jurisdictions.  Training programs should be based on identified needs, and individual courses should be developed based upon identified needs.  Probably a good opportunity for me to mention that ICS Training Sucks (but a realistic training needs assessment would fix it).  Similarly, the objectives we identify for exercises should be grounded in recognizing what capabilities and plans we need to validate.

Observation: When we look at the 32 Core Capabilities from the National Preparedness Goal, Threat and Hazard Identification is a Core Capability sitting in the Mitigation mission area.  If threat and hazard identification is so fundamental to what we do across all of emergency management, why isn’t it a common capability along with Planning, Operational Coordination, and Public Information and Warning?  Perhaps that needs to change?

  1. Boost regional efforts and coalitions

It’s interesting that everyone talks about how emergency management is a collaborative effort, yet in practice so many are resistant, reluctant, or negligent in working collaboratively.  Sure, it’s often easier to write a plan yourself, but the end result likely isn’t as good as it would be from a group effort.  In healthcare preparedness (yep, that’s a part of emergency management, too), they have been using regional healthcare coalitions.  These coalitions cover all aspects of healthcare, from hospitals, to clinics, to private practices, nursing homes, and EMS, along with health departments.

There is certainly precedent in emergency management to work collaboratively.  There are required collaborations, such as Local Emergency Planning Committees (LEPCs), as well as those emphasized in practice, such as in plan development.  LEPCs are great, and often under-utilized in a lot of areas.  In some areas, especially those with heavy industry, they are large and busy, and can’t really take on any more than they already do, but in other areas they have much less to do and could certainly work with a dual purpose as a standing emergency management coordination or advisement entity.  Regardless of how it’s done, build a local or regional EM coalition.  The relationships and perspectives, if properly organized and tasked, will reap some great benefits.  Don’t forget to make them regional, if that makes sense for you.  Disasters don’t give a damn about the funny lines we draw on maps.  And don’t just make these groups about meetings… actually engage them in meaningful preparedness activities and other aspects of emergency management.

  1. Embrace scholar-practitioners

One of the items McFate mentioned in his interview was embracing scholar-practitioners. Now I’m not the kind of person to espouse that a practitioner is any better than a scholar, or vice versa.  They each have an important role, especially in a profession like emergency management, where there is a lot of theory (more than most people realize) and a lot of application.  That said, we don’t have to pick a side.  You can be whoever you want, in fact you can even do both.  Does being a practitioner mean that you have to be a full-time emergency manager? Nope.  Being a scholar doesn’t necessarily mean you must be a professor or a student pursuing an advanced degree, either.  I would absolutely argue that regularly reading some research papers or a book on related topics, or even this blog, makes you a scholar.  If you have interest beyond just direct application, and like to think or discuss broader ideas in emergency management, that makes you a scholar.

I think it is scholar-practitioners that have that capacity to advance our profession more than others.  Not only is this group doing, but they are thinking about how to do it better.  If they come up with an idea of how to do it better, they have the greatest chance of actually giving their idea a try.  They are also the ones most prone to share their lessons learned, both successes and otherwise.

  1. Understand emergency management as a social science

Speaking of theory, we need to recognize emergency management for what it is.  While specific applications of emergency management may be within niche areas of practice and academic disciplines, most of emergency management is really a social science.  Social science is fundamentally about the relationships of people.  That is what we do in emergency management.  There are aspects of social science that may apply more than others, such as sociology or public health, but we also need to embrace political science.

In application, emergency managers need to become more astute in politics.  Not the partisan running for office type of politics, but politics as an aspect of governance, policy, and relationship building.  As an emergency manager, it’s your job to understand what every agency and department does in your jurisdiction, and how they fit into the function of emergency management.  Yes, you can espouse the benefits of emergency management and business continuity to them, but how do they fit into emergency management?  Some connections are easy to make, especially the public safety ones or extensions of that such as transportation, public works, and public health.  But many are quick to dismiss administrative, support, and social welfare agencies.  The better you understand them and are able to champion their involvement in emergency management, the stronger coalition you will build.

  1. Mindset: always in the disaster space

I mentioned in the introduction that the lines between the phases of emergency management are blurred.  We used to teach (and some still do) of distinct phases of emergency management: mitigation, preparedness, response, and recovery.  Sure it’s easier to teach about these when we put them in their own box, but that gives the impression to many that we only do one at a time.  The reality is that most jurisdictions are certainly doing mitigation, preparedness, and recovery right now – and maybe even some element of response.

The main point here is that we need to change mindsets of people.  I’ve had plenty of people ask me what emergency managers do when there isn’t an active disaster.  I certainly have no problem satisfying this common curiosity, but the simple fact that they ask means that we aren’t promoting enough of what we do.  We need put ourselves and others in the mindset that are always operating in the disaster space.  It doesn’t need to mean that there is always a disaster response we are involved in, but we need to be very clear that we are active every single day in disaster-related work.

I’ll take this one step further, and that’s to suggest that the primary function of every government agency is emergency management.  Consider that we have roads not only for ease of everyone’s transportation, but so that we can more quickly and efficient respond to save lives and property.  Our public works departments provide potable water and sewage systems for public health purposes, which is part of the greater emergency management family.  I could give examples for every government agency.  The administrative departments support those agencies and the implementation of their missions.

It’s also worth mentioning here that since several of these agencies have involvement in our infrastructure that we need to seriously step up our investments in infrastructure, which not only make it better and more effective and efficient, but also more resilient (tying back to my first point)

  1. Step away from tactics

Far too many emergency managers still focus on tactics.  In defense of that, it’s easy to do, especially if you come from a public safety background.  I still think it’s important to understand tactics.  That said, an effective emergency manager needs to think less about implementation and more about strategy and relationships. There are plenty of tacticians out there.  One more isn’t needed.  What is needed is someone who can step back and see the forest for the trees, as they say.

  1. Private citizens won’t prepare, but volunteers can be engaged

We need to let citizen preparedness go.  I’m not saying we should give up on our message of individual and family preparedness, because it can make a difference, but we need to recognize that most citizens simply won’t do it.  This is a concept that has largely evolved out of society.  In the days of civil defense we were engaging a different generation of people.  We also presented them with a credible and scary threat that was being put in their face all the time.  Now is not that time.  Sure, there are models of citizen preparedness that still work to extraordinary lengths, such as in Cuba, but government oppression and a cold war mentality contribute significantly to that.  Our society has evolved to an extent of individuals not having the time, wherewithal, or interest in preparing themselves.  Sure there are exceptions to every rule, but largely, society has an expectation of being provided for by the government.

Citizen engagement, on the other hand, is still a great reserve that we can spend more effort tapping.  Trained, organized volunteers can accomplish an incredible extent of activity.  Volunteer management is no easy task, though.  Programs need to be developed and promoted, volunteers recruited and trained, and organizations sustained.  Volunteers must be given purpose and don’t forget about the critical link with government… how will this happen.  Religious institutions, corporate and union volunteer groups, and entities such as CERT are all great.  We just need to do a better job at incentivizing, managing, and engaging.

  1. Plan better for recovery

Ah, recovery.  Everyone talks about how we need to do it better, but too few resources are applied to making that happen.  Remember that preparedness starts with a needs assessment and planning.  We can identify estimates of disaster impacts from which we then extrapolate reasonable benchmarks of performance within the core capabilities of recovery.  The problem is that most recovery plans are written at too high a level and generally not followed through on.  Why? Maybe because the emphasis is always on the life safety aspect of response plans.  Certainly that’s important (and we can still do so much better with our response plans), but most recovery oriented plans fall incredibly short.  It seems that most governments that even bother to write recovery plans only do so to the extent of the plan being a framework.  They identify what the goals are, what agencies are involved, and provide some high-level objectives.  Typically no strategy is provided and the management of the recovery function is rarely mentioned, despite such a focus that we have on incident management.

I just recently had a discussion with a client about recovery exercises.  They were approached about the need to conduct more of them.  Smartly, they responded by putting the focus back on the requester by asking if the recovery plans were ready to be exercised.  Once the requestor took a moment to consider, their answer was no.  Remember that (in most cases) exercises validate plans.  We can conduct an exercise in the absence of a plan, but generally that only confirms the lack of a plan.  Plans establish the standards of performance that we use in exercises and in real life.

  1. Use technology to the greatest extent, but prepare for austerity

Ah, technology.  It’s a wonderful thing, until it doesn’t work.  I’m a big fan of the efficiencies that technology provide, especially when technology is developed to solve a specific problem, not to create new ones.  Processes should dictate technology needs, not the other way around.

Technology is mostly a data tool.  It helps us to communicate more quickly and efficiently; access, organize, and transmit data; visualize data; and collect data.  More specifically, we use technology platforms such as EOC management systems and GIS.  These have allowed us to make significant strides in what we do and how we do it.  I’ve used dashboards, databases, maps, 3D models, simulators, and more to do my job.

I’ve seen some emergency managers simply not embrace technology.  And I mean at all.  Not even a computer.  I understand how they are able to function, and though they may have brilliant minds for emergency management, they are simply not able to do much without an assistant to research, type, print, and even communicate for them.  While I’m seeing this less and less, there are still some of these folks out there, and it’s not just older generations, either.

There are many who have a reasonable literacy of technology, but still aren’t embracing inexpensive or even free resources that would make them more effective.  This is even more important for the majority of emergency managers, who are typically one-person offices with few resources.   Maybe listing some of these resources will occur in a future post of mine.

Despite the wonders of technology, I often advocate procedures for going dark (i.e. when your technology fails).  After all, we are emergency managers, are we not?  Every EOC that uses a technology tool to manage functions within their EOC should absolutely have a low tech back up, procedures and training in how to implement it, and an annual exercise to test those procedures and keep people in practice.  Carbon paper and gas station maps are your friends.

~~

Well there they are: 10 strategies for improving emergency management.  As I stated in the introduction, there really isn’t anything revolutionary here, although some concepts might be a bit controversial, which I am happy to embrace.  Perhaps I missed an important point or have a poor perspective on something.  I absolutely welcome your comments and feedback, as always.

© 2019 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC℠®

 

Advertisements

10 Considerations for Your EOC

Many jurisdictions, agencies, and organizations have emergency operations centers (EOCs) identified in their emergency plans to support incident response and recovery operations.  Through my career, I’ve seen all manner of EOCs, used to support entire incidents or just specific missions, ranging in size from just a handful of people to well over 100 people, various organizational models, and even varying degrees of successful implementation.  I’ve also seen many different locations for EOCs.

An EOC can be established anywhere, but just like any broad statement, there are a number of caveats to that.  Here are 10 things to consider in identifying a location for your EOC:

  1. Out of harm’s way

While it’s difficult to determine where an incident will strike, most jurisdictions have areas that may be less susceptible than others.  While it’s certainly convenient to have your EOC off a major highway, consider that a significant accident on that highway will impact access to your facility.  Locating your EOC near an industrial district or in a flood plain is just asking for trouble.  Be smart about where you locate your EOC relative to your geographic risk profile.

  1. Plenty of parking and accessibility

Few things are more frustrating than arriving to an EOC and not having a place to park.  That’s simply a silly problem to have and reflects greatly on shortsightedness.  If you are stuck in a certain location, plan for an overflow lot, signage, and a shuttle.  Also make sure your building is accessible.  I’ve seen far too many EOCs located either in basements or upper floors without any elevators or other ability for access for people with disabilities.

  1. Utility services and communications with redundancies

It practically goes without saying in our current age of technology, but we need to ensure full utility service in our EOCs.  This includes the basics like electricity, HVAC, and water, but also internet, terrestrial telephone, cellular service, television service (either cable or satellite), and radio communications.  The best facilities will have redundancies in these services to the greatest extent possible.  Generators (with fuel) are rather essential.  Engage your IT staff to ensure maximum flexibility and connectivity with wifi and wireless printing, while still maintaining secure networks.  Each work space should also be able to easily access outlets without running an excess of extension cords (but always have some on hand!).

  1. Meal and break rooms

Constant engagement fuels stress and exhaustion which leads to degradation of our ability to perform.  While work in an EOC may not be so physically strenuous, it can be mentally draining and having respite locations are important.  Both for respite and the sake of keeping work spaces clean, you want to have a separate dining area that can accommodate seating for everyone (at least in shifts), a place to wash hands, refrigeration of food and beverages, potable water and coffee/tea, and space for prepared food to be delivered and maintained within safe temperatures.

  1. Seating and tables

It seems odd to have to say this, but adequate seating is quite important.  I’ve been in EOCs that simply didn’t have it.  While I appreciate the ability of a jurisdiction to set up an ad-hoc EOC, a single six foot table and a few folding chairs aren’t likely to meet your needs.  If you don’t have a dedicated EOC (not everyone needs one!), meeting and conference rooms may have plenty of seating, though if they are too small, you will be extremely limited.  Thankfully folding tables and chairs are reasonably inexpensive and easy to store.  Consider the functional spaces you need to accommodate your EOC’s organization, be it ICS-based, Incident Support Model-based, or Emergency Support Function-based.  Functional groups should have their own work spaces and the arrangement and workspaces they need to accommodate and facilitate their functions.  Always plan for more people than you expect!

  1. Away from distractions

Your EOC shouldn’t be in a space that other wise will receive a lot of foot traffic.  While co-location of facilities can seem like a great idea before an incident, having your EOC in the same building as a shelter or your fire department is probably a bad idea.  It’s not only distracting, but also infringes on utility and communication usage, and even security.

  1. Security

Speaking of security, ensure that access to your EOC is limited only to those who should be there.  Generally, personnel not working in or serving the EOC should not have access to it.  It’s a pain to have civilians, the media, or other random persons wandering into an EOC, especially when they want immediate answers to complicated questions or feel their needs should be addressed first.  Along with ensuring access controls, security procedures should be in place, including a staffed reception desk and sign-in.  Personally, I also prefer armed security (law enforcement) for most EOCs.

  1. Meeting and briefing space

Meetings and briefings are a necessity in incident management.  It’s a way in which we share information, work through problems, and make decisions.  Of course there is always the danger of personnel getting stuck in a perpetual meeting, but that’s a topic for another blog post.  Ideally, your EOC should have adequate breakout space for these meetings and briefings.  An open space with a podium may be necessary for media briefings, and meeting rooms with conference call and video conference capabilities may also be required.  Having a separate space allows a meeting to take place without distraction from the general EOC activity while also being able to discuss sensitive information.

  1. Display space

One of the hottest commodities in an EOC is display space.  Space to project with an LCD projector, hang chart paper or maps, and write on with a dry-erase marker is pretty essential to helping ensure that people are informed and information is tracked.  Higher-tech EOCs may elect to have flat screen monitors mounted on the wall, as well.  Easel stands and portable white boards can augment this and make your space more flexible as well.

  1. A good backup site

One of the best tips I can provide about having a great space for an EOC is to have two!  You will be thankful you have that second space identified and planned for in a continuity situation.  If you don’t need it, it can always be used for something else, but if you do need and don’t have it, you will be scrambling to find a location, get your personnel there, and ensure you have supplies, equipment, and other needs addressed.

 

There are certainly a number of other considerations for EOCs, but paying heed to these ten will get you far.  Your EOC doesn’t need to be a dedicated facility.  It can be any reasonably flexible open space, such as town hall, a large meeting space, a training facility, a hotel conference space, or even a warehouse – your needs should determine your space.  Once you have identified your space, make it functional and ensure that you have an EOC plan and procedures. Train staff, develop job aids to support their tasks, and exercise your plans regularly!

© 2019 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®℠

We Only Need One ICS

I came across an article yesterday posted on EMS1/AMU’s blog about EMS adopting an incident command system.  It’s an article that leaves me with a lot of questions.

I want to examine some individual statements within the article.

  1. “Many EMS providers lack training and awareness about implementing an incident command structure.”

 

This is 100% true, but I’ll also expand this statement across much of public safety and emergency management.  Aside from well-experienced practitioners of ICS, which there are relatively few compared to the greater public safety/EM community, most simply aren’t equipped to implement a significant incident management system.  The biggest reason is that ICS training sucks.

 

  1. “EMS organizations have only recently recognized the value and need for such a command structure as part of their response strategy.”

 

I would suggest that this is partly true, but in many parts of the nation, requirements and standards have been established by way of executive order, state and regional EMS protocols, and other means for EMS to use ICS.  Many of these have been in place since the 90s, before HSPD-5 and NIMS requirements, but certainly with the emergence of NIMS in 2003, this has largely been a standard of practice for EMS, if not a requirement in many places (and under specific circumstances, such as required through OSHA 1910.120).  While I understand that ‘standards’ and ‘requirements’ don’t necessary define value, they essentially dictate a need.

 

  1. There was a recognition that “EMS providers were having difficulty applying fireground incident command practices to EMS calls.”

 

While I agree with what I think is the spirit and intent of this statement and bring this back to my comments on item 1 above, I’m still cringing at the ‘fireground incident command’ phrase in this statement.  ICS isn’t just for the fireground. While it may have been born in wildfires, that was decades ago.  We are now officially in 2019 and should be well past this concept that ICS is only for the fireground.  Even if we disregard, for the sake of discussion, the requirements for all responders to use ICS, such as those in OSHA 1910.120, which predate NIMS, HSPD-5 was signed almost 17 years ago!  Nothing in HSPD-5 or the original NIMS document elude to the current implementations of ICS being a fireground system.  It was to be applied to all responders.

 

  1. “During a response, providers did not establish a formal command structure”

 

Totally true.  This applies, however, not just to EMS, but to most of public safety.  See my comment for item 1.

 

  1. “In 2012… they began to research various fire and EMS command models that were scalable and practical for all types of critical EMS calls.”

 

I’m not sure why there is a need to look past NIMS ICS.  Perhaps we are stepping back to my comment on item 1 again, but if you understand the system, you can make it work for you.

~

It is absolutely not my intent to throw negativity on the author or the people who spearheaded the implementation of an EMS-specific ICS as cited in this article.  They clearly identified what they perceived to be a need and tried to address it.  I give them credit for that.  It should be seen, though, that they identified many of the same needs that ICS was developed to address in the first place.  They then created a system (which has many of the same qualities of ICS) that is focused on EMS needs during an incident.  The issue here is bigger than this article, and certainly more endemic.  Unfortunately, the article doesn’t really provide much detail on their ‘provider in command’ model, but what they describe can all be accomplished through NIMS ICS if properly utilized.  They even identify objectives of their model, which are really just pre-identified incident objectives.  They certainly don’t require a different model.  I think, however, what they largely accomplished was an audience-specific training program to show how elements of ICS can be implemented.  I just don’t think they needed to change the model, which is what the article seems to indicate.

Sadly, trying to make customized adaptations of ICS is nothing new.  For years, some elements of the fire service have dug in with certain models which are fire-ground centric.  Other disciplines have dome similar things.  It’s worth mentioning that FEMA had developed a number of discipline-specific ICS courses, such as ICS for Public Works or ICS for Healthcare.  While the intent of these courses is to provide context and examples which are discipline-specific (which is a good practice) rather than new models specific to these disciplines, I think that has inadvertently given some the impression that there are different systems for different disciplines.  ICS is ICS.

Once again, I put the blame on poor training curriculum.  When a system is developed and proven to work under a wide variety of circumstances and for a wide variety of users, yet users keep feeling a need to develop adaptations for themselves, this is not a failure of the system or even the users, it’s a failure of the training.

There are facets of public safety and emergency management that are generally not using ICS as well or as often as they should.  EMS is one of them.  As an active EMT for over a decade (including time as a chief officer), I can attest that (in general) ICS training for EMTs is abysmal.  The text books tend to skim over the pillars of ICS and focus on the operational functions of triage, treatment, and transport.  While these are important (for a mass casualty incident… not really for anything else), they fail not only in adequately TEACHING the fundamental principles of ICS (which can and should be used on a regular basis), but they fall well short of actually conveying how to IMPLEMENT ICS.  Further, much of the training provided includes a concept of ‘EMS Command’, which is opposed to what is in ICS doctrine.  We shouldn’t be encouraging separate commands and ICS structures at the tactical level of the same incident.

A few years ago I had started a crusade of sorts to get a better ICS curriculum developed.  There was a lot of support for this concept across the public safety and EM community, not only in the US but other nations as well.  Perhaps with the coming of the new year that effort needs to be reinvigorated?

© 2019 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC

EOC Training is Coming from FEMA

Last week I posted an article espousing the lack of emergency operations center (EOC) content in the most recently updated ICS-100 course.  In response to this article, I heard from someone at FEMA’s Emergency Management Institute (EMI) letting me know about two courses which are currently in development, focusing on EOCs.  The first is IS-2200: Basic EOC Functions.  This is being designed as a four-hour online course.  The second is E/L/G-2300: Intermediate EOC Functions.  This course is being designed for a three-day long classroom delivery.  These courses are both expected to release in the spring of 2019.

For those who aren’t familiar with FEMA’s course codes…

IS: Independent Study (web-based delivery)

E: In-resident course, typically delivered at EMI

L: A course delivered on-location by FEMA personnel anywhere around the nation

G: State-delivered courses

Personally, I’m thrilled to get definitive word that courses are being developed and that we have a timeframe for deployment.  I’m a big proponent of the roles EOCs can play in incident management, yet so much of the training conducted for EOC personnel for so many years has been ad-hoc at best.  Hopefully this will further move us toward standardization and common implementation of best practices.

© 2018 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC

Incident Management vs Incident Command

As I was writing my thoughts on the updated ICS-100 course in my previous post, I got to thinking that it may be prudent to reinforce the difference between incident management and the incident command system (ICS).  ICS is a specific application of incident management, while incident management is, in all, much broader than ICS.  Incident management includes field responses, emergency operations centers (EOCs), activities of secondary and tertiary organizations, funding streams, public information, and even the mechanics of politics focused on that disaster response.  Ideally, we would prefer these to all be orchestrated, such that they operate lock-step, but rarely, if ever, do we see such a thing.  It would be as if a chorus, band, orchestra, stage performers, ushers, concessioners, stage hands, lighting and sound operators, and custodial staff were all working on the same performance and conducted by one person.  They don’t.  It just doesn’t happen that way.  That’s why incident management systems, such as ICS, were developed.

Knowledge and application of systems, like ICS, are certainly important.  The beginning of every ICS class tells you why, so I don’t need to get into that here.  But to continue with my oft criticized analogies, if ICS is the trees, incident management is the forest.  And, as it turns out, many people can’t see the forest for the trees.  While ICS may be concerned with putting out the fire, stopping the bleeding, or catching the proverbial bad guy, incident management is about so much more.  Even doctrinally, consider that the National Incident Management System (NIMS), comprised of key elements, such as resource management, command and coordination (this is the ICS piece, and more), and communications and information management.  We also need to consider incident management beyond these, in as broad a scope as possible.

Incident management is a deliberate series of actions taken to solve problems associated with incidents and disasters.  There are a lot of problems that can be caused, directly or indirectly, by whatever issue we are dealing with, be it flood, fire, or hostile event.  Incident management needs to prioritize these problems and take action to address them.  While it may sound like our incident command system structures do the same type of thing, they are often concerned with immediate effects and actions that save lives and stabilize the incident, as they should be.  But that focus, necessarily, is narrow in scope and doesn’t address all the ancillary and important issues that an incident may cause.

Consider FEMA’s Emergency Support Function (ESF) structure and the matters they address.  Here are a few:

  • Transportation
  • Communications
  • Public Works and Engineering
  • Mass Care, Emergency Assistance, Housing, and Human Services
  • Public Health and Medical Services
  • Agricultural and Natural Resources
  • Energy
  • External Affairs

Do your plans address these issues?  And by plans, I mean real, actionable plans.  Many jurisdictions have functional annexes to their plans, most following the federal ESF structure, which do little more than state what agencies participate in each of the jurisdiction’s ESFs and what their primary goals are.  Let’s be honest… these are aren’t plans.  They are fully inadequate to be plans.  These are prose I might use for the introduction of a plan, but certainly not the substance of the plan itself.  This is exactly why we are missing the mark when it comes to incident management.  We talk a lot about ICS, ICS is in our plans, we train people in ICS (though not as good as we should be), emphasize ICS in exercises, and focus on ICS when an incident occurs, but how much attention is given to broader incident management?  Typically far too little.  I’ve actually had conversations with local public safety officials, asking them how well they feel they are prepared for the next disaster, and they responded that they are fine because they are trained in ICS.  I’ve received this response in more than one jurisdiction.  That’s pretty scary, especially given the lackluster condition of their plans.

Can ICS be applied to broader incident management issues?  It sure can.  It’s simply a management system that can be applied to anything you want.  But the problem is that people conceptualize ICS as something to only use ‘in the field’ and during the more urgent initial period of response.

The take-away from this is that we need to identify what our issues are and how we are going to manage them.  These are essential parts of the planning process.  Write good plans.  Invest time, effort, and likely some money into it.  Do you need to use the ESF structure?  No, but certainly make sure that all concerns are addressed.  Think about the cascading impacts of an incident.  Leverage stakeholders from across the community to ensure that you are getting input from multiple perspectives and interests.  Doing so will help you be better prepared to manage the entirety of the incident.

As always, thoughts are appreciated.

© 2018 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC

Updated IS-100 Course: Missing the Target

Earlier this week, FEMA’s Emergency Management Institute (EMI) released course materials, including student manual, handouts, instructor guide, and visuals, for the updated IS-100/ICS-100: An Introduction to the Incident Command System.  Note that this update (IS-100.c) has been available online since the summer.  The release of materials, however, included no errata, so absent comparing the previous version to this, I can’t speak specifically to what the changes include, though I’m aware from their release of the online course several months ago that there were adjustments to account for some of the revised content of the third edition of the NIMS doctrine, released in October of last year.

Those familiar with my running commentary for the past few years of ‘ICS Training Sucks’ are aware that much of my wrath was focused on the ICS-300 and ICS-400 courses.  That said, with the release of the third edition of NIMS (my review of the document can be found here), there were some needed additions to incident management fundamentals and my realization that the ICS-100 and ICS-200 courses are ignoring a significant population of professionals in their content.  While ICS itself was largely built for field personnel working within a command (vice coordination) structure, over the years, the prevalence of various forms and types of emergency operations centers (EOCs) has grown significantly.  One of the biggest additions in the most recent version of the NIMS document was, in fact, the inclusion of much more meaningful content on EOCs and their potential organizational models.  While still a minority compared to first responders, there is a significant audience of people taking ICS-100 because of their assignment to a local, county, state, or organizational EOC.  Yet, the ICS-100 materials have scantly more than ONE SLIDE talking about EOCs.

Yes, we do have courses such as the ICS/EOC Interface course and others that dive deeper into EOC operations and how they coordinate with each other and with command structures, but the introduction to all of this is often the ICS-100 course, which all but ignores EOCs and the audiences who primarily serve in them.  In fact, there are many jurisdictions that require EOC personnel to have ICS training (smartly), which starts with the ICS-100 course (why?  Because it’s the best/only thing generally available to them), but I’m sure many people taking the course are a bit confused, as it doesn’t speak at all to their role.  While I feel that ICS training for EOC personnel is important, an introductory course like this should include a bit more on EOCs.

As with my original writing on ICS Training Sucks, I bring this back to the fundamentals of instructional design, which is focused on the AUDIENCE and what THEY NEED TO LEARN.  It’s evident that these fundamentals are being ignored in favor of a quick update, which might change some content but does not improve quality.  Let’s actually look at who are audience groups are and either incorporate them all into the course, or develop another course and curriculum to meet their specific needs (aka EOC-100).  Otherwise, they are simply ignoring the fact that what is currently available is like fitting a square peg into a round hole.  Sure it fills a lot of space, but there are also some significant gaps.

While a number of jurisdictions have identified this need and developed their own EOC training, there are a lot of standards and fundamentals that could be addressed by FEMA in a national curriculum.  This is certainly a missed opportunity, and one that makes many of our responses less than what they should be.

© 2018 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC

NIMS Alert: NQS Qualifications and Task Books for Recovery, Mitigation, and Incident Evaluation

The National Integration Center (NIC) has been busy with developing more National Qualification System (NQS) tools for incident management.  Here are the titles for the latest release open to public comment:

  • Damage Assessment Coordinator
  • HM Community Education and Outreach Specialist
  • HM Community Planner Specialist
  • HM Engineering and Architect Specialist
  • HM Floodplain Management Specialist
  • EHP Environmental Specialist
  • EHP Historic Preservation Specialist
  • Incident/Exercise Evaluator
  • Public Assistance
  • State Disaster Recovery Coordinator

There may be some incident management and response purists out there wondering why they should care about these particular titles.  I’ll agree that most of them aren’t used in a life-saving response capacity, but these are the people you want to have backing you up – otherwise you may never get away from the incident and you will find yourself in a very foreign land where complex requirements from FEMA and other federal agencies are the rules of play.

Having worked disaster recovery for some massive incidents, such as Hurricane Sandy, I can personally attest to the value so many of these people bring to the table.  It’s great to see qualification standards being established for them, just as they are for core incident management team personnel and resources.  While my experience with most of these is ancillary, however, I’ll leave specific commentary on them to those functional experts.

There is one role in here that I’m particularly pleased to see and will comment on, and that’s the Incident/Exercise Evaluator.  I wrote last year on this topic specifically and have reflected on its importance in other posts.  I see the inclusion of an Incident Evaluator in the NQS as being a huge success and the beginning of a conscious and deliberate shift toward evaluation and improvement in what we do.  Looking at the resource typing definition, I’m pretty pleased with what the NIC has put together.

What I like… I appreciate that they include a note indicating that personnel may need additional training based upon the nature or specialization of the incident or exercise.  They include a decent foundation of NIMS/ICS, exercise, and fundamental emergency management training across the various position types (although most of these are FEMA Independent Study courses -which I think are great for introductory and supplemental matter, but shouldn’t be the only exposure personnel have), including a requirement of completion of the Homeland Security Exercise and Evaluation Program (HSEEP) for a Type 1.

What I feel needs to be improved…  Considering that the Type 1 Incident/Exercise Evaluator is expected to lead the evaluation effort, I’d like to see more than just HSEEP training being the primary discerning factor.  Just because someone has completed HSEEP doesn’t mean they can plan a project, lead a team, or extrapolate HSEEP exercise evaluation practices to be effective for incident evaluation.  I suggest HSEEP should be the requirement for the Type 2 position (which would correlate well to the position description), with additional training on project management and leadership supporting the Type 1 position.  While the note is included re: the potential need for additional training, there is nothing in this about operational experience, which I think is rather important.  Lastly, this seems to identify a need for course and/or guidance specific to incident evaluation, which can and should use the principals of HSEEP as its foundation, but identify the differences, best practices, and approaches to applying them to an incident or event.

I’d love to hear your thoughts on incident evaluation as well as the other positions being identified in the NQS. Do you participate in the national engagements and provide feedback?

© 2018 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC™