INTRODUCTION

On February 28, 2003, the President issued Homeland Security Presidential Directive (HSPD)-5, Managem= ent of Domestic Incidents. The two basic outcome components in this directive a= re the National Incident Management System (NIMS) and the National Response Pl= an (NRP).

NIMS has been issued with= the caveat that the portions of it that have been most completely prepared are Chapters II Command and Management and III Preparedness. (Cha= pter I is Introduction and Overview). This Appendix will confine itself of these three chapters in this revision of the C/WLEPC ERP.

The basis for having a NI= MS is the desire of the Federal government to have, “…a consistent nationwide template to enable Federal, State, local, and tribal governments= and private-sector and nongovernmental organizations to work together effective= ly and efficiently to prepare for, prevent, respond to, and recover from domes= tic incidents, regardless of cause, size, or complexity, including acts of catastrophic terrorism.”

The NIMS is built on the foundation provided by existing incident management and emergency response systems at the various levels of government. “It also sets in motion = the mechanisms necessary to leverage new technologies and adopt new approaches = that will enable continuous refinement of the NIMS over time.”

“The NIMS enables effective, efficient, and collaborative incident management at all levels of government through a core set of doctrine, concepts, principles, procedures, terminology, technologies, organizational processes and standards requireme= nts applicable to a broad community of NIMS users.

