ICS/SEMS/NIMS Combined Basic Curriculum. Student Manual

Transcription

1 ICS/SEMS/NIMS Combined Basic Curriculum Student Manual

2 Table of Contents Unit 1 Unit 2 Unit 3 Unit 4 Unit 5 Introduction and Course Overview Incident Command System (ICS) Multiagency Coordination System (MACS) and Mutual Aid Standardized Emergency Management System (SEMS) and National Incident Management System (NIMS) Course Summary and Close Appendix A Appendix B Appendix C Appendix D Appendix E Acronyms ESFs Mutual Aid Template IS Tests and Links ICS and SEMS Activities Table of Contents

3 Table of Contents This Page Intentionally Left Blank Table of Contents

4 Unit 1 Introduction and Overview

5 This Page Intentionally Left Blank

6 Unit 1 Introduction and Overview Duration 60 Minutes Scope Statement This unit provides participants with a review of course contents and delivery format, and an understanding of ICS/SEMS/NIMS. Terminal Learning Objectives Upon completion of this unit, participants will have an understanding of course contents and delivery format. Enabling Learning Objectives Identify course content, delivery format, schedule, objectives and instructors and participants expectations. Lesson Topics Course Overview Introductions Course Expectations Page 1.1

7 Resources Unit 1 Introduction and Overview Course Assessment Strategy Verbal and visual assessment of understanding Participation in introductions Question and answer period Instructor-to-Participant Ratio 1:25 Reference List Not Applicable Practical Exercise Statement Not Applicable Instructor Notes Instructor notes are contained throughout the lesson plan as appropriate Page 1.2

8 Unit 1 Introduction and Overview Slide 1 Slide 2 Course Manager Instructors Page 1.3

9 Unit 1 Introduction and Overview Slide 3 Name Job title and organization NIMS/SEMS experience One item on your Bucket List Slide 4 Schedule/Evaluation Sign-in sheet Breaks and Lunch Distractions Participant Manual Slide Formats Handouts EM Specialists Certificates Credentialing Page 1.4

10 Unit 1 Introduction and Overview Slide 5 Understand ICS/SEMS/NIMS Understand Mutual Aid Understand Multiagency Coordination Understand Common Operating Picture Understand Communications Understand Resource Management Slide 6 Page 1.5

11 Unit 1 Introduction and Overview This Page Intentionally Left Blank Page 1.6

12 Unit 2 Incident Command System (ICS)

13 This Page Intentionally Left Blank

14 Unit 2 Incident Command System (ICS) Duration 90 Minutes Scope Statement This unit provides participants with information about the Incident Command System, Command Staff, and Multiagency Coordination Terminal Learning Objectives Upon completion of this unit, participants will know how the Incident Command System works, who the Command Staff is and what Multiagency Coordination does. Enabling Learning Objectives Understand the Incident Command System Understand the Command Staff s role Understand Multiagency Coordination System Lesson Topics Incident Command System Command Staff Multiagency Coordination System Page 2.1

15 Unit 2 Incident Command System (ICS) Resources Course Handouts Activities Assessment Strategy Verbal and visual assessment of understanding Participation in activities and group discussions Question and answer period Instructor-to-Participant Ratio 1:25 Reference List Not Applicable Practical Exercise Statement Not Applicable Instructor Notes Instructor notes are contained throughout the lesson plan as appropriate Page 2.2

16 Slide 1 Unit 2 Incident Command System (ICS) Page 2.3

17 Slide 2 Unit 2 Incident Command System (ICS) Developed after a devastating 1970s wildfire in California Ineffective Response Firefighting RESources of California Organized for Potential Emergencies FIRESCOPE What is ICS ICS Structure Span of Control ICS was developed in the aftermath of a devastating 1970s wildfire in California where numerous problems were encountered. Response problems are likely to result from: Lack of accountability Poor communications Lack of orderly, systematic planning No common, flexible, pre-designated management structure No predefined methods to integrate interagency requirements into the management structure The U.S forest Service, Cal Fire and other Southern California fire agencies formed FIRESCOPE Firefighting RESources of California Organized for Potential Emergencies. ICS is a standardized approach to incident management. ICS: Enables coordinated response among various jurisdictions and agencies Establishes common processes for planning and managing resources Allows integration of facilities, equipment, personnel, procedures and communications ICS structure is flexible for any type, scope, and complexity of incident. The ICS structure is based on lessons learned, ensures safety of responders, achievement of objectives, and efficient use of resources. ICS structure is also used for natural, technological, human-caused hazards and planned events. Page 2.4

18 Unit 2 Incident Command System (ICS) Someone who serves as a director every day may not hold that title under ICS structure. Elected and appointed officials should not assume the role of incident commander for all incidents and direct the on-scene technical operations from the EOC. ICS uses the same management functions regardless of the size of the incident ICS Span of Control: Number of people one person can effectively supervise - between 3 and 7 subordinates with 5 being optimal. Page 2.5

19 Slide 3 Unit 2 Incident Command System (ICS) Common Terminology Modular Organization Management by Objectives Reliance on an Incident Action Plan The ability to communicate is absolutely critical. During an incident, communications should use common terms or clear text. Do not use radio codes, agency-specific codes, acronyms, or jargon. The goal is to promote understanding among all parties involved in managing an incident. Common Terminology or plain English allows diverse incident management and support organizations to work together. Common terminology covers organizational functions, resource description, and incident facilities. Incident response communications should feature plain language commands. Field manuals and training should be revised to reflect the plain language standard. ICS Structure develops in a top down modular fashion. ICS is based on the incident objectives and resource requirements; expands and contracts to use only those needed elements, and requires that each element has a person in charge. ICS structure is unique and has no correlation to most agency administrative structures. Incident objectives are used to ensure everyone in the ICS organization has a clear understanding of what needs to be accomplished. Incident objectives are established based on 1) Life Safety, 2) Property, and 3) Environment. Management by Objectives - Incident objectives are communicated throughout the ICS organization. This includes establishing overarching incident objectives; developing strategies based on the objectives; developing and issuing assignments, plans, procedures, and protocols; establishing specific, measurable tactics or tasks, and directing efforts to accomplish them; and documenting results to measure performance and facilitate corrective actions. Page 2.6

20 Unit 2 Incident Command System (ICS) Every incident must have an Incident Action Plan (IAP). An IAP provides a concise, coherent means of capturing and communicating the incident priorities, objectives, and strategies. Incident Action Plans Specify incident objectives and communication protocols State activities to be completed Cover a specified timeframe, called an operational period May be written or oral except for hazardous materials incidents, which require a written IAP Page 2.7

21 Slide 4 Unit 2 Incident Command System (ICS) Command Coordination Command Function Chain of Command Unity of Command Command: The act of directing, ordering, or controlling by virtue of explicit statutory, regulatory or delegated authority at the field level. Coordination: Provides support to the command structure and may include incident prioritization, critical resource allocation, communications systems integration, and information exchange Command Function: Must be clearly established at the beginning of incident or when command is transferred, the process must include a briefing Transfer of command is the process of transferring the responsibility for incident command from one Incident Commander to another. Transfer of Command may take place when: A more qualified Incident Commander assumes command Jurisdiction/agency is legally required to take command Incident changes in complexity The Incident Commander is always highly qualified and trained to lead incident response. Page 2.8

