National Dispatch Efficiency Working Group

Interagency Standards for Resource 

Ordering Guide (ISROG)

Standard Business Practices for Using IROC Portal within the 

Interagency Dispatch Community

March 24, 2023
Interagency Standards for Resource Ordering Guide (ISROG)

March 24, 2023

Page 1

Table of Contents

Contents

Table of Contents............................................................................................................................ 1

Incident Action Tile ........................................................................................................................ 2

Incident Details Screen ................................................................................................................... 5

Pending Request Tile ...................................................................................................................... 6

Create New Request Screen............................................................................................................ 6

Manage Request Screen.................................................................................................................. 9

Request Status Action Tile............................................................................................................ 12

Resources Action Tile................................................................................................................... 12

Resource Status Screen................................................................................................................. 12

Resource Item Screen ................................................................................................................... 12

Roster Screen ................................................................................................................................ 13
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 2 

Note: The following standard business practices are only for the IROC Portal

Incident Action Tile

Create New Incident

IRWIN to IROC Interface. Basic incident header information, including Incident Name, 

Initial date/time, Incident Number, Incident Type, Description, Office Reference, Location, 

Dispatch, Protecting Unit, Billing Unit, and Default Cache can now be added to IROC from 

some Authoritative Data Sources; i.e., CAD systems, FireCode, etc. through an interface 

with IRWIN. When an incident’s basic header information is added to IROC in this fashion, 

the Authoritative Data Source system of record, and any changes to the data fields described 

above must be edited in the Authoritative Data Source. 

Incident Type. There are many types of incidents. Select the appropriate type of incident. 

Incident types that are described below have standardized uses. The following is a link to 

incident types and definitions according to NWCG: 

https://www.nwcg.gov/sites/default/files/data-standards/stds/values.pdf

https://www.nwcg.gov/sites/default/files/data-standards/pdf/business-rules.pdf

- “Incident/Event Support” - will be selected when requesting resources to work directly 

for the host agency responsible for supporting an actual incident. An event dealing with 

effective and timely support by the wildland fire community of an Event Host's dispatch 

unit, in order to relieve the dispatch unit of increased business volume due to anticipated 

or existing wildland fire or event activity. This category includes activities such as 

expansion of the existing Incident Support Organizations (ISO), such as initiating 

Expanded Dispatch operations, expanding Technical Support (such as establishment of 

contract-resource inspection stations), Multiagency Coordinating Group (MAC Group) 

support, and expanding administrative support (such as support of bill-payment centers)

- “Preparedness/Preposition” - will be selected when requesting resources that, once 

arrived, will be available for wildfire reassignments during the commitment duration. An

event dealing with effective and efficient response by the wildland fire community to 

planned, anticipated or event activity. This category includes activities such as move-up 

and cover, fire menace standby, and severity activities.

 

- “Out of Area Response” – An event where resources are mobilized to a Wildfire (WF) 

Event within their corresponding dispatch Center’s response area (boundary). When 

resources arrive on scene, it is determined the ignition is not within their area of response, 

but in fact plots within an adjacent dispatch center’s response area (boundary)

- “Training – Classroom,” “OJT,” “Proficiency,” and “Simulation”. A scheduled activity 

that provides instruction so as to make attendees fit, qualified, or proficient in a particular 

area. This is a planned event. Requests for NIRSC radio items in support of these 

incidents will be placed through NICC. NICC will not process overhead resource orders 

for training unless it is required for an AD hire, or for a unique situation (agency approval 
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 3 

required). See chapter 10 of the National Mobilization Guide for information on training 

incidents and planned events. https://www.nifc.gov/nicc/mobguide/Chapter_10.pdf .

Incident Name. Incidents established in IROC should be appropriately named. When left 

blank, the incident name will default to the incident number. It is recommended to 

appropriately name each incident before placing requests outside of the local host agency 

and/or the ordering unit jurisdiction. Below are recommendations and examples for naming 

incidents within IROC. See Chapter 70 of the National Mobilization Guide for information 

on Incident Naming Protocols. https://www.nifc.gov/nicc/mobguide/Chapter_70.pdf

When naming a “Fire - Wildfire” incident within IROC, it is recommended that a local 

geographic feature be included within the incident name. There is no requirement to include

the word “Fire” within the incident name.

Example: Naming a “Fire - Wildfire” incident; the Vale District located in Oregon (ORVAD) requires crews for a fire near Castle Rock. Utilize the category “Fire - Wildfire” 

