Service Level Targets
A service level targetA distinct measurement of service to be provided based on time and percentage of compliance: delivery target, response target, and resolution target. (SLT) is a key element of a service level agreementAn agreement between the service provider and the customer documenting the agreed upon service levels for the service. between a service provider and a customer. Service level targets are agreed as a means of measuring the performance of the service provider and are outlined as a way of avoiding disputes between the two parties based on misunderstanding.
In HEAT, targets are linked to service level packageThe level of service provided to a customer. A defined level of utility and warranty for a particular service package. Each service level package is designed to meet the needs of a particular pattern of business activity.s, service level agreements, and request offeringA service item offered by a provider that an end user can request through the Service Catalog. For example, "Request for a new mailbox," and "Quarantine" are request offerings under the Email service.s. For example, you can have general targets linked to a service level package (such as, promise to respond to an email within 24 hours), but have specific targets linked to a request offering (such as, promise to send a new phone within 5 days).
HEAT provides the following targets:
- Delivery Target: How soon can the request be delivered. Primarily for service requests. Results from the duration component are used to evaluate compliance of the service request delivery target and the overall service level agreement target.
- Response Target: How soon can the provider respond to a customer request. Primarily for incidents. Information about whether the target duration was met or exceeded is used to evaluate the compliance of both the incident response target and the overall service level agreement target.
Resolution Target: When can the issue expect to be resolved. Primarily for incidents. Results from the duration component are used to evaluate compliance of the incident resolution target and the overall service level agreement target.
- Overall Compliance: This target aggregates compliance information (that is, duration met/not-met data) from service level targets for all incidents and service requests that fall under the service level agreement.
- If the aggregated met/not-met data for all service level targets results in a percentage that meets the overall service level agreement compliance target, the service level agreement is in compliance.
- If the aggregated met/not-met data for all service level targets results in a percentage that is below the overall service level agreement compliance target, the service level agreement is considered to be out of compliance.
- You specify the overall compliance target when you create a service level package, and an service level agreement inherits the target when the package is subscribed to and the service level agreement is created.
The Delivery, Response, and Resolution targets have two components:
- Duration target: Measured in days, hours, and minutes. The target time for an incident or request to be assigned to a Service Desk Analyst for resolution.
- Compliance target: A running percentage of the times that the target duration was not exceeded. Separate compliance targets exist for the response target and for the overall service level agreement target.
This example is based on two incidents and one service request, which were all submitted by a single organizational unit and are covered under the same service level agreement.
Service Level Target Example 1
Service Level Target Example 2
The incidents have a response duration target of three days and a compliance target of 95%. This means that if the incidents are responded to in three days or less, the duration target is met. If the duration target is met at least 90% of the time, the compliance target is met and the incident response service level target is considered to be in compliance.
The incidents have a resolution service level target duration of five days and a compliance target of 90%. This means that if the incidents are resolved in five days or less, the duration target is met. If the duration target is met at least 90% of the time, the compliance target is met and the incident resolution service level target is considered to be in compliance.
The service request has a duration target of five days. This means that if the service request can be delivered in five days or less, the duration target is met. If the duration target is met at least 90% of the time, the compliance target is met and the service request delivering service level target is considered to be in compliance.
The service level agreement has an overall compliance target inherited from the service level package. This target is evaluated using all met and not met data from the duration targets.
Percentages from individual compliance calculations in the service level targets are not used to evaluate the overall service level agreement compliance target. Only the met/no met data from duration targets is used. |
1. | Log into the Service Desk Console as a service owner and open the Services workspace. |
2. | Double-click the service to which to define a target, then choose the Service Level Package tab. |
3. | Choose a service package from the list, then click Go To. The Service Level Package page appears. |
4. | Define the targets within the target tabs at the bottom of the page. |
1. | Choose the Delivery Target tab, then click Go to. The target record appears. |
2. | Enter information as needed into the fields. |
Field | Description |
---|---|
Name | Automatically populated based on the service and service level package. Cannot be modified. |
Hours of Operation | Automatically populated based on the hours of operation setting for the service level package. You can also choose an HOP from the drop-down list. |
Description | Optional. A brief description. |
Compliance Target (%) | This field is automatically populated base on the business rules for the service package object. You can also enter the percentage of completion that is required to fulfill the target. |
If a request offering is already linked to the service or the service level package, the target values are overridden by the delivery targets specified for the request offering. |
3. | Click Save. |
In the absence of service level incident response targets, the default escalation schedule for incident response runs. If you define the incident response target for an incident service category here, then the values you enter here override the defined escalation schedule.
1. | Choose the Response Target tab, then click Go to. The target record appears. |
2. | Enter information as needed into the fields. See -fields- above. |
3. | Click Save. |
In the absence of service level incident resolution targets, the default escalation schedule for incident resolution runs. If you define the incident resolution target for an incident service category here, then the values you enter here override the defined escalation schedule.
1. | Choose the Resolution Target tab, then click Go to. The target record appears. |
2. | Enter information as needed into the fields. See -fields- above. |
3. | Click Save. |
The overall compliance target is defined within a service level package.
1. | From the Service Level Package workspace, open the service level package to which to define the overall compliance target. |
2. | In the Compliance Target field, enter the number (from 1 to 100) of acceptable compliance. |
3. | Click Save. |
If the actual target compliances fall below the overall compliance target, the request is escalated. See Escalations.
You can create a target override (also called a target variant or target condition) for an response target or resolution target. For example, you might want to set a different response target for a priority 1 incident. If the ticket submitted is priority 2, 3, 4, or 5, the default incident response target will be used. However, if the incident submitted is priority 1, the target variant priority 1 target is used instead (it overrides the default incident response target).
1. | Log into the Service Desk Console as a service owner and open the Service Level Target workspace. A list of service level targets defined for each service level package appears. |
2. | Double-click a target to view its details. |
3. | Under the Target Override Conditions tab, click New. The New Target Condition window appears. |
4. | Enter the values as needed: |
Field | Description |
---|---|
Criteria Field | Criteria. The default field is priority. |
Criteria Value | A number. |
Delivery Target Days Hours Minutes |
The number of days, hours, and minutes for this condition. |
5. | Click Save. |
When a new service level package is created, the business rule called NewServicePackageCreation is triggered. This business rule runs the CreatePackageSLTs quick action. This quick action automatically creates the following service level target records:
- Service request delivery service level target
- Incident response service level target
- Incident resolution service level target
Each service level package can have only one setting for each type of service level target.
To change the default values used for the auto-creation of service level targets, you must change the global values shown in the following table. Global values are set through the Configuration Console. See Defining Global Constants.
Global Value Names For: |
||
Service Request Delivery SLT | Incident Response SLT | Incident Resolution SLT |
SLTDeliveryComplianceTarget | SLTResponseComplianceTarget | SLTResolutionComplianceTarget |
SLTDeliveryTargetDurationHrs | SLTResponseTargetDurationHrs | SLTResolutionTargetDurationHrs |
SLTDeliveryTargetDurationMin | SLTDeliveryTargetDurationMin | SLTResolutionTargetDurationMin |