IQCS 2.0: Control Tables

Control tables are the foundation for implementing agency standards in the IQCS 2.0. Control tables serve numerous functions in the application and are used for the following:

• Provide a place to establish and maintain core data (agency list, agency organizations, airport list, position requirements, course information, course equivalents, incident list, etc.) for consistency in the application.
• Control tables eliminate redundant data entry by providing a standard list and default values.
• Contribute to data integrity within the application by providing uniformity and consistency of data entry.
• Improve reporting by improving data entry standards. 

Once they are established, control tables serve to store and maintain data at the record level.

The Agency control tables defines the agencies that are utilizing the IQCS 2.0 application for their responder incident qualification management. Per IQCSCMB direction, the addition of an agency must be approved by the IQCSCMB, and in some situations the NWCG parent organization, prior to activation in the application. 

This control table and an agency record are the foundation for all things associated to that agency (agency organizations, agency organizational structure, agency organization-unit id relationship, agency standard process mapping, agency standards, responder record, responder qualification processing, etc.).  

The permission access for this IQCS 2.0 control table is set to a view-only access and may not be available to all roles.

Instructions - Navigating to the Agency Control Table
To view the table, follow the steps below..

1. Navigate to Main Menu > Control Tables >  Agency.
   • 
2. Agency Code. The industry standard code issued to the agency.
3. Agency Title. The industry standard title issued to the agency.
4. Agency Lead. The current IQCS agency lead for the agency.
5. Status. The current standing of the agency utilizing the application for incident qualification management. 

The Agency Organization table is used to reflect the individual agency organizations that exists in an active or inactive status. Agencies are built with their own specific and unique organizational structure in the application. These structures are used to organize agency responders and provide user security to (or from) responder records.

Each agency organizational structure start with the agency identifier (Agency control table). From there it utilizes individual organizations to build/establish a hierarchy of to reflect an organizational structure of the agency states/regions/etc. IQCS agency leads are the stewards for their organizations and the organizational structure in the application. Agency organizations can be found at https://iqcsweb.nwcg.gov/agency-organizations.

All changes to agency organizations, including the organizational structure, must be reviewed and approved by the IQCS agency lead prior to implementation to the application. 

The permission access for this IQCS 2.0 control table is set to a view-only access and may not be available to all roles.

Instructions - Navigating to the Agency Organization Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Agency Organization.
   • 
2. Agency. The agency that the organization belongs to and manages it. Used for security and reporting.  
3. Agency Organizational Code. The issued code per identified standard.
4. Organizational Title. The issued title per identified standard.
5. Parent Org. The identified higher level organization that the organization sits under. Used for security and reporting.
6. Level. Used in the organizational structure to create a hierarchy of organizations. Used for security and reporting.
7. Status. The current standing of the agency organization in the application for responder/security per the agency. 

Agency Organizations Use in User Security

A user profile can be assigned multiple agency organizations for their specific security needs to manage responder profiles. User security can limited to a single organization, organizations within a single agency or organizations across multiple agencies.  

A responder profile can only be assigned to a single Agency, Agency Organization and Agency Provider Unit ID. If a responder's profile is set to an agency organization that a user does not have security access to, then that responder's profile will not be viewable to that user. 

Adding or Modifying an Agency Organization 

Agency organization requests (new and/or modification) can be processed by following IQCSCMB process. To review current agency organizations, visit the Agency Organizations page.

1. Complete the Request for IQCS Organization Codes form and submit it to your IQCS agency representative.
2. The IQCS agency representative will evaluate and ensure completeness. If approved, they will forward the completed form to the IQCS agency lead.
3. The IQCS agency lead will evaluate and ensure completeness and adherence for their agency organizational structure. If approved, they will forward the form to the IQCS application security contact.

DO NOT submit the request directly to IQCS staff and/or help desk as it must be authorized by the IQCS agency lead. Any request not submitted by an IQCS agency lead will not be processed by security.  

Agency Standard Process Mapping table is utilized by the application to apply the agency standard hierarchy as defined by the IQCS agency lead for their specific agency to their specific agency responders. Per the IQCSCMB, all agencies must have at a minimum the NWCG PMS 310-1 standard active in their agency standard process mapping. Any changes to an agency's Agency Standard Process Mapping must be reviewed and approved by the identified IQCS Agency Lead. 

