Spring Brings Changes to ROSS Status

           

Version 2.0, expected to be released in the spring, will have fairly transparent changes to the user. Behind the scenes, however, significant improvements have occurred.

Several new, more powerful servers have been added, and the server configuration has undergone substantial re-engineering. System software, such as Oracle, Versata and BRIO, also was upgraded. Many security enhancements will be implemented with this release, as the system is going through certification and accreditation. This review will include hardware, software, computer facilities, policies, regulations and user guides. The focus of Version 2.0 is to improve the performance of the system. While network issues are outside the ability of the ROSS team to affect, a network performance review will be conducted with the 2.0 rollout.

Version 2.1 is scheduled for a June release. The focus of this version is to address critical software problems or bugs, additional development within the approved scope, and improvements to reporting needs. The to-do list is much longer than the available programming time, so priorities were set based on input from users. Some changes include:

• Release to home

  Dispatchers with the proper role will be able to release their resources from non-local incidents.

• Ordering chain improvements

  All units in a request's chain will be able to view the request, edit travel and reassign resources. Dispatch will be updated on status changes.

• Search for a resource

  Users will be able to search for aircraft, crew, equipment or overhead items by resource name including resources managed by other dispatch centers, even when the resources are not assigned.

• Name requests

  Users will be able to create and place name requests for a specific overhead resource (ROSS or non-ROSS) on the New Request screen; change a regular request to a name request until it is placed; and edit the requested name while request is pending.

• Pending request

  Qualified emergency/administratively determined firefighters will be displayed on the available tab; problems with reassignment of group requests will be corrected; users will be able to create a manifest for a request filled by a status-only office; “fill with new resource” will be restricted by role; options to “fill with EFF/AD” and “fill with agreement” will be added.

• Edit request

  Requesting units will be able to edit the requested catalog item as long as the request is pending. This includes requests to other units.

• Preposition

  Duplicate display of prepositioned call-when-needed resources will be corrected; problem causing locked resources will be corrected; users will be required to select a release option when filling a non-local request with a prepositioned resource.

• Web status

  Government non-dispatch units such as rural fire districts will be able to use Web status for their aircraft, crew, equipment, and overhead non-service and service items; remote supervised employees and nested supervisors will be permitted.

• Reports

  A dispatch center workload report will be added that includes all pending and filled requests generated by the user's dispatch center no matter where they are pending or where they were filled, all pending requests placed with the user's dispatch center, and all closed requests generated by the user's dispatch center.

A complete list of version changes will be issued with the release.

The National Interagency Resource Ordering and Status System is a National Wildfire Coordinating Group — sponsored information systems development project. The scope of the project focuses on automating current processes enabling dispatch offices to electronically exchange and track information near real-time. When complete, ROSS will track all tactical, logistical, service and support resources mobilized by dispatch. For more information, visit http://ross.nwcg.gov.