|
|
|
|
|
About Decisions
WFDSS replaces the WFIP, WFSA, and LTIP processes for developing risk-informed decisions and preparing decision documents related to wildland fire incidents.
Risk-informed decision making requires two distinct but linked processes: analysis and deliberation. Analysis involves the rigorous, replicable methods to provide information about factual questions. While analysis brings new information into the decision making process, it informs the deliberation. Deliberation is the discussion, reflection, and persuasion to communicate, raise issues, collectively consider issues, increase understanding, and facilitate substantive decisions. New analyses are framed as deliberation brings new insights, questions, and problem formulations.
Figure 1: Risk Informed Decision Process WFDSS
The top portion of the slide shows a risk informed decision process through analysis and deliberation. The blue strip at the bottom of the slide shows the WFDSS decision flow process and how it lines up with the deliberative risk informed decision process. In WFDSS the INFORMATION tab is the Problem Formulation of risk informed decision making. SITUATION and OBJECTIVES provide the Information Gathering and Analysis of the risk informed process. The COURSE OF ACTION is the Synthesis. RATIONALE is the Thought Process and Affirmation of Analysis results. DECISION SUMMARY is the Application-Decision Implementation. REPORTS aligns with the Archival Documentation.
-----------
Last updated on 5/16/2018 10:32:13 AM.
WFDSS is the system of record for creating, compiling, and publishing a decision related to wildland fire incidents. The WFDSS Decision ensures that a fire incident is managed using the latest science, relative risk assessments, and fire model data. Incident owners create a pending decision using the WFDSS application when an incident escapes initial attack, grows significantly in cost and/or resource use, or requires a new course of action. The Decision is reviewed and approved for each incident by designated reviewers and approvers. When a decision is approved it is a Published Decision.
The Decision includes information about the following:
- Incident. This includes name, unique identifier, responsible agency, location, and discovery date/time.
- Situation. Multiple mapping layers can display how fire perimeter growth impacts landscape values or points of interest. Incident owners can run Basic and Short Term Fire Behavior analyzes, view objectives, Energy Release Component (ERC) graphs, and/or current weather.
- Objectives. The incident owner designates incident-specific objectives and requirements that satisfy guidance found in Strategic Objectives and Land Management Plans.
- Course of Action. The incident owner develops a strategic plan to manage the fire. This includes costing estimates and any additional actions required to implement the strategic plan.
- Cost. Estimated Final Cost can be documented as well as the cost estimation method used to derive it.
- Decision List. The incident owner reviews/edits the list of reviewers and approvers, creates and checks in the decision, and submits it for review and/or approval.
GA Editors, Dispatchers, Incident Owners, and decision approvers work together in order to publish a decision.
Incident owners are responsible for completing and compiling the required documentation before beginning the review/approval process for an incident decision. For Decisions using the Advanced and the Default Editor, at the top of the Decisions page there is a section titled Requirements that must be completed before the pending decision can be Reviewed / Approved. Users can also use the requirements fly-out menu on the right to ensure all required components are completed
The Default Editor also contains the vertical tab Decision Requirements that contains a list of items that need completed prior to beginning the Review/Approval Process. It contains a list of tasks that must be completed before a decision can be reviewed and approved. The list is generated when you initially create a decision and it updates automatically, as you develop and save inputs. The list below contains items from the list and links to topics that can help you complete each task:
- Enter the Unique Fire Identifier for the incident. (See Editing Incident Information.)
- Enter the Incident Size greater than 0 Acres. (See Editing Incident Information.)
- Draw a Planning Area. (See Creating Planning Areas.)
- Develop a relative risk assessment. (See Calculating Relative Risk.)
- Complete the Organization Assessment.
- Designate at least one approver for the decision. (See Assigning Incident Privileges.)
- Include at least one FMU from the list of FMUs for the incident. (See Manually Add FMU to Incident FMUs or Creating Planning Areas.)
- Include incident objectives and requirements. (See Creating Incident Objectives and Requirements.)
- Identify and include at least one action item for the course of action. (See Estimating Final Cost for an Incident .)
- Estimate a Final Cost on the Cost page. (See Completing a Course of Action.)
- Create a Pending Decision from Decision page. (See To document a decision.)
- Add content to the "Rationale" section of the decision (See Editing a Decision.)
- Publish a Pending Decision by review and approval of the decision by designated approver(s).
- As you proceed through the development of a decision, you can check this list periodically to determine which tasks have yet to be done. If all requirements have been met, a message appears in the list that states the minimum system requirements for the pending decision have been satisfied.
Incident Owners and Editors use the Decision Editor to add supportive text, images, and information to a decision document before it is published. This support information explains why actions were taken during the incident that help control the incident and declare it out.
When a decision is submitted for review and or approval, the owner approver and reviewers all receive email notification when the decision becomes reviewable.
In This Section |
See Also |
Reference |