# Presentation: 274411

## FPA DEPLOYMENT LIVEMEETING

- Date

- Data Input and Dispatch Logic

## Agenda

**Today’s Topic: Data Input/Dispatch Logic **
**Questions****	****Presented by:  Sue Weber/Cal Gale****	****	****	**

## Just a Reminder . . .

- Please mute your phone unless asking a question
- No mute button?
- Try *6 for mute
- *6 again to disable mute
- When asking a question, state your name and FPU

## Input Data

**White Papers on the Web**
**  **Revised Understanding Preproduction Delays in Fire Program Analysis (FPA) Initial Response Simulation (IRS) Module  7/10/2008
- _[ ](http://www.fpa.nifc.gov/Library/Papers/Docs/FPA_2/WP_IRS_Delays_3_20_2008_final.pdf)_Understanding Delays in Fire Program Analysis (FPA) Initial Response Simulation (IRS) Module  3/20/2008

-   Dispatch Location Associations
-   Delays
-   Attributes

## Dispatch Logic: High Level Overview

- You, the planner, define which type of fire resources responds to fire events based on expected fire behavior
- The FPA application functions as a     “duty officer” who assigns resources to a fire in a specific FWA based on your inputs
- How does that work?

## Planner Inputs

- By FWA
- Dispatch Logic Table name
- # of Fire Dispatch Levels (3, 4, or 5)
- Number and type of fire resources
- By Fire Dispatch Level

**Notes:**
In general, For each FWA you will input a dispatch table name and your table will include a fire danger “index”,  dispatch levels, and the number and type of resources you will send to fires.  This table can be globally applied to all the FPU, certain FMUs (and their FWAs) or to individual FWAs.

## 1. Dispatch Logic Table Name

- Dispatch Logic Table name

**Notes:**
In general, For each FWA you will input a dispatch table name and your table will include a fire danger “index”,  dispatch levels, and the number and type of resources you will send to fires.  This table can be globally applied to all the FPU, certain FMUs (and their FWAs) or to individual FWAs.

## 2. Index

**2. Index**

- A method of assessing fire behavior, used in many fire management plans or dispatch pre-attack plans
- FPA system currently uses a derived Burn Index (BI)
- Planners apply fire resource responses to fires based on anticipated fire behavior and other factors

## 3. Fire Dispatch Levels

- Allows Fire Planners to create dispatch logic tables that closely match each agency’s fire management or dispatch plans
- Planners can set the number of FDLs - either three, four, or five
- Places fire behavior characteristics into “bins” to simplify dispatching type and quantity of fire resources

**Notes:**
Dispatch levels – consider them like “buckets” that contains a group of characteristics (for now that would be Burning Index) - they allow you to create a dispatch logic table similar to your fire management plans/dispatch plans. 
Places fire behave characteristics into bins to simplify dispatching system

## 3. Dispatch Logic “Type”

- System groups fire producer types to allow planners to assign specific numbers and/or types of resources to Fire Dispatch Levels
- It also assembles crews, engines, dozers, and tractor plow types into their own groups
- Avoids creating bias in model towards specific individual fire resources

**Notes:**
Dispatch logic type: Takes fire producer types and groups together similar resources to keep it simpler.  So with a certain type of fire behavior, the system will dispatch by group.  Eliminates bias (intentional or unintentional) towards using a specific engine when there may be another one that’s closer.  Plus, you don’t know ahead of time when the system is using a specific resource on an ongoing fire – so you don’t want to be too specific.  It’s a similar thought process as used in dispatching. 

## Dispatching Resources

- Each fire event has a calculated ROS, FL, BI and FIL
- Fires are binned in Fire Danger Levels based on the derived BI
- Fires receive a response sequentially based on their date & time of discovery
- Uses as many resources as are available (& _specified_) based on the Dispatch Logic to contain a fire
- All the resources in the dispatch logic table for a given dispatch level will be dispatched at one time when available.

**Notes:**
If you have 6 engines in your dispatch logic, it sends 6 engines (w/ quickest arrival time) – it will return unused engines based on your “dispatch not used contain delay”.
System dispatches resources closest to fire and if they aren’t used on the fire it returns to their dispatch location.  

## Dispatching Resources

- The model first looks at the closest dispatch location to find a resource type listed in the table.  It then uses the resource with the best production capability if more than one fire resource is available for dispatch
- When the resource types with the shortest arrival time and production capability are already committed it searches for the specified resource with the next shortest arrival time.
- Returns unused resources based on your “Dispatch Not Used Contain Delay”
- Can apply Dispatch Logic table to one or more FWAs

## Dispatch Logic Held Constant Across Options

| Fire Resources | Minus 10% | Base | Plus 10% | “Minimum” 
Dispatch Logic |
| --- | --- | --- | --- | --- |
| Engines | 1 | 2 | 3 | At least 3 |
| Handcrew | 1 | 1 | 2 | At least 2 |
| Helicopter | 0 | 1 | 1 | At least 1 |

- Build your logic to accommodate your highest options
- For your lower options, disassociate unwanted resources when  building your option
- Logic can be edited, but then you must rerun the analysis

**Notes:**
FWAs can have different logic but it must be held constant across all options
Example on slide shows as you work on your analysis you’ll input your base level of resources in a FWA.  If you have to lose 10% of budget you will have to accommodate that by reducing resources.  The example shows what resources you will include to accommodate a smaller budget.  Dispatch logic has to accommodate your high options and low side of the options.  For lower options you disassociate the resources you can’t afford – you don’t have to alter your dispatch logic to do that. To disassociate resources, go to Preparedness Options/Resource Assignment

## Things to consider

- Each FWA can have a different dispatch logic table but these must be held constant across the options
- Use current dispatch plans only as guidance & expect to make changes from the FPU’s actual dispatch plan as you validate the model
- ROS in the model may be higher than what you experience in real life
- Don’t make dispatch logic “too tight” – remember the model is fighting the fire until it exceeds your simulation limits

**Notes:**
The number of resources that you enter into your dispatch logic should not be too tight (too few), but also not too loose (way too many!) since the model will send everything you ask for - if it’s available.  It will then return those resources not needed based on your “Dispatch Not Used Contain Delay”.
You can globally apply dispatch logic tables to FMUs or FWAs to make it simpler and you can apply dispatch tables across several FMUs or FWAs.
You could have one single Dispatch Logic table that works for your entire FPU but that may not serve you well.  However, think about the general types of dispatches that you do in your FPU – some examples include full suppression, limited response, roadless areas (emphasis on aerial resources), WUI protection, wilderness (no mechanized).   You may want to build a table for each and then apply them to the appropriate FWAs.

## Things to consider

- Works with “*other than full suppression*” responses by FWA
- Refer to “exceeds simulation limits” time & acres
- Limit  # and type of resources based on desired response
- Supports FMP restrictions and constraints
- Dozers not allowed in wilderness FWAs?
- Terrain limits the type of resources that can respond?

**Notes:**
For “other than full suppression”: think about what you put in for FWA “exceeds simulation limits” in terms of acres and hours. You will want to limit number and types of resources dispatched to fire.  Build into your dispatch logic

## Things to consider

- For Dispatch Logic to work correctly:
- Are dispatch locations associated to the FWA?
- Are fire resources assigned to dispatch locations?
- For lower funding levels, have you disassociated those fire resources that you don’t want included?
- Is your “Dispatch Not Used Contain Delay” appropriate?
- Are your FDL breakpoints appropriate?
- 80% of your fires occur at low burning index but the model has only 10% of them at that level

**Notes:**
Here’s a list of things to consider – like a checklist –to make sure the Dispatch Logic will work right.
You input your “break points” in your fire danger “levels” – and this is how your fires are binned.  But if you set your levels wrong, your fires may end up spread incorrectly across the wrong bins.   

## How to Get Started?

- Focus on setting up Dispatch Logic for your Validation Run
- Validation run will be discussed on a future call...
- Then refine dispatch logic as you build your options