HSPD-5 requires Federal department and agencies to make adoption of the NIMS by State and local jurisdictions a condition for Federal preparedness assistance (through gran= ts, contracts, and other activities, beginning in FY 2006 (October 1, 2006).

A key point that is made = in the NIMS is that it, “is based upon an appropriate balance of flexibility= and standardization.” In other words the emergency incident’s complexity level will determine the level of actual implementation of the standards put forth in the NIMS. The present knowledge of the Incident Comm= and System that has been used by members of the C/WLEPC for some time should al= low a smooth transition to the concepts put forth in the NIMS. Depending on the complexity and length of the emergency incident, the IC may choose to combi= ne organizational positions addressed in the NIMS and/or assume them himself, = as long as the spirit of the NIMS is maintained and results will be same as required by the NIMS. The individual IC is the best position at an emergency incident to make such decisions, keeping in mind the NIMS

INTRODUCTION (CONTINUED)<= /p>

guidelines and factors su= ch as the complexity of the emergency incident, the availability of qualified sta= ff personnel, the projected length of the emergency incident, etc.

I. COMMAND AND MANAGEMENT=

A. Incident Command Syste= m

<= /span>1. = Concepts and Principles

&n= bsp; a. = Most Incidents are Managed Locally

While a= ll past incidents in the C/WLEPD have been managed locally, given the hazards (emergencies) that can impact the C/WLEPD, including Terrorism, there is a = very good likelihood that at sometime in the future an incident that starts out locally will become multi-jurisdictional, and/or involve one or more additi= onal hazards (emergencies) and/or will last for a period beyond the initial capabilities of the of the emergency preparedness organizations in the C/WL= EPD. When this does happen, and additional jurisdictions become involved and/or = State and Federal agencies become involved, having all agencies and jurisdictions using the same ICS will eliminate problems of Command and Management that otherwise would in all probability arise.

&n= bsp;

b. &nb= sp; The NIMS Requires that Command and Management functions be performed in accorda= nce with a standard set of ICS Organizations, Doctrine and Procedures. The ICS organization, doctrine and procedures are basically additions to the ICS sy= stem that the C/WLEPD jurisdictions have been using since the inception of the C= /WLPEC. Therefore, to adept to the NIMS ICS should be easily done with a minimal am= ount of additional training and exercises (drills).

c. &nbs= p; The ICS is Modular and Scalable

= ICS is designed to the following operating characteristics:

= &nb= sp; (1). suita= ble for all varieties of organization;

= &nb= sp; (2). appli= cable and acceptable to users throughout the country;

= &nb= sp; (3). readi= ly adaptable to new technology;

= &nb= sp; (4). adapt= able to any emergency incident; and

(5). <= /span>a scalable organizational structure based on the size and

= &nb= sp; = &nb= sp; complexity of the emergency incident.

<= /span>

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

<= /span>1. = Concepts and Principles (Continued)

&n= bsp; d. = The ICS has Interactive Management Components.

These s= et the stage for effective and efficient incident management and emergency respons= e.

e. &nbs= p; The ICS establishes common terminology, standards, and procedures that enable diverse organizations to work together effectively.

(1). <= /span>Standard set of pre-designated organizational elements and =

func= tions.

(2). <= /span>Common names for resources used to support incident

oper= ations.

(3). = Common “typing” for resources to reflect specific capabilities.

(4). <= /span>Common identifiers for facilities and operational locations

used= to support incident operations.

&n= bsp; f. &= nbsp; The ICS Incorporates Measurable Objectives.

&n= bsp; = ; &n= bsp; (1) Measurable objectives ensure fulfillment of incident

= &nb= sp; = = management goals.

(2). = Objective-setting should start at the top and be communicated throughout the entire Incident Command organization.

&n= bsp; g. = The Implementation of ICS Should Have the Least Possible Disruption on

&n= bsp; = ; = Existing Systems and Processes

(1). = To facilitate its acceptance nationally within the Emergency Preparedness community.

&n= bsp; = ; &n= bsp; (2). To in= sure continuity in the transition process.

&n= bsp; h. = The ICS Should be User Friendly and Be Applicable Across a Wide

&n= bsp; = ; = Spectrum of Emergency Response and Incident Management Disciplines.

This wi= ll allow the communications, coordination, and integration that is critical to an effective and efficient NIMS.

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

<= /span>2. = ICS Management Characteristics

&n= bsp; a. = Common Terminology

&n= bsp; = ; &n= bsp; (1). Organ= izational Functions

(a). &n= bsp; Major organization elements and subordinate units with Incident Management responsibilities are named and defined.

(b). &n= bsp; Terminology for the organizational elements involved is standard and consistent.

&n= bsp; = ; &n= bsp; (2)= . Resou= rce Descriptions

Personn= el, facilities, major equipment, and major supplies used to support Incident Management activities.

(a). Are g= iven common names

(b). Are “typed” with respect to their capabilities

&n= bsp; = ; &n= bsp; (3)= . Incid= ent Facilities

Common terminology is used to designate the relevant facilities in the vicinity of= the Emergency Incident area.

&n= bsp;

&n= bsp; b. = Modular Organizations

The Inc= ident Command organizational structure develops in a top-down manner that is based upon:

&= nbsp; (1). Size = of the Emergency Incident,

&= nbsp; (2). Compl= exity of the Emergency Incident,

&= nbsp; (3). The specifics of the hazard (emergency) environment, and

(4). &n= bsp; Length of time estimated to resolve and recover from the emergency incident.

&n= bsp; c. = Management by Objectives

&n= bsp; = ; &n= bsp; (1)= . Estab= lish overarching objectives.

(2). &n= bsp; Develop and issue assignment, plans, procedures, and protocols.

(3). &n= bsp; Establish specific, measurable, and clear objectives for the various emergency incide= nt management function activities, and direct efforts to attain the resolution= and recovery from the emergency incident.

(4) &nb= sp; Document results in order to measure performance and facilitate corrective actions f= or future emergency incidents of similar nature.

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

<= /span>2. = ICS Management Characteristics (Continued)

&n= bsp; d. = Reliance on the Incident Action Plan (IAP)

The IAP provides an effective means of stating overall incident objectives for both operational and support activities.

&n= bsp; e. = Manageable Span of Control

&n= bsp; = ; &n= bsp; (1)= . Key to effective and efficient incident management

(2). &n= bsp; Supervisory responsibility should range from 3 to 7 persons, depending on:

= &nb= sp; (a). Type = of Incident

= &nb= sp; (b). Natur= e of Task

= &nb= sp; (c). Hazar= ds and Safety Factors

= &nb= sp; (d). Distance be= tween Personnel and Resources

&n= bsp; f. &= nbsp; Pre-designated Incident Locations and Facilities

The IC = will decide the location of the ICP and operational and support activities. (Resource Reception Center, Staging Area, Triage and Treatment, Patient Transportation, Evacuation Reception, Shelter-In-Place, Decontamination, Et= c.)

&n= bsp; g. = Comprehensive Resources Management

&n= bsp; = ; &n= bsp; (1)= . Inclu= des:

&n= bsp; = ; &n= bsp; = ; &n= bsp; (a). Categ= orizing

&n= bsp; = ; &n= bsp; = ; &n= bsp; (b). Order= ing

&n= bsp; = ; &n= bsp; = ; &n= bsp; (c). Dispa= tching

&n= bsp; = ; &n= bsp; = ; &n= bsp; (d). Tracking

&n= bsp; = ; &n= bsp; = ; &n= bsp; (e). Recov= ering

&n= bsp; = ; &n= bsp; (2)= . Resou= rces include:

&n= bsp; = ; &n= bsp; = ; &n= bsp; (a). Perso= nnel

&n= bsp; = ; &n= bsp; = ; &n= bsp; (b). Teams=

&n= bsp; = ; &n= bsp; = ; &n= bsp; (c). Equip= ment

&n= bsp; = ; &n= bsp; = ; &n= bsp; (d). Supplies

&n= bsp; = ; &n= bsp; = ; &n= bsp; (e). Facil= ities

&n= bsp;

&n= bsp; h. = Integrated Communication

&n= bsp; = ; &n= bsp; (1)= . Common Communications Plan for Voice and Data

&n= bsp; = ; &n= bsp; = ; &n= bsp; (a). Equip= ment

&n= bsp; = ; &n= bsp; = ; &n= bsp; (b). Syste= ms

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

<= /span>2. = ICS Management Characteristics (Continued)

&= nbsp; h. = Integrated Communication (Continued)

(1). &n= bsp; Common Communications Plan for Voice and Data (Continued)

&n= bsp; = ; &n= bsp; = ; &n= bsp; (c). Proto= cols

&n= bsp; = ; &n= bsp; (2)= . Inter= operable Processes and Architecture

&n= bsp; i. &= nbsp; Establishment and Transfer of Command

(1). &n= bsp; Initial designation of IC is by jurisdiction or agency with primary authority over incident

(2). &n= bsp; Upon any command transfer, a concise, but comprehensive briefing must take place=

<= /span> &= nbsp; j. &= nbsp; Chain of Command and Unity of Command

(1). &n= bsp; Chain of Command is the orderly line of authority within the ranks of the incident management organization.

(2). &n= bsp; Unity of Command means each person in the incident management organization has one immediate supervisor only.

&n= bsp; k. = Unified Command

&n= bsp; = ; &n= bsp; (1)= . Utili= zed when the emergency incident involves:

&n= bsp; = ; &n= bsp; = ; (a). Multi= ple local jurisdictions

(b). &n= bsp; A single local jurisdiction with State or Federal agency involvement

(c). &n= bsp; Multiple local jurisdictions with multi-state and/or federal agencies

(2). &n= bsp; The purpose is to allow local jurisdiction and/or state and federal agencies wi= th different authorities and responsibilities to work together effectively wit= hout affecting individual jurisdiction and/or State and Federal agencies authori= ty, responsibility, or accountability.

&n= bsp;

&n= bsp; l. &= nbsp; Accountability

&n= bsp; = ; &n= bsp; (1). Check-In for all resources p= rior to utilization

(2). Incid= ent Action Plan serves as the template for incident management direction and coordination

(3). Unity of Command<= /span>

(4). Span of Control

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

<= /span>2. = ICS Management Characteristics (Continued)

l. &= nbsp; Accountability (Continued)

(5). Resou= rce Tracking involves the recording and reporting of every resource status chan= ge as it occurs

m. Deployment of resources will take place based upon incident management decisions only.=

&nbs= p;

n. = Information and Intelligence Management involves an incident management process for the gathering, sharing, and managing of incident related information and intelligence.

&nbs= p;

&nbs= p; 3. = ICS Organization and Operations

&nbs= p; &= nbsp; a. = Command of an Incident is held by the Incident Commander

&nbs= p; &= nbsp;

&nbs= p; &= nbsp; b. = The Incident Commander

&nbs= p; &= nbsp; &nbs= p; (1) The Command Options

&nbs= p; &= nbsp; &nbs= p; &= nbsp; (a). Single Command IC

&nbs= p; &= nbsp; &nbs= p; &= nbsp; &nbs= p; (i). Normal single local jurisdiction

(ii). By agreement of all jurisdictions and/or agencies when the incident involves multiple jurisdictions and one or more State and/or Federal agencies.<= /o:p>

&nbs= p; &= nbsp; &nbs= p; &= nbsp; (b). Unifi= ed Command

All involved local jurisdictions and State and/or Federal agencies:

&n= bsp; = ; &n= bsp; = ; (i). Participate in the UC Structure

(ii). &= nbsp; Contribute to the process of determining overall incident strategies

(iii). = Select incident objectives

(iv). = Ensure that joint planning for tactical activities is accomplished in accordance w= ith approved incident objectives

(v). &n= bsp; Ensure the integration of tactical operations

(vi). = Approve, commit, and make optimum use of all assigned resources

Supporting NGOs are represented in the above concept by

the Liaison Officer.

The above concept calls for a very high degree of

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

3. ICS Organization= and Operations (Continued)

(1) The Command Options (Continued)

= (= b). Unifi= ed Command (Continued)

cooperation, coordination, and objectivity, since in essence

the role of the IC is filled by a collaborative.

If circumstances permit, it is suggested that a single IC be

agreed upon, so as to promote greater unity of effort and

efficiency.

&n= bsp; c. = Command Staff (All report to the IC)

&n= bsp; = ; = (1). Public Information Officer

&n= bsp; = ; &n= bsp; (a)= . Inter= faces with the various publics

&n= bsp; = ; &n= bsp; (b)= . Inter= faces with the various media

(c). &n= bsp; Interfaces with other units of the Incident Command organization

(d). <= /span>Develops accurate and complete information about the Incident(s) for both internal a= nd external consumption

(e). = Only one PIO per incident(s), with assistants as justified by the particular incident(s)

(f). &n= bsp; All news releases require the IC’s approval

&n= bsp; = ; = (2). Safety Officer

&n= bsp; = ; &n= bsp; (a). Monit= ors incident operations

(b). &n= bsp; Advises the IC on all matters of operational safety (including the health of the incident personnel

(c). &n= bsp; Only one SO per incident(s), with assistants as justified by the particular incident(s)

(d). <= /span>Coordinates closely with Operations Chief and Planning Chief of the incident General St= aff

&n= bsp; = ; = (3). Liais= on Officer

&n= bsp; = ; &n= bsp; Is point of contact with the IC for representatives of:

&n= bsp; = ; &n= bsp; (a)= . Other governmental agencies

&n= bsp; = ; &n= bsp; (b)= . NGOs<= /p>

&n= bsp; = ; &n= bsp; (c)= . Priva= te entities

&n= bsp; = ; &n= bsp; (d)= . Assisting agencies and organizations

&n= bsp; = ; &n= bsp; (e)= . Coope= rating agencies and organizations

(4). &n= bsp; Assistant for command staff may be appointed in keeping with the scope and complexity= of the incident(s).

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

3. ICS Organization= and Operations (Continued)

c. = Command Staff (All report to the IC) (Continued)

(5). Addit= ional command staff may be appointed, in keeping with the scope and complexity of= the incident(s).

&n= bsp; d. = The General Staff

Represe= nts and is responsible for the functional aspects of the Incident Command structure, including:

&= nbsp; (1). Opera= tions Chief

Directs= the Operations Section, which is responsible for all activities focused on:

(a). Reduc= tion of the immediate hazard

(b). Saving lives and property

(c). Estab= lishing situation control

(d). Restoring n= ormal operations

(2). &n= bsp; Depending on the scope and complexity of the incidents, the Operations Chief may have three levels of organization below him. They are:

= (a). Branc= hes

= (b). Divis= ions and Groups

(c). &n= bsp; Special Resources, which are a combination of personnel and equipment required to enable incident management operations.

(i). &n= bsp; Single Resource, which is an individual and the related equipment (with operators = if need be).

(ii). &= nbsp; Task Force, which is any combination of resources assembled in support of a spec= ific mission or operational need.

(iii). Strike Team, which is a set number of resources of the same kind and type that hav= e an established minimum number of personnel.

(3). &nb= sp; Planning Chief

&n= bsp; = ; &n= bsp; Dir= ects the Planning Section, which is responsible for:

(a). &n= bsp; Collection, evaluation, and dissemination of incident situation information and intelligence to the IC or UC and incident management personnel

(b). &nb= sp; Preparation of Status Reports

(c). &nb= sp; Display of situation information

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

3. ICS Organization= and Operations (Continued)

= <= /span>(3). Plann= ing Chief (Continued)

(d). Maintenance of status of resources assig= ned to the incident

(e). Development and documentation of t= he IAP, based upon guidance from the IC or UC

(i). &nb= sp; Incident Objectives

(ii). &n= bsp; Organization Chart or List

(iii) &n= bsp; Assignment List

(iv). <= /span>Communications Plan

(v). &nb= sp; Logistics Plan

(vi). <= /span>Responder Medical Plan

(vii). Incident Plan

(viii). Heal= th and Safety Plan

(ix). <= /span>Additional Scenario Dependent Components

&n= bsp; = ; = (4) The Planning Chief supervises Unit Heads for:

&n= bsp; = ; &n= bsp; (a)= . Resou= rces

&n= bsp; = ; &n= bsp; (b)= . Situa= tion

&n= bsp; = ; &n= bsp; (c)= . Demob= ilization

(d). Documentation

&n= bsp; = ; = (5). Logis= tics Chief

Directs= the Logistics Section, which is responsible for all support requirements needed= to facilitate effective and efficient incident management, including:

(a). &nb= sp; Ordering resources from off-incident sites

(b). &nb= sp; Facilities

(c). &nb= sp; Transportation

(d). Supplies

(e). &nb= sp; Materials

(f). &nb= sp; Equipment repair and maintenance

(g). &nb= sp; Food services

(h). &nb= sp; Communications and information technology support

(i). &nb= sp; Emergency responder medical services

(6). &nb= sp; The Logistics Chief directs the following Units:

&n= bsp; = ; &n= bsp; (a)= . Suppl= y

&n= bsp; = ; &n= bsp; (b)= . Food<= /p>

&n= bsp; = ; &n= bsp; (c)= . Ground Support

&n= bsp; = ; &n= bsp; (d)= . Communicati= ons

&n= bsp; = ; &n= bsp; (e)= . Facil= ities

(f). &nb= sp; Medical

<= /span>

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

3. ICS Organization= and Operations (Continued) &n= bsp; = ;

&n= bsp; = ; = (7). Finan= ce/Administration Chief

Directs= the Finance/Administration Section, which is responsible for units covering:

&= nbsp; (a). Compe= nsation/Claims

&= nbsp; (b). Procu= rement

&= nbsp; (c). Cost<= /p>

&= nbsp; (d). Time

&n= bsp; = ; = (8). Infor= mation and Intelligence Function

(a) &nb= sp; Normally handled as a unit of the Planning Section, but under various degrees of incident complexity and/or length, it may be justified as:

(i). Its own General Staff Section

(ii). Withi= n the Command Staff

(iii).<= span style=3D'mso-tab-count:1'> A Branch of= the Operations Section

(b). &nb= sp; Information includes:

(i). Gathering relevant data

(ii). Organ= izing relevant data

(iii).<= span style=3D'mso-tab-count:1'> Presenting relevant data to appropriate incident

personnel &nbs= p;

(c). &n= bsp; Intelligence includes gathering, analyzing, organizing, and disseminating information to appropriate incident personnel on:

(i). National security matters

(ii). Risk assessments

(iii).<= span style=3D'mso-tab-count:1'> Medical intelligence

(iv). Weather information

(v). Geosp= atial data

(vi). Structural designs

(vii).<= span style=3D'mso-tab-count:1'> Toxic contaminant levels

(viii).= Utilities and public wo= rk data

<= /span>4. = Area Command

&n= bsp; a. = An Area Command is an organization that is only established when either:

(1). = To oversee the management of multiple incidents that are each being handled by= a separate ICS organization, or

(2). &n= bsp; To oversee the management of a very large incident that involves multiple ICS organizations, such as incidents that:

= (a). Are n= ot site specific

I. COMMAND AND MANAGEMENT (CONTINUED)

A. Incident Command System (Continued)

4. Area Command (Continued)

&n= bsp; a. = (Continued)

&n= bsp; = ; = (2). (Cont= inued)

&n= bsp; = ; &n= bsp; (b)= . Are geographically disbursed

&n= bsp; = ; &n= bsp; (c)= . Evolv= e over longer periods of time

(d). <= /span>Require extraordinary cooperation among Federal, State, local, NOG, and relevant private sector entities

Examples of the above criteria (2a-d) are:

&= nbsp; (a). Biolo= gical terrorism

&= nbsp; (b). Chemi= cal terrorism

&= nbsp; (c). Nucle= ar terrorism and/or

&= nbsp; (d). Radiological terrorism

(3). &nb= sp; To oversee a number of incidents that are:

&= nbsp; (a). In th= e same area, and

&= nbsp; (b). Of th= e same type

Examples of the above criteria (3a-b) are:

&= nbsp; (a). Hazar= dous material spills

&= nbsp; (b). Oil S= pills

(c). &nb= sp; Major fires

b. &nbs= p; An Area Command becomes a Unified Area Command if the incidents are of a multi-jurisdictional nature

c. &nbs= p; Responsibilities of an Area Command

= (1). Set o= verall incident-related priorities

= (2). Alloc= ate critical resources according to priorities

(3). &nb= sp; Ensure that incident area is properly managed

(4). &n= bsp; Ensure that incident management objectives are met and no not conflict with each o= ther or with agency policy

(5). &n= bsp; Identify critical resource needs and report them to EOCs and/or multi-agency coordination entities

(6). &n= bsp; Ensure that short-term emergency recover is coordinated to assist in the transitio= n to full recovery operations

B. Multi-agency Coordinat= ion Systems

1. &nbs= p; Subject system is a combination of facilities, equipment, personnel, procedures, and communications, integrated into a common entity, with responsibility for

coordin= ating and supporting emergency incident management.

&n= bsp;

I. COMMAND AND MANAGEMENT (CONTINUED)

B. Multi-agency Coordinat= ion Systems (Continued)

<= /span>2. = The primary functions of the subject system are to:

&n= bsp; a. = Support incident management policies and priorities

&n= bsp; b. = Facilitate logistics support and resource tracking

&n= bsp; c. = Coordinate incident related information

d. &nbs= p; Coordinate interagency and intergovernmental issues regarding incident management policies, priorities, and strategies

Note: Direct tact= ical and operational responsibility for conducting incident management activities rests with the Incident Command.

3. &nbs= p; Subject system elements are:

= a. = Emergency Operating Center (“Room” by C/WLEPC definition)

(1). &n= bsp; The physical location at which the coordination of information and resources to support incident management activities normally takes place.

(2). &n= bsp; When organized by major functional discipline:

= (a). Fire protection

= (b). Law enforcement

= (c). Emerg= ency Medical Service

= (d). Etc., as lo= gical to an incident

(3). &n= bsp; When organized by jurisdiction:

= (a). Munic= ipality

= (b). Count= y

= (c). Multi= -County Region

= (d). Etc., as lo= gical to an incident

(4). &n= bsp; When organized by a combination or (2). and (3). above, which is most likely

(5). &n= bsp; Department Operations Centers (DOCs), if and when organized because of a justifiable n= eed:

(a). &n= bsp; Focus on internal agency incident management and response

(b). &n= bsp; Are linked to the responsible EOC

(c). &n= bsp; Are linked to the responsible Incident Command

&n= bsp;

I. COMMAND AND MANAGEMENT (CONTINUED)

B. Multi-agency Coordinat= ion Systems (Continued)

<= /span>3. = (Continued)

&n= bsp; b. = Multi-Agency Coordination Entities &nbs= p; &= nbsp; &nbs= p; &= nbsp;

(1). &n= bsp; Utilized when there is an extremely complex emergency incident(s) involving multi-jurisdictions, multi-agencies, and/or multi-disciplines

(2). &n= bsp; Are referred to by many titles

= (a). Crisis Action Team

= (b). Policy Committee

= (c). Incid= ent Management Group

= (d). Executive T= eam

= (e). EOC s= erving a dual purpose

= (f). Etc.<= /p>

(3). &n= bsp; Provide incident(s) appropriate services, including:

(a). &n= bsp; Ensuring that each agency involved in incident management activities is providing appropriate situational awareness and resource status information

(b). &n= bsp; Establishing priorities among incidents and/or Area Commands in concert with IC(s) or UC= (s) involved

(c). &n= bsp; Acquiring and allocating resources required by management personnel in concert with priorities established by the IC(s) or UC(s)

(d). <= /span>Anticipation and identifying future resource requirements

(e). &n= bsp; Coordinating and resolving policy issues arising from the incident(s)

(f). &n= bsp; Providing strategic coordination as required

(g). &n= bsp; Upon the termination of incident(s) management, ensuring that improvements in pl= ans, procedures, communications, staffing, and other capabilities necessary for improved incident management are acted upon, in coordination with appropria= te preparedness organizations.

C. Public Information Sys= tems

<= /span>1. = Public Information Principles

&n= bsp; a. = The PIO Supports the Incident Command

&n= bsp; = ; = (1). Repre= sents and advised the IC on all public relations matters

&n= bsp; = ; = (2). Handl= es:

&n= bsp; = ; &n= bsp; (a)= . All m= edia and public inquiries

&n= bsp; = ; &n= bsp; (b)= . Emerg= ency public information and warnings

I. COMMAND AND MANAGEMENT (CONTINUED)

C. Public Information Sys= tems (Continued)

&n= bsp; a. = (Continued)

&n= bsp; = ; = (2). (Cont= inued)

&n= bsp; = ; &n= bsp; (c)= . Rumor monitoring and response

&n= bsp; = ; &n= bsp; (d)= . Media monit= oring

(e). &n= bsp; Coordination of public relations near, as well as at, the emergency incident scene

(f). &n= bsp; Serving as the link with Joint Information Center, if such is established

&n= bsp; b. = Coordination and Integration of Public Information Functions

&n= bsp; = ; = (1). Across participation functional agencies

&n= bsp; = ; = (2). Across jurisdictions

&n= bsp; = ; = (3). With = NGOs and relevant private sector organizations

&n= bsp; = ; = (4). Use a JIC(s) in more complex emergency incidents

(a). &n= bsp; Must communicate and coordinate with each other PIO when a single JIC is establi= shed

(b). &n= bsp; Must communicate and coordinate with each other JIC(s) when two or more JICs are established

(c). &n= bsp; Public awareness functions must also be communicated and coordinated with all Information and Intelligence Units established within a complex incident response scenario where there are one or more JICs

c. &nbs= p; Organizations Participating In Incident Management Retain Their Independence

(1). &n= bsp; Where one or more JICs are established, the principle of coordinating and contributing to the effectiveness of the public information product is the = concept

(2). &n= bsp; Each PIO is still responsible for any public information matters that impact only his or her own incident scene

<= /span>2. = System Description and Components

&n= bsp; a. = Joint Information System

&n= bsp; = ; = (1). Inter= agency Coordination and Integration

&n= bsp; = ; = (2). Devel= oping and Delivering Coordinated Messages

&n= bsp; = ; = (3). Suppo= rt for Decision Makers

&n= bsp; = ; = (4). Flexi= bility, Modularity, and Adaptablility

I. COMMNAD AND MANAGEMENT (CONTINUED)

C. Public Information Sys= tems (Continued)

<= /span>2. = System Description and Components (Continued)

&n= bsp; b. = Joint Information Center

(1). &n= bsp; Includes Representatives of Each Jurisdiction, Agency, and Organization involved in Emergency Incident Management

(2). &n= bsp; A Single JIC Is Preferable, but Complex Emergency Incidents May Call for Mult= iple JICs (Large Area and/or Multiple Jurisdictions)

(3). &n= bsp; Logical Procedures and Protocols Are Necessary for Communicating with Other Appropr= iate Components of the ICS (and Other JICs, if Established

<= /span>3. = System Purpose and Organization

&n= bsp; a. = Joint Information System Purpose

(1). &n= bsp; Provides an organized, integrated, and coordinate mechanism to ensure the delivery of understandable, timely, accurate, and consistent information to the public during a complex emergency incident

(2). &n= bsp; It includes:

(a). &n= bsp; The plans, protocols, and structures used to provide information to the public during incident operations

(b). &n= bsp; Encompasses all government jurisdictions, NGOs, and relevant private sector PIOs, staff, and JICs established to support an emergency incident(s)

(c). &n= bsp; The following organizational principles:

(i). &n= bsp; The JIC must include representatives of each jurisdiction, agency, NGO, and pri= vate sector organization involved in incident management activities

(ii). &= nbsp; A single JIC location is preferable,= but the JIS should be flexible and adaptable enough to accommodate multiple JIC locations when required

(iii). = Each JIC must have procedures and protocols to facilitate communication and coordination and coordination with other JICs and with the other appropriate components of the ICS organization

<= /span> &= nbsp;

I. COMMAND AND MANAGEMENT (CONTINUED)

C. Public Information Sys= tems (Continued)

<= /span>3. = System Description and Components (Continued)

b. = Joint Information Organizational Components

(1). &n= bsp; Press Secretariat, that is made up of representatives of all relevant organizatio= ns involved in the emergency incident(s)

(2). &n= bsp; Liaison Office (as required)

(3). &n= bsp; Research Team

(4). &n= bsp; Media Operations

(5). &n= bsp; Logistics Team

II. PREPAREDNESS

A. Concepts and Principle= s

<= /span>1. = Levels of Capability

a. &nbs= p; Preparedness involves actions to establish and sustain prescribed levels of capability necessary to execute a full range of incident management operations

b. &nbs= p; Preparedness focuses on guidelines, protocols, and standards for planning, training, personnel qualification and certification, equipment certification, and publication management

<= /span>2. = A unified Approach

A major objective of preparedness efforts is to ensure mission integration and interoperability in response to emergent crises across functional and jurisdictional lines, as well as among public, NGO, and private sector organizations.

<= /span>3. = Mitigation

Mitigat= ion activities provide a critical foundation across incident management, from prevention through response and recovery, including

a. &nbs= p; Ongoing public education and outreach activities designed to reduce loss of life and destruction of property

b. &nbs= p; Structural retrofitting to deter or lessen the effects of incidents and reduce loss of life, destruction of property, and negative effects on the environment

II. PREPAREDNESS (CONTINU= ED)

A. Concepts and Principals (Continued)

<= /span>3. = Mitigation (Continued)

c. &nbs= p; Code enforcement through such activities as zoning regulation, land management, = and construction regulations (building, plumbing, electrical, and HAVC), includ= ing the consideration of the establishment of such codes, where they do not exi= st

d. &nbs= p; Flood insurance and the buy-out of properties subjected to frequent flooding, etc= .

e. &nbs= p; NIMS Publications

= This area of the NIMS has not been developed to the extent it is ready for inclu= sion in this revision of the C/WLEPC ERP.

B. Achieving Preparedness=

<= /span>1. = Preparedness Organizations

Prepare= dness is the responsibility of individual jurisdictions and their preparedness agenc= ies, including the coordination of the various preparedness activities among all appropriate organizations (governmental, NGO, and private sector). Prepared= ness Organizations should:

a. &nbs= p; Establish and coordinate emergency plans and protocols, including public communicatio= ns and awareness.

b. &nbs= p; Integrate and coordinate the activities of the jurisdictions and functions within the= ir purview.

c. &nbs= p; Establish the standards, guidelines, and protocols necessary to promote interoperabil= ity among member jurisdictions and relevant organizations.

d. &nbs= p; Adopt standards, guidelines, and protocols for the provision of resources to requesting relevant organizations, including protocols for supporting NGOs.=

e. &nbs= p; Set priorities for resources and other requirements.

f. &nbs= p; Ensure the establishment and maintenance of multi-agency, multi-governmental jurisdiction and agency, NGO, and relevant private sector organization coordination mechanisms.

II. PREPAREDNESS (CONTINU= ED)

B. Achieving Preparedness (Continued)

<= /span>2. = Preparedness Programs

Individ= ual jurisdictions establish procedures that address the requirement for each st= ep of the preparedness cycle (planning, training, equipping, exercising/drilli= ng, evaluating, and taking action to correct and mitigate). These programs should adopt relevant NIMS standards, guidelines, processes and protocols.<= o:p>

<= /span>

<= /span>a. = Preparedness Planning

&n= bsp; (1). Emerg= ency Operations Plan (EOP)/Emergency Response Plan (ERP)

Each jurisdiction develops and EOP/ERP that defines the scope of preparedness and incident management activities necessary for it, as well as provide informa= tion on:

&= nbsp; (a). Organ= izational structure

&= nbsp; (b). Roles= and responsibilities

&= nbsp; (c). Polic= ies

&= nbsp; (d). Protocols

&= nbsp; (e). Respo= nse activities

&= nbsp; (f). Recov= ery activities

&= nbsp; (g). Long = term prevention

&= nbsp; (h). Long = term mitigation

&= nbsp; (i). Purpose of the plan

&= nbsp; (j). Concept of operations

&= nbsp; (k). Plan = development and maintenance

&= nbsp; (l). Relevant data bases

&= nbsp; (m). Glossary of relevant terms

&= nbsp; (n). Addit= ional information as relevant

An EOP/= ERP should be flexible enough for use in all emergencies, taking = into consideration personnel, apparatus, equipment, supplies, materials, and facilities available.

&n= bsp; (2). Proce= dures

&n= bsp; = ; = There are four standard levels of procedural documents

(a). &n= bsp; Overview – a brief concept summary of an incident-related function, team, or capability.

(b). &n= bsp; SOP or operations manual – a complete reference document that details the procedures for performing a single function or a number of interdependent functions.

(c). &n= bsp; Field Operations Guide (FOG) or handbook – a durable pocket or desk guide t= hat contains essential information required to perform specific assignments or functions.

II. PREPAREDNESS (CONTINU= ED)

B. Achieving Preparedness (Continued)

2. Preparedness Programs (Continued)

a. = Preparedness Planning (Continued)

(2). Proce= dures (Continued)

(d). <= /span>Job Aid – a checklist or other aid that is useful in performing or traini= ng for a job.

(3). Prepa= redness Plans

&= nbsp; &nbs= p; Preparedness plans describe the following:

(a). &nb= sp; Process and schedule for identifying and meeting training needs.

(b). &n= bsp; Process and schedule for developing, conducting, and evaluating exercises (drills) = and correcting identified deficiencies.

(c). &n= bsp; Arrangements for procuring or obtaining required incident management resources through mutual-aid mechanisms

(d). <= /span>Plans for facilities and equipment that can withstand the effects of hazards (eme= rgencies) that the jurisdiction is likely to face.

&n= bsp; (4). Corre= ctive Action and Mitigation Plans

(a). &n= bsp; Corrective action plans are designed to implement procedures that are based upon lesso= ns learned from actual incidents or from training and exercises (drills).

(b). &n= bsp; Mitigation plans describe activities that can be taken prior to, during, or after an incident, to reduce or eliminate risks to persons or property or to lessen = the actual or potential effects of consequences of an incident.

&n= bsp; (5). Recov= ery Plans

(a). &n= bsp; Short-term recovery plans describe actions beyond rapid damage assessment and those necessary to provide immediate life support for victims.

(b). &n= bsp; Long-term recovery plans involve the identification of strategic priorities for restoration, improvement, and growth.

b. = Training and Exercises

(1). &n= bsp; Incident management organizations and personnel, including all levels of government, NGOs, and relevant private sector organizations, must be appropriately trai= ned to improve all-hazards (emergencies) incident management capability.

(2). &n= bsp; Incident management organizations and personnel must participate in realistic exerci= ses (drills), including multi-interdisciplinary and multi-jurisdictional events, as well as NGO and relevant private sector interaction.

II. PREPAREDNESS (CONTINU= ED)

B. Achieving Preparedness (Continued)

<= /span>2. = Preparedness Programs (Continued)

<= /span>b. = Training and Exercise (Continued) &= nbsp;

(3). &n= bsp; To assist in (1). and (2). above, the NIMS Integration Center, as defined in Chapter V. (not ready for inclusion in local plans for 2005), will

(a). &n= bsp; Facilitate the development and dissemination of national standards, guidelines, and protocols for incident management training and exercises.

(b). &n= bsp; Facilitate the use of modeling and simulation capabilities for training and exercise programs.

(c). &n= bsp; Facilitate the definitions of general training requirements and approved training cour= sed for all NIMS users.

(d). <= /span>Review and approve, with the assistance of relevant national organizations and the input from personnel at all levels of government and from relevant NGOs and private sector emergency preparedness organizations, discipline-specific requirement and training courses.

<= /span>c. = Personnel Qualifications and Certifications

(1). &n= bsp; NIMS has set requirements for emergency management and emergency response person= nel to meet national standards for qualification and certification.

(2). &n= bsp; Such qualification and certification will be mandatory for emergency management = and emergency response personnel involved in incidents involving mutual aid ser= vice in another state.

(3). &n= bsp; Local government jurisdictions should credential personnel (paid and volunteer) in their own jurisdictions.

(4). &n= bsp; To enable the above qualification and certification function at the national level. The NIMS Integration Center as defined in NIMS Chapter VII (not ready for inclusion in this ERP in 2005):

(a). &n= bsp; Facilitates the development and/or dissemination of national standards, guidelines, and protocols for qualification and certification.

(b). &n= bsp; Reviews and approves the discipline-specific requirements submitted by functionally oriented incident management organizations and associations.

(c). &n= bsp; Facilitates the establishment of a data maintenance system to provide incident managers with detailed qualifications, experience,

II. PREPAREDNESS (CONTINU= ED)

B. Achieving Preparedness (Continued)

2. Prepa= redness Programs (Continued)

&= nbsp; (c). (Cont= inued)

Personnel Qualifications and Certifications (Continued)

and tra= ining information needed to credential personnel for prescribed incident manageme= nt positions

<= /span>d. = Equipment Certification

(1). &n= bsp; A critical component of operational preparedness is the acquisition of equipm= ent that will perform to certain standards, including the capability to interoperable with equipment used by other jurisdictions.

(2). &n= bsp; To enable national-level equipment certification, the NIMS Integration Center,= as defined in Chapter VII of the NIMS (not ready for inclusion in the 2005 ERP= ), will

(a). &n= bsp; In coordination with appropriate governmental, NGO, relevant private sector or= ganizations, and incorporating standards and certification programs already in use by nationwide incident management response organizations, facilitate the development and/or publication of national standards, guidelines, and proto= cols for equipment certification.

(b). = Review and approve, with the assistance of national professional organization and = with input from governmental, NGO, and relevant private sector organizations, li= sts of emergency responder equipment that meet national certification requireme= nts.

<= /span>e. = Mutual Aid Agreements

(1). &n= bsp; Mutual-aid agreements are the means for one jurisdiction to provide resources, apparat= us, equipment, supplies, materials and other required support to another jurisdiction during an incident.

(2). &n= bsp; Each jurisdiction should be party to a written mutual-aid agreement, such as the NIMS Emergency Management Assistance Compact, with appropriate jurisdiction= s, NGOs, and relevant private sector entities.

(3). &n= bsp; At a minimum, mutual-aid agreements should include the following:

= (a). Defin= itions of key terms used in the agreement,

= (b). Roles= and responsibilities of individual parties,

(c). Proce= dures for requesting and providing assistance,

(d). <= /span>Procedures, authorities, and rules for payment, reimbursement, and allocation of costs,=

(e). &n= bsp; Notification procedures,

(f). &n= bsp; Protocols for interoperable communications,

II. PREPAREDNESS (CONTINU= ED)

B. Achieving Preparedness (Continued)

<= /span>2. = Preparedness Programs (Continued)

<= /span>e. = Mutual Aid Agreements (Continued)

(g). &n= bsp; Relationships with other agreements among jurisdictions,

(h). &n= bsp; Workers Compensation coverage and payment,

(i). &n= bsp; Treatment of liability and immunity,

(j). &n= bsp; Recognition of qualifications and certifications, and

(k). &n= bsp; Sharing agreements, as required.

<= /span>f. &= nbsp; Publications Management

(1). &n= bsp; The NIMS will compose, produce, and distribute a wide variety of publications u= nder specific management guidelines and protocols.

(2). &n= bsp; To enable national-level publications management, the NIMS Integration Center,= as defined in Chapter VII of the NIMS (not ready for inclusion in this 2005 ERP Revision), will:

(a). &n= bsp; Facilitate the development, publication, and dissemination of national standard, guidelines, and protocols for a NIMS publication system,

(b). &n= bsp; Facilitate the development of general publications for NIMS users, as well as their issuance via the NIMS publication management system, and

(c). &n= bsp; Review and approve, with the assistance of appropriate and relevant national professional organizations, and with the input from relevant governmental, = NGO, and private sector entities, the discipline-specific publication management requirements and training courses submitted by relevant professional organizations and associations.

III. RESOURCE MANAGEMENT<= /p>

A. Concepts

1. &nbs= p; Provision of a uniform method of identifying, acquiring, collecting and tracking resources.

2. &nbs= p; Standardization of the classification of kinds and types of resources required to support t= he incident management organization in its enablement of effective mutual aid = and donor assistance.

3. &nbs= p; Use of a credentialing system tied to uniform training and certification standa= rd in order to ensure that the requested personnel resources are successfully integrated into the ongoing incident operations.

III. RESOURCE MANAGEMENT (CONTINUED)

A. Concepts (Continued)

4. &nbs= p; Coordination by the EOC and/or multi-agency coordination entities, as well as specific elements of the ICS structure, such as the Resources Unit section.

5. &nbs= p; Inclusion of resources contributed by private sector and non-governmental organizatio= ns.

B. Principles

1. &nbs= p; Advance Planning for how to manage and employ resources in a variety of possible emergency circumstances.

2. &nb= sp; Resource Identification and Ordering involving:

a. &nbs= p; Use of standardized processes and methodologies to order, identify, mobilize, dispatch, and track the resources required to support incident management activities.

b. &nbs= p; Performance of such tasks either at the IC’s request, or in accordance with plann= ing requirements.

3. &nbs= p; Categorization of Resources by size, capacity, capability, skill, and other characteristic= s to make the resource ordering and dispatch process within jurisdictions, across jurisdiction, and between governmental and non-governmental entities more efficient and to ensure that ICs receive resources appropriate to their nee= ds.

4. &nbs= p; Use of Pre-incident Agreements, such as mutual aid, EMAC, etc., among all parti= es that might request or provide resources to ensure the employment of standardized, interoperable equipment, and other incident resources during incident operations.

5. &nbs= p; Use of Effective Resources Management in a systematic and effective manner.

a. &nbs= p; Development of tools and related standardized processes to support acquisition activiti= es used to obtain resources to support operational requirements, such as missi= on tasking, contracting, drawing from existing stock, and making micro-purchas= es.

b. &nbs= p; Development of management information systems to collect, update, and process data, tra= ck resources, and display their readiness status, such as GIS, resource tracki= ng systems, transportation tracking systems, inventory management systems, and reporting systems.

c. &nbs= p; Development of ordering, mobilization, dispatching, and demoblization standard protocol= s to request resources, prioritize requests, activate and dispatch resources to incident sites, and return resources to normal locations, such as tracking systems that identify the location and status of mobilized and dispatched resources.

III. RESOURCES MANAGEMENT (CONTINUED)

C. Managing Resources

1. &nbs= p; Identifying and Typing Resources through the categorizing resource that Incident Comman= ders commonly request, use and deploy, by capability.

2. &nbs= p; Certifying and Credentialing Personnel to ensure that personnel representing various jurisdictional levels and functional disciplines posses a minimum of common level of training, currency, experience, physical and medical fitness, and capability for the incident management or emergency responder position that they are tasked to fill.

3. &nbs= p; Inventorying Resources through the entering of such resources into a resource tracking system maintained at local, state, regional, and national levels and making such information available to relevant organizational units. such informati= on would include the availability of assets, the need for pre-incident readine= ss warehousing resource shelf live and environmental requirements, and replenishment funding requirements.

4. &nbs= p; Identifying Resource Requirements throughout the various stages of an incident and take= the necessary steps to have the needed resources readily available during the l= ife of an incident.

5. &nbs= p; Ordering and Acquiring Resources through the establishment of clear and concise protocols for local and non-local resources not already readily available, utilizing higher levels of the incident management organization as necessar= y.

6. &nbs= p; Tracking and Reporting Resources through a standardized, integrated resource tracking process through the life of an incident, in order to provide incident management with a clear picture of where resources are located, assist rele= vant incident staff to effectively receive the subject resources, protect the sa= fety of personnel and security of supplies and equipment, and enable the coordination of movement of personnel, equipment, supplies, and materials.<= /p>

7. &nbs= p; Mobilizing and Demobilizing resources through timely action by relevant incident management personnel, including securing information about relevant resourc= es at the time of notification, tracking of resources from origin to incident = site location, utilizing standard, interagency mobilization guided at all governmental levels, and following through with the orderly demobilizing of= all resources at the termination of an incident, utilizing relevant plan components, plans, and protocols.

8. &nbs= p; Returning and Recovering Resources through their final disposition according to relev= ant policies, procedures, and protocols, including return, rehabilitation, replenishment, disposal, and retrograde classification.

a. &nbs= p; Non-expendable resources are fully accounted for at the incident site and again upon retur= n to the source unit that issued them, where the issuing

III. RESOURCE MANAGEMENT (CONTINUED)

C. Managing Resources (Continued)

<= /span>8. = (Continued)

&n= bsp; a. = (Continued)

source = unit restores and resources to full functional capability and readies them for t= he next mobilization, with broken or lost items being replaced as soon as poss= ible by the organization unit responsible for the loss or breakage.

b. &nbs= p; Expendable resources are also fully accounted for, with the user organizational unit bearing the costs of replacing such expendable resources.

IV. COMMUNICATIONS AND INFORMATION MANAGEMENT

B. Managing Information and Communications systems enables the essential functions need= ed to provide a common operating picture and interoperability for incident management at all levels, resulting in effective incident information management and

incident management communications.

&nb= sp;

1. &nbs= p; Information Management by the NIMS Integration Center (NIC) will facilitate the definit= ion and maintenance of documented policies and interoperability standards requi= red to guide the development of NIMS-related information systems.

a. &nbs= p; Pre-incident preparedness information will be the responsibility of the relevant emergen= cy preparedness organizational units involved in the resolution of the inciden= t, along with relevant private-non-profit and private sector entities.

b. &nbs= p; The information management system will provide guidance, standards, and tools to enable relevant governmental agencies, non-governmental entities and private sector entities to most effectively conduct information management activiti= es.

c. &nbs= p; Communications networks will be used by the relevant Emergency Operations Center to disseminate critical information that constitutes a common operating pictur= e, including indications and warnings, incident notifications, and public communications. Notifications will be made to the appropriate jurisdictional levels and to relevant non-governmental entities and relevant private sector entities through the mechanisms defined in emergency operations, emergency response, and incident action plans at all levels of government.

d. &nbs= p; Information management technologies of relevant nature will be planned for in advance by the relevant emergency preparedness agencies at all

IV. COMMUNICATIONS AND INFORMATION MANAGEMENT (CONTINUED)

B. Managing Communications and Information (Continued)

<= /span>1. = Information Management by NIMS Integration Center (Continued)

&n= bsp; d. = (Continued)

levels = of government in order to tie together all command, tactical, and support units involved in incident management, and enable such entities to share informat= ion critical to incident resolution and the cataloguing of required corrective actions.

2. &nbs= p; Incident Management Communications process systems establishment of an effective nat= ure will be the responsibility of the relevant emergency preparedness organizations, in order to support a complete spectrum of incident manageme= nt activities.

a. &nbs= p; Individual jurisdictions will be required to comply with national interoperable communications standard when such standards are developed.

b. &nbs= p; Incident communications will follow the standards called for under the ICS.

c. &nbs= p; The incident command manages communications at an incident command manages communications at an incident, using a common communications plan and an in= cident-based communications center established solely for use by the command, tactical a= nd support resources assigned to the incident, with all entities involved in managing the incident utilizing common terminology for communications prescribed by the NIMS.

3. &nbs= p; Interoperability Standards will be administered by the NIC in order to facilitate the development of data standards, to include secure communications when requir= ed for the functions described below; and develop standards in accordance with such functions.

a. &nb= sp; Incident notification at all levels will utilize standard notification and situation report data, but will not prevent information unique to a reporting organization from being collected or disseminated; as well as standardize t= he transmission of data in a common format to enable the passing of appropriate notification information to a national system where data queries and information/intelligence assessment and analysis can occur.

b. &nbs= p; Status reporting will be defined by a standard set of date elements to facilitate = the process for all levels of government to initiate status reports, and then disseminate them to other jurisdictions, such as Situation Reports (SITREPS) and Pollution Report (POLRPS).

c. &nbs= p; Analytical data collection of an environmental nature by relevant agencies at all leve= ls of government need to have a standard set data elements established, which would enable more reliable laboratory analysis and

IV. COMMUNICATIONS AND INFORMATION MANAGEMENT (CONTINUED)

B. Managing Communications and Information (Continued)

<= /span>3. = Interoperability Standards (Continued)

&n= bsp; c. = (Continued)

improve= the quality of assessments provided to decision makers; facilitate collection of analytical data in the field, such as information on public health and envi= ronmental monitoring, in a manner that observes standard data definitions; and allow = the transmission of the data to laboratories using standardized analysis proces= ses.

d. &nbs= p; Geospatial information, correctly utilized, is of an increasing important nature to in= cident management personnel, since it can be used to integrate assessments, situat= ion reports, and incident notification into a coherent common operating picture; tie the use of geospatial data to consistent standards to prevent incorrect= ly transformed or otherwise misapplied coordinated to cause inconspicuous, yet serious errors; and enable systems to be used in remote field locations whe= re telecommunications capabilities may not have sufficient bandwidth to handle large images or are limited in terms of computing hardware.

e. &nbs= p; Wireless communications and computing standards for interoperations will be included= in the NIMS for emergency management and emergency response entities at all le= vels of government and for relevant non-governmental entities to ensure that incident management entities can communicate and share information with oth= er through effective wireless systems.

f. &nbs= p; Identifications and authentication of individuals and organizations that access the NIMS information management system, and in particular those that contribute information to the system, such as situation reports, must be properly authenticated and certified for security purposes, thus requiring a national authentication and security certification standard for the NIMS that is flexible and robust enough to ensure that information can be properly authenticated and protected, a responsibility to be assigned to the NIC with representative of the various levels of government and non-governmental entities collaborating.

g. &nbs= p; A National database of incident reports, that can be used to support incident management efforts, will be developed collaboratively through the NIC by representatives of relevant entities at all levels of government responsible for receiving initial incident reports.

V. SUPPORTING TECHNOLOGIES

INTRODUCTION

Technology and technological systems provide supporting capabilities essential to implementing continuously refining the NIMS, including:

A. &n= bsp; Voice and data communications systems,

B. &n= bsp; Information systems (record keeping and resource tracking),

C. &n= bsp; Display systems, and

D. Specialized technologies that facilitate incident operations and incident management activities.

&nbs= p;

Strategic research and development ensures that ongoing development of science and technology

takes pla= ce. The NIMS also relies upon scientifically based technical standards that support= the

nation= 217;s ability to prepare for, prevent, respond to, and recover from domestic incidents.

&nbs= p;

A. &n= bsp; CONCEPTS AND PRINCIPLES

&nbs= p; 1. = Interoperability and Compatibility

a. Systems must be able to work together and should not interfere with one another, especially when there is the involvement of multiple jurisdictions, organizations, and functions.

b. = This is achieved through the use of such tools as:

&= nbsp; 1. = Common communications and data standards

&= nbsp; 2. = Digital data formats

&= nbsp; 3. = Equipment standards

&= nbsp; 4. = Design standards

&nbs= p;

2. Technology Support

a. = Permits organizations using the NIMS to enhance all aspects of incident management = and emergency response.

b. = Facilitates incident operations.

c. = Sustains the research and development programs that underpins future incident manage= ment capabilities.

&nbs= p;

&nbs= p; 3. = Technology Standards

a. Based upon the requirements developed through preparedness organizations at vario= us jurisdictional levels.

b. = National standards facilitate the interoperability and compatibility of major operational systems across jurisdictional, geographic, and functional lines= .

&nb= sp;

V. SUPPORTING TECHNOLOGIES (CONTINUED)

A. &n= bsp; CONCEPTS AND PRINCIPLES (CONTINUED)

&nbs= p; 4. = Broad-Based Requirements

a. = Needs for new technologies, procedures, protocols, and standards to facilitate incident management exist at both the local and state, and the national lev= els.

b. = NIMS provides a mechanism for collecting and prioritizing the needs from the loc= al to the national level.

c. = The needs will be met by coordinating basic, applied, developmental, and demonstration research, testing, and evaluation activities.

&nbs= p;

&nbs= p; 5. = Strategic Planning for R&D

&nbs= p; &= nbsp; a. = Identifies future technologies that can:

i. = Improve preparedness, prevention, response, and recovery

capabilities, or

&= nbsp; ii. = Lower the cost of existing capabilities.

b. = The NIMS Integration Center will integrate into the national R&D agenda the incident management science and technology needs of relevant public, nongovernmental,a nd private entities operating within the NIMS at all leve= ls of government.

B. &n= bsp; SUPPORTING INCIDENT MANAGEMENT WITH SCIENCE AND TECHNOLOGY

&nbs= p; 1. = Operational Scientific Support

a. = Indentifies and, on request, mobilizes scientific and technical assets that can be used= to support incident management activities.

b. = Draws on the scientific and technological expertise of Federal agencies and other relevant governmental, nongovernmental, and private sector organizations. <= /p>

&nbs= p;

2. Technical Standards Support

The subject support enable= s the development and coordination of technology standard for the NIMS to ensure = that all of its components perform effectively together without disrupting one another. The following principles will be used to define the subject standa= rds.

a.&n= bsp; Performance Measurements as a Basis for Standards <= /p>

A performance measurement structure, based upon how relevant activities work effectively in the real world of emergency preparedness, will, to help incident management organizations use equipment systems effectively, will develop:

V. SUPPORTING TECHNOLOGIES (CONTINUED)

B. SUPPORTING INCIDENT MANAGEMENT WITH SCIENCE AND TECHNOLOGY (CONTINUED)

&= nbsp; 2. = Technical Standards Support (Continued)

&= nbsp; &nbs= p; a. = Performance Measurements as a Basis for Standards (Continued)

&= nbsp; &nbs= p; &= nbsp; i. &= nbsp; Guidelines

&= nbsp; &nbs= p; &= nbsp; ii. = Performance standards

&= nbsp; &nbs= p; &= nbsp; iii. Testing protocols

&= nbsp; &nbs= p; &= nbsp; iv. Personnel certification

&= nbsp; &nbs= p; &= nbsp; v. = Reassessment

&= nbsp; &nbs= p; &= nbsp; vi. Training procedures

&nbs= p; &= nbsp; b. = Consensus-Based Performance Standards

i. &= nbsp; Builds on existing approaches to standards for interoperable equipment and systems= .

ii. = Takes advantage of existing organizations with long-standing interest and experti= se, including:

&= nbsp; (a). Natio= nal Institute of Justice

&= nbsp; (b). Natio= nal Institute for Standards and Technology

&= nbsp; (c). natio= nal Institute for Occupational Safety and Health

&= nbsp; (d). American Na= tional Standards Institute

&= nbsp; (e). Ameri= can Society for Testing and Materials

&= nbsp; (f). natio= nal Fire Protection Association

iii. The NIMS Integration Center has established working relationships among the organizations listed in b. ii. above and incident management organizations = at all levels to develop performance standards for incident management technol= ogy.

c. = Test and Evaluation by Objective Experts

i. &= nbsp; NIMS technology criteria will rely upon private sector and public sector testing laboratories to evaluate equipment against NIMS technical standards.

ii. = The NIMS Integration Center will issue appropriate guidelines as part of its standard-development and facilitation responsibilities.

d. = Technical Guidelines for Training Emergency Responders on Equipment Use =

i. &= nbsp; Inputs from mulnerability analysts, equipment developers, users, and standards exp= erts will be employed to develop sscientifically based technical guidelines for training emergency responders on how to use relevant equipment properly

V. SUPPORTING TECHNOLOGIES (CONTINUED)

B. SUPPORTING INCIDENT MANAGEMENT WITH SCIENCE AND TECHNOLOGY (CONTINUED)

&= nbsp; 2. = Technical Standards Support (Continued)

d. = Technical Guidelines for Training Emergency Responders on Equipment Use (Continued)

&= nbsp; ii. = The training guidelines referred to in i. above:

&= nbsp; &nbs= p; (a). Refle= ct threat and vulnerability information

&= nbsp; &nbs= p; (b). Equip= ment and systems capabilities

&= nbsp; &nbs= p; (c). A ran= ge of expected operating conditions

iii. Performance measures and testing protocols developed from the subject training guidelin= es provide a reproductible method of measuring the effectiveness of equipment = and systems.

&nbs= p; 3. = Research and Development to Solve Operational Problem

a.&n= bsp; R & D planning will be based on the operational needs of the entire range of NIMS users.

b.&n= bsp; USDHS is responsible for integrating user needs at = all levels into the national R & D agends.

&nb= sp;