Because agencies often have agency-specific incident qualification standards that are outside the NWCG PMS 310-1, then most also have their own agency standard included in the control should they adopt agency-specific standard. The DOI agencies are also required to have the DOI IPQG standard as a component of Agency Standard Process Mapping. 

In a case that an incident qualification standard exists and is active in multiple standards, example NWCG PMS 310-1 and agency-specific, then the application will enforce the incident standard requirements per the standard and priority mapping of the agency that the responder is currently assigned. 

In the example above, the Task Force Leader (TFLD) incident qualification has three active standards; NWCG PMS 310-1, BLM agency-specific and USFS agency-specific. Using the Agency Standard Process Mapping screenshot above, BIA agency responders would be mapped/held to the NWCG PMS 310-1 standard because there is no active BIA agency-specific (priority #1) TFLD standard. Where as a BLM agency responder's would be mapped/held to the BLM TFLD agency-specific standard due to their standard mapping priorities that the agency standard is priority #1. 

The permission access for this IQCS control table is set to a view-only access for most user roles.  

Instructions - Navigating to the Agency Control Table
To view the table, follow the steps below..

1. Navigate to Main Menu > Control Tables > Agency Standard Process Mapping.

Airports (Jetports) are utilized on responder/overhead resources by the ordering and dispatching applications for incident response. Although IQCS 2.0 has no direct need for Jetport data on a responder's profile, this is data that IQCS 2.0 collects that then is shared to the integration as a component of the resources profile for other applications to utilize. The Airport data is managed by FAA and pulling into the IQCS 2.0 Airport (Jetport) control table daily via FAA AIS Open Data source. 

The permission access for this IQCS 2.0 control table is set to a view-only access for all users, including application administrators.

Instructions - Navigating to the Airport (Jetport) Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Airport (Jetport).

   

Country is utilized on other control tables in the application. Although editable in IQCS 2.0, it is sourced from NWCG via the Country Code Data Standard in which adopts the International Organization for Standardization (ISO) standard for two-letter country codes. 

In time IQCS 2.0 will sync from a data source to eliminate the need to manually maintain. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Country Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Country.

   

Country Subdivision Code is utilized on other control tables and responder profile (qualification) locations in the application. Although editable in IQCS 2.0, it is sourced from NWCG via the Country Subdivision Code Data Standard which adopts the International Organization for Standardization (ISO) standard for country subdivision codes of up to three alpha-numeric characters. This standard replaces the NWCG State Code standard.

In time IQCS 2.0 will sync from a data source to eliminate the need to manually maintain. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Country Subdivision Code Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Country Subdivision Code.

   

The Course Table holds the NWCG Course/Training Catalog and approved agency-specific trainings utilized in incident qualification management. Information added and maintained on this control table is then used on other course related control tables, position requirements control table and responder profile (qualification) records. 

The NWCG Course/Training Catalog is the system of record for the NWCG listing in the Course Table. These NWCG courses are automatically (manually) updated to reflect changes to the NWCG Course/Training Catalog. The IQCS 2.0 receives guidance from the NWCG Incident and Position Standards Committee (IPSC), the IQCS Change Management Board (CMB) and IQCS Agency Leads regarding requests to add, change or remove courses.

The permission access for this IQCS control table is set to a view-only access for most user roles. 

Instructions - Navigating to the Course Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Course.
   • 
2. Course Code. Reflect the issued code per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.).
3. Course Title. Reflect the issued title per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.).
4. Course Status. Reflect the current standing/utilization per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.).
5. Training Category. Reflect the current category per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.).
6. Effective Date. Reflect when the course was added/updated per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.).
7. Hours. Reflect the identified course hours per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.). Utilized in reporting.
8. Course Catalog. Reflect the catalog/source or managing party (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.).
9. Continuing Education Units. Requested addition by the IQCSCMB for future utilization.
10. Recurrent. Reflect if the course is recurrent per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.). Utilized in setting expiration date.
11. Frequency. Reflect if the course is on an annually or monthly recurrent requirement per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.). Utilized in setting expiration date.
12. Recurring Length. Reflect if the course frequency length per the source (NWCG Course/Training Catalog, Agency Lead, IQCSCMB, ect.). Utilized in setting expiration date.
13. Mass Training. Reflects if the course can be utilized to mass award completion per the Mass Training feature. Defined by the IQCSCMB or agency lead if the course is single agency utilization. 

Adding Courses to the IQCS 2.0 Course Control Table

