1 / 60

National Incident Management System - An Introduction (IS-700)

National Incident Management System - An Introduction (IS-700). National Incident Management System. NIMS grew out of Federal concern with the absence of an ICS that was standard across the nation.

gail
Download Presentation

National Incident Management System - An Introduction (IS-700)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. National Incident Management System-An Introduction(IS-700)

  2. National Incident Management System NIMS grew out of Federal concern with the absence of an ICS that was standard across the nation. While originally ICS was the focus, NIMS soon grew into an entire emergency management organization system. NIMS is extremely similar to the California Standardized Emergency Management System (SEMS)

  3. The National Incident Management System • Homeland Security Presidential Directive 5 ordered the establishment of a National Incident Management System (NIMS). • NIMS provides a consistent nationwide approach for responding to all kinds of incidents – no matter what the size, scope, cause or complexity.

  4. The National Incident Management System A comprehensive, national approach to incident management • Applicable at all jurisdictional levels and • across functional disciplines • Be applicable across a full spectrum of hazard • scenarios • Improve coordination and cooperation • between public and private entities

  5. The National Incident Management System What is the chief benefit of NIMS? • It is Applicable across jurisdictions and functions. • Used for all types of emergencies • Encourages interoperability • Enhances the ability of different classes of responders to work effectively together

  6. The National Incident Management System CONCEPTS and PRINCIPLES • NIMS provides a flexible framework • that facilitates government and • private entities working together to • manage domestic incidents. • NIMS provides a set of standardized • organizational structures, as well as • requirements for processes, procedures, • and systems.

  7. National Incident Management System Components NIMS is comprised of several components that work together as a system to provide a national framework for preparing for, preventing, responding to, and recovering from domestic incidents • Command and Management • Supporting Technologies • Preparedness • Ongoing Management and Maintenance • Resource Management • Communication and Information Management

  8. National Incident Management System COMPONENT 1 Command and Management Under NIMS

  9. Incident Command And Management • NIMS employs two levels of incident management structures • depending upon the nature of the incident (ICS and MACS). • NIMS requires that responses to all domestic incidents utilize a • common management structure. • ICS represents organizational “best practices” and has • become the standard for incident management across the • country • ICS is interdisciplinary and organizationally flexible to meet the • needs of incidents of any kind, size or complexity.

  10. Features of the Incident Command System ICS has several features that make it well suited to managing incidents. • Common terminology • Organizational resources • Manageable Span of Control • Organizational facilities • Use of position titles • Reliance on an Incident Action • Plan (IAP) • Integrated communications • Accountability

  11. Features of the Incident Command System (2) • Common Terminology • The ability to communicate within ICS is critical • ICS requires the use of common terminology • In addition to standard titles for facilities and positions, the use of • “clear text” is essential Uncommon Terminology: “Response Branch, this is HazMat1. We are 10-24.” Common Terminology: “Response Branch, this is HazMat1. We have completed our assignment.”

  12. Features of the Incident Command System (3) • Organizational Resources • Resources are “typed” with respect to capability; i.e., personnel, facilities, major equipment. • Manageable Span of Control • Maintaining adequate span of control throughout the ICS • organization is critical. • Effective span of control may vary from three to seven.

  13. Features of the Incident Command System (4) • Organizational Facilities Common terminology is also used to: • Define incident facilities • Help clarify the activities that take place at a specific facility • Identify organizational members • at the facility

  14. Features of the Incident Command System (5) • Use of Position Titles ICS positions have distinct titles • Only the Incident Commander is called “Commander” • Only the heads of Sections are called “Chief” • Learning and using standard terminology helps reduce • confusion between the day-to-day position occupied by an • individual and his/her position at or during the incident

  15. ICS Position Titles and Organizational Levels Use of Position Titles – Supervisory Levels

  16. ICS Relies on Incident Action Plans Reliance On An Incident Action Plan • IAPs provide a coherent means to communicate the overall • incident objectives in the context of both operational and support • activities. • IAPs depend on management by objectives to accomplish • response tactics. • Objectives are used to: • Develop and issue assignments, plans, procedures and protocols • Direct efforts to attain the objectives in support of defined strategies

  17. ICS Requires Integrated Communications Integrated Communications Integrated communications include: • The “hardware systems that • transfer information • Planning for the use of all • available communication • frequencies and resources • The procedures and processes • for transferring information

  18. Accountability is a Critical ICS Feature Accountability • Effective accountability at all jurisdiction levels and within • individual functional areas during an incident is essential. • To that end, ICS requires: • An orderly chain of command • Check-in for all responders • Unity of command

  19. NIMS produces two familiar concepts but gives them new (or federal specific) meanings NIMS recommends variations in incident management. The two most common variations involve the use of: UNIFIED COMMAND AND AREA COMMAND

  20. Unified Command means grouping together many agencies with different functions UNIFIED COMMAND Multi-Agency Response UNIFIED COMMAND ( Fire, Police, EMS, Public Works ) Operations Planning Logistics Finance/ Administration Example of Unified Command: A hazardous materials spill that contaminates a nearby reservoir may require that FD, Water Authority, LEPC, Health and Environment respond to the incident.

  21. UNIFIED COMMAND How Does It Work? • Agencies work together to: • Analyze Intelligence Information • Establish Objectives and Strategies for a single IAP • Unified Command does not change other features of ICS • Participate in the decision-making process

  22. Area Command is used to group responses to multiple incidents in the same jurisdiction or incidents with a response area that crosses jurisdictions AREA COMMAND ICP 3 ICP 1 ICP 2 An Area Command is an organization established to oversee the management of: • Multiple incidents, each being managed by an ICS of its own • Large incidents that cross jurisdictional boundaries Area Command is particularly relevant to public health emergencies because these incidents are typically not site specific and may cross jurisdictions

  23. Area Command: What does it do? The Area Command has responsibility for: • Setting overall strategy and priorities • Allocating critical resources • Ensuring proper incident management • Ensuring that objectives are met. • Ensuring that strategies are followed.

  24. Area Command: How is it organized? AREA COMMAND Finance Planning Logistics An Area Command is organized similarly to a an ICS structure, but ... Because operations are conducted on-scene, and area commands are not scene based, there is no Operations Section

  25. Multi-agency Coordinating Systems (What Are They?) MACS are a combination of resources that are integrated into a common framework for coordinating and supporting domestic incident management activities. These resources MAY include: • Facilities • Equipment • Personnel • Procedures • Communications

  26. Multi-agency Coordinating Systems (What Do They Do?) The primary functions of Multiagency Coordination Systems are to: • Support incident management policies and priorities • Facilitate logistics support and resource tracking • Coordinate incident related information • Coordinate interagency and intergovernmental issues regarding • incident management policies, priorities, and strategies

  27. Multi-agency Coordinating Systems (What Do They Do?) The primary functions of Multi-agency Coordination Systems are to: • Support incident management policies and priorities • Facilitate logistics support and resource tracking • Coordinate incident related information • Coordinate interagency and intergovernmental issues regarding • incident management policies, priorities, and strategies • Make resource allocation decisions based on incident • management priorities

  28. Multi-agency Coordinating Systems Elements Multi-agency Coordinating Systems include EOCs and in certain multi-jurisdictional or complex incidents, Multi-agency Coordination Entities • Emergency Operations Center • Locations from which coordination of information and resources • take place. • Are typically established by the emergency management agency at the • local, tribal or State levels. • Multiagency Coordination Entity • Typically consist of principles from organizations with direct incident • management responsibilities, or with • Significant incident management support or resource capabilities

  29. Multi-agency Coordinating Systems Elements • Emergency Operations Centerorganization and staffing is flexible, but should include: • Coordination (Operations) • Communications (Logistics/Operations) • Resource dispatching and tracking (Logistics) • Information collection, analysis, and dissemination • (Planning/Logistics) EOCs may also support multi-agency coordination and joint information activities.

  30. Multi-agency Coordinating Systems Elements • Multi-agency Coordination Entity Incident Responsibilities include: • Ensuring each agency is providing necessary status information. • Establishing priorities between incidents • Acquiring and allocating required resources. • Coordinating and identifying future resource requirements. • Coordinating and resolving policy issues. • Providing strategic coordination.

  31. Multi-agency Coordinating Systems Elements • Multi-agency Coordination Entity Post-incident Responsibilities • Following an incident(s) MAC Entities are typically responsible for • ensuring revisions are acted on and may include revisions made to: • Plans • Procedures • Communications • Staffing •         Other capabilities necessary for improved • incident management.

  32. National Incident Management System Public Information

  33. Public Information Officer • Advises the Incident or SEOC Command on all public information • matters related to the management of the incident, including: • Media and public inquiries • Emergency public information and warnings • Rumor monitoring and control • Other functions necessary for coordinating, clearing and disseminating accurate and timely information • Establishes and operates within the parameters established for • the Joint Information System (JIS)

  34. Joint Information System (JIS) • Provides an organized, integrated, and coordinated mechanism for • providing information to the public in an emergency. • Key elements include: • interagency coordination and integration, • developing and delivering coordinated messages, and • support for decision-makers. • Includes plans, protocols, and structures used to provide information.

  35. Joint Information Center (JIC) (formerly JENC) • Provides a central location for integrated and coordinated information • across jurisdictions and agencies, • among all government partners, • the private sector, and • non-governmental agencies • The physical location where PI staff can co-locate to perform the • following functions: • critical emergency information, • crisis communications, and • public affairs.

  36. Joint Information Center (2) • Provides the organizational structure for coordinating and • disseminating official information. • Incident Commanders and Multiagency Coordinating Entities are • responsible for following functions: • establishing and overseeing JICs, including • processes for coordinating and clearing public information. • In Unified Command, those contributing to joint public • information management do not lose their individual identities • or responsibilities.

  37. Levels of Joint Information Centers • JICs may be established at all levels of • government. • All JICs must communicate and coordinate with each other • on an on-going basis using established JIS protocols.

  38. Joint Information Centers Characteristics JICs have several characteristics in common: • Includes representatives of all players in the management of an • incident . • Each JIC must have procedures and protocols for • communicating and coordinating effectively with other JICs and • appropriate ICS components. • A single JIC is preferable, but the JIS must be flexible to accommodate • multiple JICs.

  39. Typical Joint Information Center Organization Joint Information Center Press Secretary (jurisdictional) Liaison (as required) Media Team Logistics Team Research Team Additional functions may be added as required to meet the public information needs of the incident(s)

  40. National Incident Management System Preparedness Primarily applies to jurisdictions not fire departments. PFD maintains a planning process that produces SOPs and this process is on-going.

  41. What Is Preparedness? Preparedness: • Is a key, critical phase of the emergency management cycle. • Involves all of the actions required to establish and sustain the level • of capability necessary to execute a wide range of incident management • operations. • Is implemented through a continuous cycle of : • planning, • training and equipping, • exercising • evaluating, and • taking action to correct and mitigate.

  42. What Is Preparedness? (Continued) Preparedness: • Ensures mission integration and interoperability in response to • emergent crisis. • Includes efforts to coordinate between public and private sectors. • Is the responsibility of individual jurisdictions in coordinating their • activities among all preparedness stakeholders.

  43. Preparedness Tools NIMS provides tools to help ensure and enhance preparedness. These tools include: • Preparedness organizations and programs that provide or establish • processes for planning, training, and exercising. • Personnel qualification and certification • Equipment certification • Mutual aid • Publication management National-level preparedness standards related to NIMS will be maintained and managed through a collaborative process at the NIMS Integration Center

  44. Responsibilities of Preparedness Organizations Preparedness organizations at all levels should follow NIMS standards and undertake the following tasks: • Establish and coordinate emergency plans and protocols. • Integrate and coordinate the activities and jurisdictions within • their purview. • Establish guidelines and protocols to promote interoperability • among jurisdictions and agencies. • Adopt guidelines and protocols for resource management. • Establish priorities for resources and other response requirements. • Establish and maintain multi-agency coordination mechanisms.

  45. Preparedness Planning • Preparedness plans describe how personnel, equipment, and other • resources will be used to support incident management. • Plans represent the operational core of preparedness and provide • mechanisms for: • Setting priorities • Integrating multiple entities and functions • Establishing collaborative relationships • Ensuring that communications and other systems support the • complete spectrum of incident management activities.

  46. Types of Preparedness Plans Jurisdictions must develop and maintain several types of plans, including: • Emergency Operations Plans (EOPs) – How jurisdiction will respond • to emergencies. • Procedures – Overviews, SOPs, field operations guides, job aids, etc. • Preparedness Plans – How training needs will be identified and met, how • resources will be obtained, facilities and equipment required for hazards. • Corrective Action or Mitigation Plans – which includes activities • required to implement procedures based on lessons learned from actual • incidents or training and exercises. • Recovery Plans – Actions to be taken to facilitate long-term recovery

  47. Training & The NIMS Integration Center • Training and Exercises • Organizations and personnel at all levels (governmental and private sector) must: • Be trained to improve all-hazard incident management capability • Participate in realistic exercises to improve integration and interoperability. NIMS Integration Center To assist jurisdictions in meeting these needs the NIMS Integration Center will: • Facilitate the development and dissemination of national standards. • Facilitate the use of modeling and simulation in T&E programs. • Facilitate the definition of general training requirements and approved courses for all NIMS users. • Review and approve discipline-specific training requirements and courses.

  48. Personnel Qualification and Certification • Under NIMS, preparedness is based on national standards for the qualification and • certification of emergency response personnel. • Managed by the NIMS Integration Center standardization will help ensure a • jurisdictions key response personnel will possess minimum skills, knowledge, • and experience. Standards to include: • Training • Experience • Credentialing • Currency • Physical and mental fitness. • Personnel certified to support interstate incidents will be required to meet • national qualification and certification standards.

  49. NIMS Certification of Equipment • A critical component of operational preparedness is that equipment: • Performs to certain standards, and • Is compatible with equipment used by another jurisdiction. • To facilitate national equipment certification, the NIMS Integration Center will: • Facilitate the development and/or publication of national equipment • standards, guidelines, and protocols. • Review and approve lists of emergency responder equipment that • meet national requirements.

  50. Mutual Aid Agreements and EMAC Mutual Aid Agreements and the Emergency Management Assistance Compact: • Provide the means for one jurisdiction to provide resources or other support to • another during an incident. • Facilitates the timely delivery of assistance during an incident • Jurisdictions (including States) are encouraged to enter into agreements with: • Other jurisdictions • Private sector and non-governmental organizations • Private organizations, i.e., American Red Cross

More Related