Resetting goals for the same request
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*
When defining request-based service targets, you can select the Reset Goal for Same Request option so that the goal for a service target is reset whenever a condition is satisfied. When the condition is met, the measurement starts and behaves like any other service target. If the condition is met again, the service target starts to track a new request. The first measurement stops, the measurement is evaluated, and the measurement record retained for reporting purposes.
If you build the data source filters to use the system date as the reference start time, then the new measurement for the second request starts with the full goal time allowed.
Important
If you configure start time as defined on the application form at the data source level and then reset the goal for an SVT, the system creates a new measurement record when the Reset condition is met. However, the start time for this new measurement record is the same as the previous start time, because the system calculates the time from the same field as the previous measurement record. As a result, the SVTDueDate does not change.
For example, you are committed to responding to any communication from a customer within one hour. The condition for the goal to be reset is that the request is assigned. After a customer sends a communication and the request is assigned, the measurement starts. After the request is closed and some time elapses, a customer sends another communication and the request is assigned again, thereby meeting the condition. The goal is reset and the service target starts to track this request.
You can also use this feature for an OLA to track how long each group spends on request when the request is reassigned. Unlike the Tracking Time by Support Teams feature, the goal is reset so that each group is allotted the same amount of time. For example, a hardware group is assigned a service desk incident to correct a problem. After 15 minutes, they discover that it is not a hardware, but a software problem and reassign the incident to the software group.
See the following procedures to enable this feature.
Determine the criteria to be met.