1 / 66

National Incident Management System Incident Command System

National Incident Management System Incident Command System. Craig R. Savageau, M.S. HCMG, EMT-P Educator Office of Disaster Preparedness Saint Barnabas Health Care System. WHY NIMS?. Presidential Decision Directive -5 Preparedness funding tied to compliance Executive Order 50

nixie
Download Presentation

National Incident Management System Incident Command System

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 SystemIncident Command System Craig R. Savageau, M.S. HCMG, EMT-P Educator Office of Disaster Preparedness Saint Barnabas Health Care System NIMS/ICS Introduction

  2. WHY NIMS? • Presidential Decision Directive -5 • Preparedness funding tied to compliance • Executive Order 50 • JCAHO Environment of Care • E.C. 1.4 e. Definition of a common (that is, "all-hazards") command structure within the organization for responding to and recovery from emergencies, that links with the command structure in the community. • It works! NIMS/ICS Introduction

  3. What about HEICS? • Hospital Emergency Incident Command System • A version of ICS/IMS developed for hospitals • Not specifically NIMS compliance • HEICS and ICS have minor differences, defeating the intent of NIMS • Concepts of HEICS can still be used while maintaining NIMS compliance • Job Action Sheets NIMS/ICS Introduction

  4. History of ICS • Developed in the 1970s as a result of devastating wildfires in California • Needed a system to work toward common goals in efficient and effective manner • Organizational charts and other techniques taken from business management principles NIMS/ICS Introduction

  5. The Incident Command System… • IS a system to provide management during emergencies • IS NOT an emergency operations plan • DOES assist in developing an incident specific management structure • DOES NOT replace existing hospital management structures NIMS/ICS Introduction

  6. Without an Incident Management System… • CHAOS would result! NIMS/ICS Introduction

  7. Incident Command System • Can be used for any size emergency – large or small • Uses common terminology and operating procedures • Timely combining of resources during an emergency • System for controlling personnel, equipment, facilities, and communication NIMS/ICS Introduction

  8. UNDERSTANDING ICS KEY ELEMENTS • Common Terminology • Modular Organization • Management by Objectives • Incident Action Plans • Manageable Span of Control • Predestinated Incident Facilities • Resource Management • Integrated Communications • Establishment and Transfer of Command • Unity of command and Chain of Command • Unified Command • Accountability • Deployment • Information or Intelligence Management • Flexibility NIMS/ICS Introduction

  9. Emergency Operations Center • The center formerly know as the “Command Center” • Emergency Operations Center is the correct NIMS terminology NIMS/ICS Introduction

  10. Emergency Operating Centers (EOC) • The EOC is a pre-designated facility established by an agency to coordinate the overall response and support to an emergency. NIMS/ICS Introduction

  11. EOC Mission • Communication and Intelligence • Strategic Direction • Coordination and Documentation NIMS/ICS Introduction

  12. When do we activate the EOC? NIMS/ICS Introduction

  13. NIMS/ICS Introduction

  14. Predesignated Incident Facilities • Established by the Incident Commander based on the requirements and complexity of the incident. Base Incident Command Post Base Staging Area Camp NIMS/ICS Introduction

  15. Command Post • Dedicated central location • Isolated from noise and other distractions • Status board and other visual aids • Let people know where it is and how to contact the CP NIMS/ICS Introduction

  16. Staging Area • An area where resources are kept awaiting assignment • May be pre-designated • May be multiple staging areas per incident NIMS/ICS Introduction

  17. Incident Facilities: Base • Base: • Is the location from which primary logistics and administrative functions are coordinated and administered. There is only one Base per incident, and it is designated by the incident name. • May be collocated with the Incident Command Post. • Is established and managed by the Logistics Section. The resources in the Base are always out of service. B Symbol NIMS/ICS Introduction

  18. Incident Facilities: Camps • Camps: • Are where resources may be kept to support incident operations if a Base is not accessible to all resources. Multiple Camps may be used, but not all incidents will have Camps. • Are temporary locations within the general incident area that are equipped and staffed to provide food, water, sleeping areas, and sanitary services. • Are designated by geographic location or number. C Symbol NIMS/ICS Introduction

  19. Tactical Resources Classifications • Currently working on an assignment under the direction of a supervisor Assigned • Ready for immediate assignment and has been issued all requiredequipment Available • Not available or ready to be assigned (e.g., maintenance issues, rest periods) Out-of- Service NIMS/ICS Introduction

  20. Other Incident Facilities • HELISTOP • HELIBASE NIMS/ICS Introduction

  21. UNDERSTANDING ICS Common terminology • ICS uses standardized titles for positions, organizational levels, and facilities • Allows for easier communication and organization between agencies NIMS/ICS Introduction

  22. UNDERSTANDING ICS Modular Organization • Only the parts of the organization chart that are needed for the incident are activated • Positions can stand up, and stand down as needed • ICS is designed to expand or contract to fit the needs of the incident • Levels can be added or deactivated depending on the size, scope, and/or nature of the incident NIMS/ICS Introduction

  23. UNDERSTANDING ICS Span of control • Difficult and inefficient for one person to manage too many or too few people • In order to maintain span of control, one person should only manage between 3-7 people/units (ideally 5) • Less than 3 people/units – consider dissolving the supervisory position • More than 7 people/units – an additional level of management should be added NIMS/ICS Introduction

  24. UNDERSTANDING ICS Unity of command • Each unit or person within ICS should answer to ONE person • Multiple superiors can lead to an inability to handle assigned tasks, or leave objectives unattained • Staff accountability • More effective flow of communication NIMS/ICS Introduction

  25. UNDERSTANDING ICS • Unified Command concept • Senior-level SMEs from different agencies/departments make joint decisions on strategic objectives • Each “discipline” has a say in the decision-making process • Communication and directives flow outward from unified command to various branches in the table of organization NIMS/ICS Introduction

  26. UNDERSTANDING ICS Unified Command Continued: • Sharing of information, resources, and responsibility to ensure the smooth and efficient delivery of services • One person (the incident commander) is “in charge” and sets the direction and focus of the group NIMS/ICS Introduction

  27. Reliance on an Incident Action Plan • Every incident must have an Incident Action Plan (IAP) that: • Specifies the incident objectives. • States the activities to be completed. • Covers a specified timeframe, called an operational period. • May be oral or written—except for hazardous materials incidents, which require a written IAP. NIMS/ICS Introduction

  28. Elements of an Incident Action Plan • Every IAP must have four elements: • What do we want to do? • Who is responsible for doing it? • How do we communicate with each other? • What is the procedure if someone is injured? NIMS/ICS Introduction

  29. Primary ICS Functions Command Staff General Staff NIMS/ICS Introduction

  30. POSITIONS WITHIN ICS Incident Commander (IC) • Overall responsibility for the incident • Every incident MUST have an Incident Commander • First person on scene of an incident should establish a command • May be replaced by a more qualified person as additional units arrive (Delegation of Authority) NIMS/ICS Introduction

  31. POSITIONS WITHIN ICS Responsibilities of the Incident Commander • Establish scene safety • Request additional resources (if necessary) • Establish a staging area • Establish an Incident Command Post • Set incident objectives and priorities • Appoint personnel to function in other ICS positions NIMS/ICS Introduction

  32. POSITIONS WITHIN ICS Operations Section Chief • Work with the IC to ensure completion of goals • Develop tactical objectives • Manage units and resources to accomplish the objectives of the incident • Oversees ICS elements tasked with operations dedicated to resolving and mitigating the incident NIMS/ICS Introduction

  33. Levels of Organization • There can be additional levels of organization used under this (or any) section, known as: • Branches • Divisions • Groups • Task Force/Strike Team • Single Resources NIMS/ICS Introduction

  34. NIMS/ICS Introduction

  35. POSITIONS WITHIN ICS • Branches: • Used to manage assets to help maintain span of control, and are an intermediate management level between the Operations Section and lower levels • Can separate units by function, geography, or any other reason to maintain the span of control • Common examples are EMS Branch, Fire Branch, and Law Enforcement Branch • Are lead by Branch Directors • There may be one deputy for each Branch Director NIMS/ICS Introduction

  36. POSITIONS WITHIN ICS • Divisions: • Established to divide an area geographically • Named to describe the geographic area related to the incident operations • Lead by a supervisor • Not expected to need an assistant NIMS/ICS Introduction

  37. POSITIONS WITHIN ICS Groups: • Established to manage a functional area of operations within a branch or a section • Designed according to a specific task they are meant to carry out • Lead by a supervisor • Not expected to need an assistant NIMS/ICS Introduction

  38. POSITIONS WITHIN ICS Single Resource • A lone resource, self lead NIMS/ICS Introduction

  39. POSITIONS WITHIN ICS Task Force: • A collection of different resources tasked with a specific mission NIMS/ICS Introduction

  40. POSITIONS WITHIN ICS Strike Team: • A collection of like resources that may be tasked with any mission NIMS/ICS Introduction

  41. POSITIONS WITHIN ICS Planning Section • Responsible for developing short- and long-term plans • Collects, evaluates, and displays information about the incident • Maintains status of equipment and personnel • Maintains incident documentation • Led by Planning Section Chief NIMS/ICS Introduction

  42. POSITIONS WITHIN ICS Planning Section • May be broken down into the following units: • Resources Unit • Situation Unit • Documentation Unit • Demobilization Unit • Technical Specialists NIMS/ICS Introduction

  43. POSITIONS WITHIN ICS • Planning Section • Each unit is lead by a Unit Leader • May have a unit manager assigned to the Leader • Not all incidents will require the activation of a Planning Section, or all of the different units - in these cases the responsibilities of the section revert to the IC • When there is a Planning Section, but not all of the units are established, those responsibilities fall back on the Planning Section Chief NIMS/ICS Introduction

  44. POSITIONS WITHIN ICS Logistics Section • Responsible for all support and services needed at an incident - Personnel - Facilities - Equipment - Supplies NIMS/ICS Introduction

  45. POSITIONS WITHIN ICS • Logistics Section • This section will be established by the Incident Commander, depending on the needs of the incident • May be broken down into two functional Branches: • Service Branch • Support Branch • Each of these branches is overseen by a Branch Director • Each branch can contain three functional units; not all of these units may be required at a specific incident NIMS/ICS Introduction

  46. POSITIONS WITHIN ICS • Service Branch • Communications Unit • Medical Unit • Food Unit • Each unit is lead by a Unit Leader, who may be assisted by a Unit Manager • If the Logistics Section is not established, the responsibilities of that section falls back on the Incident Commander • If the Logistics Section is established, but the two branches are not, the responsibility of each branch falls back on the Logistics Section Chief • Support Branch • Supply Unit • Facilities Unit • Ground Support Unit NIMS/ICS Introduction

  47. POSITIONS WITHIN ICS Finance Section Chief • Oversees the Finance/ Administration section • Usually only utilized at large scale events • Responsible for tracking and recording costs and personnel time NIMS/ICS Introduction

  48. POSITIONS WITHIN ICS Finance • There can be four units established within this section: • Time Unit • Cost Unit • Procurement Unit • Compensation Unit • These units are established based on the particular needs of the incident, as deemed by the Incident Commander NIMS/ICS Introduction

  49. Common Responsibilities

  50. Mobilization • Only mobilize to an incident when requested or when dispatched by an appropriate authority. • Make sure that you receive a complete deployment briefing. NIMS/ICS Introduction

More Related