Tag Incident Command System

Five Domains of Incident Management

Tim Riecker, The Contrarian Emergency Manager 3 Comments

Earlier this summer, RAND, under contract to CDC as part of a five-year project related to examining and assessing incident management practices in public health, developed and released the Incident Management Measurement Toolkit. Overall, I think the tool developed is a solid effort toward standardizing the evaluation of incident management. The tool guides a depth of examination into incident management practices. It can be a bit daunting at a glance, but the methodology of evaluation is generally what I’ve been practicing over the past several years for developing incident and event AARs. I’d also suggest that it’s scalable in application.

I feel it’s important to note that incident management teams involved in non-public health applications were also engaged in the research. The outcomes of the project and the inclusion of non-public health incident management practices in the research indicate to me that this tool can be applied broadly and not limited to public health applications.

Serving as a foundation for the assessment tool and methodology are five Domains of Incident Management that the project team identified. Provided with key activities, these include:

  1. Situational Awareness and Information Sharing – Perception and characterization of incident-related information to identify response needs.
  2. Incident Action and Implementation Planning – Ongoing articulation and communication of decisions in coherent incident action plans.
  3. Resource Management and Mobilization – Deployment of human, physical, and other resources to match ongoing situational awareness, identification of roles, and relevant decisions.
  4. Coordination and Collaboration – Engagement and cooperation between different stakeholders, teams, and departments in managing the incident.
  5. Feedback and Continuous Quality Improvement – The need for ongoing evaluation and refinement of incident management processes.

In consideration of these domains, I think the activities inherent within them are fairly agnostic of the type of incident management system (i.e. ICS) used. I also think these same domains can be applied for recovery operations, again, regardless of the system or organization being utilized; as well as the principal practice at work (public health, emergency management, fire service, law enforcement, etc.).

I’ve been intending to write about these domains for a while, but each time I considered them, something stood out to me as being a bit askew. I finally realized that these really aren’t domains that encompass all of incident management. Rather, these domains are better associated with an incident management system, such as the Incident Command System (ICS). The first three domains are very clearly applied directly to an incident management system, and the fourth is the general concept of multiagency coordination, which is a common concept of incident management systems. The last domain is simply quality management which is certainly integral across various incident management systems.

While I don’t believe my view undermines the tool’s value, it highlights the need for a clearer understanding of its limitations. An incident management system, like ICS, is just one part of incident management and doesn’t cover all related activities. Some tasks in incident management, such as setting priorities, decision-making, troubleshooting, and dealing with political and social issues, are often not directly related to the tactical management systems we use. Additionally, many important aspects fall within leadership that aren’t covered by the NIMS doctrine or the Planning P. Although organizing resources is a central part of incident management, there are many other activities not addressed in a tactical response that may influence tactical applications but are not part of a defined incident management system. While one could argue these activities fit into the five identified domains, I feel this analysis doesn’t provide a complete picture of a complex response. More information would be needed.

That said, I really like this toolkit. I think it provides a structured mechanism for evaluating common practices of incident management systems, which itself can provide a foundation for a more comprehensive assessment of incident management. That comprehensive assessment, beyond the incident management system, is also more anecdotal and often requires persons experienced in asking the right questions and clarifying perspectives and opinions – things that ultimately can’t be done (or at least done easily) with an assessment tool.

So regardless of what the nature of your incident is, consider using the Incident Management Measurement Toolkit as part of your AAR process.

What are your thoughts on the RAND tool? Have you used it? What do you think of the five domains they have identified?

©2024 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®

ICS: Problems and Perceptions

Tim Riecker, The Contrarian Emergency Manager 4 Comments

Oddly enough, I’ve recently seen a spate of LinkedIn posts espousing the benefits of the Incident Command System (ICS). Those who have been reading my material for a while know that I’m a big proponent of ICS, though I am highly critical of the sub-par curriculum that we have been using for decades to teach ICS. The outcome is an often poorly understood and implemented system resulting in limited effectiveness.

Yes, ICS is a great tool, if implemented properly. Yet most implementations I see aren’t properly conducted. To further muddy these waters, I see emergency plans everywhere that commit our responders and officials to using ICS – this is, after all, part of the National Incident Management System (NIMS) requirement that many have – yet they don’t use it.

So why isn’t ICS being used properly or even at all? Let’s start with plans. Plans get written and put up on a proverbial shelf – physical or digital. They are often not shared with the stakeholders who should have access to them. Even less frequently are personnel trained in their actual roles as identified and defined in plans. Some of those roles are within the scope of ICS while some are not. The bottom line is that many personnel, at best, are only vaguely familiar with what they should be doing in accordance with plans. So, when an incident occurs, most people don’t think to reference the plan, and they flop around like a fish out of water trying to figure out what to do. They make things up. Sure, they often try their best, assessing what’s going on and finding gaps to fill, but without a structured system in place and in the absence (or lack of referencing) of the guidance that a quality plan should offer, efficiency and effectiveness are severely decreased, and some gaps aren’t even recognized or anticipated.

Next, let’s talk about ICS training. Again, those who have been reading my work for a while have at least some familiarity with my criticism of ICS training. To be blunt, it sucks. Not only does the content of courses not even align with course objectives, the curriculum overall doesn’t teach us enough of HOW to actually use ICS. My opinion: We need to burn the current curriculum to the ground and start over. Course updates aren’t enough. Full rewrites, a complete reimagining of the curriculum and what we want to accomplish with it, needs to take place.

