Calculating Response time in Performance analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2018 03:28 AM
hi all
how can we calculate avg response time for incidents.
using indicators.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2018 11:35 AM
What conditions are considered "Response" for your organization, and is that tracked anywhere? For example via an OLA? Or is there some Business Rule that writes data to the actual Incident?
Regards,
Chris

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2018 12:22 PM
We use our SLA durations to determine the Average Response Time for incidents. We also display the percent of SLAs achieved and breached in a pie chart on a PA incident dashboard.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2018 11:19 PM
hi,
we use business elapsed time, sla is Time to own(TTO), sla type is SLA.
I need this in an indicator which takes the average.
scores need to be in hours.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2018 08:20 AM
Ok, perfect. One way to approach this is to create an Indicator with an SLA breakdown, and a Widget using the Breakdown.
And Automated Indicator can be configured to average the Business Elapsed time. You can use the already existing Incident.SLA.Task.ResolveTime.Hours script. Here is an example of the new Indicator:
At this point, you could use the Additional Conditions tab to add logic to the Indicator to only run against the 'Time to Own (TTO)' SLA, however if you do that, it will limit the re-use. A more holistic approach is to add the SLA breakdown as below...
Now when I view the Breakdown tab on the scorecard for the new Indicator, I can see the average Elapsed Business Time against any SLA:
The last step is to create a widget visualization that utilized the Breakdown. Here is an example screenshot:
Hopefully this makes sense - again the goal here is not just to create the functionality, but do it in a way that enables re-use. The best way to do that is to use Breakdowns and Widgets to add logic, instead of creating a custom made Indicator for each need.
Let me know if this doesn't work for you, or if you have more questions,
Chris