incident command system overview canuslant incident management workshop portland, me – may 15,...

39
Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Upload: doreen-austin

Post on 24-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Incident Command System Overview

CANUSLANT Incident Management WorkshopPortland, ME – May 15, 2007

LCDR Matt McCann

Page 2: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Objectives

Wrap weeks of emergency management

command/control training into 45 minutes!

1. National policy mandates

2. Incident Command System for executives

3. ICS/Response Management System (RMS) linkages

Page 3: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Federal Coordinating StructuresFederal Coordinating Structures

NRP: Establishes Federal coordination structures/mechanisms, directs incorporation of existing plans, and provides a consistent approach to managing incidents.

NIMS: Standardizes incident management processes, protocols, training, and procedures for use by all responders.

Legislation: The Homeland Security Act of 2002,

and Homeland Security Presidential Directives 5/8

Page 4: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

National Response Plan National Response Plan • Builds on what worked from previous plans and incident

responses

• Forges new approaches and mechanisms to address today’s threats

• Establishes a national incident management capability

• Addresses the complete spectrum of incident management activities

• Uses National Incident Management System (NIMS) Incident Command System

Page 5: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

NRP Construction

Fully Incorporates• Federal Response Plan• Domestic Terrorism

Concept of Ops Plan• Federal Radiological

Emergency Response Plan

• National Contingency Plan

Integrates• Other national-level

contingency plans

Key concepts– National Operations

Center (was HSOC)

– Interagency Advisory Council (was IIMG)

– Principal Federal Official

– Joint Field Office

Foundation: National Incident Management System

Page 6: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

NIMS Components

• Command and Management – Organizational systems

• Preparedness – Planning/training/drills/exercises/mutual aid

• Resource Management

• Communications/Information Management

• Supporting Technologies

• Ongoing Management and Maintenance– NIMS Integration Center (NIC)

Page 7: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Federal Response Concept • Incidents handled at lowest possible organizational level

• DHS receives notification of actual and potential incidents– “Top-down” or “bottom-up” approach

• Consultation/coordination amongst departments/agencies to:– Assess national implications– Determine need for full or partial NRP activation

• Coordinating structures activated to provide unified, standardized approach for implementing Federal incident management responsibilities:– Direct implementation of Federal authorities– Federal support to State, local and tribal governments– Federal-to-Federal support– Proactive response to catastrophic incidents

• Coordinating structures provide national capability– Ability to address impacts, execute immediate nation-wide actions to avert or

prepare for subsequent events and manage multiple incidents

Page 8: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

ICS Program History

• Born in the Vietnam War, but attributed to Southern California wildfires in 1970s

• Recognized need for common emergency response system due to responder fatalities

• Mandated all-risk application and initially evaluated in the wild land fire environment

• Design objective includes all levels of government, including executives

Page 9: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Use of ICS is equally effective for planned or unplanned events…

Page 10: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Incident Command System Designed to turn a crisis from an emergency phase to a project phase as quickly as possible - From reactive to proactive.

Key features:

• Modular Organization - highly structured yet flexible• Manageable Span of Control• Standard Terminology / Forms / Symbols• Chain of Command Structure• Consolidated Action Plan “All Hazards, All Risks”• Structured Resource Management System• Established Curriculum• Available at Low Cost• Commonly Used Nationwide • Logical/Functional• Common Incident Support Facilities• Integrated Communications• Management by Objectives• Personnel Accountability

Page 11: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Why did L’Etats Unis adopt ICS?– On-scene incident management structure

– System generally being used by first responders to manage incidents

– Training & exercise program

– Certification & qualification system

– Support technologies

– System documentation

Page 12: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

LEVEL

ICS-100

ICS-200

ICS-300

Basic

Intermediate

NIMS ICS National Training Curriculum Baseline

#2Basic

Features of ICS

#1Purpose of ICS

#3Incident

Commander & Command Staff

Positions

#4General

Staff Functions

#5Facilities

#6Common

Responsibilities

#1Leadership & Management

#2Delegation of Authority &

Management by Objectives

#3Functional

Areas & Positions

#4Briefings

#5Organizational

Flexibility

#6Transfer of Command

#1ICS

Fundamentals Review

#2Unified

Command

#3Assessment &

Agency Guidance Establishing Objectives

#4Incident

Resources Management

#5Planning Process

#6Demob,

Transfer of Command &

Close Out

BasicIS-700 IS-800 NRP IntroductionNIMS Introduction

Page 13: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

ICS Applied

• Agency/organization executives have vital role

• All-risk system knows no bounds if properly applied

• To be effective it must have:

– Strong agency support

– Thorough system documentation

– Intensive training and exercises

– Evaluation/corrective action process

• System has never failed

Page 14: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

USCG Application Examples

• Oil spill/HAZMAT response and recovery

• Multi-casualty

• Port Security

• Water transportation or private sector accidents

• Planned marine or waterside events

• Terrorism response

• Designated Emergency Support Function