Bad curriculum aside… For some reason people think that ICS training will solve all their problems. Why? One reason I believe is that we’ve oversold it. Part of that is most certainly due to NIMS requirements. Not that I think the requirements, conceptually, are a bad thing, but I think they cause people to think that if it’s the standard that we are all required to learn, it MUST be THE thing that we need to successfully manage the incident. I see people proudly boasting that they’ve completed ICS300 or ICS400. OK, that’s great… but what can you actually do with that? You’ve learned about the system, but not so much of how to actually use it. Further, beyond the truth that ICS training sucks, it’s also not enough to manage an incident. ICS is a tool of incident management. It’s just one component of incident management, NOT the entirety of incident management. Yes, we need to teach people how to use ICS, but we also need to teach the other aspects of incident management.

We also don’t use ICS enough. ICS is a contingency system. It’s not something we generally use every day, at least to a reasonably full extent. Even our first responders only use elements of ICS on a regular basis. While I don’t expect everyone to be well practiced in the nuances and specific applications of ICS, we still need more practice at using more of the system. It’s not the smaller incidents where our failure to properly implement ICS is the concern – it’s the larger incidents. It’s easy to be given a scenario and to draw out on paper what the ICS org chart should look like to manage the scenario. It’s a completely different thing to have the confidence and ego in check to make the call for additional resources – not the tactical ones – but for people to serve across a number of ICS positions. Responders tend to have a lot of reluctance to do so. Add to that the fact that most jurisdictions simply don’t have personnel even remotely qualified to serve in most of those positions. So not only are we lacking the experience in using ICS on larger incidents, we also don’t have experience ‘ramping up’ the organization for a large response. An increase in exercises, of course, is the easy answer, but exercises require time, money, and effort to implement.

One last thing I’ll mention on this topic is about perspective. One of the posts I read recently on LinkedIn espoused all the things that ICS did. While I understand the intent of their statements, the truth is that ICS does nothing. ICS is nothing more than a system on paper. It takes people to implement it. ICS doesn’t do things; PEOPLE do these things. The use of ICS to provide structure and processes to the chaos, if properly done, can reap benefits. I think that statements claiming all the things that ICS can do for us, without inserting the critical human factor into the statement, lends to the myth of ICS being our savior. It’s not. It must be implemented – properly – by people to even stand a chance.

Bottom line: we’re not there yet when it comes to incident management, including ICS. I dare say too many people are treating it as a hobby, not a profession. We have a standard, now let’s train people on it PROPERLY and practice it regularly.

©2024 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®

Federal Coordination of All-Hazard Incident Management Teams

Tim Riecker, The Contrarian Emergency Manager 9 Comments

A few months ago the FEMA administration decided that the US Fire Administration (USFA) would discontinue their management of the All-Hazards Incident Management Team (AHIMT) program, which they have developed and managed for years. While I was never in favor of the USFA managing the program (AHIMTs are not fire-service specific), the staff assigned to the program did an admirable job of growing the AHIMT concept to what we have today.

The All-Hazards Incident Management Team Association (AHIMTA), which has been a vocal proponent of the development of AHIMTs, has thankfully been working to make people aware of this change. As part of their advocacy, they also wrote to FEMA Administrator Deanne Criswell regarding their concerns with the dissolution of this formal program. Administrator Criswell responded to AHIMTA, indicating that despite successes, the AHIMT program has “not been able to establish a sustainable or robust AHIMT program with long-term viability.” She did indicate that the USFA will continue providing related training to state, local, tribal, and territorial (SLTT) partners (though she specified that USFA training efforts will apply to fire and EMS agencies) and that she has directed the USFA to collaborate with the FEMA Field Operations Directorate to continue support to AHIMTs.

This change and some of the wording in the Administrator’s response is obviously very concerning for the future of AHIMTs. I first question the Administrator’s statement about the AHIMT program not being sustainable long-term. Not that I’m doubting her, but I’m curious as to what measures of sustainability she is referring. I’m guessing most of the issue is that of funding, along with this never having fully been part of the USFA’s mission. Everything really does boil down to funding, but how much funding can a small program office really need? I’m also concerned about the USFA continuing with the AHIMT training mission (as I always have been), and even more so with the Administrator’s specification of fire and EMS (only?) being supported. While I have no issue at all with the USFA, and think they have done a great job with IMT and related training, their primary focus on fire and EMS (even absent the Administrator’s statement) can be a barrier (real or perceived) to other disciplines obtaining or even being aware of the training.

I firmly believe that a federal-level program office to continue managing, promoting, and administering a national AHIMT program is necessary. I do not think it should be in the USFA, however, as it has been, as their mission is not comprehensive in nature. It’s a program that should be managed properly within FEMA, though not by the FEMA Field Operations Directorate, which is primarily charged with FEMA’s own field operations. While this does include FEMA’s own IMATs, their focus is internal and with a very different purpose. My biggest inclination is for the program to be placed within the NIMS Integration Center, which already does a great deal of work that intersects with AHIMTs. On the training side of things, I’d like to see AHIMT training moved to FEMA’s Emergency Management Institute (EMI), to emphasize the inclusion of SLTT participants regardless of discipline. Incident management, as a comprehensive response function, is inclusive of all hazards and all disciplines and practices, just like emergency management.

