ICS Overview

1. ICS Overview

2. What Is an Incident? • An incident is . . . . . . an occurrence, either caused by human or natural phenomena, that requires response actions to prevent or minimize loss of life, or damage to property and/or the environment.

3. What Is ICS? • The Incident Command System is a standardized on-scene, all-hazard management approach used throughout the lifecycle of an incident. • The Incident Command System may be used to manage both emergency & non-emergency situations by both government & private-sector organizations. A few examples would be: • A training conference • Planning a community event including a parade, fair or large sporting event • A visit from a foreign dignitary.

4. What Is ICS? The Incident Command System is a standardized approach to incident management that is applicable for use in all hazards by all levels of government.

5. ICS Purposes • Using management best practices, the Incident Command Systems (ICS) helps to address: • The safety of responders and others. • The achievement of tactical objectives. • The efficient use of resources. • Lack of accountability including unclear chains of command and supervision.

6. History of ICS • Historically, the reason for most incident response failures were due to: • Lack of accountability. • Poor communication & management. • Lack of a planning process. • Poor management; overloaded Incident Commanders. • No method to integrate interagency requirements. • The identification of these areas of management weakness resulted in the development of ICS.

7. History of ICS • After-action reports from ineffective incident responses find that response problems are far more likely to result from: • Inadequate management. • Lack of an orderly, systematic planning process. • No common, flexible, predesigned management structure that enabled commanders to delegate responsibilities and manage workloads efficiently.

8. Homeland Security Presidential Directives (HSPDs) • Management of Domestic Incidents • Established standardized organizational structure for communication to use in response to natural, technological & manmade incidents. HSPD-5 HSPD-8 National Preparedness Mandates • National Preparedness Goal • National Incident Management System (NIMS) • National Response Framework (NRF)

9. National Incident Management System (NIMS) • NIMS is a consistent, nationwide approach for all levels of government to work effectively and efficiently together. • NIMS was called for in Homeland Security Directive (SHPD-5) in February of 2003. • NIMS is a core set of concepts, principles and terminology for incident command & multiagency coordination.

10. National Response Framework (NRF) • NRF: Establishes . . . • Federal coordination structures/mechanisms. • Direction for incorporation of existing plans. • Consistent approach to managing incidents. • When a variety of agencies are involved in a response, the Incident Command System supersedes the National Response Framework.

11. ICS Benefits • Meets the needs of incidents of any kind or size. • Allows personnel from a variety of agencies to meld rapidly into a common management structure. • Provides a preset structure for logistical and administrative functions in an emergency. • Is cost effective by avoiding duplication of efforts. And oversees efficient use of resources.

12. Summary • ICS . . . • Is a standardized management tool for meeting the demands of small or large emergency or nonemergency situations. • Represents "best practices," and has become the standard for emergency management across the country. • May be used for planned events, natural disasters, and acts of terrorism. • Is a key feature of NIMS.

13. Basic Features of ICS

14. Common Terminology • Using common terminology is critical to ensure efficient, clear communication to define: • Organizational functions. • Incident facilities. • Resource descriptions. • Position titles. To emphasize… ICS facilitates the ability to communicate by using Common Terminology.

15. Use of Plain English • When communicating, ICS requires the use of plain English. • Do not use agency-specific codes, radio codes, or jargon. EMT = Emergency Medical Treatment EMT = Emergency Medical Technician EMT = Email Money Transfer Even if you use radio codes on a daily basis, why should you use plain English during an incident response?

16. Modular Organization • Develops in a top-down, modular fashion. • Is based on the incident size,complexity and type of hazard. • Incident objectives determine the organizational size. • Only functions/positions that are necessary will be filled. • Each element must have a person in charge.

17. Overall Priorities • Incident objectives are established based on the following priorities: • #1: Life Saving • #2: Incident Stabilization • #3: Property Preservation

18. Reliance on an Incident Action Plan • Every incident must have an Incident Action Plan (IAP) that: • Specifies measurable strategic objectives to be achieved within the specified period. • Covers a specified timeframe, called an operational period. • Provides direction to take actions based on the objectives identified in the plan during the operational period. • May be oral or written—except for hazardous materials incidents, which require a written IAP.

19. Unity of Command • Under unity of command, personnel: • Report to only one supervisor. • Receive work assignments only from their supervisors. Don’t confuse unityof command with Unified Command!

20. Unified Command • Creates a single ICS structure with a built-in process for effective and responsible multijurisdictional or multiagency approach. • In a complex incident there are multiple Incident Commanders representing multiple jurisdictions working together to establish incident objectives.

21. Agency 1 Incident Commander Agency 2 Incident Commander Agency 3 Incident Commander Unified Command • Enables multiple Incident Commanders of all responsible agencies to work together to establish the incident objectives and strategies. • Incident Commanders within the Unified Command make joint decisions and speak as one voice establishing a single command structure.

22. Unified Command • Enables agencies with different legal, geographic and functional responsibilities to coordinate, plan and interact effectively. • Maintains unity of command. Each employee only reports to one supervisor.

23. Manageable Span of Control • Span of control: • Pertains to the number of individuals or resources that one supervisor can manage effectively during an incident. • 3-7 subordinates however 5 is ideal • Is key to effective and efficient incident management. Supervisor Resource 1 Resource 3 Resource 2

24. 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

