Presentation is loading. Please wait.

Presentation is loading. Please wait.

Incident Command System (ICS) - Review -

Similar presentations


Presentation on theme: "Incident Command System (ICS) - Review -"— Presentation transcript:

1 Incident Command System (ICS) - Review -
Santa Clara County Fire Officer Academy Incident Command System (ICS) - Review - Steve Prziborowski May 2008

2 Incident Command System Definition
An Incident Management System using: a common organizational structure assigned incident resources stated objectives

3 Elements of an effective Incident Management System
Suitable for use regardless of jurisdiction or agency involved The organizational structure must be able to adapt to an incident regardless of how complicated Expandable in a logical manner from initial response to a major emergency so as not to have one plan for "everyday" use and a separate plan for "the big one” Basic common elements in organization, terminology, and procedures

4 The Incident Command System (ICS) as a Management Tool
Ensures Unity of Command in that each individual participating in the operation only reports to one supervisor. Provides a standard set of terms for communicating designation of resources and facilities. Plain English is used rather than 10-codes. Lines of authority provide for lines of communication. This means that the right people receive the proper messages because all communications follow the chain. Provides for Span of Control which is the number of subordinates one supervisor can manage effectively (3-7 with 5 preferred).

5 ICS as a Management Tool (cont.)
Has all-risk design. Confusion is reduced by the fact that the same methods are used regardless of the type of situation and agencies involved. Provides for safety of personnel. All persons are accounted for and efforts are coordinated in a manner which provides for the safety of all persons. Provides for modular expansion. As either the incident enlarges or additional resources become available, span of control continues to meet the needs. Improved resource utilization. With a clear organizational structure, each resource can concentrate on its assignment and eliminate duplication of effort.

6 ICS should be used for all incidents…not just the “big ones”.
Why?

7

8 Span of Control range is three to seven

9 OPTIMUM SPAN OF CONTROL IS ONE TO FIVE

10 Branch That organizational level having functional or geographic responsibility for major segments of incident operations (such as Air Ops, Service or Support). The Branch level that is organizationally between Sections and Divisions/ Sectors/Groups (>5).

11 BRANCHES MAINTAIN SPAN OF CONTROL
THERE ARE TWO TYPES OF BRANCHES Geographic Branches

12 LOGISTICS SECTION CHIEF
BRANCHES (continued) Functional Branches LOGISTICS SECTION CHIEF SERVICE BRANCH SUPPORT BRANCH Communications Unit Medical Unit Food Unit Facilities Unit Supply Unit Ground Support Unit

13 DIVISIONS Will always divide an Incident geographically
B C 1 2 3 4 5 6 7 STRUCTURE INCIDENT HAZMAT OR WILDFIRE INCIDENT

14 GEOGRAPHIC DIVISIONS:
1 2 3 4 5 6 7 OUTER INNER PERIMETER PERIMETER

15 GROUPS POOL SPECIALIZED RESOURCE TEAMS or
ESTABLISH FUNCTIONAL AREAS OF OPERATION

16 FUNCTIONAL GROUPS:

17

18 E-x-p-a-n-d-a-b-l-e

19 In ICS, common terminology is applied to:
Organizational elements: Sections, Units, Divisions, etc. Position Titles: Officers, Chiefs, Leaders, Managers Resources: Engine, Truck, Tanker, Crew, Dozer Facilities: Base, Helispot, Camp, ICP, Helibase

20 ICS Integrated Communications
COMMUNICATIONS SYSTEMS FREQUENCY AND RESOURCE USE PLANNING INFORMATION TRANSFER PROCEDURES

21 “Clear Text“ The use of plain English in radio communications transmissions. No Ten Codes, or agency specific codes are used when using clear text.

22 TWO WAYS TO ORGANIZE INCIDENT COMMAND
B A C SINGLE COMMAND UNIFIED COMMAND

