> > >
Use this form to create and manage forecast models. A forecast model names and identifies a specific forecast.
You can define a forecast model in two levels, so that one model includes one or more other models, or submodels. This allows you to aggregate the individual forecasts. When you run forecast scheduling for a top-level forecast model, the program calculates gross requirements for all models that are designated as submodels.
Note
|
|---|
|
You must define all forecast models before you can designate one or more models as submodels of a forecast model. A forecast model that is used as a submodel cannot contain other submodels. A forecast submodel uses its own parameters, not those of the top-level forecast model. |
Tasks that
use this form
Navigating
the form
The following tables provide descriptions for the controls in this form.
Tabs
|
Tab |
Description |
|---|---|
|
|
View a list of the existing forecast models. |
|
|
View a list of any designated submodels for the selected forecast model. |
Fields
|
Field |
Description |
|---|---|
|
|
Assign a unique identification to the forecast model. You can use both numbers and letters. |
|
|
Assign a name to the model or submodel. |
|
|
When this check box is selected, you cannot edit the forecast lines with which the model is associated. |
|
|
When this check box is selected, the forecast lines that the model is associated with generate cash flow forecasts in the section. Note that cash flow forecasts are not generated for projects. |
|
|
Designate one or more submodels for the selected forecast model. |
|
|
Use the project date to budget the invoice revenue date. |
|
|
Budget with WIP (work in process) on time and material projects. |
|
|
Budget with WIP (work in process) on fixed price projects. |
|
|
Budget with WIP (work in process) on investment projects. |