22 Unit 2 Incident Command System (ICS) Chain of Command is an orderly line of authority within the ranks of the incident management organization. The Chain of Command does NOT prevent personnel from directly communicating with each other to ask for or share information. Unity of Command means that every individual has one designated supervisor to whom he or she reports. Under Unit of Command personnel report to only one ICS supervisor and receive work assignments only from their ICS supervisor. When at an incident, you no longer report to your day-to-day supervisor. Page 2.9

23 Slide 5 Unit 2 Incident Command System (ICS) Command in the Field Command or Management Management in the EOC Management determines priorities, objectives, and strategic goals (Action Planning); manages organizational structure, event resources, coordinates event activities and activities of outside agencies, ensures safety, approves the EOC Action Plan, and authorizes release of information to the media. The Management Staff consists of Emergency Operations Center Director, Public Information Officer, Safety Officer and Liaison Officer. Operations manages all field activities, coordinates all tactical operations, assists the Director in developing strategic goals and objectives for the event, and develops operational plans. The Operations Staff consists of Police, Fire, EMS, and Mass Care and Shelter personnel. Planning/Intelligence manages Situation Status (past, present, predicted), Resource Status (present and predicted) and handles all documentation for the event. Planning responsibilities include Information Management, Planning for Operational Periods, Development of the Action Plan and Advance Planning. Logistics is responsible for providing facilities, services, and materials for the event. Logistics manages service and support resources and tracks resources. Finance & Administration takes care of all costs and financial considerations. Finance/Administration is responsible for future payments, budgeting, payment of personnel costs and cost recovery. Page 2.10

24 Slide 6 Unit 2 Incident Command System (ICS) Commander Incident Commander Responsibilities Deputy Incident Commander The agency with primary jurisdictional authority over the incident designates the individual at the scene responsible for establishing command. The Incident Commander (IC) is the only position that is always staffed. The IC develops the incident objectives that direct all subsequent incident action planning, approves the Incident Action Plan (IAP), and resources ordered or released. The IAP establishes the overall incident objectives, strategies, and tactics. The IC has overall responsibility for the incident and must have authority to manage the incident. The IC is designated with overall incident management responsibility. The Incident Commander should have the level of training, experience, and expertise to serve in this capacity. Qualifications to serve as an IC are not based on rant, grade, or technical expertise. The Incident Commander has overall responsibility for managing the incident by establishing objectives, planning strategies, and implementing tactics. The IC is responsible for ensuring the overall incident safety;. The IC provides information services to internal and external stakeholders; establishes and maintains liaison with other agencies; and may appoint one or more Deputy Incident Commanders. The Deputy Incident Commander must be qualified to assume the Incident Commander s Position. The Deputy IC performs specific tasks requested by the Incident Commander and performs the incident command function in a relief capacity. To maintain Span of Control, the Incident Commander first establishes the Operations Sections. The remaining Sections are established as needed to support the operation (Planning and Intelligence, Logistics, and Finance/Administration). Page 2.11

25 Slide 7 Unit 2 Incident Command System (ICS) Command Staff General Staff Command Staff consist of the Public Information Officer (PIO), Safety Officer, and Liaison Officer. Public Information Officer serves as the conduit for information to and from internal and external stakeholders, media and the public.. The PIO gathers, verifies, coordinates, and disseminates accurate, accessible, and timely information on the incident s cause, size, and current situation; resources committed; and other matters of general interest for both internal and external audiences. The Incident Commander must approve the release of all incident-related information. The PIO should participate in or lead the Joint Information Center (JIC) to ensure information is consistent. The JIC is a central location that facilitates operation of the Joint Information System (JIS).. The Joint Information System (JIS) is the framework for organizing, integrating, and coordinating the delivery of public information. The JIS provides a structure for developing and delivering incident-related messages by developing, recommending, and executing public information plans and strategies. Safety Officer: Monitors safety conditions and develops measures to ensure safety of incident personnel. The Safety Officer advises the Incident Commander on all matters relating to operational safety, including the health and safety of personnel assigned to the incident. Liaison Officer: Serves as the primary contact for other governmental and nongovernmental agencies and the private sector General Staff refers to Incident management personnel organized according to function, (Operations Chief, Planning & Intelligence Chief, Logistics Chief, and Finance & Admin Chief) and who report directly to the Incident Commander. Page 2.12

26 Slide 8 Unit 2 Incident Command System (ICS) Operations Chief (OPs Chief) Branches Divisions Groups Units Task Force Strike Teams Single Resources The Operations Chief is responsible for all tactical activities to reduce the immediate hazard, save lives, property, establish situational control, and restore normal operations. The Ops Chief reports to Incident Commander,. To maintain Span of Control, the Ops Section may use one or more of, the following elements Branches Have functional, geographic, or jurisdictional responsibility for major parts of the incident operations. The person is charge of a Branch is a Director. Division Has responsibility for operations within a defined geographic area. The person in charge of a Division is a Supervisor. Group Used to divide the incident into functional areas of operation. The person in charge of a Group is a Supervisor. Units Have functional responsibility for a specific incident planning, logistics, or finance/admin activity. The person in charge of a Unit is a Leader Task Forces - Group of mixed resources with common communications. The person in charge of a Task Force is a Task Force Leader Strike Teams - Specified combination of similar resources with common communications. The person in charge of a Strike Team is a Strike Team Leader Single Resource Individual piece of equipment and its personnel, or a crew of team of individuals. Page 2.13

27 Slide 9 Unit 2 Incident Command System (ICS) Plans/Intel Chief Plans/Intel Section Units The Planning/Intelligence Section collects, evaluates, and disseminates incident information and intelligence for the Incident Commander. The Plans/Intel Section Prepares status reports Displays situation information Maintains the status of resources assigned to the incident Prepares and documents the Incident Action Plan Develops Demobilization plans Plans/Intel Units include: Situation Unit: Collects, organizes and analyzes incident status information GIS Unit: Does all mapping of the incident Documentation Unit: Collects, records and maintains all documents relevant to the incident Advanced Planning Unit: Predict need for resources, sheltering, etc. for the next hours Resource Unit: Records the status of resources committed to the incident Demobilization Unit: Ensures orderly, safe and efficient demobilization of incident resources Technical Specialist: Personnel with special skills that can be used anywhere in the ICS organization Page 2.14

28 Slide 10 Unit 2 Incident Command System (ICS) Logistics Chief Logistics Section Branches The Logistics Chief ensures adequate resources are available (personnel, supplies and equipment) to meet the incident objectives. The Logistics Section is responsible for all services and support needs, including: Providing communication planning and resources Setting up food services for responders Setting up and maintaining incident facilities Providing support transportation Providing medical services to incident personnel Support Branch Supply Unit: Orders, receives, stores and processes all incident-related resources and supplies Ground Support Unit: Provides and maintains all ground transportation during an incident Facilities Unit: Sets-up, maintains and demobilizes all facilities in support of the incident Service Branch Food Unit: Fill food and water requirements, plans menus, orders food, provides cooking facilities Communications Unit: Provides communications planning and resources Medical Unit: Arrange for medical services for incident personnel Page 2.15