25. Transfer of Command • Moves the responsibility for incident command from one Incident Commander to another. • Must include a transfer of command briefing for the incoming Incident Commander (may be oral, written, or both) • Must notify all personnel that a change in command is taking place. • Any Incident Commander is responsible until authority is delegated to another person.

26. Transfer of Command May take place when: • The current Incident commander needs rest • A jurisdiction or agency is legally required to take command • The incident changes in complexity • A more qualified Incident Commander arrives and assumes command.

27. Summary • ICS: • Utilizes management features including the use of common terminology and a modular organizational structure. • Emphasizes effective planning through the use of management by objectives and Incident Action Plans. • Supports responders by providing data they need through effective information and intelligence management.

28. Summary continued • ICS: • Utilizes the principles of chain of command, unity of command, Unified Command, and transfer of command. • Helps ensure that resources are ready through accountability and mobilization. • Ensures full utilization of incident resources by maintaining a manageable span of control, establishing predesignated incident facilities, implementing resource management practices, and ensuring integrated communications.

29. Incident Commander and Command Staff Functions

30. Command Staff General Staff Incident Commander • The Incident Commander performs all major ICS command and staff responsibilities unless the ICS functions are delegated and assigned. Incident Commander Public Information Officer Liaison Officer Safety Officer Operations Section Chief Planning Section Chief Logistics Section Chief Finance/Admin Section Chief

31. Incident Commander Role • The Incident Commander: • Provides overall leadership for incident response. • Delegates authority to others. • Takes general direction from agency administrator/official. • Only position that is always filled • Is responsible for all activities and functions until delegated and assigned to staff. • Assesses need for staff. • Establishes incident objectives. • Directs staff to develop the Incident Action Plan. Incident Commander

32. Command Staff Command Staff • It may be necessary for the Incident Commander to designate a Command Staff who: • Provide information, liaison, and safety services for the entire organization. • Report directly to the Incident Commander. Incident Commander Public Information Officer Liaison Officer Safety Officer

33. General Staff Functions

34. General Staff • Expanding incidents may require delegation of authority to perform operations, planning, logistics and finance/administration functions Incident Commander Public Information Officer Command Staff Liaison Officer Safety Officer General Staff Operations Section Planning Section Logistics Section Finance/Admin Section

35. Operations Section Chief The Operations Section Chief: • Develops the tactical objectives and organization. • Directs all tactical field resources. • Conducts and coordinates all incident tactical operations Operations Section Chief

36. Use of Position Titles • Using specific ICS position titles: • Provides a common standard across all responder • Allows ICS positions to be filled by the most qualified individuals rather than just being filled by rank alone. • Standardizes communication. • Describes the responsibilities of the position.

37. Planning Section Chief • The Planning Section Chief: • Collects and evaluates information throughout the incident and during the after-action review process. • Maintains resource status. • Prepares and copies the Incident Action Plan and necessary maps. • Maintains documentation for incident records. Planning Section Chief Incident Commander General Staff Operations Section Planning Section Logistics Section Finance/Admin Section

38. Planning Section • Track the status of all resources. • Maintains and displays situation status. • Prepares the Incident Action Plan. • Develops alternative strategies. • Provides documentation services. • Prepares the Demobilization Plan. • Provides a primary location for Technical Specialists assigned to an incident.

39. Logistics Section Chief • The Logistics Section Chief: • Provides support, resources and services needed to meet incident activities. • Ensures personnel have food, communications, medical support, and transportation as needed to meet incident objectives. • Contracts for and purchases goods and services needed at the incident. Logistics Section Chief Incident Commander Planning Section Logistics Section Finance/Admin Section Operations Section

40. Logistics Section Logistics Section • Make sure all incident personnel have what they need: • Communications • Provides communication planning and resources. • Support: • Medical support • Food • Ground support • Supplies & equipment • Facilities Service Branch Support Branch Commun. Unit Supply Unit Medical Unit Facilities Unit Food Unit Ground Unit

41. Finance/Administration Section Chief • The Finance/Admin Section Chief: • Manages costs related to the incident. • Provides accounting, procurement, time recording and cost analyses • Responsible for compensation for injury or damage to property. Finance/Administration Section Chief Incident Commander Planning Section Logistics Section Finance/Admin Section Operations Section

42. Common Responsibilities

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

44. Check-In at the Incident: Purpose • The check-in process helps to: • Track resources. • Prepare personnel for assignments and reassignments. • Organize the demobilization process. • Locate personnel in case of an emergency. • Establish personnel time records and payroll documentation. • Check in only once at an authorized location

45. Current situation assessment and objectives Specific job responsibilities Location of work area Procedural instructions for obtaining additional resources Safety hazards and required safety procedures/Personal Protective Equipment (PPE), as appropriate Initial Incident Briefing After you check-in, locate your incident supervisor and obtain your initial briefing.

46. Supervisory Responsibilities • If you are a supervisor, you must: • Maintain a daily unit log indicating the names of personnel assigned and a listing of the major activities that occurred during the operational periods to which you were assigned. • Provide briefings to your subordinates, adjacent forces, and replacement personnel.

47. Be Accountable for Your Actions • Maintain chain of command and unity of command. Take direction from a single supervisor. • Communicate potential hazards and changing conditions using clear text and Plain English. • Act professionally and avoid/report prohibited activities such as: • Sexual harassment or discrimination. • Use of illegal drugs or alcohol.