Defining Agreement Thresholds
Thresholds define the points at which an agreement should start escalation events, and the point at which an agreement is breached.
Thresholds define the points at which an agreement should start escalation events, and the point at which an agreement is breached.
Thresholds are based upon matrices, which are defined by your administrator. You can define IPK and Workflow Thresholds for SLAs, OLAs, and UCs.
A matrix is a table containing threshold times. The actual times in the matrix are (usually) based upon Priority, and either Config Item or Problem Type.
For example: A matrix may set the breach time at 30 minutes for all high priority calls and 60 minutes for lower priority calls, but calls with a CMDB Type of Server have half those times.
Thresholds are defined for agreements by applying matrices to escalation and breach times. Escalation times should always be lower than breach times. Remember, escalations are warnings that occur within a system to prevent agreements from being breached. If your escalation times are the same as your breach times, calls will not escalate until it is too late, that is, when an agreement breach has occurred.
Rather than setting up many complicated matrices based on different types and levels of escalation and breaches, ASM Core lets you apply factors to a matrix. Factors are numbers that multiply all the existing times in a matrix by a certain amount.
For example: You might have an agreement breach matrix for SLAs defined by your administrator. You want to set up breach and escalation times based on that matrix for your current agreement. You are using Three Level Resolve Escalation. Let us assume for the purpose of this example that the matrix you are applying has one time, 100 minutes, for all combinations of Problem and Config Item Types.
You want to set first level escalation to occur at 40 minutes, second level to occur at 60 minutes and third level escalation to occur at 80 minutes. The agreement is breached at the 100 minute mark (that is, if the call has not been resolved by 100 minutes).
To do this, you don’t need multiple matrices for each of these escalation levels. You would just apply the same matrix at 1st, 2nd and 3rd escalation levels with a factor of 0.4, 0.6 and 0.8 respectively. The table below shows how this works.
| Event | Base Matrix Time | Factor | Final Time |
|---|---|---|---|
If you set a factor for a particular escalation or breach time, that factor is used as a multiple against the base time for that matrix.
Factors can be any positive number. If you are using an escalation matrix for a breach time, you should apply a larger number as a factor (say two or three).
If you are doing it the other way around and using a breach matrix for escalation times (such as in the above example), you should definitely use a small number (between zero and one) to ensure your escalation times are below your agreement breach times.
By default, all factors are set at one (i.e., exactly the same as the original matrix time). You don’t have to use factors; your administrator may create specific matrices for different escalation types and escalation levels instead.
If a threshold setting does not apply to the current agreement type, it is disabled (for example if you create an OLA or UC, the threshold settings for Response, First Call Back are disabled).
If you create an SLA, you can set the Resolve, Response, and First Call Back thresholds.
If you create an OLA, you can set the Resolve and Action thresholds.
If you create a UC, you can set the Resolve and Action thresholds.
Action events start when the call/task to which the OLA or UC is applied is forwarded internally or externally.
Familiarize yourself with the concepts behind matrices and factors.
In the Explorer pane, expand Agreement, then select IPK Thresholds or Workflow Thresholds.
Select the Edit icon in the toolbar to activate the fields if necessary.
The Thresholds window is divided into two parts:
4. Select a breach threshold checkbox to activate it. This activates the selected breach threshold for the agreement and enables the other options in the row.
5. Complete the details.
6. After you have finished configuring the agreement breach events, select the Save icon.
Familiarize yourself with the concepts behind matrices and factors.
In the Explorer pane, expand Agreement, then select IPK Thresholds or Workflow Thresholds.
Select the Edit icon in the toolbar to activate the fields if necessary.
The Thresholds window is divided into two parts:
4. Select a breach threshold checkbox to activate it. This activates the selected escalation threshold for the agreement.
You can enable one, two or three levels of resolve escalation (if they are enabled for your system).
5. Complete the details.
6. After you have finished configuring the escalation events, select the Save icon.
Lvl 1 Esc.
100 minutes
0.4
40 minutes
Lvl 2 Esc.
100 minutes
0.6
60 minutes
Lvl 3 Esc.
100 minutes
0.8
80 minutes
SLA Breach
100 minutes
1 (default)
100 minutes
Breach Definition
Here you apply matrices for Resolve, Response, First Call Back, and Action agreement breaches. You must enable these options or define breach times for this agreement to create breach events.
For IPK Thresholds, there are four rows in this section, corresponding to Resolve, Response, First Call Back, and Action agreement breach times. Depending on how your agreements are defined, you may need to have some or all of these enabled for the agreement you are creating.
For Workflow Thresholds, there are two rows in this section, corresponding to Resolve and Action agreement breach times. Depending on how your agreements are defined, you may or may not need to have this enabled.
Escalation Definition
Here you can set times for Resolve, Response, First Call Back, and Action escalation
Use Matrix
Select the matrix you want to use.
On the IPK Thresholds window, this list displays only Call matrices.
On the Workflow Threshold window for SLAs, this list displays only Request matrices. For OLAs and UCs, this list only displays Task and Approval matrices.
Factor
Specify a factor. The default is 1. The factor can be any positive number, and will be multiplied by the numbers in the matrix. Therefore, if you apply a factor of 0.5, the times in the matrix will all be halved to determine the breach times for this agreement.
Recipients
Define the recipients for the breach.
You can only define recipients if the Agreements option is selected on the Service Level Management Settings window. Otherwise, the Recipients button is disabled.
Breach Definition
Here you apply matrices for Resolve, Response, First Call Back, and Action agreement breaches. You must enable these options or define breach times for this agreement to create breach events.
For IPK Thresholds, there are four rows in this section, corresponding to Resolve, Response, First Call Back, and Action agreement breach times. Depending on how your agreements are defined, you may need to have some or all of these enabled for the agreement you are creating.
For Workflow Thresholds, there are two rows in this section, corresponding to Resolve and Action agreement breach times. Depending on how your agreements are defined, you may or may not need to have this enabled.
Escalation Definition
Here you can set times for Resolve, Response, First Call Back, and Action escalation
Use Matrix
Select a matrix to use for the escalation. If you are unsure what to use, select Use Breach Matrix to automatically select and apply the matrix chosen for that type of breach.
If you pick ‘Matrix A’ as a First Call Breach matrix, selecting the Use Breach Matrix option will automatically select ‘Matrix A’ for the First Call Back escalation matrix.
Factor
Specify a factor to use with the matrix. Similar to breaches, this number will be used as a multiplier against all the numbers in the matrix to calculate the escalation times. It is likely you will use a factor of 1 for the Breach Definition and small multiples (such as 0.5 or 0.3) for escalation times. Alternatively, you could use a large factor (such as 5 or 10) for the Breach Definition and a factor of 1 for the Escalation Definitions.
Ensure that your escalation times are always below your breach times. Otherwise, calls will not escalate until it is too late (that is, once the agreement has been breached).
Min. Minutes
Type a number that will be used as a minimum time for that escalation type. Any time from the escalation matrix that (after being multiplied by the factor) is smaller than the min. minutes time is set to that time.
Minimum times are useful if you want to use a matrix and a factor for breach and escalation times, but want to ensure that no completely unrealistic times are applied to agreements.
If you have a matrix sorted by problem type and with times of one hour, two hours and four hours for high, medium and low priorities. Your factor is 0.5, and you set min. minutes to 60. High priority calls have a time of half an hour (one multiplied by 0.5), but that is set to one hour so it meets the minimum time. Medium and high priority calls are set to one and two hours respectively are being multiplied by their factors; these meet the minimum time, so are unaffected.
Recipients
Define the Recipients for the breach.
You can only define recipients if the Agreements option is selected on the Service Level Management Settings window. Otherwise, the Recipients button is disabled.