29 Slide 11 Unit 2 Incident Command System (ICS) Finance/Admin Chief Finance/Admin Units The Finance/Admin Chief sets up for incident specific financial management. The F/A Chief is responsible for Contract negotiation and monitoring Timekeeping Cost analysis Compensation for injury or damage to property Documentation for reimbursement (e.g. under mutual aid agreements and assistance agreements. Time Keeping Unit: Records time for incident personnel Cost Unit: Tracks costs, analyzes cost data, makes estimates and recommends cost savings Compensation/Claims Unit: Handles concerns resulting in property damage, injuries or fatalities at the incident Procurement: Responsible for vendor contracts Page 2.16

30 Slide 12 Unit 2 Incident Command System (ICS) Unified Command Area Commands Unified Command is two or more Commanders from various Jurisdictions who have jurisdictional authority, and operate together from a single command structure with a single set of incident objectives Unified Command uses collaborative strategies, reduces duplication, and maximizes use of resources. Unified Command enables agencies with different legal, geographic, and functional responsibilities to coordinate, plan, and interact effectively. Unified Command has the following features Single integrated incident organization Co-located (shared) facilities - One ICP Single Planning Process Single Incident Action Plan Area Command manages multiple incidents handled individually by separate ICS organizations. Area Command sets the overall strategy and priorities, and identifies and allocates resources. The Area Command ensures strategies are followed and objectives are met. Area Command maintains effective communication and assists in transition to full recovery operations Direct tactical and operational responsibility for conducting incident management activities rests with the Incident Command. Page 2.17

31 Slide 13 Unit 2 Incident Command System (ICS) Briefing Accountability Recordkeeping Demobilization Briefings must include the current situation, identify your specific job responsibilities, and describe ICS structure and your position. Briefings must also include procedures to obtain necessary resources, operational periods and safety procedures. Accountability during incident operations is essential. All responders must check-in to receive an assignment. Checking in ensures personnel accountability Track resources Prepare personnel for assignments, Locate personnel in case of emergency Establish personnel time records and payroll documentation, Plan for releasing personnel Organize the demobilization process. Everyone follows the Incident Action Plan. Each individual is assigned only one supervisor. Supervisors must be able to supervise and control their subordinates, and must record and report resource status changes. Recordkeeping requires printing all entries. Dates are in month/day/year format. Make sure the date and times are on all forms and records. Use local time in 24-hour military format (1:00 p.m. = 1300 hours). Resources are demobilized at the end of their assignment. Before checking out and leaving you should complete all tasks and required forms/reports. Brief replacements, subordinates, and supervisor. Evaluate the performance of subordinates, follow checkout procedures, and return any incident issued equipment or other expendable equipment. Complete post incident reports, time records, critiques, evaluations and medical follow-up. Page 2.18

32 Slide 14 Unit 2 Incident Command System (ICS) Incident Command Post Staging Area Base Camp Helibase Helispot ICS Incident Facilities are established by the Incident Commander based on the requirements and complexity of the incident. Incident Command Post Location where the Incident Commander oversees all incident operations. The Incident Commander directs operations from the ICP which is usually located at or in the immediate vicinity of the incident site. Staging Area A temporary location where personnel and equipment are gathered while waiting assignment Base - The location where primary logistics and administrative functions are coordinated and administered Camp Provides sleeping, food, water, and sanitary services to incident personnel Helibase A location where helicopter-centered air operations are conducted Helispot A temporary location where helicopters can safely land and take off Page 2.19

33 Slide 15 Unit 2 Incident Command System (ICS) You ve been tasked with setting up an Incident Command Post with an ICS Structure. Work in your groups What organizational functions of ICS structure need to be put in place? Who is involved? What is the time period to complete the activities? What area the top three priorities? What supporting resources/equipment/materials are needed? Is Mutual Aid required? Page 2.20

34 Slide 16 Unit 2 Incident Command System (ICS) Page 2.21

35 Unit 2 Incident Command System (ICS) This Page Intentionally Left Blank Page 2.22

36 Unit 3 Multiagency Coordination System (MACS) and Mutual Aid

37 This Page Intentionally Left Blank

38 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Duration 60 Minutes Scope Statement This unit provides participants with an overview of Multiagency Coordination System (MACS) and Mutual Aid Terminal Learning Objectives Upon completion of this unit, participants will understand the Multiagency Coordination System and how Mutual Aid works. Enabling Learning Objectives Identify the components and principles of the Multiagency System (MACS) Understand Mutual Aid Lesson Topics Multiagency Coordination System (MACS) Mutual Aid Page 3.1

39 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Resources Course Handouts Activities Assessment Strategy Verbal and visual assessment of understanding Participation in group discussions and activities Question and answer period Instructor-to-Participant Ratio 1:25 References Not Applicable Practical Exercise Statement Not Applicable Instructor Notes Instructor notes are contained throughout the lesson plan as appropriate Page 3.2

40 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 1 Page 3.3

41 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 2 Multiagency Coordination System (MACS) Multiagency Coordination is a process that allows all disciplines to work together more efficiently and effectively. Multiagency Coordination is defined as the architecture to support coordination for incident prioritization, critical resource allocation, communications systems integration, and information coordination. MACS occurs across the various disciplines involved in incident management, jurisdictional lines or levels of government. MACS can and does occur on a regular basis whenever personnel from different agencies interact in preparedness, prevention, response, recovery, and mitigation activities. MAC System: Dispatch Centers: Coordinates acquisition, mobilization and movement of resources Emergency Operation Center (EOC): Supports on-scene response by coordination and tracking of resources, communications, and information collection, analysis and dissemination. Department Operation Centers Equipment Personnel (can commit agency resources) Page 3.4

42 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 3 MAC Determinations MAC Readiness MAC Coordination defines business practices, standard operating procedures, processes, and protocols by which participating agencies coordinate their interactions. MACS provides support, coordination, and assistance with policy-level decisions to the ICS structure managing an incident. MACS may be as simple as a teleconference and may require an assembled group and associated support systems. There is no simple policy for activating MAC system: When Unified Command is established When more than one jurisdiction becomes involved in response When incident could expand rapidly When similar past events have required multiagency coordination When chief executive requests activation of MAC MACs may be necessary for Incident priority determination; critical resource acquisition and allocation; interagency activities relevant to incident management, and coordination. When multiple layers of a MAC System are involved, they usually deactivate in reverse order from activation (i.e., Federal, State and local). Maintain MAC readiness Replenish resource Update rosters, media lists, and other contact information Conduct tests, training and exercises Maintain and update equipment Follow-up and implement recommendations from exercises Page 3.5

43 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 4 MAC Group Members MAC System Functions A MAC Group is comprised of administrators/executives, or their designees, who are authorized to represent or commit agency resources and funds. A MAC Group does not have any direct incident involvement and is often located some distance away from the incident site(s) or may function virtually. A MAC Group requires a support organization for its own logistics and documentation needs; to manage incident-related decision support information (tracking critical resources, situation status, and intelligence or investigative information); and to provide public information to the media and public. A MAC Group may be established at any level (National, State, or Local) or within any discipline (emergency management, public health, critical infrastructure, or private sector). MAC Group members consist of elected senior officials, agency administrators or executives, or their designees, who are authorized to represent or commit agency resources and funds. The principal functions and responsibilities of MAC entities typically include: Ensure each agency involved in incident management activities provides appropriate situational awareness and resource status information Establish priorities between incidents and/or Area Commands in concert with Incident Commanders or a Unified Command Acquire and allocate resources required by incident management personnel in concert with the priorities established by Incident or Unified Command Page 3.6

44 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Anticipate and identify future resource requirements Coordinate and resolve policy issues arising from the incident(s) Provide strategic coordination as required The primary functions of MACS are to Support incident management policies and priorities Facilitate logistics support and resource tracking Inform resource allocation decisions using incident management priorities Coordinate incident related information, and coordinate interagency and intergovernmental issues regarding incident management policies, priorities, and strategies Page 3.7

45 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 5 Based on a Catastrophic Earthquake Assigned issue problem list Determine if a MAC Group is needed & why Who should be part of the group What s its purpose How do you communicate Page 3.8

46 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 6 Many hospitals structurally compromised Water and electricity is compromised Long wait time for medical assistance Low medical supplies and personnel Lacking sterile facilities to treat victims Security issues at the hospitals Slide 7 Water systems compromised Sewage system compromised Need water monitoring Common Health Advisory Needed Vector Control County Health Facilities Compromised Pharmaceuticals Needed Page 3.9

47 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 8 Water Systems Down Multiple-Water Districts Involved Need for Emergency Drinking Water Distribution of Drinking Water Long term issues regarding restoration Slide 9 Capacity of Shelters is maxed out Limited electricity and water Access and Functional Needs Issues Pets Issues Security Issues Spontaneous Shelters Popping Up Page 3.10

48 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 10 Mutual Aid Agreements Mutual Aid Agreement Benefits Jurisdictions are encouraged to enter into mutual aid and assistance agreements with other jurisdictions and/or organizations from which they expect to receive, or to which they expect to provide, assistance. States are also encouraged to participate in interstate compacts and to consider establishing intrastate agreements that encompass all local jurisdictions. A mutual aid agreement is a legal document that provides a formal framework for assistance between parties. Agreements should be documented in writing to reduce or eliminate misunderstandings. A mutual aid agreement outlines request and response procedures, liability, reimbursement, and worker s compensation procedures. Agreements should be developed before an incident occurs. Agreements should be among all parties that might provide or request resources during an incident. Mutual Aid and Assistance Agreements Coordinate planning Expand available response resources Ensure timely arrival of aid Arrange for specialized resources Minimize administrative conflict and litigations Maximize use of all available resources Recover response costs. A Capability Assessment determines the jurisdictions ability to respond to or adequately deal with incidents identified in the hazard analysis. Page 3.11

49 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 11 Purpose and Scope References and Authorities Definitions Effect on existing agreements Roles and Responsibilities Mediation/dispute resolution Training and Exercises Purpose and Scope: The Purpose and Scope section sets the tone for the agreement. The section should include 1) need for the agreement, 2) range of incidents, and 3) member organizations. References and Authorities: Includes details about existing statues and/or regulations that authorize mutual aid agreements. Definitions define key terms to avoid different interpretations. Effect on existing agreements is a comprehensive legal review to determine if any serious conflicts exist with existing agreements. New agreements should replace older agreements to avoid conflict and potential disputes. Roles and Responsibilities include the roles and responsibilities of each party. This section usually has information about who can activate the mutual aid agreement. Mediation/Dispute Resolution includes information about how disputes are resolved. This may include using mediation, arbitration, and /or court of jurisdiction Training and Exercises include language on training and exercises, including how often training and exercises are conducted. Page 3.12

