1. National Incident Management System
IS-100 Incident Command System
IS-700 NIMS
Welcome to the NIMS workshop.
We are not going to “certify” you in NIMS, but we are going to give you the knowledge to go back to your agencies/jursdictions get on the web and take the IS100 and the IS700 at the point where you pass the two tests then you will be NIMS certified..
Admin Stuff: Restrooms, Breaks, Exits, etc.
Introductions

2. Where Are We Going? Conducting NIMS Workshops
Developing a NIMS Implementation Plan
NIMCAST
Waiting
We are conducting NIMS workshops throughout the state – this is currently our *** one.
The NIMS implementation plan has been writen at the state level it is now being passed on to the local level at which point you will need to take the template and develop a implementation plan for your agency/and or jurisdiction.
NIMCAST is an online assessment tool to determine were you (or your agency) is currently at where NIMS compliance is concerned.

3. NEMA
NEMA Website:

4. NEMA-NIMS Page

5. NIMS – FEMA Bruce Blatchford (deputyblath@yhaoo.com)
This is the FEMA NIMS web site. If you haven’t seen this you might want to go there. A great resource including frequently asked questions, NIMCAST, compliance and training issues.

6. NIMCAST

7. Overall Objectives Understanding of the NIMS
Ability to receive a certification for IS-700 and IS-100
Begin the process of being NIMS compliant
What we hope to cover by going over the IS100 and IS700. Again, we are not going to be able to “certify” you in NIMS but we are going to allow you the opportunity to become NIMS certified.

8. ICS-100 Objectives
Describe how ICS became the standard for emergency management.
Provide examples of how ICS is interdisciplinary and organizationally flexible.
Identify five major management functions.
Describe the principles of span of control.

9. ICS-100 Objectives (cont.)
Describe the purpose of unique position titles in ICS.
Determine the roles and responsibilities of the Incident Commander, Command Staff and General Staff.
Determine, when it is appropriate to expand and contract the ICS organization.
Identify the facilities used in ICS.

10. Types of Incidents Planned events Fire, both structural and wildfire
Hazardous materials incidents
Search and rescue missions
Oil spills
Natural disasters
Terrorist/WMD events

11. What Is ICS?
Standardized, on-scene, all-hazard incident management concept.
Allows its users to adopt an integrated organizational structure.
Has considerable internal flexibility.

12. What Is ICS?
A proven management system based on successful business practices.
The result of decades of lessons learned in organization and management of emergency incidents.

13. Weaknesses Addressed by ICS
Lack of accountability, including unclear chain of command and supervision.
Poor communication, including system and terminology problems.
Lack of an orderly, systematic planning process.

14. Weaknesses Addressed by ICS
No common, flexible, pre-designed management structure.
No pre-defined methods to integrate interagency requirements into the management structure and planning process.

15. What ICS Is Designed To Do
Meet the needs of incidents of any kind or size.
Allow personnel from a variety of agencies to mold rapidly into a common management structure.
Provide logistical and administrative support to operational staff.

16. What is ICS Designed to do?
Be cost effective by avoiding duplication of efforts.
ICS has been tested in more than 30 years of emergency and non-emergency applications, by all levels of government and in the private sector.

17. ICS Features ICS ICS Organization Incident Action Plan
Common Responsibilities
Span of Control
Incident Action Plan
Incident Facilities

18. Five Major Management Functions
Logistics Section
Finance/ Administration Section
Operations Section
Planning Section
Incident Command

19. ICS Span of Control
Supervisor
Resource 1
Resource 3
Resource 2

20. Maintaining Span of Control
Supervisor
Resource 1
Resource 3
Resource 2
Resource 4
Resource 5

21. ICS Position Titles Provide a common standard for all users.
Distinct titles allow for filling positions with the most qualified individuals.
Useful when requesting personnel.

22. ICS Organizational Components
Section
Division
Group
Branch
Task Force
Strike Team
Single Resource

23. Maintaining Span of Control
Divisions: Divide incident geographically, led by a Supervisor.
Groups: Describe functional areas of operation, led by a Supervisor.
Branches: Used when the number of Divisions or Groups exceeds the span of control and can be either geographical or functional, led by a Director.

