National Incident Management System
The National Incident Management System (NIMS) is a standardized approach to incident management developed by the United States Department of Homeland Security. The program was established in March 2004, in response to Homeland Security Presidential Directive-5, issued by President George W. Bush. It is intended to facilitate coordination between all responders (including all levels of government with public, private, and nongovernmental organizations). The system has been revised once, in December 2008. NIMS is the common framework that integrates a wide range of capabilities to help achieve objectives.
NIMS defines multiple operational systems, including:
NIMS is the result of 40 years of work to improve interoperability in management of an incident. In the 1970s, different agencies at the local, state, and Federal levels got together and created FIRESCOPE, which is the precursor to NIMS. ICS and MACS are both part of FIRESCOPE. in 1982, the authors of FIRESCOPE and the NWCG created the National Interagency Incident Management System (NIIMS) to help make ICS and MACS guidelines applicable to any incident and/or hazard. Many communities adopted the NIIMS, but not everyone did. After 9/11, there was a need for more coordination and clearer communication among agencies, so the DHS started to expand upon FIRESCOPE and NIIMS and created the first NIMS document releasing it in 2004.
Identifying and managing resources allows the Incident Commander to get the correct resources as needed. Identifying the resources can help the IC know that they exist and are ready to deploy for use.
Identifying and Typing ResourcesEdit
Identifying and Typing resources include finding the resources and making sure they are qualified and capable for the job. This process also involves finding out what the resources are most useful for.
Resource Management During an IncidentEdit
Resource management during an incident involves keeping track of resources, requesting resources, and demobilizing resources.
Mutual Aid is when there is a document and/or agreement between jurisdictions to help each other by sending needed resources.
NIMS Management CharacteristicsEdit
NIMS runs on 14 principles of management to help incident management run smoother. The 14 principles include:
- Common Terminology - Communications involve common vocabulary and plain English (i.e. No 10 code)
- Modular Organization - The organizational structure is modular, and can be changed as needed to fit the incident's needs.
- Management by Objectives - This involves creating specific objectives that can be measured to insure that they are being met.
- Incident Action Planning - Incident Action Plans help guide incident activities.
- Manageable Span of Control - Manageable Span of Control allows supervisors to efficiently lead their subordinates on an incident. The rule of thumb for span of control is one supervisor to five-seven subordinates.
- Incident Facilities and Locations - Depending on the incident, the Incident Commander may designate areas for facilities such as Triage Areas, Emergency Shelters, and Incident Command Posts (ICPs).
- Comprehensive Resource Management - Resources are anything that can help in an incident, including personnel, equipment, supplies, etc. Comprehensive Resource Management involves keeping an accurate inventory of all resources available.
- Integrated Communications - Integrated Communications are important since there are multiple different agencies and government levels working together. Integrated Communications can involve using communication software such as video conferencing, and common radio frequencies.
- Establishment and Transfer of Command - At the beginning of any incident, The Incident Commander should establish the command function, and designate where the command post is located. When command is being transferred, the new Incident Commander is briefed on the Incident Action Plan and the status of the incident.
- Unified Command - Unified Command allows the leaders from multiple agencies to work together as Incident Command.
- Chain of Command and Unity of Command - Chain of Command is the linear format from Supervisor to Subordinate. Unity of Command means that each personnel only reports to one supervisor.
- Accountability - Accountability means that every person at an incident has responsibility, has to follow specific guidelines, follow the check-in/check-out rule, and be part of the resource tracking.
- Dispatch/Deployment - Any resources needed on an incident can only deploy if they are requested. No resource can self-deploy. If too many resources self-deploy, the incident may end up with too many resources, and may have nowhere to stage them.
- Information and Intelligence Management - This principle establishes the process for gathering information and processing that information.
Incident Command SystemEdit
The Incident Command System (ICS) is a standardized all-hazards, all incident approch to any incident that allows multiple resources to work together.
The ICS Command Structure is a modular system that can be expanded or contracted as the incident requires. There are multiple staffing positions within the unified command structure. The main staff include Incident Command, Command Staff, and General Staff.
Incident Command or Unified Command are in charge of the entire incident. They direct the workings of the incident.
The Command Staff help the Incident Commander with running an incident when the incident becomes bigger then the IC can handle alone. The three positions within the Command Staff include:
- Public Information Officer (PIO) - The PIO is in charge of talking to the public, the media, and any other external entities. They help inform the public about what is happening at the incident, what has happened, and any other information that needs to be disseminated.
- Safety Officer - The Safety Officer is in charge of the safety of the personnel at the incident. They can request medical resources and other resources important to the safety of the incident. They can stop any unsafe behavior on an incident.
- Liaison Officer - The Liaison Officer is in charge of giving out information to the personnel and resources at an incident. The Liaison Officer is also the person that incident personnel may bring their questions to.
The General Staff do the work like writing IAPs or requesting and documenting resources. Like Command Staff, these positions can be filled as needed. The four main general staff positions are:
- Operations Section - This section plans and performs the activities important to accomplishing the incident objectives. The Operations Section also supports the development of the IAP.
- Planning Section - This section plans and creates the Incident Action Plan (IAP) on a daily basis.
- Logistics Section - The Logistics Section is in charge of requesting and demobilizing resources. They are also in charge of transportation, supplies, medical support, IT support, food, and other required services during the incident.
- Finance/Administration Section - This section works on getting the funding needed for the incident, along with taking care of administrative work.
Another general staff position that is not normally added, but can be added if need is the Information/Intelligence Section. As the name suggests, this staff position is in charge of gathering information and intelligence.
Emergency Operations CenterEdit
An Emergency Operations Center (EOC) is where the command, coordination, and planning are carried out during an emergency. The EOC can be either a fixed location or a mobile location, such as a tent or trailer.
Multiagency Coordination SystemsEdit
The Multiagency Coordination System (MACS) allows multiple agencies to work together and allows for coordination, unified command, planning, and resource allocation.
The communication part of NIMS includes four key principles. They include:
- Interoperability - Allows organizations and agencies to communicate across a wide range of media, including, voice, email, video conferencing, other software, etc.
- Reliability, Scalability, and Portability - Any communication must be reliable and be able to be sized based on the needs of the incident.
- Resilience and Redundancy - Any communication system must be able to provide uninterrupted service, even when normal infrastructure is down, and must be duplicated, should one system go down.
- Security - The communication system must have good security to prevent classified information from leaking out, and to comply with HIPAA.
IS-700.B: An Introduction to the National Incident Management System 
IS-100.C: Introduction to the Incident Command System 
Approximately 14 additional courses are available on selected topics.
- "National Incident Management System" (PDF). Department of Homeland Security. October 2017. Retrieved May 13, 2020.
- Bush, George W. (28 February 2003). "Homeland Security Presidential Directive-5" (PDF). www.dhs.gov. United States Department of Homeland Security. Retrieved 7 January 2017.
- "NIMS Training Program" (PDF). Department of Homeland Security. September 2011. Retrieved March 29, 2014.
- "National Incident Management System" (PDF). FEMA. October 2017. Retrieved March 28, 2021.