For the first phase we see the following deliverables and associated benefits:
-
A comprehensive service catalogue with a functional and a customer-service ‘view’ covering GS and IT services; easily extensible to cover other domains. This has the following benefits:
-
One coherent way to document services, clarifying expectations on quality and scope between providers and consumers
-
A single source that will constitute the reference for status boards, service desk, incident tracking tools, yellow pages, service portal, and all related future defined processes..
-
Give a perspective that did not exist previously, the usage of functional elements to provide customer services.
-
An organization independent view, hiding the internals of the ‘how’ from the users who are primarily interested by the ‘what’.
-
Provides a framework that can easily cover services provided by other departments.
-
A means to identify synergies between and duplication of services
-
A single incident management process covering all services provided by IT and GS (likely applicable or easily adaptable to services provide elsewhere at CERN). This has the following benefits:
-
Dramatic improvement in user experience by clear and coherent treatment of incidents from a user perspective, independent of the cause or nature of the incident, nor who is in charge of the resolution.
-
Standard process based on best practice allows for benchmarking inside (between service providers) and outside the organization.
-
Negotiation on service levels between customer and service owners based on objective measurable facts, independent on ‘who’ provides the service, nor ‘how’ it’s implemented.
-
A single request fulfillment process covering all services provided by IT and GS (likely applicable or easily adaptable to service provide elsewhere at CERN). This has the following benefits:
-
Same benefits as the incident management process
-
It provides a placeholder for all requests that are not yet covered by existing request fulfillment systems (like EDH and InforEAM).
-
A single tool to be shared by all actors involved in executing the processes we are putting in place. This has the following benefits:
-
Simplicity; users are completely isolated from the ‘who’ and ‘how’; coherent user interface, coherent behavior.
-
Steep learning curve (only need to learn one tool).
-
Agility; actors can move from one service to another without retraining on tools.
-
Trivial passing on of tickets between actors, allowing seamless collaboration across group and departmental boundaries, resulting in transparency.
-
Efficiency, no need to build multiple interfaces to glue multiple tools together.
-
A single entry point (Service Desk) that will take calls and provide support covering the entire scope of the services provided by IT and GS, with potential to cover a wider scope in future: This has the following benefits:
-
One number to call, one place to go, one web form to fill out
-
Easy natural knowledge sharing between agents
-
Higher motivation of agents due to varied and widened scope
-
Synergies; compared to the old scheme with multiple dedicated help desks, a single central service desks provides improved customer service through
-
Wider scope
-
Wider coverage over time (e.g.. telephone operator 24/7)
-
Redundancy and resiliance, backup to cover absences
-
Load balancing possible (if certain service areas are in high demand)
-
A management dashboard with performance indicators on service operation: This has the following benefits:
-
KPI’s based on common definitions for all services
-
Benchmarking within the organization and with the outside
-
Objective input for capacity management and other strategic processes (like financial management).
Page last updated on: 30 January 2017 at 17:15