Resolution delay taking Coverage window into account
In this tutorial, we suppose that you are calculating TTO and TTR taking into account Coverage Window, using SLA considering business hours extension, and you want to display the time spent let say in TTR, but ignoring the non-working periods.
Within a stopwatch we have 4 internal sub-items:
|timespent||Elapsed||total time spent within the states associated with the stopwatch - not accurate if stopwatch is running!|
|started||Started||when the stopwatch has started for the first time|
|laststart||LastStart||when the stopwatch has started for the last time - empty if stopwatch is stopped|
|stopped||Stopped||when the stopwatch was stopped for the last time - empty if stopwatch is running|
Resolution delay will give you the time between
those two internals:
ttr_stopped. But that may not be what you want, as
this delay is the total time between those two events.
You want is the real time spent by your support team to resolve
a ticket, ignoring periods outside of the coverage window. This is
exactly what is stored in the stopwatch sub-item
iTop Essential & Professional
Within the ITSM Designer, go to the class UserRequest and press
the new field icon:
In the pop-up window, select
Stopwatch = Select the stopwatch, in our case
Total time spent
Add this field to the presentation / details view.
Create an iTop extension and declare in XML a field of the UserRequest class, like this one:
- itop_design / classes / class@UserRequest
<fields> <field id="ttr_timespent" xsi:type="AttributeSubItem" _delta="define"> <target_attcode>ttr</target_attcode> <item_code>timespent</item_code> </field> </fields>
You may display it or not in the details screen of a UserRequest, it will anyway be available in “Customize this list” view, in dashlets and OQL queries.
Here is an example of a
timespent display versus
The stopwatch was started and stopped multiple times, as a result, “Elapsed” does not correspond to the difference between “Started” and “Stopped”
7*60s + 49s = 469s: Provider time spent is just a nice display of the “Elapsed” sub-item
It's an extract from this tutorial: Counting time waiting for 3rd party