50 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 12 Liability and Insurance Limitations License, Certificate, and Permit Portability Terms and Conditions Reimbursement Severability Liability and Insurance spells out the liability of all parties and provides guidance for arbitration or resolution of any claims. Participating jurisdictions should have insurance or another form of protection in place. Limitations specifies the conditions under which a participating jurisdiction s obligation to provide assistance and resources may or may not be limited. License, Certifications & Permit Portability specifies conditions under which a person or entity who holds a license, certifications, or other permit is deemed to be licensed, certified, or permitted in the jurisdiction requesting assistance. Terms and Conditions specify the duration or life expectancy of the agreement. The agreement should have a beginning and an end date. Reimbursement clarifies issues over reimbursement (who pays for what, eligible expenses, triggers for the reimbursement provision) Severability addresses how one or more of the signatures can leave the agreement while leaving the rest of the agreement intact. Page 3.13

51 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 13 Types of Aid and Agreements Law and Fire EMMA Intra and Interstate Mutual Aid Operational Plan Types of Mutual Aid and Assistance Agreements Law Mutual Aid Law Enforcement agencies use Mutual Aid to assist each other during an incident Fire Mutual Aid- Fire departments use Mutual Aid to assist each other during incidents Emergency Managers Mutual Aid (EMMA) Send staff to assist other EOCs when needed Statewide/Intrastate Mutual Aid- Agreements (coordinated through the State) that incorporate both State and local governmental and nongovernmental assets. Intrastate mutual aid is used between two or more governmental entities, jurisdictions, agencies, departments, etc. within the boundaries of a State, who agree to provide or receive aid from one another. Interstate Agreements Out-of-State assistance through formal State-to-State agreements such as the Emergency Management Assistance Compact (EMAC). The primary purpose of a mutual aid operational plan is to provide detailed procedures for implementing a mutual aid agreement. Mutual aid can be activated in one of three ways: 1) Notification through dispatch, which contacts assisting parties directly 2) Notification through the State emergency management agency (EMA), which then contacts assisting parties 3) Direct contact between authorized officials, either orally or in writing Self-dispatch is unacceptable. Unsolicited aid violates the terms and conditions of a mutual aid agreement. Page 3.14

52 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements The mutual aid operational plan should provide details on how to request assistance Most plans should include: Type of incident Time the incident occurred or is expected to occur Actions already taken Areas and number of people involved Estimates of loss of life, injuries, and extent of damage Type and amount of assistance required A contact for follow-up questions If resource needs change, the Incident Commander s best course of action is to contact the mutual aid working group. Page 3.15

53 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 14 Requests for Assistance Mobilization Resource accountability Documentation Demobilization Once a request for assistance has been made, the mobilization of resources begins. Mutual aid operational plans should include provisions for managing the mobilization process. Resource accountability requires Check-in or incident arrival Task assignment and location Task modification, if necessary Task progress reporting Task extension, reassignment, or completion Documentation requires mission and task activity, reimbursement, accountability, and claims management. Responsibility for documentation is shared at all levels from the individual resource level up to and including the authorized representatives of the requesting and assisting parties. Demobilization requires Debriefing personnel Completing any incident-specific checkout procedures Completing and submitting required documentation Arranging return travel Ensuring that released resources are prepared and safe to travel Tracking released assets back to their home duty station in the requesting jurisdiction in a safe and timely manner. Page 3.16

54 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 15 Training and Exercise Discussion Based Operations Based After Action Report Training allows participants to use the concepts and principles of SEMS/NIMS in exercises, planned events, and actual incidents. Participants become comfortable using SEMS/NIMS, including the Incident Command System. Mutual aid partners must familiarize themselves with each other s operating and mutual aid procedures. Mutual aid agreements and operational plans should provide for training within and between the parties, including training, and frequency. Mutual aid partners provide the same liability immunity for training as a real emergency and provide for cost sharing as defined in the agreement. Exercises should begin at a basic level with small and simple scenarios (i.e. seminars, tabletops, etc.). As the coordination between parties improves, develop more complex scenarios to test parties communications and interoperability (Full Scale and Functional). Exercises should not only exercise the system, but also provide participants the opportunity to work together and develop essential relationships. To improve SEMS/NIMS performance, staff should participate in realistic exercises and include multidisciplinary, multijurisdictional incidents. Exercises should require interactions with the private sector and nongovernmental organizations and cover all aspects of preparedness plans, particularly the processes and procedures for activating local, intrastate, and/or interstate mutual aid agreements and assistance agreements. Exercises contain a mechanism for incorporating corrective actions and lessons learned from incidents into the planning process. Page 3.17

