MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_01C804F5.D4B24290" This document is a Single File Web Page, also known as a Web Archive file. If you are seeing this message, your browser or editor doesn't support Web Archive files. Please download a browser that supports Web Archive, such as Windows® Internet Explorer®. ------=_NextPart_01C804F5.D4B24290 Content-Location: file:///C:/E67C29E3/CHAPTERVI-C.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" A

 

A.  &nb= sp;     INTRODUCTION

        =    

The Incident Command System (ICS), long adopted by emergency response organizat= ions in the Cabell/Wayne Local Emergency Planning District, is evolving to some extent, because of the National Incident Management System (NIMS), establis= hed as one of two major components of Homeland Security Presidential Directive-5 (HSPD-5). The purpose of NIMS is to ensure that all Federal, State and local emergency response and emergency management organizations in the United Sta= tes will be able to work effectively together in any emergency incident, no mat= ter how large the emergency incident or how complex the emergency incident. NIM= S, which is effective October 1, 2005, builds upon the long adopted ICS.<= /o:p>

 

The NIMS recognizes that the local Incident Commander is the primary decision m= aker with regard to the resolution of an emergency incident, and that he must ha= ve flexibility in establishing the Incident Command organization, taking into consideration the complexity of the emergency incident and the availability= of qualified personnel resources to staff the Incident Command structure. (See Chapter I, Appendix “F”).

        =    

I. = ;         SINGLE JURISDICTION ORGANIZATION

        =    

The ICS organization for a single jurisdiction basically consists of three part= s; the Incident Command, the incident field operations, and the Emergency Operations Room (EOR) which provides support during the more complex emerge= ncy incidents.

        =    

A.        The Incident Command Post (ICP)

The ICP consists of the Incident Commander, the Command Staff*, and the General        

Staff*

NOTE: An asterisk (*) denotes a term from the NI= MS

        &= nbsp;    1.&= nbsp;       Command Staff

        &= nbsp;           &nbs= p;   a. Public Information Officer

        &= nbsp;           &nbs= p;   b. Safety Officer

        &= nbsp;           &nbs= p;   c. Liaison Officer*

        &= nbsp;           &nbs= p;   Serves as point of contact for the IC, with

        &= nbsp;           &nbs= p;            &= nbsp;  1. Other governmental agencies

        &= nbsp;           &nbs= p;            &= nbsp;  2. Non-governmental Organizations (NGO’s)

        &= nbsp;           &nbs= p;            &= nbsp;  3. Relevant private sector entities

        &= nbsp;           &nbs= p;            &= nbsp;  4. Assisting agencies and organizations

        &= nbsp;           &nbs= p;            &= nbsp;  5. Cooperating agencies and organizations

        &= nbsp;           &nbs= p;   d. Additional Command Staff

        &= nbsp;   May be appointed in keeping with the scope and complexity of the incident.=

        &= nbsp;  

        &= nbsp;           &nbs= p;  

 

I.     &nb= sp;    SINGLE JURISDICTION ORGANIZATION (Continued)