The dissolution of the AHIMT program at the federal level makes no sense to me at all. The absence of a program office not only degrades the importance of incident management teams, but of incident management as a concept and a skillset – which I think also needs some vision beyond the current IMT model to support local incident management capabilities. I’m appreciative of the AHIMTA and their advocacy for a federal AHIMT program office, and I’m hopeful that they will be able to convince FEMA of this need and that a program office is properly restored.

© 2022 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®

NIMS Change – Information and Communications Technology Branch

Tim Riecker, The Contrarian Emergency Manager 4 Comments

FEMA recently released a draft for the National Incident Management System (NIMS) Information and Communications Technology (ICT) guidance, providing a framework for incorporating ICT into the Incident Command System (ICS). The draft guidance in many ways formalizes many of the functional changes ICS practitioners have been incorporating for quite a while.

Essentially, the guidance creates an ICT branch within the Logistics Section. That branch can include the traditional Communications Unit as well as an Information Technology (IT) Service Unit. They also make allowances for a Cybersecurity Unit to be included the branch – not as an operational element for a cyber incident, but largely in a network security capacity. The creation of an ICT branch is also recommended for emergency operations centers (EOCs), regardless of the organizational model followed.

The IT Service Unit includes staffing for a leader, support specialists, and a help desk function, while the Cybersecurity Unit includes staffing for a leader, a cybersecurity planner, a cybersecurity coordinator, and a cyber support specialist. The position descriptions and associated task books are already identified pending final approvals and publication of this guidance, with the Cybersecurity and Infrastructure Security Agency (CISA) seemingly ready to support training needs for many of the new positions.

I’m fully in support of this change. FEMA is accepting feedback through October 20, 2022, with instructions available on the website provided previous.

Not being a communications or IT specialist myself, I’m interested in the perspectives of others on this.

© 2022 Tim Riecker, CEDP

Emergency Preparedness Solutions, LLC®

EOCs and IMTs

Tim Riecker, The Contrarian Emergency Manager 3 Comments

The world of incident management is foggy at best. There are rules, sometimes. There is some valuable training, but it doesn’t necessarily apply to all circumstances or environments. There are national models, a few of them in fact, which makes them models, not standards. Incident management is not as straight forward as some may think. Sure, on Type 4 and 5 incidents the management of the incident is largely taking place from an incident command post. As you add more complexity, however, you add more layers of incident management. Perhaps multiple command posts (a practical truth, regardless of the ‘book answer’), departmental operations centers, emergency operations centers at various levels of government, and an entire alphabet soup of federal operations centers at the regional and national levels with varying (and sometimes overlapping) focus. Add in operational facilities, such as shelters, warehouses, isolation and quarantine facilities, etc. and you have even more complexity. Trying to map out these incident management entities and their relationships is likely more akin to a tangle of yarn than an orderly spiderweb.

Incident Management Teams (IMTs) (of various fashion) are great resources to support the management of incidents, but I often see people confusing the application of an IMT. Most IMTs are adaptable, with well experienced personnel who can pretty much fit into any assignment and make it work. That said, IMTs are (generally) trained in the application of the incident command system (ICS). That is, they are trained in the management of complex, field-level, tactical operations. They (usually) aren’t specifically trained in managing an EOC or other type of operations center. While the principles of ICS can be applied to practically any aspect of incident management, even if ICS isn’t applied in the purest sense, it might not be the system established in a given operations center (in whatever form it may take). While IMTs can work in operations centers, operations centers don’t necessarily need an IMT, and while (formal) IMTs are great resources, they might not be the best solution.  

The issue here certainly isn’t with IMTs, though. Rather it’s with the varying nature of operations centers themselves. IMTs are largely a defined resource. Trying to fit them to your EOC may be a square peg/round hole situation. It’s important to note that there exists no single standard for the organization and management of an EOC. NIMS provides us with some optional models, and in practice much of what I’ve seen often has some similarity to those models, yet have deviations which largely prevent us from labeling what is in practice with any of the NIMS-defined models in the purist sense. The models utilized in EOCs are often practical reflections of the political, bureaucratic, and administrative realities of their host agencies and jurisdictions. They each have internal and external needs that drive how the operations center is organized and implemented. Can these needs be ultimately addressed if a single standard were required? Sure, but when governments, agencies, and organizations have well established systems and organizations, we’ll use finance as an example, it simply doesn’t make sense to reorganize. This is why we are so challenged with establishing a single standard or even adhering to a few models.

The first pathway to success for your operations center is to actually document your organization and processes. It seems simple, yet most EOCs don’t have a documented plan or operating guideline. It’s also not necessarily easy to document how the EOC will work if you haven’t or rarely have activated it at all. This is why we stick to the CPG-101 planning process, engaging a team of people to help determine what will or won’t work, examining each aspect from a different perspective. I also suggest enlisting the help of someone who has a good measure of experience with a variety of EOCs. This may be someone from a neighboring jurisdiction, state emergency management, or a consultant. Either way, start with the existing NIMS models and figure out what will work for you, with modifications as needed. Once you have a plan, you have a standard from which to work.

