Skip to content
From Fire Safety Academy Wiki
Lisa (talk | contribs)
New FSE wiki article: National Incident Management System (written by Claude Opus 5.5)
 
Lisa (talk | contribs)
FSE wiki: fact-check corrections to NIMS source attribution and historical scope (written by Claude Opus 5.5)
Line 5: Line 5:
== Definition and scope ==
== Definition and scope ==


Van Helden and Stewart (2008) write that, pursuant to the Department of Homeland Security and presidential directives, federal, state and local governments were instructed to develop guidelines, standards and protocols to implement NIMS.<ref name="VHS-12-199">Van Helden and Stewart (2008), p. 12-199.</ref> All state and local governments were strongly encouraged to adopt NIMS as their single approach to terrorist attacks, major disasters and other emergencies. Schmidt (2008) describes NIMS as a national approach to incident management that applies at all jurisdictional levels and across functional disciplines.<ref name="Schmidt-1-143" /> It covers the full range of potential incidents and hazard scenarios, regardless of size or complexity, and was designed to improve coordination and cooperation between public and private entities.
Van Helden and Stewart (2008) write that, pursuant to the Department of Homeland Security and presidential directives, federal, state and local governments were instructed to develop guidelines, standards and protocols to implement NIMS.<ref name="VHS-12-199">Van Helden and Stewart (2008), p. 12-199.</ref> All state and local governments were strongly encouraged to adopt NIMS as their single approach to terrorist attacks, major disasters and other emergencies.<ref name="VHS-12-199" /> Schmidt (2008) describes NIMS as a national approach to incident management that applies at all jurisdictional levels and across functional disciplines.<ref name="Schmidt-1-143" /> It covers the full range of potential incidents and hazard scenarios, regardless of size or complexity, and was designed to improve coordination and cooperation between public and private entities.


Loflin (2008) describes NIMS as a core set of doctrine, principles, terminology and organisational processes that enables effective, efficient and collaborative incident management at all levels.<ref name="Loflin-12-121" /> To provide a framework for interoperability and compatibility, it balances flexibility against standardisation. The flexibility applies to all phases of incident management: prevention, preparedness, response, recovery and mitigation. NIMS provides a set of standardised organisational structures, among them ICS, multi-agency coordination systems and public information systems. It also sets requirements for processes, procedures and systems to improve interoperability among jurisdictions and disciplines.<ref name="Loflin-12-121" />
Loflin (2008) describes NIMS as a core set of doctrine, principles, terminology and organisational processes that enables effective, efficient and collaborative incident management at all levels.<ref name="Loflin-12-121" /> To provide a framework for interoperability and compatibility, it balances flexibility against standardisation. The flexibility applies to all phases of incident management: prevention, preparedness, response, recovery and mitigation. NIMS provides a set of standardised organisational structures, among them ICS, multi-agency coordination systems and public information systems. It also sets requirements for processes, procedures and systems to improve interoperability among jurisdictions and disciplines.<ref name="Loflin-12-121" />
Line 15: Line 15:
NIMS dates from the years after 11 September 2001. Schmidt (2008) states that it was developed following the terrorist attacks of that day.<ref name="Schmidt-1-143" /> In Homeland Security Presidential Directive 5 (HSPD-5), President Bush called on the Secretary of Homeland Security to develop a national incident management system.<ref name="Loflin-12-121" /> Its purpose was a consistent nationwide approach for all levels of government to work together on domestic incidents. The department issued NIMS on 1 March 2004, after close collaboration with state and local officials and a wide range of public safety organisations. The report of the National Commission on Terrorist Attacks upon the United States (the "9/11 Commission") also recommended national adoption of ICS to improve command, control and communications.<ref name="Loflin-12-121" />
NIMS dates from the years after 11 September 2001. Schmidt (2008) states that it was developed following the terrorist attacks of that day.<ref name="Schmidt-1-143" /> In Homeland Security Presidential Directive 5 (HSPD-5), President Bush called on the Secretary of Homeland Security to develop a national incident management system.<ref name="Loflin-12-121" /> Its purpose was a consistent nationwide approach for all levels of government to work together on domestic incidents. The department issued NIMS on 1 March 2004, after close collaboration with state and local officials and a wide range of public safety organisations. The report of the National Commission on Terrorist Attacks upon the United States (the "9/11 Commission") also recommended national adoption of ICS to improve command, control and communications.<ref name="Loflin-12-121" />