A.        The Incident Command Post (ICP) (Continued)

        &= nbsp;   1.         = Command Staff (Continued)

        &= nbsp;           &nbs= p;   d. (Continued)

        &= nbsp;           &nbs= p;   Examples are:

        &= nbsp;           &nbs= p;            &= nbsp;  (1). Legal Counsel*

        &= nbsp;           &nbs= p;            &= nbsp;  (2). Medical Advisor*

        &= nbsp;           &nbs= p;            &= nbsp;  (3). Facility Representative

 

        &= nbsp;   2.         = The General Staff

        &= nbsp;           &nbs= p;   Represents and is responsible for the functional aspects of the Incident Command structure. Reports to the Incident Commander.

        &= nbsp;           &nbs= p;   a. Operations Chief*

        &= nbsp;   Directs the Operations* Section. Supervises the following Branches*, as needed,

        &= nbsp;   in an incident.

        &= nbsp;           &nbs= p;            &= nbsp;  (1).   Incident Site

        &= nbsp;           &nbs= p;   (2).   Reception Area* (The point at which all incident resources are

        &= nbsp;           &nbs= p;   checked in, prior to being dispatched to the Staging Area, the

        &= nbsp;           &nbs= p;   Incident Site or to another incident related location).

        &= nbsp;           &nbs= p;   (3).   Traffic Diversion and Securi= ty

        &= nbsp;           &nbs= p;   (4).   Search and Rescue=

        &= nbsp;           &nbs= p;   (5).   Decontamination

        &= nbsp;           &nbs= p;   (6).   Triage/Treatment<= /span>

        &= nbsp;           &nbs= p;   (7).   EMS Transportation

        &= nbsp;           &nbs= p;   (8).   Evacuation=

        &= nbsp;           &nbs= p;   (9).   Evacuees Reception

        &= nbsp;           &nbs= p;   (10). Shelter-In-Place

        &= nbsp;           &nbs= p;   (11). Additional Functional Branches as needed

        &= nbsp;   b. Planning Chief*

        &= nbsp;   Directs the Planning Section which is responsible for:

        &= nbsp;           =     (1). Collection and evaluation of, and dissemination of incident situation

        &= nbsp;           =      information and intelligence to the Incident Commander, the Unified =

        &= nbsp;           =      Command* (if such is established), and appropriate other incident

        &= nbsp;           =      management personnel.

        &= nbsp;           =      (2). Preparation of Status Reports

        =             &nb= sp;    (3). Display of incident situational information

        =             &nb= sp;    (4). Maintenance of the status of resources assigned to the incident=

        &= nbsp;           =      (5). Development and documentation of the incident Action Plan (IAP)= *,

        &= nbsp;           =      based upon guidance for the IC or UC

  &nbs= p;            &= nbsp;           &nbs= p;         

 

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'>I.          SINGLE JUR= ISDICTION ORGANIZATION (Continued)

A.        The Incident Command Post (ICP) (Continued)

2.         = The General Staff (Continued)

        &= nbsp;   b. Planning Chief* (Continued)

        &= nbsp;           =       (6). Supervises the Following Section Heads if the incident complexi= ty

        &= nbsp;           =        justifies it:   

        &= nbsp;           &nbs= p;            &= nbsp;  (a). Resources*

        &= nbsp;           &nbs= p;            &= nbsp;  (b). Situation*

        &= nbsp;           &nbs= p;            &= nbsp;  (c). Demobilization*

        &= nbsp;           &nbs= p;            &= nbsp;  (d). Documentation*

        &= nbsp;   c. Logistics Chief*

        &= nbsp;   Directs the Logistics Section, which is responsible for:

        =                =              (1).   Procuring additional resourc= es

        &= nbsp;           =     (2).   Incident op= erations related facilities

        &= nbsp;           =     (3).   Incident Operations related transportation

        &= nbsp;           =     (4).   Supplies

        &= nbsp;           =     (5).   Materials

        &= nbsp;           =     (6).   Equipment r= epair and maintenance

        =             &nb= sp;   (7).   Food Servic= es

        &= nbsp;               (8).<= span style=3D'mso-spacerun:yes'>   Communications and informati= on technology support

        &= nbsp;           =     (9).   Emergency responder medical service

        &= nbsp;           =     (10). Supervising the following Units, as justified by the        =             &nb= sp;          

        =             &nb= sp;    complexity of the incident

        &= nbsp;           &nbs= p;            &= nbsp;  (a). Supply

        &= nbsp;           &nbs= p;            &= nbsp;  (b). Food

        &= nbsp;           &nbs= p;            &= nbsp;  (c). Ground Support

        &= nbsp;           &nbs= p;            &= nbsp;  (d). Communications

        &= nbsp;           &nbs= p;            &= nbsp;  (e). Facilities

        &= nbsp;           &nbs= p;            &= nbsp;  (f). Medical

        &= nbsp;   d. Finance/Administration Chief*

        &= nbsp;   Directs the Finance/Administration Section, which is responsible for Units

        &= nbsp;   Covering:

        &= nbsp;           =     (1). Compensation/Claims

        &= nbsp;           =     (2). Procurement

        &= nbsp;           =     (3). Cost

        &= nbsp;           =     (4). Time

 

 = ;

 = ;

 = ;

 = ;

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'>I.          SINGLE JURISDICTION ORGANIZATION (Continued)

B.        Incident Commander’s Organizational Options

        &= nbsp;   Dependent on the complexity and anticipated time of resolution of the incident

        &= nbsp;   and/or the availability of qualified personnel, the IC has the option of:

        &= nbsp;           &nbs= p;   1.         = Assuming the responsibilities of an immediate subordinate position

        &= nbsp;           &nbs= p;            &= nbsp;  that he is qualified for, other than PIO

        &= nbsp;           =      2.     &nbs= p;  Combining the responsibilities of two or more immediate subordinate positions

 

