Using PPOST to Address Incident Priorities

In incident management we talk a lot about objectives, strategies, and tactics. Objectives being an identification of what needs to be accomplished; strategies outlining our approaches in how to achieve any given objective; and tactics providing the details of who, what, when, and where along with specific applications to support a specific strategy. With most responses being reasonably routine, many experienced responders go from objectives to tactics in the snap of a synapse. This is based on experience, training, standards, and lessons learned that are so practiced and ingrained in what we do, it’s practically an automatic response. But what of more complex incidents which challenge us with anything but the routine?

An extraordinary response often requires us to step back, take a breath, and think things through. The challenges are complex and necessitate that we approach things with deliberate procedure, and certainly documenting our outcomes, if not our entire thought process. While the formula of objectives, strategies, and tactics still inherently works, some are understandably so overwhelmed with what they face, that even developing objectives can seem to be too much in the weeds at the onset. For the solution, I turn to my northern neighbors – Canada.

While I’m not sure who to actually credit with the PPOST acronym, I know it’s most commonly cited in incident management practices, plans, and training in Canada. PPOST stands for:

  • Priorities
  • Problems
  • Objectives
  • Strategies
  • Tactics

Using PPOST in your approach can better help you to focus on what needs to be done. We know from ICS training and other courses that our immediate incident management priorities are:

  • Life safety
  • Incident stabilization
  • Property conservation

While additional priorities can be added later in the timeline of the incident these are the principle three we need to address. These priorities are fairly straightforward and help us to identify and classify our problems, placing them into the buckets of each of these priorities.

When we open our senses to a complex incident, we are often overwhelmed with problems. It can be difficult to figure out where to start brining order to the chaos. Fundamentally, list out every problem you identify. As you identify each problem, figure out which bucket (priority) it belongs in. Particularly at the onset of an incident, if it doesn’t relate to one of these three priorities, it’s not a problem that needs to be addressed (at least right now).

Now take a look at the problems you identified as being life safety issues. These are your first priority to address. It doesn’t mean you can’t also work on the problems identified in other priorities… that of course comes down to the resources you have available, though the second priority should of course be incident stabilization, followed by property conservation.

Even within these priority buckets, there are some problems which will have higher priority. A simple example: It may not be possible to affect a rescue of people until a fire is suppressed. So once we have a priority assigned to each of our problems, we still need to identify those problems which hold the greatest urgency within each of the priority areas.

To tackle the problems, we now develop objectives, strategies, and tactics for each, addressing them in order of priority and urgency.

If you are looking for additional information on PPOST, be sure to make ICS Canada your first stop.

Be smart and stay safe.

© 2020 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC

Properly Leveraging the EOC Safety Officer

One of my Twitter connections tweeted over the weekend about the importance of the Safety Officer in the Emergency Operations Center (EOC) during the pandemic response.  This is absolutely true, but it’s not the only time the EOC Safety Officer should be engaged.  There is a significant role for them in many EOC activations, but they are historically underutilized, often relegated to monitoring for trip hazards in the EOC and making sure that no one hits their head on the desk when they fall asleep on those long wind-down shifts. 

While the Safety Officer in an Incident Command Post has a great deal of work to do, monitoring tactical hazards and implementing mitigative measures, we often think that with the EOC’s hands-off approach to tactics (something else that is also a myth in incident management) that there is little for an EOC Safety Officer to do.  Obviously, the potential of an EOC Safety Officer depends on the specific circumstances of the incident and the scope of support being provided by the EOC, especially if it’s staffed with the proper personnel. 

Remember that the Safety Officer is a member of the Command (or EOC Management) staff, and therefore can have assistants to support technical needs as well as a volume of work.  While ideally we want people trained as Safety Officers (in accordance with the NIMS position-specific curriculum), let’s face it – most of pool of position-trained personnel come from the fire service.  While on the surface there is obviously nothing wrong with that – fireground safety applications are incredibly detailed and require a very specific know-how – we need to leverage people with the proper background based on the incident we are dealing with.  That could be someone with a fire background, but, for example, a public health incident likely requires a Safety Officer (or advising assistant Safety Officer) to have a public health background; just as an emergency bridge replacement likely requires someone with an engineering background to be the Safety Officer. 

