FSH 5109.19 - FIRE MANAGEMENT ANALYSIS AND PLANNING HANDBOOK
                       1/83 WO AMENDMENT 1

84 - FPL-FIREPLAN*FPL-PROGRAMS.FPL-IAA

84.1 - Information Entry.  In response to prompts from program 
/FPL-IAA/, the following items of information are supplied 
interactively via a remote terminal:

    1.  FMAZ Designator.  (5 alpha-numeric characters.)

    2.  Maximum Size of Fire To Be Modeled.  (Escaped size.)  The 
default value is 300 acres, but the user may set a lower limit.  
(Fires not contained within the limit must have their final size 
subjectively established and acreage manually added to summary 
tables.)  A limit lower than 300 acres may be more appropriate 
for areas where even escaped fires historically seldom reach 300 
acres due to topography or physical barriers which mitigate or 
restrict spread.

    3.  Fire Management Option ID.  This is an identifier of the 
option used for each program run.  The entry is a 3 digit 
integer.

    4.  NFDRS Fuel Model.  The letter designates the Dominant 
fuel model assigned to the FMAZ on the /FPL-LEVEL2/ lead card.

    5.  Highest Fire Intensity Level for FMAZ.  Enter the highest 
FIL at which a fire is expected to occur in this particular FMAZ.  
The FIL is an integer, 1 through 6 allowed.  This value can be 
deduced from the /FPL-LEVEL2/ output.

    6.  Projected Average Annual Number of Fires by Fire 
Intensity Level.  (WORKSHEET 1) This is the output of the /FPL-
FREQ/ program as modified by the prevention option analysis for 
the FMAZ.  There are as many entries as the number of intensity 
levels entered above.  Decimal entries are acceptable, (such as 
5., .13 or 1.7).  Enter projections beginning with those for 
intensity level 1; separate entries by a comma.  If an intensity 
level has no fires predicted for it, enter a zero.

    7.  50th and 90th Percentile Rates of Spread.  (WORKSHEET 1.)  
In response to program prompts, enter the 50th and 90th 
percentile rates of spread for each intensity level.  These 
figures can be interpolated from the /FPL-LEVEL2/ output.  
Separate the entries with a comma.  Example:  6, 12.  

    8.  Number of Representative Fire Situations To Be Run for 
FMAZ and the Fraction of Projected Fire Load Represented by Each.  
(WORKSHEET 1.)  A maximum of 18 representative fires are 
permitted per FMAZ.  It is recommended that no more than 6 
geographical locations be selected in a FMAZ, with 1, 2, 3 fire 
dispatch situations represented at each.  Enter the number of 
representative fires followed by the fraction of the FMAZ's 
projected fire occurrence that each fire represents (separate by 
commas).  Example:  4,.15,.3,.40,.15 for a case where four fires 
are to be used; 15 percent of the projected occurrence will be 
represented by the first fire, 30 percent by the second, and so 
on.  Be certain that the sum of the fractions for the fires 
equals 1.00.  See section 84.2 for additional explanation.  

    9.  Fire Size at Time of Discovery.  (WORKSHEET 1.)  This is 
an estimate of the typical size of fires in the FMAZ when 
discovered.  The area is entered to the nearest .01 acre.  

    10.  Number of Dispatches To Be Sent to Representative 
Fire(N).  Enter the number of initial action dispatches 
designated as planned in the initial action suppression force for 
this fire.  This will be the number of lines completed on 
WORKSHEET 3.  The program will use, in order of arrival, only 
those designated and required for containment at the 50th and 
90th percentile rates of spread for each FIL.  A maximum of 30 
dispatches may be made to each representative fire.  

    11.  For Each Dispatch, Enter Number of Units, Attack Time, 
Line Production Rate, and the Lowest Intensity Level at Which It 
Is Dispatched.  (WORKSHEET 3.)  "Number of Units" is number of 
persons for crews if person handcrew rates are used; or number of 
crews if the crew production rates are used.  For other ground 
units, it is the number of identical units arriving at the same 
time (such as 3 engines (pumpers) or 2 dozers) if more than one:  
otherwise, enter 1.  For airtankers (fixed-wing or helitankers), 
enter 99 for number of units.  This is a "flag" to the program 
that the unit is an airtanker, and is not an indicator of 
capacity or number (one unit is assumed).  