C.        Incident Field Operations

        &= nbsp;   The incident field operations, under the Operati= ons Section Chief is organized

        &= nbsp;   into Branches,* (further organization of the Branches is into Divisions* and/or =

            Groups*) dependent upon the scope, complexity, and length of time of the =

        =      incident. The more common Branches, with the titles presently used in the

        =      C/WLEPD:

  &nbs= p;            &= nbsp;       

  &nbs= p;            &= nbsp;        1. Incident Branch Site

  &nbs= p;         This Branch is supervised by the Branch Supervisor/Incident Site     

(BS/IC). This operation focuses on the core reso= lution of the incident. The Branch Supervisor will normally be a senior emergency response profession who is most related to the type of incident.=

 

2. Search and Rescue Branch

  &nbs= p;         This Branch is supervised by the Branch Supervisor/Search and Rescue  

(BS/S&R). This operation focuses on the loca= ting and retrieving individuals who have become unaccounted for during the initi= al period of the incident. The Branch Supervisor will normally be a senior emergency responder who is fully qualified to lead and manage this Branch’s activities.

 

  &nbs= p;            &= nbsp;        3. Reception Area Branch*

This Branch is supervised by the Branch Supervisor/Reception Area (BS/RA). This operation focuses on the initial in= take management of incident resources, personnel, apparatus, equipment, and supp= lies that will ultimately be dispatched to the Staging Area or to an incident related site.

 

 

 

 

 

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'> 

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'>I.          SINGLE JURISDICTION ORGANIZATION (Continued)

C.        Incident Field Operations (Continued)

 

4. Staging Area Branch

This Branch is supervised by the Branch Supervisor/Staging Area (BS/SA). This operation focuses on the management of resources that are readily available for utilization in any aspect of the evolving incident by the IC.

 

5.      Traffic Diversion and Site Security Branch<= /o:p>

  &nbs= p;            &= nbsp;        This Branch is supervised by the Branch Supervisor/Traffic Diversion and       

        =             &nb= sp;   Sight Security (BS/TD&SS). This operation focuses on the diversi= on of all

        =             &nb= sp;   unauthorized pedestrian and vehicular traffic from entry into the incident

        =             &nb= sp;   site as established by the IC, as well as internal site security as necessary.

        =             &nb= sp;   The position of BS/TD&SS is normally held by a senior law enforc= ement

        =             &nb= sp;   officer. Chapter XI of the C/WLEPC ERP, Traffic Diversion Plan =

        =             &nb= sp;   addresses traffic diversion and related site security in some depth.=  

 

6.      Decontamination Branch

  &nbs= p;            &= nbsp;           &nbs= p;        This Branch is supervised by the Branch Supervisor/Decontamination

  &nbs= p;            &= nbsp;           &nbs= p;        (BS/D). This operation focuses on the establishment and operation of  

        =             &nb= sp;            =    decontamination stations for personnel, vehicles, equipment and supp= lies

        =             &nb= sp;            =    that have been contaminated.

 

7.      Triage and Treatment Branch

  &nbs= p;            &= nbsp;           &nbs= p;        This Branch is supervised by the Branch Supervisor/Triage and Treatment

        =             &nb= sp;            =    (BS/T&T). This operation focuses on establishing priorities for = the

        =             &nb= sp;           =     treatment of injured victims of the incident and provision of stabilizing =

        =             &nb= sp;            =    medical treatment, prior to transportation to a hospital for further medical

        =             &nb= sp;            =    care. The person in charge of T&T is a qualified senior officer = of an EMS

        =             &nb= sp;            =    operation, or a hospital emergency department nurse or physician.

 

8.      EMS Transportation Branch

        =             &nb= sp;            =    This Branch, which should be located adjacent to the T&T Branch area, is

        =             &nb= sp;            =    supervised by the Branch Supervisor/EMS Transportation (BS/EMS T). <= o:p>

        =             &nb= sp;            =    The operation focuses on establishing and managing orderly and =

        =              =             &nb= sp;  expeditious transportation of injured incident victims that have been

        =             &nb= sp;            =    stabilized to one or more area hospitals according to MedCommand

        =             &nb= sp;            =    Directions.

 

 

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'>I.          SINGLE JUR= ISDICTION ORGANIZATION (Continued)