23 MANAGING AN INCIDENT USING UNIFIED COMMAND
B C UNIFIED COMMAND A B C OBJECTIVES AND STRATEGY INCIDENT ACTION PLAN OPERATIONS SECTION CHIEF HAZMAT INCIDENT DIV. A DIV. B DIV. C

24 Under Unified Command there will always be:
A single, coordinated IAP One Ops Section Chief One Incident Command Post A Unified Ordering Point

25 Reasons to Transfer Command
More qualified person assumes command. A jurisdiction or agency change in command legally required or makes good management sense Normal turnover of personnel on long or extended incidents.

26 Upon arrival at the Incident a Higher Ranking Officer shall:
1. ASSUME COMMAND or 2. MAINTAIN COMMAND or 3. REASSIGN COMMAND to a third party or 4. FILL ANOTHER ICS POSITION

27 TRANSFER OF COMMAND BRIEFING
What have we got What do we need Basically the who, when, where, what, why Incidents current status & prognosis? The plan of action? Current strategy/tactics Any resources at scene, enroute and / or ordered? Current ICS structure Any related issues or concerns? Basically the info from the ICS 201 Form

28

29

30 THE COMMAND STAFF: COMMAND STAFF INCIDENT COMMANDER INFORMATION
LIAISON SAFETY INCIDENT COMMANDER OPERATIONS PLANNING LOGISTICS FINANCE COMMAND STAFF 7-12

31

32 Incident Commander “IC”

33 Incident Commander Responsibilities
The individual responsible for the management of all incident operations. Establishes a command organization. Assesses situation, determines scope of incident, and prioritizes the problem. Evaluates overall strategy on a continual basis. Directs activities and maintains communications with Command Staff, Plans, Logistics, and Operations.

34 INCIDENT COMMANDER MAJOR RESPONSIBILITIES AND DUTIES
Keep agency administrator informed of incident status Approve the use of students, volunteers, and auxiliary personnel Authorize release of information to the news media Order the demobilization of the incident

35 IC - ESTABLISHES THE IMMEDIATE PRIORITIES
FIRST PRIORITY IS INCIDENT SAFETY People involved in incident Responders Other emergency workers Bystanders

36 IC - ESTABLISHES THE IMMEDIATE PRIORITIES
SECOND PRIORITY IS INCIDENT STABILIZATION Protect the public Sufficient kinds of resources? Sufficient sized organization?

37 Command Staff They report directly to the Incident Commander
INFORMATION OFFICER SAFETY OFFICER They report directly to the Incident Commander LIAISON OFFICER

38 Safety Officer

39 Safety Officer Responsibilities
A Command Staff member responsible for monitoring and assessing safety hazards, unsafe situations, and developing measures for ensuring personnel safety. Identify existing and potential hazards Keep all personnel informed of existing and potential hazards Correct unsafe acts or conditions and exercise emergency authority to prevent unsafe acts when immediate action is needed Investigate accidents within the incident area

40 Liaison Officer Several agencies will be sending personnel
IC can no longer provide sufficient time for all representatives Two or more jurisdictions may be involved

41 Agency Representative
An individual assigned from an assisting or cooperating agency who has been delegated full authority to make decisions on all matters affecting that agency’s participation. Agency Representatives report to the Liaison Officer.

42 Information Officer Responsible for interface with the media or other appropriate agencies requiring information directly from the scene. Member of the Command Staff.

43 GENERAL STAFF POSITIONS
THE GENERAL STAFF: INCIDENT COMMANDER PLANNING FINANCE OPERATIONS LOGISTICS GENERAL STAFF POSITIONS 07-17

44 Operations Chief

45 Operations Chief Responsibilities
Responsible for all tactical operations at the incident. Supervises emergency operations Establishes communication procedures with IC and subordinates Determines need for immediate and anticipated resources Requests periodic progress reports from Division/Group Supervisors

46

47

48

49 ICS RESOURCE STATUS CONDITIONS
“AVAILABLE” (Within 3 Minutes) “OUT OF SERVICE” (usually mechanical reasons) “ASSIGNED” (or “Committed”)