24. Maintaining Span of Control
Task Forces: Mixed resources with common communications reporting to a Leader.
Strike Teams: A set number of resources of the same kind and type with common communications reporting to a Leader.
Single Resources: Individuals, a piece of equipment and its personnel complement, or a crew or team of individuals.

25. Finance/ Administration Section Public Information Officer
ICS Structure
Logistics Section
Finance/ Administration Section
Operations Section
Planning Section
Incident Command
Public Information Officer
Safety Officer
Liaison Officer
Command Staff:
The Command Staff provide Information, Safety, and Liaison services for the entire organization.
General Staff:
The General Staff are assigned functional authority for Operations, Planning, Logistics, and Finance/Administration.

26. Incident Commander’s Role
Has overall responsibility for managing the incident.
Must be fully briefed, and should have a written delegation of authority.
Personnel assigned by the Incident
Commander have the delegated authority of their assigned positions.
Only position that is always filled.

27. Incident Commander Responsibilities
Overall command and control.
Ensures incident responder safety.
Protects health and safety of the general public and the environment.
Provides information to internal and external stakeholders.
Maintains liaison with other agencies.

28. Expanding the Organization
Logistics Section
Finance/ Administration Section
Operations Section
Planning Section
Incident Command
Public Information Officer
Safety Officer
Liaison Officer
Command Staff:
The Command Staff provide Information, Safety, and Liaison services for the entire organization.
General Staff:
The General Staff are assigned functional authority for Operations, Planning, Logistics, and Finance/Administration.

29. Command Staff Public Information Officer Safety Officer
Liaison Officer

30. PIO Responsibilities
Advise the Incident Commander on information dissemination and media relations.
Serve as the primary contact for anyone who wants information (internal & external).
Obtain information from the Planning Section, community, media and others.
Coordinate with other public information staff.

31. Safety Officer Responsibilities
Ensures responder safety.
Advises Incident Command on safety issues.
Minimizes employee risk.

32. Liaison Officer Responsibilities
Gathers information about support agencies.
Coordinates for agencies not in command structure.
Provides briefings and answers questions.

33. Understanding the General Staff
Logistics Section
Finance/ Administration Section
Operations Section
Planning Section
Incident Command

34. ICS Section Chiefs and Deputies
Team Leader
Individual Resource
Deputy
Section Chief

35. Operations Section Chief Role
Develop and manage the Operations Section.
Develops and implements strategies and tactics.
Work very closely with other members of the Command and General Staff to coordinate tactical activities.

36. Operations Section Expanding
Mass Care Specialist
Fire Strike
Team Leader
Transportation Specialist
Engineering Specialist
Operations
Section Chief

37. Planning Section Chief Roles
Gathers, analyzes, and disseminates intelligence and information.
Manages the planning process.
Compiles and develops the Incident Action Plan.
Manages the activities of Technical Specialists.
Works closely with the Incident Commander and General Staff.

38. Incident Action Plan Elements
What, Where, When, Who, How?
What do we want to do?
Where do we stage?
When are we going to do it?
Who is responsible for doing it?
How do we communicate with each other?
What is the procedure if someone is injured?

39. Logistics Section Chief: Role
Provides resources and services to support the incident.
Develops portions of the IAP.
Contracts for goods and services.

40. Finance/Administration Section Chief: Role
Negotiate contracts
Time keeping for personnel and equipment
Documenting and processing claims
Tracking costs

41. Finance/ Administration Section Public Information Officer
ICS Structure
Logistics Section
Finance/ Administration Section
Operations Section
Planning Section
Incident Command
Public Information Officer
Safety Officer
Liaison Officer
Command Staff:
The Command Staff provide Information, Safety, and Liaison services for the entire organization.
General Staff:
The General Staff are assigned functional authority for Operations, Planning, Logistics, and Finance/Administration.

42. Communications within ICS
The ability to communicate with ICS is critical.
Use standard, common terminology.
Use standard ICS position titles and facility names.
Develop a communications plan and protocols specific to the incident.
Determine flow path for communications.

43. Communications Discipline
Observe strict radio/telephone procedures.
Use plain English in all communications.
Limit radio and telephone traffic to essential information only.
Follow procedures for secure communications as required.

