SLA and Process Statuses

It is important to understand how SLA assigns status to Processes it monitors because there are two ways that SLA sets Process status. The first has to do with predicted start and end times, and the second has to do with actual start and end times.

Note: "Status" here refers to the status reported in the Status column on the SLA Dashboard screen, not the regular Process status.

Predicted Process Statuses

The SLA Extension keeps a history of the actual start and end times of each Process that is monitored by an SLA Rule. Using this information, RunMyJobs predicts when the next execution of the Process will occur and sets the Process status accordingly. This typically occurs at the beginning of a day, but the time may vary because RunMyJobs updates its prediction calculations every minute. Having this information in advance lets you intervene if necessary to get the Process back on track.

The predicted Process statuses are:

• Not Started: The Process is forecast to start (for SLA for starttime rules) or end (for SLA for endtime rules) within the Lead Offset but before the SLA Deadline.

• Not Started Late: The Process is forecast to start or end within the Late Offset (after the SLA Deadline).

• Not Started Very Late: The Process is forecast to start or end after the end of the Late Offset. In other words, the Process is predicted to end in status Missed.

Final Process Statuses

When a Process that is monitored by an SLA Rule actually starts or finishes, its status is set as shown in this diagram.