Course are added per addition to source standards (example: NWCG Course/Training Catalog), IQCS agency lead approval or IQCSCMB approval.  

The best place to start with requesting a course be added for incident qualification management is with your IQCS agency lead. They will be able to answer any questions, determine level of utilization (NWCG versus national versus agency-specific), the qualification for the requirement, and decide to support or not.

For a non-NWCG course to be added, the request to add needs to go through an agency-specific approval process or, if multi-agency utilization but not NWCG, then the IQCS Change Management Board (IQCSCMB) approval process. The agency lead (for single agency use) or IQCSCMB agency leads (for multi-agency use) will review the request and make a decision. If approved, they will direct IQCS staff to set up the course in the control table and add it as a qualification requirement for the identified position qualification(s).

If the course is to remain agency-specific (example: BIA, BLM, USFS, etc.) only then the IQCS agency lead will assign the next course code from their agency-specific course number block (example: BI200, BL300, FS500, etc.). For a national multi-agency course, the IQCSCMB chair will assign the next available course number from their N9000 block.  

The Course Catalog control table is used largely on the Course control table to reflect the source of the course information. A large number of the courses in the IQCS 2.0 Course control table are sourced/managed by the IQCSCMB. 

The permission access for this IQCS control table is set to a view-only access for most user roles. 

Instructions - Navigating to the Course Catalogs
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Course Catalog.

   

There are times, per NWCG, IQCSCMB or agency-specific standards, that a completion of a single course will grant competency for other courses utilized in incident qualification standards. Because of this direction, the IQCSCMB established the control table that will process the granting of an identified course(s) when a responder completes a training per their completion date. 

For example, if a responder completed S130 after 11/30/2022, then the responder's training profile will also receive a completion record for RT130 and S110. Where as, if a responder completed S130 between 12/01/2003 to 10/31/2021 then they would receive a completion record for RT130 and L180.

Values on this control table are only added once approved by the IQCSCMB or agency lead if sole agency utilization. 

Instructions - Navigating to the Course Add Training
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Course Add Training.
   • 
2. Effective Date. The date approved for a course to be granted to a responder per the completion and completion date of identified course.
3. Grant to Responder. The indicator to grant per the effective date and the course completion date.
4. Course Code [course code, course title, course status].
5. Course Add ID [course code, course title, course status]. The identified course approved to be granted per the course completion and completion date. 

Per standards, NWCG, IQCSCMB and/or agency-specific, there are identified course completions that meet the objects of other courses that are utilized in incident qualification management. Because of this direction, the IQCSCMB developed the Equivalent control table to identify and apply the equivalencies to ALL responder records consistently in the application and eliminate the need to manually record course completions (administrative action) course course the responder did not complete to their responder's training profile. 

The responder's training profile will indicate the course completed and the application will process the equivalency if one exists for an incident qualification standard. 

Values on this control table are only added once approved by the IQCSCMB due to multi-agency impacts.  

The permission access for this IQCS control table is set to a view-only access for most user roles. 

Instructions - Navigating to the Equivalent
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Equivalent.

   • 
2. Data Type.
3. Date Added.
4. Course.
5. Equivalent Course. 

Event Kind & Event Category is utilized on the Incident control table and the responder profile (qualification experience) in the application. Although editable in IQCS 2.0, it is sourced from NWCG via the Event Kind & Category Data Standard with the description that This data standard specifies general, high-level codes and descriptions to be used in categorizing the types of incidents and planned events to which the interagency wildland fire community responds.

In time IQCS 2.0 will sync from a data source to eliminate the need to manually maintain. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Event Kind & Category Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Event Kind & Category.
   • 

To credit a responder profile with experience on an incident, the incident must first exist in the Incident control table. It is important to keep in mind that the Incident control table is merely a placeholder for very basic incident information as the IQCS 2.0 is not the system of record for incidents. The IQCS 2.0 application is the system of record for responder qualifications and experience used to build and maintain those incident qualifications.

The IQCS 2.0 application is connected to the Integrated Reporting of Wildland-Fire Information (IRWIN) application and pulls nine (9) incident header fields to populate the Incident Setup control table. Due to changing incident complexity over the life of a fire, these this field is not recorded on the Incident control table. Incident complexity can be entered at the Responder Profile page for their experience record to reflect when they were committed.

There are two methods (data sources) for an incident record to exist in the Incident control table:

