Objectives Effects 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 IMT Lend/Lease Reallocation IMT Reserve Surge Task Force Zone 1 Team 1 Zone 3 Team 3 Emerging Large Incident or Existing, Decision is made to Zone incident Zone 2 Team 2 ROSS - Consider Request Block Numbering I-Suite – Separate Databases Incident Screen Be aware of the SYS default. Biscuit Zone 1 Biscuit Zone 2 Request Number Block 1000019999 Request Number Block 20000 - 29999 Biscuit Zone 3 Request Number Block 30000 - 39999 Single IMT – Databases merged in I-Suite Sour Biscuit Resources reassigned Request Number Block 40000 - 49999 What is the purpose? Operational Fiscal What is the final desired result? Maintain a single financial code Track incident costs separately Incident 1 ABC1 Incident 2 ABC2 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 Incident 3 ABC3 Incident 4 ABC4 Resource XYZ Engine 123 Crew ABC Etc., Etc. Incident 1 E-5 C-3 O-2 Complex Incident E-10 C-8 O-23 Incident 1 ABC1 Incident 2 ABC2 Create a new Data Base in I-Suite and Manage 4 separate Manage databasesall in Iincidents Suite as one Incident 3 ABC3 Incident 4 ABC4 Select Primary Incident Incident A reassign/merge and resources from other incidents Incident C Handletomerged as Continue handlefire merged a single incident fires as separate fires Incident 1 ABC1 Incident 2 ABC2 Not recommended if No issue if not the incidents complexed have been complexed Incident 3 ABC3 Incident 4 ABC4 Agreement between IMTs to share assigned resources for a limited period of time. I-Suite – Receiving Incident will capture costs as a line item, not actual posted time. Sending Incident will post time using accounting code from receiving incident. ROSS – These resources will not be reassigned in ROSS Caution – Some cooperator resources cannot be paid without a resource order. During periods of resource scarcity, this strategy will transfer resources between ongoing or emerging incidents to meet the current needs. I-Suite – Closed out by sending incident Re-entered by receiving incident ROSS – Reassigned to new incident Resources identified (if currently on an incident) or assembled (if not currently on an incident) and mobilized to support emerging new large incidents. I-Suite – Resources will continue to charge to current incident until reassigned. ROSS – Resources will be reassigned once the new assignment is identified. 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). I-Suite – (TBD) is responsible for posting resource time to the appropriate accounting code. Receiving incidents will be contacted daily to account for task force costs in I-Suite. ROSS – NWCC will coordinate all resource assignments. Incident activity will be documented in ROSS.