Initial response targets

Table of contents

Related articles

Introduction

When you manage a service, it is important to measure it to find out what are its strengths and weaknesses. From the information that is gathered, you can make changes to processes, give training or coaching to employees, communicate more information to the customers, etc. to improve on what the service can offer. 

The basic Octopus configuration already includes the required options to set up resolution service targets for incidents and service requests, but it is possible to add the initial response targets on requests. This is beneficial, because if the response to the requests is reasonable, a greater number of them will be resolved within the time frame. 

The activation of the initial response targets is therefore an additional tool to help measure and improve services. 

Prerequisites

Before the initial response targets can be configured, the service level targets must have been activated in the Options.  

What you need to know: 

The Administer Octopus permission is required to configure the resolution and initial response targets.

To activate the resolution targets

Go to Tools > Option in the 2- Service Level Agreement (SLA) section.

  1. Activate the option.
  2. Add the hours of operation.
  3. Add the service's holidays.
  4. Configure the Resolution targets for incidents.
  5. Configure the Process targets for service requests (SR).
  6. Save the modifications with OK.

NOTE: It is also possible to configure the resolution targets for incidents and service requests in the Configuration Data

Visual Explanation

 

To activate the initial response targets

Before you can configure the initial response targets for the incidents and service requests, you must contact our Service Desk to activate the Initial response targets.

 

Initial response targets configuration

What you need to know: 

Before proceeding to the configuration of the initial response targets, the option must have been activated by the Octopus Service Desk.

Once the option has been activated, the initial response configuration can be done in : 

Tools > Reference data management

For incidents

  1. From the reference data, open the Incident node. 
  2. Open the Priority node.
  3. Select one of the priorities.
  4. From the Service Level Agreement section, add or modify the Take charge target.
    • Generally, we recommend that the response delay be ± 20 % of the resolution delay. 
  5. Save the modifications with the disk icon and repeat the process for other priorities.
  6. Finish the configuration with the Close button at the bottom right.
Visual Explanation

 

For service requests

  1. From the reference data, open the Service request node. 
  2. Open the Types node.
  3. Select one of the service requests.
  4. From the Take charge target (SLA), add or modify the response delay.
    • Generally, we recommend that the response delay be ± 20 % of the resolution delay. 
  5. Save the modifications with the disk icon and repeat the process for other service requests.
  6. Finish the configuration with the Close button at the bottom right.
Visual Explanation

How the initial response targets work

The response is always calculated between the Open Date and the Response Date of the request. If the Take assignment action is not performed and the request is resolved, than the Resolution Date will also be the Response Date

What you need to know: 

It is only the first time the request is taken in charge that will be used for the Response Delay calculation. If the request is taken in charge again during its lifecycle, these other responses will have no effect on the initial response target.  

Here are the fields that can be used in searches or shown in lists to follow the initial response targets: 

  • Response SLA.
  • Take Assignment Due Date.
  • Response Date.
  • Response Delay.
  • Response Delay (Business Days).

From a list, the Take Assignment Due Date will be: 

  • Empty.
    • If the Take assignment action has not been done.
  • In black.
    • When the response was done within the expected delay.
  • In red.
    • When the response was done later than the expected delay.

X
Help us improve our articles








Help us improve our articles