Through my experience, I’ve found that occupational health and safety personnel (either OSHA-proper from the US Dept of Labor or State/Local Occupational Health and Safety personnel) are great for this position, and even better if they have the proper ICS training.  On one hand, I’d call them generalists, because you can utilize them for darn near any incident, but calling them generalists almost feels insulting, as their knowledge of laws, regulations, and guidelines is often very extensive, and if they don’t know, they know where to find the information.  They also work well with hazard-specific specialists who can be integrated as assistants.  They can also call upon a small army of other OSHA-types to support field monitoring of safety matters. 

I will mention a word on using ‘regulators’ as Safety Officers.  Some may be reluctant to do so.  Reflecting again on my experience, I’ll say that Federal/State/Local OSHA-types are great to work with in this regard.  They are often willing to be flexible, developing and implementing an incident safety plan that can be phased, with safety personnel initially providing guidance and correction (when appropriate) and enforcing later. 

In looking at the scope of responsibility for an EOC Safety Officer, we do need to consider the scope of responsibility for any Safety Officers working from Incident Command Posts to ensure the work is complimentary, with minimal duplication of effort, but enough overlap for continuity.  The Safety Officers in an ICP will be primarily focused on the operating area of their ICP.  They are less likely to be concerned with safety matters off-site. 

For an ‘intangible’ incident, such as the current pandemic, we are more apt to find EOCs running the show vs incident command posts.  Obviously, this greatly expands the responsibility of the Safety Officer – in a jurisdiction’s primary EOC, as well as the Safety Officers in departmental operations centers (DOCs) – as many tactical operations are truly being managed from the EOC.  Considerations such as Personal Protective Equipment (PPE) and operating guidelines for all areas of operation and all tactics are likely to be coming from the EOC Safety Officer.  If DOCs or other incident management facilities are involved, the Safety Officer of the jurisdiction’s primary EOC may be collaborating with the Safety Officers from these other facilities to ensure a common operating picture in regard to safety, a unified safety plan, and consistent monitoring and enforcement.  A Safety Officer operating in this capacity needs to be comprehensive in their scope, not just looking at the hazards associated with the primary issue (i.e. an infectious disease), but examining all tactics and considerations, ranging from people operating equipment, to emerging weather hazards.

For an incident with more traditional EOC involvement, a Safety Officer still has a full range of responsibilities, though the actual range of these are still dictated by the scope of the incident.  If an EOC is primarily serving as a resource ordering point, the EOC Safety Officer should be communicating with the Safety Officer at the ICP to ensure an understanding of the hazards in general operating area as well as the specific hazards and PPE needs of the application each resource will be assigned to.  The EOC Safety Officer should be ensuring that responding resources are aware of these safety requirements, as well as potential safety concerns while in transit.  The EOC Safety Officer may be providing the ICP Safety Officer with specialized safety support, analysis, and resources, including supplies and equipment (in coordination with EOC Logistics). 

An EOC supporting multiple ICPs (and even coordinating with several DOCs) should have a more involved and proactive Safety Officer, as they need to be coordinating safety matters across each of these incident management structures.  This includes ensuring a common operating picture in regard to safety, a unified safety plan, and consistent monitoring and enforcement.  They are also likely to be involved in working with EOC Logistics to ensure the proper supplies and equipment.  They should be watching for tactical applications or resource movements of each incident management structure to ensure there are no conflicts or impacts in regard to safety. 

An EOC more significantly engaged is likely to be providing mission support (a topic I’ll be writing about in the near future).  In summary, EOC mission support are generally tactical applications which are developed and managed by an EOC to address matters that are beyond the scope of the ICP or those which the Incident Commander can’t presently deal with.  EOC mission support could include things like sheltering, points of distribution, or a family assistance center.  Once up and running, each of these examples should have their own management structure including a Safety Officer to address their specific needs, but the EOC Safety Officer should be heavily involved in the planning and development stages of these missions, as well as coordinating and supporting safety matters to each of them, similar to what has been mentioned previously. 

Lastly, I’ll suggest that an EOC Safety Officer may also be working with third parties, to include non-government organizations, the private sector, and the public.  Depending on the activity of any of these, the EOC Safety Officer should be keeping tabs on what the safety issues are and communicating with these parties.  The role of the EOC Safety Officer could even include public education.  A great example of this was the October 2006 snowstorm in Erie County, NY.  The Safety Officer from the County EOC (staffed by US DOL/OSHA) coordinated several chainsaw safety courses for the public, knowing that despite the number of safety messages distributed via the Public Information Officer, homeowners, who perhaps never used a chainsaw or hadn’t used one in years, would be out in their yards clearing debris from fallen trees.  These courses were incredibly effective and appreciated by the public. 

