NIMS 2017 Update: Overview and Changes to the National Incident Management System, Study notes of Logistics

Download NIMS 2017 Update: Overview and Changes to the National Incident Management System and more Study notes Logistics in PDF only on Docsity! FEMA Emergency Management Institute National Incident Management System (NIMS) 2017 Learning Materials Slide 1 NIMS 2017 Learning Materials Purpose • In October 2017 FEMA published a revision of the National Incident Management System (NIMS). • The 2017 NIMS document replaces the 2008 NIMS. • This content is to provide information to emergency management practitioners on the key changes contained in the new NIMS 2017 document. • These learning materials are provided as a “bridge” to deliver interim NIMS 2017 document refresh information until updated NIMS courses are available. • This is not intended as stand-alone training on NIMS. This content is designed as a supplement to be used in conjunction with existing legacy NIMS/ ICS course materials in order to provide students with additional information on key NIMS 2017 changes. Slide 2 NIMS 2017 – Overview (1 of 2) NIMS 2017 strengthens guidance for effective incident management:  Reflects and incorporates policy updates from lessons learned from exercises and real-world incidents and disasters  Clarifies the processes and terminology for qualifying, certifying, and credentialing incident personnel, building a foundation for the development of a national qualification system  Removes the Preparedness component of NIMS to avoid redundancy with the National Preparedness System and Goal  Clarifies that NIMS is more than just Incident Command System (ICS), and that it applies to all incident personnel, from the incident command post to the National Response Coordination Center  Demonstrates the applicability of NIMS to all five mission areas (Prevention, Protection, Mitigation, Response and Recovery)  Adds guidance on the Intelligence and Investigations function Slide 5 NIMS 2017 – Overview (2 of 2) • Refines the model for the Operational Period Planning Cycle • Provides expanded EOC guidance based on input from local, state, tribal and territorial EOC leaders • Describes common functions and terminology for staff in Emergency Operations Centers (EOC), while remaining flexible to allow for differing missions, authorities, and resources of EOCs across the Nation • Explains the relationship among Incident Command Structure (ICS), Emergency Operation Centers (EOCs), and senior leaders/ policy groups (Multiagency Coordination Group) • Enhances guidance on information management processes Slide 6 NIMS 2008-2017 Comparison NIMS 2008 Com- ponent Contents 1 Preparedness 2 Communications and Information Management 3 Resource Management 4 Command and Management • Incident Command System (ICS) • Multiagency Coordination System (MACS) • Public Information 5 Ongoing Management and Maintenance Elements of both the structure and content of NIMS have been changed in the NIMS 2017 update NIMS 2017 Com- ponent Contents 1 Fundamentals and Concepts of NIMS 2 Resource Management 3 Command and Coordination • Incident Command System (ICS) • Emergency Operations Centers (EOC) • Multiagency Coordination Group (MAC Group) • Joint Information System (JIS) 4 Communications and Information Management Slide 7 Overview of NIMS Components (1 of 2) NIMS 2008 defined five NIMS Components: Preparedness, Communications and Information Management, Resource Management, Command and Management, and Ongoing Management and Maintenance. NIMS 2017 defines three NIMS framework components which enable diverse organizations to integrate capabilities and achieve shared goals: • Resource Management • Command and Coordination • Communications and Information Management Slide 10 Overview of NIMS Components (2 of 2) Definitions of the three NIMS framework components: • Resource Management describes standard mechanisms to systematically manage resources, including personnel, equipment, supplies, teams, and facilities, both before and during incidents in order to allow organizations to more effectively share resources when needed. • Command and Coordination describes leadership roles, processes, and recommended organizational structures for incident management at the operational and incident support levels and explains how these structures interact to manage incidents effectively and efficiently. • Communications and Information Management describes systems and methods that help to ensure that incident personnel and other decision makers have the means and information they need to make and communicate decisions. Slide 11 NIMS 2017 Component 2: Resource Management • Reorganizes key resource management activities to address resource planning (pre-incident) resource management activities (during incidents), and mutual aid • Establishes a foundation for a national qualification system by clarifying processes for qualifying, certifying and credentialing incident personnel • Emphasizes the role of the Authority Having Jurisdiction (AHJ) 2008 NIMS • Concepts and Principles • Managing Resources 2017 NIMS • Resource Management Preparedness • Resource Management During an Incident • Mutual Aid Slide 12 Authority Having Jurisdiction (AHJ) • The AHJ is a public or private sector entity that has the legal authority to establish and administer processes to qualify, certify, and credential personnel for incident-related positions. • The AHJ may be a state or Federal agency, training commission, NGO, private sector company, or a tribal or local agency such as a police, fire, or public health department. • The AHJ derives authority to credential from the elected official or, in the private sector, from the senior executive. Slide 15 NIMS Qualification, Certification and Credentialing Process • The NIMS qualification, certification and credentialing process supports sharing of personnel resources for mutual aid. • Nationally standardized criteria and minimum qualifications for positions provide a consistent baseline for qualifying and credentialing the incident workforce. • This is a decentralized process that relies on Authorities Having Jurisdiction (AHJ). • Each jurisdictional authority develops, implements, maintains, and oversees the qualification, certification, and credentialing process within its organization or jurisdiction. Slide 16 Resources - Preparedness Activities • Before an incident jurisdictions and organizations develop resource plans. • This resource planning includes identifying resource requirements based on an assessment of threats and vulnerabilities and developing strategies to obtain the needed resources. • Resource management strategies include stockpiling resources, establishing mutual aid agreements to obtain resources from neighboring jurisdictions, determining approaches to reassigning resources from non-essential tasks, and developing contracts to rapidly acquire resources from vendors when needed. • A resource inventory is used to track resource availability and enables organizations to acquire resources promptly when needed for an incident. Slide 17 NIMS 2017 Component 3: Command and Coordination • Defines the fourteen NIMS Management Characteristics • Describes four NIMS Command and Coordination structures:  Incident Command System (ICS)  Emergency Operations Centers (EOCs)  Multiagency Coordination Group (MAC Group)  Joint Information System (JIS) 2008 - Command and Management • Incident Command System (ICS) • Multiagency Coordination System (MACS) • Public Information 2017 – Command and Coordination • Multi-Agency Coordination Systems (MACS):  ICS  EOCs  MAC Group  JIS Slide 20 NIMS Management Characteristics NIMS bases incident management and coordination on fourteen NIMS Management Characteristics (formerly called ICS Management Characteristics) • Common Terminology • Modular Organization • Management by Objectives • Incident Action Planning • Manageable Span of Control • Incident Facilities and Locations • Comprehensive Resource Management • Integrated Communications • Establishment and Transfer of Command • Unified Command • Chain of Command and Unity of Command • Accountability • Dispatch/ Deployment • Information and Intelligence Management The name is new but the 14 characteristics remain the same Slide 21 NIMS Command and Coordination Structures – Incident Command System (ICS) • The Incident Command System (ICS) is used for on-scene Management of Incidents • When an incident occurs or threatens, local emergency personnel manage response using ICS Slide 22 Incident Command System Structure ICS still includes five major functional areas: • Command • Operations • Planning • Logistics • Finance/Administration. INCIDENT COMMANDER PUBLIC INFORMATION OFFICER SAFETY OFFICER LIAISON OFFICER OPERATIONS SECTION CHIEF PLANNING SECTION CHIEF LOGISTICS SECTION CHIEF FINANCE/ ADMINISTRATION SECTION CHIEF Slide 25 Intelligence/ Investigations Placement in ICS The Intelligence/ Investigations (I/I) function may be used for incidents involving intensive intelligence gathering and investigative activities. The IC/UC can place the I/I function in multiple locations within the incident command structure based on factors such as the nature of the incident, the level of I/I activity, and the relationship of I/I to other incident activities. The I/I function can be placed in the Planning Section, in the Operations Section, within the Command Staff, as a separate General Staff section, or in some combination of these locations. Slide 26 Incident Management Team (IMT) Incident Management Assistance Team (IMAT) IMT: IMTs are rostered groups of ICS-qualified personnel, consisting of an Incident Commander, other incident leadership, and personnel qualified for other key ICS positions. IMTs exist at local, regional, state, tribal, and national levels and have formal notification, deployment, and operational procedures in place. IMTs can be delegated the authority to act on behalf of the affected jurisdiction or organization. IMAT: Some IMTs are referred to as Incident Management Assistance Teams (IMAT) to clarify that they support on-scene personnel and/or the affected jurisdiction(s). IMATs exist at various levels of government and within the private sector. As an example, FEMA IMATs deploy to incidents to help identify and provide Federal assistance, and coordinate and integrate inter-jurisdictional response in support of an affected state or tribe. Slide 27 NIMS Command and Coordination Structures – Emergency Operations Centers (EOCs) • Emergency Operations Centers (EOCs) are used for the offsite support to on-scene ICS operations. • If the incident is large or complex, local Emergency Operations Centers activate. • NIMS 2017 provides expanded guidance on EOC structures and activation levels. Slide 30 Emergency Operations Centers (EOCs) • NIMS 2017 EOC content was developed with input from EOC leaders across the nation. • NIMS 2017 describes common functions, examples of organizational structure and terminology for staff in EOCs. • ICS is used to manage on-scene, tactical-level response; EOCs are used to manage off-scene support to ICS. • Common EOC functions include information management, resource management, and communicating policy decisions. Slide 31 Emergency Operations Centers (EOCs) – Expanded NIMS 2017 EOC Content • Jurisdictions and organizations across the Nation use EOCs • EOCs are locations where staff from multiple agencies assemble to provide coordinated support to incident command, on-scene personnel, and/or other EOCs. • The purpose, authorities, and composition of the teams that staff EOCs vary widely, but generally, the teams consolidate and exchange information, support decision making, coordinate resources, and communicate with personnel on scene and at other EOCs. • NIMS 2017 identifies three common ways of organizing EOC Teams: 1. ICS or ICS-like structure 2. Incident Support Model structure 3. Departmental structure Slide 32 EOC Structures (3 of 3) Departmental EOC Structure Emergency Manager Department of Natural Resources Department of Health & Human Services Department of Public Works Department of Public Safety Department of Administration Department of Education Jurisdictions/organizations may opt instead to use their day-to-day departmental/agency structure and relationships in their EOC. By operating in the context of their normal relationships, department/agency representatives can function in the EOC with minimal preparation or startup time. Slide 35 EOC Activation and Deactivation • EOCs are activated for various reasons based on the needs of a jurisdiction, organization, or Incident Commander; the context of a threat; the anticipation of events; or in response to an incident. • EOCs frequently have multiple activation levels to allow for a scaled response, delivery of the needed resources, and a level of coordination appropriate to the incident. • The next slide outlines the three activation levels in NIMS 2017: Slide 36 EOC Center Activation Levels Level Activation Level Title Description 3 Normal Operations/ Steady-State ● Activities that are normal for the center, when no incident or specific risk or hazard has been identified, are underway. ● This includes routine watch and warning activities if the center normally houses this function. 2 Enhanced Steady State/ Partial Activation ● Certain EOC Team members/ organizations are activated to monitor a credible threat, risk or hazard and/or to support the response to a new and potentially evolving incident. 1 Full Activation ● EOC team is activated, including personnel from all assisting agencies, to support the response to a major incident or credible threat. Slide 37 NIMS Command and Coordination Structures – Joint Information System (JIS) • The Joint Information System (JIS) is the fourth NIMS Command and Coordination structure. • JIS integrates incident information and public affairs to provide consistent, coordinated, accurate, accessible, timely and complete information to the public and stakeholders during incident operations. • JIS operates across and supports the other NIMS structures: ICS, EOCs and MAC Group Slide 40 JIS Activities JIS activities include: • Coordinating interagency messaging • Developing, recommending and executing public information plans and strategies • Advising the Incident Commander or Unified Command, MAC Group and EOC director on public affairs issues • Addressing and managing rumors and inaccurate information A Joint Information Center (JIC) manages these JIS activities Slide 41 What Happened to Multiagency Coordination Systems (MACS)? • NIMS 2008 defined MACS as “the architecture to support coordination for incident prioritization, critical resource allocation communications systems integration and information coordination.” EOCs and MAC Groups were elements of MACS. • NIMS 2017 defines MACS as “an overarching term for the NIMS Command and Coordination systems: ICS, EOCs, MAC Group/ policy groups and JISs.” This broadens the definition of MACS to include the Command and Coordination architecture for tactical coordination (ICS), operational support coordination (EOCs), policy level coordination (MAC Group) and their support through coordinated information (JIS). Slide 42 NIMS Training Updates • Core EMI NIMS, ICS and EOC courses are in revision based on the NIMS 2017 publication • Current NIMS/ ICS courses will remain active until revised courses are available • EMI courses affected by changes in the NIMS 2017 are scheduled for revision during 2018 Slide 45 Sequence of NIMS Course Updates The first three EMI courses with updated NIMS content will be: • IS 0100: ICS-100 Incident Command System (ICS) • IS 0700: National Incident Management System (NIMS) • IS 0800: National Response Framework (NRF) Revision of additional courses for ICS and EOCs will follow. Slide 46 Incident Command System (ICS) Training Recommended Sequence of ICS Training All Emergency Management Practitioners • IS 0100: Introduction to the Incident Command System, ICS 100 • IS 0700: National Incident Management System (NIMS), An Introduction Emergency Management Supervisors add • IS 0200: Incident Command System for Single Resources and Initial Action Incidents • IS 0800: National Response Framework, An Introduction Advanced NIMS Training for ICS Leaders/ Supervisors • G 0191: ICS/EOC Interface • E/L/G 0300: Intermediate ICS for Expanding Incidents • E/L/G 0400: Advanced ICS for Command and General Staff • NIMS ICS All Hazards Position Specific Courses (E/L/G 0949-0991) Slide 47 Extended Alt Text slides for 508 Compliance Slide 50 Alternative Text Slide 18 The graphic depicts the NIMS Resource Management process. The Resource Management Process defines the six resource management tasks performed in an incident. At the beginning of the cycle incident objectives, strategies and tactics are used to identify resource requirements. In the second step these resource requirements are ordered and acquired. In the third step the resources are mobilized. In the fourth step these resources are tracked and reported on during utilization. In the fifth step the resources are demobilized when no longer required for the incident. Finally, the cost of using the resource is reimbursed to the resource’s owner, and any depleted items are restocked for future requirements. Return to Previous slide Slide 51 Alternative Text Slide 29 The graphic depicts the Planning “P” chart. The Planning “P” process begins with the initial response and the information gathering and sharing. The steps in these processes are incident/threat, notification, initial response and assessment, agency administrator briefing (if appropriate), incident briefing ICS 201, initial UC meeting (if Unified Command), IC/UC sets initial incident objectives, and initial strategy meeting and information sharing. After this initial step the process moved to being a cycle of tactics meeting, preparing for planning meeting, planning meeting, IAP preparation and approval, operational period briefing, begin operational period, execute plan and assess progress, IC/UC validate or adjust objectives, strategy meeting if objectives adjusted, and then back to tactics meeting to begin the cycle over again. Information gathering and sharing is happening continuously throughout this process. Return to Previous Slide Slide 52