Attack time is elapsed time in minutes from discovery until that 
unit begins work on the fire.  It is a combination of report, get 
away, and travel time for each unit.  

If showing an airtanker making a second drop (that is, drop--
return to base--reload--return and drop), list it as a second 
dispatch.  (The second attack time would be the total elapsed 
time from discovery to its second arrival).  

"Production Rate" is a function of the type of dispatch and 
applies to one unit of the attack force as entered in "number of 
units."  It is expressed as the rate of line construction, in 
chains per hour, for the kind of unit, fuel model, and slope as 
given in production rate tables.  The exception is for 
airtankers; enter the size of the drop in hundreds of gallons, 
e.g., for 1200 gallons, enter 12.  

Lowest intensity level is the lowest fire intensity level that a 
particular type of unit would be dispatched.  For instance, if an 
airtanker would not be ordered at intensity levels 1 or 2, then 
the appropriate entry would be a 3.  

Care should be taken that the simulated fires are 'attacked' in 
the same order as the workload fractions were entered in item 8.

84.2 - Output.  Program /FPL-IAA/ will, after the above entries 
have been made, print out the results from the initial attack 
sequence on the first set of simulated fires.  /FPL-IAA/ will 
then ask for these items for the second simulated fire, and so on 
through the number of fires as entered in section 84.17, item 8.  
After /FPL-IAA/ prints out the results for the last simulated 
fire, it asks:  "PRINT SUMMARY TABLES FOR ZONE FOR THE RUN?"  A 
"YES" answer will produce a tabulation of final sizes, 
probabilities, and expected annual frequencies of fires by 
location and intensity level (ex. 1) for the FMAZ.  It also 
provides expected average annual burned area by fire size class 
and intensity level (ex. 2) for the FMAZ and expected average 
annual number of fires by fire size class (ex. 1).  However, if a 
summary is not wanted for the FMAZ, enter "NO." But keep in mind 
that the results for the FMAZ thus far are erased.  The 
assumption, if a summary is not requested, is that the results 
were unsatisfactory.  

The operator will then be asked if the session is to be 
continued.  If the answer is "YES", choices for changing the 
input information are indicated by entering a number as follows:

    1.  All entries.  (Program starts from beginning.)

    2.  Fuel model, number of intensity levels and number of 
fires per intensity level.  If the number of intensity levels is 
changed, change the rate of spread entries).

    3.  Rates of spread.

    4.  Number of representative locations.

    5.  The list of forces dispatched to any location.

    6.  Fire size at discovery.

    7.  The option identifier.

    8.  Terminate program.  

After each change, with the exception of item 8, the operator is 
given the opportunity to make further changes.  When the answer 
is "NO", the program will return with the new values entered.  


                  SEE PAPER COPY FOR EXHIBIT 1


84.3 - Run/Lead Card Deck 

    (Demand mode)
    @RUN RUN-ID,ACCT-NO,FPLRRFF
    @ASG,A FPL-FIREPLAN*FPL-PROGRAMS.
    @XQT FPL-FIREPLAN*FPL-PROGRAMS.FPL-IAA
    o
    o (INTERACTIVE CHANGES)
    o
    FIN

(Batch mode) 

FPL-IAA may be run in batch mode with the following cards used in 
the run stream in place of the interactive exchanges:  

