Introduction to

the Incident
Command
System (ICS)
Objectives:
1. Enhance understanding of Incident Command
System as a vital tool for effective disaster
response;

2. Provide an overview of ICS – background,

concepts, principles and features, capabilities,
organization, facilities and common terminologies,
and

3. Demonstrate knowledge of basic ICS functions

through exercises & class discussion context
CC_XXXXXXXX_2
Background

 The Filipinos has always lived in harm’s way from natural hazards
because of the country’s geographical location.

 In addition, there are other emerging hazards that Filipinos have to

contend with such as climate change, pandemic situations and acts
of terrorism that require effective and efficient response
management system.

 The lessons of past disaster events have also manifested the

inadequacy and / or lack of an effective on-scene management of
emergency operations such as the ULTRA or WOWOWEE incident
on February 4, 2006, Tropical Storm “Ondoy” (International Name
“Ketsana”, Sept. 24-27, 2010), and the Quirino Grandstand Hostage
Taking on August, 2010 once again confirmed this gap, i.e., the
absence of an Incident Commander at the inception of the incident;
no ICP, and poor crowd control and media management.
Background
There are identified pre-ICS problems such as the
following:

- Too many people reporting to one supervisor

- Too many responders

- Different emergency response organizational structures

- Lack of reliable incident information

- Inadequate and incompatible communications

- No formal ICS structure

Background
• Pre-ICS problems (con’t.)
- No check-in procedures for responders

- Lack of structure for coordinated planning between

agencies

- Unclear lines of authority

- Terminology differences between agencies

- Unclear or unspecified incident objectives

Background
 Other persistent issues at the operational level

- Lack of clarity on who’s in charge; who’s directing

operations on the ground, especially in a multi-agency
operations setting
- Confusion especially for catastrophic incidents
- Political intervention
- Need for Standard Operating Procedures (SOPs)
- Inadequate expertise in managing on-scene disaster
operation activities
Background
• ICS in the Philippines – How it evolved

- Introduced in the Philippines through the ASEAN-US

Cooperation on Disaster Management, Phases 1(2004-2006) & 2
(2009-2012); US Department of Agriculture-Forest Service (US DA-
FS) as implementing agency and USAID as funding agency.

- Ratification of the ASEAN Agreement on Disaster Management

and Emergency Response (AADMER) by the ten (10) ASEAN
Member States (AMS) on December 24 2009. The AADMER called
on the Member States, among others, to prepare standard operating
procedures for regional cooperation and national action such as
regional standby arrangements and coordination of disaster relief
and emergency response.
•
Background
• ICS in the Philippines – How it evolved

•RA 10121, s-2010, otherwise known as “ An Act Strengthening the Philippine Disaster Risk Reduction and
Management System, Providing for the National Disaster Risk Reduction and Management Framework and
Institutionalizing the National Disaster Risk Reduction and Management Plan, Appropriating Funds Therefor and
For Other Purposes”

OCD MANDATE UNDER RA 10121:

MISSION – “To administer a comprehensive national civil defense and disaster risk reduction and
management program by providing leadership in the continuous development of strategic and systematic
approaches as well as measures to reduce the vulnerabilities and risks to hazards and manage the
consequences of disasters”.

TASK: Sec. 9 (g), RA 10121- “To formulate standard operating procedures for the deployment of rapid
assessment teams, information sharing among agencies and coordination (underscoring supplied) before and
after disasters at all levels”.
•
•Rule 7 (h), IRR, RA 10121 - OCD shall “establish an Incident Command System (ICS) as part of the country’s
on-scene disaster response system to ensure the effective consequence management of disasters or
emergencies”.
•
Background
• ICS in the Philippines – How it evolved (con’t.)

ICS Institutionalization Initiatives :