NIMS built on an existing system rather than starting from nothing. Loflin (2008) calls ICS one of the most important best practices taken into NIMS, a standard, on-scene, all-hazards system already used by fire fighters, hazardous materials teams, rescuers and emergency medical teams.<ref name="Loflin-12-121" /> ICS had grown out of the FIRESCOPE programme in California after the wildland fires of 1970. In 1982 it was adopted for wildland fire agencies as the National Interagency Incident Management System.<ref name="Loflin-12-120">Loflin (2008), p. 12-120.</ref><ref name="Loflin-12-119">Loflin (2008), p. 12-119.</ref> The Incident Command System Operational System Description (ICS 120-1), maintained by the FIRESCOPE agencies and the National Wildfire Coordinating Group, later served as the basis for the NIMS ICS.<ref name="Loflin-12-121" /> Snyder (2008) describes NIMS as the expansion of the incident management system within the department's National Response Plan.<ref name="Snyder-12-193">Snyder (2008), p. 12-193.</ref>
NIMS built on an existing system rather than starting from nothing. Loflin (2008) calls ICS one of the most important best practices taken into NIMS, a standard, on-scene, all-hazards system already used by fire fighters, hazardous materials teams, rescuers and emergency medical teams.<ref name="Loflin-12-121" /> ICS had grown out of the FIRESCOPE programme in California after the wildland fires of 1970.<ref name="Loflin-12-119">Loflin (2008), p. 12-119.</ref> In 1982 FIRESCOPE ICS documentation was revised and adopted as the National Interagency Incident Management System.<ref name="Loflin-12-120">Loflin (2008), p. 12-120.</ref> The Incident Command System Operational System Description (ICS 120-1), maintained by the FIRESCOPE agencies and the National Wildfire Coordinating Group, later served as the basis for the NIMS ICS.<ref name="Loflin-12-121" /> Snyder (2008) describes NIMS as the expansion of the incident management system within the department's National Response Plan.<ref name="Snyder-12-193">Snyder (2008), p. 12-193.</ref>


Federal funding was tied to adoption. When NIMS was released, Secretary Tom Ridge and Under Secretary Brown highlighted that ICS compliance was possible fairly quickly.<ref name="Loflin-12-122" /> In some cities the fire and police departments had worked together with ICS for years, while elsewhere only the fire department used it. Law enforcement, public works and public health knew the concept but regarded ICS as a fire service system. Loflin writes that NIMS ends this discrepancy, because HSPD-5 requires state and local adoption of NIMS as a condition for receiving federal preparedness funding.<ref name="Loflin-12-122" />
Federal funding was tied to adoption. When NIMS was released, Secretary Tom Ridge and Under Secretary Brown highlighted that ICS compliance was possible fairly quickly.<ref name="Loflin-12-122" /> In some cities the fire and police departments had worked together with ICS for years, while elsewhere only the fire department used it. Law enforcement, public works and public health knew the concept but regarded ICS as a fire service system. Loflin writes that NIMS ends this discrepancy, because HSPD-5 requires state and local adoption of NIMS as a condition for receiving federal preparedness funding.<ref name="Loflin-12-122" />
Line 23: Line 23:
Van Helden and Stewart (2008) list the three systems on which the NIMS incident command structure is based: the incident command system, the multiagency coordination system and public information systems.<ref name="VHS-12-200" /> ICS provides the on-scene organisation, with an incident commander, a command staff and sections for operations, planning, logistics and finance/administration.<ref name="Schmidt-1-143" /> Within NIMS it is the standardised organisational structure for the management of all incidents.<ref name="Loflin-12-121" /> The public information function centres on a joint information center (JIC), the essential communication point for all local entities involved in disaster response and recovery.<ref name="VHS-12-211">Van Helden and Stewart (2008), p. 12-211.</ref> The JIC is responsible for the overall coordination of public information, which becomes essential when disasters cross jurisdictional and geographic boundaries.
Van Helden and Stewart (2008) list the three systems on which the NIMS incident command structure is based: the incident command system, the multiagency coordination system and public information systems.<ref name="VHS-12-200" /> ICS provides the on-scene organisation, with an incident commander, a command staff and sections for operations, planning, logistics and finance/administration.<ref name="Schmidt-1-143" /> Within NIMS it is the standardised organisational structure for the management of all incidents.<ref name="Loflin-12-121" /> The public information function centres on a joint information center (JIC), the essential communication point for all local entities involved in disaster response and recovery.<ref name="VHS-12-211">Van Helden and Stewart (2008), p. 12-211.</ref> The JIC is responsible for the overall coordination of public information, which becomes essential when disasters cross jurisdictional and geographic boundaries.