To be honest, I’m in favor of breaking tradition within EOCs and designating EOC safety matters, such as trip hazards and signage for mopped floors, to those who are managing EOC facility needs (i.e. the Center Support Section if you are using the Incident Support Model).  This assignment more appropriately corresponds with the focus of the Center Support Section and allows the EOC Safety Officer to maintain focus on what’s going on outside the EOC. 

So there is some food for thought on how to properly use an EOC Safety Officer.  Don’t continue to let it be a lame position as so many have in the past.  It has incredible importance when properly utilized and staffed.  I’m interested in hearing about how you have leveraged EOC Safety Officers, or if you are a Safety Officer, what activities you have performed from an EOC. 

Be safe out there. 

© 2020 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC

Responding to Coronavirus & a Second Major Incident

Springtime is practically upon us.  Trees are budding, asparagus is growing (yes, I mentioned asparagus), birds are chirping, and snow is melting.  And it’s raining.  Some people call it spring, others call it the first flood season of the year.  Flooding isn’t the only hazard we face right now.  It’s still early enough for the threat of snow and ice storms, and we’ve already seen tornado activity in the US.  Oh, and by the way, we’re dealing with a pandemic.  EDIT: In the midst of writing this post and also exchanging emails re Coronavirus with a client in Utah, he exclaimed in one of his responses that a 5.7 earthquake had just struck with an epicenter just outside Salt Lake City.  As one of my old bosses used to say, you can’t make this stuff up. 

So often we are used to dealing with one disaster at a time.  Yes, sometimes we get hit with a one-two punch, or other times the same incident, such as a hurricane, persists, but these are typically localized, not a nation-wide concern, much less global.  When our resources are already strained from dealing with Coronavirus, it can be a challenge to respond to another significant incident, especially when there is little mutual aid to be had.  I often think back to an example I use back from my days in EMS, and that’s the multi-trauma patient.  Most EMS instructors, following the standard curriculum, will teach you how to treat lacerations, fractures, burns, and the like.  But rarely do we learn about how to deal with those things when they all happen at once. I remember back when I was a young pup EMT, my first multi-trauma patient was a victim of a motor vehicle accident (as it probably was for most EMTs).  I recall having a brief moment of panic because that’s not what we were taught to handle.  My brain quickly reset, and I went back to my ABCs, assessing and stabilizing the patient in priority order. 

Another personal example I have is the crash of American Airlines Flight 587 on November 12, 2001 – two months and one day after 9/11.  The plane crashed in Queens borough of New York City as the result of a critical structural failure.  260 souls on board, plus 5 on the ground died.  This occurred in the midst of the response to one of the most impactful disasters in US history.  In a way we ‘lucked out’ that the incident occurred in New York City.  On a normal day, the City of New York can leverage more resources in a response than some US states and even nations.  November 2001 was anything but ‘normal’ with a massive amount of additional resources still rotating into the City to support 9/11 activities.  While at this point, two months following 9/11, things were reasonably stable in and around ground zero, the crash of Flight 587 still required a significant change in operations.  From my recollection, in the State EOC in Albany, we actually split some of our staff for a brief period of time (within the same chain of command), with some staying focused on 9/11 activity while others were focused on the crash.  We didn’t create a new organization, but there were people in Operations and Planning committed specifically to monitoring and supporting the new incident.  Like a Venn diagram, there were some different needs in the initial response with some overlapping needs between the two incidents.  As the two circles moved closer together, creating more overlap, we re-integrated our staff to track and support both incidents collectively.  I recall the reintegration occurring after only a few operational periods. 

