IROC Outage 03/22/2020
IROC Dashboard is currently down. User visiting the site will receive an error stating: This site can't be reached.
Technicians are aware of the issue and working to correct it but do not have a timeline for when it will be available. Updates will be posted as they are known.
Thank you for your patience.
e-ISuite Updates Due To ROSS to IROC Transition
With ROSS (Resource Ordering and Status System) being decommissioned and the IROC (Incident Resource Ordering Capability) system replacing it, there are a few things we’d like to share on how this will affect the e-ISuite user community.
IROC was deployed the week of March 9, 2020. In the initial release, the e-ISuite import file capability (formerly known as the ROSS Import) is not available. The IROC team anticipates having this capability available mid to late April.
Significant changes to the e-ISuite application need to be made to accept the new IROC Resource Import file. Currently, the e-ISuite application is being updated to replace the User Interface. A decision has been made that the changes to the e-ISuite application will be incorporated into the new User Interface release. We will keep you updated with information as more details become available, such as the anticipated release date for the new User Interface.
During the absence of an IROC Resource Import, resources need to be input into e-ISuite manually. We realize this is an increased workload and apologize for the inconvenience. Please plan your staffing needs accordingly.
e-ISuite Project Team
NAP Generic Account types such as Duty Officer have been Removed
With the implementation of FAMAuth authentication for IROC, security rules prevent generic account types such as the Duty Officer Accounts for Web Status.
At this time ALL Duty Officer Accounts have been removed. Each individual responsible for those accounts will have to apply for an unique NAP Account under their name; someone like the Chief of the Fire Department, or Fire Management Officer, for example.
We understand that some of the accounts have already been linked to either login.gov or eAuth; we are in the process of unlinking those accounts, so those individuals can re-link with their individual accounts.
INCIWEB Production Scheduled Maintenance - 03/10/2020 0700 MST to 0930 MST
There will be patching on INCIWEB Production from 0700 MST to 0930 MST on Tuesday, March 10th. During this time users will not be able to access the application.
FAMWEB Production Scheduled Maintenance - 03/10/2020 0700 MST to 1100 MST
Due to maintenance on servers at the National Interagency Technology Center (NITC) all FAMWEB applications and Cognos reporting will not be available on March 10, 2020 from 0700 MST to 1100 MST. In addition to the FAMWEB applications the FAMWEB production page will also not be available.
NAP 1.3.14 Deployment
NAP 1.3.14 will be deployed Thursday, March 5, 2020 starting at 2200 MST lasting for 3 hours. During this time all applications that authenticate via the NAP will be down. Those applications are ICBS, e-ISuite, ROSS Practice, WIMS and INCIWEB.
Is Your Dispatch IROC-Ready?
Pre Go Live Readiness
A smooth transition from ROSS to IROC relies heavily on data integrity. It is highly recommended that dispatch centers have all their transactional data “buttoned up” in ROSS before the program is shut off on March 5th. Transactional data refers to ROSS data that is constantly in flux, such as incidents, requests, and travel. A few examples of “buttoning up data” include:
- Closing all incidents that do not have any open requests.
- Filling all open requests.
- Setting travel for all resources going on assignment.
- Ensuring that all travel is complete.
The less transactional data "hanging out" there when ROSS is turned off, the better. In theory, when dispatch centers log in to IROC for the first time, the ROSS data pulled on March 5th will be there, exactly as it was when ROSS was turned off.