1. Conduct of ICS Inception Workshop; ICS Instructor Development through the conduct
of six (6) ICS Courses, namely: 5-day ICS Basic/Intermediate Course ( July 19-23, 2010),
Integrated Planning Course (Oct. 11-21, 2010), Admin. & Finance Sec. Chief Course (Feb. 28-
Mar. 1, 2011), Operations Sec. Chief Course (Mar. 3-4, 2011), Logistics Sec. Chief Course
(Mar. 4-7, 2011), and Incident Commanders’ Course (Mar. 8-11, 2011).
Thirty-four (34) participants from partner agencies, namely, BFP, PNP, DOH, DSWD,
MMDA, FNTI, Olongapo City, Davao City Rescue 911, APSA and OCD have successfully
completed the above courses and certified as ICS National Cadre of Instructors by the
NDRRMC-OCD and United States Department of Agriculture – Forest Service (USDA-FS).
They are now constituted as the core of the NDRRMC Incident Management Team (NIMT)
who can be mobilized by the National Council, as necessary, to assist in on-scene disaster
response and management in affected areas of the archipelago.
Background
• ICS in the Philippines – How it evolved (con’t.)

ICS Institutionalization Initiatives (cont.)

2. Submission of proposed NDRRMC Memorandum Circular to the Chairperson,
NDRRMC / Secretary, DND on the Use of Incident Command System (ICS) as an On-
Scene Disaster Response and Management Mechanism under the Philippine Disaster
Risk
Reduction and Management System (PDRRMS)
- Essential Features:
a. Common Terminologies
b. Basic Concepts, Principles and Features of ICS
c. Policy Statements
- Sustained ICS Capability Building Program through regular
conduct of ICS Training and Instructor Development.
-Constitution of a National Incident Management Team composed of the ICS
National Cadre
What Is an Incident?
• An incident is . . .
. . . an occurrence, caused by
either human or natural
phenomena, that requires
response actions to prevent
or minimize loss of life, or
damage to property and the
environment.
 What is ICS?
A standard, on-scene, all-hazard incident
management concept that can be used by all
DRRMCs/ emergency management and
response agencies

• Used for routine incidents as well as major

disasters; activated at first response

Allows its users to adopt an integrated

organizational structure to match the complexities
and demands of single or multiple incident without
being hindered by agency or jurisdictional
boundaries.
 ICS Purposes
Using management best practices, ICS
helps to ensure:
The safety of responders and others.
The achievement of tactical objectives.
The efficient use of resources.
ICS Benefits
Meets the needs of incidents of
any kind or size
Allows personnel from a variety of
agencies to meld rapidly into a
common management structure
Provides accountability and a
planning process
Provides logistical and
administrative support to
operational staff
Is cost effective by avoiding
duplication of efforts
Incidents Managed Using ICS

 Natural disasters – typhoons, tornadoes,

floods, earthquakes, volcanic eruption,
tsunami
Human and animal disease outbreaks
Search and rescue missions
Hazardous materials incidents
Terrorist incidents
 Hostage-Taking
Recovery operations
Distribution of humanitarian assistance
Planned events such as fiestas, parades,
sport events, conferences, concerts, etc.
Countries Using ICS
Fully Implemented:
- United States
- Canada
- Australia
- New Zealand
- Mexico

In Transition:
South Asia
- Bhutan
- India – 2010 Indian Response System
- Sri Lanka
ASEAN Nations
- Indonesia
- Philippines
- Thailand
- Brunei Darussalam
Africa – Ethiopia, Ghana
Latin America – Many countries
Basic Principles
of ICS
Non-Permanent Organization
ICS is only activated in response to an incident
NOT a permanent organizational structure or
secretariat
During incident response, ICS personnel leave
“regular” positions
ICS personnel fill positions within organization
based on their ICS training and experience
UNITY OF COMMAND AND CHAIN OF COMMAND

UNITY OF COMMAND - CHAIN OF COMMAND -

Establishes a clear line of Orderly ranking of
supervision management positions in line
of authority

Unity of command means Chain of command refers

