Tag MACS

Emergency Management: Coordinating a System of Systems

Tim Riecker, The Contrarian Emergency Manager 1 Comment

Emergency management, by nature, is at the nexus of a number of other practices and professions, focusing them on solving the problems of emergencies and disasters.  It’s like a Venn diagram, with many entities, including emergency management, having some overlapping interests and responsibilities, but each of them having an overlap in the center of the diagram, the place where coordination of emergency management resides. That’s what makes the profession of emergency management fairly complex – we are not only addressing needs inherent in our own profession, we are often times doing it through the application of the capabilities of others.  It’s like being the conductor of an orchestra or a show runner for a television show. It doesn’t necessarily put emergency management ‘in charge’, but they do become the coordination point for the capabilities needed.

Presentation1

 

This high degree of coordination depends on the functioning and often integration of a variety of systems.  What is a ‘system’?  Merriam-Webster offers that a system is a “regularly interacting or interdependent group of items forming a unified whole.”  Each agency and organization that participates in emergency management has its own systems.  I’d suggest that these broadly include policies, plans, procedures, and the people and technologies that facilitate them – and not just in response, but across all phases or mission areas.  Like the Venn diagram, many of these systems interact to (hopefully) facilitate emergency management.

There are systems we have in many nations that are used to facilitate components of emergency management, such as the National Incident Management System (NIMS), the Incident Command System (ICS) (or other incident management systems), and Multi-Agency Coordination Systems (MACS).  These systems have broad reach, working to provide some standardization and common ground through which we can manage incidents by coordinating multiple organizations and each of their systems.  As you can find indicated in the NIMS doctrine, though, NIMS (and the other systems mentioned) is not a plan.  While NIMS provides us with an operational model and some guidance, we need plans.

Emergency Operations Plans (EOPs) help us accomplish a coordination of systems for response, particularly when written to encompass all agencies and organizations, all hazards, and all capabilities.  Likewise, Hazard Mitigation Plans do the same for mitigation activities and priorities.  Many jurisdictions have smartly written disaster recovery plans to address matters post-response.  We also have training and exercise plans which help address some preparedness measures (although generally not well enough).  While each of these plans helps to coordinate a number of systems, themselves becoming systems of systems, we are still left with several plans which also need to be coordinated as we know from experience that the lines between these activities are, at best, grey and fuzzy (and not in the cuddly kitten kind of way).

The best approach to coordinating each of these plans is to create a higher level plan.  This would be a comprehensive emergency management plan (CEMP).  Those of you from New York State (and other areas) are familiar with this concept as it is required by law.  However, I’ve come to realize that how the law is often implemented simply doesn’t work. Most CEMPs I’ve seen try to create an operational plan (i.e. an EOP) within the CEMP, and do very little to actually address or coordinate other planning areas, such as the hazard mitigation plan, recovery plans, or preparedness plans.

To be successful, we MUST have each of those component plans in place to address the needs they set out to do so.  Otherwise, we simply don’t have plans that are implementation-ready at an operational level.  Still, there is a synchronicity that must be accomplished between these plans (for those of you who have experienced the awkward transition between response and recovery, you know why).  The CEMP should serve as an umbrella plan, identifying and coordinating the goals, capabilities, and resources of each of the component plans.  While a CEMP is generally not operational, it does help identify, mostly from a policy perspective, what planning components must come into play and when and how they interrelate to each other.  A CEMP should be the plan that all others are built from.

Presentation2

I’m curious about how many follow this model and the success (or difficulty) you have found with it.

As always, if you are looking for an experienced consulting firm to assist in preparing plans or any other preparedness activities, Emergency Preparedness Solutions is here to help!

© 2016 – Timothy Riecker

Emergency Preparedness Solutions, LLC

Training EOC Personnel – ICS is not Enough!

Tim Riecker, The Contrarian Emergency Manager 6 Comments

A consistent misconception is that if an emergency operations plan calls for an Emergency Operations Center (EOC) to utilize the Incident Command System (ICS), then EOC personnel only require ICS training to be successful in their jobs.  ICS training, however, only gets personnel part way to success.

Regular readers of my blog know that I am a big advocate of conducting needs assessments.  Often times, agencies don’t know how to conduct a needs assessment, don’t think it’s important enough to conduct one, don’t think that conducting one is necessary, or simply don’t even consider conducting a needs assessment.  The result is creating training or using existing training that does not meet the real needs.  Certainly if an EOC is using the foundations of ICS to define its organizational structure and processes, then ICS training is absolutely important.  Consider, however, the multitude of other processes that take place in an operational EOC that are not included (in whole or in part) in ICS training.  Processes including financial management and procurement, situation reporting, and use of EOC management and resource tracking software are so diverse and can very from jurisdiction to jurisdiction.

The unique application of Multi-Agency Coordination Systems (MACS), an element of the National Incident Management System (NIMS), just like ICS, by each jurisdiction also has to be considered.  While there are numerous best practices in MACS, their interface with ICS – often implemented through an EOC – is influenced significantly by governmental structure, statutory responsibilities, and politics more than can be addressed by any training curriculum. Consider simply the differences between a state EOC, a county EOC, and a local government EOC and their unique roles and needs. For as much standardization NIMS encourages, there will still be different ways of implementing these systems.  In the end, the challenge remains the same – how do we train people to function in EOCs?

First, do conduct that needs assessment.  What do people have to know and what skills must they have to be successful in an EOC?  At this point, I speak foundationally, as additional and more in-depth training can be explored based on position and responsibility.  Certainly ICS – with sufficient detail in positions of the organization and the planning process.    What else do they need to know?  ICS training does not address in detail what an EOC is or does – an important understand for people to have.  What processes must they be familiar with?  What tools or methodologies does the EOC use that must be trained on?  Are there specific organizational elements that require unique interactions with the greater organization (such as emergency support functions <ESFs>)?  Look through your jurisdiction’s EOC Standard Operating Procedures/Guidelines (you do have one, right?) to help you identify some of these needs.

Second, identify how to address these training needs.  ICS organization and the planning process are covered in the ICS-300 course, so that will meet some of your needs.  Unfortunately, since so many of the other needs are unique to your jurisdiction, you will have to build custom training to meet these needs.  Yes, FEMA does have available a course called EOC Management and Operations (IS/G – 775).  While some material in this course may or may help meet your training needs, chances are the course in its entirety will not.  First, it dedicates time discussing ideal facilities for an EOC (not really necessary if you already have such a facility), and second, while it provides an outline for general EOC operations it still won’t address all of your specific needs, although course materials can be used as a resource to inform your instructional design.

Third, build staying power into your training.  Much of what is learned is quickly forgotten, especially when people don’t practice it often.  There are a few strategies to combat this knowledge loss… 1) offer refresher training, 2) conduct regular exercises, 3) create job aids.  ICS is big on job aids – that’s very simply what the ICS forms are.  There are a multitude of additional job aids that you can create for your EOC.  Practically every position and process can have checklists and flow charts which help remind staff of what they need to do and in what order to do it in.

This can all be a lot of work, but it will pay off next time you have to activate your EOC.  Remember, there is always help available.  My consulting firm, Emergency Preparedness Solutions, has a great deal of experience working in a variety of EOCs across the country.  We have developed plans, procedures, job aids, training, and exercises unique to each EOC.  We can help you!  Check out our website at www.epsllc.biz or contact us at consultants@epsllc.biz.  Be Proactive, Be Prepared!™

© 2014 – Timothy Riecker