Once you have that plan, train people in the plan. Figure out who in your agency, organization, or jurisdiction has the knowledge, skills, and abilities to function within key positions. FEMA’s EOC Skillsets can help with this – even if the positions they use don’t totally map to yours, it’s not difficult to line up most of the common functions. Regardless of what model you are using, a foundation of ICS training is usually helpful, but DON’T STOP HERE. ICS training alone, even if your EOC is ICS-based, isn’t enough. I can practically guarantee your EOC uses systems, processes, or implementations unique to your EOC which aren’t part of ICS or the ICS training your personnel received. Plus, well… if you haven’t heard… ICS training sucks. It can be a hard truth for a lot of entities, but to prepare your personnel the best way possible, you will need to develop your own EOC training. And of course to complete the ‘preparedness trifecta’ you should then conduct exercises to validate your plans and support familiarity.

All that said, you may require help for a very large, long, and/or complex incident. This is where government entities and even some in the private sector request incident management support. Typically this incident management support comes from established IMTs or a collection of individuals providing the support you need. The tricky part is that they aren’t familiar with how you are organized or your way of doing things. There are a few ways to hedge against the obstacles this potentially poses. First, you can establish an agreement or contract with people or an organization that know your system. If this isn’t possible, you can at least (if you’ve followed the guidance above) send your plan to those coming to support your needs, allowing them at least a bit of time in transit to study up. Lastly, a deliberate transition, affording some overlap or shadowing time with the outgoing and incoming personnel will help tremendously, affording the incoming personnel to get a hands-on feel for things (I recommend this last one even if the incoming personnel are familiar with your model as it will give an opportunity to become familiar with how you are managing the incident). Of course all of these options will include formal briefings, sharing of documentation, etc.

Remember, though, that there are certain things your agency, organization, or jurisdiction will always own, especially the ultimate responsibility for your mission. Certain internal processes, such as purchasing, are still best handled by your own people. If your operations are technical and industry-specific, such as for a utility, they should still be managed by your own people. That doesn’t mean, however that your people can’t be supported by outside personnel (Ref my concept of an Incident Support Quick Response Team). The bottom line here is that IMTs or any other external incident support personnel are great resources, but don’t set them up for a slow start, or even failure, by not addressing your own preparedness needs for your EOC. In fact any external personnel supporting your EOC should be provided with a packet of information, including your EOC plan and procedures, your emergency operations plan (EOP), maps, a listing of capabilities, demographics, hazards, org charts for critical day-to-day operations, an internal map of the building they will be working in, and anything else that will help orient them to your jurisdiction and organization – and the earlier you can get it to them the better! Don’t forget to get your security personnel on board (building access cards and parking tags) and your IT personnel (access to your network, printers, and certain software platforms). Gather these packets beforehand or, at the very least, assemble a checklist to help your personnel quickly gather and address what’s needed.

© 2021 Tim Riecker, CEDP

Emergency Preparedness Solutions, LLC®

Building Local Incident Management Capability

Tim Riecker, The Contrarian Emergency Manager 2 Comments

Just over a year ago I wrote An Alternate Concept of Incident Management Support, identifying the gap that exists in most local communities and areas for improved incident management capability. While I still think that formal Incident Management Teams (IMTs) are the gold standard, not every community or even multi-county region can support a formal IMT, which requires dozens of personnel and rigorous qualification and maintenance. Over the past year, we’ve seen a lot of use of IMTs across the nation, supporting the COVID-19 response and myriad other incidents. Sitting in over the last few days on the All Hazard Incident Management Team Association (AHIMTA) virtual symposium, there is a lot of exciting evolution happening with IMTs as they continue to enhance their capabilities. And while this is great, I feel we are leaving a lot of areas behind. This isn’t on the AHIMTA, but rather on the emergency management community as a whole. That said, there are certainly some intersections, as a lot of the training available to IMT personnel may need to be made more accessible to those who would be part of the Incident Support Quick Response Teams (ISQRTs) as I came to call them in the article I mentioned from last year, and addressing a fundamental need I’ve been espousing for a long time.

As I’ve soaked in a lot of great information from the AHIMTA symposium about IMTs, the need to build local capability in the absence of IMTs is even more apparent. Some may argue that IMTs are available to deploy to any area if requested. Possibly. Obviously there are a lot of conditions… what are other teams dealing with? What’s the relative priority of the requesting area? EMAC is certainly an option, but States need to approve the local request if they are to put the request into the EMAC system. The state may not agree with the need, may not want to spend the funds for an incoming team for an incident that may not receive a federal declaration, or it may not be practical to wait a couple of days to get an IMT on the ground when the response phase of the incident may be resolved or near resolved by then.   

Fundamentally, every area should have its own organic incident management capability. As mentioned, most areas simply can’t support or sustain the rigors of a formal IMT, but they can support a short roster of people who are interested, able, and capable. This is a situation where a little help can go a long way in making a difference in a local response for a more complex Type 4 incident or the onset of a Type 3 incident – or simply to do what they can for a larger incident where additional help simply isn’t available. I mentioned in last year’s article that the focus should really be on incident planning support, with an Incident Management Advisor to support the IC and local elected officials, an Incident Planning Specialist to help the local response organization harness the Planning Process, a Planning Assistant to support the detailed activities involved in a Planning Section such as situational awareness and resource tracking, and an Operations and Logistics Planner to support local responders who may have great tactical knowledge, but not much experience on operational planning much less forecasting logistical needs associated with this. Largely these are all advisors, who are likely to integrate into the incident management organization, so we aren’t creating new ICS positions, though I still encourage some deeper and deliberate application of incident management advisors.

