Skip to main content
PDWare Customer Success Center

09. Analyzing and Using Scenarios

This article describes how to analyze the impact of scenarios, how to create useful views for scenarios, and how to export/import scenarios.

Overview


There are many ways to leverage scenarios in ResourceFirst. In addition to the front end features, you have the the ResourceFirst reporting engine powered by QlikView®.

Terminology Note: The terms "current plan" and "current forecast" both refer to normal project and assignment records (rows) that are not part of a scenario.

Scenario Views

Reminder: Scenarios contain projects; assignments are included in scenarios by virtue of being on scenario projects.

The project and assignment (labor and financial) system fields relevant for scenario views are as follows:    [These are system field names, NOT configured column titles]

PID, ORIGINALPID, PSCENARIONAME, PSCENARIOSTATUS, PSCENARIOVERSION

AID, ORIGINALAID

Note: Fields can be laid out in any order with the Edit Views dialog. The order shown here is useful but not required.

Assignment Scenario Views

When you create an assignment view, public or personal, you can "map" project fields into the view, along with native assignment fields.

clipboard_ea32ced6d0bf61d1dcc31e7eb480a3875.png

Row 1 is an assignment (AID = 172) in the current forecast on the project with PID (Project ID) 18. It has no background color and the font is normal.

Row 2 is an assignment (AID = 7507) on scenario project PID 446. Scenario project PID 446 is a scenario for current forecast project PID 18. Row 2 has no ORIGINAL AID which means it was created new directly in the scenario project. If this scenario is posted to the current forecast, this assignment will be added to project PID 18.

Row 3 is an assignment (AID = 7350) on scenario project PID 446. This assignment has ORIGINAL AID 172 which means it was created from the Row 1 assignment.  If this scenario is posted to the current forecast, this assignment will overwrite the current forecast for original assignment 172.

It is NOT necessary to include all system scenario fields in your views but they are available when useful.

Project Data Scenario Views

Every project scenario record has an ORIGINAL PID value. Every scenario has only 1 instance of an ORIGINAL PID value, i.e., scenarios contain only one copy of original projects.

clipboard_e3732772eec81886951f2458e695d81cd.png

 

A current plan project can be included in multiple scenarios at the same time. BE CAREFUL USING THIS CAPABILITY!  This also provides the opportunity for confusion and mistakes.

clipboard_ed150de7ede065e50f63abf81e33ef333.png

("What-If") Scenario Pages

The (What-If) Scenario pages have some features in common, including scenario features. See the Financial (What-If) Scenario and Project (What-If) Scenario articles for a full explanation of the features that are not related to scenarios.

There are two features that interact when analyzing scenarios on the What-If Scenario pages.

The Show checkbox on the scenario control dialog/pane.

clipboard_efa2119b0bcaedf2db4a2722928cb7c8f.png

The scenario/forecast selection drop down on the What-If Scenario page.

clipboard_e6fa5ed4ea8ef05117b9f7a4ece4ed81d.png

The Show checkbox defines which scenarios are included in rollup calculations on the Scenario page.

The drop-down selections define what to include from the data that are present for rollup.

 All Data

clipboard_ea7de1f20575e095e07e3cc3861285000.png

Forecast Only

clipboard_e047173794e3257e9f2fec1b557d41046.png

 Scenario Only

clipboard_e11195c3f5e98ffd90de4781d142cafff.png

Combined (as if scenario(s) are posted)

clipboard_e11195c3f5e98ffd90de4781d142cafff.png

Variance

clipboard_e594347e4eac5b43189a7075654af7940.png

  • Was this article helpful?