Tag homeland security

Water System Preparedness

Tim Riecker, The Contrarian Emergency Manager Leave a comment

For at least the past eight years or so, I’ve kept tabs on what the Environmental Protection Agency (EPA) has been doing for emergency preparedness for water systems.  Their efforts, spearheaded from their Water Security Division, include information on comprehensive emergency management activities – mitigation and resilience, surveillance and response, preparedness, and more.  Their website offers a plethora of resources, not only for water utilities and systems operators, but for others as well.  These resources include tools and guidance for conducting risk assessments, creating emergency plans, building resilience, developing a training and exercise plan, and conducting exercises.  These resources and tools all help to de-mystify emergency management systems and help to build a bridge into the emergency management world.  While they provide information on certain hazards, such as flooding or criminal activity, their approach, overall is all-hazards.  The EPA includes links to ICS and other FEMA training, as well as other agencies, and encourages water systems to interact with other agencies at the local, state, and federal level.

Back in November of last year, I gave a review of the TEEX course MGT: 342 Strategic Overview of Disaster Management for Water and Wastewater Utilities.  Those who work with or for water utilities would certainly benefit from attending this training and reviewing the EPA’s Water Security Division website.  Water is an important component of our Critical Infrastructure, with dependencies cascading across all other sectors.  These resources strengthen and support our continued preparedness within these sector, while also adding to whole community preparedness.

The EPA Water Security Division provides a quarterly e-newsletter, to which you can subscribe to stay abreast of their tools, resources, and information.

© 2016 – Timothy M. Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness

ICS: Let’s Keep Talking

Tim Riecker, The Contrarian Emergency Manager Leave a comment

I find it interesting that a topic so seemingly mundane – that of the incident command system (ICS) has seen an increase of discussion lately.  The NIMS Refresh seems to have fueled some of that, but other writings and conversations have also been taking place.  While I’ve certainly been critical of the national ICS training program in several of my writings, there have been other thoughts posted on ICS, some you absolutely must take a look at:

Are We Overthinking ICS?  This article, posted by noted emergency management consultant Lucien Canton has some great thoughts on the proposed NIMS Refresh.  He brings up an excellent point about the disappearance of Multi-Agency Coordination Systems (MACS) – something I had myself completely missed in my review.  A must read.

ICS and ESF: An Unhappy Marriage?  Another article by Lu Canton.  This piece gives a concise review of the differences between ICS and FEMA’s Emergency Support Function (ESF) structure and gives some ideas on how the two can be brought together.  I’ve seen the things Lu suggests in action, and I promise you, they can work.

Where Incident Management Unravels.  This article by Charles Bailey in the August edition of the Domestic Preparedness Journal took me on a wild ride, for which I’ll have some extended commentary here… I’ve read and reread this article several times, each time having different reactions and responses.  Through my first read, I saw this piece as being highly critical of ICS. Then I read it again, and I began to understand.  While I don’t agree with all Chief Bailey’s points, I respect everything he is saying and absolutely appreciate the thoughts and ideas this article offers.  I’ll leave you to read the article for yourself and form you own opinions.  The bottom line is the importance of early efforts to gain control over the chaos of the incident.  NIMS/ICS doesn’t provide us with all the answers for how to do that – something that I think needs to be reflected in better instruction of the principles of ICS.  Chief Bailey mentions toward the end of his piece the need to create ‘nimble response paradigms’ for initial response – a concept I fully agree with.  I also think that Chief Cynthia Renaud has some incredible insights on this matter in her Edge of Chaos paper.

I’m excited about the volume of discussion over NIMS and ICS lately.  It’s the system we rely on to manage incidents, coordinate resources, and ultimately save lives.  It’s kind of a big deal.  It should be good, and we should do it right.  While it’s the best we currently have, that doesn’t mean the system is perfect, nor will it ever likely be.  Similarly, the human elements involved in training, interpretation, and implementation of the system means that we will rarely do things ‘by the book’, but we are never handed disasters ‘by the book’, either, which emphasizes the number of variables involved in incident management.  The system must continue to evolve to be effective and to reflect our new and changing ideas on incident management.  We need to regularly examine the system critically and as realists and implement positive changes.  That said, change needs to be carefully administered.  We can’t make change for the sake of change, and we must be mindful that constant change will itself create chaos.