1. User entered
   • Are editable.
   • Unique Incident ID (previously called Incident Number) auto populated from the Begin Date, Unit ID and Local Incident ID fields.
   • Incident Year auto populated from Begin Date.
   • Event Category limited to the subcategory of the selected Event Kind.
   • Will not sync/merge to an IRWIN pulled incident.
      
2. Imported from IRWIN
   • Will display an IRWIN ID and a Last Updated date/time.
   • Are not editable in the IQCS application.
   • Data pulled (new and updates) every 60 minutes.
   • Will not sync/merge to an existing user entered incident.

The permission access for this IQCS 2.0 control table is set to add/edit access for most user roles.

Instructions - Add an Incident to the Incident Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Incidents.
2. Select the + Incident button.
   • 
3. Incident Name. Enter the full name of the incident. Required.
4. IrwinID. For user entered records, this field will default to N/A-INCIDENT WAS ENTERED BY USER .
5. Unique Incident ID. Will auto generated from Year, Unit Identifier and Year.
6. Begin Date. Enter the date on which the incident began. Required.
7. Year. Will auto generate from Begin Date.
8. Unit Identifier. Enter/select the Unit Identifier (Unit ID).
9. Local Incident ID. Enter the Local Incident Identifier. Example: 000001.
10. Country. Enter/select the Country of the incident. Will default to United States of America.
11. State. Enter/select the State of the incident. If you have selected a Unit Identifier, the State will default from that value. If no Unit Identifier was entered, then you will need to enter the State value.
12. Event Kind. Enter or lookup for the incident.
13. Event Category. Enter or look up the category. Only those that are a sub-category to Event Kind will be selectable.
14. Source. Will auto generate to User.
15. Last Updated Date. Will auto populate to date time data was entered or updated. 

Instructions - Viewing and/or Editing an Incident at the Incident Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Incidents.
2. Search for the Incident.
3. Select the Edit icon to open the page.
4. Imported from IRWIN
   • Cannot be updated.
   • Will display an IRWIN [Incident] ID.
   • Last Updated will display the last time the IQCS pulled/received an update.
5. User Entered Incident
   • Will not have an IRWIN Incident ID.
   • Are editable.
   • Changes will result in an update to responder’s experience records.
6. Select the Apply Changes or Cancel button.

Instructions - Deleting an Incident at the Incident Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Incidents.
2. Search for the Incident.
3. Select the Edit icon to open the page.
4. Select the Delete button.
   • Incident record will be removed.
   • Associated responder profile experience records will have the Unique Incident ID, Incident Name and Event Category removed from their record. User entered data will remain on profile.
   • Recreating the incident will not reassociate the responder profile experience records. 

The IQCSCMB identified the need to capture the individual IFPM qualification and training requirements for display on the responder's IQCS 2.0 Master Record report should they have attained the requirement. As result the IQCSCMB developed the IFPM Requirements control table which is solely used for the IQCS - IFPM Employee Application Report section of the Responder master Record report. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the IFPM Requirements Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > IFPM Requirement.
   • 
2. Category. Type of requirement competency. Used to determine what section of the IQCS - IFPM Employee Application Report section to place the attainment.
3. Requirements. Identified by the IQCSCMB agencies.
4. Title. Identified by the IQCSCMB agencies.
5. Status. The current standing of the IFPM Requirement. Used to determine if to continue to include in the section of the IQCS - IFPM Employee Application Report section. 

The Licenses and Certifications control table reflect the IQCSCMB approved values to be recorded a responder's profile in the Licenses & Certificates page. This data is also utilized on the Position [Qualification] Requirement control table to reflect a incident qualification standard. Per IQCSCMB direction, all Licenses & Certificates must be expiring. Values on this control table are only added once approved by the IQCSCMB or agency lead if sole agency utilization. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Licenses & Certificates Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Licenses & Certificates.

   

The Agency Organizations to Agency Provider Unit Identifier (Unit ID) control table connects specific Agency Organizations to an Agency Provider Unit ID. 

This need was identified by the IQCSCMB to limit their specific Agency Organizations to be returned when their Agency Provider Unit ID is utilized on the Responder Profile page. This limitation on data also assists uses with reducing the long list of Unit Identifiers and eliminates the potential for errors. 

The association of an Agency Organization to an Agency Provider Unit ID does NOT happen and is NOT maintained automatically. This association must be identified and approved by the IQCS agency lead. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Agency Organizations to Agency Provider Unit Identifier (Unit ID) Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Organization-Unit ID.
   • 
