SM_Demo and SM CAPs

The purpose of the SM Content Acceleration Pack (CAP) is to provide a set of items (Dashboard pages, Scorecards, Contexts, KPIs, Metrics, and more) that automatically gathers information from across your enterprise to build key performance indicators (KPIs) related to SM-related issues with OOTB data from Data Warehouse. The CAP includes the Service Manager Perspectives. The CAP provides broad and deep insight that should enable you to Improve Staff Effectiveness, Improve Responsiveness, Achieve Process Excellence, Improve Quality of Delivery, Improve Customer Satisfaction. This CAP provides a 360 degree Service Manager view.

The SM CAP includes data from the Service Manager data source.

The relevant content pack is SM. For details, see Integration with SM.

ClosedUser Story

  1. Maggie is the Service Management Director of the IT service department. As part of her daily routine, she’d like to log into the IT Business Analytics (ITBA) application to understand the overall performance of her organization and check if there are any critical issues on the table.
  2. Maggie starts reviewing the SM Director Scorecard and under the Customer perspective, she notices that the status of Improve Customer Satisfaction objective is Red and it seems that the trend started in the previous period.
  3. To understand why the Improve Customer Satisfaction objective was not met, she clicks the objective and checks the related KPI in the KPI View Component. She notices that the reason for not meeting the Customer Satisfaction objective is due to poor SLA and OLA performance.
  4. Maggie decides to start her analysis with the Number of SLA Targets Breached KPI.
  5. She clicks the KPI to view the historical trend of the KPI and check its forecasted behavior.
  6. She notices that lately, the behavior of this KPI got worse.
  7. The KPI granularity is Monthly. She wishes to find the specific day or week this KPI started to be breached. To do so, she clicks the Calendar icon and selects Weekly.
  8. The historical results of this KPI are now presented in a weekly resolution.
  9. She finds out the specific week when the KPI started to breach.
  10. Maggie also noticed in the Forecast component that the KPI will continue to be breached in upcoming months and therefore understands that something needs to be done.
  11. She continues the drill down to understand which specific SLA Agreements were breached.
  12. She checks the Top 3 Breached SLA Target by Customer component and drills down using the Agreement Name dimension.
  13. Maggie checks the last periods and notices that Sharepoint Service agreement is the top target that was breached.
  14. She writes an annotation to John, the owner of the Sharepoint Service in the organization, requesting clarifications.
  15. John receives an email from Maggie regarding the problematic KPI. He logs on to the ITBA application, checks the same KPI, and sees that the indeed the number of breached Sharepoint Service SLAs is high.
  16. John is not surprised since lately the Sharepoint service has not been stable due to large number of issues appeared after upgrading to a new version. Most of the issues were already resolved.
  17. He writes an annotation back to Maggie stating that the SLA will improve in the upcoming period and that he expects to see an improvement very soon.

ClosedSM_Demo and SM 

User interface elements are described below (when relevant, unlabeled elements are shown in angle brackets):

UI Element

Description

Pages

SM-Change Management Overview Page

SM_Demo and SM CAPs

SM-Incident Management Overview Page

SM-Problem Management Overview Page

SM-Request Management Overview Page

SM-Service Desk Overview Page

SM-Service Level Management Overview Page

SM-Service Manager Overview Page

Scorecards
  • SM Director
  • Service Manager
Business Contexts
  • SM_ServiceManagement
  • SM_Demo

For details, see ????.

KPIs and Metrics