Have you read any other great articles on ICS lately?  What thoughts do you have on ICS, ICS training, and the need for ICS to evolve?  What’s missing?

© Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness

Do you Really Know Unified Command?

Tim Riecker, The Contrarian Emergency Manager Leave a comment

Despite how much incident command system (ICS) instructors try to hammer this one home, there still remains some measure of confusion about what the concept of unified command really is. I regularly review documents or sit in meetings where unified command is improperly defined, applied, and discussed.  There are many who espouse that they use unified command instead of ICS.  Unified command is, in fact, an application of ICS, just like many other concepts within the system.  It is not a different system. When unified command is used, all other concepts within ICS remain the same.

From the National Incident Management System (2008) document, unified command is defined as follows: In incidents involving multiple jurisdictions, a single jurisdiction with multiagency involvement, or multiple jurisdictions with multiagency involvement, Unified Command allows agencies with different legal, geographic, and functional authorities and responsibilities to work together effectively without affecting individual agency authority, responsibility, or accountability.

Once we can gain an understanding of what unified command is, implementation of unified command is where the greatest misconceptions lie.  People often think that unified command is applied with a concept best described as ‘We use unified command, but the Fire Chief is in charge.’.  Nope.  That’s not it.  That’s simply an application of single command, with deputies coming from other agencies.  Unified command is truly unified.  The participants in unified command operate at the same level of authority.  Obviously standards of professionalism and legal authority should hold true, ensuring that none are issuing orders contrary to those of their counterparts, and often there is deference to the member of unified command who may have certain jurisdiction or subject matter expertise as it applies to a particular matter, but decisions and made and applied jointly.  The unified command, therefore, acts and speaks as a single entity.

Given the factors described above, as well as the need to properly synchronize incident management (see my recent article on this topic, here), unified command is absolutely something that should be prepared for.  Because of the nuances of its application, planning for unified command is helpful.  While the application of unified command is generally optional, some regulations and policies may require its use under certain circumstances. Be it required or not, plans establish a course of action for stakeholders to follow and can be strongly supported by procedures.  Plans should at least acknowledge that unified command may be an option for certain incidents, and may need to identify who makes the decision to implement unified command.  I’ve seen some plans require unified command for certain incidents, which I’m not crazy about.  Unified command, as mentioned, is just one more application of ICS.  Given the right circumstances, a single command may be the best option.  That said, if something isn’t included in a plan, even as an option, it may not even be considered during an incident.  Unified command should always at least be an option.

As an example of unified command application, the United States Coast Guard (USCG) commonly encourages and participates in unified command for many of their incidents, often pulling together, at a minimum, the USCG, a local or state government representative, and a representative of the responsible party (owner and/or operator).  They do this because it makes sense.  While the USCG has legal authority over navigable waterways and a response requirement within those waterways, incidents can also impact the shorelines, which are generally the responsibility of state and local governments.  State and local governments may also be providing a great deal of resources to assist in the incident.  International laws require that responsible parties do, in fact, take responsibility (usually financially) for incidents caused by or involving their vessels, which makes them a significant (although sometimes reluctant) stakeholder.

Further preparedness measures are needed for practitioners to become proficient in the application of unified command.  The inclusion of the option in plans alone isn’t enough.  It should be trained, so people understand what it is and how best to apply it.  The concept of unified command is incorporated into every level of the ICS national training curriculum.  Sadly, the common misconceptions associated with unified command tell me that we aren’t communicating well enough what unified command actually is.  Beyond training, the best opportunity to reinforce the application of unified command is exercises.  Exercises obviously offer an opportunity for a no-fault environment which allow for informal feedback and formal evaluation, which should both inform potential improvements. Unified command certainly should be practiced to be successful.  The reason it’s so successful with USCG applications is because their people train and exercise heavily in ICS concepts, including unified command.  They also enter a unified command environment with an eye toward coaching other participants who may not be so familiar with it and how it works.