2. Agency.
3. [Agency Provider] Unit ID.
4. [Agency] Organization. 

Position Code & Position Title is utilized on the Position Details control table to reflect an issued code and title for a incident qualification standard. Although editable in IQCS 2.0, it is sourced from NWCG via the Position Code & Position Title Data Standard with the description that This data standard provides a code (mnemonic) and title for each position used in incident management response.

This data IS NOT when the incident qualification standard was published for utilization but this reflects with the NWCG PNB issued the code and title for utilization in the wildland fire community. There are cases were after PNB issues a code and title, the incident qualification standard may be years in development before being published. 

In time IQCS 2.0 will sync from a data source to eliminate the need to manually maintain. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Position Code & Position Title Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Position Code & Position Title.

   

The Position [Qualification] Details control table holds the general information of an NWCG and agency-specific position standard. It is the foundational piece that is then used in the Position [Qualification] Requirements control table. The following of an incident qualification standard are maintain at the Position [Qualification] Requirements control table.

• Standard
• Position Code and Position Title
• Status
• Endorsement
• Currency Length
• Position Task Book Requirement

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Position [Qualification] Details Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Position [Qualification] Details.
   • 
2. Status. The indicator if the incident qualification is included in the current publication of the identified standard.
3. Standard. The publication source of the incident qualification requirements. Incident position standards include incident position descriptions (duties and responsibilities) and position qualification requirements for training, experience, physical fitness, and position currency.
4. Position Code and Position Title. The NWCG Position Naming Board (PNB) approved position code and position title for consistency throughout the wildland fire community.
5. Endorsement. The type of incident for which the incident qualification standard is defined.
6. Currency Frequency. Currency for a position can be maintained by successful performance within the given timeframes in that position or successful performance as a Trainee or Qualified in identified positions.
7. Currency Length. The annual maximum time allowed for maintaining currency.
8. Position Task Book Indicator. Indicates if a position task book is a component of the incident position qualification standard.
9. Position Task Book Frequency. A PTB is valid for three years from the date of initiation. Upon documentation of the first evaluation record, the three-year time limit is reset from that new date.
10. Position Task Book Period. A PTB is valid for three years from the date of initiation. Upon documentation of the first evaluation record, the three-year time limit is reset from that new date.

The Position [Qualification] Requirements control table builds on the Position [Qualification] Details control table as is where the requirement pieces of an incident qualification standard are reflected. The following of an incident qualification standard are maintain at the Position [Qualification] Requirements control table.

• Standard Change Date
• Required Training
• Required Experience
• Physical Fitness Level
• These Positions Maintain Currency for XXXX

Because of the complexity of the standard change date and the application of each requirement per agency direction, the following are also a component of this control page for each requirements identified.

• Status
• Category
• Level [of competency]
• Required for Trainee
• Required for Position Task Book Issuance
• Apply Requirement Retroactively
• Allow for Administrative Override [if responder is missing requirement competency]

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Position [Qualification] Requirements Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Position [Qualification] Requirements.
   • 
2. Position Code & Position Title. Populated from the Position [Qualification] Details control table for this qualification. The NWCG Position Naming Board (PNB) approved position code and position title for consistency throughout the wildland fire community.
3. Standard. Populated from the Position [Qualification] Details control table for this qualification. The publication source of the incident qualification requirements. Incident position standards include incident position descriptions (duties and responsibilities) and position qualification requirements for training, experience, physical fitness, and position currency.
4. Endorsement. Populated from the Position [Qualification] Details control table for this qualification. The type of incident for which the incident qualification standard is defined.
5. Effective Date. Indicated the incident qualification standard publication date for the requirements. The date on this page has been defaulted from the Position Qualifications record.
6. [Requirement] Status. Indicates if the identified incident qualification requirement is being enforced per the effective date of the standard.
7. Category. The competency type that the position incident qualification requirement belongs.
8. Requirement. The position incident qualification condition that must be met for the responder to be qualified per the standard. List returns those that belong to the identified category.
9. Level. The position incident qualification requirement attainment status that the responder must have in their incident qualification record to meet the identified standard requirement.
10. Required for Trainee [qualification status]. The position incident qualification requirement has been identified to be in the identified status, includes current/valid, for a responder to be statused as a trainee.
11. Required for [Position] Task Book [Issuance]. The position incident qualification requirement has been identified to be attained/valid for the position task book to be issue/record for a responder.
12. [Apply] Retroactive. The position incident qualification requirement has been identified to be applied to the current effective dated record and all previous effective dated records.
13. [Administrative Action] Override Allowed. The position incident qualification requirement has been identified to allow (Yes) the certifying official the authorization to administrative action a responder's qualification status from unqualified to another status if responder is missing this requirement. If identified as No then an administrative action of the missing requirement cannot be performed.