The handbook authors name the working principles in slightly different ways. Van Helden and Stewart give the core values as span of control, unity of command, accountability, resource tracking and the operation of incident action plans.<ref name="VHS-12-200" /> C. J. Wright (2008a) lists the NIMS elements of an incident management system as common terminology, modular organisations, integrated communications, a unified command structure and consolidated action plans.<ref name="CJWright-13-142">C. J. Wright (2008a), p. 13-142.</ref> His list continues with a manageable span of control, predesignated incident facilities and the management of all resources. For communications centres, Merklinger (2008) gives an effective span of control under NIMS of five to seven people per supervisor.<ref name="Merklinger-12-260">Merklinger (2008), p. 12-260.</ref>
The handbook authors name the working principles in slightly different ways. Van Helden and Stewart give the core values as span of control, unity of command, accountability, resource tracking and the operation of incident action plans.<ref name="VHS-12-200" /> C. J. Wright (2008a) lists the NIMS elements of an incident management system as common terminology, modular organisations, integrated communications, a unified command structure and consolidated action plans.<ref name="CJWright-13-142">C. J. Wright (2008a), p. 13-142.</ref> His list continues with a manageable span of control, predesignated incident facilities and resource management.<ref name="CJWright-13-142" /> For communications centres, Merklinger (2008) gives an effective span of control under NIMS of five to seven people per supervisor.<ref name="Merklinger-12-260">Merklinger (2008), p. 12-260.</ref>


Resource typing is one of the tools behind common terminology. Within NIMS, resources are divided into categories such as law enforcement, public works and fire fighting, and further defined by kind and type.<ref name="VHS-12-205">Van Helden and Stewart (2008), p. 12-205.</ref> The aim is that all agencies use one approach to categorising the resources available in an emergency. Van Helden and Stewart give the example of a community that requests a generator without stating its type, size, fuel or electrical hookup. With resource typing, the county and the state understand the request and can respond in time. The specific terms are listed in the National Mutual Aid Glossary of Terms and Definitions, and in 2008 the authors described resource typing as a work in progress.<ref name="VHS-12-205" />
Resource typing is one of the tools behind common terminology. Within NIMS, resources are divided into categories such as law enforcement, public works and fire fighting, and further defined by kind and type.<ref name="VHS-12-205">Van Helden and Stewart (2008), p. 12-205.</ref> The aim is that all agencies use one approach to categorising the resources available in an emergency. Van Helden and Stewart give the example of a community that requests a generator without stating its type, size, fuel or electrical hookup. With resource typing, the county and the state understand the request and can respond in time. The specific terms are listed in the National Mutual Aid Glossary of Terms and Definitions, and in 2008 the authors described resource typing as a work in progress.<ref name="VHS-12-205" />
Line 45: Line 45:
NIMS reaches beyond the fireground. Merklinger (2008) writes that, with new federal requirements, NIMS should be applied in any communications centre.<ref name="Merklinger-12-260" /> For industrial fire brigades, Snyder (2008) recommends training in an incident management system, especially for brigade leaders. He notes that NFPA 1561 contains the minimum requirements and that training courses on the newly introduced NIMS were available from the Department of Homeland Security.<ref name="Snyder-12-195">Snyder (2008), p. 12-195.</ref>
NIMS reaches beyond the fireground. Merklinger (2008) writes that, with new federal requirements, NIMS should be applied in any communications centre.<ref name="Merklinger-12-260" /> For industrial fire brigades, Snyder (2008) recommends training in an incident management system, especially for brigade leaders. He notes that NFPA 1561 contains the minimum requirements and that training courses on the newly introduced NIMS were available from the Department of Homeland Security.<ref name="Snyder-12-195">Snyder (2008), p. 12-195.</ref>


NIMS also shapes cooperation between agencies. Denlinger states that mutual-aid plans should specify that NIMS and ICS will be used during all incidents. She adds that most states and provinces had large-area disaster plans coordinated under NIMS.<ref name="Denlinger-12-65">Denlinger (2008), p. 12-65.</ref> At aircraft accidents, Kreckie (2008) describes ICS and NIMS protocol as leaving the fire department in charge until rescue is complete, the fire is out and the scene is safe. Command of the incident then passes to law enforcement.<ref name="Kreckie-13-112">Kreckie (2008), p. 13-112.</ref>
NIMS also shapes cooperation between agencies. Denlinger states that mutual-aid plans should specify that NIMS and ICS will be used during all incidents. She adds that many US states had large-area disaster plans coordinated under NIMS.<ref name="Denlinger-12-65">Denlinger (2008), p. 12-65.</ref> At aircraft accidents, Kreckie (2008) describes ICS and NIMS protocol as leaving the fire department in charge until rescue is complete, the fire is out and the scene is safe. Command of the incident then passes to law enforcement.<ref name="Kreckie-13-112">Kreckie (2008), p. 13-112.</ref>


