Lancaster County

1
Lancaster County

• NIMS ICS Update
• March 3, 2006

2
NIMS

• NIMS integrates existing best practices into a
  consistent, nationwide approach to domestic
  incident management.
• NIMS consists of six major components

3
NIMS Components

• Command and Management
• ICS
• The same ICS we have been using for years
• Multi-agency Coordination Systems
• Mutual Aid Agreements
• Public Information Systems
• Reverse 911

4
NIMS Components

• Preparedness
• Planning (County and Municipal EOP)
• Training (ICS Training)
• Exercises
• Personnel Qualification and Certification (Pro
  Board Certifications)
• Equipment Acquisition and Certification
• Mutual Aid (Municipal Level)
• Publications Management (Standardized forms and
  document development such as SOGs)

5
NIMS Components

• Resource Management
• Typing (Type 1 through 5)
• Type 1 is the most capable
• All apparatus is in the process of being typed
• Mobilize and Dispatch

6
NIMS Components

• Communications and Information Management
• Incident Management Communications
• Interoperable Communications (800 MHz Radio
  System)
• Information Management
• Processes, Procedures and Systems

7
NIMS Components

• Supporting Technologies
• New Radio System
• CAD System
• Incident Management System

8
NIMS Components

• Ongoing Management and Maintenance
• Ensure ongoing compliance and improvement

9
Lancaster County Implementation Plan

• Final Draft will be available soon
• Will be available for download on LEMA and LCWC
  web sites
• www.lema.co.lancaster.pa.us
• www.lcwc.co.lancaster.pa.us

10
Lancaster County Implementation Plan

• NIMS Working Group Members
• LEMA
• LCWC
• LCPSTC
• Lancaster County Police Chiefs Assoc.
• Lancaster County Fire Chiefs Assoc.
• Lancaster County EMS Council
• More to be added in the future.

11
Lancaster County Implementation Plan

• Concept of Implementation
• Four distinct phases of Adoption
• Phase I Initial Staff Training
• Awareness Level
• Operations Level
• Supervisory Level
• Command Level

12
Lancaster County Implementation Plan

• Phase II Identification of Plans and Procedures
• Identify the plans and procedures that will need
  to be reviewed and modified to be NIMS compliant.

13
Lancaster County Implementation Plan

• Phase III
• Modification of Existing Plans identified in
  Phase II
• Resource Management
• Resource Typing

14
Lancaster County Implementation Plan

• Phase IV Supporting NIMS Integration Center
  Standards
• Credentialing and certification of personnel

15
Incident Command System

• What is changing for Lancaster County
• Adopt and Use Standard Terminology
• ICS Training

16
Incident Command System

• Some ICS rules to follow
• Maintain Span of Control (3 to 7)
• Maintain Unity of Command
• Use Proper Terminology

17
Incident Command System

• Standard Terminology
• Sides of a Building
• Current Side 1, 2, 3, 4
• New Side Alpha, Bravo, Charlie, Delta
• Floors of a Building
• Current First Floor, Second Floor, etc.
• New First Floor, Second Floor, etc.
• Division 1, 2 is only used when a supervisor is
  assigned to the floor. Division 2 is the title
  or radio designator of the person in charge of
  the second floor.

18
Incident Command System

• Basements
• Basement 1, Basement 2, etc
• If a Division Supervisor is assigned, it could be
  Basement Division 1, or Sub Division 1.
• Exposures
• Exposures follow the sides of the building
• Exposure B, Exposure B1
• Exposure D, Exposure D1

B
D
D1
19
(No Transcript)
20
Incident Command System

• Standard Terminology (cont.)
• Command and General Staff Positions
• Command
• Incident Commander, Unified Command
• Officers Safety, PIO, Liaison
• General Staff
• Section Chief
• Branch Directors
• Group and Division Supervisors
• Team and Task Force Leaders

21
Incident Command System

• Standard Terminology (cont.)
• Division and Group Supervisors
• Divisions are Geographic Areas, i.e. Sides of a
  Building, Floors of a Building, Interior, Roof,
  Basement, etc.
• Groups are Functional Elements, i.e. Suppression,
  Ventilation, Water Supply, etc.
• Sectors do not exists in ICS

22
Incident Command System

• Standard Terminology (cont.)
• Use of Operations Section Chief
• Most current applications are incorrect...
• What we are actually doing is assigning a Group
  or Division Supervisor.
• Should only be used in complex or large
  incidents.
• Should not be used unless all tactical operations
  are turned over to the Operations Section Chief.
• Should be used to maintain span of control.

23
Incident Command System Training Levels
24
Incident Command System Training Levels
Incident Commander
Public Information Officer
Safety Officer
Liaison Officer
Operations Section Chief
Planning Section Chief
Finance/Administration Section Chief
Logistics Section Chief
Service Branch
Compensation/ Claims Unit
Resource Unit
Support Branch
Branches
Situation Unit
Supply Unit
Communications Unit
Procurement Unit
Division/Group Supervisors
Strike Team/ Task Force Leaders
Demobilization Unit
Facilities Unit
Medical Unit
Time Unit
Documentation Unit
Food Unit
Ground Support Unit
Single Resources Leaders
Cost Unit
Technical Specialists
Response Personnel
Recommended Training
25
Incident Command System

• Switchover Date to correct terminology is
• April 3, 2006

26
Regional Incident Support Team (IST) / Incident
Management Team (IMT)

• Required under Under Act 227 (2002) for all
  regions to implement.
• Team Leaders
• Greg Noll
• Chief Don Konkle (HFD)
• Deputy Chief Tim Sevison (HFD)
• Marty Nevil (PATF 1)
• Will not assume command.
• Strictly a Tool that can be requested by the
  Incident Commander for incidents that may
  overwhelm the local Incident Management Structure
  due to incident size, complexity, or duration.
• Focus is on support for Planning, Finance/Admin
  and Logistics.
• Designed to provide support for the initial and
  second operational periods.

27
NIMS / ICS Update

• Questions ???