C.      =            Incident= Field Operations (Continued)

 

9.      Evacuation Area Branch

  &nbs= p;            &= nbsp;           &nbs= p;        This Branch, which administrative location should be immediately

        =             &nb= sp;            =    adjacent to the area to be evacuated (up-wind if the incident involv= es a

        =             &nb= sp;            =    hazardous material emission) is supervised by the Branch =

        =             &nb= sp;            =    Supervisor/Evacuation Area (BS/EA). This operation focuses on the

        =             &nb= sp;            =    orderly notification and expeditious evacuation of those persons ins= ide the

        =             &nb= sp;            =    area to be evacuated by whatever mode of movement that is relevant to the

        =             &nb= sp;            =    incident and to the individuals to be evacuated.

 

10.  Evacuation Reception Site Branch

        =             &nb= sp;            =    This Branch, which may have more than one operational location, is <= o:p>

        =             &nb= sp;            =    headed up by the Branch Supervisor/Evacuation Reception Site (BS/ERS= ).

        =             &nb= sp;            =    The location of each operational site should be well away from the <= o:p>

        =             &nb= sp;            =    incident and any possible impact from it. Each location will have a =

        =             &nb= sp;            =    BS/ERS unless the number is such that it makes better sense to the I= C to

        =             &nb= sp;            =    have one BS/ERS over individual Assistant BS/ERSs at the various

        =             &nb= sp;            =    operational sites. Most likely, the BS/ERS and any Assistants will b= e

        =             &nb= sp;            =    qualified staff members or volunteers of the American Red Cross or t= he

        =             &nb= sp;            =    Salvation Army.

 

11.  Shelter-In-Place Area Branch

        =             &nb= sp;            =    This Branch is headed up by the Branch Supervisor/Shelter-In-Place <= o:p>

        =             &nb= sp;            =    (BS/SIP), who is responsible to see that all pre-designated SIP sites are

        =             &nb= sp;            =    operational and in contact with him/her. The Supervisor will also be=

        =             &nb= sp;            =    responsible for monitoring the SIP public notices by TV, radio, Nati= onal

        =             &nb= sp;            =   Weather Service (NWS) and other means, taking corrective action for = the

        =                 =             IC, if shortcomings are noted.

 

12.  Other appropriate Branches as needed.=

        =             &nb= sp;            =    The Operations Chief, with the approval of the IC, may establish and=

        =             &nb= sp;            =    operate other appropriate Branches as appropriate to a particular incident.

 

 

 

 

 

 

 

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'>I.          SINGLE JURISDICTION ORGANIZATION (Continued)

 

D.      =           The Emergency Operations Room

  &nbs= p;            &= nbsp;           &nbs= p;        1. Defined

The Emergency Operations Room (EOR) is one part = of the Emergency Operations Center, the other being the Emergency Communications Center.

 

The purpose of the EOR is to provide support and guidance to the Incident Commander by providing information not readily available to the IC, answering questions from the IC, Providing additional resources to the IC, and in general providing any and all support to the IC, who in all probability will be almost over extended by the tactical incident resolution challenges for incidents lasting more than eight hours or appear that it will do so. The complexity of some incidents will reduce the eight = hour guide line mentioned.

 

The EOR will be located in reasonable proximity = to the jurisdictions Emergency Communications Center, and it will provide the necessary environment for calm, objective decisions involving the provision= of information, resources, and guidance to the IC.

 

2.      Organization

The EOR will be organized in one of two basic ma= nners:

a. The abbreviated operation where the EOR Coord= inator for the jurisdiction involved opens the EOR, but does not fully staff it, providing needed information, answering questions from the IC, securing additional resources for the IC so that the incident may be resolved as expeditiously, and providing guidance as needed. This is done upon the requ= est of the IC, when he/she believes the provision of assistance from the EOR wi= ll not be needed for more than a reasonable amount of time and the complexity = of the incident will not justify full activation of the EOR.=

b.      The full activation of the EOR, also initiated b= y the IC, where the EOR

Coordinator is joined by those in the following = list that are appropriate for the incident:

