Skip to main content

IQCS 2.0: IRWIN Integration

  • May 2017 IQCS first connected to the Integrated Reporting of Wildland-Fire Information (IRWIN) v5 application to begin pulling incident header fields to populate the Incident Setup page. This connection eliminated the need to enter/create incidents in the IQCS application being exchanged through IRWIN and thus decreasing the workload to users. This was the first step of the connection while ROSS was still in place and prior to IROC being stood up and integrated with IRWIN.

    In March 2020 with the implementation of IRWIN v6, and IROC, the qualification applications became part of the write/read systems in the IRWIN integration. IQCS began writing (sending) responder and qualifications to IRWIN using existing business rules. It also began reading (importing) responder experience records.

    May 2025, per priority and direction of the IQCS Change Management Board (IQCSCMB), IQCS migrated program to began pulling training completion data that has been populated to IRWIN from the Learning Management Systems (LMS) for responders in the IQCS application.

    This expansion brought the data exchange with IRWIN to the following:

    • Write (send) Responder Data
    • Write (send) Responder Certified Qualification Data
    • Read (Pull) Incident Data
    • Read (Pull) Responder Experience Data
    • Read (Pull) Responder Training Data

    With the integration is it important to keep in mind that NOT all responders records need to be integrated to IRWIN. Per business requirements an IQCS responder record can exist and be managed in IQCS without being integrate to IRWIN. Examples of some situations include:  

    • Agency has business requirements not to integrate their responder records.
    • Responder is no longer engaged in incident response and thus the record need not be integrated.
    • Responder has NO agency certified qualifications. 

  • Responder Profile Integration 

    For an IQCS 2.0 responder record and their certified qualification data to be integrated to IRWIN, and thus available to connected systems, data requirements must be met. It all begins with the responder's administrative record. If the responder administrative record (the person info) is not integrated then their certified qualification CAN NOT be sent. 

    If you are having issues integrating a qualification record, first check to see if the responder (person) record is showing as integrated with IRWIN. 

    IRWIN Required Responder Data

    For an IQCS 2.0 responder profile to be integrated to IRWIN, the IRWIN required fields MUST be populated on the responder's profile record. Per IQCSCMB, an responder profile can exist in IQCS 2.0 and be managed without integration to IRWIN. However, if there is a need to integrate the responder record, ensure that the following data has been populated. 

    • Name
    • Birth Month and Birth Day
    • Primary Email
    • Primary Phone
    • Agency Provider Unit ID
    • Employment Category
    • Home Dispatch Unit ID
    • Home Jetport
    • Manager Contact Information 

    Manager Contact Information 

    The contact information for the manager of a responder resource is used in duplicate resolution and also transferring resources from one system of record (SOR) to another. The order the application uses to send manger information is the following. If one is left blanks, then the application will move on the next until populated data is found. 

    • Account Manager
    • Certifying Official
    • Responder

    Troubleshooting Not Integrated Records When All IRWIN Required Info Has Been Entered. 

    There are times when a record is showing as NOT Integrated although all the required information has been entered. In order to reinitiated a send to IRWIN, we suggest walking through the following process.

    *****PENDING NEW APPLICATION PROCESS****

  • Agencies may have responders that do not need to go to IRWIN and made available to connect systems but are needed to managed in the IQCS application for incident qualification records. 

    To create an IQCS only record create your responder as normal but exclude the dispatch Unit ID or Jetport. Because these two fields are mobilization specific fields and the record is not being added to IRWIN for mobilization, then they do not need to be entered in IQCS.

    You will get a one-time message warning that the responder does not have all the required information. Click on No. You will not receive any further messages that the responder is missing IRWIN required data. The exception:

    • At some point the required data is filled-in and the record saved.
    • An IRWIN ID is received – indicated by the status of Integrated.
    • Required data is removed after an IRWIN ID is received.
      • In this case, you will get a message each time you visit pages with missing data.

    If the responder record was integrated but is not longer participating in incident response, then the Dispatch Unit ID and/or Jetport data can be removed. Removing an IRWIN required data field will release the record in IRWIN (setting SOR from IQCS to NONE) indicate that the IQCS is no longer updating the responder information in IRWIN. 

  • Managing conflicts with other responders in IRWIN is the responsibility of the IQCS 2.0 Account Manager. Conflicts can be against records that have a System of Record (SOR) of IQS, IROC, IQCS, or NONE.

    Access to the conflict table and responders on the table is based on IQCS 2.0 roles and agency organizational access.

    IRWIN Conflict Resolution 

    For a SOR of IROC, IQS or IQCS, reach out to the contact person and ask that they go through their process of making a responder available to another qualification system. For IQCS 2.0, that is changing the responder's profile status to Inactive. For IQS, you will get a transfer file. For IROC, there is no transfer file therefore no electronic record for that responder.

    • Duplicate
      • This action (button) indicates that the IQCS 2.0 responder record is a duplicate to another IQCS 2.0 record for the same responder that is already in the IQCS 2.0 application. The multiple records that exist in IQCS for this responder need to cleaned up to have only one IQCS record per IQCS 2.0 responder. Selection will notify IQCS staff to delete this record. DO NOT USE when the in-conflict Resource System of Record (SOR) is identified as IQS, IROC or NONE - - use Claim Responder
    • Not a Duplicate
      • This action (button) indicates that the IQCS 2.0 responder is not a duplicate to existing record in IQCS 2.0 or IRWIN and the unique record to be added to IRWIN.
    • Claim Responder
      • This action (button) is used when an IQCS 2.0 responder conflicts with their own record that is already in IRWIN due to management by another application/system. For IQCS 2.0 to take over management of a record in IRWIN, the Resource System of Record (SOR) must be NONE. A record can only have one managing system and IQCS can not take it from another system. If the Resource SOR is IQS or IROC, then IQCS can not take over record until they they have released management.

    Instructions - IRWIN Conflict Resolution

    *****PENDING NEW APPLICATION PROCESS****

  • An IQCS 2.0 resource profile must have an Irwin RID and a status of INTEGRATED for certified incident qualifications to be sent to IRWIN. Without BOTH of these pieces of data the two applications cannot transfer data on the resource or their certified qualifications. 

    It all begins with the responder's profile record. If you are having issues integrating a certified qualification record, first check to see if the responder's profile is showing as integrated with IRWIN. If the responder profile is not integrated then their certified qualification CAN NOT be sent. 

    Send Agency Certified Qualification to IRWIN

    For an agency certified qualification to be available to be sent to IRWIN, the following are required:

    • The position qualification status must be qualified or trainee.
    • The Certifying Official must complete the agency certification process and agency certify the qualification.
    • IRWIN status must be Integrated (not in conflict).

    NOTE: It all begins with the responder's profile record. If you are having issues integrating a certified qualification record, first check to see if the responder's profile is showing as integrated with IRWIN. If the responder profile is not integrated then their certified qualification CAN NOT be sent. 

  • For every integration message (action) IQCS 2.0 application sends to IRWIN, IRWIN will return a response to IQCS 2.0. The vast majority of these responses are "Successful" but there are situations when a data add or data change can not be performed. It is highly recommended that a user review these messages when troubleshooting why data is not in IROC/CADs (via IRWIN) as expected. 

    There are two ways to review this IRWIN Integration Message data in the IQCS 2.0 application: 

    1. Responder Profile Auto Doc Integration Messages
      • This is specific to a single responder
    2. IRWIN Integration Messages
      • This will return actions be a single user or batch process for many responders profiles. 
    Instructions - Review Responder Profile Auto Doc Integration Messages

    *****PENDING NEW APPLICATION PROCESS****

    Instructions - Review Integration Messages

    *****PENDING NEW APPLICATION PROCESS****

     

    Errors

    *****PENDING NEW APPLICATION PROCESS****

     

  • There has been an identified need to develop an application process that will allow a user to compare what is in IRWIN for a responder profile and sync the data to IRWIN if not correctly reflecting IQCS 2.0. Example, a view that shows the name in IRWIN compared to the name in IQCS. If not a match, then a button/process to repush data to IRWIN to sync up the applications. 

    Likewise, there has been an identified need to develop an application process that will allow a user to re-pull data from IRWIN for records that may have not been pulled in by the application. 

    Instructions - Reviewing Data in IRWIN and Syncing Data to IRWIN

    *****PENDING NEW APPLICATION PROCESS****

    Instructions - Syncing Data from IRWIN

    *****PENDING NEW APPLICATION PROCESS****

  • On May 3rd, 2017 IQCS connected to the Integrated Reporting of Wildland-Fire Information (IRWIN) v5 application to begin pulling incident header fields to populate the Incident Setup page. This connection eliminates the need to enter/create incidents in the IQCS application being exchanged through IRWIN and thus decreasing the workload to users.

    IQCSCMB identified nine (9) data fields to be pulled into IQCS for use in responder incident qualification management. An incident record must exist in order for experience to be credited to it. 

    IRWIN Imported Incidents

    • Are not editable.
    • Incident header data pulled (new and updates) once every 60 minutes.
    • Imported incidents will display an IRWIN ID.
    • Nine fields pulled from IRWIN: IRWIN ID (GUID), Unique Incident ID (calendar year-unit identifier-local incident ID), Incident Name, Begin Date, Unit Identifier (Protecting Unit), Event Kind, Event Category, State. 

  • With the implementation of IRWIN v6 on March 9, 2020 the qualification applications have became part of the write/read systems in the IRWIN integration. The IQCS 2.0 application writes (sends) responder and their qualifications and then reads (imports) incident and responder experience records.

    The experience records that the qualification systems pull in are ones that have been completed (assigned and released from an incident) in the dispatch/ordering systems for IQS and IQCS 2.0 responders. The frequency of the import in to IQCS 2.0 is hourly for both incidents and experience.  

    The IQCSCMB set business requirements on the data and the processing of the data to/from IRWIN. 

    IRWIN Imported Experience Records

    • Incident and experience records are queried from IRWIN for import on a 60 minute cycle.
    • All incidents are pulled for population to the IQCS 2.0 Incident control table but only IQCS 2.0 SOR responder experience records will be imported in.
    • The qualification must be agency certified and integrated in order for an experience to be pulled in for it.
    • Experience records must have an arrival and departure (release) date in order to be available for import.
    • Assignments that are canceled enroute or reassigned enroute will not generate an experience records for import.

  • May 2025, per priority and direction of the IQCS Change Management Board (IQCSCMB), IQCS migrated programming to begin pulling training completion data that has been populated to IRWIN from the Learning Management Systems (LMS) for responders in the IQCS application.

    Building upon the current integration of data with IRWIN, the IQCS 2.0 application writes (sends) responder and their qualifications and then reads (imports) incident, responder experience and responder training records.

    The training records that the qualification application will pull in are ones that have been pushed to IRWIN by a LMS, are in a completed status for IQS and IQCS 2.0 responders. The frequency of the import in to IQCS 2.0 will be nightly (once every 24 hrs) for training records.  

    The IQCSCMB set requirements on the data and the processing of the training records from IRWIN and the application is programmed to reflect. 

    IRWIN Imported Training Records

    • Training records will be queried from IRWIN for import on a nightly cycle (once every 24 hrs).
    • Only records with a CompletionDate data element will be pulled in from IRWIN.
    • Records will be populated to the responder's Training record on the Qualification Training tab. No records will be added to Other Training.
    • Records will be identified as sourced from the integration by using the IRWIN CreatedBySystem data element.
    • Records will be displayed as view only and will not be editable in IQCS 2.0.
    • Records pulled in completion date will be populated to the start date and the end date.
    • Updates to the record in IRWIN will be pulled and applied to the record in IQCS 2.0.
Article Category
IQCS 2.0 Application User Guide