== The World Trade Center and the NIST recommendation ==
== The World Trade Center and the NIST recommendation ==
Line 51: Line 51:
NIST's investigation of the World Trade Center disaster led to a direct recommendation on NIMS. On 11 September 2001 there was no formal structure of unified command between the New York City departments below the commissioner level, and the fire and police command posts were separated.<ref name="NIST-191">National Institute of Standards and Technology (2005), p. 191.</ref> In its Recommendation 24, NIST called for codes and protocols to ensure effective and uninterrupted command and control in large-scale building emergencies.<ref name="NIST-220" /> State, local and federal jurisdictions should implement NIMS and work with the Department of Homeland Security to test and implement an effective unified command and control system. NIST notes that NIMS addresses interagency coordination and establishes a response matrix that assigns lead agency responsibilities for different types of emergencies and functions. At a minimum, each supporting agency should assign an individual to coordinate with the lead agency at each incident command post.<ref name="NIST-220" />
NIST's investigation of the World Trade Center disaster led to a direct recommendation on NIMS. On 11 September 2001 there was no formal structure of unified command between the New York City departments below the commissioner level, and the fire and police command posts were separated.<ref name="NIST-191">National Institute of Standards and Technology (2005), p. 191.</ref> In its Recommendation 24, NIST called for codes and protocols to ensure effective and uninterrupted command and control in large-scale building emergencies.<ref name="NIST-220" /> State, local and federal jurisdictions should implement NIMS and work with the Department of Homeland Security to test and implement an effective unified command and control system. NIST notes that NIMS addresses interagency coordination and establishes a response matrix that assigns lead agency responsibilities for different types of emergencies and functions. At a minimum, each supporting agency should assign an individual to coordinate with the lead agency at each incident command post.<ref name="NIST-220" />


The NIST report on WTC 7, published in 2008, repeated this recommendation.<ref name="NIST-1A-70">National Institute of Standards and Technology (2008), pp. 70–71.</ref> It linked the recommendation to that building, because the New York City Office of Emergency Management had its centre in WTC 7. The centre was evacuated early in the day, and NIST found that its location there contributed to weaker interagency command and control on 11 September 2001. In New York itself, NIST reported that the city was studying NIMS as a potential means of operating a city-wide incident command system.<ref name="LV-177">Lawson and Vettori (2005), p. 177.</ref> FDNY concentrated on training in ICS, on training several teams as incident management teams, and on helping to establish a City-wide Incident Management System.<ref name="LV-177" />
The NIST report on WTC 7, published in 2008, repeated this recommendation.<ref name="NIST-1A-70">National Institute of Standards and Technology (2008), pp. 70–71.</ref> It linked the recommendation to that building, because the New York City Office of Emergency Management had its centre in WTC 7.<ref name="NIST-1A-70" /> The centre was evacuated early in the day, and NIST found that its location there contributed to weaker interagency command and control on 11 September 2001.<ref name="NIST-1A-70" /> In New York itself, NIST reported that the city was studying NIMS as a potential means of operating a city-wide incident command system.<ref name="LV-177">Lawson and Vettori (2005), p. 177.</ref> FDNY concentrated on training in ICS, on training several teams as incident management teams, and on helping to establish a City-wide Incident Management System.<ref name="LV-177" />


== Limits and practical issues ==
== Limits and practical issues ==
Line 57: Line 57:
The handbook authors identify training as the main practical difficulty. Van Helden and Stewart write that most communities striving to be NIMS compliant faced great challenges in training.<ref name="VHS-12-200" /> They regarded the initial and recurrent training of all entities that will operate in a disaster as one of the most important things to plan for over the following decade. The level of training is defined in the NIMS documents of the Department of Homeland Security.<ref name="VHS-12-200" />
The handbook authors identify training as the main practical difficulty. Van Helden and Stewart write that most communities striving to be NIMS compliant faced great challenges in training.<ref name="VHS-12-200" /> They regarded the initial and recurrent training of all entities that will operate in a disaster as one of the most important things to plan for over the following decade. The level of training is defined in the NIMS documents of the Department of Homeland Security.<ref name="VHS-12-200" />


Plans can also become too heavy to use. According to Van Helden and Stewart, many preparedness plans written to comply with state and federal guidelines become so extensive that they are not practical during a real emergency.<ref name="VHS-12-201">Van Helden and Stewart (2008), p. 12-201.</ref> They therefore recommend that local governments prepare a smaller field-operating guide or other abbreviated versions of their plans. On the other side, Loflin notes that some purists may claim that a particular application of ICS is not consistent with NIMS.<ref name="Loflin-12-122" /> His answer is that ICS need not be approached "with the same mathematical precision used by an engineer"; progress is made as long as implementation is consistent with the basic principles of NIMS.
Plans can also become too heavy to use. According to Van Helden and Stewart, many preparedness plans written to comply with state and federal guidelines become so extensive that they are not practical during a real emergency.<ref name="VHS-12-201">Van Helden and Stewart (2008), p. 12-201.</ref> They therefore recommend that local governments prepare a smaller field-operating guide or other abbreviated versions of their plans.<ref name="VHS-12-201" /> On the other side, Loflin notes that some purists may claim that a particular application of ICS is not consistent with NIMS.<ref name="Loflin-12-122" /> His answer is that ICS need not be approached "with the same mathematical precision used by an engineer"; progress is made as long as implementation is consistent with the basic principles of NIMS.


