Guia Completo para ITIL4 - Desenho de Serviço INGLES
Guia Completo para ITIL4 - Desenho de Serviço INGLES
Guia Completo para ITIL4 - Desenho de Serviço INGLES
REDACTED
IT Support
Table of Contents
1. MANAGEMENT SUMMARY ........................................................................................................ 6
1.1 Preface ............................................................................................................................................6
1.2 Executive Summary.........................................................................................................................6
1.3 Certification status........................................................................................................................10
1.4 Word of Thanks .............................................................................................................................10
2. WORK PERFORMED ..................................................................................................................11
2.1 Pre-Audit Review of Documentation ............................................................................................11
2.2 On-Site Audit .................................................................................................................................11
2.3 List of Evidence .............................................................................................................................11
2.4 Interviews Conducted ...................................................................................................................11
2.5 Analysis of Data Collected ............................................................................................................13
2.6 HDI Review ....................................................................................................................................13
3. RATING METHODOLOGY ...........................................................................................................14
4. MATURITY LEVELS ....................................................................................................................15
4.1 Enabler Categories ........................................................................................................................15
4.2 Results Categories.........................................................................................................................15
5. SUMMARY OF RATING SCORES .................................................................................................16
5.1 Rating Scores in Tabular Format ...................................................................................................16
5.2 Rating Scores in Graphical Format................................................................................................17
5.3 Activity Rating Scores....................................................................................................................18
Enablers ..............................................................................................................................................18
Results ................................................................................................................................................21
6. RATING REMARKS ....................................................................................................................23
6.1 1.0 Leadership ...............................................................................................................................23
1.010 Alignment to Organization .......................................................................................................24
1.020 Integration within Support Model ...........................................................................................25
1.030 Resource Allocation and Alignment .........................................................................................26
1.040 Promoting Teamwork ..............................................................................................................27
1.050 Marketing and Promotion ........................................................................................................28
1. Management Summary
1.1 Preface
This report summarizes the HDI Support Center Certification audit performed for the
REDACTED IT Support located at 1340 Pickering Parkway, Suite 101 Pickering, ON L1V
0C4. This audit was conducted to assess the maturity of IT Support based on the HDI
Support Center Standard against the certification requirements for the HDI Support Center
Certification program.
IT Support submitted documentation prior to the on-site audit for review by the HDI
Certified Auditor. The on-site audit was scheduled and performed July 06-10, 2020
(undertaken via virtual meetings). During the on-site audit, the HDI Certified Auditor
conducted interviews with management, staff, and customer representatives; observed the
support center activities; and reviewed additional documentation to gather evidence to
assign maturity ratings for each activity. Upon completion of the on-site visit, analysis of all
of the information collected was performed off-site to calculate the audited rating scores
and prepare this report. The results of the certification audit are included in this report along
with remarks that substantiate the audit ratings.
allowed IT Support to become very nimble in reacting to customer needs and committed to
quality improvement.
Strengths
IT Support has done an admirable job in preparing itself to achieve HDI Support Center
Certification. As can be seen in the chart below, the results show that the organization is well
balanced across most categories, showing no significant weak areas.
Leadership and Customer Satisfaction are key strengths reflecting IT Support management’s
commitment to the larger organization and IT Support staff commitment to its customers.
The tools and technologies (Resources) are well utilized and the organization is not hesitant
to adopt new technologies when an improvement in service delivery can be justified.
Some staff have been in their roles for many years and turnover is almost non-existent.
However, satisfaction remains high, reflecting well on the culture cultivated within the
organization.
staffing costs, perhaps setting the goal as a band (+x% and – y% of forecast) could
better show performance. Showing volumes as a stacked bar of incidents and requests
may provide insight into trends.
8.013 Number of Incoming Contacts – Data should measure the actual contacts. What
number of emails, chats, IM contacts and phone calls are being handled that are not
getting logged?
8.030 Abandon Rate – Reporting monthly could better identify inconsistencies in service
levels.
8.050 First Contact Resolution Rate – Clarifying criteria that constitute FCR would provide
validity to data.
8.070 Backlog – Tracking improvement on both volume and days open might be easier if
considered as an inventory that incorporates the actual number of days open for each
ticket. (# of tickets open x number of days open).
8.110 Knowledge Management Link Rate – The target is low and may not reflect the desired
goal of increasing the use of the knowledge base.
8.120 Cost per Unit – Adding a target can help drive the organization toward management
of the cost per ticket.
2. Work Performed
2.1 Pre-Audit Review of Documentation
HDI provided IT Support with a list of documentation to gather and submit prior to the on-
site audit. IT Support provided the documentation (Pre-Audit Binder) to HDI on May 21,
2020. The HDI Certified Auditor reviewed the materials prior to the site visit.
Sr. TIA
Systems Integration Lead
09:00 - 11:50 Manager, IT Support
Manager, IT Support
12:30 - 14:25 Manager, IT Support
Manager, IT Support
14:35 - 16:15
16:20 - 17:09 Manager, IT Support
08-Jun 08:00 - 08:15 Director, IQSS
Manager, IT Support
Manager, IT Support
Sr. TIA
Systems Integration Lead
08:15 - 11:00 Manager, IT Support
Sr. TIA
Systems Integration Lead
11:00 - 12:00 Senior TIA (Head Office)
12:30 - 13:30 Manager, IT Support
Manager, IT Support
13:30 - 17:20
09-Jul 08:00 - 08:30
Director, IQSS
Manager, IT Support
Manager, IT Support
Sr. TIA
Systems Integration Lead
8:30 -9:30 Manager, IT Support
9:30 - 10:15 TIA
10:00 - 11:00 TIA
11:00 - 11:45 Sr. TIA (Head Office)
12:30 - 13:15 TIA
13:15 - 14:00 TIA - IQSS
14:00 - 14:50 Sr. TIA
15:00 - 16:00 Manager, IT Support
16:00 - 16:15 Director, IQSS
Manager, IT Support
Manager, IT Support
Sr. TIA
Director, IQSS
Manager, IT Support
10-Jul 08:00 - 9:00 Manager, IT Support
Sr. TIA
Systems Integration Lead
3. Rating Methodology
Each category of the HDI Support Center Certification Standard contains individual activities
that represent best practices for support centers. A rating score is assigned by the auditor
to reflect the support center’s maturity level for each activity. There are four levels of
maturity for each activity. The rating score for each activity is determined by scoring “yes”
and “no” answers to the maturity level descriptions associated with each activity. These are
the raw rating scores which represent the maturity of the support center in each activity.
Each activity has a “weight factor,” a number from 1 to 3 which reflects the relative
importance of that activity to the overall category rating (1=lowest and 3=highest). The raw
rating scores are combined with the weight factors to compute a “weighted rating” for each
category. The weights for each activity are shown in the Activity Rating Scores section.
The overall rating is calculated using the weighted combination of the rating scores achieved
for each category. The weights for each category are shown in the Summary of Rating
Scores section.
Minimum rating scores of 2.3 in each category and 2.5 overall are required to achieve the
status of HDI Certified Support Center.
4. Maturity Levels
4.1 Enabler Categories
During the audit, the auditor received from the support center management and staff
answers with respect to the activities in the enabler categories of the HDI Support Center
Standard. There are four maturity levels:
1 Just started Recognition of the value of the activity and the
beginnings of plans for improvement.
2 Some progress Evidence that the activity is being performed and is
reviewed for improvement, and there are some
examples of successful implementation or results.
3 Considerable progress Evidence that the activity is being consistently
performed and is regularly reviewed. There are
examples of improvements although implementation
may not be universal or applied to its full potential
across the organization.
4 Fully achieved/optimized An approach or result that is implemented universally,
continual improvement efforts exist, and it is difficult
to envision significant improvement.
Leadership
4.0
2.0
1.0
Performance Results People Management
0.0
Audited Rating Score Minimum Rating Scores Required for Certification Previous Audit Results
1.0 Leadership
Activity
Activity Weight Rating
ID
1.010 Alignment to Organization 2 4
1.020 Integration within Support Model 3 4
1.030 Resource Allocation and Alignment 2 4
1.040 Promoting Teamwork 1 4
1.050 Marketing and Promotion 2 4
1.060 Distribution and Communication of Information 1 4
4.0 Resources
Activity
Activity Weight Rating
ID
4.010 Financial Resources 2 4
4.020 Physical Environment and Ergonomics 1 4
4.030 Infrastructure 1 2
4.040 Incoming Contact Distribution System 1 3
4.050 Investigation and Diagnosis Resources 1 4
4.060 Workforce Management Tool/System 2 2
4.070 Service Management Tool/System 2 4
4.080 Remote Support Tools 1 4
4.090 Knowledge Management Tool/System 2 4
4.100 Knowledge Resources 1 4
4.110 Reporting Tool/System 2 3
Results
6. Rating Remarks
6.1 1.0 Leadership
Leadership defines how all levels of management and all employees in leadership roles guide
their organizations toward success by inspiring and motivating staff and driving continual
improvement. All levels of support center staff should understand why the ir jobs are
important, receive satisfaction from their work, and feel supported and valued for their
efforts by the support center management. Effective leaders ensure that the work being
done is aligned with the needs of the organization, and the value of the work being done is
communicated and understood throughout the entire organization. They provide highly
visible support and encouragement, and they inspire cooperation and enthusiasm.
0
Alignment to Integration within Resource Allocation Promoting Teamwork Marketing and Distribution and
Organization Support Model and Alignment Promotion Communication of
Information
Remarks
Maturity Level 1
Met - Delivering accurate, timely assessments; building and maintaining stakeholder
relationships; and achieving or exceeding revenue goals are identified as key to
REDACTED's success.
Maturity Level 2
Met - Data security and governance are necessary to maintain REDACTED's
credibility. Support of Property Inspectors and their completion of Property
Valuations are critical, as are Year-end assessments and periodic re-
assessments.
Maturity Level 3
Met - As expressed during interviews, staff identified core applications (Insight and
IPS) as key where outages have a significant impact on REDACTED's business.
Maturity Level 4
Met - As an example, Covid-19 required IT Support to adjust policies and procedures
to accommodate support staff and end-users working from home.
Remarks
Maturity Level 1
Met - IT Support management is well versed in their understanding of the support
organization and continuously interacts with management and staff of the other
support functions.
Maturity Level 2
Met - The IT Support Operational Guidelines document provides a good overview of
the support model. Staff are familiar with its contents and understand the needs of
the organization as demonstrated by the leading of the swarming process.
Maturity Level 3
Met - Management and staff communicate at daily scrums, weekly stand-up
meetings, sprint meetings and bi-weekly calls.
Maturity Level 4
Met - A Change Advisory Board (CAB) meeting is held daily. The IT Support
Manager and representation from head office TIA team attend.
Remarks
Maturity Level 1
Met - A ratio support model of 80- 100 users per one TIA, with adjustments for
locations is used for initial determination of IT Support staff required.
Maturity Level 2
Met - In addition to the staffing ratio, a review of incident and request resolution is
compared to the target service levels for each location and adjustments to the
staffing model are made.
Maturity Level 3
Met - Overall staffing numbers are provided by HR and the IT Support staffing
calculation is done quarterly to begin planning adjustments. Staffing is then
augmented with temporary staff and co-op students.
Maturity Level 4
Met - The adjustments and incremental temporary staff are allowing IT Support to
meet service level targets.
Remarks
Maturity Level 1
Met - Skype or Team sessions are used to bring everyone together to introduce
new features/functionality. Boot camps for Agile training were another initiative to
bring teams closer together. Afternoon calls are held three times per week and
hosted by different team members.
Maturity Level 2
Met - Two offsite meetings of 3 days duration used to be held. The most recent was
in January. Now moving toward annual regional meetings in centralized locations.
Representatives from other IT teams are invited to participate and present.
Maturity Level 3
Met - Many initiatives are cross functional. Documented "stories" require defined
goals and measurements. Big Wins presentations are used to share successes.
Maturity Level 4
Met - An example of celebrated shared success is the ISO 27001 certification
initiative recognized by the CAO.
Remarks
Maturity Level 1
Met - Communication messages are posted on the IT Support site. Support staff are
profiled on the support site promoting the people and skills of support.
Maturity Level 2
Met - Email signatures direct users to the IT Support site. Managers are advised to
encourage their staff to use the support site.
Maturity Level 3
Met - Support participates in Regional office meetings representing IT Support. At
100-day events, support will attend and present support success and projects.
Maturity Level 4
Met - Town hall meetings are also used to communicate progress and performance.
Demonstrations of improvement initiatives are given to the Executive Management
Group (EMG) and board members.
Remarks
Maturity Level 1
Met - Key performance indicators (KPI) are available to all staff on live dashboards
within Jira.
Maturity Level 2
Met - Operational results may be shared on calls held twice per week with IT
management. Quarterly reports are shared with REDACTED executives.
Maturity Level 3
Met - Progress is discussed in daily meetings, scrums, and pilot meetings. The
Manager's Tactical Call held every week is open to all managers and directors where
results are shared.
Maturity Level 4
Met - Updates on strategic initiatives and completed roadmap initiatives are
presented to the Executive Management Group (EMG), typically quarterly.
0
Purpose Goals and Objectives Operational Plans Stakeholder Engagement
0
Service Improvement Plans Support Center Services Definition Security of Systems and Information
2.050 2.060 2.070
2.010 Purpose
The purpose of the support center within the organization must be established,
documented, communicated, and reviewed for continual improvement. There are many
different approaches and models that can be employed, which include the development of
statements of vision, mission, purpose, core values, service philosophy, management
philosophy, and other statements.
Level Maturity Description Yes/No
The purpose of the support center is communicated within the
1 support center, and support center staff can articulate their own Yes
understanding of its meaning.
The purpose of the support center is documented and published
2 Yes
inside and outside of the support center.
The purpose of the support center is aligned with the
3 Yes
organization’s vision, mission, and objectives.
An activity to review the alignment of the purpose of the support
4 center to the vision, mission, and objectives of the organization is No
conducted at least annually.
Current State Maturity Rating 3
Remarks
Maturity Level 1
Met - The IT Support Mission is defined. Staff interviewed understood its intention
to help drive efficient, quality service.
Maturity Level 2
Met - The mission is published on the IT Support site.
Maturity Level 3
Met - REDACTEDs objectives were an integral part of the process to develop IT
Support's mission statement.
Maturity Level 4
Not Met - The rewording of the mission statement was recently undertaken.
However, this activity was driven to optimize the statement for publishing on the
website as opposed to a desire to raise awareness and commitment of IT Support
staff.
Remarks
Maturity Level 1
Met - SLA targets have been negotiated and IT Support has defined service level
objectives (SLO) that are effectively stretch goals. Operational goals are
documented and included as an index in the reporting package.
Maturity Level 2
Met - Tactical objectives are defined on story boards for each sprint. Also, a Kanban
board is used to capture tactical initiatives for smaller projects. Work Objects
defined in Confluence identify the underlying initiatives.
Maturity Level 3
Met - The IT Support Roadmap is used as the strategic plan for the organization.
The roadmap is developed in advance of year end. Work objects identify the
Strategic outcome that is being supported.
Maturity Level 4
Met - The strategic goals of IT Support align with the five pillars identified in the
corporate strategic plan. The strategic plan is advertised on the intranet page and
communicated in management meetings and CAO virtual chats.
Remarks
Maturity Level 1
Met - Operating procedure documentation can be found in the Confluence
knowledgebase.
Maturity Level 2
Met - Policies and process documents can also be found in Confluence.
Maturity Level 3
Not Met - A comprehensive operations plan has not been developed though some
of the required content could be found in various documents.
Maturity Level 4
Not Met - No plan has been documented. However, evidence was presented that
some of its required content is being updated.
Remarks
Maturity Level 1
Met - IT Support's stakeholders have been identified as internal users - business
users; head office supporting functions; and IT Department teams.
Maturity Level 2
Met - Feedback is obtained through event-based surveys and executive feedback
received from senior leadership.
Maturity Level 3
Met - As part of the Agile process, stakeholders are invited to participate as product
owners.
Maturity Level 4
Met - Sprint reviews, daily scrums, and reviews of 100-day projects are used to
provide feedback to stakeholders.
Remarks
Maturity Level 1
Met - IT Support uses a Kanban board to identify and track ad-hoc improvement
initiatives.
Maturity Level 2
Not Met - Stories are documented for most improvement initiatives. However,
continuity between Kanban initiatives and measured outcomes are not clearly
documented.
Maturity Level 3
Met - Daily scrums provide feedback on key support improvement initiatives.
Maturity Level 4
Met - An Agile coach is employed to review plans and progress on a continual basis
and to recommend adjustments to the process.
Remarks
Maturity Level 1
Met - A list of services is published on the intranet and can be found in the
REDACTED IT Support Operational Guidelines document.
Maturity Level 2
Met - User friendly terminology is used. The hours of operations and service
expectations are also included.
Maturity Level 3
Not Met - The list of services is not comprehensive. IT Support uses its own lists to
identify services and service owners.
Maturity Level 4
Met - The user facing list of services is updated in the IT Support Operations
Guidelines document as changes occur.
Remarks
Maturity Level 1
Met - Buildings all require card access and a "zero trust" environment is in place
where no services can be accessed from a personal device.
Maturity Level 2
Met - Acceptable use, access management, remote wiping of devices, and other
security policies and practices are in place, published on the intranet, and covered
in onboarding training. Code of conduct and phishing refresh er training is required
annually, and completion tracked by IT Security.
Maturity Level 3
Met - Procedures for reporting and handling breaches are found in the IT SEC
Information Technology Security Incident Management Procedure document. Issues
are recorded in Jira and escalated to IT Security.
Maturity Level 4
Met - To maintain ISO 27001 certification, compliance is routinely audited by IT
Security.
0
Job Descriptions Orientation Training Plans Ongoing Skill Assessment Career Development Plans Performance Management
and Training Plans
0
Staff Satisfaction Compensation Program Recognition and Reward Workforce Management Retention Program
Management Programs
3.050 3.060 3.070 3.080 3.090
Remarks
Maturity Level 1
Met - Job descriptions are in place for the roles used within IT Support - Junior
Infrastructure Analyst; Technology Infrastructure Analyst (TIA); Senior TIA;
Supervisor, IT Support; and Manager, IT Support. Descriptions are posted on the
intranet.
Maturity Level 2
Met - The job descriptions accurately reflect key accountabilities and activities, job
requirements, and competencies.
Maturity Level 3
Met - Job descriptions are referenced for performance management and planning
purposes.
Maturity Level 4
Met - Descriptions are reviewed by HR and union representatives routinely as part
of the bargaining process. IT Support management provides input regarding any
proposed changes.
Remarks
Maturity Level 1
Met - Staff are hired into one role as there is no differentiation between field and
head office (service desk) support. A standard training plan is used and updated as
needed.
Maturity Level 2
Met - Training time is adjusted based on the knowledge and experience of the new
TIA to ensure that the plan can be completed.
Maturity Level 3
Met - A facilitator is assigned for the topics covered in the training plan. Both the
facilitator and the trainee sign off on successful completion of the various activities
within the plan.
Maturity Level 4
Not Met - While there was evidence that the training plan has been updated to
accommodate new requirements, no evidence was presented to demonstrate that
changes to training are integrated into change management practices.
Remarks
Maturity Level 1
Met - A skills inventory is contained in the IT Support Team Skills Matrix workbook.
The inventory includes all key applications supported. The required level of skills is
identified for the three technical support roles.
Maturity Level 2
Met - Staff assess themselves on their perceived level of expertise for the various
applications. Results are reviewed and used to drive coaching and career
development initiatives for the individual.
Maturity Level 3
Not Met - The review of consolidated results for the team are used to drive training
sessions during weekly meetings. However, no evidence of any formal training plans
or forecasts was presented.
Maturity Level 4
Met - The budget for training is held by the Learning and Development team who
ensure training is funded.
Remarks
Maturity Level 1
Met - A formal career development discussion occurs as part of the annual
performance management appraisal (PMA) process.
Maturity Level 2
Met - Employees document their aspirations in the development goals section of
the PMA document. Goals can include formal and informal training objectives.
Maturity Level 3
Met - Progress is discussed in monthly one-on-one meetings. Employees can go
into the IRIS system at any time and update the status of progress toward their
goals.
Maturity Level 4
Met - See Maturity Level 1 above.
Remarks
Maturity Level 1
Met - The PMA process is completed annually based on the calendar year.
Maturity Level 2
Met - Feedback is provided during a mid-year and year-end formal reviews. Within
IRIS, any outstanding tasks are identified, and notifications sent to managers.
Maturity Level 3
Not Met - Three objectives are provided to staff for inclusion in the PMA. These
objectives may relate to IT Support improvement initiatives. Operational
performance objectives are not generally included as a measure of performance.
Maturity Level 4
Not Met - One of the two opportunities for compensation improvement is
contractually mandated and not tied to performance or the performance process.
Remarks
Maturity Level 1
Met - IT Support staff are surveyed quarterly to assess their satisfaction levels. The
survey contains 15 questions.
Maturity Level 2
Met - Survey results are compiled by management. Results are shared by email.
Discussions during the daily support call highlight concerns and improvemen ts.
Maturity Level 3
Met - Corrective actions are identified for questions where ratings require attention
or are perceived as an opportunity to drive improvement. The switch from Bomgar
to the Crisp and Splashtop tools were a direct result of survey feedback.
Maturity Level 4
Met - The survey is conducted quarterly, and measurable results are tabulated.
Remarks
Maturity Level 1
Met - As part of contract negotiations, pay scales are reviewed and compared to
ensure equity of affected roles.
Maturity Level 2
Met - Salary increases are predetermined based on current pay and contractually
negotiated increases. However, if performance is rated below a 3, the step increase
will be held.
Maturity Level 3
Not Met - Performance ratings are more tied to subjective behavioral factors as
opposed to support center or organizational goals.
Maturity Level 4
Met - One of the two annual increases is tied to the results of the performance
management process.
Remarks
Maturity Level 1
Met - The We Value You and the Life Events programs provides recognition for
years of service and events outside of work. We Value You also allows staff to
recognize peer contributions.
Maturity Level 2
Met - Both programs are used and funded through HR.
Maturity Level 3
Met - Program changes are managed as a project. IT staff would be consulted and
sometimes involved in changes.
Maturity Level 4
Not Met - IT Support management is provided feedback, but not directly involved in
analyzing the outcomes of the programs.
Remarks
Maturity Level 1
Met - Staffing levels are determined based upon a ratio of users to support and the
volume of calls being generated from the supported user community.
Maturity Level 2
Met - A schedule is kept in Teams to ensure support across all locations during key
hours. Response and resolution service level performance data is incorporated in
the staffing/scheduling determination process.
Maturity Level 3
Met - The process for calculating staffing requirements is documented in the
Resource Allocation and Utilization document. Review is conducted quarterly.
Maturity Level 4
Met - The process and calculations are reviewed quarterly. Adjustments to the
assumptions may result and the process revised.
Remarks
Maturity Level 1
Met - The current retention process is ad-hoc. Acting roles are used to help
groom/assess staff's ability to cover other roles.
Maturity Level 2
Not Met - Retention planning is now being done as required for forecasting to
finance and HR but the process is not yet documented.
Maturity Level 3
Met - Retention targets are now being forecasted and tracked, though due to low
staff churn, this mainly involves planned retirements. Results are being tracked on
the Succession tab in an Excel workbook.
Maturity Level 4
Met - IT management is now routinely reviewing program results.
0
Financial Resources Physical Environment Infrastructure Incoming Contact Investigation and Workforce
and Ergonomics Distribution System Diagnosis Resources Management
Tool/System
0
Service Management Remote Support Tools Knowledge Management Knowledge Resources Reporting Tool/System
Tool/System Tool/System
Remarks
Maturity Level 1
Met - The director, IQSS, holds the budget for the IT Support team.
Maturity Level 2
Met - The director forecasts the anticipated costs for labor and project related
items.
Maturity Level 3
Met - IT Support appears to be adequately funded for staffing and infrastructure
needs.
Maturity Level 4
Met - The director participates in monthly meetings with Finance where over/under
line items are reviewed and adjustments made. Funding to support new initiatives is
identified within the Agile process.
Remarks
Maturity Level 1
Met - While many of the TIAs work in field offices which were not viewed, the Head
Office IT Support area is comparably fitted.
Maturity Level 2
Met - IT Support resides in a glassed-in room that shelters support staff from office
traffic and conversations.
Maturity Level 3
Met - A collaboration space is included in the enclosed area. Large wall mount
monitors display operational and performance data. Workspaces are arranged to
allow easy communication among staff. IT Operations staff are located adjacent to
IT Support.
Maturity Level 4
Met - Workspaces are fitted with ergonomic mice, keyboards, chairs, and adjustable
desks. Ergonomic assessments can be arranged to accommodate any special needs.
4.030 Infrastructure
Availability, capacity, resilience, and reliability within the technology infrastructure are
necessary for the systems and tools that are critical to the successful operation of the
support center.
Level Maturity Description Yes/No
The technology infrastructure used to deliver support center
1 services has sufficient availability and capacity to meet the Yes
requirements of the support organization.
Reports are available on the capacity and availability of the
2 technology infrastructure used to deliver support center services. Yes
Remarks
Maturity Level 1
Met - The main technologies - Jira, Confluence, O365, and network infrastructure
are considered adequate and stable.
Maturity Level 2
Met - Much of the infrastructure used and supported is hosted in REDACTED's
AWS cloud and is governed by a 99.6% uptime service level objective. Uptime is
reported monthly.
Maturity Level 3
Not Met - Monitoring tools identify resource usage in real time. Performance is
reviewed weekly and capacity adjustments made. Plans regarding capacity of non-
cloud infrastructure (telephony, licenses, etc.) were not present.
Maturity Level 4
Met - Quarterly meetings have been set up to review availability and capacity of key
systems.
Remarks
Maturity Level 1
Met - Jira Service Desk distributes contacts received via email and self-service.
Clarity Connect receives and distributes phone calls.
Maturity Level 2
Met - Many contacts are received and handled via Jira which routes tickets to a
queue presenting all new tickets created within the last 16 hours. A customized
dashboard provides agents the ability to see the number and status of contacts and
displays times to response and resolution.
Maturity Level 3
Met - When a service level is set to breach within an hour, emails are sent by the
system every 30 minutes to the assigned person, dispatch team managers, and any
staff subscribed to monitor the ticket.
Maturity Level 4
Not Met - The telephony system is not integrated with Jira. Crisp, the chat tool, is
not directly integrated although functionality is in place to allow support to log a
ticket and include chat dialogue from within Crisp.
Remarks
Maturity Level 1
Met - Documentation regarding investigation and diagnosis actions is stored in the
Confluence knowledgebase.
Maturity Level 2
Met - Service Desk and Field TIAs use similar configurations to those supported
allowing them to conduct testing and troubleshooting on their own systems.
Maturity Level 3
Met - The Splashtop tool allows connectivity to customer environments and servers.
Maturity Level 4
Met - A lab is in place at head office. Regional offices have set-ups where testing
and imaging can be done locally.
Remarks
Maturity Level 1
Met - An Excel workbook is used to determine staffing levels. A ratio of one support
person to every 80 to 100 staff is used as the baseline. Calculations incorporate the
number of tickets and the number of hours required to resolve.
Maturity Level 2
Met - Both service level response and resolution targets are factored in to
determining staffing levels by supported locations.
Maturity Level 3
Not Met - The tool is only used for reviewing staffing levels and performance. Staff
do have access to dashboards within Jira to view SLA performance. The staffing
schedule is maintained in Teams where staff can see assignments, but Teams does
not track adherence.
Maturity Level 4
Not Met - Data is extracted from Jira and used for calculations. Results can be fed
back into a Jira dashboard.
Remarks
Maturity Level 1
Met - Jira Service Desk is used as the service management system of record.
Maturity Level 2
Met - All support groups use the Jira Service Desk tool which is linked to the Jira
system used by the development teams.
Maturity Level 3
Met - The IT Support portal allows users to view the status of existing tickets,
append comments, and initiate new incidents and service requests.
Maturity Level 4
Met - Users and support staff can configure notifications by subscribing to the
ticket. Rules are configured to send notifications when a ticket is created, assigned,
resolved, closed, or comments added.
Remarks
Maturity Level 1
Met - The Splashtop application allows support staff to view and access user
workstations.
Maturity Level 2
Met - Splashtop sends a web link to the user which provides a code that will allow
support staff to access and take control of the workstation if required.
Maturity Level 3
Met - Remote access is being used more frequently since work from home has been
enforced. Previously, it was used around 10% of the time.
Maturity Level 4
Met - Splashtop is not integrated into Jira, but a custom field has been added to the
ticket form to indicate its use.
Remarks
Maturity Level 1
Met - Confluence is used as the knowledge repository.
Maturity Level 2
Met - Users can rate (thumb up/down) an article and can add comments as
feedback.
Maturity Level 3
Met - Confluence is integrated with Jira Service Desk. Articles can be searched from
within the ticket. Support staff can link knowledge articles to tickets and vice versa.
Maturity Level 4
Met - Via the IT Support Portal, users can search the knowledgebase. When logging
a new ticket, the system will suggest content to users.
Remarks
Maturity Level 1
Met - Support staff use the knowledgebase.
Maturity Level 2
Met - Any member of the support team can contribute new or updated content.
Maturity Level 3
Met - A member of the Quality team checks the quality of the content and vets it
before it is made available to end users.
Maturity Level 4
Met - Designated spaces within Confluence are set up for the various support teams
who control their content and the sharing of access to it.
Remarks
Maturity Level 1
Met - Jira Service Desk provides dashboard capabilities to present performance
results. Plug-ins are used to access and present customized data.
Maturity Level 2
Met - Dashboards present real-time status regarding SLA, and performance can be
boxed to provide results based on desired periods of time. The Clarity Connect
admin portal provides access to basic telephony reporting.
Maturity Level 3
Met - Dashboards provide ample historical and real-time reporting. Color-coding is
used to highlight potential performance issues.
Maturity Level 4
Not Met - No analytics tools are used to assist in forecasting.
0
Event Management Customer/User Service Level Feedback Request Fulfillment Incident Management
Satisfaction Management Management
Management
0
Logging of Categorization of Prioritization of Status Levels of Initial Investigation and
Incidents/Requests Incidents/Requests Incidents/Requests Incidents/Requests Diagnosis of
Incidents/Requests
5.065 5.070 5.080 5.090 5.095
0
Escalation of Resolution of Incidents Closure of Incidents Reopening of Incidents Problem Management
Incidents/Requests
0
Change Management Service Asset and Continual Improvement of Support Center Services Quality Assurance
Configuration Management Support Center Continuity Management Management
Processes/Procedures
Remarks
Maturity Level 1
Met - Autoscaling, Data Dog, and Zabbix tools are used to monitor servers. EventIO
is used to monitor status of key services. AirWatch is used to monitor mobile device
configuration.
Maturity Level 2
Not Met - The swarm process is used to alert and initiate involvement for major
outages. A Chat channel is used by the service desk to notify other TIAs regarding
events and monitors display status. However, procedures have no defined timelines
or guidelines as to which events should be reported, or how and when.
Maturity Level 3
Not Met - In so far as handling an outage, roles and responsibilities are clear
regarding resolution. However, the IT Support's role for notification to management
and users is not defined.
Maturity Level 4
Met - A senior TIA works with IT Operations and IT Security to coordinate and
initiate changes to monitoring practices.
Remarks
Maturity Level 1
Met - A survey is generated from within Jira and sent to the requestor for every
incident or request. The survey asks for a star rating and comments. The rating
scale is 1 to 5, with 5 being the best rating.
Maturity Level 2
Met - Negative survey responses (3 stars or less rating) or those with negative
sentiment are followed up on. The process is documented in the Customer
Satisfaction document. Follow-up on very satisfied ratings/comments is undertaken
on an ad-hoc basis.
Maturity Level 3
Met - A target has been set to achieve a rating of 4.9, out of a possible 5. Detail on
the survey is available on a Jira dashboard and shared with staff on daily calls after
quarterly results have been tabulated.
Maturity Level 4
Not Met - An annual survey happens close to year end to gain input on overall IT,
but it does not provide feedback actionable by IT Support.
Remarks
Maturity Level 1
Met - Key Performance Metrics are defined as internal service level objectives that
are above those presented to customers. These are published on the Support
Confluence page.
Maturity Level 2
Met - Service level targets are noted in the IT Support Operations Guidelines
document and in the Incident and Service Request Guides that are published on the
Support site.
Maturity Level 3
Met - The Exec dashboard is displayed on monitors within the support area and
available to all with JIRA accounts. These results are shared with EMG weekly and
presented to the Board quarterly.
Maturity Level 4
Met - IT Support is held to account for service level performance. Agreements are in
place with an external vendor regarding the purchase and warranty replacements of
hardware. IT Operations and Cloud Ops have agreements with infrastructure
vendors.
Remarks
Maturity Level 1
Met - Users provide feedback via surveys and are encouraged during visits and
interactions to voice comments/concerns/suggestions to IT Support Management.
Using the Send Us Feedback link on the IT Support site will create a ticket in Jira
that will be actioned.
Maturity Level 2
Met - Survey feedback is followed up if sufficient information is provided to be able
to identify the requestor. A target has been set to follow-up on at least 20 surveys
monthly.
Maturity Level 3
Met - Procedures are documented for handling survey feedback with IT Support
Management and Quality Monitoring staff conducting the follow-ups.
Maturity Level 4
Met - The process document gets updated quarterly with changes and results.
Remarks
Maturity Level 1
Met - Procedures for fulfilling requests are documented in the Service Request
Process Guide and in Confluence.
Maturity Level 2
Met - Requestors are notified automatically by Jira upon creation, status changes,
and resolution.
Maturity Level 3
Met - Quality Monitoring staff review closed tickets and provide feedback, ensuring
procedures are followed.
Maturity Level 4
Met - Procedures undergo annual review and are updated as required between
reviews. Changes are tracked in the Document Review and Approval within the
process document.
Remarks
Maturity Level 1
Met - Procedures for handling incidents are documented in the Incident
Management Process Guide.
Maturity Level 2
Met - A RACI Chart documented in the Incident Management Guide identifies the
roles and responsibilities for steps related to the incident management process.
Maturity Level 3
Met - Quality Monitoring staff review closed tickets and provide feedback as do
those involved in the Dispatch Swarming process.
Maturity Level 4
Met - Procedures undergo annual review and are updated as required between
reviews. Changes are tracked in the Document Review and Approval within the
process document.
Remarks
Maturity Level 1
Met - Procedures for logging incidents and requests can be found in the respective
process guides.
Maturity Level 2
Met - Comments are added to the tickets to capture input, actions taken, and
resolution activities.
Maturity Level 3
Met - Quality Monitoring staff review tickets to ensure that the actions have been
properly documented.
Maturity Level 4
Met - Procedures contained in the process guides are reviewed at least annually.
Remarks
Maturity Level 1
Met - Procedures for categorizing incidents and requests can be found in the
respective process guides.
Maturity Level 2
Met - The categories within Jira align to the affected component (application or
device) that the issue relates to.
Maturity Level 3
Met - Quality Monitoring staff review tickets to ensure proper categorization.
Maturity Level 4
Met - Procedures contained in the process guides are reviewed at least annually.
The listing of components shows both active and archived entries indicating that
they are being updated.
Remarks
Maturity Level 1
Met - Procedures for prioritizing incidents and requests can be found in the
respective process guides.
Maturity Level 2
Not Met - The procedures identify a policy of allowing TIA staff to change priority,
but not the associated procedures.
Maturity Level 3
Not Met - Quality Monitoring staff review tickets to ensure proper prioritization, but
no review of priority change is undertaken.
Maturity Level 4
Not Met - Procedures regarding the changing in ticket priority need to be
documented and included in the review cycle.
Remarks
Maturity Level 1
Met - Ticket status definitions can be found in the respective process guides.
Maturity Level 2
Met - The status of tickets is reviewed and managed at the daily scrum attended by
the dispatch swarm lead. Dashboards identify tickets whose status has not been
updated.
Maturity Level 3
Met - The Jira system notifies the reporter when ticket status changes.
Maturity Level 4
Not Met - The lack of clarity in the documented procedures is an indication that
they are not being reviewed for improvement.
Remarks
Maturity Level 1
Met - Procedures are documented in the associated process guides. Details can be
found in How To documents and troubleshooting sections in procedures guides.
Maturity Level 2
Met - Staff document actions and findings are within the ticket comments.
Maturity Level 3
Met - Quality Monitoring staff review tickets to ensure the proper troubleshooting
steps were used and documented.
Maturity Level 4
Met - As a result of routine review, templates for investigation and escalation have
been jointly developed.
Remarks
Maturity Level 1
Met - Procedures for escalating incidents and requests can be found in the
respective process guides. The Support Awareness Map details the various contacts
and requirements for functional escalation of supported components
(applications/systems).
Maturity Level 2
Not Met - Hierarchical escalations are documented in the process guides, but only
from the perspective of the ticket reporter. Procedures as to how a TIA should
escalate an issue to management are not defined.
Maturity Level 3
Met - An escalation form is included in the ticket which is then escalated to a Senior
TIA. Swarm leads and Quality Monitoring staff review tickets to ensure proper
escalation procedures are being followed.
Maturity Level 4
Met - Routine review of procedures occurs as the Support Awareness Map is kept
as a living document.
Remarks
Maturity Level 1
Met - Procedures for resolving incidents can be found in Confluence.
Maturity Level 2
Met - Ticket reporters are automatically notified by Jira when the incident status is
set to Resolved.
Maturity Level 3
Met - Quality Monitoring staff review tickets to ensure the correct resolution state
was used and sufficient details provided.
Maturity Level 4
Not Met - Confusion regarding the application of Closed verses Resolved within Jira
is an indication that the process is not rigorously reviewed for improvement.
Remarks
Maturity Level 1
Met - Procedures for closing tickets are documented in the process guides. The
system will automatically close a resolved ticket after two business days.
Maturity Level 2
Met - A survey is sent to the user regarding impending closure of the ticket
providing instructions on reopening the ticket if they are not satisfied. During QA
review an analyst may contact the user by phone, email, or instant message to
validate proper closer.
Maturity Level 3
Met - QA practices ensure that procedures are being followed. Proper closure was
also validated during operations observation activities.
Maturity Level 4
Not Met - Proper review of procedures should have identified the uncertainty of the
functionality of the Close button on the incident form and clarified its use.
Remarks
Maturity Level 1
Not Met - End users may request the reopening of an incident via the self-service
portal but procedures for handling closed incidents are not documented.
Maturity Level 2
Met - A Resolved ticket status goes to Reopened and then changes to any another
active status as per workflow. This change of status is counted and reported.
Maturity Level 3
Not Met - As the procedures are not clear, this cannot be adequately assessed.
Maturity Level 4
Not Met - Procedures cannot be properly reviewed as they are not documented.
Remarks
Maturity Level 1
Met - Procedures are found in the Support Problem Management Process
document. A PRIMARY TICKET is logged, and incidents are linked to this ticket.
Maturity Level 2
Met - An identified problem will trigger a swarm which IT Support leads, thus being
made aware of the issue. A Retrospective following the swarm will provide the
detection/workaround/fix which is typically stored in Confluence.
Maturity Level 3
Met - In the context of reactive problem management (swarming), IT Support roles
and responsibilities are defined as is the responsibility of other support teams to
keep the ticket and dispatch swarm lead updated.
Maturity Level 4
Not Met - Some proactive analysis may result in a Kanban, but formal proactive
problem management analysis is not conducted.
Remarks
Maturity Level 1
Not Met - IT Support system changes are governed by the overarching change
management procedures. The Kanban process will drive stories regarding required
changes. These stories are tracked but may not be tied to the change management
process, nor are changes to internal IT Support processes and procedures.
Maturity Level 2
Met - A Change Calendar is maintained in Confluence, Service availability is shown
in JIRA, and identifies services to be iREDACTEDted by impending changes.
Maturity Level 3
Met - The roles and responsibilities of IT Support management and staff are outlined
in the Support Change Management Process document. Version history indicates
that this document is reviewed at least annually.
Maturity Level 4
Met - IT Support is represented at the daily CAB meetings.
Remarks
Maturity Level 1
Met - Procedures are in place to manage assets and configuration information.
Tracking is done using the Jira Assets functionality.
Maturity Level 2
Met - The PDQ program takes inventory on systems and identifies discrepancies
which are then logged in JIRA. IT Support staff can edit records and are responsible
to ensure data is correct.
Maturity Level 3
Met - IT Support responsibilities are defined in the Asset Management Audit
Procedures document.
Maturity Level 4
Met - Support staff consult the data to validate client equipment and configurations.
Remarks
Maturity Level 1
Met - Process guides and documents such as onboarding and off-boarding are
documented.
Maturity Level 2
Met - The commitment to quality improvement within IT Support extends to the
updating of documentation. Version tracking confirms key documents are being
updated.
Maturity Level 3
Met - Scrum activities involve stakeholders in the review and improvement of
processes and procedures.
Maturity Level 4
Not Met - A process to ensure that documents are being reviewed for improvement
opportunities is not in place.
Remarks
Maturity Level 1
Not Met - Checklists are in place to ensure IT Support capabilities are operational
during contingency. How IT Support will gather equipment to conduct support
remotely is documented. However, the scenarios under which contingency plans
will be enabled are not defined nor are procedures as to how these situations will be
managed.
Maturity Level 2
Met - The required systems for IT Support are included in the IT Disaster Recovery
Program Framework and the Business Continuity Management Framework in the IT
Operations sections.
Maturity Level 3
Met - Restoral timeframes and staffing levels are identified within the above-
mentioned documents.
Maturity Level 4
Met - In addition to tested failovers, a yearly tabletop exercise regarding continuity
is conducted. IT Support management participates in this exercise.
Remarks
Maturity Level 1
Met - Approximately 30% of closed tickets are reviewed for quality.
Maturity Level 2
Met - Quality assurance practices can be found in the IT Support - Quality
Management document. A team of three TIAs is assigned to review closed tickets
on an ongoing basis and assess parameters related to the service level provided,
the ticket details captured and troubleshooting procedures followed.
Maturity Level 3
Met - The IT Support manager meets with Quality Team once per week to review
the data. Overall results are then discussed in the morning call. A Quality Team
member will then conduct appropriate coaching.
Maturity Level 4
Not Met - Due to bargaining unit guidelines, quality scores cannot be incorporated
into the PMA process.
0
Staff Satisfaction Turnover Unplanned Absence Utilization
6.010 6.020 6.030 6.040
Remarks
Maturity Level 1
Met - IT Support conducts a staff satisfaction survey quarterly.
Maturity Level 2
Met - A target is established for each question on the survey prior to its release.
Maturity Level 3
Met - Results show that no targets have been missed on any of the questions over
the past 4 quarters.
Maturity Level 4
Met - See above.
6.020 Turnover
Unplanned staff turnover can be an indication of low morale and increased job
dissatisfaction. Actual turnover must be tracked and compared against an established goal.
Level Maturity Description Yes/No
Performance data is collected and reported on a regular schedule
1 Yes
(e.g., monthly, quarterly, twice yearly, or yearly).
Reports show performance data compared against an established,
2 Yes
quantitative performance goal/target.
Reports show performance data trending toward the established
3 goal/target over the past six months (or equivalent reporting Yes
periods).
Reports show the established turnover goal/target has been
4 achieved or exceeded in at least nine of the past twelve months (or Yes
equivalent reporting periods).
Current State Maturity Rating 4
Remarks
Maturity Level 1
Met - Data on planned and unplanned exits is tracked annually and reported by HR
monthly.
Maturity Level 2
Met - The target is no more than one unplanned exit per year. No goal is set on
planned exits as they are normally retirements which are identified a year in
advance.
Maturity Level 3
Met - There have been no unplanned exits in the last 3 years.
Maturity Level 4
Met - See above.
Remarks
Maturity Level 1
Met - Data regarding unplanned absences is collected and reported monthly.
Maturity Level 2
Met - The target is to have no more than 16 days of unplanned absences in a
calendar month.
Maturity Level 3
Met - Only 13 days of absences have been occurring on average over the last year.
Maturity Level 4
Met - Within the past 12 months, there has been only one month where the target
was not met.
6.040 Utilization
Optimal utilization of support staff is necessary for successful support center performance.
Actual utilization must be tracked and compared to an established goal.
Level Maturity Description Yes/No
Performance data is collected and reported on a regular schedule
1 No
(e.g., monthly, quarterly, twice yearly, or yearly).
Reports show performance data compared against an established,
2 Yes
quantitative performance goal/target.
Reports show performance data trending toward the established
3 goal/target over the past six months (or equivalent reporting No
periods).
Reports show the established performance goal/target has been
4 achieved or exceeded in at least nine of the past twelve months (or No
equivalent reporting periods).
Current State Maturity Rating 0
Remarks
Maturity Level 1
Not Met - In the submitted data for this activity, utilization was being defined as the
measure of elapsed time from ticket creation to its resolution, excluding time in
paused states. This is really a measure of service performance and not TIA effort.
Maturity Level 2
Met - A target was set for utilization of 70% as defined above.
Maturity Level 3
Not Met - As the measurement is not properly stated, performance could not be
assessed.
Maturity Level 4
Not Met - See above.
0
Periodic Satisfaction Results Ongoing Satisfaction Results Feedback Results
7.010 7.020 7.030
Remarks
Maturity Level 1
Met - An annual survey of all REDACTED staff containing 10 questions related to
their satisfaction with IT services is run by an external company. The most recent
survey had 1200 respondents.
Maturity Level 2
Met - A target has been established to achieve an average rating of 52 out of 100 on
the 10 questions.
Maturity Level 3
Met - Performance has been 2 to 3 points above target.
Maturity Level 4
Not Met - Only 3 surveys (years) worth of data was available which is not enough to
assess long term consistency.
Remarks
Maturity Level 1
Met - A 5-star rating system is used to capture user satisfaction following resolution
of the incident or request. A dashboard displays daily/weekly/monthly/quarterly
performance. The results are reported quarterly.
Maturity Level 2
Met - A target has been set to attain a rating of 4.9, out of a possible 5. Recently,
satisfaction was reported at 4.91.
Maturity Level 3
Met - Results have been consistently above 4.9 over the past five quarters.
Maturity Level 4
Met - See above.
Remarks
Maturity Level 1
Met - Ticket survey results are reviewed, and user sentiment is assigned based on
ratings and comments. The review of survey returns is ongoing, and results
reported quarterly.
Maturity Level 2
Met - The target is to ensure that 96% of the feedback is positive. Most recently,
feedback was rated at 96.44% positive.
Maturity Level 3
Met - Performance has trended down from a high of 98% but has consistently
stayed above the target.
Maturity Level 4
Met - See above.
0
Number of Number of Incoming Self-Service Effectiveness Average Time to Respond Abandon Rate Incident Resolution Time
Incidents/Requests Contacts
Logged
0
First Contact First Level Resolution Reopened Incidents Backlog Hierarchical Functional Escalation
Resolution Rate Rate (Management) within Support Center
Escalations
8.050 8.055 8.060 8.070 8.080 8.085
center.
0
Functional Escalation Incident Resolution Time Knowledge Management Cost per Unit Quality
outside Support Center Distribution (Resolved by Link Rate
Support Center)
Remarks
Maturity Level 1
Met - The number of incidents and requests logged are tracked and reported
quarterly.
Maturity Level 2
Met - A service level objective has been set at 18,000 incidents/requests logged per
year (4.5K/Qtr.). The current average is around 7,000 per quarter.
Maturity Level 3
Met - Have been above target in all 5 quarters reported.
Maturity Level 4
Met - See above.
Remarks
Maturity Level 1
Met - The number of tickets logged by contact channel method is reported
quarterly.
Maturity Level 2
Not Met - The target is measuring performance against the same criteria as 8.010
(number of tickets logged). Actual interactions are not being accurately captured
nor is a target set that could be used to drive desired changes in behavior.
Maturity Level 3
Not Met - Performance cannot be assessed without valid targets against which to
compare.
Maturity Level 4
Not Met - See above.
Remarks
Maturity Level 1
Met - The number of page views on the IT Support Portal is tracked and reported
quarterly.
Maturity Level 2
Met - A target has been set to achieve 6,500 page views per quarter which is based
on 30% of staff accessing the support site once per week. 7,214 page views were
counted in the most recent quarter.
Maturity Level 3
Met - Although the target was missed in two quarters, it had previously been
exceeded significantly and has trended back above target in the most recent
quarter.
Maturity Level 4
Not Met - The target was not met in two of the last five quarters.
Remarks
Maturity Level 1
Met - Response time is determined when the status of a ticket changes from New to
In Progress. It is calculated and reported quarterly.
Maturity Level 2
Met - The SLO has been set for first response within 0.5 hours. In the most recently
reported quarter, it was 0.31 hours.
Maturity Level 3
Met - Response time has been below target for the last five quarters, averaging
around 0.36 hours with a consistent downward trend.
Maturity Level 4
Met - The SLO has not been breached in the six quarters of data reported.
Remarks
Maturity Level 1
Met - Abandoned calls are measured and reported quarterly.
Maturity Level 2
Met - The target on abandoned phone calls is set at 3%. Currently, it has been
reported at 4.58%.
Maturity Level 3
Not Met - A positive trend back toward the target was being evidenced, but the
target was not reached, and the trend has turned negative in the most recent
quarter.
Maturity Level 4
Not Met - Performance has not been consistent, and the abandoned rate has not
been met in the last four quarters.
Remarks
Maturity Level 1
Met - Incident resolution times by priority are tracked and reported quarterly.
Maturity Level 2
Met - Resolutions SLOs are set by priority - 3 hours for high priority, 5 hours for
medium, and 12 hours for low. In the most recent quarter, objectives were met for all
priorities.
Maturity Level 3
Met - The average resolution time has been met for all priorities over the past four
quarters except for medium priority incidents in Q2 2019.
Maturity Level 4
Met - With only one breach almost 12 months ago, performance can be considered
consistent.
Remarks
Maturity Level 1
Met - FCR is measured and reported quarterly as a combined total for incidents and
service requests, excluding requests such as purchases. Resolution is considered
FCR based on the indication by the resolving TIA.
Maturity Level 2
Met - The target on FCR is set at 70%. It has been recently reported at 98%.
Maturity Level 3
Met - FCR has not been below 96% in the past 5 quarters.
Maturity Level 4
Met - See above.
Remarks
Maturity Level 1
Met - Any ticket closed by a TIA within IT Support (Service Desk, Head Office, or
Field) is counted as having been resolved at first level. FLR is reported quarterly.
Maturity Level 2
Met - The SLO is to keep FLR above 90%. In the last full quarter, it was reported to
be 96%.
Maturity Level 3
Met - FLR has been reported at 96% or above for the past 4 quarters.
Maturity Level 4
Met - See above.
Remarks
Maturity Level 1
Met - An incident whose status has changed from Resolved back to an active state
qualifies as a reopened incident. Performance is reported quarterly.
Maturity Level 2
Met - The target has been set to keep the reopened rate at or below 3%. It is
currently reported at 1.6%.
Maturity Level 3
Met - The target has not been breached in the past five quarters. Performance has
ranged from 1.26% to 1.94%.
Maturity Level 4
Met - See above.
8.070 Backlog
The total number or percentage of open incidents/requests at the support center compared
to their age.
Level Maturity Description Yes/No
Performance data is collected and reported on a regular schedule
1 Yes
(e.g., monthly, quarterly, twice yearly, or yearly).
Reports show performance data compared against an established,
2 Yes
quantitative performance goal/target.
Reports show performance data trending toward the established
3 goal/target over the past six months (or equivalent reporting No
periods).
Reports show the established performance goal/target has been
4 achieved or exceeded in at least nine of the past twelve months (or No
equivalent reporting periods).
Current State Maturity Rating 2
Remarks
Maturity Level 1
Met - Backlog is a measure of the number of tickets still open at the end of the
reporting period, which is currently quarterly.
Maturity Level 2
Met - Targets have been set to keep the number of open tickets below 400, with
the average number of days open below 250 days. For Q2 2020, only 162 issues
were open with an average open time of 118 days.
Maturity Level 3
Not Met - Prior to Q2, performance had been trending well above both targets, with
around 450 open tickets averaging over 400 days open. While the trend in volume
was down, the average number of days open was increasing.
Maturity Level 4
Not Met - Changes in closure requirements were made to help drive down the
backlog. The change in performance has not been evidenced to assess consistency.
Remarks
Maturity Level 1
Met - A ticket where a manager has been assigned or added as a participant is
considered a management escalation. Performance is reported quarterly.
Maturity Level 2
Met - The target is to ensure that less than 3% of tickets get escalated. Currently,
performance was reported at 1%.
Maturity Level 3
Met - On average, only 1% of tickets have been escalated to management over the
past five quarters. Q2 2020 reported the highest rate at only 2%.
Maturity Level 4
Met - See above.
Remarks
Maturity Level 1
Met - A ticket where a Senior TIA has been added as a participant, an assignee, or
added comments is considered to have been functionally escalated within IT
Support. Performance is reported quarterly.
Maturity Level 2
Met - The target is to ensure that less than 3% of tickets get escalated. Currently,
performance was reported at 1%.
Maturity Level 3
Met - Only 1% of tickets have been functionally escalated within IT Support over the
past five quarters.
Maturity Level 4
Met - See above.
Remarks
Maturity Level 1
Met - When a member of another team outside IT Support has been added as a
participant or assigned to a ticket it is considered a functional escalation. These are
tracked and reported quarterly.
Maturity Level 2
Met - The SLO for functional escalations is to ensure that less than 4% of closed
tickets were escalated. Currently, performance was reported at 2%.
Maturity Level 3
Met - Only 2% of tickets have been functionally escalated outside IT Support over
the past five quarters.
Maturity Level 4
Met - See above.
Remarks
Maturity Level 1
Met - The average incident resolution time by priority level is reported quarterly by
location and compared against the SLA and SLO resolution targets.
Maturity Level 2
Met - The target is to ensure that there are no breaches of SLO/SLA targets.
Maturity Level 3
Met - Only one SLA average resolution time target has been missed for medium
priority issues in one location.
Maturity Level 4
Not Met - The number of SLO resolutions times was missed. The number had been
dropping since its peak in Q2 2019 but appears to be rising.
Remarks
Maturity Level 1
Met - The number of times an article within the Confluence knowledge base gets
linked to a resolved ticket is tracked and reported quarterly.
Maturity Level 2
Met - A target is set to exceed a 1% link rate. Currently in Q2, the link rate is 0.47%.
Maturity Level 3
Not Met - While a positive trend has been seen over the past 4 quarters,
performance is still far away from the desired target, which is found to be very low.
Maturity Level 4
Not Met - The target has yet to be achieved.
Remarks
Maturity Level 1
Met - The cost per resolved ticket is calculated using actual labour costs for all TIAs.
It is calculated and reported quarterly.
Maturity Level 2
Not Met - No target has been set. The cost per ticket in Q1 was $89.
Maturity Level 3
Not Met - Costs range from a low of $72 to a high of $93 per resolved ticket over
the past 6 quarters. However, performance cannot be assessed without an
established target.
Maturity Level 4
Not Met - See above.
8.130 Quality
The quality of support center interactions should be measured and reported (e.g.,
measurable results from criteria defined in the quality assurance management program).
Level Maturity Description Yes/No
Performance data is collected and reported on a regular schedule
1 Yes
(e.g., monthly, quarterly, twice yearly, or yearly).
Reports show performance data compared against an established,
2 Yes
quantitative performance goal/target.
Reports show performance data trending toward the established
3 goal/target over the past six months (or equivalent reporting Yes
periods).
Reports show the established performance goal/target has been
4 achieved or exceeded in at least nine of the past twelve months (or No
equivalent reporting periods).
Current State Maturity Rating 3
Remarks
Maturity Level 1
Met - The review of quality of recorded tickets is ongoing. Results are tabulated and
reported quarterly.
Maturity Level 2
Met - The overall target on quality was raised from 90 to 94 in 2020. The combined
rating for the most current reported data is 95.5%.
Maturity Level 3
Met - Quality scores have stayed above the target and improved slightly.
Maturity Level 4
Not Met - Quality reviews only began in Q4 2019, not allowing enough data to
qualify for the rating of a 4.
7. Auditor Information
7.1 Auditor
Darrell Bond is one of the founding partners of RADAR Solutions Group Inc., a services
management consulting and training provider focused on creating service excellence. Since
1998, RADAR has been helping customers enhance their service delivery operation s through
business and operations assessments, process improvement activities, and skills
development.
Darrell has applied his successful management techniques to a wide variety of projects and
programs ranging from locally focused service improvement projects to implementation of
worldwide service programs. He has been instrumental in helping transform organizations
through the adoption and integration of ITSM principles and processes including Incident,
Problem, Change, and Knowledge Management. In addition to defining and improving
processes, many of these projects have involved enhancing or integrating new service
management systems and telephone technologies.
With more than 36 years of experience in customer service delivery, Darrell has a strong
background in helping new businesses build service capabilities and existing organizations
transform, expand and improve their services through the application of proven best
practices. With a reputation for exceeding client expectations, Darrell’s quest to help others
improve service quality led him to become an HDI Certified Auditor, Assessor, and Instructor
where he teaches various classes for directors, managers, analysts, and individual
contributors.
Member of:
• HDI International Standards Committee
Mobile: 613-797-5141
Email: [email protected]
Fourteen years ago, Steve’s path migrated to IT Service Management consulting and training
utilizing the ISO/IEC 20000 Standard for IT Service Management and the ITIL® best
practices framework. It was this path that also led Steve to becoming an advocate and
ardent supporter of HDI and the HDI Support Center Standard. He’s been a Certified HDI
Auditor since 2012 and is also a member of the HDI Certification Standards Committee,
which is responsible for the development and maintenance of HDI standards used
worldwide.
Steve holds a B.S. in Business Administration from the University of Louisville and possesses
two of the highest-level IT Service Management (ITSM) related certifications.
8. How to contact us
If you have questions or comments after reading this report, or need clarification, please do
not hesitate to contact the auditor or HDI.
HDI
121 S. Tejon Street, Suite #1100
Colorado Springs, CO 80903
Toll-free: (800) 248-5667
Email: [email protected]
9.1 Leadership
Leadership defines how managers and employees guide their organizations toward success
by inspiring and motivating employees. Support personnel should understand why their job
is important, receive satisfaction from their work, and feel supported and valued for their
efforts by management. Effective leaders guide the formulation and evolution of statements
of purpose, and ensure that they are communicated and understood throughout the entire
organization. They provide highly visible support and encouragement. Important leadership
skills include fostering meaningful teamwork, resolving communication issues, determining
resource requirements, determining priorities, and inspiring an environment of cooperation
and enthusiasm.
acted upon, measured and revised as required to achieve desired results. Specific plans,
policies and procedures must be established to define the way in which the organizational
goals will be achieved. To be useful, plans must lead to the achievement of measurable
results and be coordinated with the plans of the organization.
9.4 Resources
The support center must have access to the resources and tools necessary to achieve its
goals and objectives; these may be infrastructure-related or support-specific. The scope of
this includes financial and human resources, physical facilities, communications infrastructure
and processes, specialized organizational knowledge and competencies, hardware/software
tools, and/or third party partnerships. Support technology including telephony, labs and
equipment, workforce management systems, service management systems, remote access
tools, knowledge management systems and reporting systems can provide significant
improvements in support center efficiency and customer productivity, which should result in
cost savings, revenue enhancements, higher quality services, and better alignment with
business needs.