My big thought today is how do we make something like this happen? First, I think we need to sell FEMA and State IMT programs and or State Training Officers on the concept. That comes first from recognizing and agreeing on the gap that exists and that we must support the organic incident management capability of local jurisdictions with fewer resources, through something that is more than the ICS courses, but less than what is required for an IMT. Part of this is also the recognition that these ISQRTs are not IMTs and not intended to be IMTs but fill an important role in addressing this gap. This will go a long way toward getting this past ICS and IMT purists who might feel threatened by this or for some reason disagree with the premise.

Next is establishing standards, which first is defined by general expectations of activity for each of these roles, pre-requisites for credentialing, then training support. The existing position-specific training is likely not fully appropriate for these positions, but a lot can be drawn upon from the existing courses, especially those for Incident Commander and the Planning Section positions, but there are also some valuable pieces of information that would come from Operations Section and Logistics Section Courses. I’d suggest that we work toward a curriculum to address these specific ISQRT roles. There are then some administrative details to be developed in terms of local formation, protocols for notification and activation, etc. State recognition is important, but perhaps approval isn’t necessarily needed, though coordination and support from States may be critical to the success of ISQRTs, again considering that these are most likely to be serving areas with fewer resources. ISQRTs will also need to work with local emergency managers and local responders to gain support, to be included in local preparedness activities, and to be called upon when they should be. A lot of success can be gained from things such as local/county/regional/state meetings of fire chiefs and police chiefs.

Do you agree with the gap that exists for most communities? What do you think we need to get the ball rolling on such a concept?

© 2021 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®

A Re-Framing of Incident Management Structures

Tim Riecker, The Contrarian Emergency Manager 5 Comments

I recently finished reading Team of Teams by Gen. Stanley McChrystal. The General tells of the new perspective and strategy he needed to employ to better manage the Joint Special Operations Task Force in the 2000s hunting down Al Qaeda insurgents. The Task Force was being out paced by a decentralized organization with all the home team advantages. McChrystal and his team assessed where the Task Force was failing and applied new principles which brought them increased success. The book not only provides examples from the Task Force, but also goes through history and various applications of business and industry to illustrate how different perspectives on organizational management can bring better results. It was fascinating to read this with the constant thought of incident management on my mind and seeing how the early state of the Joint Special Operations Task Force, as well as many of the business and industry examples, had many of the same challenges of incident management today. Highly recommended reading!

Those of you who have been with me for a while know that I’m a big fan of the Incident Command System (ICS), even though I have a lot of issues with how we have been trying to train people to use it (ICS Training Sucks). Similarly, I have a lot of passion for Emergency Operations Centers (EOCs) and the various organizational models which can be used in these facilities, including those which have a lot of similarity to ICS. I’ll collectively refer to these as incident management.

The root of Gen. McChrystal’s book emphasizes the benefits of organizations that are flexible and collaborative, vs the traditional hierarchal organizations. It’s interesting that much of what we espouse as successful implementations in incident management focuses on flexibility and working together, yet the organizational models we use, and sometimes even just the way we depict them, impedes this success. The traditional org charts that we obsessively plaster up on every wall of every command post and EOC emphasize a chain of command, which is so often confused with lines of communication and the continued and necessary close coordination we need to have in an incident management organization. While chain of command is still necessary to understand, that’s really the only value of the hierarchal organization chart.

From Team of Teams, I’d like you to look at two sets of graphics which are found on this site. (these are important to look at… so click the link!) The first identifies complicated vs complex systems (or environments). Complicated systems may be multi-faceted, but largely have a linear progression. Complex systems are unpredictable. I’d offer that incident management can include both, being a complex system until such a point that we can stabilize the incident, then morphing into a more predictable though still complicated system. The primary argument of Team of Teams is to match the organizational structure to the environment, meaning that while a more linear, hierarchal organizational structure is fine for a complicated system, a more dynamic structure is needed for dealing with complex systems.

The second set of graphics depicts three organizational models from Team of Teams. The first is the familiar Command model. This model, as I mentioned earlier, emphasizes chain of command, though clearly also emphasizes stove-piping, which isn’t a reflection of best practices for being dynamic or having coordination across organizational elements. As argued in the book, the separation of organizational elements only works if their functions are not related or connected. We know in ICS that each function is strongly connected to others.  As such, the Command model really doesn’t represent the reality of ICS, even though it’s what we always depict.

The second model, labeled Command of Teams shows collaboration within each team. In consideration of ICS functionality, when I have managed a Planning Section, I expect my team to work together. Yes, they each have different roles and responsibilities, but they all contribute to the primary purpose of the Planning Section. As just a small example, the Demob Unit absolutely must work with the Resources Unit to have knowledge of what resources are on the incident and various data sets about each. They must also collaborate with the Situation Unit Leader who can provide not only information on the current state of things, but hopefully projections of the situation, helping the Demob Unit Leader to develop more accurate timelines for demobilization. This is all well and good, but this model still maintains separation of the major components of the organization (stove-piping).

Next, consider the Team of Teams model, the third in this graphic. At first glance, it looks messy and chaotic, but consider that the principles it tells us are what we should be doing. Again, as a Planning Section Chief, I expect my team members to not just work together, but to coordinate across the entire organization as needed to get their jobs done. Using the Demob Unit as a continued example, their job requires information from and coordination with Logistics, certainly Operations, and even Finance/Admin, and Safety. Their ability to coordinate with others has nothing at all to do with chain of command, and I know my team is more effective when they are interfacing across the organization. My team quickly learns that they don’t need my permission to coordinate with others.