50 PERSONNEL ACCOUNTABILITY MAINTAINED THROUGH THE USE OF:
CHECK-IN FORM RESOURCE STATUS KEEPING SYSTEM UNITY OF COMMAND

51 PERSONNEL ACCOUNTABILITY IS ALSO MAINTAINED THROUGH :
DIVISION C DIVISION A DIVISION B UNIT LOG UNIT LOG UNIT LOG UNIT LOG DIVISION / GROUP ASSIGNMENT LISTS UNIT LOGS

52 Technical Specialists
Personnel with special skills who are activated only when needed. Technical Specialists may be needed in the areas of fire behavior, water resources, environmental concerns, resource use, or training. Technical Specialists report initially to the Planning Section but may be assigned anywhere within the ICS organizational structure as needed.

53 “ Incident Action Plan “ or IAP
The strategic goals, tactical objectives, and support requirements for the incident. All incidents require some form of an Action Plan! For simple incidents the Action Plan is not usually in written form. Large or complex incidents will require that the Action Plan be documented in writing.

54 The IAP

55 COMMUNICATIONS NETWORKS THAT MAY BE REQUIRED
Command Net Tactical Nets Support Net Ground-to-air Air-to-air 02-17

56 INCIDENT COMMAND POST Location where primary command functions are performed Only one per incident May be located with other facilities (plans, base) Normally not relocated The communications center is often located with the ICP The incident commander will be at the ICP

57 RESPONSE GUIDELINES: Assemble or update a travel kit
Prepare personal items you will need Review your emergency assignment Know to whom you will report and what your responsibility will be Ensure that family members know your destination and how to contact you

58 INFORMATION NEEDED PRIOR TO DEPARTURE FOR INCIDENT ASSIGNMENT
Incident type and name or designation Incident check-in location & time Travel instructions Communications instructions Resource order number & request number Your unit’s radio designation 06-04

59 INCIDENT CHECK-IN LOCATIONS
Incident Command Post: Resources Unit Base Or Camp(s) Staging Areas Helibase

60 FOR DIRECT TACTICAL ASSIGNMENTS REPORT TO YOUR:
DIVISION / GROUP SUPERVISOR OR OPERATIONS SECTION CHIEF OR INCIDENT COMMANDER However, at the end of first operational period, ensure that you have checked in at the Appropriate check-in location! 06-06

61 RESOURCE STATUS KEEPING SYSTEMS
T-Cards CREWS OH A/C E 2466 Incinet & ROSS

62 RESOURCE MANAGEMENT IN I.C.S.
TASK FORCES Combination of Single resources STRIKE TEAM Combination of same Kind and type

63 KINDS OF RESOURCES: Overhead Crews Equipment Aircraft

64 TYPES OF ENGINES: TYPE 1 TYPE 3 Pass around the FOG...

65 ADVANTAGES TO RESOURCE TYPING
Helps plan for resource needs In ordering resources In monitoring effectiveness of resource use

66 WAYS OF ORDERING RESOURCES
AS A SINGLE RESOURCE (1-onion) AS A TASK FORCE (various veggies) AS A STRIKE TEAM (5 lbs of onions)

67 EXAMPLES OF A SINGLE RESOURCE

68 EXAMPLE OF A MIXED RESOURCES to form a TASK FORCE:

69 REQUIREMENTS TO BE A STRIKE TEAM:
Same kind and type of resources Must have a leader Communications between resources and leader Must have transportation (as required) Operates within span of control limits (3-7)

70 SUMMARY CONSIDERATIONS
Correct / report harassment or discrimination Do not use alcohol or drugs Represent agency & self professionally 06-12

71 Questions?

72 www.code3firetraining.com website
Contact Information Steve Prziborowski cellular website


Download ppt "Incident Command System (ICS) - Review -"

Similar presentations


Ads by Google