Creating Service Request SLAs

Service Manager has different classes of work items for which SLAs can be configured. This recipe will show how to set up SLA management for the Service Request class scoped to Implementation Time.

Getting ready

Be familiar with the following recipes:

  • Creating SLA metrics
  • Creating priority queues
  • Configuring business hours and non-working days
  • Creating Service Level Objectives
  • Creating management Packs to save your SCSM personalization in Chapter 2, Personalizing SCSM 2016 Administration

How to do it...

We will refer to the previous recipes. The main change is to ensure the work item class, where referenced, is changed to target the Service Request class, as shown in the following screenshot:

How to do it...

Implementation Time SLA

Perform the following recipes in this order:

  1. Creating Priority Queues: Follow the Creating Priority Queues recipe, but each time you create a new queue, ensure that the name and description are changed to reflect the priority and that they are for Service Requests.

    Tip

    Ensure that during the creation, the class is changed to Service Request. This will give you a different choice of priority for Service Requests. With incidents, you specified a numeric value. With Service Requests, use the drop-down selection list to choose the priority of Low, Medium, High, or Immediate:

    Implementation Time SLA

  2. Configuring business hours and non-working days: Only one calendar is required based on the hours/days that you provide Service Request services to your customers. This could be the same calendar used for Incident Management, depending on your individual organization.
  3. Creating SLA metrics: Use the example in the recipe, but change the class to Service Request and End date to Completed Date, as shown in the following screenshot:

    Implementation Time SLA

  4. Creating Service Level Objectives: Create a SLO for each priority; usually this will be 4 SLOs for Priority Low, Medium, High, or Immediate Service Request types. Each time you create a new SLO, ensure that the name and description change to reflect the respective Service Request SLO and its Priority. Ensure that the correct priority queue for Service Requests is also selected.

For each SLO, you will need to supply a target and warning threshold value. The following table shows common values that can be used, but should reflect your organization's specifically defined requirements and/or agreements with your customers:

Priority

Target

Warning threshold

Immediate

9 hours

6 hours

High

45 hours

33 hours

Medium

90 hours

67 hours

Low

180 hours

180 hours

How it works...

By defining the different parts that make up your organization's requirements and tying them together with a SLO, Service Manager now enables you to model your SLA requirements and keep track of how the service is performing. This recipe provides steps to implement Service Request specific SLAs using the unique properties of the service request process.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.144.36.141