# UCR Guidelines -- Management of Type 3 Command [May 2007]{.underline}

**All Type III Incidents**

-   UCR Type 3 Incident Management Teams (Wilmore and Phillips) will be
    utilized for all type 3 incidents during established rotations
    starting May 27^th^ through September 15^th^.

```{=html}
<!-- -->
```
-   When our local teams are not available an ICT3 with team members
    will be ordered and filled for all Type 3 incidents using UCR Type 3
    Cadre list.

-   Additionally the following guidelines will be used for all local Ad
    hoc Type 3 Teams ordered by UCR Management through GJ dispatch.

**Single Jurisdiction Incidents (primarily Federal jurisdiction)**

-   Smokejumpers, non-local resources and/or qualified cooperator
    personnel may act in the capacity of Type 3 Incident Commander
    (ICT3) based on their qualifications as the incident transitions
    into extended attack.

**Multi-jurisdictional Incidents (Federal, State and/or local
cooperator)**

-   On multi-jurisdictional incidents, a member of the UCR Type 3 Cadre
    (ICT3) list will replace and mentor a smokejumper or other non-local
    resource within one operational period following the initial
    incident response if the incident involves private land in addition
    to one or more Federal jurisdictions.

-   In the interim, the Zone Fire Management Officer or designee will
    act in the capacity as incident liaison officer (LOFR) between the
    Incident Commander and local partners/jurisdictions to ensure proper
    consideration is given to local politics, socio-economic concerns
    and management direction provided by Federal Line Officers and local
    elected officials.

-   Unified command (as applied locally) will have one incident
    commander (ICT3) who receives direction and objectives from a group
    of representatives (agency administrators) from affected
    jurisdiction(s).

**Type 3 Incident Command**

-   Type 3 Incident Commanders (ICT3s) will be qualified according to
    the *310-1*.

***FS -** Refer to FSM 5109.17 for Additional standards.*

-   ICT3s are required to manage the incident. They must not have
    concurrent

> responsibilities that are not associated with the incident, and they
> must not

concurrently perform single resource boss duties. It is important to
note that not

all Type 3 complexity incidents require a full complement of individuals
at the

command and general staff positions.

-   A Type 3 Incident Commander (ICT3) is expected to exercise their
    authority and establish the appropriate organizational structure for
    each incident based on complexity and span of control.

-   As an incident escalates, a continuing assessment of the complexity
    level should

be completed to validate the continued ICT3 effort or the need for a
higher level

of incident management.

The following chart illustrates the minimum qualifications required for
individuals performing Type 3 complexity functions.

+------------------+---------------------------------------------------+
| **Type 3         | **Specific 310-1 or equivalent qualification      |
| Functional**     | standards required to perform ICS functions at    |
|                  | Type 3 level**                                    |
| **               |                                                   |
| Responsibility** |                                                   |
+------------------+---------------------------------------------------+
| Incident Command | Incident Commander Type 3                         |
+------------------+---------------------------------------------------+
| Safety           | Line Safety Officer                               |
+------------------+---------------------------------------------------+
| Operation        | Strike Team Leader or Task Force Leader           |
+------------------+---------------------------------------------------+
| Division         | Single Resource Boss                              |
+------------------+---------------------------------------------------+
| Plans            | Local entities can establish level of skill to    |
|                  | perform function                                  |
+------------------+---------------------------------------------------+
| Logistics        | Local entities can establish level of skill to    |
|                  | perform function                                  |
+------------------+---------------------------------------------------+
| Information      | Local entities can establish level of skill to    |
|                  | perform function                                  |
+------------------+---------------------------------------------------+
| Finance          | Local entities can establish level of skill to    |
|                  | perform function                                  |
+------------------+---------------------------------------------------+

> **Note**: Type 3 experience that is input into the Incident
> Qualification and Certification System (IQCS) will not exceed an
> individual's current Red Card qualifications.

**Type 3 Incident Characteristics**

-   Ad hoc or pre-established Type 3 organization managed by a Type 3

Incident Commander.

-   The IC develops the organizational structure necessary to manage the

incident. Some or all of ICS functional areas are activated, usually at
the

division/group supervisor and/or unit leader level.

-   The Incident Complexity Analysis process is formalized and certified
    daily

> with the jurisdictional agency. It is the IC's responsibility to
> continually

reassess the complexity level of the incident. When the complexity

analysis indicates a higher complexity level the IC must ensure that

suppression operations remain within the scope and capability of the

> existing organization, and that span of control is consistent with
> established ICS standards.

-   Local and non-local resources used.

-   Resources vary from several resources to several task forces/strike
    teams.

-   May be divided into divisions.

-   May require staging areas and incident base.

-   May involve low complexity aviation operations.

-   May involve multiple operational periods prior to control, which may
    require a written Incident Action Plan (IAP).

