Finding out when a User-Specified Late Time (SLA) Applies

Users can specify a given time of day as late criterion for a jobstream. The specified late time is not qualified with a “relative day”, as it relates to the beginning of the job stream. Automic Automation Intelligence must “figure out” which day the SLA applies to using some kind of logic.

Example

For a jobstream that typically starts at 21:00 on Monday and ends at 08:00 Tuesday, the user sets the late criterion to 03:00.

Handling

Automic Automation Intelligence can reasonably assume that, given the average jobstream duration and the start time, the SLA is NOT likely to be interpreted as 03:00 on Monday (since the stream starts well after that time).

It is feasible that the user intends the SLA (03:00) to apply to Tuesday, and the jobstream historically finishes 5 hours “late”.

It is also feasible that the user intends the SLA (03:00) to apply to Wednesday, and the jobstream historically finishes 19 hours “early”.

Automic Automation Intelligence must make a determination if the SLA is for Tuesday or Wednesday by some method.

The method that Automic Automation Intelligence uses is:

If the average jobstream run duration is less than or equal to 12 hours, the SLA applies for the “current” day – the same day on which the jobstream finishes.

If the average jobstream run duration is greater than 12 hours, the SLA applies for the “next” day – the day after the jobstream finishes.

Therefore:

Modifying the “max jobstream run duration” has the effect of recalculating the average jobstream run duration by rebuilding the jobstream run history.

When the user sets the max jobstream run duration to a value that causes the average jobstream run duration to be less than or equal to 12 hours, the SLA is assigned to the “current” day – the day on which the jobstream normally ends.

When the user sets the max jobstream run duration to a value that causes the average jobstream run duration to be greater than 12 hours, the SLA is assigned to the “next” day – the day after which the jobstream normally ends.

Configuring an Override

Automic Automation Intelligence has the ability for the user to override this behavior on a per-jobstream basis. By selecting the “options” button from the “Late Criterion” tab, you can “override automatic calculation” and enter “1” day to the field labeled “jobstream completes N calendar day(s) after jobstream starts”.

Note: Each jobstream is unique and this should only be configured when it is clear that the jobstream in question is encountering this 12-hour boundary condition and AAI is miscalculating the day on which the late time falls.