ics plain & simple

15
Incident Command System ICS Plain and Simple Copyright © 2013 by Herbert Cole. All rights reserved. Sunday, May 26, 13

Upload: herbert-cole

Post on 09-Aug-2015

1.147 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Ics plain & simple

Incident Command SystemICS Plain and Simple

Copyright © 2013 by Herbert Cole. All rights reserved.

Sunday, May 26, 13

Page 2: Ics plain & simple

What is ICS?

Originally developed in Southern California during the early 1970's, the Incident Command System (ICS) is the standard for on-scene incident management within the United States of America.

The Incident Command System (ICS) is a function based system that supports the goals and objectives of incident management in an organic and flexible manner.

Sunday, May 26, 13

Page 3: Ics plain & simple

ICS Functions• MANAGE stuff in

support of incident goals and objectives.

• DO stuff in support of incident goals and objectives.

• GET stuff in support of incident goals and objectives.

• PLAN stuff in support of incident goals and objectives.

• PAY FOR stuff in support of incident goals and objectives.

Sunday, May 26, 13

Page 4: Ics plain & simple

ICS Sections

• Command

• Operations• Logistics

• Planning / Intelligence• Administration / Finance

* In rare circumstances Intelligence can be separate section.

Each function within the ICS is assigned to a SECTION that has primary responsibility for that function. There are five* sections in the incident command system.

Sunday, May 26, 13

Page 5: Ics plain & simple

ICS Section & Functions• Command = Manage Stuff

• Operations = Do Stuff

• Logistics = Get Stuff

• Planning / Intelligence = Plan Stuff

• Administration / Finance = Pay for Stuff

Sunday, May 26, 13

Page 6: Ics plain & simple

ICS Conceptualized

Manage Stuff

Do Stuff Get Stuff Plan Stuff Pay for Stuff

Sunday, May 26, 13

Page 7: Ics plain & simple

Functional Responsibilities

ICS is an ORGANIC system, meaning that it expands and contracts as needed in support of the incident goals and objectives. As an ORGANIC system, ICS is FLEXIBLE.

ICS is NOT a rigid organizational hierarchy. It may be that in the early stages of an incident there will be resource constraints that require one person to oversee multiple functional areas.

IMPORTANT: Check your Ego at the door. ICS is Ego NEUTRAL! You may be the boss in everyday operations, but in ICS you fill a function as needed in support of incident objectives.

Sunday, May 26, 13

Page 8: Ics plain & simple

Command (Manage Stuff)

The seed to ICS implementation begins with ONE person, the Incident Commander. The Incident Commander is the first person on scene and is responsible for the following:

1. Initial scene stabilization2. Establishing initial priorities and objectives3. Sets goals and defines the ICS functions necessary to

respond to the incident4. Assigns Deputies and Section Chiefs as needed

Sunday, May 26, 13

Page 9: Ics plain & simple

Operations (Do Stuff)The Operations Section is where the primary incident response activities occur. These activities are typically carried out by Public Safety (Fire, EMS, Law Enforcement, etc…) and specialized volunteer groups (CERT, MRC, County Search and Rescue, etc…). Operations may be broken down further by functional duties (Branch) and geographic responsibilities (Division).

Use what you need, nothing more, nothing less. Delineation of Branch, Division, etc… within the ICS should only be done in furtherance of meeting the goals and objectives needed to manage the Incident . If you don’t need them, don’t use them.

Sunday, May 26, 13

Page 10: Ics plain & simple

Logistics (Get Stuff)The Logistics Section supports the overall material resource needs of the ICS. As the ICS evolves and an Incident Action Plan (IAP) begins to take shape, Logistics will be called upon to provide the material support necessary to meet the goals and objectives of the incident response. Logistics support may include:

• Food and Water• Shelter• Medical Supplies• Specialized Equipment

• Transportation• Communications• IT and Networking

Sunday, May 26, 13

Page 11: Ics plain & simple

Planning (Plan Stuff)The Planning and Intelligence section is responsible for collecting information, analyzing information, and creating plans and maintaining current incident status (inclusive of resource usage and allocation status). Check-in of personnel and physical resources is typically included as a function of the Planning and Intelligence Section, therefore it should be the first section established by the Incident Commander.

Sunday, May 26, 13

Page 12: Ics plain & simple

Admin/Finance (Pay for Stuff)

The Administrative and Finance Section is responsible for Records Management, Payroll, and the overall incident budget. When the operations section has long been put to bed, the Admin/Finance Section will still be sorting out paperwork, bills due, payroll issues, etc…. This is the section that will be looked to for incident review and audit materials so it is important that all ICS sections understand that …”If you didn’t write it down, it didn’t happen.”

Sunday, May 26, 13

Page 13: Ics plain & simple

Functional Organization

Do Stuff Get Stuff Plan Stuff Pay for Stuff

Manage Stuff

Sunday, May 26, 13

Page 14: Ics plain & simple

Part I Quiz1. The incident command system is a _________ based

system that is both __________ and ____________.2. ICS supports the ____________ & ______________ of

incident management.3. List the 5 ICS Sections and their corresponding function.4. ICS is the standard for on-scene incident management in

the United States. TRUE FALSE5. Draw a conceptualized diagram of the ICS.

Sunday, May 26, 13

Page 15: Ics plain & simple

About the AuthorHerbert Cole is an Emergency Management Professional based in Northern California. He is an expert in leading teams, and overseeing the implementation of resilient community oriented emergency management programs.

A nationally recognized speaker and author on Emergency Management topics, he is a strong advocate for the development of public / private resiliency partnerships that support the emergency management cycle.

Sunday, May 26, 13