-   Documented operational briefings will occur for all incoming
    resources

> and before each operational period. Refer to the *Incident Response
> Pocket*

*Guide* for a briefing checklist.

-   Type 3 IC will not serve concurrently as a single resource boss or
    have any

non incident related responsibilities.

**Position Certification**

-   Command and General staff positions may be filled with individuals
    qualified at a higher level in accordance with FSH 5109.17 or PMS
    310-1 standards as applicable to agency jurisdiction.

-   Resource orders will be processed as soon as possible to fill
    existing vacancies on the Command and General staff or to replace
    individuals with other qualified individuals at a higher level as
    appropriate to provide safe and effective management of the
    incident.

-   The Zone Fire Management Officer and Zone Assistant Fire Management
    Officer should not fill the Incident Commander or other Command and
    General Staff positions concurrently. One or both of these positions
    must retain oversight and supervision responsibilities at the zone
    level during the incident.

-   If the local Unit (UCR) is unable to field the Operations or Safety
    position within one operational period of the incident being
    classified as a Type III incident, Unit Fire Managers will resource
    order these positions or a complete Type III Incident Management
    Team or equivalent to assume incident management responsibilities.

-   Planning, Logistics, Finance Section Chief: Many cooperator
    personnel in management positions within their own jurisdiction can
    redeem the responsibilities of the position if individuals qualified
    at the Unit Leader (Resource or Situation) are not available from
    the UCR Type III Incident Management Cadre. The Zone FMO may name
    request these individuals based on the availability of the
    individual.