55 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements The After-Action Report Review process should be a responsibility of the mutual aid working group and should ask What parts of the mutual aid system worked as intended? What parts of the mutual aid system did not work as intended? Why? What are we going to do better next time? Are there lessons learned that should be shared? What follow-up is needed and who is responsible? Page 3.18

56 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 16 Mutual Aid Working Group Drafting Mutual Aid Agreements A Mutual Aid working group should include Elected officials, tribal leadership, and heads of counties and/or municipalities. State and local emergency management agency (EMA) officials. Representatives of relevant response organizations, associations, and public agencies. Emergency medical services (EMS), hospitals, and public health organizations. Mutual aid, technical, logistics, and legal experts Responsibilities include Review drafts of the agreement Authorize the agreement on behalf of their respective organizations Attend regular meetings to review the status of the mutual aid system Communicate plan details to their respective organizations Assist with implementation of training and exercises Maintain documents such as the agreement and the operational plan Review after-action reports from mutual aid events and the requirements of emergency response and terrorism preparedness Make recommendations to improve the mutual aid system Page 3.19

57 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Use a template or model agreement for guidance on how to develop a new mutual aid agreement. (Sample in Appendix C) Step 1: Review existing agreements and authorities Step 2: Review hazard identification and vulnerability assessments Step 3: Conduct capability assessments Step 4: Update Emergency Operations Plans and resource inventories Step 5: Identify resource needs and gaps Step 6: Develop new agreements or update existing agreements Page 3.20

58 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements Slide 17 Page 3.21

59 Unit 3 - Multiagency Coordination System (MACS) and Mutual Aid Agreements This Page Intentionally Left Blank Page 3.22

60 Unit 4 The Standardized Emergency Management System (SEMS) and The National Incident Management System (NIMS)

61 This Page Intentionally Left Blank

62 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Duration 100 Minutes Scope Statement This unit provides participants with a review of California s Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS). Terminal Learning Objectives Upon completion of this unit, participants will understand California s Standardized Emergency Management System and the National Incident Management System (NIMS) Enabling Learning Objectives Identify SEMS components Identify Five Levels of Response Understand SEMS functions and features Understand NIMS functions and features Lesson Topics SEMS Components Five Levels of Response SEMS Functions and Features Emergency Management Assistance Compact (EMAC) NIMS Page 4.1

63 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Resources Handouts Activities Assessment Strategy Verbal and visual assessment of understanding Participation in group discussions and activities Question and answer period Instructor-to-Participant Ratio 1:25 Reference List Not Applicable Practical Exercise Statement Not Applicable Instructor Notes Instructor notes are contained throughout the lesson plan as appropriate Page 4.2

64 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 1 Page 4.3

65 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 2 History Purpose The Standardized Emergency Management System (SEMS) was introduced in 1991 after the East Bay Hills Fire in Oakland Hills. SEMS was adopted in 1993 under Government Code Section SEMS intent is to improve coordination of Federal, State and local emergency management and response On December, 1, 1996, SEMS went into effect and requires all state agencies must use SEMS to be eligible for response related personnel costs. Local jurisdictions must use SEMS to be reimbursed costs. SEMS is an Emergency Response System based on FIRESCOPE ICS and includes a Maintenance System. California uses SEMS to coordinate and manage emergency response that involve more than one agency or jurisdiction. SEMS improves Facilitation of information Enhances coordination between agencies Tracks resource mobilization and deployment. Page 4.4

66 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 3 State Region Operational Area Local Government Field Note: Pure ICS used in the field & ICS principles used in the EOC levels SEMS has five levels: 1) Field Level 2) Local Government Level 3) Operational Area Level 4) Regional Level 5) State Level All responses begin at the Field Level. The local government level is a city and the first place with an EOC. The Operational Area (OA) level is all political subdivisions within the county (city, special districts). The OA can broker resources within the county. The Regional Level coordinates movement of resources between counties within that region. The State level coordinates and manages state resources in support of local government. Preparedness Organizations are responsible for establishing/coordinating plans and protocols. All Plans must be in accordance with the State Emergency Plan and Protocols and comply with SEMS. Preparedness Organizations promote interoperability, adopt resource management guidelines, establish response priorities, and establish/maintain multi-agency coordination mechanisms. Page 4.5

67 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 4 SEMS has four components: 1) Incident Command System Includes ICS in the field and ICS principles in EOCs and Department Operations Centers (DOCs) 2) Multi/Inter-Agency Coordination (EOC) includes Multi Agency Coordination (MAC) groups 3) Mutual Aid- California Master Mutual Aid Agreement 4) Operational Area concept ICS must be used in the field and ICS Principles are used in the EOCs. Page 4.6

68 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 5 SEMS uses the same ICS functions. SEMS features Common terminology Management by objectives Action Planning Page 4.7

69 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 6 Operational Area Concept Master Mutual Aid Agreement Mutual Aid Assistance Systems The Operational Area (Op Area) Concept includes the county and all political subdivisions. The Op Area coordinates Mutual Aid within the County Boundaries and may broker resources between its subdivisions. Master Mutual Aid original agreement was in 1950 and includes all California political subdivisions. Master Mutual Aid is a voluntary and reciprocal agreement which provides services, resources, and facilities. Established Mutual Aid/Assistance agreements from essential links Emergency Management Mutual Aid (EMMA) Fire & Rescue Mutual Aid Law Enforcement Mutual Aid Emergency Medical Mutual Aid Page 4.8

70 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 7 Who s involved Emergency Management Assistance Compact (EMAC) Emergency Management involves everyone. Individuals and households (CERT, preparedness, mitigation) Private Sector (Critical infrastructure, provide goods and services critical to response) Nongovernmental Organizations (sheltering, food, counseling, recovery assistance) Local Governments (Local response resources ensure the safety and welfare of their residents) Tribal Governments (Safety of tribes) EMAC provides State-to-State Assistance, and uses interstate mutual aid and assistance agreements. EMAC is administered by National Emergency Management Association (Ratified by congress). Page 4.9

71 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 8 You have to set up a County EOC to respond to this growing crisis What organizational functions of SEMS structure need to be in place? Who is involved? What are the top three priorities? What is the time period to complete the activities? What supporting resources/equipment/needs are needed? Is Mutual Aid required? Which type? Will you need a MAC? Page 4.10

72 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 9 HSPD-5 HSPD-8 Mandates NIMS Mandates ICS Homeland Security Presidential Directives (HSPD) 5 & 8 mandates the use of SEMS and NIMS. HSPD-5 requires the Department of Homeland Security to coordinate with other Federal departments, and agencies and state, local, and tribal governments to establish a National Response Framework (NRF) and a National Incident Management System (NIMS). HSPD 5 Management of Domestic Incidents - To enhance the ability of the United States to manage domestic incidents by establishing a single, comprehensive national incident management system. Adopt NIMS and use in individual incident management programs and activities. Makes adoption of NIMS by State, tribal, and local organizations a condition for Federal preparedness assistance (through grants, contracts, and other activities). HSPD-5 required the Secretary of Homeland Security to establish a mechanism to ensure the ongoing management and maintenance of NIMS. HSPD 8 National Preparedness - (1) This directive established policies to strengthen the preparedness of the United States to prevent and respond to threatened or actual domestic terrorist attacks, major disasters, and other emergencies by requiring a national domestic all-hazards preparedness goal, (2) establishing mechanisms for improved delivery of Federal preparedness assistance to State and local governments, and (3) outlining actions to strengthen preparedness capabilities of Federal, State, and local entities. Page 4.11

