1. Introduction to Incident Command System (IS 100b)
Curry Mayer, Chief
Training Branch
California Emergency Management Agency

2. The Incident Command System (ICS) In the Beginning
ICS was developed in the aftermath of a devastating 1970s wildfire in California
The U.S. Forest Service, Cal Fire & other Southern California Fire Agencies formed FIRESCOPE
(Firefighting RESources of California Organized for Potential Emergencies).
ICS was developed in the aftermath of a devastating 1970s wildfire in California where numerous problems were encountered.

3. Incident Command System
Standardized, on-scene, all-hazard incident management concept
Efficiently integrates responders from a variety of agencies
Allows personnel from a variety of agencies to meld into an integrated organizational structure to match the complexities and demands of single or multiple incidents without being hindered by jurisdictional boundaries
match the complexities and demands of single or multiple incidents without being hindered by jurisdictional boundaries

4. WHY DO WE NEED ICS? A coordinated response system
Standardization of Response Organization
Interoperability of communications & resources

5. Basic ICS Features Common terminology Modular organization
Management by objectives
Reliance on an Incident Action Plan

6. Basic ICS Features Chain of Command and Unity of Command
Unified Command
Manageable Span of Control
Resource Management
Predesignated Incident Facilities

7. ICS Benefits The safety of responders, workers and others
Standardized approach to incident management applicable for use in all hazards by all levels of government
The efficient use of resources
Manage a variety of incidents emergency and non emergency like parades, sporting events, etc.

8. Common Terminology Using common terminology helps define:
Organizational functions
Incident facilities
Resource descriptions
Position titles
Cannot use agency or radio terminology
Reduces confusion between a person’s response position & day-to-day professional position

9. SEMS & NIMS & ICS
Both the Standardized Emergency Management System (SEMS) and the National Incident Management System (NIMS) are required to use ICS
SEMS - Government Code § 8607 – California Emergency Services Act in January 1993
NIMS - Homeland Security Presidential Directive 5 (HSPD-5) in February 2003