NIMS is a United States framework. The handbook describes it as it stood up to 2008, including resource typing that was still being defined.<ref name="VHS-12-205" /> The Department of Homeland Security itself recognised that the overwhelming majority of incidents are handled every day by a single local jurisdiction.<ref name="Loflin-12-121" /> There will, however, be instances in which successful incident management depends on responders from several jurisdictions and on personnel and equipment from other states and the federal government.<ref name="Loflin-12-121" /> Loflin adds that such resources must come together in an organisational framework that everyone understands and must follow a common plan developed through incident action planning.<ref name="Loflin-12-122" />
NIMS is a United States framework. The handbook describes it as it stood up to 2008, including resource typing that was still being defined.<ref name="VHS-12-205" /> The Department of Homeland Security itself recognised that the overwhelming majority of incidents are handled every day by a single local jurisdiction.<ref name="Loflin-12-121" /> There will, however, be instances in which successful incident management depends on responders from several jurisdictions and on personnel and equipment from other states and the federal government.<ref name="Loflin-12-121" /> Loflin adds that such resources must come together in an organisational framework that everyone understands and must follow a common plan developed through incident action planning.<ref name="Loflin-12-122" />

Revision as of 23:52, 7 November 2026

The National Incident Management System (NIMS) is the national framework of the United States for managing domestic incidents, issued by the Department of Homeland Security on 1 March 2004.[1] It provides a consistent approach that lets federal, state, tribal and local governments, and private organisations, work together to prepare for, prevent, respond to and recover from incidents of any cause, size or complexity.[1][2] NIMS is described as a core set of doctrine, principles, terminology and organisational processes, built on a balance between flexibility and standardisation.[1] Its incident command structure rests on three systems: the Incident command system (ICS), a multiagency coordination system and public information systems.[3]

NIMS was developed after the terrorist attacks of 11 September 2001, under Homeland Security Presidential Directive 5, which made state and local adoption a condition for federal preparedness funding.[2][4] It adopted ICS, which the fire service had pioneered for Firefighting, as the standard organisational structure for all incidents.[1] By the time of the 2008 NFPA Fire Protection Handbook, NIMS was presented as the single tool for all branches of government in the management of critical incidents. Its authors also note that many communities seeking compliance faced great challenges in training.[3] NIST recommended in 2005 that state, local and federal jurisdictions implement NIMS, based on its investigation of the emergency response at the World Trade Center.[5]

Definition and scope

Van Helden and Stewart (2008) write that, pursuant to the Department of Homeland Security and presidential directives, federal, state and local governments were instructed to develop guidelines, standards and protocols to implement NIMS.[6] All state and local governments were strongly encouraged to adopt NIMS as their single approach to terrorist attacks, major disasters and other emergencies.[6] Schmidt (2008) describes NIMS as a national approach to incident management that applies at all jurisdictional levels and across functional disciplines.[2] It covers the full range of potential incidents and hazard scenarios, regardless of size or complexity, and was designed to improve coordination and cooperation between public and private entities.

Loflin (2008) describes NIMS as a core set of doctrine, principles, terminology and organisational processes that enables effective, efficient and collaborative incident management at all levels.[1] To provide a framework for interoperability and compatibility, it balances flexibility against standardisation. The flexibility applies to all phases of incident management: prevention, preparedness, response, recovery and mitigation. NIMS provides a set of standardised organisational structures, among them ICS, multi-agency coordination systems and public information systems. It also sets requirements for processes, procedures and systems to improve interoperability among jurisdictions and disciplines.[1]

The scope is wider than the fire service. Van Helden and Stewart note that earlier approaches to managing large incidents had components similar to NIMS, but that the federal government had never designated one unified, all-hazards approach.[3] Incident command models typically began in the fire service and then spread to other branches of government. Under NIMS, the same tool is used by all branches of federal, state and local government, including fire, police and public works. Each government entity therefore has to identify who will fill the key roles in the system.[3]

Origins

NIMS dates from the years after 11 September 2001. Schmidt (2008) states that it was developed following the terrorist attacks of that day.[2] In Homeland Security Presidential Directive 5 (HSPD-5), President Bush called on the Secretary of Homeland Security to develop a national incident management system.[1] Its purpose was a consistent nationwide approach for all levels of government to work together on domestic incidents. The department issued NIMS on 1 March 2004, after close collaboration with state and local officials and a wide range of public safety organisations. The report of the National Commission on Terrorist Attacks upon the United States (the "9/11 Commission") also recommended national adoption of ICS to improve command, control and communications.[1]