that every individual has a to the orderly line of
designated supervisor to authority within the ranks
whom they report at the of the incident
scene of the incident. management organization.
19
 Span of Control

ICS span of control for any supervisor:

Is between 3 and 7 subordinates.
Optimally does not exceed 5 subordinates.
 Modular Organization
Organizational structure based on:
Size, type, and complexity of
the incident
Specific hazards created
by the incident
Incident objectives and planning
process

Guidelines:
 Only needed functions/positions are filled
 Each activated element must have a person in charge
 An effective span of control must be maintained
 Delegation of Authority
Commander
Incident

Res fficial  The Responsible Official establishes

pon
O
sibl policy, direction, parameters, and delegates
authority to the Incident Commander for the
e

on-scene response
 The Incident Commander has direct
tactical and operational responsibility for
conducting incident management activities
 Responsible Official generally not at scene
all the time but maintains contact as
necessary
Information from the Delegation of Authority
used to develop Incident Objectives and
Incident Action Plan
Reliance on an Incident Action Plan
• The Incident Commander approves an Incident Action
Plan (IAP) that:
- Specifies the incident objectives
- States the activities to be completed
- Covers a specified timeframe, called
an operational period
- May be oral or written
- Is developed for a specific operational period
- Takes into account direction the Responsible
Official as well as legal and policy considerations
Resource Management

Resources – refer to any personnel, team, equipment,

aircraft, supplies and facilities available to
support management and response activities.

Resource Management includes processes for

categorizing, ordering, dispatching, tracking, and
recovering resources. It also includes processes for
reimbursement of resources, as appropriate.

24
24
Common Terminology
In ICS, the use of common terminology applies
to:
a. Organizational Elements
- All ICS major functions and functional units are
named and defined. Terminology for each
organizational element is standard consistent.
b. Resource Descriptions
- Major resources personnel, facilities, major
equipment, and supply items are given common
names and are listed by type and kind with respect
to their capabilities.
Common Terminology (cont.)

c. Incident Facilities
– Facilities used during the response are named
according to common terminology.
d. Position Titles
– All ICS managers and supervisors are referred to
by standardized ICS titles such as Officer, Chief,
Director, Supervisor or Leader.

26
Common Terminology (cont.)
Common Terminology and Clear Text
- All ICS communications should use clear text
(that is, plain language). Do not use radio codes,
agency-specific codes, acronyms, or other jargon.

This is Unit 1, we
have a
10-37,
Code 2.

27
Integrated Communications

Integrated ICS communications involve the

following three (3) elements:
a. Communication plans that address
resources and requirements.
b. Modes of communication (hardware) to be
used to transfer information.
c. Procedures and processes for
disseminating information.

28
Integrated Communications (cont.)
Communications networks that may be
required:

a. Command Net
b. Tactical Nets
c. Support Nets
d. Ground-to-Air
e. Air-to-Air

29
10. Integrated Communications (cont.)

COMMAND NET

INCIDENT COMMANDER

LIAISON OFFICER
SAFETY OFFICER
INFORMATION OFFICER

PLANNING OPERATION LOGISTICS FINANCE/ADMIN

DAMAGE ASSESSMENT &

Needs Analysis TEAM
AL

SAR TEAM
TAC ET
I C
N
T

MEDICAL TEAM

FIRE SUPPRESSION TEAM

30
30
 ACCOUNTABILITY
A number of procedures ensure accountability of
resources (personnel and equipment):
a. Check-in – All responders, regardless of
agency affiliation, must check-in to the
incident and receive an assignment,
following the procedures established by
the IC.
b. Incident Action Plan – Response operations
must be directed and coordinated as
outlined in the IAP.

31
ACCOUNTABILITY (cont.)

c. Unity of command – Each individual involved in

incident operations is assigned
to only one supervisor.

d. Span of control – Supervisors must be able to

effectively supervise their
subordinates and manage all
resources under their
supervision.
32
ACCOUNTABILITY (cont.)

