SLA basic reporting percentage - Achieved & Breached

[Allan Ray]

Hello 

im new to this tool and would like to know how to get basic SLA reporting for our assigned group. 

what i need is separate or combined in one page.

1. Achieved SLA % monthly 
2. Breached SLA % monthly 

basically i need to know our monthly SLA target achievements of our incident tickets whether we are hitting our SLA targets like  98% , 95% or100% 

appreciate your help! thanks! 

[Tommy SN Sahlin · Accepted solution]

Hi guys,

I don't completely agree with gargharshdeep88's suggestion... Source Type and Table is fine, report Type depends on what you want to visualize. However I think the grouping and filtering should be built a bit differently. Try to avoid using the stage "Achieved" since it is deprecated.

How it should be built will depend on how your SLA Definitions are defined, and how you use the Incident State model. It will also depend on your reporting requirements, and if you need the reports for analytical or operational reasons.

But, as an example (making some best practice assumptions), say that you want to follow up on how many incident SLA's have been handled per month, and for each month see how many percent have breached (and how many have not):

• Data:
• Source type: "Table"
• Table: "Incident SLA"
• Conditions (funnel): I would simply use "Stage is Completed" since I'd only want to follow up on completed Task SLA's. Typically a Task SLA is set to Stage Completed when the incident is set to State Closed, which is when the user and the support organization are in agreement that the incident has been dealt with in a satisfactory way.
• Type: if I only wished to see the previous month's result, I'd choose a pie chart. But since I, in this example, want to see the result for all previous months, I'll instead choose Time Series > "Line" or "Area" (depending on what you like best).
• Configure:
• Group by: "Has breached" (which is a true/false field), so that you for each month will see how many have breached and how many have not
• Trend by: "Closed" since I want my report grouping based on the time stamp for when the incidents were closed
• per: "Month" (since this example is monthly, although there are several other options)
• Aggregation: Count

If I instead were looking to create operative reports, to see how things are going in run-time, I might preferrably create a few "Single Score" reports (counters) showing how many incidents have breached, how many are close to breaching etc and put them in a dashboard together with a couple of overview reports that can be grouped by state, priority, group etc by the dashboard user.

cheers, hope that helps  /Tommy

[gargharshdeep]

Hi Allan,

Here is way to get the required information -  

Source Type - Table

Table - Incident_SLA

Type - Bar or Pie chart

Group by - Stage.

Set the filter as - Stage is one of "Achieved or Breached"

[Tommy SN Sahlin · Accepted solution]

Hi guys,

I don't completely agree with gargharshdeep88's suggestion... Source Type and Table is fine, report Type depends on what you want to visualize. However I think the grouping and filtering should be built a bit differently. Try to avoid using the stage "Achieved" since it is deprecated.

How it should be built will depend on how your SLA Definitions are defined, and how you use the Incident State model. It will also depend on your reporting requirements, and if you need the reports for analytical or operational reasons.

But, as an example (making some best practice assumptions), say that you want to follow up on how many incident SLA's have been handled per month, and for each month see how many percent have breached (and how many have not):

• Data:
• Source type: "Table"
• Table: "Incident SLA"
• Conditions (funnel): I would simply use "Stage is Completed" since I'd only want to follow up on completed Task SLA's. Typically a Task SLA is set to Stage Completed when the incident is set to State Closed, which is when the user and the support organization are in agreement that the incident has been dealt with in a satisfactory way.
• Type: if I only wished to see the previous month's result, I'd choose a pie chart. But since I, in this example, want to see the result for all previous months, I'll instead choose Time Series > "Line" or "Area" (depending on what you like best).
• Configure:
• Group by: "Has breached" (which is a true/false field), so that you for each month will see how many have breached and how many have not
• Trend by: "Closed" since I want my report grouping based on the time stamp for when the incidents were closed
• per: "Month" (since this example is monthly, although there are several other options)
• Aggregation: Count

If I instead were looking to create operative reports, to see how things are going in run-time, I might preferrably create a few "Single Score" reports (counters) showing how many incidents have breached, how many are close to breaching etc and put them in a dashboard together with a couple of overview reports that can be grouped by state, priority, group etc by the dashboard user.

cheers, hope that helps  /Tommy

[Allan Ray]

wow very detailed explanation thanks!. seems this is more easy to understand monthly wise. so i added a filter condition 'Assignment Group is ' and got what im looking for. however is there away to get the percentage visible so its easy to identify the breached tickets and not. 

[Tommy SN Sahlin · Accepted solution]

Hi Allan,

your question was pretty similar to an example I presented recently in a workshop, so it wasn't much effort, haha...

Actually, I don't know of a way to visualize the percentages directly in Report Designer, although maybe (hopefully) somebody else does.

You can hover over the bars and see the percentages, or if you go to Style and click the check box "Display data labels" you'll get them in a table below the chart. Not exactly what you were asking for, I know...

cheers, hope that helps  /Tommy