ICS 100/700 Training

1. ICS 100/700 Training George Hadley Based on Port of Seattle Fire course

2. Course Mechanics • Two answer sheets (one for IS-100 and one for IS-700) • Exam questions • Comments on slides correlate to questions (the comment would say “Look at ICS 100 test question 13 and fill in the answer on the answer sheet.”) 100-13

3. On February 28, 2003, President Bush issued Homeland Security Presidential Directive 5. HSPD–5 directed the Secretary of Homeland Security to develop and administer a National Incident Management System (NIMS). NIMS provides a consistent nationwide template to enable all government, private-sector, and nongovernmental organizations to work together during domestic incidents. Background

4. What is NIMS? NIMS is a comprehensive, national approach to incident managementbased on best practicesthat is applicable at all jurisdictional levels and across functional disciplines and is designed to: • Be applicable across a full spectrum of potential incidents and hazard scenarios. • Improve coordination and cooperation between public and private entities. 700-1

5. What is an Incident? An occurrence, caused by humans or natural phenomena, requiring response actions to prevent/ minimize loss of life or damage to property and/or the environment, including: • Fire, both structural and wildland. • Natural disasters, such as tornadoes, floods, ice storms or earthquakes. • Human and animal disease outbreaks. • Search and rescue missions. • Hazardous materials incidents. • Criminal acts and crime scene investigations. • Terrorist incidents, including the use of weapons of mass destruction. • National Special Security Events, such as Presidential visits or the Super Bowl. • Other planned events, such as parades or demonstrations. 100-4

6. NIMS Integration Center (1 of 2) The NIMS Integration Center has been established to oversee all NIMS-related aspects and is designed to: • Facilitate the development and dissemination of national standards, guidelines, and protocols for incident management training. • Facilitate the use of modeling and simulation in training and exercise programs.

7. NIMS Integration Center (2 of 2) • Facilitate general training requirements and approved training courses for all NIMS users. • Review and approves, discipline-specific training requirements and courses. • 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. 700-18 700-19

8. NIMS ComponentsOutline • Preparedness • Resource Management • Communications and Information Management • Supporting Technologies • Ongoing Management and Maintenance • Command and Management • Incident Command System (ICS)

9. NIMS ComponentsPreparedness • Preparedness involves all of the actions required to establish and sustain the level of capability necessary to execute a wide range of incident management operations: • Planning • Training and Equipping • Exercising and Evaluating • National-level preparedness standards related to NIMS will be maintained and managed through the NIMS Integration Center 700-15

10. NIMS ComponentsPreparedness Organizations Preparedness organizations at all levels must 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.

11. NIMS ComponentsPreparedness Organizations (cont.) • Establish guidelines and protocols to promote interoperability among jurisdictions and agencies. • Establish guidelines and protocols for resource management. • Establish priorities for resources and other response requirements. • Establish and maintain multi-agency coordination mechanisms. 700-16

12. NIMS ComponentsPreparedness Planning Jurisdictions must develop several types of plans, including: • Emergency Operations Plans (EOPs) which describes how the jurisdiction will respond to emergencies. • Procedures include overviews, standard operating procedures, field operations guides, job aids, or other critical information needed for a response.

13. NIMS ComponentsPreparedness Planning • Preparedness Plans which describe how training needs will be identified and met. • Corrective Action or Mitigation Plans which include activities required to implement procedures based on lessons learned from actual incidents or training and exercises. • Recovery Plans which describe the actions to be taken to facilitate long-term recovery. 700-17

14. NIMS ComponentsEffective Resource Management • Advance planning • Resource identification and ordering • Entry into mutual aid agreements ensure the timely delivery of resources during incidents Requests for items that the Incident Commander cannot obtain locally must be submitted through the EOC or Multi-Agency Coordination Entity 700-20 700-23

15. NIMS ComponentsEffective Resource Management • Planning for demobilization at the same as beginning the mobilization process • Tracking resources continuously from Mobilization to Demobilization • Recovering resources 700-24

16. NIMS ComponentsResource Categorization Categorizing resources into one of two categories: • Tactical Resources: Personnel and major items of equipment that are or are potentially available to the Operations function on assignment to incidents are called tactical resources. • Support Resources: All other resources required to support the incident. Food, communications equipment, tents, supplies, and fleet vehicles are examples of support resources.