(Begin all entries in col. 1; separate multiple entries with 
commas; entries are free format with no right or left 
justification requires.) 

  C     Description           Data Type &            Example
  a                           maximum No. 
  r                           characters 
  d                           permitted
  1     FMAZ identifier       Alpha-Numeric (5)      ZONES
  2     MAX. fires size       Alpha                  Yes of NO
        modeled; if 300A 
        is OK, enter or 
        'YES' & skip 2A; 
        'NO'
  2     Max. fire size        Integer                175
  A     300A
  3     Option                Integer (3)            021
        identifier
  4     NFDRS fuel model      Alpha (1)              G
  5     Highest FIL for       Integer (1)            4
        FMAZ
  6     Avg. # fires per      Real or Integer        3.7.8.4.2  
        yr by Fil; # of                              .95
        entries must = 
        card 5
  7     50th & 90th           Real of Integer        2,5,6
  A     percentile ros; 
        2 entries for 
        FIL
  o
  o
  7     (Repeat for each 
  B     FIL, # cards 
        must   card 5)
  o
  o
  o
  8     Number of Rep.        Integer, Real          3,.6,.15-
        situations, &                                ,.25
        decimal fraction 
        of occurrence
  9     Size at               Real or Integer        .08
        discovery
  1     Number                Integer                5
  0     dispatches to 
        first Rep. fire 
        situation
  1     Individual            INT.,INT.,INT.         2,35,2.5-
  1     dispatch Data;                               ,2
  A     one card for 
        each Real, 
        Integer  or line 
        on WORKSHEET 3
  1     (Number of cards 
  1     must = card 10)
  B
  o
  o
     (Repeat card series 10 and 11 for each representative 
     fire)
  1     PRINT SUMMARY         Alpha                  YES or NO
  2     TABLES?
  1     MAKE ANOTHER          Alpha                  NO
  3     RUN?
        (A "YES" entry requires a series of inputs in a mode 
        designed for interactive response to make program 
        entry changes.  In a batch entry changes.  In a batch 
        run, it is more efficient to rerun the program with 
        individual cards changed.   A "NO" entry will 
        terminate the program).

84.4 - Data Entry From File.  To facilitate making successive 
batch or demand runs with changes in the data, it is suggested 
that a user file be created and the responses be listed in it for 
use by FPL-IAA in place of the individual data cards.  Changes in 
input data can be quickly made to the file by the text editor.  

84.5 - Diagnostics.  

    **** DATA ENTRY PROBLEM.  PLEASE REENTER DATA **** 

    Action:  From main program. If in demand mode, reenter data 
item(s) in error upon program prompt.  If in batch mode, run may 
terminate with FTN I/O error or read wrong data for item(s).  If 
batch mode, correct card in error and rerun FPL-IAA.  

    ** WARNING ** LOCATION ?? FIL ?? REPRESENTS A HIGH FIRE 
FREQUENCY AND MAY GIVE INVALID RESULTS.  

    Action:  This is a warning that a given specific 
representative fire situation (FIL and rate of spread) will 
represent an expected annual frequency of more than 5 fires.  If 
the outcome of the simulation for that situation is a large fire, 
the total number of large fires represented may be unrealistic.  
If this is the case, one or more additional representative 
locations should be designated for that FMAZ, and the number of 
fires in the FMAZ redistributed among them.

85 - UTILITY ROUTINES.  The routines listed herewith are 
designated to perform a variety of calculations and data handling 
operations to facilitate various steps in the level 1 and level 2 
analysis.  

85.1 - FPL-FIREPLAN*FPL-PROGRAMS.FPL-MATCHDAY.  This program is 
used to generate a listing of fire report records lacking 
corresponding fire weather data for one or more weather station.  
This program should be executed after fire report data and 
weather data have been retrieved from their respective libraries.  
Inputs to this program are mass storage data files containing 
fire report records and weather station records from component 
programs in sections 83.1 -- .3 respectively.

85.11 - Lead Cards.  None.

85.12 - Outputs.  For each fire weather station, 2 types of 
outputs are produced.  

    1.  Listing of fire report records lacking corresponding fire 
weather data.

    2.  Summary of the number of fires by fire size class having 
and lacking fire weather data.  

85.13 - Diagnostics.  If either of the fire report records or the 
weather records contain alpha-numeric data in numeric only 
fields, an error message is printed identifying the record number 
of the erroneous record in the appropriate file.  Records in 
error are ignored.  The user is encouraged to correct any errors 
before proceeding any further into the analysis.  

85.14 - Run/Lead Card Deck

123456789012345678901234567890123456789012345678901234567890 

@R@RUN,L RUN-ID,ACCOUNT,FPLRRFF,5,500
@ASG,A FPL-FIREPLAN*FPL-PROGRAMS.
@ASG,A FPLRRFF*REPORTS-RETR.
@USE 7.,FPLRRFF*REPORTS-RETR.
@ASG,A FPLRRFF*GETDATA2-WX.
@USE 9.,FPLRRFF*GETDATA2-WX.
@ASG,T 8.
@XQT FPL-FIREPLAN*FPL-PROGRAMS.FPL-MATCHDAY 