for the incident type and by following the recommended incident naming convention, an 

appropriate name may be Castle Rock. 

When naming other types of incidents that are available within IROC such as “Flooding” 

or “Hurricane/Typhoon” or “Fire – Prescribed”, it is recommended to use the event or 

activities pre-existing name if established within the incident name created within IROC. A 

Prescribe Fire record will have RX in the naming convention. 

 

Example: Naming a “Flooding” incident; the Fairbanks Area Forestry office in Alaska 

(AK-FAS) requires a hand crew for the placement of sandbags along the Tanana River. 

Utilize the category “Flooding” for the incident type and when adhering to the 

recommended incident naming convention, an appropriate name may be Tanana River 

Flood – January 2021. 

When naming an “Incident/Event Support” incident within IROC, the incident name 

should include the word “Support” in the incident name when ordering resources that are 

mobilized in response to an agency’s approved severity request. If a specific incident is 

being supported, the incident name would also be included. 

Example #1: Naming an “Incident/Event Support” incident; the Boise Interagency 

Dispatch Center located in Idaho (ID-BDC) requires additional dispatch personnel to help 

with predicted high-volume fire activity. Utilize the category “Incident/Event Support” 

for the incident type and when adhering to the recommended incident naming 

convention, an appropriate incident name may be BDC Dispatch Support 

Example #2: Naming an “Incident/Event Support” incident; the fire cache managed by 

the Boise National Forest located in Idaho (ID-BOF) requires a forklift to assist with the 

large volume of fire supplies being ordered by the Lowman fire. Utilize the category 

“Incident/Event Support” for the incident type and when adhering to the recommended 
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 4 

incident naming convention, an appropriate incident name may be Lowman – Cache 

Support. 

Example #3: Naming an “Incident/Event Support” incident associated with a local 

centers’ use of GACC support code; the Southern Area Coordination Center located in 

Georgia (GA-SAC) asks the Tennessee Interagency Coordination Center (TN-TNCC) to 

host a Type 1 Airtanker on the GACC support . Utilize the category “Incident/Event 

Support” for the incident type and when adhering to the recommended incident naming 

convention, an appropriate incident name may be SACC Support - TN. 

When naming “Preparedness/Preposition” incidents within IROC, the incident name 

should include either the word “preparedness”, “preposition”, “support” or “severity”. 

Example #1: Naming a “Preparedness/Preposition” incident; the Boise National Forest in 

Idaho (ID-BOF) requires additional engines be located throughout the forest for a 

predicted high volume of new fires. Utilize the category “Preposition/Preparedness” for 

the incident type and when adhering to the recommended incident naming convention, an 

appropriate incident name may be 2023 BOF IA Preposition. 

Example #2: Naming a “Preparedness/Preposition” incident; the Mendocino National 

Forest in California (CA-MNF) requires a Type 1 helicopter and associated personnel to 

be located at the forest helibase for a predicted high volume of new fires. Utilize the 

category “Preposition/Preparedness” for the incident type and when adhering to the 

recommended incident naming convention, an appropriate incident name may be 

Mendocino July Aviation Severity. 

Example #3: Naming a “Preparedness/Preposition” incident; the USFS Region 8 in 

Georgia (GA-R08) requires additional crews throughout the Appalachian Mountains 

forests for predicted high fire danger. Utilize the category “Preposition/Preparedness” for 

the incident type and when adhering to the recommended incident naming convention, an 

appropriate incident name may be Region 8 Support. 

Protecting Unit. Identify the Protecting Unit by responsible/jurisdictional agency. The 

Protecting Unit is the agency that provides the primary financial code for payment of requested 

resources and/or the agency that generates the need for requesting the resources. 

Location Name. IROC defaults to incident number and this displays on the printed resource 

order. You may type up to 50 characters of additional information. 

Enter Coordinates. Ensure latitude and longitude (DMS) are entered accurately, and that they 

represent the actual location of the incident. If an accurate latitude and longitude are not known 

at the time of incident creation, coordinates for the nearest known location to the incident should 

be entered. Coordinates should be updated once the accurate latitude and longitude is 

determined.

Financial Code. Locate the host agency financial code. If using more than one financial code 

from the same agency, identify the primary code by selecting the default button. In certain 
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 5 

instances, more than one agency may have financial codes included. An active incident default