There are a number of keys to success for unified command.  Chief among them are an understanding of what it is and what is expected and an ability to work as a team.  Working well as a team involves essential elements such as communication, coordination, and checking your ego at the door. Rarely is unified command successful when someone is trying to strong-arm the matter.  A successful unified command requires discussions to identify the priorities that each agency or jurisdiction has, and determining how to properly plan, shape, and synchronize the response efforts to ensure that each of these is handled appropriately.  Clearly, some measure of negotiation must regularly take place.

People often ask who should be part of the unified command.  The membership of unified command should remain fairly exclusive.  Representatives should only come from those agencies or jurisdictions that are significant stakeholders within the incident (i.e. they have responsibility or authority for major components of the response).   Just because an agency or jurisdiction is providing resources or support to an incident does not mean they should be part of the unified command.  Unified command functions best when it is small.  If your unified command effort is exceeding five or six people, you are entering the land of management by committee, and that should be avoided.  While some claim that there are a multitude of interests that should be represented in the management of an incident, I would suggest establishing a multi-agency coordination group, which is a policy-level body who can guide the incident command/unified command from that level.  The goal is to have only essential agencies working at the command level.

As I continue the crusade of improving ICS training, we will need to ensure that the concept of unified command gets some special attention to ensure better understanding of what it is and how it works.

I’m interested to hear your thoughts and practices on how you prepare for and implement unified command within your jurisdiction or organization.

© 2016 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness

 

 

Base Camp Connect – Field-Deployable Interoperability Solution

Tim Riecker, The Contrarian Emergency Manager Leave a comment

Hello readers!  I wanted to make everyone aware of an incredible product out there for communications interoperability – Base Camp Connect.  This is a mobile, field-deployable interoperability platform that can bridge voice, data, and radio in minutes.  Right on their home page, they link to a YouTube video demo of their system, which shows many of its capabilities.

Along the top of their webpage, you will also find a number of tabs, including a blog.  Base Camp Connect has brought on some talented bloggers, and me, to write on topics including communications, incident management, and others.  The posts I write for Base Camp Connect are exclusive content only found on their website and LinkedIn page.

Check out their website and the YouTube videos, follow them on LinkedIn, and read through some blog posts.  In fair disclosure, while Base Camp Connect does not pay me to promote their product, they do pay me to write content for them.  I really do think they have a great product, though – so check it out.

-TR

Building a System of Response

Tim Riecker, The Contrarian Emergency Manager 1 Comment

On even relatively simple incidents, multiple agencies respond, each with their own priorities, objectives, and authorities.  Even on these small and fairly routine incidents, agencies will complain about one another, typically from a lack of understanding of their role and priorities at an incident scene.  On-scene conflict between police and fire departments is almost cliché, but if you’ve been in this business for a while, you’ve certainly seen it occur.

The number of agencies and interests often expands with great leaps and bounds as the size, duration, and complexity of an incident grows.  While we have incident management systems (such as the incident command system or ICS) which help us to organize and manage the multitude of resources and interests involved during an incident, it’s critical that we have a better understanding and accountability of these agencies and interests before a complex incident occurs.  How can this best be done?

Management Level

Establishing this mutual understanding and accountability is the foundation of a system of response.  From the broadest levels, this is established in the National Response Framework, which is a national-level document describing how the US Federal government organizes to response to large incidents, but also identifies, in general terms, the roles and responsibilities of state, local, tribal, private, nonprofit, faith-based, and community stakeholders; along with how they interrelate during a response.  In the US, states have their own emergency operations plans, which further narrow this perspective within their state, addressing their own unique hazards, resources, laws, and ways of operating.  County and local governments, individual agencies, organizations, and others can and often times do have their own plans with a continually refined focus.