There are several points emphasized in the Team of Teams book that support the Team of Teams model, particularly through the lens of incident management, including:

  1. Efficiency vs Adaptability. Certainly, in incident management we want both, but particularly in the earlier stages of response, adaptability is more important than efficiency. We need to be able to respond to a dynamic, changing environment in the best ways possible. The Team of Teams model maximizes our adaptability.
  2. Procedure vs Purpose. The structure of checklists and other depictions of rigid procedures, which largely serve to strengthen efficiency, can only get us so far in a complex environment. Leaning back into the efficiency vs adaptability argument, rigidity doesn’t serve us well in incident management. When we focus on purpose, we are more adaptable and resilient. When people are focusing exclusively on their own narrow set of tasks, they often lose the big picture that is the overall purpose. In the complexity of incident management, we need to see the forest, not just the trees, in order to understand needs, implications, priorities, dependencies, and options.
  3. Mutually Exclusive and Collectively Exhaustive (MECE) (pronounced mee-see). MECE is used extensively in the business consulting world to depict clear delineation of tasks within one large activity. ICS likes to force us into a MECE environment, which is certainly great for efficiency and eliminating duplication of efforts. While those things are important, the MECE principal eliminates overlap and coordination. The book uses a great example of a sports team to drive this home. Using a sports analogy of my own, consider that in hockey each team has the broad player categories (positions) of forwards, defensemen, and goaltenders. While they each have very distinct purposes and playing strategies, they need to have some overlap to support teamwork, effectiveness, and contingencies. They can’t simply function in a bubble and expect success. ICS loves the rigidity of separating tasks to specific positions, but to be successful there needs to be coordination.
  4. Common Operating Picture. The book uses the term ‘collective intelligence’, but the principal is the same, being that members of the team at large are at least familiar with what is going on, can access more detailed information as needed, and have the information they need to best perform their jobs. The Team of Teams concept promotes this exchange of information and expanded situational awareness.
  5. Leadership at all Levels. While Team of Teams doesn’t explicitly say this, there are several references related to it. We know in any effective organization, especially incident management, the Incident Commander or EOC manager shouldn’t be the only leader. We need leadership practiced at all levels of the organization. We expect Section Chiefs to be leaders; Unit Leaders, Branch Directors, Group Supervisors, etc. Even individual resources can exhibit and practice leadership. This contributes to our adaptability.

After examining these models, I think most will agree that in incident management we really do use the Team of Teams model, but not to the fullest extent. Why is that? I think it’s primarily because we graphically depict our organizations using the Command model and so much of our mindset is fixated on that structure and a perceived rigidity of the positions and flow within that structure. Sure, the Command model is cleaner and less intimidating, but it psychologically predisposes us to silos. In ICS, for example, we do have people coordinating across sections, but aside from the ‘scripted’ activities (i.e. those within the Planning Process), it seems to not come easily.  

We have a lot of room for improvement, and I think we can do so without violating any of the tenets of ICS. We can open ourselves to a more dynamic environment while still maintaining chain of command, unity of command, and span of control. Safety is still emphasized. ICS espouses the free flow of information, but flow of information is different from collaboration – a term rarely found in ICS materials.  In many plans and training that I develop, when I’m referencing certain positions, I often identify the key interactions that position has both within and external to the organization. Interactions are a key to success and need to not just be acknowledged, but emphasized. There is an almost social aspect to the Team of Teams model, but not in the butterfly kind of way. It’s simply a socialization of the system. More people being familiar with what’s going on and what the priorities of others are. This type of environment encourages better communication, more ideas, and an ability to make course corrections on the fly. I think some will push back saying that they want people to ‘stay in their lanes’, but professionals who are well trained should still maintain a primary focus on their job.

Gen. McChrystal emphasizes that a big key to really implementing the Team of Teams model is the mindset of the ranking officer – the Incident Commander or EOC Manager in our case. They need to be willing to let go of what they might have traditionally controlled. They are still absolutely in command, but we need to consider what they should be directly in command of. What decisions REALLY need to be made by the IC or EOC Manager? I’ve seen too many people at that level want to be involved in every decision. I’ve heard all the excuses. Yes, they are the ones ultimately responsible. Yes, they need to justify actions to their boss. But that doesn’t mean they need to have their hands in everything. That’s often less than effective. (Funny enough, I’ve also experienced those who espoused these reasons for micromanaging, yet they were never available to the team to actually make decisions. That puts the team in a difficult position.)

If the ICs or EOC Managers are the ones who set objectives, we could go the extent of saying that any changes of activity within the scope of those objectives should be allowable without needing their approval. That might be a bit extreme for some (yes, I know that they are approving the incident action plan, which identifies things to the tactical level), but if we trust the people who are put in key positions throughout the organization – not only are they all leaders, but armed with a common operating picture and knowing what is called ‘the Commander’s intent’ in military lingo – we should trust that when urgency dictates, they are empowered to make decisions. Pushing decision-making to the lowest practical level can make us more responsive, perhaps saving lives or at least ‘stopping the bleeding’ until a definitive strategy can be developed.