financial code must be selected in order for requests for NFES supply items to be accepted by 

ICBSR through the IROC-ICBSR interface. If a financial code becomes invalid, the financial 

code should be deleted. DO NOT mix financial codes that are not similar in intent (the financial 

code should match the incident type). All Forest Service financial codes require an associated 

override code. Note that four-character fire codes created in the FireCode system can be 

imported to IROC through IRWIN. See chapter 70 of the National Mobilization Guide for 

information on Agency specific cost coding for incidents. 

https://www.nifc.gov/nicc/mobguide/Chapter_70.pdf

- Severity, Suppression, FEMA Financial Codes. - When an agency has assigned a 

financial code to an incident resource order with the intent of obligating suppression 

funds (FireCode), severity funds, Federal Emergency Management Agency (FEMA) 

disaster funds, or similar funding sources, DO NOT assign an additional financial code 

that obligates an agency’s budgeted or allocated funds (hard dollars), instead create a 

new incident. 

- Agency Budget, Allocated, Hard Dollar Codes. When an agency has assigned a 

financial code to a resource order with the intent of obligating budgeted (hard dollars) 

or allocated funding, DO NOT permit an additional financial code that obligates 

suppression funds, severity funds, Federal Emergency Management Agency (FEMA) 

disaster funds, or similar funding sources, instead create a new incident. 

Radio Frequencies. 

See Frequencies under Incident Details Screen section.

Complex. A Complex Incident shall be created in a CAD system or ICS209. The complex 

incident then can be added into IROC from the IRWIN interface.

Incident Details Screen

NOTE “IRWIN to IROC Interface”: Any changes to incident’s basic header information 

data fields must be edited in the Authoritative Data Source, i.e. CAD, FireCode, etc.

Contacts Information. Enter new contact information specific to the incident under the 

Contacts Information accordion view. All contacts categorized “Block 8” located within the 

Contacts Information accordion view will be displayed on a printed resource order within the 

Incident Base / Phone Number field. Delete or recategorize any contacts that should not be 

displayed on a printed resource order. 

For example, the host agency creates an expanded dispatch organization for an incident, a 

new contact name with the appropriate phone number including area code (Arbuckle 

Expanded 999-999-9999) will be created within the Contacts Information accordion view 

and all old contact information is deleted or recategorized. The expanded dispatch contact 
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 6 

will be used until the expanded organization is released. When expanded is released, the 

contact should be deleted and the normal contact name and phone number (Arbuckle 

Dispatch) and telephone number must be re-created for the duration of the incident. 

Financial Code Information. If you have filled a request and as part of this activity must 

assign a specific agency financial code, or are in need of a financial code, you may contact 

the ordering office through established ordering channels and request them to enter the 

financial code in IROC. Alternately, you may utilize the “Add New Financial Code” 

function from the manage request screen to enter your agency specific financial code (see 

Manage Request Screen). In this case you must document your actions, and you should 

contact the ordering office to inform them of the change. 

Frequencies Information. Identify and select frequencies before ordering the resource that 

needs them. Identify and select both air-to-air and air-to-ground frequencies before placing 

Aircraft orders. 

When frequencies are added or removed from an incident, you must update and revise this 

information immediately. Large incidents will identify frequencies within the Incident 

Action Plan (IAP). It is recommended that the dispatch unit supporting a large fire maintain 

current frequency information by utilizing the IAP. Delete any frequencies that should not 

be displayed on a printed resource order. 

Organization. Dispatch centers cannot be the billing organization. The billing organization 

needs to be a single agency that is has fiscal responsibility for the incident.

Airports. Use this screen to add airports. These airports will populate the jetport section on 

the pending request screen. 

Request Blocks. This screen identifies the various request blocks associated with the 

incident. Check with dispatch management before using request blocks as there may be local 

protocols to follow. 

Shipping Addresses. This screen can be used to add shipping addresses to the incident. 

Please ensure that the full address, including zip code is added. 

Documentation Interface Icon. Enter any important documentation pertaining specific to 

the incident. 

Pending Request Tile

Create New Request Screen

Financial Code. Select the appropriate Financial Code for the request. The Financial Code 

must be entered before the new request is created; it must not be left blank.
Interagency Standards for Resource Ordering Guide (ISROG)

March 24, 2023

Page 7

Need Date/Time. Enter the appropriate Need Date/Time the resource is needed. The Need 

Date/Time must be entered before the new request is created; it must not be left blank. 