85.2 - FPL-FIREPLAN*FPL-PROGRAMS.FPL-MULTIDAY.  This program is 
used to generate a report depicting multiple fire occurrences 
stratified by year and month.  Multiple fire occurrences are 
partitioned into 20 classes -- 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11-
20, 21-30, 31-40, 41-50, 51-60, 61-70, 71-80, 81-90, 91-100, and 
101 or more fires on a given day.  The number of fires and acres 
burned by fire size class are given for each fire occurrence 
class.  A report is printed only for months and fire occurrence 
classes having nonzero entries.  The fire reports mass storage 
data file created in section 83.1 is used as input to this 
program.  

85.21 - Lead Cards.  None.

85.22 - Outputs.  Three types of reports are produced.  

    1.  Monthly report of multiple fire occurrences.  

    2.  Yearly.
    3.  Total for all years of record.  

85.23 - Diagnostics.  If alpha-numeric data is encountered in a 
field that is designated as numeric only, then an error message 
will be printed identifying the record number in error on the 
input data file.  Records in error are ignored in the analysis.  

85.24 - Run/Lead Card Deck

123456789012345678901234567890123456789012345678901234567890 
-----------------------------------------------------------------
-----------------------------------
@RUN,L RUN-ID,ACCOUNT,FPLRRFF,5,200
@ASG,A FPL-FIREPLAN*FPL-PROGRAMS.
@ASG,A FPLRRFF*REPORTS-RETR.
@ASG,T 9
@USE 7.,FPLRRFF*REPORTS-RETR.
@XQT FPL-FIREPLAN*FPL-PROGRAMS.FPL-MULTIDAY 

85.3 - Utility Sort/Merge for Adding Fire Data.  The following 
runstream will get data from the fire report library extract file 
REPORTS-RETR and from the add missing fires file ADDMISS-FIRE and 
will merge the two files to produce a new fire report data file 
REPORTS-RADD.  Replace the file name REPORTS-RETR with REPORTS-
RADD in the run set up for program FPL-AREA to insert user 
assigned values for the combined fire report data file.  

See FIRE REPORT PASSING file format for FIREPLAN, section 82.12a, 
exhibit 1, for format to prepare fire report data.  Only columns. 
1-60 are used.  Information in columns. 61-78 is added to the 
file via program /FPL-AREA/.  Information in column. 79 is added 
to the file by program /FPL-LEVEL1/.  

@RUN,L        RUN-ID,ACCT-NO,FPLRRFF,5,200
@ASG,CP       FPLRRFF*ADDMISS-FIRE.
@DATA,IQL     FPLRRFF*ADDMISS-FIRE.
**MISSING FIRE DATA RECORDS** 
    .      .    .      .
    .      .    .      . 
@END
@FREE         FPLRRFF*ADDMISS-FIRE.
@ASG,A        FPLRRFF*REPORTS-RETR.
@ASG,A        FPLRRFF*ADDMISS-FIRE.
@ASG,CP       FPLRRFF*REPORTS-RADD.
@TASG         XA.,512             . SORT SCRATCH FILE
@SORT,S
RSZ60 LABEL=NONE
MODE=SDF
DATA=ASCII
RECORD=5                          . THOUSANDS OF RECORDS INPUT
FILESIN=REPORTS-RETR,ADDMISS-FIRE
FILEOUTREPORTS-RADD
KEY9,14,S,A,1                     . DATE
@EOF 

85.4 - Utility Sort/Merge for Adding Weather Data.  The following 
runstream will get data from the fire data library extract file 
GETDATA2-WX and from the add missing WX  file ADDMISS-WX and will 
merge the two files to produce a new WX data file GETDATA2-WXA.  
Replace the file name GETDATA2-WX with GETDATA2-WXA in the run 
set up for program FPL-MOIST to generate fuel moistures for the 
combined WX data file.

See appendix B (format of AFFIRMS archived fire weather data), 
'The National Fire Weather Data Library:  What it is and how to 
use it', (Furman and Brink, 1975), RM-19.  Only columns. 1-61 are 
used.  Cols. 20-22, 1-hr T/L moist and columns. 36-38, 100-hr T/L 
moist may be blank if data is unavailable.  