73 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 10 Goal 1: Prevent and disrupt terrorist attacks Goal 2: Protect the American people and our critical infrastructure and key resource Goal 3: Respond to and recover from incidents that do occur (National Response Framework supports this goal) Goal 4: Continue to strengthen the foundation to ensure our long-term success Page 4.12

74 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 11 Concepts and Principles Benefits The National Incident Management System (NIMS) integrates existing best practices into a consistent nationwide framework for incident management at all jurisdictional levels and across functional disciplines. NIMS allows responders at all levels to work together more effectively and efficiently. NIMS is not an incident management or resource allocation plan. NIMS is not a static system. NIMS is a national approach to managing incidents, regardless of cause, size, or complexity. NIMS provides a flexible framework for everyone to work under and a set of standardized organizational structures. NIMS unifies how we respond to disasters and emergencies. A few benefits of NIMS include: Improves incident national coordination and cooperation between public & private entities Provides guidance &certification standards for all resources used in incident management Provides for compatibility and interoperability among all involved organizations Standardized organizational structure Provides elected officials a way to Ensure agency policies are clearly stated Evaluate effectiveness and correct any deficiencies Support a coordinated, multiagency approach. Page 4.13

75 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 12 Command and Management Incident Command System Multi-Agency Coordination Public Information System NIMS components include Command and Management Preparedness Resource Management Communications and Information Management Supporting Technologies Ongoing Management and Maintenance Like SEMS, NIMS uses ICS. NIMS uses Unified Command and Area Command. Staff organization used is Command and General Staff positions. Plans for demobilization begin as soon as possible to facilitate accountability. Incident Action Plans are used. Multi-Agency Coordination Systems are a combination of resources working together.. The Joint Information System (JIS) is the framework for organizing, integrating, and coordinating the delivery of public information. The JIS provides information to the public during an emergency. The JIS includes plans and protocols to communicate timely and accurate information to the public. The JIS also coordinates communication across different jurisdictions and agencies. The Joint Information Center (JIC) is where coordination of information and resources to support incident management take place. The JIC is a physical location where public information staff from various agencies convenes. The scale of the incident may require multiple JIC locations. Different JICS can communication with each other through established protocols. Page 4.14

76 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 13 Preparedness Planning Training and Exercises Preparedness establishes and maintains incident response capability. Preparedness activities include coordinating individuals, non-governmental organizations, and the private sector. Aspects of Preparedness include Planning Training and Exercises Personnel Qualification and Certification Equipment Certification Public Management Mutual Aid Agreements The planning process identifies resource needs based on the threats to and vulnerabilities of the jurisdiction. The planning process develops alternative strategies to obtain needed resources and creates new policies to encourage positioning of resources. Plans outline how to set priorities, establish relationships and coordinate efforts between organizations, and ensure support for all incident management activities. Plan maintenance should be done on a regular basis. Some common reasons for plan updates include changes in references and authorities, threat and risk assessment, resource availability, and community demographics. Training allows practitioners to use concepts and principles with scenarios and become more comfortable using ICS and NIMS. Exercises can improve performance and identify the need for corrective action. Exercises can be multidisciplinary/multijurisdictional incidents and cover aspects of preparedness plans. Exercises contain the mechanism for incorporating corrective action and lessons learned. Page 4.15

77 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 14 National Integration Center Credentialing Ongoing Management and Maintenance The National Integration Center (NIC) oversees all aspects of NIMS, including: Developing compliance assessment criteria Promote compatibility between national level standards and private and public groups Facilitate the establishment of a documentation and database related to qualification, certifications, and credentialing of personnel and organizations Credentialing ensures consistent training, licensure, certification standards, and competency or proficiency. Credentialing involves evaluating and documenting certification, license or degree; training and experience; and competence and proficiency. The NIC is responsible for providing strategic direction for and oversight of NIMS. This includes developing a process for ongoing revisions and updates to the NIMS. Input is encouraged from all entities. Page 4.16

78 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 15 Key concept Readiness What are some factors that impact Readiness? Resource Management manages resources during an incident.. This standardized process includes Identifying Ordering, Tracking Paying for and restocking resources used during a response. Incidents are handled at the lowest jurisdictional level possible. Incidents that have the potential to expand rapidly in size, scope, or complexity may to have resources staged. No-notice incidents are particularly challenging Readiness is our current collective ability to respond to any incident. Readiness is fluid depending on availability of human and material resources and can change daily. Page 4.17

79 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 16 Resource Request Process Standardized Approach Disasters happen at the local level. The local government maintains control of all assets used in the response and recovery phases. When a local jurisdiction does not have the necessary resources they turn to the Operational Area (Op Area). The Op Area then makes a request to the Region.The Region requests support from the state. When the state has exhausted all resources they turn to the federal government. Request for resources flow from the on-scene incident command through the local and OP Area Emergency Operations Centers to State. The State then turns to the Federal Government. The benefits of standardized approach include Consistent method of identifying, acquiring, allocating, and tracking resources Resources can be typed to improve effectiveness Coordination facilitates integrating of resources for optimal use Uses available resources from all sectors Page 4.18

80 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 17 Identify Requirements Order and Acquire Mobilize Track and Report Recovery and Demobilize Reimbursement Inventory Identify Requirements: When identifying resource requirements ask where, how much when, and who. Ordering and Acquire: Use a standardized resource-ordering process. The closest resource is used first. Resources are provided with consent of the jurisdiction providing the resource. To Mobilize resources requires document ng the date, time, and place of departure. Determine mode of transportation and the estimated time of arrival. Identify the location, anticipated assignment, and duration of deployment. Document the ordering number, incident number, and the cost and funding codes. Track and Report Track resources prior to, during, and after an incident. Tracking provides a clear picture of where resources are, prepares staff to receive resources, protects the safety and security of personnel, equipment, and supplies, and enables resource coordination and movement. Recovery and demobilization includes final disposition of all resources. Resources are disposed of or replenished. Resources can be returned to a state of readiness. The demobilization process should begin as soon resources are received. Reimbursement recoups funds expended for incident-specific activities. This includes collecting bills and documentation; validating costs; and securing proper authorizations. Use the proper procedures and forms for reimbursement. Inventory shows what resources are available and can assist with replenishment and reimbursement. Inventory also allows for timely mobilization of resources. Page 4.19

81 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 18 Common Operating Picture Interoperability A common operating picture must be accessible across jurisdictions and agencies. A common operating picture is established and maintained by gathering, collating, synthesizing, and disseminating information. Interoperability enables response personnel to interact and work together. Communications systems should effectively interface. Interoperability allows for sharing data throughout the response. Page 4.20