Prior to placing requests, verify that the Need Date/Time is realistic and, if needed, revise the 

date and time.

NICC will not process “after-the-fact” new requests for resources that have been selfdispatched or self-mobilized to an incident. NICC will not process “after-the-fact” requests 

that are intended to provide correction to the length of commitment for a past assignment.

NICC may process “after-the-fact” requests when compelling circumstances are present, 

such as to correct an accidental release of a resource due to a IROC user error; or to follow 

up with a resource order for a resource appropriately mobilized under a neighborhood initial 

attack agreement. Prior to placing the request, the ordering unit must provide adequate 

documentation.

Deliver To. Select pre-identified information or create new Deliver To. Any special or 

unique reporting information related to the specific request may be included.

Navigation/Reporting Instructions. Provide detailed reporting or navigation instructions 

for incoming resources in this field. For NFES items that will be provided by a cache this 

section must contain a valid address or latitude /longitude. 

Incident Jetports. All new requests created for the incident that will be filled with non-local 

resources requiring commercial air travel must have the commercial jetport identified in the 

Incident Jetport section. 

Inclusions and Exclusions. Ensure the appropriate inclusions and exclusions are selected.

EFF/AD Exclusion: Example-An incident is unable to support an EFF/AD employee at the 

incident location. Check the “EFF/AD Exclusion” box prior to creating the new request.

Host Agency Only: Example-A non-fire US Fish and Wildlife Service incident is funded by 

the Agency only with no reimbursable funding. Select the “Host Agency Only” box prior to 

creating the new request.

Federal Only: Example-An incident to provide assistance internationally is created under a 

federal agreement that does not allow for the use of non-Federal resources. Select the 

“Federal Only” box prior to creating the new request.

Contractor Not Acceptable: Example- An incident is unable to support a Contractor at the 

incident location. Check the “Contractor Not Acceptable” box prior to creating the new 

request.

Portal to Portal Acceptable: Example- An incident can support a Portal to Portal. Check the 

“Portal to Portal Acceptable” box prior to creating the new request.
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 8 

Special Needs. Use special needs only to describe information that is not documented 

anywhere else. Identify information that is critical to the resource mobilization. 

- DO NOT identify name requests for overhead single resources in special needs. 

Name requests for overhead must be created using the “named request” function in 

the IROC Create New Request Screen or in the Manage Request Screen. 

- DO NOT enter information in the special needs field that is listed or specified in 

another IROC field. For example, do not duplicate an inclusion or exclusion in the 

special needs field.

Information identified in Special Needs:

- Only use the THSP position code when there is no other appropriate position code 

available. Use of the THSP position code (Technical Specialist) requires additional 

information be added to the Special Needs field. The ordering unit must describe the

duties to be performed by the THSP position prior to placing the request. When 

appropriate, a GACC or NICC can direct an ordering unit to correct and resubmit a 

THSP request as an appropriate Position. Example: THSP – Duty Officer. This 

individual will be serving in a role that does not have a unique Position 

Code/qualification. Therefore, THSP is the appropriate position code to use with a 

description of what they will be doing, serving as the duty officer. 

- Resource mobilization information. Identify information critical to the resource 

mobilization such as the time and physical location that an incident management team 

will receive the team in-briefing. 

- Approved items. Identify any items that must be approved in advance of 

mobilization. Select as appropriate Rental Vehicle Approved, Cell Phone Approved 

and/or Laptop Approved using the radial button. Utilize Special Needs to describe 

following approved items, e.g. Mobile Devices, agency owned vehicle (AOV) or 

privately owned vehicle (POV). 

- Required items of high importance. Identify required items such as personal 

protective equipment (PPE), tools, or lunches. Identify the off-incident location 

where a helicopter manager will meet the Call-When-Needed helicopter. Identify if 

the resource needs to be self-sufficient. List if you are willing to approve back fill for 

resources filling the request. Directions to contact IC/Duty Officer/Dispatch, etc. for 

specifics regarding mobilization. 

- Resource suggests. Include the official name as it is listed in IROC, the local unit, and 

appropriate GACC. Include the contact telephone number and identify the agency 

employment status. Any dispatch unit within the established ordering chain may fill 

the pending request with a qualified and available resource.

Named Request Only. Use the Named Request Only field when a name request is created 

for an overhead single resource. NICC will not process any “name requests” unless they are 
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 9 