So what to do when an incident occurs during our current pandemic?  There are a few concerns, some related to incident management, others related to our tactical responses and humanitarian needs.  While our general response times are likely to be improved, many resources are already strained.  We are likely in an operational continuity mode already, currently working with or ready to work with fewer staff as Coronavirus impacts our people and their families.  It’s incredibly important to be rotating your emergency staff, keeping people as rested as possible.  We can also leverage the lead agency status that is presently at play in most jurisdictions, with public health having the lead, and emergency management agencies and others supporting them.  If something occurs other than a second public health event, the emergency management agency may be able to pivot to be the lead coordinating agency for the new incident while still supporting public health.  (Of course, I say this fully recognizing that the vast majority of emergency management offices are one-person shops.)  If you are able to split off some staff within your Coronavirus organization (really speaking in terms of your EOC) similar to my Flight 587 example, that may be a workable strategy.  Another strategy could be the reverse of that, where most of your organization is focused on the new incident, since that is in its critical early stages, leaving a few other staff to continue supporting Coronavirus needs.  I generally wouldn’t consider creating parallel organizations as most jurisdictions simply don’t have the capacity for that, plus EOCs are intended to be able to support multiple incidents.  The splitting off of staff is generally only for the early response to ensure that we are gathering information and providing the support that is needed.  We can still leverage the organization as a whole (you probably don’t have a need to dedicate anyone in Logistics or Finance specifically to the new incident, though expenses should be tracked separately), and the chain of command still remains intact.  Your planning process, likewise, should accommodate both incidents. Depending on the scope of the new incident, certain subject matter experts may need to be brought in to address specific response and disaster recovery needs for the new incident.  Overall, flexibility is key.  I’ll also say that all this can be done while still adhering to organization tenants of ICS (even if your EOC doesn’t purely use ICS). 

From a more tactical perspective, the main concerns are staffing and safety.  Staffing, as mentioned before, may be a challenge as we progress through the most infectious stages of this pandemic.  Your continuity plans must absolutely address this.  I mention safety not only in regard to whatever hazards the new incident brings about, but also the continued safety measures we need to maintain for Coronavirus.  The most prominent of these safety measures are those involving an expanded circle of exposures for responders and the public; dealing with large numbers of victims, perhaps displaced from a building who may need shelter and other care.  Mass care is a big concern. Certainly, for smaller numbers of victims, hotels may be more appropriate than a shelter, but we know that we need to prepare for a credible worst-case scenario.  How?

  • We must ensure that our responders, VOAD, and social services agencies are prepared to address needs. 
  • With so many facilities being closed, we need to ensure that we still have access to identified shelters and the people and resources necessary to support them. 
  • Many of the VOAD organizations and social services agencies may have limited operations due to Coronavirus, with staff working from home.  Do they have the resources and equipment at-hand to support a response or do they need to retrieve these from their offices? 
  • Do they have an ability to recall staff? 
  • Is there any change in their capability and capacity? 
  • Are the supply chains we use for shelter food and supplies still viable?    
  • What needs to be done to support social distancing and limit exposure within a shelter environment?
  • How will you address isolation needs for those who may have been exposed or are symptomatic?
  • Are their activation and notification procedures impacted by Coronavirus? 

Now is the time to convene your VOAD and social services agencies (by tele/video conference, of course) to answer these questions and ensure that a written plan (an amendment to your standing sheltering/human needs plan) is developed and circulated for common understanding. 

Regardless of the circumstances, we cannot allow ourselves to become so focused on Coronavirus that we forsake the challenges we would face should another major incident strike, the changes to our capability and capacity, and the continued preparedness we need to maintain.  Remember, preparedness doesn’t stop simply because we are in the midst of a disaster. I’ll also mention that I’m certainly not the first to consider this issue.  Over the past few days, several people, including Ralph Fisk and Dr. Samantha Montano have posted their concerns about our ability to respond to other disasters in the midst of the Coronavirus response and impacts.  It’s something that shouldn’t just be on our minds, it’s something we need to be prepared for.  Developing a contingency plan for your EOC operations and other related support is something that should absolutely be taking place sooner rather than later.

I’m sure I didn’t cover all possibilities or considerations on this topic (I rarely do on any topic), but my intent is to get your mental juices flowing and to plant some ideas.  Please be sure to share any ideas or considerations you have in your contingency preparedness. 

Be smart, stay safe, stay healthy, and be good to each other. 

© 2020 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC

Improving the HSEEP Templates

For years it has bothered me that the templates provided for the Homeland Security Exercise and Evaluation Program (HSEEP) are lacking.  The way the documents are formatted and the lack of some important content areas simply don’t do us any favors.  These templates go back to the origination of HSEEP in the early 2000s and they have seen little change since then.  It gives me concern that the people who developed these have struggled with concepts of document structuring and don’t understand the utility of these documents. 