e. Division/ Group f. UNIT LOGS – a record of

Assignment Lists – identifies personnel assigned and
resources with active major events in all ICS
assignments in the organizational elements
Operations Section

DIVISION A DIVISION C UNIT LOG UNIT LOG

DIVISION B UNIT LOG

UNIT LOG
 ACCOUNTABILITY (cont.)

g. Resource tracking – Supervisors must record

and report resource status changes as
they occur.
Manual System T-Card System
s or
using forms ap s
ic M rd
n et Boa
g s
Ma tatu
S

34
 Command vs. Coordination
 Command – Incident Commander commands on-scene
operations and reports to Responsible Official

 Coordination - Responsible Official coordinates with other

agencies through venues such as an EOC or interagency
committees

 EOCs and interagency committees provide support

and coordination to incident command by:
- Making policy decisions
- Establishing priorities
- Resolving critical resource issues
- Mobilizing and tracking resources
- Collecting, analyzing, and disseminating information
 Command vs. Coordination - PDRRMS Context

 Coordination and
support serve the needs
of the command functions National/Regional/Local
– generally located away
from the site, most often OpCen
at the DRRMC Operations
Center (OpCen)
Coordination

 Command is the Command

direct management of
the on-scene Incident Incident
operations
 ICS
Organization
ICS – Primary Organization Functions

Incident
Commander

Information Safety

Liaison

Finance/
Operations Planning Logistics
Administration
 ICS Functions: Who Does What?
Command: Overall Finance/Admin: Monitors
responsibility for the incident. incident costs and
Sets objectives. provides fiscal guidance.
Incident Procures needed
Command resources

Operations Planning Logistics Finance/Admin

Section Section Section Section

Operations: Planning: Logistics:

Develops tactical
organization and directs
all resources to carry out
the Incident Action Plan
Develops Incident Provides resources
Action Plan to and all other
accomplish objectives. services needed to
Maintains resource & support the incident
situation status
 Incident Complexity and Resource Needs
Incident Resource Needs ICS Structure
Complexity
 Large Disaster – All Units Activated
Incident Commander

Public Information Liaison

Officer Officer

Safety
Officer

Finance/Admin.
Operations Section Planning Section Logistics Section
Section

Resources Demob. Service Support Time Compensation

Unit Unit Branch Branch Unit Claims Unit
Air Ops
Branches
Branch
Situation Doc. Procurement Cost
Unit Unit Commun. Supply Unit Unit
Unit Unit
Divisions Groups
Medical Facilities
Unit Unit
Strike Team
Ground
Food
Task Force Support
Unit
Unit
Single Resource
UNIFIED COMMAND
 one of the incident management options

 enables all agencies that have jurisdictional or functional

responsibility for the incident to manage an incident together
by establishing a common set of incident objectives and
strategies.

 allows Incident Commanders to make joint decisions by

establishing a single command structure.

 participating agencies retain their authority,

responsibility or accountability.

42
UNIFIED COMMAND (cont.)

Unified Command is used for the following

types of incidents:
 Incidents involving multiple
jurisdictions.
 Incidents involving a single jurisdiction
with multi-agency participation.
 Incidents involving multiple
jurisdictions with multi-agency
participation.
43
UNIFIED COMMAND (cont.)

Under unified command, there will always

be:

1. One Incident Command Post (ICP)

2. A single ordering point
3. A single coordinated Incident Action
Plan
4. One Operations Section Chief

44
UNIFIED COMMAND (cont.)
Example: Managing an incident using Unified Command
(multiple jurisdictions)
UNIFIED
COMMAND

A A B C

C Strategy, Incident
Objectives and
Action Plan

B OPERATIONS
SECTION
CHIEF

FLOODING SAR Group

Medical
Group
Security
Group

INCIDENT
45
 ICS Facilities and Symbols:

 Incident Command Post

 Base B
 Camps C
 Staging areas S

 Helibase H

 Helispots H-3
Questions ?

47