Update 15.11.2014
Additional improvements have been made! You can read more and download file here Further “Service Level Tracking Summary Report” improvement 

Summary reports about achieved service level agreements are of course absolutely necessary. For example, for reporting to the management or evidence of achieving the level of operation to our customers, audit trail, etc…

Let’s see a real case with a “Service Level Tracking Summary Report” report.

The report is available “out of the box” but has some shortcomings and opportunities for improvements. Especially in terms of user experiences.

Two challenges that we have to solve:

  • The exported report “Service Level Tracking Summary Report” has collapsed sections by default:



Because of this report initially not show any useful information. That’s not OK.

  • Yes we have an interactive report but when you click "expand" you must wait in some cases 5 minutes or even more. It depends on how many SCOM “Service Levels Tracking” objects are included and how many various intervals are included.

It is understandable that the user experience is poor. Especially in case of managers or customer representatives.

Therefore, we slightly adapt the definition of the report and remove “expand | collapse” options. We’ve got two advantages: expanded table in case of interactive use or in exported report for example in “.pdf” format. Exactly what we need!



Now the report display much more information without extra expanding clicks and rendering waits. The analysis can begin…

You can download it from here...

You must upload report definition file to SCOM reporting services and overwrite out of the box report in “Microsoft Service Level Report Library” library.



Set correct “Data Source” element.



And “Apply” changes.

Now the initially rendered interactive report show service levels and their corresponding goals and values across various time interval. Report is also ready for export to “.pdf”.

We must be aware that in the case of importing management pack “Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp“  for example, because we deploy System Center 2012 Operations Manager SP1 Update Rollup 5 (Always carefully read KB article) we overwrite report definition. So we have to repeat the above procedure. But this is not so often that it represents overhead.

This posting is provided “AS IS” with no warranties, and confers no rights.