I firmly believe that the documents we use in exercise design, conduct, and evaluation should be standardized.  Many of the benefits of standardization that we (should) practice in the Incident Command System (ICS) certainly apply to the world of exercises, especially when we have a variety of different people involved in each of these key phases of exercises and entering at different times.  Much like an incident, some people develop documents while others are users.  Both should count on a measure of standardization so they don’t have to figure out what they are looking at and how to navigate it before actually diving into the content.  That doesn’t mean, however, that standards can’t evolve to increase utility and function. 

I’ve written in the past about the dangers of templates.  While they are great guides and reminders of certain information that is needed and give us an established, consistent format in which to organize it, I still see too many people not applying some thinking to templates.  They get lost in plugging their information into the highlighted text areas and lose all sense of practicality about why the document is being developed, who the target audience for the document is, and the information they need to convey. 

Some of my bigger gripes…

  • Larger documents, such as ExPlans, SitMans, Controller/Evaluator Handbooks, and After-Action Reports MUST have a table of contents.  These documents can get lengthy and a TOC simply saves time in finding the section you are looking for. 
  • Some exercises are complex and nuanced.  As such, key documents such as ExPlans, SitMans, and Controller/Evaluation Handbooks must have designated space for identifying and explaining those situations.  This could be matters of multiple exercise sites and site-specific information such as different scopes of play for those sites, limited scopes of participation for some agencies, statements on the flow and execution of the exercise, and others.
  • Recognize that the first section of an EEG (Objective, Core Capability, Capability Target, Critical Tasks, and sources) is the only beneficial part of that document.  The next section for ‘observation notes’ is crap.  Evaluators should be writing up observation statements, an analysis of each observation, and recommendations associated with each observation.  The information provided by evaluators should be easily moved into the AAR.  The EEG simply does not facilitate capturing this information or transmitting it to whomever is writing the AAR. 
  • The AAR template, specifically, is riddled with issues. The structure of the document and hierarchy of headings is horrible.  The template only calls for documenting observations associated with observed strengths.  That doesn’t fly with me.  There should similarly be an analysis of each observed strength, as well as recommendations.  Yes, strengths can still be improved upon, or at least sustained.  Big missed opportunity to not include recommendations for strengths.  Further, the narrative space for areas of improvement don’t include space for recommendations.  I think a narrative of corrective actions is incredibly important, especially given the very limited space in the improvement plan; plus the improvement plan is simply intended to be an implementation tool of the AAR, so if recommendations aren’t included in the body of the AAR, a lot is missing for those who want to take a deeper dive and see specifically what recommendations correlate to which observations and with an analysis to support them. 

Fortunately, strict adherence to the HSEEP templates is not required, so some people do make modifications to accommodate greater function.  So long as the intent of each document and general organization remains the same, I applaud the effort.  We can achieve better execution while also staying reasonably close to the standardization of the templates.  But why settle for sub-par templates?  I’m hopeful that FEMA’s National Exercise Division will soon take a look at these valuable documents and obtain insight from benchmark practitioners on how to improve them.  Fundamentally, these are good templates and they have helped further standardization and quality implementation of exercises across the nation.  We should never get so comfortable, though, as to let tools such as these become stagnant, as obsolesce is a regular concern. 

I’m interested in hearing what you have done to increase the value and utility of HSEEP templates.  How would you improve these?  What are your pet peeves? 

© 2020 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®

We’re Off on the Road to Central City

FEMA Training Bulletin number 1580 announced the publication of the Emergency Management Institute’s (EMI) Online Exercise System Simulation Document (ESSD).  The ESSD, quoted from the website is ‘a compilation of information and resources that would typically be available in any community as they respond to and manage an emergency or disaster in a local community.’  The purpose of the ESSD, essentially, is to provide all the information needed for a fictional jurisdiction for use in exercises.  If you’ve taken some classes at EMI, the HSEEP course, ICS courses, or other programs from FEMA/EMI, you are probably already familiar with the magical place called Central City.

Central City, Liberty County, and other jurisdictions that are part of this fictional area have been in use for decades.  Much of the information published in the ESSD has been available at one point or another, developed to serve the needs of different scenario-based training.  The ESSD packages it all conveniently in one place.

While in some training programs, there is direct benefit to developing a scenario grounded in a real location, we often have course participants who come from different areas.  While you can still certainly develop a scenario in a real location for use in a class like this, the use of Central City (et al) can be an ideal option.  With all the resources and supporting information provided in the ESSD, you likely have everything you need.