82 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 19 Reliability, Portability, Scalability Resiliency and Redundancy Equipment Standards Training and Testing Communications systems should be Reliable (able to function) in any type of incident. Communications Systems should be Portable (movable) to different locations and compatible with other systems. Communication Systems should also be Scalable (expand or contract). Communications systems should have Resiliency (ability to perform after damage or loss of infrastructure), and Redundancy (duplication of services or the ability to communicate through diverse, alternative methods). Equipment standards require systems and equipment to be maintained and updated. All communications systems and equipment must be tested on a regular basis. Tests can verify whether systems perform to expected standards. Systems to test include computer and other data systems and communications systems. Systems include hardware and equipment, and the human tasks needed to activate and operate them. Systems should be tested any time a change has been made to ensure they work. Page 4.21

83 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 20 Standardized Communications Data Standards Encryption/Tactical Language Language and Terminology There are four types of Standardized Communications: Strategic Communications High-level directions Tactical Communications Communications between command and support elements Support Communications Coordination in support of strategic and tactical communications Public Address Communications Emergency Alerts and Warnings Communications Data Standards are a standard set of organizational structures and responsibilities that include Common Typing of resources Common communications protocols Common identifiers for personnel, facilities, and operational locations Plain language and common terminology facilitates safety, interoperability across jurisdictions and disciplines, and understanding. Page 4.22

84 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 21 When OES met with the DHS representatives, they determined work conditions needed to be improved Office of Environmental Services (OES), Disaster Health Services (DHS) Page 4.23

85 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 22 Purpose Response Doctrine Role and Responsibilities State Coordinating Officer (SCO) Federal Coordinating Officer (FCO) Principal Federal Officer (PFO) Actions that support National Response The National Response Framework (NRF) is a guide to how the U.S. conducts response to incidents. It is built on scalable, flexible, and adaptable concepts identified in the National Incident Management System (NIMS) to align key roles and responsibilities across the Nation. This Framework describes specific authorities and best practices for managing incidents. The National Response Framework provides structure and mechanisms to ensure effective Federal support. During a catastrophic incident, the State Coordinating Officer is assigned by the Governor to expedite the delivery of needed services. The Federal Coordinating Officer coordinates federal assistance to a state affected by a disaster or emergency. The Principal Federal Officer (FPO) promotes collaboration and works to resolve any Federal interagency conflict. The structures, roles, and responsibilities described in this Framework can be partially or fully implemented in the context of a threat or hazard, in anticipation of a significant event, or in response to an incident. Selective implementation of National Response Framework structures and procedures allows for a scaled response, delivery of the specific resources and capabilities, and a level of coordination appropriate to each incident Page 4.24

86 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 23 Uses the NIMS ICS structure Incidents managed at the lowest jurisdictional level Integrates agencies into a seamless system Uses a public information system Identifies resources based on established standards Ensures personnel are properly trained Ensures interoperability and redundancy of communications The basic premise of the National Response Framework is that incidents should be managed at the lowest jurisdictional level possible. The National Response Framework (NRF) provides additional guidance for incident management. The NRF builds upon NIMS with flexible, scalable, and adaptable coordinating structures to align key roles and responsibilities Nationwide. The NRF incorporates public and private sector participation and focuses on how the Federal Government is organized to support communities and states in catastrophic events. The NRF identifies specific concepts that should be addressed in and Emergency Operations Plan (EOP). Page 4.25

87 Unit 4 Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) Slide 24 Page 4.26

88 Unit 5 Course Summary

89 This Page Intentionally Left Blank

90 Duration 60 Minutes Unit 5 Course Summary and Close Scope Statement This unit will conclude the course, answer questions and administer post-test and course evaluation. Terminal Learning Objectives (TLO) Upon completion of this unit, participants will have successfully completed the course objectives. Enabling Learning Objectives (ELO) Obtain answers to any questions Pass the post-test Complete course evaluation form Lesson Topics Review course material Provide question and answer opportunity Administer post-test Participants to complete course evaluation form Page 5.1

91 Resources Unit 5 Course Summary and Close Course Post-test Evaluation form Assessment Strategy Participant post-test results Instructor-to-Participant Ratio 1:25 Instructor Notes Instructor notes are contained throughout the lesson plan as appropriate. Page 5.2

92 Unit 5 Course Summary and Close Slide 1 Slide 2 ICS SEMS NIMS Communications Resource Management Page 5.3

93 Unit 5 Course Summary and Close Slide 3 Page 5.4

94 Unit 5 Course Summary and Close Slide 4 Page 5.5

95 Unit 5 Course Summary and Close Slide 5 Page 5.6

96 Appendix A Acronyms

97 This Page Intentionally Left Blank

98 Appendix A Acronyms Acronyms Cal OES CERT DOC EMA EMAC EMMA EMS EOC EOP ESF FCO FEMA FIRESCOPE FSE FX GIS HSPD IAP IC ICP ICS JFO California Governor s Office of Emergency Services Community Emergency Response Team Department Operations Center Emergency Management Agency Emergency Management Assistance Compact Emergency Management Mutual Aid Emergency Medical Services Emergency Operations Center Emergency Operation Plan Emergency Support Function Federal Coordinating Officer Federal Emergency Management Agency Firefighting RESources of California Organized for Potential Emergencies Full Scale Exercise Functional Exercise Geographic Information Systems Homeland Security Presidential Directive Incident Action Plan Incident Commander Incident Command Post Incident Command System Joint Field Office ICS/SEMS/NIMS Combined Course December 2014 A.1 Appendix B

99 Appendix A Acronyms JIC LOGS MAC NIMS NGO NIC NRF OA or Op Area Ops OSHA PIO SEMS SCO SOC TTX Joint Information Center Logistics Multiagency Coordination National Incident Management System Non-governmental Organization (e.g., Red Cross, Salvation Army) National Integration Center National Response Framework Operational Area (California county and all of the political subdivisions within that county) Operations Occupational Safety and Health Administration Public Information Officer Standardized Emergency Management System State Coordinating Officer State Operations Center (California) Tabletop Exercise ICS/SEMS/NIMS Combined Course December 2014 A.2 Appendix B

100 Appendix B Emergency Support Functions (ESFs)

101 This Page Intentionally Left Blank

102 Appendix B Emergency Support Functions Emergency Support Functions ESF1 ESF2 ESF3 ESF4 ESF5 ESF6 ESF7 ESF8 ESF9 ESF10 ESF11 ESF12 ESF13 ESF14 ESF15 Transportation Communications Public Works and Engineering Firefighting Emergency Management Mass Care, Housing, and Human Services Resources Support Public Health and Medical Services Urban Search and Rescue Oil and Hazardous Materials Response Agriculture and Natural Resources Energy Public Safety and Security Long-term Community Recovery and Mitigation External Affairs ICS/SEMS/NIMS Combined Course December 2014 Page B.1 Appendix C

103 Appendix B Emergency Support Functions This Page Intentionally Left Blank ICS/SEMS/NIMS Combined Course December 2014 Page B.2 Appendix C

104 Appendix C Mutual Aid Template

105 This Page Intentionally Left Blank