44. Incident Facilities
Incident Command Post (ICP): Where the Incident Commander oversees the incident.
Staging Areas: Where resources are kept while waiting to be assigned.
Base: Where primary logistics functions are coordinated and administered.
Camps: Where resources may be kept.
Helibase/Helispot: The area from which helicopter operations are conducted.

45. Check-In at the Incident
Ensure personnel accountability
Track resources
Prepare personnel for assignments and reassignments
Locate personnel in case of an emergency
Establish personnel time records and payroll
Plan for releasing personnel
Organize the demobilization process

46. Check In List (Example)
From:
ICS 209-OS
Time of Report
3. Spill Status (Estimated, in Barrels) [Ops & EUL/SSC]

47. Initial Incident Briefing
Briefings received and given should include:
Situation assessment
Specific job responsibilities
Coworkers
Work area
Eating and sleeping arrangements
Instructions for obtaining additional supplies, services, and personnel
Operational periods/work shifts
Required safety procedures and PPE

48. Incident Briefing Examples

49. Incident Recordkeeping
Print or type all entries
Enter dates by month/day/year format
Enter date and time on all forms and records. Use local time.
Fill in all blanks. Use N/A as appropriate.
Use military 24-hour time.
Section Chiefs and above should assign a log keeper (scribe).

50. Incident Recordkeeping Example

51. Incident Demobilization
Complete work assignments
Brief replacements, subordinates, and supervisor
Follow check-out procedures

52. Incident Demobilization
Provide follow-up contact information.
Return incident-issued equipment.
Complete post-incident reports, critiques, evaluations, and medical follow-up.
Resolve payment and/or payroll issues.

53. Objective Review ICS is the standard for emergency management.
ICS is interdisciplinary and organizationally flexible.
Identified five major management functions.
Identified the principles of span of control.
Position titles in ICS.

54. Objective Review (cont.)
Roles and responsibilities of the Incident Commander, Command Staff and General Staff.
Ability to expand and contract the ICS organization.
Identify the facilities used in ICS.

55. Questions

56. The National Incident Management System

57. Objectives IS-700 Identify how ICS is a component of NIMS.
Describe the functions and purpose of Multiagency Coordination Systems.
Identify resource management and the coordination and oversight of resources.
Explain the area command and unified command as it relates to NIMS.

58. What is NIMS?
A comprehensive, national approach to incident management
Applicable at all jurisdictional levels and across disciplines

59. NIMS: What It Is / What It’s Not
NIMS is…
Core set of:
Doctrine
Concepts
Principles
Terminology
Organizational processes
Applicable to all hazards
NIMS is not…
An operational incident management plan
A resource allocation plan
A terrorism / WMD-specific plan
Designed to address international events
NIMS
NIMS provides overall conceptual framework for incident management.
NRP
NRP an operational plan spelling out how efforts and resources of participants are integrated into a cohesive response operation.
Forms the basis of how the federal government interfaces with state, local, tribal governments and the private sector.
Includes planning assumptions, roles and responsibilities, concept of operations and preparedness guidelines.
Details missions, policies, structures, responsibilities of federal agencies responding to Incidents of National Significance.
Outlines functions of each Emergency Response Function coordinators, primary agencies and support agencies.

60. NIMS – HSPD-5

61. NIMS Compliance Your jurisdiction must adopt NIMS: ICS by Oct 1, 2004
Other aspects by a later date (to be determined)

62. Why Do We Need NIMS? Lessons learned have shown the need for:
A coordinated response
Standardization
Interoperability

63. NIMS Concepts and Principles
NIMS is:
Flexible to enable all responding organizations to work together.
Standardized to improve overall response and interoperability.

64. NIMS Standard Structures
Incident Command System (ICS)
Multi-agency Coordination Systems
Public Information Systems

65. Preparedness Planning, training, and exercises
Personnel qualification and certification
Equipment acquisition and certification
Publication management
Mutual Aid/Emergency Management Assistance Compacts (EMAC)

66. Resource Management Includes standardized: Descriptions Inventories
Mobilization
Dispatch
Tracking
Recovery

67. Communications & Information Management
NIMS identifies requirements for:
Communications
Information management
Information sharing

68. Supporting Technologies
NIMS provides systems to standardize:
Voice and data communications
Information management
Data displays

69. ICS Proven on-scene, all-hazard concept
Interdisciplinary and organizationally flexible
Appropriate for all types of incidents