Speaking of all that material, what’s in the ESSD?  A sampling:

  • Community profiles
  • Hazard Vulnerability Analysis
  • Laws and Ordinances
  • Emergency Plans
  • Resource and Capability Lists
  • Critical Infrastructure

Having used these jurisdictions and much of this material in courses in the past, course managers do need to expect that it will take time for participants to find some information they are looking for.  In real life, they may or may not be familiar with certain information sets.  The ESSD system was developed to be searchable, which is a huge help, though it’s always good to have one or two paper copies as back ups (note… depending on what you are providing, that may be hundreds of pages).  Since many participants are bringing tablets and laptops to class, all that’s needed is internet service to access all this great information.

I do have a couple of noted observations for improvement.

  1. Having just mentioned printing, I’ll state that first. There doesn’t seem to be a way from within the site to print the material or export it to a PDF.  Yes, you can print from your browser, but formatting is drastically thrown off.
  2. The maps are still horrible. While most of the maps are better than what we’ve had in many of the training materials they have been included in, they are still not high def or zoomable. In fact, many of them are still blurry on my computer screen.  For detailed areas, such as the urban Central City, users (and even scenario designers) may have a need to get much closer to the information.  The Central City map itself, is still difficult to read, especially the myriad of small icons strewn throughout the map.  I would have hoped that re-working this map would have been a priority in the ESSD, as it’s a regular complaint in the classes it’s used in.

Another resource I’ve used in the past (2007 or 2008?) was Zenith City, which was provided by the EPA.  Similar to the FEMA ESSD, the EPA provided a wide array of information for the fictional Zenith City and surrounding jurisdictions.  While the EPA still has a significant exercise program (if you haven’t checked out their stuff, you should), I don’t know whatever happened to the Zenith City information… it’s no where to be found.  (Note: if anyone happens to have the Zenith City material, please let me know!  I’d love to add it back into my library of resources!)

I’m thrilled that FEMA pulled all the Central City material together in this collection, and even added new information.  Central City has always provided us with a great location to unleash hell on, and allow responders and emergency managers to solve so many problems.  I’m just glad I don’t live there!

© 2020 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC

ICS Training Sucks: A Revival

It’s sad to say that in the past four and a half years of stumping for changes in ICS training, we have seen little progress.  I was recently sent a response org chart developed by an agency that completely tore apart ICS and rebuilt it in a fundamentally different image.  ICS is a standard.  It shouldn’t be changed.  Once you change it, especially at fundamental levels, you no longer have a standard.  It has innate flexibility, but those are applied without changing the fundamentals.  I vented some of my frustration about this last night on Twitter, to a mix of celebration and naysayers, as expected.  Some of those naysayers think the system simply doesn’t work. Others think the system simply can’t accommodate their type of agency.

(note that I’m using the word ‘agency’ here to mean any type of government, non-government, or private sector organization.  I decided to use it since I’m also heavily using the term ‘organization’ in regard to the structure we apply for a response)

So let’s back up a bit.  Why is this happening?  It starts with people having some knowledge of ICS and, with good intentions, wanting to adapt it to their agency and their circumstances.  But there is simply no reason to do any adaptation.  The functions outlined in ICS are all you need in a field-level response.  I’ve heard all the excuses – “We need to make it work for us.”  “FEMA needs to build an ICS for our type of agency.”  “It’s not you, it’s me.” I’ve worked with a lot of stakeholders across a lot of sectors across the whole country, and I have yet to find a field-level response that I can’t organize without violating the fundamentals of ICS.

I’m sure I’ve said this before, but adhering to the standard is important because if we don’t adhere to a standard, we are out of the loop.  If enough people don’t adhere to a standard, it’s no longer a standard.  Either way, the benefits of having a standard are crumpled up and thrown away.

One problem is that a lot of entities, particularly large agencies with multiple components, like to ensure that every function or department within their static structure is represented in an ICS model.  This isn’t what ICS is built for.  If you are seeking specific representation, you can assign agency representatives to the ICP or the EOC, or use a department-based EOC model, but the foundational ICS structure itself isn’t intended to reflect your static organization.  You have an animal control officer.  Do they need to be represented in your pre-planned ICS org chart?  No, they are brought in as a resource if needed, likely in Operations.  You have an IT department.  Do they need to be represented in your pre-planned ICS org chart?  Not as a department. But their capability is identified, likely for assignment within Logistics.  It’s not about recreating ICS to fit your static organization.  It’s about knowing the capabilities of your static organization and applying them within the established ICS structure when and how they are needed. 

