The metric forecast is calculated once when performing a Commit of the contract version by having the calculation engine calculate the contract once in a forecast mode. The Forecast mode is performing a full calculation engine cycle on the contract (from the start to the end date of the contract version). The purpose of this cycle is to calculate the forecast values only. (There are no calculations are done on the T_RAW_DATA table).
In Forecast mode the calculation engine calculates the business logic of the forecasted metrics only.
All the Business Logic methods are calculated (excluding Result and Target) in the same order as in a regular cycle.
The differences between a Forecast mode cycle and a regular cycle of the calculation engine are:
Note: Forecasted events are intermediate events that are added in Forecast mode. This means that these events are written by other forecasted metrics during the forecasted cycle. These events are located in the T_INTERMEDIATE_DATA table and are marked with CALCULATION_MODE=FORECAST.
Note: It is the user's responsibility to commit the contract in the right order. This means that if one contract contains a metric that sends forecast events to another metric from a different contract, the sending metric should be calculated first. Therefore, the contract should be committed first. There is no problem when both metrics are in the same contract.
Note: It is possible to simulate the Forecast mode from the Business Logic Scope page by setting the Forecast Calculation check box. The Business Logic Scope page in this case displays the Forecast method results.
|
Copyright © 2013 CA.
All rights reserved.
|
|