NIMS built on an existing system rather than starting from nothing. Loflin (2008) calls ICS one of the most important best practices taken into NIMS, a standard, on-scene, all-hazards system already used by fire fighters, hazardous materials teams, rescuers and emergency medical teams.[1] ICS had grown out of the FIRESCOPE programme in California after the wildland fires of 1970.[7] In 1982 FIRESCOPE ICS documentation was revised and adopted as the National Interagency Incident Management System.[8] The Incident Command System Operational System Description (ICS 120-1), maintained by the FIRESCOPE agencies and the National Wildfire Coordinating Group, later served as the basis for the NIMS ICS.[1] Snyder (2008) describes NIMS as the expansion of the incident management system within the department's National Response Plan.[9]

Federal funding was tied to adoption. When NIMS was released, Secretary Tom Ridge and Under Secretary Brown highlighted that ICS compliance was possible fairly quickly.[4] In some cities the fire and police departments had worked together with ICS for years, while elsewhere only the fire department used it. Law enforcement, public works and public health knew the concept but regarded ICS as a fire service system. Loflin writes that NIMS ends this discrepancy, because HSPD-5 requires state and local adoption of NIMS as a condition for receiving federal preparedness funding.[4]

Components and principles

Van Helden and Stewart (2008) list the three systems on which the NIMS incident command structure is based: the incident command system, the multiagency coordination system and public information systems.[3] ICS provides the on-scene organisation, with an incident commander, a command staff and sections for operations, planning, logistics and finance/administration.[2] Within NIMS it is the standardised organisational structure for the management of all incidents.[1] The public information function centres on a joint information center (JIC), the essential communication point for all local entities involved in disaster response and recovery.[10] The JIC is responsible for the overall coordination of public information, which becomes essential when disasters cross jurisdictional and geographic boundaries.

The handbook authors name the working principles in slightly different ways. Van Helden and Stewart give the core values as span of control, unity of command, accountability, resource tracking and the operation of incident action plans.[3] C. J. Wright (2008a) lists the NIMS elements of an incident management system as common terminology, modular organisations, integrated communications, a unified command structure and consolidated action plans.[11] His list continues with a manageable span of control, predesignated incident facilities and resource management.[11] For communications centres, Merklinger (2008) gives an effective span of control under NIMS of five to seven people per supervisor.[12]

Resource typing is one of the tools behind common terminology. Within NIMS, resources are divided into categories such as law enforcement, public works and fire fighting, and further defined by kind and type.[13] The aim is that all agencies use one approach to categorising the resources available in an emergency. Van Helden and Stewart give the example of a community that requests a generator without stating its type, size, fuel or electrical hookup. With resource typing, the county and the state understand the request and can respond in time. The specific terms are listed in the National Mutual Aid Glossary of Terms and Definitions, and in 2008 the authors described resource typing as a work in progress.[13]

NIMS also changes some titles. Loflin notes that, with the advent of NIMS, "safety officer" became the correct title for this position on the command staff. NFPA 1521 keeps the term incident safety officer to distinguish it from the health and safety officer.[14] Every public information officer should be trained in NIMS and follow its procedures for that position, which is part of the command staff reporting directly to the incident commander.[15]

NIMS in emergency management

NIMS operates inside the wider field of Emergency management. Van Helden and Stewart describe four phases of the emergency management cycle: mitigation, preparedness, response and recovery.[3] The phases form a loop and build on one another, and some may occur at the same time. The authors note that these phases are consistent with NFPA 1600, Standard on Disaster/Emergency Management and Business Continuity Programs, which the 9/11 Commission endorsed. Emergency plans that define roles in the field and in the Emergency operations centre should all be tied into NIMS.[16] State, regional, local and department plans must work together, especially for requests for additional resources through Mutual aid and other agreements.

Emergency support functions are a second organising idea. They are functions carried out by federal, state and local governments in response to a disaster, such as transportation, communications, fire fighting, mass care and health.[10] The federal concept began with 10 elements, and states and local governments have expanded it further. Van Helden and Stewart consider it important that incident commanders integrate the emergency support functions into a NIMS-compliant plan. Some communities have NIMS-compliant plans in which the support functions are less visible, but the same elements are still present whatever names are used.[10]