70. ICS Features Common terminology Organizational resources
Manageable span of control
Organizational facilities
Use of position titles
Reliance on an Incident Action Plan
Integrated communications
Accountability

71. Common Terminology
ICS requires:
Common terminology
“Clear” text

72. Organizational Resources
Includes:
Personnel
Facilities
Equipment and supplies
Requires “typing” by capability

73. Span of Control From 3 to 7 reporting elements per supervisor
5 is optimum

74. Incident Facilities Established as required by the incident
An ICP is always established

75. Incident Command Organizational Level Incident Command Command Staff
General Staff (Section)
Branch
Division/Group
Unit
Strike Team/Task Force
Title
Incident Commander
Officer
Chief
Director
Supervisor
Leader

76. Incident Action Plans Communicate incident objectives
Are based on operational periods
Are disseminated throughout the incident organization

77. Integrated Communications
Hardware systems
Planning for use of all frequencies and resources
Procedures for transferring information internally and externally

78. Accountability Orderly chain of command Check-in for all responders
Assignment of only one supervisor per individual (unity of command)

79. (Representatives From Local Jurisdictions) Finance/ Administration
Unified Command
Unified Command
(Representatives From Local Jurisdictions)
Finance/ Administration
Logistics
Planning
Operations

80. How Does Unified Command Work?
Agencies work together to:
Analyze intelligence
Establish objectives and strategies
Unified Command does not change other features of ICS.

81. Area Command
Area Command
ICP 1
ICP 2
ICP 3

82. What Does Area Command Do?
Sets overall strategy and priorities
Allocates resources
Ensures proper management
Ensures objectives are met
Ensure strategies are followed

83. Finance/ Administration
Area Command
Area Command
Planning
Logistics
Finance/ Administration

84. Multiagency Coordination Systems
A combination of resources
Integrated into a common framework
Used to coordinate and support incident management activities

85. Multiagency Coordination Systems
Support incident management policies and priorities
Facilitate logistics support and resource tracking
Make resource allocation decisions based on incident management priorities
Coordinate incident-related information
Coordinate interagency and intergovernmental issues regarding incident management policies, priorities, and strategies

86. Multiagency Coordination System Elements
EOC
Other entities

87. Information Management
EOC Organization
EOC Manager
Coordination
Communications
Resource Management
Information Management

88. EOC Organization Coordination Resources Priorities
Strategic coordination
Multiagency Coordination Entity
Incident Command/ Unified Command 1
Incident Command/ Unified Command 2
Situation status
Resource needs
Other Multiagency Coordination Entities

89. Public Information for Domestic Incidents
Advises the IC
Establishes and operates within the JIS
Ensures that decision makers and the public are informed

90. The JIC Physical location where public information staff collocate
Provides the structure for coordinating and disseminating critical information

91. JICs State JIC Local JIC 1 Local JIC 2 Agency 1 PIO Agency 2 PIO
IC/UC/Area Command
PIO
(at incident JIC)

92. JIC Characteristics
Includes representatives of all players in the response
Has procedures and protocols for communicating and coordinating with other JICs

93. Joint Information Center
JICs
Joint Information Center
Research Team
Media Team
Logistics Team
Press Secretary
(jurisdictional)
Liaison
(as required)

94. What Is Preparedness?
Actions to establish and sustain prescribed levels of capability
Ensures mission integration and interoperability

95. Responsibilities of Preparedness Organizations
Establishing/coordinating plans and protocols
Integrating/coordinating activities
Establishing guidelines and protocols to promote interoperability
Adopting guidelines for resource management
Establishing response priorities
Establishing/maintaining multiagency coordination mechanisms

96. Preparedness Planning
Plans describe how resources will be used.
Plans describe mechanisms for:
Setting priorities
Integrating entities/functions
Establishing relationships
Ensuring that systems support all incident management activities

97. Types of Plans Emergency Operations Plans (SEOP/LEOP) Procedures
Preparedness Plans
Corrective Action and Mitigation Plans
Recovery Plans

98. Training and Exercises
The NIMS Integration Center will:
Facilitate development and dissemination of national standards, guidelines, and protocols.
Facilitate use of modeling/simulation.
Define general training requirements and approved courses.
Review/approve discipline-specific training requirements.