Note The Demo CAP includes KPIs with names followed by (Demo). The CAP includes the same KPIs with names that do not include (Demo). The KPIs are the same but have different names so that both the Demo CAP and the CAP can be activated at the same time.

  • Approved vs Rejected Changes KPI. The number of approved changes relative to the number of rejected changes. The approved and rejected changes are broken down by:

    1. Urgency, Impact, Service/Business Service, CI, CI Type, Platform.
    2. Risk (side-by-side).
    3. Cost vs. Projected ROI (side-by-side).
  • Average Cost of a Change KPI. The average cost of a change that occurred during the measurement period.

    Limitation - if the cost change time and the change create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Average Cost of a Problem KPI. The average cost of a Problem created during the measurement period.

    Limitation - if the cost change time and the problem create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Average Cost of a Request KPI. The average cost of a Request that was created during the measurement period.

    Limitation - if the cost change time and the request create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Average Cost of an Incident KPI. The average cost of an Incident that was created during the measurement period.

    Limitation - if the cost change time and the incident create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Average Interaction Closure Duration KPI. The average time elapsed from the interaction creation time till the interaction close time.

  • Average Outage Duration by Service KPI. The average duration of outages associated with an incident.

  • Average Time to Agreed SLA Phase KPI. The average duration of SLAs from the first time they are "draft" to the time they are "agreed" during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Change Backlog Size KPI. The backlog of opened changes.

  • Change Success Rate KPI. The number of successful changes relative to the total number of changes performed during the measurement period.

  • Incident Aging KPI. The number of open incidents older than 5 days (or any other given time frame) relative to the total number of open incidents. This Metric. measures the efficiency of the service desk by determining how quickly technicians address the incidents and group the incidents into aging categories.

  • Incident Backlog Size KPI. The trend of the number of incidents. Managers can track the total number of opened incidents within a specified time period to determine the effectiveness of incident prevention initiatives that include training, automation, proactive processes, and maintenance.

  • Incident Resolution Time KPI. The average time elapsed from the incident creation time till the incident close time.

  • Interaction Backlog Size KPI. The trend of the number of interactions. Managers can track the total number of opened interactions within a specified time period to determine the effectiveness of interaction prevention initiatives that include training, automation, proactive processes, and maintenance.

  • Mean Time to Resolve Incident KPI. The average time elapsed from the incident creation time till the incident close time.

  • Mean Time to Resolve Problem KPI. The average time elapsed from the problem creation time till the problem close time.

  • Number of Breached SLA Incidents KPI. The number of incidents from the SLA(SLT) category that were opened during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Number of Breached SLA with Breached OLA KPI. The number of SLA targets with relevant OLA targets that were both breached during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of Breached SLA with Breached UC KPI. The number of SLA targets with relevant UC targets that were both breached during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of Changes Where Remediation is Invoked KPI. The number of changes where remediation is invoked during the measurement period.

    Version Limitation - This KPI. is available only if you have SM Codeless mode(PD) version.

  • Number of Closed Incidents KPI. The number of incidents closed during the measurement period.

  • Number of Completed Changes KPI. The number of changes that were completed successfully during a measurable period (for example: daily/weekly/monthly).

  • Number of Documented SLAs in Place KPI. The number of Service Level Agreements that were agreed to during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of Failed Changes KPI. The number of changes that failed during the measurement period.

  • Number of Incidents Caused by Change KPI. The number of created incidents caused by change failure that occurred during the measurement period.

    Limitation - If the linkage setup time and the incident create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM Codeless mode(PD) version.

  • Number of OLA Targets Breached KPI. The number of Service Level Targets for Operational Level Agreement that were breached during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of OLA Targets Close to Breached KPI. The number of Service Level Targets for Operational Level Agreements that were close to breached during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of OLA Targets Met KPI. The number of Service Level Targets for Operational Level Agreements that were met during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of Opened Changes KPI. The amount of new changes opened during the specific period.

  • Number of Opened Incidents KPI. The amount of new incidents that were opened during the measurement period.

  • Number of Opened Interaction KPI. The amount of new interactions that were opened during the specific period.

  • Number of Opened Problems KPI. The amount of new problems that were opened during the measurement period.

  • Number of Opened Requests KPI. The number of new requests that were opened during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Number of Rejected Changes Caused by Incomplete Change Specifications KPI. The number of rejected changes caused by incomplete change specifications that occurred during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Number of Rejected Changes Caused by Incomplete Impact Assessments KPI. The number of rejected changes caused by incomplete impact assessments that occurred during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Number of SLA Targets Breached KPI. The number of Service Level Targets for SLA that were breached during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of SLA Targets Close to Breached KPI. The number of Service Level Targets for SLA that were close to breached during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of SLA Targets Met KPI. The number of Service Level Targets for SLA that were met during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of UC Targets Breached KPI. The number of Service Level Targets for Underpinning Contracts that were breached during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of UC Targets Close to Breached KPI. The number of Service Level Targets for Underpinning Contracts that were close to breached during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Number of UC Targets Met KPI. The number of Service Level Targets for Underpinning Contracts that were met during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Percentage of Agreements Reviewed Within the Period KPI. The number of agreements with a non-expired review date relative to the total number of agreements.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Percentage of Availability Compared to SLTs KPI. The total outage time relative to the total service-based SLT uptime during the measurement period.

  • Percentage of Changes Resulting in Outage KPI. The number of changes opened during the measurement period that resulted in outage, relative to the total number of changes.

  • Percentage of Closed Incidents KPI. The number of incidents that were closed relative to the total number of incidents that were opened during the measurement period.

  • Percentage of Closed Problems KPI. The number of problems that were closed relative to the total number of Problems that were opened during the measurement period.

  • Percentage of Closed Requests KPI. The number of requests that were closed relative to the total number of requests that were opened during the measurement period.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Percentage of Emergency Changes KPI. The number of changes of type emergency that occurred compared with the total number of changes that occurred during the measurement period.

    Version Limitation - This KPI. is available only if you have SM Codeless mode(PD) version.

  • Percentage of Escalated Incidents KPI. The number of incidents that were escalated relative to the total number of incidents that were opened during the measurement period. According to the escalation rule in the SM application, based upon the Alerts definition, an incident that has met one of the Alert definitions is considered an escalated incident. This analysis enables organizations to identify inefficiencies in the incident routing process.

  • Percentage of First Call Resolution KPI. (Percentage of first call resolution of service requests) The number of interactions that were solved by the first line without assistance from other support lines, relative to the total number of interactions that occurred during the measurement period. This Metric. enables organizations to identify the percentage and call counts that the initial customer contact completes for non-Employee Self Service (ESS) calls. The Metric. is commonly one of the crucial drivers of customer satisfaction. By monitoring first call resolution, Call Center managers can determine how well the service is performing and whether additional staff or knowledge tools are necessary to facilitate high call volumes.

  • Percentage of Improvement Plans Related to Agreements KPI. The number of agreements with service improvement plans relative to number of agreements.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Percentage of Incidents Classified as Security Related KPI. The number of incidents classified as security-related relative to the total number of incidents that occurred during the measurement period.

  • Percentage of Interactions in Backlog KPI. The number of open interactions that are older than 28 days (or any other given time frame) relative to the total number of open interactions. This number reflects the size of the backlog of old unresolved interactions.

  • Percentage of OLA Targets Breached KPI. The number of Service Level Targets for Operation Level Agreements that were breached during the measurement period relative to the total number of Service Level Targets.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Percentage of Reopened Incidents KPI. The number of closed incidents that were reopened, relative to the total number of incidents closed during the measurement period. This KPI. is meaningful only if your Incident Management process allows reopening calls.

  • Percentage of SLA Targets Breached KPI. The number of Service Level Targets for SLAs that were breached during the measurement period relative to the total number of Service Level Targets. Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Percentage of SLAs Due to Expire KPI. The number of SLAs that, according to plan, should expire in the upcoming three months relative to the total number of active SLAs.

  • Percentage of Service Based SLAs Agreed KPI. The number of service-based SLAs agreed relative to the total number of SLAs. Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Percentage of UC Targets Breached KPI. The number of Service Level Targets for Underpinning Contracts that were breached during the measurement period relative to the total number of Service Level Targets for UC.

    Version Limitation - This KPI. is available only if you have SM 9.40 version.

  • Percentage of Unauthorized Implemented Changes KPI. The number of unplanned changes relative to the total number of changes during the measurement period.

  • Problem Backlog Size KPI. The backlog of open problems.

  • Problem Resolution Time KPI. The average time elapsed from the problem creation time till the problem close time.

  • Request Backlog Size KPI. The backlog of opened requests.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Total Cost of Change KPI. The total cost of a Change created during the measurement period.

    Limitation - if cost change time and change create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Total Cost of Incident KPI. The total cost of an Incident created during the measurement period.

    Limitation - if cost change time and incident create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Total Cost of Problem KPI. The total cost of a Problem created during the measurement period.

    Limitation - if cost change time and problem create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

  • Total Cost of Request KPI. The total cost of a Request created during the measurement period.

    Limitation - if cost change time and request create time are not recorded in the same measurement period, the KPI. will not able to count it.

    Version Limitation - This KPI. is available only if you have SM 9.40 Codeless mode(PD) version.

Data (External Tables)

SM Director

Service Manager

ClosedSM-Change Management Overview Page

ClosedSM Director Page

ClosedSM-Incident Management Overview Page

ClosedSM-Problem Management Overview Page

ClosedSM-Request Management Overview Page

ClosedSM-Service Desk Overview Page

ClosedSM-Service Level Management Overview Page

ClosedSM-Service Manager Overview Page