-   Information Officer: Many cooperators (County Sheriff's) have public
    affair officers that can function effectively in the capacity as
    IOF3 while not possessing NWCG qualifications. For
    multi-jurisdictional incidents, the need generally exists for more
    than one information officer. The incident commander or
    representatives of affected jurisdictions will designate the 'lead'
    information officer as incident needs dictate.

**Use of Individuals Paid under the AD Pay Plan**

-   Individuals (retirees, cooperators, etc) who are currently certified
    or who have maintained currency in a position listed in the matrix
    on page 2 may be utilized on a name request basis to fill positions
    on the command and general staff with the exception of Type 3
    incident commander (ICT3).

-   Type 3 Incident Commanders (ICT3) may not be filled by a retiree.
    UCR staff members and local cooperator personnel who are IQCS
    certified as ICT3 and identified on the Type 3 Incident Management
    cadre can be utilized. Type 3 incident commanders from outside the
    UCR will be certified to applicable agency standards and current in
    the position.

-   As noted on the preceding matrix of positions, individuals with
    proven expertise and ability to act in the capacity of Type 3 Plans,
    Logistics, Information and Finance Section Chief may be assigned
    without meeting prerequisite training and/or certification.

-   Individuals will be assigned and paid on the basis of the applicable
    AD pay rate based on the position requested on a resource order as
    identified in the current Interagency Incident Business Management
    Handbook. For example, the equivalent position for a Type 3
    Logistics Section Chief is a base camp manager as noted on the
    matrix on the preceding page. The pay rate for this position is an
    AD-4.

-   The incident commander is not authorized to pay or negotiate a
    higher pay rate than that associated with the position(s) identified
    in the matrix above or the preceding example irrespective of the
    qualifications of the incumbent.

**Use of Trainees**

-   Trainees from agencies participating in the UCR will be requested
    and utilized whenever possible to provide cost effective on-the-job
    training in the local area. In addition to Type 3 Incident
    Commander, trainees should be requested for command and general
    staff positions as well as other positions as appropriate. The
    current UCR Type 3 Incident Management Cadre lists trainees for a
    variety of positions that may be considered.

-   The incident commander (or designee) is responsible to ensure that
    taskbook entries and performance ratings are completed as
    appropriate for all trainees assigned to the incident.

**Use of Cooperator Personnel**

-   Several local cooperating agencies are developing their own all risk
    Type 3 Incident Management and All Risk Teams. It would be
    beneficial to invite individual cooperator personnel and/or
    representatives of their incident management teams to 'shadow' fully
    qualified individuals assigned as members of the command and general
    staff.

-   The agency administrator(s) have made the determination during 2007
    AOP meetings that salary, travel and per diem costs associated with
    individuals engaged in shadow assignments will be charged to the
    incident. Allowing trainees in shadow positions should be discussed
    with representatives from all agencies and jurisdictions while
    preparing Delegations of Authorities and Cost Sharing Agreements and
    documented in writing to avoid accounting misunderstandings. Caution
    should be used to ensure that excess costs for trainees charged to
    UCR incidents meets local unit objectives.

**UCR Type 3 Team ordering protocols**

-   GJC will notify the IC up on rotation that his team is being
    ordered. Pertinent information will be given including incident
    name, contact phone numbers, incident location, fire size etc.etc..
    A predetermined meeting location should always be determined by
    agency officials ordering the team. Incident information will be
    necessary for all team members being called out in order to arrange
    travel and for GJC to estimate time of arrival to incident for
    ordering officials.

-   Incident Commanders or designee will provide GJC an updated roster
    with any changes of personnel bi-weekly prior to start of rotation.
    GJC will start calling primary team members off the roster provided
    by IC for as soon as possible.

**UCR Type 3 Team Rotation**

  ----------------------- ----------------------------- ------------------
  **Wilmore's T-3 Team**  **May 27^th^ - June 9^th^**   

  **Phillips T-3 Team**   **June 10^th^ - June 23^rd^** 

  **Wilmore's T-3 Team**  **June 24^th\ -^ July 7^th^** 

  **Phillips T-3 Team**   **July 8^th^ - July 21^st^**  

  **Wilmore's T-3 Team**  **July 22^nd^ -- August       
                          4^th^**                       

  **Phillips T-3 Team**   **August 5^th^ -- August      
                          18th**                        

  **Wilmore's T-3 Team**  **August 19^th^ -- September  
                          1^st^**                       

  **Phillips T-3 Team**   **September 2^nd^ --          
                          September 15th**              
  ----------------------- ----------------------------- ------------------

**Note:** If Wilmore's Team is committed during their designated
rotational period and we break another incident, Phillips Team will be
notified even if it's outside established team rotational periods. Due
to general shortages in team alternates Phillips team may not be
available (team members fishing, camping etc.etc.) If Phillips can't put
together his team dispatch will utilize the UCR Type 3 Cadre list or
order an established team through ROSS.

**2007 UCR Type 3 Team Rosters**

**[Team A]{.underline}** Phillips

  ------------------------- ------------- -------- ------------- -----------
  Type 3 Positions          **Primary**            **Trainee**   

  **INCIDENT COMMANDER**    Jeff Phillips UCR                    

  **SAFETY OFFICER**                               Rick Smith    PV-FPD

  **PUBLIC INFORMATION                             Susan Douglas Vail PD
  OFFICER**                                                      

  **PLANNING SECTION        Kimberly      Mesa     James Cooper  BLM GJFO
  CHIEF**                   Bullen        County                 

  **OPERATIONS SECTION      Doug Paul     UCR      Angie Foster  UCR
  CHIEF**                                                        

  **LOGISTICS SECTION       Nicholas      UCR      Matt McGrath  BLM-MCNCA
  CHIEF**                   Collard                              

  **FINANCE SECTION CHIEF** Valerie Saiz  UCR                    

  **DIVISION SUPERVISOR**   Randy Jacks   UCR                    

  **DIVISION SUPERVISOR**   Mike Ottosen  UCR                    

  **STRUCTURE PROTECTION    Frank         LV-FPD                 
  SPECIALIST**              Cavaliere                            

                                                                 

                                                                 

                                                                 
  ------------------------- ------------- -------- ------------- -----------

**Team B [Wilmore]{.underline}**

+------------------------+-------------+-------+----------+----------+
| Type 3 Positions       | **Primary** |       | **T      |          |
|                        |             |       | rainee** |          |
+------------------------+-------------+-------+----------+----------+
| **INCIDENT COMMANDER** | Ross        | UCR   |          |          |
|                        | Wilmore     |       |          |          |
+------------------------+-------------+-------+----------+----------+
| **SAFETY OFFICER**     | Bill        | UCR   | Gary     | UCR      |
|                        | Johnson     |       | Helming  |          |
+------------------------+-------------+-------+----------+----------+
| **PUBLIC INFORMATION   |             |       | Eric     | Eagle    |
| OFFICER**              |             |       | Lovgren  | County   |
+------------------------+-------------+-------+----------+----------+
| **PLANNING SECTION     | Barry Smith | Eagle | Darryl   | Aspen FD |
| CHIEF**                |             | C     | Grob     |          |
|                        |             | ounty |          |          |
+------------------------+-------------+-------+----------+----------+
| **OPERATIONS SECTION   | Tommy Hayes | UCR   |          |          |
| CHIEF**                |             |       |          |          |
+------------------------+-------------+-------+----------+----------+
| **LOGISTICS SECTION    | Scott       | B     | Robert   | Burning  |
| CHIEF**                | Thompson    | asalt | Thrower  | Mtn FPD  |
|                        |             | FD    |          |          |
+------------------------+-------------+-------+----------+----------+
| **FINANCE SECTION      | Jennifer L. | WR    |          |          |
| CHIEF**                | Jones       | F-RRD |          |          |
+------------------------+-------------+-------+----------+----------+
| **DIVISION             | Mark        | UCR   |          |          |
| SUPERVISOR**           | Murrell     |       |          |          |
+------------------------+-------------+-------+----------+----------+
| **DIVISION             | Ody         | UCR   |          |          |
| SUPERVISOR**           | Anderson    |       |          |          |
+------------------------+-------------+-------+----------+----------+
| **STRUCTURE PROTECTION | John Wilson | E     |          |          |
| SPECIALIST**           | job share   | R-FPD |          |          |
|                        |             |       |          |          |
|                        | Bob Struble | Stea  |          |          |
|                        |             | mboat |          |          |
|                        |             | FD    |          |          |
+------------------------+-------------+-------+----------+----------+
|                        |             |       |          |          |
+------------------------+-------------+-------+----------+----------+
|                        |             |       |          |          |
+------------------------+-------------+-------+----------+----------+
|                        |             |       |          |          |
+------------------------+-------------+-------+----------+----------+

**2007 Interagency Standards for Fire and Aviation Operations Appendix
G**

+--------------------------------------------------------+------+-----+
| #  Incident Complexity Analysis                        | **Y  | **N |
|                                                        | es** | o** |
| **Type 3, 4, 5**                                       |      |     |
+--------------------------------------------------------+------+-----+
| ## Fire Behavior                                       |      |     |
+--------------------------------------------------------+------+-----+
| ## Fuels                                               |      |     |
| extremely dry and susceptible to long-range spotting o |      |     |
| r you are currently experiencing extreme fire behavior |      |     |
+--------------------------------------------------------+------+-----+
| ## Weather forecast                                    |      |     |
| indicated no significant relief or worsening situation |      |     |
+--------------------------------------------------------+------+-----+
| ## Current or pre                                      |      |     |
| dicted fire behavior dictates indirect control strateg |      |     |
| y with large amounts of fuel within planned perimeter  |      |     |
+--------------------------------------------------------+------+-----+
| ## Firefighter Safety                                  |      |     |
+--------------------------------------------------------+------+-----+
| Performance of firefighting resources affected by      |      |     |
| cumulative fatigue                                     |      |     |
+--------------------------------------------------------+------+-----+
| ## Overhead over extended mentally and/or physically   |      |     |
+--------------------------------------------------------+------+-----+
| ## Communi                                             |      |     |
| cation ineffective with tactical resources or dispatch |      |     |
+--------------------------------------------------------+------+-----+
| ## Lack of a cohesive management structure             |      |     |
+--------------------------------------------------------+------+-----+
| ## Organization                                        |      |     |
+--------------------------------------------------------+------+-----+
| ## Operations are at the limit of span of control      |      |     |
+--------------------------------------------------------+------+-----+
| ## Incident act                                        |      |     |
| ion plans, briefings, etc., missing or poorly prepared |      |     |
+--------------------------------------------------------+------+-----+
| ## Variety of                                          |      |     |
| specialized operations, support personnel or equipment |      |     |
+--------------------------------------------------------+------+-----+
| ## Unable to properly staff air operations             |      |     |
+--------------------------------------------------------+------+-----+
| #                                                      |      |     |
| # Limited local resources available for initial attack |      |     |
+--------------------------------------------------------+------+-----+
| ## Hea                                                 |      |     |
| vy commitment of local resources to logistical support |      |     |
+--------------------------------------------------------+------+-----+
| ## Existing forces worked 24 hours without success     |      |     |
+--------------------------------------------------------+------+-----+
| ##                                                     |      |     |
| Resources unfamiliar with local conditions and tactics |      |     |
+--------------------------------------------------------+------+-----+
| ## Values to be Protected                              |      |     |
+--------------------------------------------------------+------+-----+
| ## Urban interface, structures, developments,          |      |     |
|  recreational facilities, or potential for evacuation  |      |     |
+--------------------------------------------------------+------+-----+
| ## Fire burning or threatening more                    |      |     |
|  than one jurisdiction and potential for unified comma |      |     |
| nd with different or conflicting management objectives |      |     |
+--------------------------------------------------------+------+-----+
| ## Unique natural re                                   |      |     |
| sources, special-designation areas, critical municipal |      |     |
|  watershed, T&E species habitat, cultural value sites  |      |     |
+--------------------------------------------------------+------+-----+
| ## Sensitive political con                             |      |     |
| cerns, media involvement, or controversial fire policy |      |     |
+--------------------------------------------------------+------+-----+
| ## Total Number of Elements Checked                    |      |     |
+--------------------------------------------------------+------+-----+

If you have checked "yes" on 3 to 5 of the analysis boxes, consider
requesting the next level of incident management support.

Prepared by:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date: \_\_\_\_\_\_\_\_\_\_\_ Time: \_\_\_\_\_\_\_\_

Reviewed by:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date: \_\_\_\_\_\_\_\_\_\_\_ Time: \_\_\_\_\_\_\_\_