appropriately created using the “name request” function in the IROC Create New Request 

Screen or in the Manage Request Screen. 

To name request a non-overhead single resource; it is appropriate to use Special Needs to add 

the name requested resource with their current dispatch unit identifier. Example: Engine 

651 (GA-CHF) or Suppression Module 21 (VA-VIC). 

Prior to placing a Name Request, the incident and ordering unit must adhere to the policy and 

associated criteria as identified within Chapter 20 of the National Interagency Mobilization 

Guide: https://www.nifc.gov/nicc/mobguide/Chapter_20.pdf 

Manage Request Screen 

Fill Tab. Set travel when filling the request.

VIPR: Use only for items procured through VIPR. (example: Dozers) 

Available: Use for filling with local, or prepositioned resources. Fill with single 

resource, master roster, configuration or start from scratch. Refer to the Roster Screen 

section for the interagency standards identifying resources that require a roster.

Refer to the GACC for area specific guidance on the following Fill Tab options: NonLocal, Preposition, Reserved, At Incident, Mob En Route, Demob En Route, Other, 

IR, Tactical, Contracts, Exclusive Use

Mode of Travel. Fill Request dialog box. Identify the mode of travel and other travel 

details. 

Support Request Tab. Support requests required for the mobilization of crews, equipment 

and overhead may be created or added by the incident dispatch, or by any unit in the ordering 

or filling chain. An overhead support request WILL NOT be created against a parent request 

that is also an overhead request, other than for local area use. 

Example: A filling unit mobilizing a DIVS to an out of area assignment will not create a 

support overhead request for a DIVS-T to accompany the qualified DIVS. A trainee request 

must be created by the incident host unit and processed through established ordering 

channels. 

NICC will not normally process support requests for equipment items required for the 

mobilization and/or demobilization of resources (e.g. Transportation, Lowboy). 

Example #1: A lowboy trailer is required to transport a Type 2 dozer. The unit filling the 

Type 2 dozer will create the support request and assign the lowboy trailer to transport the 

Type 2 dozer. If the unit filling the Type 2 dozer is unable to locate a lowboy trailer, the 

support order may be placed elsewhere. 
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 10

Example #2: A crew being mobilized to a “wildfire”; a Type 2 crew from Elko, Nevada 

requires a bus for transporting the crew to a Colorado incident. The bus should be assigned 

to a support request created by Elko Dispatch (unit filling the crew) and filled locally. The

support request will not be processed by NICC. 

Example #3: A lowboy trailer to demobilize a tractor plow from a “wildfire”; a county fire 

district in Kansas used a lowboy trailer to transport a tractor plow resource ordered to an 

incident located in Oklahoma. The lowboy returned to Kansas after delivery. During the 

assignment, the tractor plow was reassigned to multiple incidents, and as a result, the 

dispatch center for the county fire district in Kansas is unable to create a support request for 

sending the lowboy back to demob the tractor plow from its current incident assignment. 

The support request was created by the local Oklahoma dispatch unit and placed up. NICC 

will process the support request once received from the Southern Area Coordination Center; 

however, the situation should be clearly documented on the request prior to placing to NICC. 

Cache Tab. Use only when placing requests for NFES supply items. Note: DO NOT utilize 

this action when processing requests such as telecommunications items, RAWS units or other 

items that must be ordered through established ordering channels. 

Fill With Tab. 

EFF: Use only for EFF overhead resources not in IROC. These resources are only 

assigned to the individual incident and are not part of the permanent IROC database

(example: Driver).

Fill with Agreement: Use only for resources not in IROC or listed under the VIPR 

tab. These resources are only assigned to the individual incident and are not part of 

the permanent IROC database (example: Land Use Agreement). 

Fill with Local Purchase: Use only for purchasing supplies locally (example: cases 

of water purchased from Walmart). 

Fill with Override: Use only if no “Fill with” option is available. Enter complete 

documentation before completing the “Fill with Override”. 

Send Back Tab. Use only when the order was placed by mistake or the requesting unit is 

unable to retrieve the request. This feature shouldn’t be used when a request needs to be 

UTFed. 

The unit using the send back feature must contact, via telephone, the placing unit and provide 

notice that the request was sent back. 

Retrieve Tab. Use only when the order was placed by mistake or when a closer resource 

from another unit becomes available. 
Interagency Standards for Resource Ordering Guide (ISROG)

March 24, 2023

Page 11

