ROSS & I-Suite Managing Incident Resources. Objectives E ffects to consider when complexing, merging, splitting, and/or zoning incidents ROSS Incident Data Management I-Suite Database Management ROSS Request Block Numbering FIRECODE Implementing Resource Allocation Strategies
Emerging Large Incident or Existing, Decision is made to Zone incident
ROSS - Consider Request Block Numbering
I-Suite – Separate Databases
Be aware of the SYS default.
Biscuit Zone 1
Biscuit Zone 2
Single IMT – Databases merged in I-Suite
Block 10000- 19999
Biscuit Zone 3
Request Number Block 30000 - 39999
Request Number Block 40000 - 49999
Maintain a single financial code
Track incident costs separately
Single IMT -
Complex Incident –ABC5
ROSS – Request block numbering for each incident…or…reassign if early
I-Suite – Five separate incidents, manage all as one...or…one incident if reassigned
Resource Incident 1 Complex Incident
XYZ Engine 123 E-5 E-10
Crew ABC C-3 C-8
Etc., Etc. O-2 O-23
Create a new Data Base in I-Suite and Manage all incidents as one
Manage 4 separate databases in I-Suite
Select Primary Incident and reassign/merge resources from other incidents
Handle merged fire as a single incident
Continue to handle merged fires as separate fires
Not recommended if the incidents have been complexed
No issue if not complexed
Agreement between IMTs to share assigned resources for a limited period of time.
During periods of resource scarcity, this strategy will transfer resources between ongoing or emerging incidents to meet the current needs.
Resources identified (if currently on an incident) or assembled (if not currently on an incident) and mobilized to support emerging new large incidents.
Surge Task Forces are pre-identified suppression resources with overhead that can effectively and efficiently implement special mission operations in a short time period (one to four days).