Let’s put this out there… ICS isn’t just for you, it’s for everyone.  What I mean is that the greatest benefit of ICS (the prime reason it was actually devised) is for multi-agency operations.  In a local incident of any significance, your agency is likely to be part of a multi-agency response.  Depending on the type of incident, scope, location, and other factors, certain positions will be staffed with personnel selected from the agencies with primary responsibility and, hopefully, with qualified staff.  So that carefully crafted org chart you have developed for your agency’s response is largely irrelevant in a multi-agency operation.  Yes, your agency certainly should have a go-to model for single-agency responses, but consider that a single-agency response probably isn’t going to need a full-blown org chart.

There is a difference, though… and that’s for EOCs, or more specifically departmental emergency operations centers.  These are, by definition, not multi-agency, and established to support your own agency’s needs for deployment, sustainment, internal coordination, and matters that may not be addressed at the field-level.  EOCs have a variety of organizational models available to them, which don’t necessarily need to be ICS.   A problem I often see is agencies trying to accomplish everything in one org chart.  They are trying to fit executive level positions in with field response.  Stop.  Take a breath and figure out what you are trying to accomplish.  It’s OK (and perhaps necessary) for your agency to have two organizational models to accomplish what you need, depending, of course, on your agency’s role, responsibilities, and capabilities.  You may need a field-level organization that addresses a tactical response (this is ICS-based) and an EOC organization that supports that response and the needs of your agency as a whole in regard to the incident (again, lots of options for the EOC organization).  Also consider, depending on your agency, that a policy group may be necessary to guide things.  A policy group is non-operational and they essentially exist to make the broad-reaching decisions on behalf of the organization.

Why are we seeing such extensive mis-applications of ICS?  First, people still don’t understand ICS.  Second, they aren’t truly considering the needs of their agencies.  The irony is that many of the people doing this DO think they understand ICS and that they are making changes to it to better serve the needs of their agencies.  So… we’re still maintaining that ICS Training Sucks.  Do I have a total solution to that problem?  No. But in the articles you find in that link, I certainly have some ideas.  I’ve also found a great many kindred spirits in this whole crusade that agree with the need for change in how we train people in ICS.

What I do know is that the solution isn’t as straight forward as we would like it to be.  Considerations:

First, we are considerably tainted by our knowledge of current and past ICS curricula.  When talking with people about how to fix ICS training, I have to regularly remind myself to push that knowledge aside and look at the problem with fresh eyes.  Lessons learned aside; we can’t move forward when we are still planting ourselves in what is in use now.

Second, we need to consider that there may not be a single solution that fits all needs.  I still think we may need a curriculum structure similar to that used for HazMat training, which addresses the needs of different user groups (i.e. Awareness, Operations, Technician, Planner, Commander).

Third, we need to actually teach people how to apply ICS.  At present, with only a bit of exception, true application of ICS isn’t deliberately instructed until someone takes position-specific and incident management team training.  This in no way meets the needs of most agencies, many of which are volunteer, and have limited availability to go away for several weeks to get the training they need.

Fourth, recognize that if you aren’t using ICS regularly (and I mean at a large scale), your knowledge and skill degrades.  Refresher training should be required and scenario-based learning should be incorporated across the curriculum.

Fifth, stop trying to re-develop ICS.  Trust me, all the needed capabilities of your agency for a field-level response fit within an ICS org chart.  It’s not about your static organization, it’s about capabilities.  Identify and assign capabilities.

I love the continued dialog and attention this topic gets.  The only way we will see positive change is by continuing that dialog.  Please share these blogs and your ideas with colleagues.  Let’s keep spreading this and striving for change.

© 2020 Timothy Riecker, CEPD

Emergency Preparedness Solutions, LLC

~~

In memoriam: I humbly dedicate this post to a friend and colleague who recently lost a battle with cancer.  Phil Politano is known by many for his good nature, his gregarious laugh, and his incredible knowledge as a Public Information Officer.  I’ve known Phil since about 2002, and had worked with him on incidents, taught classes with him, and learned a lot from him.  Phil eventually left Central NY and moved his family a bit south, taking a job with FEMA’s Emergency Management Institute.  There, his talents were applied to their greatest extent.  He reshaped PIO training, spread that gospel to people from all around the world, and supported large scale responses with his knowledge, skills, and abilities.  He was a master in his craft and shared his mastery with anyone who wanted to learn.  He was an incredible practitioner, a great friend, and a wonderful person.  He made us all better simply by knowing him.   He is missed by so many.  Rest well.

 

 