Page 15: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Factors Determining Response Size & Structure

Administrative/jurisdictional complexity

Geographic area involved

Functional specialties required

Logistics/support, planning needs

Potential for growth

Page 16: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Basic ICS Organization

IC

Command StaffInformationLiaisonSafetyLegalIntelligence

Planning Operations Logistics Finance

* Staging Area* Branches* Divisions* Groups

* Resources* Situation* Demobilization* Documentation

* Communications* Food* Medical* Supply* Ground Support* Facilities

* Procurement* Claims* Time* Cost* Compensation

Page 17: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Response Priorities

Incident objectives are established

based on the following priorities:

#1: Life Saving

#2: Incident Stabilization

#3: Property Preservation

Page 18: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Management by Objectives

Top down management activity with the following

steps to achieve incident response goals:

1. Establish objectives

2. Identify/select strategies

3. Develop/implement tactics

Page 19: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

ICS Management ICS span of control for any supervisor:

– Between 3 and 7 subordinates.– Optimally does not exceed 5 subordinates.

Page 20: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Resource/Planning Characteristics

Written Incident Action Plans are produced when:

– Large number of tactical and support resources need to be ordered, tracked and managed.

– Multiple operational periods are required.

– Transfer of command is likely.

– Or…the boss wants one.

Page 21: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Initial UCMeeting

Incident/Event

Notification

Initial Response& Assessment

Incident BriefICS-201

Preparing for the Tactics

Meeting

Operations Briefing

Execute Plan & Assess Progress

New OpsPeriodBegins

Command &General Staff

Meeting /Briefing

IC / UC Develop/Update

ObjectivesMeeting

Preparing for the Planning

Meeting

Planning Meeting

IAP Prep &

Approval

Tactics Meeting Planning “P”

• Deliberate Planning Cycle/Process

• Complete a set of actions from Incident Action Plan

• Operational period: Normally 12 - 24 hours

• Determined by Incident Commander

Page 22: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Resource Management• Maximizes effective use of personnel and equipment.

• Reduces span of control.

• Reduces communications traffic.• Process to categorize/track resources ordered,

dispatched, recovered and demobilized. • Includes processes for reimbursement, as appropriate.

Page 23: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

ICS SummaryUtilizes management features including common terminology and a modular organizational structure.

Emphasizes effective planning through management by objectives and Incident Action Plans.

Supports responders by providing needed data through effective information and intelligence management.

Utilizes principles of chain, unity and transfer of command.

Ensures ready resources through accountability/mobilization.

Ensures utilization of incident resources by maintaining a spanof control, establishing incident facilities, implementing resource management practices and ensuring integrated communications.

Page 24: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Incident Complexity - Typing

Page 25: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

What Are Major Incidents?– Involve more than one agency

and/or political jurisdiction.

– Involve complex management and communication issues.

– Require experienced, highly qualified supervisory personnel.

– Require numerous tactical and support resources.

– Involve multiple victims, fatalities, or illnesses.

– Include widespread damage to property/environment.

– Result in psychological threat/trauma.

– Span multiple operational periods (days, weeks).

– Costly to control and mitigate.

– Require extensive recovery efforts.

– Draw national media interest.

– Designated an Incident of National Significance.

Page 26: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Incident Of National Significance

IONS are declared by the Secretary for the Department of Homeland Security,

but Federal incident management activities are coordinated by the President

unless delegated under the following HSPD-5 criteria:

• When a Federal department/agency requests assistance.• When state/local capabilities are overwhelmed and they request assistance.• When an incident substantially involves more than one Federal agency. • When DHS has been directed by the President to assume incident

management responsibilities.

Page 27: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Area Command FunctionsDirects multiple responses handled by ICS organizations; or a large incident with multiple response teams assigned.

– Provide agency/jurisdictional authority for assigned incidents.

– Ensure a clear understanding of expectations, intentions, and constraints.

– Establish critical resource efficient use priorities between incidents.

– Ensure responder assignments are appropriate.

– Coordinate demobilization or reassignment of resources between incidents. – Assists in interagency coordination.

– Reduces workload for agency officials.

Page 28: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Area Commander Responsibilities

Set overall objectives.

Establish priorities.

Allocate/reallocate critical resources.

Coordinate with higher entities and

the media….think ‘buffer’.

Coordinate the demobilization of

assigned resources.

Does not direct tactical operations.

Area CommanderArea Commander

Public Information Officer

Public Information Officer

Liaison OfficerLiaison Officer

Planning Chief

Planning Chief

LogisticsChief

LogisticsChief

Critical ResourcesUnit Leader

Critical ResourcesUnit Leader

Situation Unit LeaderSituation

Unit Leader

ICP

ICP

Page 29: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Multi-agency Coordination System

A combination of facilities, equipment, personnel,

procedures, and communications integrated into a

common system with responsibility for coordinating

and supporting incident management activities.

Page 30: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Why Focus on Coordination?