The retrieving unit must contact, via telephone and through established ordering channels, 

the unit where the request is currently pending or waiting to be filled and provide notice that 

the request is to be retrieved. 

UTF Tab. Use when you are unable to fill a pending request from outside your dispatch 

office.

- Enter complete documentation before the request is “UTFed”.

Cancel UTF Tab. Use only when there are no available resources to fill a pending request. 

Only the incident’s designated dispatch office that created the request will utilize the “Cancel 

UTF” function. The “Cancel UTF” function will only be used after it is determined that the 

request cannot be filled. 

Cancel Tab. Use only when a pending request is no longer needed by the incident. Only the 

incident’s designated dispatch office that created the request will utilize the “Cancel” 

function. The “Cancel” function will only be used after it is determined that the incident no 

longer needs the request. 

- Enter complete documentation before the request is cancelled.

To cancel a request that has been placed to another unit the canceling unit must contact, via 

telephone, the unit where the request is currently pending or waiting to be filled and provide 

notice that the request is going to be canceled. The GACC and NICC must be notified if the 

resource being cancelled is a national resource.

To cancel an already filled request the canceling unit must contact, via telephone, the sending 

unit where the request is currently filled to communicate the cancellation of the request. The 

GACC and NICC must be notified if the resource being cancelled is a national resource.

- If the assigned resource can be contacted before travel begins, the resource will be 

unfilled, and the ordering unit will cancel the request.

- If the assigned resource has begun travel but the travel has yet to start in IROC, the 

resource will be released, or unfilled and the ordering unit will cancel the request, 

provided that the resource can be contacted. Communication is needed between the 

ordering and sending unit in this scenario. 

- If the assigned resource has begun travel in IROC, the request can be released by the 

requesting dispatch upon completion of travel or the times can be adjusted to reflect the 

actual time spent in travel status to ensure accurate documentation.

- Enter the reason for cancellation and action taken before completing the cancel request 

action.
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 12

Request Status Action Tile

This tile takes you to pages addressed in other sections of this document, such as the Manage 

Request Screen, or displays information on the status of requests. 

Resources Action Tile

Resource Status Screen

All resources should reflect current status by using the appropriate level (IMT Only, Virtual 

Only, Local, State, GACC, or National) within IROC. 

Local Resources. These may be set as available for a IMT Only, Virtual Only, Local, State, 

GACC or a National dispatch after consideration of draw-down levels or a ready reserve 

operation. 

Resources assigned to “Preposition/Preparedness” incidents. The availability status 

should be set to reflect the resources’ actual availability status. If the resource is not available 

to the GACC or Nationally set to available “local”. If not set to local, the resources host

dispatch and host GACC will still view the resource as “Available.”

Returned from Assignment. The resource must have status correctly identified as soon as 

possible. It is preferred that re-status be accomplished promptly upon return to available 

status. 

Resource Item Screen

Data Entry Standards 

To prevent the duplication of resource records please search for existing resource items and 

only create new items with the consultation of your supervisor or the GACC. 

Please see the IROC Resource Data Entry Standards document for details. 

IROC_Resource_Data_Entry_Standards_2022.pdf (nifc.gov) 

Units with hand crews will maintain a maximum of one (1) crew record for each crew. 

Dispatching units will not create a new crew record for each assignment, mobilization, or 

crew dispatch. 

Overhead Single Resources should not be added in IROC. IQCS System of Record or IQS 

System of Record are the only systems to be used when adding overhead single resources to 

IROC via the IRWIN Interface. (Calfire uses IROC as SOR for their Overhead single 

resources.) 
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 13

National Resource. The “National Resource” box should only be checked for resources 

listed as such in chapter 10, National Mobilization Guide 

https://www.nifc.gov/nicc/mobguide/Chapter_10.pdf 

Record Manager Only. The Record Manager Only check box is used to designate a tactical 

aircraft that does not have a permanent home dispatch, such as national airtankers. These 

aircraft are dispatched and statused by the office that manages their current operating base.

Classification (Aircraft, Crew or Supply), Equipment Type (Equipment), or 

Qualification (Overhead) must be populated for each resource item in order to fill requests. 

Manage Removed Resources. Removed resources should be deleted when appropriate. It 

is recommended that units review their removed resources on a regular basis. 

Roster Screen

Master Rosters. A master roster is a dedicated list of positions and personnel assigned to a 

parent catalog item that has a configuration, such as crews, overhead teams, helicopters, and 