An Updated Community Lifelines Toolkit and Relationships to Incident Management

Earlier this year, FEMA released guidance on the Community Lifelines.  I wrote a piece in the spring about integrating the concept into our preparedness and response activities.  Last month, FEMA issued updated guidance for Community Lifeline Implementation through Toolkit 2.0.  In this update, FEMA cites some lessons learned in actually applying the Lifeline concept in multiple exercises across the nation, as well as from feedback received by stakeholders. Based on these lessons learned and feedback, they have made some adjustments to their toolkit to reflect how they understand, prioritize, and communicate incident impacts; the structure and format for decision-making support products. And planning for these impacts and stabilization prior to and during incidents.  They have also made some changes based upon the updated National Response Framework.  The documents associated with the updated Community Lifelines all seem to reflect an inclusion in the efforts of the National Response Framework.  It’s great to see FEMA actually tying various efforts together and seeking to provide grounded guidance on application of concepts mentioned in doctrine-level documents.

The biggest addition to the Community Lifelines update is the inclusion of the FEMA Incident Stabilization Guide.  The ‘operational draft’ is intended to serve as a reference to FEMA staff and a resource to state, local, and tribal governments on how “FEMA approaches and conducts response operations”.  It’s a 77-page document the obviously leans heavily into the Community Lifelines as a standard for assessing the impacts to critical infrastructure and progress toward restoration, not only in response, but also into recovery operations.  It even reflects on bolstering Community Lifelines in resilience efforts, and ties in the THIRA and capability analysis efforts that states, UASIs, and other governments conduct.  I’m not sure the document is really a review of how FEMA conducts operations, as they say, but it does review the ideology of a portion of those operations.  Overall, there is some very useful information and references contained in the document, but this brings me to a couple of important thoughts:

  1. The utility of this document, as with the entire Community Lifelines concept, at the state and local level is only realized through integration of these concepts at the state and local levels.
  2. We finally have guidance on what ‘incident stabilization’ really entails.

To address the first item… In my first piece on Community Lifelines, I had already mentioned that if states or communities are interested in adopting the concept of Community Lifelines, that all starts with planning.  An important early step of planning is conducting assessments, and the most pertinent assessment relative to this initiative would be to identify and catalog the lifelines in your community.  From there the assessment furthers to examine their present condition, vulnerabilities, and align standards for determining their operational condition aligned with the Community Lifelines guidelines.  I would also suggest identifying resiliency efforts (hopefully these are already identified in your hazard mitigation plan) which can help prevent damages or limit impacts.  As part of your response and short-term recovery lexicon, procedures should be developed to outline how lifeline assessments will be performed, when, and by who, as well as where that information will be collected during an incident.

As for my second item, the concept of incident stabilization has an interesting intersection with a meeting I was invited to last week.  I was afforded the opportunity to provide input to an ICS curriculum update (not in the US – more on this at a later time), and as part of this we discussed the standard three incident priorities (Life Safety, Incident Stabilization, and Property Conservation).  We identified in our discussions that incident stabilization is incredibly broad and can ultimately mean different things to different communities, even though the fundamental premise of it is to prevent further impacts.  This Incident Stabilization Guide is focused exclusively on that topic.  In our endeavor to make ICS training better, more grounded, less conceptual, and more applicable; there is a great deal of foundational information that could be distilled from this new document for inclusion in ICS training to discuss HOW we actually accomplish incident stabilization instead of making a one-off mention of it.

Going a bit into my continued crusade against the current state of ICS training… I acknowledge that any inclusion of this subject matter in ICS training would still be generally brief, and really more of a framework, as implementation still needs to be grounded in community-level plans, but this document is a great resource.  This also underscores that “learning ICS” isn’t just about taking classes.  It’s about being a professional and studying up on how to be a more effective incident manager.  ICS is simply a tool we use to organize our response… ICS is NOT inclusive of incident management.  Not only are we teaching ICS poorly, we are barely teaching incident management.

While I’ve been away for a while working on some large client projects, I’m looking forward to ending the year with a bang, and getting in a few more posts.  It’s great that in my travels and interactions with colleagues, they regularly mention my articles, which often bring about some great discussion.  I’m always interested in hearing the thoughts of other professionals on these topics.

© 2019 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®