• Increasing incident complexity • Complex and confusing legal authorities• Increasing litigation • Increasing response costs • High property losses • Life, health, safety issues• Media and public scrutiny• Political, legislative and budgetary ramifications• Competing priorities

Page 31: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Multi-agency Coordination Centers

– Provide support and coordination to incident command.

– Identify resource shortages and issues.

– Gather and provide information.

– Implement multiagency coordination entity decisions.

Local EmergencyOps Center

(EOC)

Local EmergencyOps Center

(EOC)

Incident Command

Post

Incident Command

Post

StateEmergencyOps Center

(EOC)

StateEmergencyOps Center

(EOC)

Joint FieldOffice(JFO)

Joint FieldOffice(JFO)

Incident Command

Post

Incident Command

Post

Incident Command

Post

Incident Command

Post

Area Command

Area Command

Page 32: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Expansion vs. ActivationMulti-agency coordination centers/entities may be

established through:

Expanding an existing function that includes

full-time staff and pre-emergency administrative

systems and controls.

Or

Activating a structure based on interagency

mutual-aid agreements during an emergency.

Page 33: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Activating Coordination Centers– When an emergency situation threatens, significantly impacts the

agency, or involves other agencies

– When pre-established threat levels are reached

– Under pre-established guidelines (recommended)• Joint powers agreements or memorandums of understanding• Jurisdictional response plans • Without pre-established guidelines• When there is an interagency need to coordinate• When resource requests exceed availability

Page 34: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Joint Field Office

JFO Coordination Group

Office of Inspector General

Operations Section

Logistics Section

Planning Section

Finance and Admin

Senior Federal Law Enforcement

Official

State, Local and Tribal

Representative(s)

Other Senior Federal Officials

Federal Coordinating

Officer

JFO Coordination Staff

JFO Sections

External AffairsChief of Staff-----------------------Liaison Officer

Safety CoordinatorSecurity Officer

Infrastructure Liaison

Others as needed

Defense Coordinating Officer (DCO)

Principal Federal Official

Focal coordination point for Federal support to on-scene incident management efforts (Federal MACC).

Page 35: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

NRP Coordination Structure

Joint Field Office

Regional Response

Coordination Center

National Operations

Center

Interagency Advisory Council

State Emergency Operations

Center

Multiagency Coordination Entity Strategic coordination

Multi-agency Coordination Centers/EOCs

Support and coordination

Incident Command Directing on-scene emergency management

NIMS RoleJFO

Coordination Group

AreaCommand

Incident Command

Post

Incident Command

Post

Incident Command

Post

Field LevelRegional

Level

NationalLevel

Local Emergency Operations

Center

An Area Command is established when needed due to the complexity or number of

incidents.

Role of regional components varies depending on scope and

magnitude of the incident.

Multi-agency Coordination System

Page 36: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Initial UCMeeting

Incident/Event

Notification

Initial Response& Assessment

Incident BriefICS-201

Preparing for the Tactics

Meeting

Operations Briefing

Execute Plan & Assess Progress

New OpsPeriodBegins

Command &General Staff

Meeting /Briefing

IC / UC Develop/Update

ObjectivesMeeting

Preparing for the Planning

Meeting

Planning Meeting

IAP Prep &

Approval

Tactics Meeting

RMS #1 Incident & Notification

RMS #2 Initial Objectives

RMS #3Initial Response

RMS #4Initial Strategy

Meeting

RMS #5Initial IAP

Development

RMS #6IAP Completion

& Sub-PlanDevelopment

RMS #7Form Flow

Process

RMS #8Planning Meeting

RMS #9Post IAP Debrief

RMS #10Task ID

& Logistics Facilitation

RMS #11Post Logistics

Debrief

RMS #12Pre-implement

DebriefRMS #19

Initiation ofIAP

Development

RMS #13IAP Implemented

RMS #15Expenditures

RMS #16Total

Expenditures

RMS #17Operations

Meeting

RMS #18Strategy Meeting

RMS #14Post Operations

Debrief

Coordinated Planning

Page 37: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Jurisdictionally Transparent Functions

The Joint Information Center is used to

coordinate emergency information, crisis

communications and public affairs functions;

must include representatives of all stakeholders.

Technical Specialists are personnel with special

skills who can be used anywhere within a

response organization.

Page 38: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Trans-boundary Personnel• Joint Response Team advisory personnel not filling On Scene/

Incident Commander roles as per Section 304.5 of the JMPCP provide a variety of counseling and debriefing support.

• Liaison Officers can be requested as per Section 404 of the JMPCP at both Incident Command Posts.

• Public Information Officers and Communications Officers working at a (Joint) Information Center.

• Regional Environmental Emergency Team and Environmental Unit Leader and/or Technical Specialists working at either Command Post location.

• Representatives of the Responsible Party, if applicable.

Page 39: Incident Command System Overview CANUSLANT Incident Management Workshop Portland, ME – May 15, 2007 LCDR Matt McCann

Questions?