Transcript ICS 100 / 700 Training - Skagit County Home Page

ICS 100/700 Training
George Hadley
Based on Port of Seattle Fire course
Course Mechanics
• Two answer sheets (one for IS-100 and
one for IS-700)
• Exam questions
• Comments 100-13 on slides correlate to
questions (the comment would say
“Look at ICS 100 test question 13 and
fill in the answer on the answer
sheet.”)
Background
On February 28, 2003, President Bush issued
Homeland Security Presidential Directive 5.
HSPD–5 directed the Secretary of Homeland
Security to develop and administer a National
Incident Management System (NIMS). NIMS
provides a consistent nationwide template to
enable all government, private-sector, and
nongovernmental organizations to work
together during domestic incidents.
What is NIMS?
NIMS is a comprehensive, national approach
to incident management based on best
practices that is applicable at all jurisdictional
levels and across functional disciplines and is
designed to: 700-1
• Be applicable across a full spectrum of
potential incidents and hazard scenarios.
• Improve coordination and cooperation
between public and private entities.
What is an Incident?
An occurrence, caused by humans or natural phenomena, requiring
response actions to prevent/ minimize loss of life or damage to
property and/or the environment, including:
• Fire, both structural and wildland.
• Natural disasters, such as tornadoes, floods, ice storms or
earthquakes.
• Human and animal disease outbreaks.
• Search and rescue missions.
• Hazardous materials incidents.
• Criminal acts and crime scene investigations.
• Terrorist incidents, including the use of weapons of mass
destruction.
• National Special Security Events, such as Presidential visits
or the Super Bowl.
• Other planned events, such as parades or demonstrations. 100-4
NIMS Integration Center (1 of 2)
The NIMS Integration Center has been
established to oversee all NIMS-related
aspects and is designed to:
• Facilitate the development and dissemination of
national standards, guidelines, and protocols for
incident management training.
• Facilitate the use of modeling and simulation in
training and exercise programs.
NIMS Integration Center (2 of 2)
• Facilitate general training requirements and 700-18
approved training courses for all NIMS users.
• Review and approves, discipline-specific training
requirements and courses.
• Facilitate the development and/or publication of
national equipment standards, guidelines, and
protocols.
• Review and approve lists of emergency
responder equipment that meet national
requirements. 700-19
NIMS Components
Outline
• Preparedness
• Resource Management
• Communications and Information
Management
• Supporting Technologies
• Ongoing Management and Maintenance
• Command and Management
• Incident Command System (ICS)
NIMS Components
Preparedness
• Preparedness involves all of the actions required to
establish and sustain the level of capability
necessary to execute a wide range of incident
management operations:
• Planning
• Training and Equipping
• Exercising and Evaluating
• National-level preparedness standards related to
NIMS will be maintained and managed through the
NIMS Integration Center 700-15
NIMS Components
Preparedness Organizations
Preparedness organizations at all levels
must follow NIMS standards and
undertake the following tasks:
• Establish and coordinate emergency plans
and protocols.
• Integrate and coordinate the activities and
jurisdictions within their purview.
NIMS Components
Preparedness Organizations (cont.)
• Establish guidelines and protocols to
promote interoperability among
jurisdictions and agencies.
• Establish guidelines and protocols for
resource management. 700-16
• Establish priorities for resources and other
response requirements.
• Establish and maintain multi-agency
coordination mechanisms.
NIMS Components
Preparedness Planning
Jurisdictions must develop several types
of plans, including:
• Emergency Operations Plans (EOPs)
which describes how the jurisdiction will
respond to emergencies.
• Procedures include overviews, standard
operating procedures, field operations
guides, job aids, or other critical
information needed for a response.
NIMS Components
Preparedness Planning
• Preparedness Plans which describe how
training needs will be identified and met.
• Corrective Action or Mitigation Plans
which include activities required to
implement procedures based on lessons
learned from actual incidents or training
and exercises. 700-17
• Recovery Plans which describe the actions
to be taken to facilitate long-term recovery.
NIMS Components
Effective Resource Management
• Advance planning
• Resource identification and ordering
• Entry into mutual aid agreements ensure the
timely delivery of resources during incidents
700-20
Requests for items that the Incident Commander
cannot obtain locally must be submitted through
the EOC or Multi-Agency Coordination Entity 700-23
NIMS Components
Effective Resource Management
• Planning for demobilization at the same as
beginning the mobilization process
• Tracking resources continuously from
Mobilization to Demobilization
700-24
• Recovering resources
NIMS Components
Resource Categorization
Categorizing resources into one of two
categories:
1. Tactical Resources: Personnel and major items
of equipment that are or are potentially available
to the Operations function on assignment to
incidents are called tactical resources.
2. Support Resources: All other resources required
to support the incident. Food, communications
equipment, tents, supplies, and fleet vehicles are
examples of support resources.
NIMS Components
Resource Categorization
Resource standardization (within the two
categories):
•
Resource “Typing”
•
•
Categorizing resources by capability based on
700-21
measurable standards of capability and
performance.
Certification and Credentialing
• Helps ensure all personnel possess a
minimum level of training, experience,
physical and medical fitness, and capability for
700-22
the position they are tasked to fill.
NIMS Components
Benefit to Resource Management
Managers are able to identify, order,
mobilize, dispatch, and track resources
more efficiently
NIMS Components
Communications and Information
Communications and information management
under NIMS are based on the following:
• A common operating picture that is accessible
across jurisdictions and agencies is necessary to
700-25
ensure consistency amongst responders
• Common communications and data standards
are fundamental to Incident Management
NIMS Components
Communications and Information
Public Information Officer (PIO) advises
Incident Commander on all matters related to
public information
• Operates within the parameters of the Joint
700-12
Information System (JIS)
• Information may be controlled using a central
Joint Information Center (JIC)
NIMS Components
Joint Information Center
Joint Information Center (JIC) is the physical
location where public information staff involved
in incident management activities can collocate
to perform critical emergency information,
crisis and communications.
NIMS Components
Joint Information Center
Multiple JICs may be established:
• Information must be coordinated among
them to ensure that a consistent message
is disseminated to the public
• Each JIC must use JIS procedures and
protocols for communicating and
coordinating effectively with other JIC’s
700-14
NIMS Components
Features of JIC
• Organizations retain their independence
(even if used in a Unified Command) 700-13
• The JIC includes representatives of all
players in managing the response
NIMS Components
Unified Command
• When there is more than one responding
agency with responsibility for the incident,
the leaders of which work together to form a
700-7
Unified Command of the incident
• Unified Command work together to:
• Analyze intelligence information
• Establish a common set of objectives and
strategies for a single Incident Action Plan
NIMS Components
Area Command
• Area Command is established to:
• Oversee the management of multiple incidents.
• Oversee the management of large incidents that
cross jurisdictional boundaries
• Include incidents that are
700-8
• Not site specific
• Geographically dispersed
• Evolve over time
• Operations are conducted on the scene
• Therefore, there is no Operations Section
700-9
NIMS Components
Multi-Agency Coordination System
Multi-Agency Coordination Systems are a
combination of resources that are integrated
into a common framework for coordinating and
supporting domestic incident management
activities
NIMS Components
Multi-Agency Coordination System
• Support incident management policies and
priorities by:
• Facilitate logistics support and resource
tracking.
• Make resource allocation decisions based
700-10
on incident management priorities.
• Coordinate incident-related information.
• Coordinate interagency and
intergovernmental issues regarding incident
management policies, priorities, and
strategies.
NIMS Components
Emergency Operations Center
• Emergency Operations Center (EOC)
organization and staffing is flexible, but
should include:
•
•
•
•
Coordination.
Communications.
Resource dispatching and tracking.
Information collection, analysis, and
dissemination.
• EOCs may also support Multi-Agency
700-11
Coordination and Joint Information activities
NIMS Components
Incident Command System (ICS)
The Incident Command System (ICS) is:
• A standard, on-scene, all-hazard incident
management system.
• A proven management system based on
700-3
BEST PRACTICES.
• The result of decades of lessons learned
in the organization and management of
emergency incidents.
NIMS/ICS Principles (1 of 2)
Promote inter-operability by:
700-2
• Providing a FLEXIBLE framework that can
adjust to accommodate incidents of any size.
• Meeting the needs of incidents of any kind or
size.
• Allowing personnel from a variety of
agencies to meld rapidly into a common
100-22
management structure.
NIMS/ICS Principles (2 of 2)
• Providing logistical and administrative
support to operational staff.
• Being cost effective by avoiding duplication
of efforts.
• Providing a STANDARDIZED structure for
responding to and resolving incidents.
NIMS/ICS Features
•
•
•
•
•
•
•
•
•
Outline
Clear Communication
Modular Organization
Management by Objectives
Reliance on the Incident Action Plan (IAP)
Manageable Span of Control
Pre-designated Incident Facilities and
Locations
Chain of Command and Unity of Command
Transfer of Command
Accountability (includes check-in/check out)
NIMS/ICS Features
Clear Communication
• Common Terminology
100-7
• Helps to ensure efficient, clear communication
• Clear Text
• Standardized Terms
• Organizational Functions
• Resource Descriptions
• Incident Facilities
• Position Titles
NIMS/ICS Features
Modular Organization
• ICS organizational structure develops in a
top-down, modular fashion that is based on
the size and complexity of the incident, as
well as the specifics of the hazard
environment created by the incident.
• As incident complexity increases, the
organization expands from the top down.
• Only those functions that are necessary
for a particular incident will be filled.
NIMS/ICS Features
Management by Objectives
• An approach used to communicate functional
actions throughout the entire ICS organization
• Objectives should be SMART
• Specific
• Measurable
• Attainable
• Relevant
• Timely
700-6
• Drives the formation of the Incident Action Plan
NIMS/ICS Features
Reliance on Incident Action Plan
• Every incident must have a written or oral Incident
Action Plan (IAP) to provide all incident supervisory
personnel with direction for taking actions based on
the objectives identified in the Plan during the
100-6
operational period.
• An IAP is an oral or written plan that communicates
measurable strategic objectives to be accomplished
in the operation period.
• Operation period usually equals 12 hours.
NIMS/ICS Features
Reliance on Incident Action Plan
An IAP MUST contain:
• What do we want to do?
• Who is responsible for doing it?
• How do we communicate with each other?
• What is the procedure if someone is
injured?
NIMS/ICS Features
Manageable Span of Control
• Span of control pertains to the number of
individuals or resources that one supervisor
can manage effectively during emergency
100-13
response incidents or special events.
• Effective span of control:
• Range: 3 – 7 resources per supervisor 700-4
• Ideally 5 resources per supervisor
NIMS/ICS Features
Incident Locations & Facilities
• Incident Command Post (ICP) is the location from
which the Incident Commander oversees all
incident operations.
• Must be positioned outside the hazard but close enough
100-18
to maintain incident command.
• Staging Areas are temporary locations at an
incident where personnel and equipment are staged
100-16
while awaiting tactical assignment.
• Base is the location from which primary logistics
and administrative functions are coordinated and
administered.
NIMS/ICS Features
Incident Locations & Facilities
• Camp is the location where resources may be kept
to support incident operations if a Base is not
100-23
accessible to all resources.
• Helibase is the location from which helicoptercentered air operations are conducted .
• Helispots are more temporary locations at the
incident, where helicopters can safely land and
take off.
NIMS/ICS Features
Chain and Unity of Command
• Chain of command means that there is an
orderly line of authority within the ranks of
the organization.
• Unity of command means that every
individual is accountable to only one
designated supervisor to whom they report
at the scene of an incident.
NIMS/ICS Features
Transfer of Command
The process of moving the responsibility
for incident command from one Incident
Commander to another and always
includes a briefing.
NIMS/ICS Features
Transfer of Command
Transfer of command may take place when:
• A more qualified person assumes command.
• Transfer of Command is NOT required when a higher ranking
officer arrives on scene
• The incident situation changes over time, resulting in a
legal requirement to change command.
• Changing command makes good sense, e.g., an Incident
Management Team takes command of an incident from a
local jurisdictional unit due to increased incident
complexity.
• There is normal turnover of personnel on long or
extended incidents, i.e., to accommodate work/rest
requirements.
• The incident response is concluded and incident
responsibility is transferred back to the home agency.
NIMS/ICS Features
Accountability
•
•
•
•
Orderly Chain of Command
Resource Tracking
Incident Record Keeping
Check-In
NIMS/ICS Features
Personnel Check-In
• Check-in officially logs you in at the incident
• Each responder must check in only once
• After check-in, responders must locate their
incident supervisor and obtain their initial
briefing
100-21
• Check-in helps to:
•
•
•
•
•
Ensure accountability
Track resources
Prepare personnel for assignment
Organize demobilization
Locate personnel in the event of an emergency
100-19
ICS Organization
Incident
Commander
Public Information
Officer
Operations
Section
Planning
Section
Logistics
Section
Liaison
Officer
Command
Staff
Safety
Officer
100-5
Finance/Admin
Section
General
Staff
100-2
ICS Organization
• The ICS Organization does not correlate to
any single agency
• Highest ranking official in the organization’s dayto-day operations may not be the most qualified
to manage an incident
NIMS/ICS Features
Standardized Position Titles
• At each level of the ICS Organization, individuals
of primary responsibility have distinct titles which
serves the following purposes
• Titles provide a common standard for all users
• Distinct titles for ICS positions allows for filling
ICS positions with the most qualified individuals
100-11
rather than by rank or seniority
• Standardized position titles are useful when
requesting qualified personnel
• ICS utilizes standardized position titles and
structure to avoid confusion between the incident
and a person’s day-to-day position
100-8
700-5
• Confusion over position titles has been a significant
stumbling block in the past
NIMS/ICS Features
Position Titles
ORGANIZATIONAL
LEVEL
TITLE
SUPPORT
POSITION
Incident Command
Incident
Commander
Deputy
Command Staff
Officer
Assistant
General Staff
(Sections)
Chief
Deputy
Branch
Director
Deputy
Division/Group
Supervisor
N/A
Unit
Leader
Manager
Strike Team/ Task
Force
Leader
Single
Resource
Boss
NIMS/ICS Features
Incident Command
• Incident Commander is the one position that is
always staffed
100-3
• The Incident Commander is always a highly
qualified individual trained to lead the incident
response
• Incident Commander has overall responsibility
for managing the incident by objectives,
planning strategies, and implementing tactics
• Incident Commander must be fully briefed and
should have a written delegation of authority
NIMS/ICS Features
Incident Command
Incident Commander is responsible for
• Ensuring incident safety
• Providing information services to internal
and external stakeholders
• Establishing and maintaining liaison with
other agencies participating in the incident
Incident Commander may appoint a Deputy
• Deputy must be as proficient as Incident
Commander
NIMS/ICS Features
Expanding the Organization
• Each Function may be expanded/subdivided
as needed
• Incident Commander performs all functions
unless/until it is necessary to delegate
Incident Commander is always responsible until
100-1
authority is delegated to another person
ICS Organization
Command Staff
Incident Commander
Liaison Officer
Safety Officer
Public Information Officer
Command Staff
• Public Information Officer: serves as the
conduit for information to internal and
external stakeholders, including the media
or other organizations seeking information
100-10
directly from the incident or event.
• Safety Officer: monitors safety conditions
and develops measures for assuring the
100-15
safety of all assigned personnel.
• Liaison Officer: as the primary contact for
supporting agencies assisting at an incident.
100-20
ICS Organization
General Staff
Incident
Command
Operations
Section
Planning
Section
Logistics
Section
Financial
Administration
section
Operations Section
• Conducts tactical operations to carry out the
Incident Action Plan. Develops the tactical
objectives and organization, and directs all tactical
resources.
100-9
• The Operations Section Chief is normally the
person with the greatest technical and tactical
expertise in dealing with the problem at hand
• Operations Section develops “bottom up”
• Single Resources, Task Forces, Strike Teams are
commonplace
• Branches, Groups, and Divisions may be added
to maintain appropriate span of control
Components of the Operations Section
Operation Section
Task Force
Strike Team
Single Resource
Resources, Strike Teams, & Task Forces
• Single Resources may be individuals, a piece of
equipment and its personnel complement, or a
crew or team of individuals with an identified
supervisor that can be used at an incident
• Strike Teams are a set number of resources of the
same kind and type with common communications
operating under the direct supervision of a Strike
Team Leader
• Task Forces are a combination of mixed resources
with common communications operating under the
direct supervision of a Leader
Expanding the Operations Section
Divisions
Divisions are used to divide an
incident geographically
Groups
Groups are used to describe functional
areas of operation
Branches
Branches are used when the number
of Divisions or Groups exceeds the
span of control and can be either
geographical or functional
Divisions and Groups
Example
Operations
Section
Division A
(East Side)
Health & Safety
Group
Public Works
Group
Electric Utilities
Specialist
Water Sanitation
Specialist
Branches
Example
Operations
section
Emergency
Services
Health &
Medical
Shelter &
Mass Care
Law
Enforcement
Perimeter
Control
Investigation
Group
Public
Works
Utilities
Group
Debris
Removal
Group
Planning Section
The major activities of the Planning Section
100-12
may include:
• Collecting, evaluating, and displaying incident
intelligence and information
• Preparing and documenting Incident Action
Plans
• Conducting long-range and/or contingency
planning
• Developing plans for demobilization
• Maintaining incident documentation
• Tracking resources assigned to the incident
Expanding the Planning Section
Planning
Section
Resources
Unit
Situation
Unit
Documentation
Unit
Demobilization
Unit
Technical
Specialist
Logistics Section
The Logistics Section is responsible for all of
the services and support needs, including:
• Ordering, obtaining, maintaining, and accounting
for essential personnel, equipment, and supplies
• Providing communication planning and
100-14
resources
• Setting up food services
• Setting up and maintaining incident facilities
• Providing support transportation
• Providing medical services to incident personnel
Expanding the Logistics Section
Logistics
Section
Service
Branch
Communication
Unit
Medical
Unit
Support
Branch
Food Unit
Supply Unit
Facilities
Unit
Ground
Support
Unit
Finance/Administration Section
The Finance/Administration Section is
responsible for:
• Contract negotiation and monitoring
• Time recording
• Cost analysis
• Compensation for injury or damage to
property
• Manage costs related to the incident
100-17
Expanding the Finance/Administration
Section
Financial
Administration
section
Procurement
Unit
Time Unit
Cost Unit
Compensation
Claims Unit
The End!
CONGRATULATIONS!!!!
You have completed ICS 100 and 700.
Please verify that you have filled in one
and only one answer for each question
Please turn in your exam sheet as you
leave