Читать книгу Emergency Incident Management Systems - Mark Warnick S., Louis N. Molino Sr - Страница 15

Those who cannot remember the past are condemned to repeat it.

George Santayana

It has been said that necessity is the mother of all invention, and this holds especially true with incident management. Out of necessity, the creation of what we now call Incident Management System or IMS was born so that first responders could be more effective in responding to every kind of incident that may occur. IMS methods have been modified to help manage nearly every type of emergency situation that can occur. Whether it is a disaster in a hospital, a traffic collision, an armed hostage situation, or a disaster that utilizes the military and various other federal government entities, IMS is a method that helps ensure everyone is on the same page and working together.

Unlike most creations, IMS is not a physical thing that can be concretely viewed, picked up, or even handled. These IMS systems are concepts. More accurately described, IMS methods are a set of philosophies, policies, and procedures that help the users (of the system) to control and manage chaotic emergencies. These IMS methods are also used to provide structure and safety measures during a planned event. When it is employed properly, it allows those managing an incident or an event to divide larger tasks into much smaller tasks and to assign individuals who will manage specific functions within the response or event. In essence, IMS methods are divide and conquer structures that help to ensure that no details are overlooked.

In the United States, there is an overarching IMS method that is known as the National Incident Management System (NIMS). The NIMS method will be explained more comprehensively in later chapters, but this system was essentially designed to prepare for, prevent, and manage the response and recovery to disaster (and emergency) situations. Utilizing NIMS increases the coordination among individuals who respond to disasters on the local, state, and federal levels. While an oversimplification, NIMS was designed to integrate every stakeholder into an organized system that is ready to respond. When resources are ordered by an Incident Commander (IC) utilizing NIMS, it ensures that they will more than likely get the exact resource they need, and that resource (including personnel) will be on the same page as the local government.

Beyond the use of the overarching NIMS method, there is also what can essentially be called the command and control system of managing an incident in the United States. This is known as the Incident Command System (ICS). ICS allows local governments and local first responders to control an incident while having the insurance policy of being able to integrate outside resources if the local agency is overwhelmed. This IMS method allows the Incident Commander to divide the responsibility of managing the incident into as many as five different tasks, each being managed by someone else, while the Incident Commander manages those supervisors and the overall incident. It is important to note that ICS is a component of NIMS, meaning that NIMS is the all‐encompassing IMS method and ICS supports NIMS. While it may sound confusing, especially this early in the book, it is not difficult to learn.

It should also be noted that there are other IMS methods used in the United States including Hospital Incident Command System (HICS). HICS was designed much like ICS so that it integrates with NIMS. HICS also integrates with ICS as well, and there is usually a seamless, or near seamless integration of the three IMS methods. Much like ICS, HICS facilitates command and control of an emergency or a disaster while enabling the seamless integration of outside resources, should they be needed.

While one could get the impression that IMS methods are useful in overwhelming and large‐scale disasters, they would be wrong. IMS methods can, and should, be utilized in daily emergencies. Local first responders and local nongovernmental agencies (e.g. American Red Cross and Salvation Army) should become proficient in the day‐to‐day use of IMS methods. By doing so, they will more effectively manage small incidents and become more proficient in the use of NIMS and ICS for when the “Big One” hits.

IMS methods can also be useful in nonphysical or catastrophic emergencies. Public safety agencies and other entities that are familiar with IMS can also utilize these same concepts to manage other types of nontraditional emergencies. These might include issues such as managing their day‐to‐day operations and nonphysical or nonemergent situations. IMS systems are extremely useful in organizing what may seem overwhelming.

IMS methods are also practical when an agency is facing a negative media blitz over a negative interaction. Most IMS methods can assist in making sure that all angles of public relations are covered. Consider the amount of crisis management that would be needed in an officer‐involved shooting, a negative story about an ambulance (or fire truck)‐involved collision, or even personnel caught in a scandal. Using an IMS method can and will help manage the crisis in the media, and if structured and utilized correctly, the IMS method can help initiate and provide ongoing damage control.

IMS can also be used to manage planned events such as sporting events, festivals, concerts, and similar events. Properly employed, IMS can be used to manage and control a multitude of incidents, including most nonemergency situations. We only need to look at past historical (major) sporting events to see how an IMS method can be used. It will also help to identify how resources can be organized so that they are highly effective and available.

If we look at Super Bowl LII that took place on 4 February 2018, we can see how managing a large planned event is possible when utilizing an IMS method. As you might imagine, the use of the Incident Command System (ICS) component, integrated with the National Incident Management System (NIMS) was used to manage this major sporting event. Those that oversaw the public safety aspect of this overwhelming planned event made sure that security was of the utmost importance. In their effort to provide top‐notch public safety, they utilized and managed over 40 federal agencies, approximately 840 different officers from 60 local and state agencies, and they incorporated the Minnesota National Guard (Moore, 2015). Beyond the previously mentioned assets, there were also a large contingency of processes and equipment integrated into the overall management of this planned event.

Not only was ICS component and NIMS used to manage a large security presence (to prevent some type of chaos from happening), but it was also used behind the scenes. There were emergency managers who planned, and who were on standby for a mass casualty event, Emergency Medical Services (EMS) personnel were strategically placed and prepared to jump into action should someone become ill or injured, or in the event a mass casualty incident occurred. Hazardous Material (HazMat) teams were also staged and ready to respond if a Chemical, Biological, Radiological, Nuclear, or Explosives (CBRNE) incident occurred. Additionally, a multitude of other very specific teams were managed through the utilization of ICS component and NIMS. Some security teams were scanning for problems, while separately, other teams were ready to jump into action and take the steps needed to mitigate the effects of an emergency situation. Trying to manage a planned event, or even an emergent incident that uses a lot of personnel and equipment, would be a nightmare if not for IMS methods.

In the United States, the ICS component and its supportive companion, NIMS, has become the standard in recent years. Many people have attempted to historically date the initial development of ICS, and there has been much discussion about where the main underpinning began. No concrete date or circumstance has ever been agreed upon, even though it is usually taught that Firefighting Resources of California Organized for Potential Emergencies (FIRESCOPE) was the first official iteration of the formal system known as ICS.

In retrospect, we could say that it was a long progression of events that eventually led to the IMS methods that we now see in today's world. Many different concepts, and many different incidents have used similar methods throughout the last few hundred or more years, and some of them have been concretely identified as playing a significant role in the systems of today. Various incidents have very distinct bits and pieces of current IMS methods.

As we move onward through this chapter, there will be varying incidents discussed. These incidents may have contributed to the IMS we use today, then again, it may be coincidence that these methods were used. It should be noted that some of the history and incidents that may have contributed to modern‐day IMS methods is nothing more than speculation. On the other hand, some of these incidents are concretely documented as contributing to the current IMS methods being used today.