It is through the creation and ongoing maintenance of these planning documents where our system of response is first built.  Dialogue and understanding among the stakeholders are essential.  We must learn who are partners are in emergency response (and mitigation, recovery, prevention, and protection, for that matter) and what their interests and objectives are.  Sometimes those partners are asked to participate, other times they simply arrive on scene, leaving local responders and the person in charge feeling insecure and frustrated.  In your planning efforts, try to anticipate who might be involved in a critical incident so you can better anticipate those needs.

Responder Level

To further this understanding, especially with those who may find themselves working directly with responders of other agencies, it is important to train and exercise together.  Joint training and exercises give responders an opportunity to navigate course and exercise objectives together, leveraging their own knowledge, experience, and capabilities along with those of others; increasing the value of the learning experience as well as their aptitude for joint operations.

Many training courses are well suited for mixed audiences – from the management and planning level to the tactical level.  Incident command system courses, which all responders should take to an appropriate level, are also ideal for this, especially since they should encourage discussion about operational priorities, objectives, and strategies.  Additionally, courses that are heavy in scenario-based training can greatly maximize this synergy, since they are a combination of training and structured exercises.  Courses that use simulation tables are excellent for cross-discipline integration.

Joint training and exercises might not always be practical, especially for those new to their field of practice.  Acknowledging that, consider including information on the other disciplines within the basic or academy-level training that is conducted.  A brief amount of time spent on the legal authorities, priorities, and operational objectives of partner disciplines can be valuable to creating understanding on a complex incident.

Keep it Going

As with all preparedness efforts, ‘one and done’ is not a mantra you want to follow.  To be effective, contemporary, and impactful; you have to build a legacy program.  As the program continues, strive to constantly improve.  Don’t only keep plans up to date, but create procedures on integration that lead to an effective system of response.  Use training to support these plans and procedures and use exercises as both an opportunity for practice as well as an opportunity to identify strengths and areas for improvement within the plans and procedures.  Joint exercises will help identify areas that need to be addressed, such as interoperable communications, conflicting protocols, and competing priorities.  It’s better to identify and address these matters now than during a critical incident.

© 2016 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness

Using Departmental Operations Centers for Incident Management Success

Tim Riecker, The Contrarian Emergency Manager Leave a comment

Increasingly, government agencies and departments are identifying the benefits of establishing and activating departmental operations centers (DOCs) to help manage their responses to incidents.  At the Vermont Vigilant Guard 2016 exercise, which concluded last week, I had some opportunity to discuss the benefits of DOCs, particularly with an agency who used theirs for the first time in this exercise.

For most agencies, a DOC can relieve agency representatives in an EOC from also having to manage and track their agency’s response activity.  In an EOC, an agency representative is largely a conduit for communication and they provide knowledge of their agency and their agency’s capabilities as they contribute to the greater discussions within the EOC.  According to NIMS/ICS, an agency representative should have some decision-making capability for their agency, although political and practical realities often dictate otherwise.  The overall scope of activity for an agency representative in an EOC largely precludes them from also managing the details of their agency’s response, particularly if that response is even moderately complex.

A DOC is the ideal location from which an agency can oversee and coordinate their own response to an incident.  They can deploy and track resources, address internal logistics matters, and coordinate external logistics matters back through their agency representative at the EOC.  DOCs are also an excellent application for large agencies, which may have a variety of technical functions organized throughout, such as a health department or transportation department.  Pulling together representatives from each organizational element within the agency to collectively troubleshoot, problem solve, and share resources, is excellent use of a DOC.  In a way, this application of a DOC could be considered similar to a multi-agency coordination center (MACC).

Does a DOC need to mirror NIMS/ICS (or the new Center Management System) standards?  While there is no set standard for organizing and managing a DOC, there are a lot of applications of ICS that can certainly be applied.  If you look at the main activities of your DOC, you will see where opportunities for integration of ICS principles exist.  Consider that a DOC should have and maintain good situational awareness.  While much of this can be provided by the EOC, the EOC may (should) be looking for some specific information from your agency.  A situation unit within your DOC would certainly be helpful.  Likewise, DOCs often address tactical or near-tactical application, by deploying and directing resources from throughout their agency.  Having a resource unit within your DOC will help tremendously in the tracking of these resources.  Depending on the size and scope, it may be prudent for your DOC to establish an incident action plan (IAP) of its own.

