search cancel

Incorrect results for different types of forecast

book

Article ID: 134407

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Incorrect forecast results when calculating the forecast using Actual Entries, Fixed Values, and Estimated Run time values.

To reproduce: 

1. Right-click on a jobs in AWI 

2. Select "create forecast" 

3. Create forecast with 3 following options for Runtime Calculation for Groups: Consider actual entries, Use ERT of the group, Use fixed value (5 minutes) 

4. Compare the results All results appear to be the same in all 3 cases.

Cause

By-design:

If there is no JOBG (jobgroup) involved, the ERT of the child tasks is always used. The only option that is relevant when creating a forecast on workflows is to Change the logical start time. 

Environment

Release : 12.0.X, 12.1.X, 12.2.X, 12.3.X

Component : AUTOMATION ENGINE

Resolution

By-design. If, JOBG is not involved, ONLY logical start time (actual entry for ERT) will affect the forecast (child objects of WF).

Additional Information

Examples: 

In the export attached, there is a workflow with 1 JOBS and 1 JOBG (ERT for the JOBS is 29 seconds).

Here are how the functionality works if JOBG is involved:

1. For ‘Consider actual entries’ 

-- Uses the ERT of the JOBS (will be 29 seconds on the forecast), not the JOBG

2. For ‘Use ERT of group’

-- Uses the ERT as defined in the JOBG object (runtime is set to 2 minutes on JOBG, so in forecast ERT for JOBG is set for 2 minutes, and on JOBS – 29 seconds, so Estimated End will be 2 minutes after the forecast was created)

3. For ‘Use fixed value’

-- Uses the ERT entered on the forecast (ERT will be 5 min on the forecast – so Estimated End will be minutes after forecast is created)


If, JOBG is not involved (if you remove JOBG from the workflow), ONLY logical start time (actual entry for ERT) will affect the forecast (child objects of WF)

Attachments

1569969149741__Forecast_Examples.xml get_app