17. NIMS ComponentsResource Categorization Resource standardization (within the two categories): • Resource “Typing” • Categorizing resources by capability based on measurable standards of capability and performance. • Certification and Credentialing • Helps ensure all personnel possess a minimum level of training, experience, physical and medical fitness, and capability for the position they are tasked to fill. 700-21 700-22

18. NIMS ComponentsBenefit to Resource Management Managers are able to identify, order, mobilize, dispatch, and track resources more efficiently

19. NIMS ComponentsCommunications and Information Communications and information management under NIMS are based on the following: • A common operating picture that is accessible across jurisdictions and agencies is necessary to ensure consistency amongst responders • Common communications and data standards are fundamental to Incident Management 700-25

20. NIMS ComponentsCommunications and Information Public Information Officer (PIO) advises Incident Commander on all matters related to public information • Operates within the parameters of the Joint Information System (JIS) • Information may be controlled using a central Joint Information Center (JIC) 700-12

21. NIMS ComponentsJoint Information Center Joint Information Center (JIC) is the physical location where public information staff involved in incident management activities can collocate to perform critical emergency information, crisis and communications.

22. NIMS ComponentsJoint Information Center Multiple JICs may be established: • Information must be coordinated among them to ensure that a consistent message is disseminated to the public • Each JIC must use JIS procedures and protocols for communicating and coordinating effectively with other JIC’s 700-14

23. NIMS ComponentsFeatures of JIC • Organizations retain their independence (even if used in a Unified Command) • The JIC includes representatives of all players in managing the response 700-13

24. NIMS ComponentsUnified Command • When there is more than one responding agency with responsibility for the incident, the leaders of which work together to form a Unified Commandof the incident • Unified Command work together to: • Analyze intelligence information • Establish a common set of objectives and strategies for a single Incident Action Plan 700-7

25. NIMS ComponentsArea Command • Area Command is established to: • Oversee the management of multiple incidents. • Oversee the management of large incidents that cross jurisdictional boundaries • Include incidents that are • Not site specific • Geographically dispersed • Evolve over time • Operations are conducted on the scene • Therefore, there is no Operations Section 700-8 700-9

26. NIMS ComponentsMulti-Agency Coordination System Multi-Agency Coordination Systems are a combination of resources that are integrated into a common framework for coordinating and supporting domestic incident management activities

27. NIMS ComponentsMulti-Agency Coordination System • Support incident management policies and priorities by: • Facilitate logistics support and resource tracking. • Make resource allocation decisions based on incident management priorities. • Coordinate incident-related information. • Coordinate interagency and intergovernmental issues regarding incident management policies, priorities, and strategies. 700-10

28. NIMS ComponentsEmergency Operations Center • Emergency Operations Center (EOC) organization and staffing is flexible, but should include: • Coordination. • Communications. • Resource dispatching and tracking. • Information collection, analysis, and dissemination. • EOCs may also support Multi-Agency Coordination and Joint Information activities 700-11

29. NIMS ComponentsIncident Command System (ICS) The Incident Command System (ICS) is: • A standard, on-scene, all-hazard incident management system. • A proven management system based on BEST PRACTICES. • The result of decades of lessons learned in the organization and management of emergency incidents. 700-3

30. NIMS/ICS Principles (1 of 2) 700-2 Promote inter-operability by: • Providing a FLEXIBLE framework that can adjust to accommodate incidents of any size. • Meeting the needs of incidents of any kind or size. • Allowing personnel from a variety of agencies to meld rapidly into a common management structure. 100-22

31. NIMS/ICS Principles (2 of 2) • Providing logistical and administrative support to operational staff. • Being cost effective by avoiding duplication of efforts. • Providing a STANDARDIZEDstructure for responding to and resolving incidents.

32. NIMS/ICS FeaturesOutline • Clear Communication • Modular Organization • Management by Objectives • Reliance on the Incident Action Plan (IAP) • Manageable Span of Control • Pre-designated Incident Facilities and Locations • Chain of Command and Unity of Command • Transfer of Command • Accountability (includes check-in/check out)

33. NIMS/ICS FeaturesClear Communication 100-7 • Common Terminology • Helps to ensure efficient, clear communication • Clear Text • Standardized Terms • Organizational Functions • Resource Descriptions • Incident Facilities • Position Titles

34. NIMS/ICS FeaturesModular Organization • ICS organizational structure develops in a top-down, modular fashion that is based on the size and complexity of the incident, as well as the specifics of the hazard environment created by the incident. • As incident complexity increases, the organization expands from the top down. • Only those functions that are necessary for a particular incident will be filled.