Logistics, mentioned earlier, may be another need within a DOC.  Certainly an element of finance is important for the approval of procurements and tracking of costs within the agency related to the incident.  If resources are being deployed, someone should be in charge of operations.  Lastly, any organization needs to maintain someone in charge.  A DOC Manager would be the ideal generic term for this position.

What are the draw backs of establishing a DOC?  First of all, it’s an additional layer of incident management.  While possibly necessary based on factors discussed earlier, adding layers of incident management can make incident management more complex, especially if roles of each layer and function are not well defined.  The best way to address this is pre-planning!  Staffing can also be a significant concern.  Many agencies may be too small to warrant, much less have staff available, for a DOC.  If such is the case, just as in other applications of ICS, you should be able to collapse down to a manageable size.

An often seen pitfall of DOCs is that they can quickly devolve into a management by committee type of structure; particularly with larger agencies where senior staff, who are used to regular meetings with each other, are now representing their functional interests within the DOC.  I’ve seen this result in what is essentially one endless meeting, interrupted by phone calls and emails which introduce new problems and perpetuate more discussion.  Strong leadership is absolutely required to ensure that a group such as this stays focused and on task, resolving issues on a timely basis.

Overall, the use of Departmental Operations Centers is a smart practice.  Work internally to plan their use, scoping out when and how it will be applied, where it will be located, the organization to be used, and how it is integrated into the overall incident management effort.  Once plans are developed and appropriate training is performed, exercise the plan to identify areas for improvement, turning those into corrective actions, and implementing them for continued success.

© 2016 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness

A Review and 3 Highlights of the DHS Active Shooter Preparedness Workshop

Tim Riecker, The Contrarian Emergency Manager 2 Comments

Last month I had the opportunity to attend a day-long active shooter workshop in Rochester, NY conducted by the DHS Office of Infrastructure Protection.  The focus was awareness of, preparedness for, and response to an active shooter event, with a lean towards a facilities-based audience rather than public safety.

The workshop began with discussions on recognition, then worked through each of the five mission areas (Prevention, Protection, Mitigation, Response, and Recovery).  The primary speaker was excellent, with real-world experience in active shooter situations.  While they referred to the offering as a pilot, the workshop has been around for a few years in various versions.  Understandably, and unfortunately, it’s difficult for the workshop to keep up with lessons learned from recent events.

As mentioned, the workshop weaves through the five mission areas, rather awkwardly trying to also align with the CPG 101 planning process.  I’m not sure that the two really fit well and it was clearly something new to the course, as the primary speaker missed some of the indicators for activities.  The workshop agenda also fell short, with the facilitators clearly offering a higher than usual number of breaks and of longer than usual length to maintain the workshop as a full day.

The activities were table-based, and focused on the primary steps as outlined in CPG 101, with the goal of giving some ideas and structure to the creation of an active shooter preparedness plan for a facility.  Ideas and discussion generated at our table and others were great, as attendees came from a broad array of facilities, such as schools, night clubs, health care, office buildings, and others.  The most disappointing comments were those about roadblocks people faced within their own organizations in planning and other preparedness activities for active shooters.  There is clearly a lot of denial about these incidents, which will only serve to endanger people.

With a number of public safety professionals in attendance, there was some great reflection on coordination with public safety in both preparedness and response.  One of the gems of the workshop was the number of audio and video clips provided throughout.  The segments included media and 911 clips, as well as post incident interviews with victims and responders.  The insight offered by these was excellent and they were a great value add.