The handbook also describes the National Response Plan (NRP) of the Department of Homeland Security. In its flow chart, local first responders arrive first at the scene and alert the mayor or county executive, who activates the local emergency operations centre.[17] The local government requests aid from the governor, who activates the state centre and, after a preliminary damage assessment, requests a presidential declaration. The Homeland Security Operations Center evaluates the situation and reports to the Secretary of Homeland Security, who may recommend a declaration to the President. Federal assistance is then coordinated through a Joint Field Office. Van Helden and Stewart list a clear understanding of the NRP, and of its capabilities and limitations, among the key elements of response to a major disaster.[18]

Who leads depends on the event. Following the NIMS organisational structure, a large event needs an incident commander, who may be the police chief, the fire chief, the health department director or someone else.[19] If a disaster takes a different turn, as with the release of Weapons of mass destruction material such as smallpox or with a pandemic flu outbreak, the response may be drastically different.[16] Local and state health departments then take key leadership roles, and police and fire fighters may play more of a supporting role.[20] Denlinger (2008) advises that planning for incidents involving weapons of mass destruction be done by a group that includes planners from all response agencies.[21]

Adoption in the fire service

Fire departments came to NIMS with long experience of ICS. Penney (2008) notes that the Department of Homeland Security had put a high priority on training every organisation in NIMS, and that ICS, used by fire departments for many years, fits well within it.[22] Denlinger (2008) describes ICS as a staple of fire service training for decades that had been incorporated into NIMS, which was taught across the United States in local, state and national curricula.[23] Laughlin (2008) gives the adoption of NIMS as an example of a new procedure that has to be extended to all personnel in a short time.[24] Klaene and Sanders (2008) list NIMS among the innovations that aid safe and effective fireground operations.[25]

NIMS reaches beyond the fireground. Merklinger (2008) writes that, with new federal requirements, NIMS should be applied in any communications centre.[12] For industrial fire brigades, Snyder (2008) recommends training in an incident management system, especially for brigade leaders. He notes that NFPA 1561 contains the minimum requirements and that training courses on the newly introduced NIMS were available from the Department of Homeland Security.[26]

NIMS also shapes cooperation between agencies. Denlinger states that mutual-aid plans should specify that NIMS and ICS will be used during all incidents. She adds that many US states had large-area disaster plans coordinated under NIMS.[27] At aircraft accidents, Kreckie (2008) describes ICS and NIMS protocol as leaving the fire department in charge until rescue is complete, the fire is out and the scene is safe. Command of the incident then passes to law enforcement.[28]

The World Trade Center and the NIST recommendation

NIST's investigation of the World Trade Center disaster led to a direct recommendation on NIMS. On 11 September 2001 there was no formal structure of unified command between the New York City departments below the commissioner level, and the fire and police command posts were separated.[29] In its Recommendation 24, NIST called for codes and protocols to ensure effective and uninterrupted command and control in large-scale building emergencies.[5] State, local and federal jurisdictions should implement NIMS and work with the Department of Homeland Security to test and implement an effective unified command and control system. NIST notes that NIMS addresses interagency coordination and establishes a response matrix that assigns lead agency responsibilities for different types of emergencies and functions. At a minimum, each supporting agency should assign an individual to coordinate with the lead agency at each incident command post.[5]

The NIST report on WTC 7, published in 2008, repeated this recommendation.[30] It linked the recommendation to that building, because the New York City Office of Emergency Management had its centre in WTC 7.[30] The centre was evacuated early in the day, and NIST found that its location there contributed to weaker interagency command and control on 11 September 2001.[30] In New York itself, NIST reported that the city was studying NIMS as a potential means of operating a city-wide incident command system.[31] FDNY concentrated on training in ICS, on training several teams as incident management teams, and on helping to establish a City-wide Incident Management System.[31]

Limits and practical issues

The handbook authors identify training as the main practical difficulty. Van Helden and Stewart write that most communities striving to be NIMS compliant faced great challenges in training.[3] They regarded the initial and recurrent training of all entities that will operate in a disaster as one of the most important things to plan for over the following decade. The level of training is defined in the NIMS documents of the Department of Homeland Security.[3]

Plans can also become too heavy to use. According to Van Helden and Stewart, many preparedness plans written to comply with state and federal guidelines become so extensive that they are not practical during a real emergency.[32] They therefore recommend that local governments prepare a smaller field-operating guide or other abbreviated versions of their plans.[32] On the other side, Loflin notes that some purists may claim that a particular application of ICS is not consistent with NIMS.[4] His answer is that ICS need not be approached "with the same mathematical precision used by an engineer"; progress is made as long as implementation is consistent with the basic principles of NIMS.

NIMS is a United States framework. The handbook describes it as it stood up to 2008, including resource typing that was still being defined.[13] The Department of Homeland Security itself recognised that the overwhelming majority of incidents are handled every day by a single local jurisdiction.[1] There will, however, be instances in which successful incident management depends on responders from several jurisdictions and on personnel and equipment from other states and the federal government.[1] Loflin adds that such resources must come together in an organisational framework that everyone understands and must follow a common plan developed through incident action planning.[4]