10. Homeland Security Presidential Directive 5
Adoption of NIMS is a condition for receiving Federal preparedness assistance (through grants, contracts and other activities by:
State
Tribal and
Local organizations

11. NIMS & ICS
NIMS is a core set of concepts, principles and terminology for incident command and multiagency coordination because it uses ICS
NIMS is a consistent, nationwide approach for all levels of government to work effectively because it requires the use of ICS

12. Modular Organization
Incident command structure develops from the top-down
Size is based upon the complexity of the incident
Incident objectives
Specifics of hazard environment created by incident
Only necessary functions are activated
Each activated element will have 1 person in charge

13. ICS Modular Organization
Large Incident Organization
Small Incident Organization

14. Span of Control
ICS Span of Control – Number of people one person can effectively supervise
Between 3 and 7 subordinates with 5 being optimum

15. Span of Control Considerations
The Span of Control can be affected by:
Type of incident
Nature of the task
Hazards or safety factors
Distance between personnel or resources

16. As the Incident Grows Add Modules

17. Span Out of Control
YOU

18. 5 SEMS/ICS Organizational Functions (Command/Management & General Staff)
Command or Management
PLANNING/
INTELLIGENCE
FINANCE/
ADMINISTRATION
OPERATIONS
LOGISTICS

19. ICS Uses Position Titles
Provides a common standard for performance expectations
Helps to ensure that qualified individuals fill each position
Standardization eliminates confusion between agency position titles & duties (day to day) and ICS Position Titles
Describes the responsibilities of the position

20. Command Staff

21. What History Tells Us
Main reason most incident responses fail is poor management of resources
Reports show most response problems result from inadequate management

22. Incident Command There are 3 Incident Command Structures
Single Incident Commander
Unified Command
Area Command

23. Incident Commander

24. Incident Commander Establishes Incident Command Post (ICP)
Activates and assigns Command Staff positions
Creates ICS Sections
Conducts Initial Briefing

25. Incident Commander
Approves all plans, resource requests and media releases
Guarantees incident safety
Provides information to internal and external stakeholders

26. Incident Commander
In charge until authority delegated to another person
Incident scope get more complex or
beyond existing authorities of IC
(If Incident Commander changes, all staff are notified of the change)
The only position that is
always staffed

27. Unified Command Two or more Commanders from various Jurisdictions
Operate together from a single command structure
Single set of incident objectives
Collaborative strategies
Single Incident Action Plan

28. Area Command Sets overall strategy and priorities
Identifies and allocates resources
Makes sure objectives are met
Make certain that strategies are followed
Maintain effective communication
Assists in transition to full
recovery operations
Area
Command
ICP 28

29. Public Information Officer

30. Public Information Officer
One per Incident
Advises Incident Commander on information dissemination and media relations
Obtains information from and provides information to Planning Section, community and media
Incident Commander approval needed for all releases

31. British Reporter

32. Safety Officer

33. Safety Officer One per incident
Advises Incident Commander on safety issues
Works with Operations Section to ensure safety of field personnel
Reviews Action Plan for safety implications
Has authority to stop unsafe activities (Outside of the Action Plan)

34. Liaison Officer

35. Liaison Officer Point of contact for other responding organizations
Assists in-coming organizations in obtaining incident information
Provides briefings to and answers questions from supporting organizations

36. Agency Representative

37. Agency Representative
Individual assigned to an incident by an assisting or cooperating agency
Must have the authority to make decisions for their agency
Report to the Liaison Officer (if delegated) or Incident Commander

38. Assistant
Assistants are subordinates of Command Staff, particularly for the Public Information Officer and Safety Officer

39. General Staff

40. Operations Section

41. Operations Section
Usually one of the first organizations assigned to incident
Directs and coordinates all incident tactical operations
Operations Section Chief Facilitates the Operational Period Briefing for the Operations Section

42. Operations Section Elements
When expanding the Operations Section the following elements may be used:
Branches – Has functional, geographic or jurisdictional responsibility for major parts of the incident operations. The level between Section and units
Division – Has responsibility for operations within a defined geographic area
Group – Used to divide incident into functional areas of operation

43. Operations Section Elements
Unit – Has functional responsibility for a specific incident planning, logistics or finance/admin activity
Task Forces – Group of (mixed) resources with common communications
Strike Teams – Specified combinations of same kind and type of resources with common communications
Single Resources –Individual piece of equipment and its personnel, or a crew or team of individuals

44. Planning Section

45. Planning Section
Collects, evaluates and displays incident intelligence and information
Maintains Resource Status Info
Develops Situation Status Reports
Prepares Incident Action Plan
Generates plan for demobilization
Provides Documentation Services
Primary location for Technical Specialists

46. Incident Action Plan
To facilitate “Management by Objectives” each incident must have an Action Plan, that includes:
Incident Objectives
Activities to be completed
Time period for completion of Activities (Operational Period)
Can be written or verbal

47. Planning Section
Can be organized as follows:

48. Logistics Section

49. Logistics Section
Orders, obtains, maintains and accounts for personnel, equipment and supplies
Provide communication planning & resources
Sets up food services for responders
Arrange for and maintain incident facilities
Coordinate support transportation
Provide medical services for injured personnel
Tracks status of resources

50. Logistics Branch Structure

51. Logistics Section Units
Service Branch
Communications Unit – Prepares Communications plan, distribute and maintain equipment, establish adequate communications
Medical Unit – Develops medical plan, provide first aid for incident personnel, and plan for medical emergency
Food Unit – Supply food and potable water for all incident facilities and personnel

52. Logistics Section Units
Support Branch:
Supply Unit – Determine and acquire type and amount of supplies needed to support incident
Facilities Unit – Set up and maintain required facilities to support incident.
Responsible for facility security and maintenance
Ground Support Unit – Prepare Transportation plan and arrange for transportation of personnel, supplies, etc.

53. Finance/Admin Section

54. Finance/Admin Section
Monitor incident costs
Negotiate and monitor contracts
Timekeeping
Cost analysis
Compensation for injury or damage to property
Documentation for reimbursement

55. Finance/Admin Section

56. End