Three pieces of information resonated above all others in this workshop:

  • Run, Hide, Fight (or variants thereof) was stressed as the best model for actions people can take in the event of an active shooter.
  • The inclusion of planning for persons with disabilities is extremely important in an active shooter situation. They may have less of an ability to Run, Hide, and/or Fight, and this should be accounted for in preparedness measures.
  • Essential courses of action for planning include:
    1. Reporting
    2. Notification
    3. Evacuation
    4. Shelter in Place
    5. Emergency Responder Coordination
    6. Access Control
    7. Accountability
    8. Communications Management
    9. Short Term Recovery
    10. Long Term Recovery

Since the workshop was in pilot form, there were no participant manuals provided, which a number of people were hopeful to have.  They did, however, provide a CD with a plethora of materials, including references, some videos, and planning guides.  Many of these I’ve seen and used before, but some were new to me.  There was a commitment to send us all an email with a link to a download of the participant manual once it was available.  Some of those resources can be found here.

All in all, this was a good workshop.  The mix of an audience (numbering over 60, I believe) contributed to great discussion and the primary speaker was great.  The presentation materials were solid and provided a lot of context.  While I was disappointed in the lack of a participant manual and the inclusion of too many breaks, I certainly understand that this is the pilot of a redeveloped program which they are trying to keep as timely and relevant as possible.  While I already knew of many of the concepts and standards, there was some great material and discussion, especially in the context of facilities rather than public safety response.  This is a good program which I would recommend to facility owners, managers, and safety/emergency management personnel as well as jurisdiction emergency management and public safety personnel.

© 2016 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness

Five Guidelines for Creating Effective Disaster Exercise Injects

Tim Riecker, The Contrarian Emergency Manager 1 Comment

While there is a lot of important and necessary planning that takes place before the development of exercise injects can even be considered, injects themselves are where the proverbial rubber meets the road.  How we craft those injects can often times make or break the conduct of the exercise.  Injects provide context, as if the events of the exercise were occurring in real life.  While we try to avoid delivering injects that directly prompt player responses, injects will often provide information which will lead players to react to the information provided.  Here are five guidelines to help you develop effective exercise injects:

  1. Injects must be purposeful and each one must relate back to one or more exercise objectives. Far too often we see injects that have no real bearing on the objectives of the exercise.  These are simply distractions and lead to busy work.  Keep things focused.  Just a few well-crafted injects can engage a number of players in active discussion or activity.
  2. Realistic injects are a must. While there will always be a grumble from some people claiming that something would ‘never happen that way’, due diligence must go into ensuring that injects are as realistic and grounded as possible.
  3. Be aware of who an inject would actually originate from. A common mistake I see is injects being scripted to originate from inappropriate sources.  This distracts from reality.  Also, injects should never originate from a player.
  4. Be flexible and aware. Sometimes players accomplish what they need to without an inject.  In that event, there may not be a need to use that inject.  Similarly, players may not respond to an inject as expected, so further action on the part of the Facilitators/Controllers/Simcell may be needed.
  5. Always have backups! As you build your Master Scenario Events List (MSEL), maintain a side list of contingency injects that can be used to speed up or slow down the exercise, or to address occurrences where players did not respond as expected.

Thoughts and ideas on these and other guidelines are always welcome!

© 2016 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness!

ICS Training (Still) Sucks… One Year Later

Tim Riecker, The Contrarian Emergency Manager 13 Comments

Just over a year ago, I posted my article Incident Command Training Sucks, which to date has been viewed almost 2000 times on the WordPress blog platform, alone.  Since then, I’ve written several more times on the necessity to change the foundational ICS training curriculum in the US to programs that are focused on application of ICS in initial and transitional response instead of just theory and vague instruction.  I am greatly appreciative of all the support these articles have received and the extra effort so many have taken to forward my blog on to the attention of others.  These posts have led to some great dialogue among some incredible professionals about the need to update ICS training.  Sadly, there is no indication of action in this direction.