Show the Team of Teams model around a bit. Talk about it. Sure, when people look at that org chart for the first time, I expect there will be some exasperated reactions. But when they read up on it and think it through, they will realize that we already practice it in part. What’s stopping us from full implementation? Two things… a little cultural shift and a varying degree of ego. Silly excuses for not doing things better. We are professionals, after all – right?

There is so much more gold to mine in the Team of Teams book. As mentioned before, I highly recommend this for those interested in organizational development, organizational psychology, incident management, and other related areas. It’s filled full of great examples and will likely prompt a lot of thought as it did for me.  

As always, I’m interested in your thoughts and feedback on this.

© 2021 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®

Incident Management Advisors

Tim Riecker, The Contrarian Emergency Manager 2 Comments

It’s frustrating to see poor incident management practices. For years I’ve reviewed plans that have wild org charts supposedly based on the Incident Command System (ICS); have conducted advanced-level training with seasoned professionals that still don’t grasp the basic concepts; have conducted and evaluated exercises and participated in incident responses in which people clearly don’t understand how to implement the most foundational aspects of ICS. On a regular basis, especially since people know my focus on the subject, I’m told of incident management practices that range from sad to ridiculous.

Certainly not everyone gets it wrong. I’ve seen plans, met people, and witnessed exercises and incidents in which people clearly understand the concepts of ICS and know how to put it into action. ICS is a machine, but it takes deliberate and constant action to make it work. It has no cruise control or auto pilot, either. Sometimes just getting the incident management organization to stay the course is a job unto itself.

If you are new here, I’ve written plenty on the topic. Here’s a few things to get you pointed in the right direction if you want to read more.

ICS Training Sucks. There are a series of related posts that serve as a key stone to so much that I write about.

The Human Factor of Incident Management. This bunch of related articles is about how ICS isn’t the problem, it’s how people try to implement it.  

As I’ve mentioned in other posts, it’s unrealistic for us to expect most local jurisdictions to assemble and maintain anything close to a formal incident management team. We need, instead, to focus on improving implementation of foundational ICS concepts at the local level, which means we need to have better training and related preparedness activities to promote this. Further, we also know that from good management practices as well as long-standing practices of incident management teams, that mentoring is a highly effective means of guiding people down the right path. In many ways, I see that as an underlying responsibility of mine as a consultant. Sometimes clients don’t have the time to get a job done, but often they don’t have the in-house talent. While some consultants may baulk at the mere thought of building capability for a client (they are near sighted enough to think it will put them out of work), the better ones truly have the interests of their clients and the practice of emergency management as a whole in mind.

So what and how do we mentor in this capacity? First of all, relative to incident management, I’d encourage FEMA to develop a position in the National Qualification System for Incident Management Advisors. Not only should these people be knowledgeable in implementations of ICS and EOC management, but also practiced in broader incident management issues. Perhaps an incident doesn’t need a full incident management team, but instead just one or two people to help the local team get a system and battle rhythm established and maintained. One responsibility I had when recently supporting a jurisdiction for the pandemic was mentoring staff in their roles and advising the organization on incident management in a broader sense. They had some people who handled things quite well, but there was a lot of agreement in having someone focus on implementation. I also did this remotely, demonstrating that it doesn’t have to be in person.

In preparedness, I think there is similar room for an incident management advisor. Aside from training issues, which I’ve written at length about over the years (of course there will be more!), I think a lot of support is needed in the realm of planning. Perhaps a consultant isn’t needed to write an entire plan, but rather an advisor to ensure that the incident management practices identified in planning documents are sound and consistent with best practices, meet expectations, and can be actually implemented. So much of what I see in planning in regard to incident management has one or more of these errors:

  1. Little mention of incident management beyond the obligatory statement of using NIMS/ICS.
  2. No identification of how the system is activated and/or maintained.
  3. As an extension of #2, no inclusion of guidance or job aids on establishing a battle rhythm, incident management priorities, etc.
  4. An obvious mis-understanding or mis-application of incident management concepts/ICS, such as creating unnecessary or redundant organizational elements or titles, or trying to force concepts that simply don’t apply or make sense.
  5. No thought toward implementation and how the plan will actually be operationalized, not only in practice, but also the training and guidance needed to support it.

In addition to planning, we need to do better at identifying incident management issues during exercises, formulating remedies to address areas for improvement, and actually implementing and following up on those actions. I see far too many After Action Reports (AARs) that softball incident management shortfalls or don’t go into enough detail to actually identify the problem and root cause. The same can be said for many incident AARs.

When it comes to emergency management, and specifically incident management, we can’t expect to improve without being more direct about what needs to be addressed and committing to corrective actions. We can do better. We MUST do better.

New polling function in WordPress… Let’s give it a try.

©2020 Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC®

Learning from the 2009 H1N1 Pandemic Response (Guest Post)

Tim Riecker, The Contrarian Emergency Manager 4 Comments

Another great article from Alison Poste. Please be sure to check out her blog – The Afterburn – at www.afterburnblog.com.

I’m looking forward to reading about the adaptations to ICS she references in this article.

-TR

~~

Learning from the 2009 H1N1 Pandemic Response

The ICS model remains a universal command and control standard for crisis response. In contrast to traditional operations-based responses, the COVID-19 pandemic has required a ‘knowledge-based’ framework. 

