Ross i suite managing incident resources
This presentation is the property of its rightful owner.
Sponsored Links
1 / 16

ROSS & I-Suite Managing Incident Resources PowerPoint PPT Presentation


  • 51 Views
  • Uploaded on
  • Presentation posted in: General

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

Download Presentation

ROSS & I-Suite Managing Incident Resources

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Ross i suite managing incident resources

ROSS & I-SuiteManaging Incident Resources

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


  • Multiple imts single incident

    Multiple IMTs – Single Incident

    Emerging Large Incident or Existing, Decision is made to Zone incident

    Zone 1

    Team 1

    Zone 2

    Team 2

    ROSS - Consider Request Block Numbering

    I-Suite – Separate Databases

    Zone 3

    Team 3


    Ross request block numbering

    ROSS Request Block Numbering

    Incident Screen

    Be aware of the SYS default.


    Multiple imts single incident biscuit fire example

    Multiple IMTs – Single IncidentBiscuit Fire Example

    Biscuit Zone 1

    Biscuit Zone 2

    Single IMT – Databases merged in I-Suite

    Request Number

    Block 10000- 19999

    • Request Number Block 20000 - 29999

    Sour Biscuit

    Biscuit Zone 3

    Resources reassigned

    Request Number Block 30000 - 39999

    Request Number Block 40000 - 49999


    To complex or not to complex

    To Complex or Not to Complex…..

    • What is the purpose?

    Operational

    Fiscal


    To complex or not to complex1

    To Complex or Not to Complex…..

    • What is the final desired result?

    Maintain a single financial code

    Track incident costs separately


    One imt multiple incidents complexed

    One IMT – Multiple Incidents Complexed

    Incident 1

    ABC1

    Single IMT -

    Complex Incident –ABC5

    Incident 3

    ABC3

    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 2

    ABC2

    Incident 4

    ABC4


    Complex firecode

    Complex FireCode


    Crosswalk for reassigned resources

    Crosswalk for reassigned resources

    Resource Incident 1Complex Incident

    XYZ Engine 123E-5E-10

    Crew ABCC-3C-8

    Etc., Etc.O-2O-23


    One imt multiple incidents not complexed

    One IMT – Multiple Incidents Not Complexed

    Incident 1

    ABC1

    Create a new Data Base in I-Suite and Manage all incidents as one

    Incident 3

    ABC3

    Manage 4 separate databases in I-Suite

    Incident 2

    ABC2

    Incident 4

    ABC4


    One imt incidents have merged burned together

    One IMT - Incidents have merged (burned together)

    Select Primary Incident and reassign/merge resources from other incidents

    Incident A

    Incident B

    Incident C

    Handle merged fire as a single incident

    Continue to handle merged fires as separate fires


    One imt multiple incidents to multiple imts

    One IMT – Multiple Incidents to Multiple IMTs

    Incident 1

    ABC1

    Incident 3

    ABC3

    Not recommended if the incidents have been complexed

    No issue if not complexed

    Incident 2

    ABC2

    Incident 4

    ABC4


    Imt lend lease

    IMT Lend/Lease

    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.


    Resource reallocation

    Resource Reallocation

    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


    Imt reserve

    IMT Reserve

    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 force

    Surge Task Force

    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.


  • Login