engines. The master roster expedites the assigning of that resource to an incident request. 

“Group” parent catalog items such as IA Loads of Smokejumpers or Rappellers, Crew or 

Engine Strike Teams, Task Forces may have child catalog items that have their own 

configuration. 

• Example, a strike team of engines is a configuration made up of 1 strike team leader and 

5 engines of the same type. Each engine may have its own configuration of 1 engine and 

3 to 5 overhead resources. This configuration will not be added to the strike team roster 

until the engine is added to the strike team roster. Since the engine has its own 

configuration, users must build individual rosters for each engine. 

Rosters. The subordinate requests on rosters should be comprised of overhead position 

(except in the instance of “Group” configured catalog items). Transportation, UTVs/ATVs, 

trailers etc. should be created as support requests and not added as subordinates on the roster. 

Do not roster different catalog items under the original catalog item. 

- Example. Do not roster an engine under a crew, suppression module or fuels module. 

The engine should be a separate request.

- Example. Do not roster a chase rig under an engine, crew, suppression module or fuels 

module. The chase rig is transportation and should be a support request. 

Agency resources identified below will be configured using a roster. Foreign government 

resources mobilized through NICC are not agency and will not be configured using a roster 

when assigned. 
Interagency Standards for Resource Ordering Guide (ISROG)

March 24, 2023

Page 14

Incident Management Teams

- CIM, Type 1 and Type 2 Interagency Incident Management Teams

- National Area Command Teams

- National Incident Management Organization Teams (NIMO)

- All-Hazard Incident Management Team

Incident Support Teams

- Interagency Buying Teams

- Payment Teams 

- Burned Area Emergency Response Teams (BAER)

- National Fire Prevention and Education Teams (NFPET)

Other Overhead Groups

- Interagency Wildland Fire Modules

- Suppression Modules

- Fuels Modules

- Faller Modules

Crews

- Agency Type 1 Crews (includes hotshot crews)

- Agency Type 2 or Type 2 IA Crews (if comprised of regular agency employees)

Equipment

- Agency engines

- Agency tenders

- Agency dozers

- Agency tractor plows

Aircraft

- Aerial Supervision Modules (ASM platform)

- Lead Planes

- Agency owned Air Attack platforms and their permanently assigned flight crew

- Agency exclusive use helicopters and the permanently assigned module members

- Agency owned helicopters and the permanently assigned module members

 

Working with Subordinate requests. IROC assigns subordinate request numbers to the 

resources that are filling positions on an assignment roster for a parent request that has been 

filled with a configuration. Members of an overhead team, fire crew, exclusive use helicopter, 

engine, etc. may fill a subordinate request as part of an assignment roster (see Roster Screen for 

complete list).

For example, the parent request for a Type 6 engine is request number “E-16” the 

subordinate crew members on the assignment roster would be numbered, “E-16.1,” “E-16.2,” 

“E-16.3,” and so on.
Interagency Standards for Resource Ordering Guide (ISROG) 

March 24, 2023 

Page 15

When adding subordinate requests: 

- DO NOT use this function to circumvent the system. 

- You can add a subordinate request only to a parent request filled with a configuration. 

- Either the sending or receiving unit may add a subordinate request to a parent request. 

When rotating personnel, the receiving unit may permit the sending unit to add 

additional subordinate requests. 

- If the sending unit is adding subordinate requests to a parent request they must be 

“like” resources and have the agreement of the ordering unit.

• Example #1: A parent request has been filled with a configuration for an 

exclusive use Type 2 helicopter and the resource is currently “At Incident.” The 

receiving unit (Incident Host) should create subordinate requests for replacement 

helicopter crew members as needed.

• Example #2: A parent request has been filled with a configuration for an 

exclusive use Type 2 helicopter and the resource is currently “Reserved.” The 

filling unit can create a subordinate request to add an additional trainee to the 

assignment roster.

• Example #3: A parent request has been filled with a configuration for a Type 3 

engine. The receiving unit can create a subordinate request to replace a 

crewmember that has been released for a crew swap or emergency release. 

- Add Documentation action. Add documentation when permission is granted by the 

receiving unit for a subordinate request to be added by the sending unit. 

- Add Documentation action. Add documentation when a subordinate request for a 

replacement resource is placed through the established ordering chain rather than 

direct to the filling unit.

- A Preorder cannot be selected when adding a subordinate request.