A fundamental element of ICS is the rapid establishment of a single chain of command. Once established, a basic organization is put in place including the core functions of operations, planning, logistics and finance/administration. In the face of a major incident, there is potential for people and institutions to work at cross purposes. The ICS model avoids this by rapidly integrating people and institutions into a single, integrated response organization preserving the unity of command and span of control. Support to the Incident Commander (the Command Staff) includes a Public Information Officer (PIO), a Liaison Officer and a Safety Officer.

In a study done by Chris Ansell and Ann Keller for the IBM Center for the Business of Government in 2014, the response of the U.S. Center for Disease Control and Prevention (CDCP) to the 2009 H1N1 Pandemic was examined in depth. In examining the response, a number of prior outbreak responses were reviewed. Prior to the widespread adoption of ICS, “the CDCP viewed its emergency operations staff as filling an advisory role rather than a leadership role during the crisis” (Ansell and Keller, 2014). This advisory function was the operating principle of the 2003 SARS outbreak response.

ICS was created to coordinate responses that often extend beyond the boundaries of any individual organizations’ capacity to respond. Considering the 2009 H1N1 pandemic response, the authors outline three features complicated the use of the traditional ICS paradigm:

  • The overall mission in a pandemic response is to create authoritative knowledge rather than the delivery of an operational response;
  • The use of specialized knowledge from a wide and dispersed range of sources; and 
  • The use of resources to manage external perceptions of the CDCP’s response.

In response to these unique features, the authors of the study have advocated seven adaptations to the ‘traditional’ ICS structure. These adaptations will be examined in depth in a future post.

Notwithstanding the unique challenges of a ‘knowledge-based’ response, the ‘traditional’ ICS structure is well-equipped to adapt and scale to the needs of any incident. While it is true that a ‘knowledge-based’ response differs from an operational one, this is not inconsistent with the two top priorities of the ICS model: #1: Life Safety and #2: Incident (Pandemic) Stabilization. The objectives of the incident will determine the size of the organization. Secondly, the modular ICS organization is able to rapidly incorporate specialized knowledge and expand/contract as the demands of the incident evolve. Finally, assigning resources to monitor external communications will remain the purview of the PIO as a member of Command Staff.

When the studies are written on the use of ICS in the COVID-19 pandemic, what do you think will be the key take-aways? As always, I’m interested to hear your thoughts and ideas for future topics.

Reference

Ansell, Chris and Ann Keller. 2014. Adapting the Incident Command Model for Knowledge-Based Crises: The Case of the Centers for Disease Control and Prevention. IBM Center for the Business of Government. Retrieved August 16, 2020 from http://www.businessofgovernment.org/sites/default/files/Adapting%20the%20Incident%20Command%20Model%20for%20Knowledge-Based%20Crises.pdf 

How BC is Acing the Pandemic Test (Guest Post)

Tim Riecker, The Contrarian Emergency Manager 2 Comments

I’m excited and honored to promote a new blog being written by Alison Poste. Alison has led major disaster response and recovery efforts in Alberta, Canada, including the 2013 floods and the Fort McMurray wildfires, and currently works as a consultant specializing in business continuity, emergency management, and crisis communications. Her new blog, The Afterburn – Emergency Management Lessons from Off the Shelf, takes a critical look at lessons learned and how they are applied.

I’ve pasted her first post below, but also be sure to click the link above to follow her blog. I’m really excited about the insight Alison will be providing!

– TR

~~

The pandemic has upended how those in the emergency management field have seen traditional response frameworks. Lessons learned from the pandemic response will be useful to governments and the private sector alike in the coming years.

The ICS framework for emergency response is well equipped to address the unique needs of any disaster, including a global pandemic. The rapid scalability of the structure allows the response to move faster than the speed of government. It provides the framework for standardized emergency response in British Columbia (B.C.).

The B.C. provincial government response to the coronavirus pandemic, led by Dr. Bonnie Henry, the Provincial Health Officer (PHO) has received international acclaim. It is useful therefore to learn from the best practises instituted early on in the pandemic to inform future events. 

In February 2020, the Province of B.C. published a comprehensive update to the British Columbia Pandemic Provincial Coordination Plan outlining the provincial strategy for cross-ministry coordination, communications and business continuity measures in place to address the pandemic. Based on ICS, the B.C. emergency response framework facilitates effective coordination by ensuring the information shared is consistent and effective. The Province of B.C. has provided a daily briefing by Dr. Henry and Adrian Dix, the B.C. Minister of Health as a way to ensure B.C. residents receive up to date information from an authoritative source.

While we may consider the COVID-19 pandemic to be a unique event, a number of studies have provided guidance to emergency response practitioners of today. The decisive action taken by the B.C. PHO on COVID-19, has focused on the twin pillars of containment and contact tracing. Early studies regarding the effect of contract tracing on transmission rates have seen promising results, however the tracing remains a logistical burden. As studies indicate, these logistical challenges have the potential to overwhelm the healthcare system should travel restrictions be relaxed, leading to the possible ‘importation’ of new infections. 

B.C. has instituted robust contract tracing mechanisms to reduce the spread of COVID-19 in alignment with best practises in other jurisdictions. When instituted methodically, contact tracing, consistent communication, and Dr. Henry’s mantra to “Be calm. Be kind. Be safe.” remain critical tools to ensure limited spread, a well-informed and socially cohesive population.

How has your organization helped to slow the spread of COVID-19?  As always, I welcome your feedback and suggestions for how to improve the blog.