106 CALIFORNIA DISASTER AND CIVIL DEFENSE MASTER MUTUAL AID AGREEMENT This agreement made and entered into by and between the STATE OF CALIFORNIA, its various departments and agencies, and the various political subdivisions, municipal corporations, and other public agencies of the State of California; WITNESSETH: WHEREAS, it is necessary that all of the resources and facilities of the State, its various departments and agencies, and all its political subdivisions, municipal corporations, and other public agencies be made available to prevent and combat the effect of disasters which may result from such calamities as flood, fire, earthquake, pestilence, war, sabotage, and riot; and WHEREAS, it is desirable that each of the parties hereto should voluntarily aid and assist each other in the event that a disaster should occur, by the interchange of services and facilities, including, but not limited to, fire, police, medical and health, communication, and transportation services and facilities, to cope with the problems of rescue, relief, evacuation, rehabilitation, and reconstruction which would arise in the event of a disaster; and WHEREAS, it is necessary and desirable that a cooperative agreement be executed for the interchange of such mutual aid on a local, countywide, regional, statewide, and interstate basis; NOW, THEREFORE, IT IS HEREBY AGREED by and between each and all of the parties hereto as follows: 1. Each party shall develop a plan providing for the effective mobilization of all its resources and facilities, both public and private, to cope with any type of disaster. 2. Each party agrees to furnish resources and facilities and to render services to each and every other party to this agreement to prevent and combat any type of disaster in accordance with duly adopted mutual aid operational plans, whether heretofore or hereafter adopted, detailing the method and manner by which such resources, facilities, and services are to be made available and furnished, which operational plans may include provisions for training and testing to make such mutual aid effective; provided, however, that no party shall be required to deplete unreasonably its own resources, facilities, and services in furnishing such mutual aid. 3. It is expressly understood that this agreement and the operational plans adopted pursuant thereto shall not supplant existing agreements between some of the parties hereto providing for the exchange or furnishing of certain types of facilities and services on a reimbursable, exchange, or other basis, but that the mutual aid extended under this agreement and the operational plans adopted pursuant thereto, shall be without reimbursement unless otherwise expressly 1

107 provided for by the parties to this agreement or as provided in Sections 1541, 1586, and 1587, Military and Veterans Code; and that such mutual aid is intended to be available in the event of a disaster of such magnitude that it is, or is likely to be, beyond the control of a single party and requires the combined forces of several or all of the parties to this agreement to combat. 4. It is expressly understood that the mutual aid extended under this agreement and the operational plans adopted pursuant thereto shall be available and furnished in all cases of local peril or emergency and in all cases in which a STATE OF EXTREME EMERGENCY has been proclaimed. 5. It is expressly understood that any mutual aid extended under this agreement and the operational plans adopted pursuant thereto, is furnished in accordance with the California Disaster Act and other applicable provisions of law, and except as otherwise provided by law that: The responsible local official in whose jurisdiction an incident requiring mutual aid has occurred shall remain in charge at such incident including the direction of such personnel and equipment provided him through the operation of such mutual aid plans. (Section 1564, Military and Veterans Code.) 6. It is expressly understood that when and as the State of California enters into mutual aid agreements with other states and the Federal Government, the parties to this agreement shall abide by such mutual aid agreements in accordance with the law. 7. Upon approval or execution of this agreement by the parties hereto all mutual aid operational plans heretofore approved by the State Disaster Council, or its predecessors, and in effect as to some of the parties hereto, shall remain in full force and effect as to them until the same may be amended, revised, or modified. Additional mutual aid operational plans and amendments, revisions, or modifications of existing or hereafter adopted mutual aid operational plans, shall be adopted as follows: a. Countywide and local mutual aid operational plans shall be developed by the parties thereto and are operative as between the parties thereto in accordance with the provisions of such operational plans. Such operational plans shall be submitted to the State Disaster Council for approval. The State Disaster Council shall notify each party to such operational plans of its approval, and shall also send copies of such operational plans to other parties to this agreement who did not participate in such operational plans and who are in the same area and affected by such operational plans. Such operational plans shall be operative as to such other parties 20 days after receipt thereof unless within that time the party by resolution or notice given to the State Disaster Council, in the same manner as notice of termination of participation in this agreement, declines to participate in the particular operational plan. 2

108 b. Statewide and regional mutual aid operational plans shall be approved by the State Disaster Council and copies thereof shall forthwith be sent to each and every party affected by such operational plans. Such operational plans shall be operative as to the parties affected thereby 20 days after receipt thereof unless within that time the party by resolution or notice given to the State Disaster Council, in the same manner as notice of termination of participation in this agreement, declines to participate in the particular operational plan. c. The declination of one or more of the parties to participate in a particular operational plan or any amendment, revision or modification thereof, shall not affect the operation of this agreement and the other operational plans adopted pursuant thereto. d. Any party may at any time by resolution or notice given to the State Disaster Council, in the same manner as notice of termination of participation in this agreement, decline to participate in any particular operational plan, which declination shall become effective 20 days after filing with the State Disaster Council. e. The State Disaster Council shall send copies of all operational plans to those state departments and agencies designated by the Governor. The Governor may, upon behalf of any department or agency, give notice that such department or agency declines to participate in a particular operational plan. f. The State Disaster Council, in sending copies of operational plans and other notices and information to the parties to this agreement, shall send copies to the Governor and any department or agency head designated by him; the chairman of the board of supervisors, the clerk of the board of supervisors, the County Disaster Council, and any other officer designated by a county; the mayor, the clerk of the city council, the City Disaster Council, and any other officer designated by a city; the executive head, the clerk of the governing body, or other officer of other political subdivisions and public agencies as designated by such parties. 8. This agreement shall become effective as to each party when approved or executed by the party, and shall remain operative and effective as between each and every party that has heretofore or hereafter approved or executed this agreement, until participation in this agreement is terminated by the party. The termination by one or more of the parties of its participation in this agreement shall not affect the operation of this agreement as between the other parties thereto. Upon approval or execution of this agreement the State Disaster Council shall send copies of all approved and existing mutual aid operational plans affecting such party which shall become operative as to such party 20 days after 3

109 receipt thereof unless within that time the party by resolution or notice given to the State Disaster Council, in the same manner as notice of termination of participation in this agreement, declines to participate in any particular operational plan. The State Disaster Council shall keep every party currently advised of who the other parties to this agreement are and whether any of them has declined to participate in any particular operational plan. 9. Approval or execution of this agreement shall be as follows: a. The Governor shall execute a copy of this agreement on behalf of the State of California and the various departments and agencies thereof. Upon execution by the Governor a signed copy shall forthwith be filed with the State Disaster Council. b. Counties, cities, and other political subdivisions and public agencies having a legislative or governing body shall by resolution approve and agree to abide by this agreement, which may be designated as CALIFORNIA DISASTER AND CIVIL DEFENSE MASTER MUTUAL AID AGREEMENT. Upon adoption of such a resolution, a certified copy thereof shall forthwith be filed with the State Disaster Council. c. The executive head of those political subdivisions and public agencies having no legislative or governing body shall execute a copy of this agreement and forthwith file a signed copy with the State Disaster Council. 10. Termination of participation in this agreement may be effected by any party as follows: a. The Governor on behalf of the State and its various departments and agencies, and the executive head of those political subdivisions and public agencies having no legislative or governing body, shall file a written notice of termination of participation in this agreement with the State Disaster Council and this agreement is terminated as to such party 20 days after the filing of such notice. b. Counties, cities, and other political subdivisions and public agencies having a legislative or governing body shall by resolution give notice of termination of participation in this agreement and file a certified copy of such resolution with the State Disaster Council, and this agreement is terminated as to such party 20 days after the filing of such resolution. IN WITNESS WHEREOF this agreement has been executed and approved and is effective and operative as to each of the parties as herein provided. 4

110 Signed by: EARL WARREN GOVERNOR On behalf of the State of California and all its Departments and Agencies ATTEST: November 15, 1950 Signed by: FRANK M. JORDAN SECRETARY OF STATE 5