See also

Notes

  1. ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 Loflin (2008), p. 12-121.
  2. ↑ 2.0 2.1 2.2 2.3 2.4 Schmidt (2008), p. 1-143.
  3. ↑ 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 Van Helden and Stewart (2008), p. 12-200.
  4. ↑ 4.0 4.1 4.2 4.3 4.4 Loflin (2008), p. 12-122.
  5. ↑ 5.0 5.1 5.2 National Institute of Standards and Technology (2005), p. 220.
  6. ↑ 6.0 6.1 Van Helden and Stewart (2008), p. 12-199.
  7. ↑ Loflin (2008), p. 12-119.
  8. ↑ Loflin (2008), p. 12-120.
  9. ↑ Snyder (2008), p. 12-193.
  10. ↑ 10.0 10.1 10.2 Van Helden and Stewart (2008), p. 12-211.
  11. ↑ 11.0 11.1 C. J. Wright (2008a), p. 13-142.
  12. ↑ 12.0 12.1 Merklinger (2008), p. 12-260.
  13. ↑ 13.0 13.1 13.2 Van Helden and Stewart (2008), p. 12-205.
  14. ↑ Loflin (2008), p. 12-111.
  15. ↑ Adair (2008), p. 5-58.
  16. ↑ 16.0 16.1 Van Helden and Stewart (2008), p. 12-202.
  17. ↑ Van Helden and Stewart (2008), p. 12-210.
  18. ↑ Van Helden and Stewart (2008), p. 12-209.
  19. ↑ Van Helden and Stewart (2008), p. 12-213.
  20. ↑ Van Helden and Stewart (2008), p. 12-203.
  21. ↑ Denlinger (2008), p. 12-57.
  22. ↑ Penney (2008), p. 5-32.
  23. ↑ Denlinger (2008), p. 12-54.
  24. ↑ Laughlin (2008), p. 12-167.
  25. ↑ Klaene and Sanders (2008), p. 13-3.
  26. ↑ Snyder (2008), p. 12-195.
  27. ↑ Denlinger (2008), p. 12-65.
  28. ↑ Kreckie (2008), p. 13-112.
  29. ↑ National Institute of Standards and Technology (2005), p. 191.
  30. ↑ 30.0 30.1 30.2 National Institute of Standards and Technology (2008), pp. 70–71.
  31. ↑ 31.0 31.1 Lawson and Vettori (2005), p. 177.
  32. ↑ 32.0 32.1 Van Helden and Stewart (2008), p. 12-201.

References

  • Adair, R. J. (2008). Media's role in fire and life safety education. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 5-45–5-62). National Fire Protection Association.
  • Denlinger, R. F. (2008). Managing fire-rescue departments. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 12-51–12-78). National Fire Protection Association.
  • Klaene, B. J., & Sanders, R. (2008). Fireground operations. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 13-3–13-11). National Fire Protection Association.
  • Kreckie, J. (2008). Aircraft rescue and fire fighting (ARFF). In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 13-99–13-115). National Fire Protection Association.
  • Laughlin, J. W. (2008). Training programs for fire and emergency service personnel. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 12-161–12-175). National Fire Protection Association.
  • Lawson, J. R., & Vettori, R. L. (2005). The emergency response operations (NIST NCSTAR 1-8). National Institute of Standards and Technology.
  • Loflin, M. E. (2008). Safety, medical, and health issues and programs. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 12-107–12-125). National Fire Protection Association.
  • Merklinger, J. M. (2008). Public emergency services alarm, dispatch, and communications systems. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 12-253–12-266). National Fire Protection Association.
  • National Institute of Standards and Technology. (2005). Final report on the collapse of the World Trade Center towers (NIST NCSTAR 1).
  • National Institute of Standards and Technology. (2008). Final report on the collapse of World Trade Center Building 7 (NIST NCSTAR 1A).
  • Penney, G. (2008). Disaster preparedness education. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 5-29–5-43). National Fire Protection Association.
  • Schmidt, D. L. (2008). Emergency management and business continuity. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 1-137–1-156). National Fire Protection Association.
  • Snyder, M. (2008). Industrial fire loss prevention. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 12-177–12-198). National Fire Protection Association.
  • Van Helden, W., & Stewart, T. (2008). Disaster planning and response services. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 12-199–12-214). National Fire Protection Association.
  • Wright, C. J. (2008a). Managing the response to hazardous material incidents. In A. E. Cote, C. C. Grant, J. R. Hall, Jr., & R. E. Solomon (Eds.), Fire protection handbook (20th ed., pp. 13-117–13-144). National Fire Protection Association.