The Role Assignments control table list return a user profile and the security and role setup for that person. shows who has access to an agency organization and the roles assigned to the user. Search criteria can be for an agency organization (return multiple users that have access) or a specific user (returning the agency organizations they have access too). In both cases, the user roles will also be displayed. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Position [Qualification] Requirements Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Position [Qualification] Requirements.
   • 
2. View Comprehensive Org Permissions. Lists all agency organization user has security access to.
3. User Email. The recorded user email of the user.
4. User Role. Lists all assigned roles user has been assigned.
5. Agencies With Org Access. Lists all the agencies that user has access to via the organizational security.
6. Account Locked. Identifies if the account has been locked due to application closure due to inactivity or management decision (closing due to no longer needed or an temporary administrative lock while determining course of action due to reported event).
7. Account Status. Active or Inactive. 

In order to better reflect the incident qualification standards in IQCS 2.0, the Standards control table was developed. With this table the application can clearly reflect the incident qualification standard source for the control tables like Agency Standard Process Mapping, Position [Qualification] Details and Position [Qualification] Requirements and then reflect that clearly on the responder's Responder Profile page for their incident qualifications. 

This simple control change is making big impacts for a more user friendly application. 

The permission access for this IQCS 2.0 control table is set to a view-only access for most user roles.

Instructions - Navigating to the Standards Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Standards.

Within the IQCS 2.0 Translate there are multiple NWCG and agency-specific data standards that are used throughout the application but have not be set up with their own control table. There are many data standard values included in a single table and unfortunately the table is very difficult to search within.

The permission access for this IQCS control table is set to a view-only access for most user roles.  

Instructions - Navigating to the Translate Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > Translate.
   • 
2. Field Name. The title issued/identified by the application.
3. Field Value. The code issued/identified by the application.
4. Effective Date. The date that the new value or the existing value was added or modified.
5. Long Name. The title issued/identified by the issuing party.
6. Short Name. The code issued/identified by the issuing party.
7. Status. The current standing of the value in the application for utilization.

NWCG Unit IDs are used to identify the organizational units within the federal and state government that are involved in wildland fire management. These codes are managed by the NWCG Unit Identifiers Board (UIB) chartered under the NWCG Data Management Committee (DMC).

Unit identifiers are directly tied to one or more agency organizations and are used in the exchange of data with IRWIN and connected systems.

The data in this table reflect  the NWCG Unit ID system of record (SOR), https://unitid.nifc.gov via a syncing process that will pull the information from the source application to populate this control table.  

The permission access for this IQCS 2.0 control table is set to a view-only access for all users, including application administrators.

Instructions - Navigating to the NWCG Unit Identifier Control Table
To view the table, follow the steps below.

1. Navigate to Main Menu > Control Tables > [NWCG] Unit Identifier.
   • 
2. Identifier. Reflect NWCG Unit ID. Definition pending review of their application.
3. **Unit ID (IQCS added, NOT from SOR). IQCS 2.0 formatting due to commonly used presentation of the Unit ID. Combination of State, dash, and Org Unit Code.
4. Name (Org Unit Name). Reflect NWCG Unit ID. Definition pending review of their application.
5. Tier 1 (Depart). Reflect NWCG Unit ID. Definition pending review of their application.
6. Tier 2 (Agency). Reflect NWCG Unit ID. Definition pending review of their application.
7. Geographic Area. Reflect NWCG Unit ID. Definition pending review of their application.
8. Wildland Role (Org Unit Role). Reflect NWCG Unit ID. Definition pending review of their application.
9. Org Unit Code. Reflect NWCG Unit ID. Definition pending review of their application.
10. City. Reflect NWCG Unit ID. Definition pending review of their application.
11. State. Reflect NWCG Unit ID. Definition pending review of their application.
12. Active. Reflect NWCG Unit ID. Definition pending review of their application.
13. Modified On. Last update of the data from the source.
14. Modified By. Data source