99. Personnel Qualifications and Certification
Development of standards, including:
Training
Experience
Credentialing
Currency requirements
Physical and medical fitness

100. Equipment Certifications
Facilitate development of national equipment standards, guidelines, and protocols
Review and approve equipment meeting national standards

101. Mutual Aid and EMACs
Jurisdictions at all levels are encouraged to enter into agreements with:
Other jurisdictions
Private-sector and NGOs(Non Governmental Organizations)
Private organizations

102. Publication Management
The development of naming and numbering conventions
Review and certification of publications
Methods for publications control
Identification of sources and suppliers for publications and related services
Management of publication distribution
FEMA is currently working on developing a standard on training publiciations. The old FEMA courses are no longer seen as substanal they are revamping the training.

103. What Is Resource Management?
Four tasks:
Establishing systems
Activating the systems
Dispatching resources
Deactivating resources
This is more at the state level. The ESF’s will be responsisble for defining the types of resources at the state level, the locals then will ask for resources and will be given them through the state.

104. Resource Management Concepts
Standardize identification, allocation, and tracking
Classify by kind and type
Implement credentialing system
Incorporate resources from private sector and NGOs (Non Governmental Organizations)

105. Resource Management Principles
Advance planning
Resource identification and ordering
Resource categorization
Use of agreements
Effective management

106. Lesson Overview
Advantages of common communication and information management standards
How NIMS will influence technology/technological systems

107. NIMS Intent Broad applicability
Improve coordination and cooperation among all response organizations

108. NIMS Components Command and management Preparedness
Resource management
Communications and information management
Supporting technologies
Ongoing management and maintenance

109. NIMS Concepts and Principles
Flexible framework that:
Facilitates working together . . .
At any type of incident . . .
Regardless of size, location, or complexity
Flexible structures
Requirements for processes, procedures, and systems

110. Command and Management
Incident Command System (ICS)
Multi-agency Coordination Systems

111. ICS Features Common terminology Organizational resources
Manageable span of control
Organizational facilities
Use of position titles
Reliance on an Incident Action Plan
Integrated communications
Accountability

112. Unified Command More than one responding agency within a jurisdiction
Incidents cross jurisdictions

113. Area Command Multiple incidents within a jurisdiction Large incidents
that cross jurisdictions

114. Communications and Information
Facilitate a common operating picture for:
Incident management
Information management
Interoperability standards

115. Multiagency Coordination Systems
Support incident management
Facilitate logistic support and resource tracking
Allocate resources
Coordinate information
Coordinate issue resolution

116. Multiagency Coordination Systems
EOC
Multi-agency Coordination Entities

117. Public Information Provides information to:
Command
The Public
Ensures information provided is:
Accurate
Timely
Coordinated

118. Preparedness
Actions involved to establish/maintain prescribed capability
NIMS focuses on guidelines, protocols, and standards

119. Training and Exercises
Facilitate national standards, guidelines, and protection
Facilitate use of modeling/simulation
Define general training requirements
Review/approve discipline specific requirements/courses

120. Types of Plans EOP Procedures Preparedness Plans
Corrective Action and Mitigation
Recovery

121. Personnel Qualifications
Preparedness based on standards for qualification/certification
Includes minimum:
Knowledge
Skills
Experience

122. Equipment Certification
Ensure performance to standards and interoperability
Facilitate development of national standards and protocols
Review and approve equipment meeting standards

123. Resource Management Establish systems for: Activating systems
Describing
Inventorying
Requesting
Tracking
Activating systems
Dispatching resources
Deactivating/recalling resources

124. Managing Resources Identifying and typing resources
Certifying and credentialing personnel
Inventorying resources
Identifying resource requirements
Ordering and acquiring resources
Tracking and reporting resources
Mobilizing resources
Recovering resources
Reimbursement

125. NIMS Focus on Supporting Technology
Interoperability and compatibility
Technology support
Technology standards
Broad-based requirements
Strategic planning and R&D

126. Managing Communications and Information
Incident management communications
Information management
Interoperability standards

127. NIMS Contact Gil Jamieson, Acting Director Web Page: www.fema.gov/nims
NIMS Training:
Main Number:
Mailing Address: NIMS Integration Center, 500 C Street SW, Suite 707, Washington, DC 20472
Nema Website:

128. Questions