35. NIMS/ICS FeaturesManagement by Objectives • An approach used to communicate functional actions throughout the entire ICS organization • Objectives should be SMART • Specific • Measurable • Attainable • Relevant • Timely • Drives the formation of the Incident Action Plan 700-6

36. NIMS/ICS FeaturesReliance on Incident Action Plan • Every incident must have a written or oral Incident Action Plan (IAP) to provide all incident supervisory personnel with direction for taking actions based on the objectives identified in the Plan during the operational period. • An IAP is an oral or written plan that communicates measurable strategic objectives to be accomplished in the operation period. • Operation period usually equals 12 hours. 100-6

37. NIMS/ICS FeaturesReliance on Incident Action Plan An IAP MUST contain: • 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?  

38. NIMS/ICS FeaturesManageable Span of Control • Span of control pertains to the number of individuals or resources that one supervisor can manage effectively during emergency response incidents or special events. • Effective span of control: • Range: 3 – 7 resources per supervisor • Ideally 5 resources per supervisor 100-13 700-4

39. NIMS/ICS FeaturesIncident Locations & Facilities • Incident Command Post(ICP) is the location from which the Incident Commander oversees all incident operations. • Must be positioned outside the hazard but close enough to maintain incident command. • Staging Areas are temporary locations at an incident where personnel and equipment are staged while awaiting tactical assignment. • Base is the location from which primary logistics and administrative functions are coordinated and administered. 100-18 100-16

40. NIMS/ICS FeaturesIncident Locations & Facilities • Campis the location where resources may be kept to support incident operations if a Base is not accessible to all resources. • Helibase is the location from which helicopter-centered air operations are conducted . • Helispotsare more temporary locations at the incident, where helicopters can safely land and take off. 100-23

41. NIMS/ICS FeaturesChain and Unity of Command • Chain of command means that there is an orderly line of authority within the ranks of the organization. • Unity of command means that every individual is accountable to only one designated supervisor to whom they report at the scene of an incident.

42. NIMS/ICS FeaturesTransfer of Command The process of moving the responsibility for incident command from one Incident Commander to another and always includes a briefing.

43. NIMS/ICS FeaturesTransfer of Command Transfer of command may take place when: • A more qualified person assumes command. • Transfer of Command is NOT required when a higher ranking officer arrives on scene • The incident situation changes over time, resulting in a legal requirement to change command. • Changing command makes good sense, e.g., an Incident Management Team takes command of an incident from a local jurisdictional unit due to increased incident complexity. • There is normal turnover of personnel on long or extended incidents, i.e., to accommodate work/rest requirements. • The incident response is concluded and incident responsibility is transferred back to the home agency.

44. NIMS/ICS FeaturesAccountability • Orderly Chain of Command • Resource Tracking • Incident Record Keeping  • Check-In

45. NIMS/ICS FeaturesPersonnel Check-In • Check-in officially logs you in at the incident • Each responder must check in only once • After check-in, responders must locate their incident supervisor and obtain their initial briefing • Check-in helps to: • Ensure accountability • Track resources • Prepare personnel for assignment • Organize demobilization • Locate personnel in the event of an emergency 100-21 100-19

46. Incident Commander Public Information Officer Liaison Officer Command Staff Safety Officer Operations Section Logistics Section Finance/Admin Section General Staff Planning Section ICS Organization 100-5 100-2

47. ICS Organization • The ICS Organization does not correlate to any single agency • Highest ranking official in the organization’s day-to-day operations may not be the most qualified to manage an incident

48. NIMS/ICS FeaturesStandardized Position Titles • At each level of the ICS Organization, individuals of primary responsibility have distinct titles which serves the following purposes • Titles provide a common standard for all users • Distinct titles for ICS positions allows for filling ICS positions with the most qualified individuals rather than by rank or seniority • Standardized position titles are useful when requesting qualified personnel • ICS utilizes standardized position titles and structure to avoid confusion between the incident and a person’s day-to-day position • Confusion over position titles has been a significant stumbling block in the past 100-11 100-8 700-5

49. NIMS/ICS FeaturesPosition Titles

50. NIMS/ICS FeaturesIncident Command • Incident Commander is the one position that is always staffed • The Incident Commander is always a highly qualified individual trained to lead the incident response • Incident Commander has overall responsibility for managing the incident by objectives, planning strategies, and implementing tactics • Incident Commander must be fully briefed and should have a written delegation of authority 100-3