MODULE 4: MANAGING PLANNED EVENTS AND INCIDENTS

MODULE OBJECTIVES

Upon completion of this module, the participants will be able to:

1. Describe the use of ICS for managing planned events and incidents;
2. Explain the considerations for organizing ICS; and
3. Discuss the various incident management options.

MANAGING PLANNED EVENTS

Planned events are organized gatherings such as parades, fiestas, concerts, conferences,
and other events usually characterized by having high-density population of audiences or
attendees requiring security services.

Examples of Planned Events

• Field simulation exercises and drills

• Local festivals
• National celebrations/ gatherings
• Special visits
• International conferences

Use of ICS for Planned Events

• Disasters/ incidents may threaten the lives of the attendees to the event.
• ICS helps to properly organize and preposition responders in anticipation of disasters/
incidents.

Considerations for Managing Planned Events

• Type and duration of the event

• Number and profile of attendees
• Disaster/incident scenarios
• Agencies/ organizations involved
• Resource requirements

MANAGING MAJOR INCIDENTS

Examples of Major Incidents

• Earthquakes
• Typhoons
• Floods
• Chemical spill
• HAZMAT situations
• Terrorist activities
• Civil disturbance
• Disease outbreaks

26
Characteristics of Major Incidents

• May start as major incidents (typhoons)

• May occur with little or no advanced warning (earthquakes, flash floods, bombing)
• May start as small but has potential to grow (oil spill, SARS)

Issues in Managing Major Incidents

• More casualties
• Massive damages
• Longer duration
• More agencies and jurisdictions involved
• More complex communications
• Requires more resources
• Trauma diminishes human capacity
• Greater media interest

Challenges for Major Incidents

• Time is critically important.

• The situation is unstable.
• The incident has a potential to expand rapidly.
• Communications and information may be incomplete.
• Responders may not be experienced in managing expanding incidents.
• All IMT positions are filled while a large organization is in place or is developing.
• Most or all units within sections are needed.
• Divisions/Groups are established.
• Branches may be required.
• Multiple operational periods are probably required.
• There will be a transition to a more qualified IC.
• Other agencies or jurisdictions will assist.
• Operations personnel may exceed several hundred per operational period.
• Written Incident Action Plans will be required.
• Costs associated with the incident are high.

ORGANIZING FOR PLANNED EVENT OR INCIDENT

Organizing ICS

1. Size up the situation

2. Assess if lives are at risk
3. Establish objectives
4. Determine and account resource needs
5. Develop Incident Action Plan (IAP)
6. Establish ICS organization
7. Execute IAP and monitor work progress
8. Adjust IAP as necessary

27
Considerations for Organizing ICS

• Span of control limitations

• Personnel safety
• Environmental issues

Factors in Determining the Size of the ICS Organization

• Administrative and jurisdictional complexity

• Geographical areas involved
• Span of control considerations
• Specialties required
• Logistical, planning, and other support needs
• Potential for growth
• Political importance

Organizing the Operations Section

• Organized bottom- up
• As resources increase, the structure expands into:

INCIDENT MANAGEMENT OPTIONS

Single Command

• ICS organization with single IC

• Applies during initial response

If the incident is getting larger/more complex, functions and resources are added.

28
As the incident size/complexity increases, divisions/groups are added.

For very large incident with branches…

Unified Command

• Allows different agencies/ organizations with responsibility for the incident to jointly
provide management direction
• Composed of several ICs from different agencies who work on an agreed and common
set of incident objectives

29
Incident Complex

• Applies to two or more incidents located in the same general proximity managed by a
single IMT
• Examples for Incident Complex
o Earthquakes, typhoons, floods, in the same area
o Several separate forest fires burning in close proximity
o Many separate incidents occurring simultaneously

Incidents Managed Separately

Incidents Managed as a Complex

Single Incident Divided

• Incident becomes too large and spreads to more than one jurisdiction.
• As the incident spreads, different objectives must be accomplished in different areas,
thereby requiring more IMTS.
• When to “Divide” incidents?
o When incidents have clearly different objectives
o When two or more of the principal sections are overworked due to the size of
the incident
• Considerations for Dividing a Single Incident
o Terrain and access
o Locations of future resource support
o Jurisdictional/administrative boundaries
o Current Operations Section structure
o Selection of IC, Command Staff and General Staff
o Supporting facilities
o Timing

30
Example: Flooding Incident divided into Two Incidents

Initially, flooded area was only in City A and an IMT was established. The flood spread to City
B and City C.

Incident is now too large and too complex for single IMT. Two IMTs are required.

Area Command

• An IMT functions as Area Command Team to:

o Oversee management of multiple incidents by multiple IMTs; or
o Oversee multiple IMTs managing a single very large incident
• Roles of ACT
o Establishes the overall priorities for multiple IMTs
o Allocates critical resources based on the priorities
o Reports the progress of actions of multiple IMTs to the overall agency

Example: Flooding Incident managed using Area Command

31