A recent reader mentioned that it often ‘takes guts to speak the truth’.  It’s a comment I appreciate, but I think the big issue is often complacency.  We settle for something because we don’t have an alternative.  Also, I’ve found that people are reluctant to speak out against the current training programs because there are so many good instructors or because the system, foundationally, is sound.  My criticisms are not directed at instructors or the system itself – both of which I overwhelmingly believe in.  I’m also not being critical of those who have participated in the creation of the current curriculum or those who are the ‘keepers’ of the curriculum.

Much of the existing curriculum has been inherited, modified from its roots in wildfire incident management, where it has served well.  While adjustments and updates have been made through the years, it’s time we take a step away and examine the NEED for training.  Assessment is, after all, the first step of the ADDIE model of instructional design.  Let’s figure out what is needed and start with a clean slate in designing a NEW curriculum, instead of making adjustments to what exists (which clearly doesn’t meet the need).

Another reader commented that ‘The traditional ICS courses seem to expect the IC to just waive their hands and magically the entire ICS structure just would build beneath them’.  It is phrases we find in the courses such as ‘establish command’ or ‘develop your organization’ that are taken for granted and offer little supporting content or guides to application.  The actions that these simple phrases point to can be vastly complicated.  This is much of the point of Chief Cynthia Renaud’s article ‘The Missing Piece of NIMS: Teaching Incident Commanders to Function on the Edge of Chaos’.  We need to train to application and performance – and I’m not talking about formal incident management teams, I’m talking about the responders in your communities.  The training programs for incident management teams are great, but not everyone has the time or ability to attend these.

I’m hoping that my articles continue to draw attention to this need.  Perhaps the changes that come as a result of the final NIMS refresh will prompt this; hopefully beyond just a simple update to the curriculum giving us a real, needs-based rewrite.  As I’ve mentioned before, this is public safety, not a pick-up game of kickball.  We can do better.

© 2016 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness

Achieving Coordination Through Unity of Effort

Tim Riecker, The Contrarian Emergency Manager Leave a comment

WESA 90.5, Pittsburgh’s NPR News Station, posted an interesting article titled ‘Trump Rally To Blame for Emergency Response Revamp’.  As the articles tells the story, an internal City committee spent several weeks reviewing communications and other information after an April rally in which three were arrested and four police officers suffered minor injuries.  The findings of the committee’s work included the discovery of fractured planning and response within the City of Pittsburgh.  Assuming this has been a regular practice, I’m surprised it took them this long to discover the issue and begin work to address it – although when a jurisdiction functions in a fractured fashion, it’s an easy observation to miss.

The City’s Public Safety Director stated a new system is being implemented in which a ‘unified and streamlined approach to planning’ and a ‘clearer chain of command’ will be put in place.  The article indicates that the City’s Emergency Management Office will have more of a role in coordination.

It’s good to see that Pittsburgh is making some changes to how they plan for and respond to incidents.  This should serve as a role model for a significant number of jurisdictions across the nation – and I’m sure across the world – which have siloed planning and response, with each agency conducting their own activities with little to no coordination.  Proper and safe emergency management requires a team approach, and every team needs someone to coordinate and lead.  This doesn’t necessarily mean that emergency management is in charge – in fact I feel it’s a rare occasion that emergency management should be in charge – but coordination is still an essential element of success, particularly for complex planning and operations.

The term ‘unity of effort’ is gaining more and more traction through the years.  I first heard it probably ten or twelve years ago.  I was pleased to see the intention of adding the term officially to our lexicon in the draft NIMS Refresh document that was released a couple months back.  Although it was just a mention, it was rather encouraging.  Unity of effort doesn’t require an emergency management office or an emergency manager, but having a central point of coordination helps – especially one that isn’t focused or constrained by the mission and tactics of other public safety agencies.  The mission of emergency management IS coordination!

How do you rate the public safety coordination in your jurisdiction?  Is there room for improvement?  While politics are often at play, sometimes it just takes a good measure of facilitation to bring people together in one room and talk about what needs to be accomplished.

© 2016 – Timothy Riecker, CEDP

Emergency Preparedness Solutions, LLC – Your Partner in Preparedness