(1). The Chief Executive or the jurisdiction (municipal

Mayor, or County Commission President.

(2). Municipal or County Attorney

  &nbs= p;            &= nbsp;        (3).  Municipal Police Chief or County S= heriff

(4).  Municipal Fire Chief or County Fire Coordinator

 

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'>I.          SINGLE JURISDICTION ORGANIZATION (Continued)

D.&n= bsp;   The Emergency Operations Room (Continued)

2.      Organization (Continued)

  &nbs= p;         b. (Continued)

  &nbs= p;            &= nbsp;        (5).  A senior EMS officer from the municipality, VFD, or county

  &nbs= p;                 &= nbsp;   (6).  A senior County Health Department professional

  &nbs= p;            &= nbsp;        (7).  Municipal Public Works senior representative

  &nbs= p;            &= nbsp;        (8).  Public Utilities senior representa= tives

  &nbs= p;            &= nbsp;        (9).  Municipal or County finance representative

  &nbs= p;            &= nbsp;        (10. Liaison Representatives from:

  &nbs= p;            &= nbsp;           &nbs= p;        (a). An involved facility

  &nbs= p;            &= nbsp;           &nbs= p;        (b). US Coast Guard if Ohio River is involved

  &nbs= p;            &= nbsp;           &nbs= p;        (c). Other logical organizations or agencies

  &nbs= p;            &= nbsp;        (11). Recorder/clerical support

 

  &nbs= p;            &= nbsp;        Note No. 1: If the IC Staff does not have Planning, Logistics, and

  &nbs= p;            &= nbsp;        Finance and Administration staffers as suggested by the NIMS

        =             &nb= sp;   (See Chapter I, Appendix “F” of this ERP), consider addi= ng them

        =             &nb= sp;   to the above EOR staffing list, and removing (9). above.<= /span>

 

  &nbs= p;            &= nbsp;        Note No. 2: In the City of Huntington and in Cabell County, the <= /span>

  &nbs= p;            &= nbsp;        EOR Coordinator would be the respective Emergency Services

  &nbs= p;            &= nbsp;        Director, who would establish the EOR adjacent to CCERC. In

  &nbs= p;            &= nbsp;        Wayne County, the EOR Coordinator would be the County

  &nbs= p;            &= nbsp;        Emergency Services Director, who would establish the EOR

  &nbs= p;            &= nbsp;        adjacent to the Wayne County E-911 Center.

 

  &nbs= p;         E.        EOR Operations

1.      The EOR coordinator will be responsible for cont= acting the officials and staff initially needed for the particular incident. As the incident progresses the EOR Coordinator will be responsible for deciding up= on alternative EOR staffing to further meet the needs of the incident.

 

2.      The EOR Coordinator receives reports periodicall= y from the IC on the status of the incident. The EOR Recorder records the reported event of the incident on a screen by information from a computer or on a blackboard or whiteboard, so that all members of the EOR present may have an understanding of the incident’s progress. If it appears from the information recorded that the IC can benefit from advice from the EOR membe= rs, the EOR Coordinator will convey such information to the IC.

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'> 

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'>I.          SINGLE JURISDICTION ORGANIZATION (Continued)

E.         EOR Operations (Continued)

3.      If the IC or any of his staff subordinates run i= nto problems or has a need for 

      informatio= n, the IC may call upon the EOR membership through the EOR 

      Coordinato= r for suggestions to resolve the immediate problem or to provide    

      the needed information.

 

4.      If the IC or any of his staff subordinates have = a need for additional resources (personnel, apparatus, vehicles, facilities, suppl= ies, materials, etc.) not already available at the Incident Reception Center or = the Staging Area. The IC may request through the EOR membership through the EOR Coordinator to the provision of such resources.

 

5.      The EOR Coordinator and relevant staff membershi= p will be responsible for

      handling “move up” operations of emergency response units to maintain  

      jurisdicti= on wide coverage during the incident.

 

F.&n= bsp;         EOR Equipme= nt Requirements<= /p>

In order for the EOR membership staff to be able= to perform it duties most effectively, consideration should be given to provid= ing the following equipment:

1.      Relevant emergency planning documents on compute= r disc or hard copy for   each E= OR staff member.

 

2.      Tables or work stations adequate for the proper staffing.

 

3.      Comfortable and ergonomically sound desk chairs = for the proper staffing.

 

4.      Common office supplies for each staff member or = the EOR.

 

5.      Pre-loaded (data bases, directories, relevant ma= ps and charts etc.) desk-top or lap-top computers for each staff member position or specialty computer disc packages that can be quickly loaded into common computers.

 

6.      Computer projection equipment with a variety of = maps, charts, tables, etc. that can project such information on a wall screen, or= a variety of maps, charts, tables that can be pulled down from wall mounts.

 

7.      Blackboards or whiteboards that can be seen by a= ll EOR members that semi-permanent information on incident progress can be posted.=

 

 

<= span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt'>I.          SINGLE JURISDICTION ORGANIZATION (Continued)

F.        EOR Equipment Requirements (Continued)

8.      Cellular and regular telephones for each EOR sta= ff member.

 

9.      A three-way radio system for the use of the EOR Coordinator.

 

10.  Emergency power generator.

 

G.    EOR Facility Requirements<= /p>

1.      Adjacent to emergency communications center.

 

2.      Adequate in size to hold working stations for ne= eded staff personnel to work effectively.

 

3.      Proper lighting for various EOR operations.=

 

4.      Effective HVAC equipment.

 

5.      Small kitchen facility.

 

6.      Break Room with comfortable furnishings.

 

7.      Rest Room.

 

8.      Emergency Sleeping Room (at a minimum a separate= quite room with folding cots that be set up when the EOR is staffed, incase of extended period type incidents, where EOR staff members could not go off du= ty to their homes.

 

II.  &= nbsp;     MULTI-JURISDICTION AND/OR MULTI-LEVELS OF GOVERNMENT INCIDENTS

For Multi-jurisdiction and/or multi-levels of government incidents, the NIMS establishes a number of possibilities, such = as Unified Command (UC)*, Area Command (AC)*, and Unified Area Command (UAC)*.= For information on these organizational concepts of incident management, please= see Chapter I, Appendix “F” of this ERP document.=

 

The NIMS is to take ef= fect on October 1, 2005. It is anticipated that the USDHS will provide opportuni= ties for extensive training on the NIMS, including the above three concepts of multi-jurisdictional and/or multi-l= evel incident management.

 

 

        &= nbsp;           &nbs= p;           &= nbsp;        

------=_NextPart_01C804F5.D4B24290 Content-Location: file:///C:/E67C29E3/CHAPTERVI-C_files/themedata.thmx Content-Transfer-Encoding: base64 Content-Type: application/vnd.ms-officetheme UEsDBBQABgAIAAAAIQCCirwT+gAAABwCAAATAAAAW0NvbnRlbnRfVHlwZXNdLnhtbKyRy2rDMBBF 94X+g9C22HK6KKXYzqJJd30s0g8Y5LEtao+ENAnJ33fsuFC6CC10IxBizpl7Va6P46AOGJPzVOlV XmiFZH3jqKv0++4pu9cqMVADgyes9AmTXtfXV+XuFDApmaZU6Z45PBiTbI8jpNwHJHlpfRyB5Ro7 E8B+QIfmtijujPXESJzxxNB1+SoLRNegeoPILzCKx7Cg8Pv5DCSAmAtYq8czYVqi0hDC4CywRDAH an7oM9+2zmLj7X4UaT6DF9jNBDO/XGD1P+ov5wZb2A+stkfp4lx/xCH9LdtSay6Tc/7Uu5AuGC6X t7Rh5r+tPwEAAP//AwBQSwMEFAAGAAgAAAAhAKXWp+fAAAAANgEAAAsAAABfcmVscy8ucmVsc4SP z2rDMAyH74W9g9F9UdLDGCV2L6WQQy+jfQDhKH9oIhvbG+vbT8cGCrsIhKTv96k9/q6L+eGU5yAW mqoGw+JDP8to4XY9v3+CyYWkpyUIW3hwhqN727VfvFDRozzNMRulSLYwlRIPiNlPvFKuQmTRyRDS SkXbNGIkf6eRcV/XH5ieGeA2TNP1FlLXN2Cuj6jJ/7PDMMyeT8F/ryzlRQRuN5RMaeRioagv41O9 kKhlqtQe0LW4+db9AQAA//8DAFBLAwQUAAYACAAAACEAa3mWFoMAAACKAAAAHAAAAHRoZW1lL3Ro ZW1lL3RoZW1lTWFuYWdlci54bWwMzE0KwyAQQOF9oXeQ2TdjuyhFYrLLrrv2AEOcGkHHoNKf29fl 44M3zt8U1ZtLDVksnAcNimXNLoi38Hwspxuo2kgcxSxs4ccV5ul4GMm0jRPfSchzUX0j1ZCFrbXd INa1K9Uh7yzdXrkkaj2LR1fo0/cp4kXrKyYKAjj9AQAA//8DAFBLAwQUAAYACAAAACEAlrWt4pYG AABQGwAAFgAAAHRoZW1lL3RoZW1lL3RoZW1lMS54bWzsWU9v2zYUvw/YdyB0b2MndhoHdYrYsZst TRvEboceaYmW2FCiQNJJfRva44ABw7phhxXYbYdhW4EW2KX7NNk6bB3Qr7BHUpLFWF6SNtiKrT4k Evnj+/8eH6mr1+7HDB0SISlP2l79cs1DJPF5QJOw7d0e9i+teUgqnASY8YS0vSmR3rWN99+7itdV RGKCYH0i13Hbi5RK15eWpA/DWF7mKUlgbsxFjBW8inApEPgI6MZsablWW12KMU08lOAYyN4aj6lP 0FCT9DZy4j0Gr4mSesBnYqBJE2eFwQYHdY2QU9llAh1i1vaAT8CPhuS+8hDDUsFE26uZn7e0cXUJ r2eLmFqwtrSub37ZumxBcLBseIpwVDCt9xutK1sFfQNgah7X6/W6vXpBzwCw74OmVpYyzUZ/rd7J aZZA9nGedrfWrDVcfIn+ypzMrU6n02xlsliiBmQfG3P4tdpqY3PZwRuQxTfn8I3OZre76uANyOJX 5/D9K63Vhos3oIjR5GAOrR3a72fUC8iYs+1K+BrA12oZfIaCaCiiS7MY80QtirUY3+OiDwANZFjR BKlpSsbYhyju4ngkKNYM8DrBpRk75Mu5Ic0LSV/QVLW9D1MMGTGj9+r596+eP0XHD54dP/jp+OHD 4wc/WkLOqm2chOVVL7/97M/HH6M/nn7z8tEX1XhZxv/6wye//Px5NRDSZybOiy+f/PbsyYuvPv39 u0cV8E2BR2X4kMZEopvkCO3zGBQzVnElJyNxvhXDCNPyis0klDjBmksF/Z6KHPTNKWaZdxw5OsS1 4B0B5aMKeH1yzxF4EImJohWcd6LYAe5yzjpcVFphR/MqmXk4ScJq5mJSxu1jfFjFu4sTx7+9SQp1 Mw9LR/FuRBwx9xhOFA5JQhTSc/yAkArt7lLq2HWX+oJLPlboLkUdTCtNMqQjJ5pmi7ZpDH6ZVukM /nZss3sHdTir0nqLHLpIyArMKoQfEuaY8TqeKBxXkRzimJUNfgOrqErIwVT4ZVxPKvB0SBhHvYBI WbXmlgB9S07fwVCxKt2+y6axixSKHlTRvIE5LyO3+EE3wnFahR3QJCpjP5AHEKIY7XFVBd/lbobo d/ADTha6+w4ljrtPrwa3aeiINAsQPTMR2pdQqp0KHNPk78oxo1CPbQxcXDmGAvji68cVkfW2FuJN 2JOqMmH7RPldhDtZdLtcBPTtr7lbeJLsEQjz+Y3nXcl9V3K9/3zJXZTPZy20s9oKZVf3DbYpNi1y vLBDHlPGBmrKyA1pmmQJ+0TQh0G9zpwOSXFiSiN4zOq6gwsFNmuQ4OojqqJBhFNosOueJhLKjHQo UcolHOzMcCVtjYcmXdljYVMfGGw9kFjt8sAOr+jh/FxQkDG7TWgOnzmjFU3grMxWrmREQe3XYVbX Qp2ZW92IZkqdw61QGXw4rxoMFtaEBgRB2wJWXoXzuWYNBxPMSKDtbvfe3C3GCxfpIhnhgGQ+0nrP +6hunJTHirkJgNip8JE+5J1itRK3lib7BtzO4qQyu8YCdrn33sRLeQTPvKTz9kQ6sqScnCxBR22v 1VxuesjHadsbw5kWHuMUvC51z4dZCBdDvhI27E9NZpPlM2+2csXcJKjDNYW1+5zCTh1IhVRbWEY2 NMxUFgIs0Zys/MtNMOtFKWAj/TWkWFmDYPjXpAA7uq4l4zHxVdnZpRFtO/ualVI+UUQMouAIjdhE 7GNwvw5V0CegEq4mTEXQL3CPpq1tptzinCVd+fbK4Ow4ZmmEs3KrUzTPZAs3eVzIYN5K4oFulbIb 5c6vikn5C1KlHMb/M1X0fgI3BSuB9oAP17gCI52vbY8LFXGoQmlE/b6AxsHUDogWuIuFaQgquEw2 /wU51P9tzlkaJq3hwKf2aYgEhf1IRYKQPShLJvpOIVbP9i5LkmWETESVxJWpFXtEDgkb6hq4qvd2 D0UQ6qaaZGXA4E7Gn/ueZdAo1E1OOd+cGlLsvTYH/unOxyYzKOXWYdPQ5PYvRKzYVe16szzfe8uK 6IlZm9XIswKYlbaCVpb2rynCObdaW7HmNF5u5sKBF+c1hsGiIUrhvgfpP7D/UeEz+2VCb6hDvg+1 FcGHBk0Mwgai+pJtPJAukHZwBI2THbTBpElZ02atk7ZavllfcKdb8D1hbC3ZWfx9TmMXzZnLzsnF izR2ZmHH1nZsoanBsydTFIbG+UHGOMZ80ip/deKje+DoLbjfnzAlTTDBNyWBofUcmDyA5LcczdKN vwAAAP//AwBQSwMEFAAGAAgAAAAhAA3RkJ+2AAAAGwEAACcAAAB0aGVtZS90aGVtZS9fcmVscy90 aGVtZU1hbmFnZXIueG1sLnJlbHOEj00KwjAUhPeCdwhvb9O6EJEm3YjQrdQDhOQ1DTY/JFHs7Q2u LAguh2G+mWm7l53JE2My3jFoqhoIOumVcZrBbbjsjkBSFk6J2TtksGCCjm837RVnkUsoTSYkUigu MZhyDidKk5zQilT5gK44o49W5CKjpkHIu9BI93V9oPGbAXzFJL1iEHvVABmWUJr/s/04GolnLx8W Xf5RQXPZhQUoosbM4CObqkwEylu6usTfAAAA//8DAFBLAQItABQABgAIAAAAIQCCirwT+gAAABwC AAATAAAAAAAAAAAAAAAAAAAAAABbQ29udGVudF9UeXBlc10ueG1sUEsBAi0AFAAGAAgAAAAhAKXW p+fAAAAANgEAAAsAAAAAAAAAAAAAAAAAKwEAAF9yZWxzLy5yZWxzUEsBAi0AFAAGAAgAAAAhAGt5 lhaDAAAAigAAABwAAAAAAAAAAAAAAAAAFAIAAHRoZW1lL3RoZW1lL3RoZW1lTWFuYWdlci54bWxQ SwECLQAUAAYACAAAACEAlrWt4pYGAABQGwAAFgAAAAAAAAAAAAAAAADRAgAAdGhlbWUvdGhlbWUv dGhlbWUxLnhtbFBLAQItABQABgAIAAAAIQAN0ZCftgAAABsBAAAnAAAAAAAAAAAAAAAAAJsJAAB0 aGVtZS90aGVtZS9fcmVscy90aGVtZU1hbmFnZXIueG1sLnJlbHNQSwUGAAAAAAUABQBdAQAAlgoA AAAA ------=_NextPart_01C804F5.D4B24290 Content-Location: file:///C:/E67C29E3/CHAPTERVI-C_files/colorschememapping.xml Content-Transfer-Encoding: quoted-printable Content-Type: text/xml ------=_NextPart_01C804F5.D4B24290 Content-Location: file:///C:/E67C29E3/CHAPTERVI-C_files/header.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii"





CHAPTER VI=

APPENDIX “CR= 21;

THE INCIDENT COMMAND SYSTEM

REVISED - SEPTEMBER 2= 005

------=_NextPart_01C804F5.D4B24290 Content-Location: file:///C:/E67C29E3/CHAPTERVI-C_files/filelist.xml Content-Transfer-Encoding: quoted-printable Content-Type: text/xml; charset="utf-8" ------=_NextPart_01C804F5.D4B24290--