@RUN,L        RUN-ID,ACCT-NO,FPLRRFF,5,200
@ASG,CP       FPLRRFF*ADDMISS-WX.
@DATA,IL      FPLRRFF*ADDMISS-WX. 
**MISSING WX DATA RECORDS** 
    .     .   .     .
    .     .   .     . 
@END
@FREE         FPLRRFF*ADDMISS-WX. 
@ASG,A        FPLRRFF*GETDATA2-WX. 
@ASG,A        FPLRRFF*ADDMISS-WX. 
@ASG,CP       FPLRRFF*GETDATA2-WXA. 
@TASG         XA.,512             . SORT SCRATCH FILE @SORT,SM
RSZ=80
LABEL=NONE 
RECORD=5                          . THOUSANDS OF RECORDS INPUT
FILESIN=GETDATA2-WX,ADDMISS-WX
FILEOUT=GETDATA2-WXA
KEY1,12,A,A,1                     . WX STANBR-DATE
@EOF

85.5 - FPL-FIREPLAN*FPL-PROGRAMS.FPL-FUEL.  Calculates the 
present value of the cost and net value change of a prefuel 
treatment fire program option, and an option based upon fuel 
treatment.  A comparison of the two values provides information 
on the probable economic efficiency of making the fuel treatment 
investment.  

The program calculates present value at a 4 percent discount 
rate, and a rate which may be selected by the user.  It assumes a 
straight line change in annual costs and annual net value changes 
(from pre to post) over the transition period of fuel treatment 
work.  

85.51 - Inputs.  The program is written for interactive mode, but 
may be run batch.  Inputs are the annual cost and net value 
change of a preferred efficient fire program option that does not 
involve fuel treatment investment; the annual cost, including 
fuels program maintenance, and net value change of the fire 
program option proposed for the situation after the fuel 
treatment; and the average annual fuel treatment investment and 
number of years proposed for that investment.  The C+NVC are 
developed from runs of /FPL-IAA/.  All costs are entered in 
thousands of dollars.  

85.52 - Outputs.  Annual costs are discounted to present value 
and summed for the "Pre" (or no) treatment program option and the 
fuel treatment investment plus post treatment program option.  
The program with the lowest present value is the more efficient.  

85.53 - Run/Lead Card Deck.  

    @RUN RUN-ID, ACCT#, FPLRRFF
    @ASG,A FPL-FIREPLAN*FPL-PROGRAMS.
    @XQT FPL-FIREPLAN*FPL-PROGRAMS.FPL-FUEL
       o
       o (INTERACTIVE EXCHANGES)
       o
    @FIN

In batch mode, use following cards in place of interactive 
exchange.  (Entries, except card 4, are free format.) 

 CARD    DESCRIPTION             DATA TYPE   MAX.#CHAR    EX. 
 1       Program Descriptions    I           1           1
 2       C+NVC "Current"         R of I      8           250.6
         Program ($000)
 3       C+NVC Post Treatment    R or I      8, 8, 2     175,-
         Program; Avg Annual                             15.7-
         Fuel Investment; # yrs                          ,8
         of Investment
 4       2nd Discount Rate       R (or       3           .075
 op-                             blank)
 tion-
 al
 5       RE-RUN Program Option.  I           1           1
         Enter 1 if Additional 
         Data is to Follow;  
         Otherwise 2

(If additional data is to be run, repeat cards 2 through 5.)

86 - FILE MANAGEMENT.  Mass storage files created with the UP or 
CP option on the ?ASG card will be purged after 6 days.  
Hopefully, analysis can be completed in this time frame and the 
files can be allowed to die naturally.  

The following files need not be saved if one is successful in 
getting through program /FPL-SORT/.  
    FPLRRFF*REPORTS-RETR.
    FPLRRFF*REPORTS-AREA.
    FPLRRFF*REPORTS-LEV1.
    FPLRRFF*GETDATA2-WX.

Consider saving the following files for as long as it takes to 
complete the fire planning on the forest.  

    FPLRRFF*REPORTS-SORT.
    FPLRRFF*FUEL-MOIST.
    User-created files for inputs to FPL-IAA.

FPLRRFF*MOIST-NNNNN, if created for use by /FPL-LEVEL2/, need 
only be saved until the /FPL-LEVEL2/ runs for management area 
NNNNN are completed.  

Do not retain files for any longer than needed.  The space is 
needed for other uses.