Service Management Processes: Difference between revisions
No edit summary |
No edit summary |
||
| Line 259: | Line 259: | ||
==<span id="comparison-yasm-itil-prozesse">Comparison: YaSM and ITIL processes</span>== | ==<span id="comparison-yasm-itil-prozesse">Comparison: YaSM and ITIL processes</span>== | ||
Those familiar with [https://wiki.en.it-processmaps.com/index.php/Main_Page ITIL®] will recognize the similarity between the YaSM process structure and the service lifecycle introduced with ITIL | Those familiar with [https://wiki.en.it-processmaps.com/index.php/Main_Page ITIL®] will recognize the similarity between the YaSM process structure and the service lifecycle introduced with ITIL V3 - but also the differences (see also: "[[YaSM and ITIL V3|How YaSM relates to ITIL V3]]"). | ||
We chose to arrange a set of [[#Supporting_processes|supporting processes]] "underneath" the [[#Service_lifecycle_processes|lifecycle processes]] because this makes the whole process structure a lot easier to understand: | We chose to arrange a set of [[#Supporting_processes|supporting processes]] "underneath" the [[#Service_lifecycle_processes|lifecycle processes]] because this makes the whole process structure a lot easier to understand: | ||
Some of the complexity in ITIL results from the fact that ITIL places every process in one of [https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_2011 five service lifecycle stages]. Configuration management, for instance, is part of the service transition stage. But configuration management activities take place at various points across the service lifecycle, and configuration information is needed as an input for virtually every ITIL process. It is thus more straightforward and intuitive to treat the management of configuration information as a "supporting" process outside the service lifecycle. | Some of the complexity in ITIL V3 results from the fact that ITIL places every process in one of [https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_2011 five service lifecycle stages]. Configuration management, for instance, is part of the service transition stage. But configuration management activities take place at various points across the service lifecycle, and configuration information is needed as an input for virtually every ITIL process. It is thus more straightforward and intuitive to treat the management of configuration information as a "supporting" process outside the service lifecycle. | ||
<p> </p> | <p> </p> | ||
| Line 285: | Line 285: | ||
<p>Based on: Reference processes for enterprise service management (ESM / BSM), IT service management (ITSM) and ISO 20000 from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p> | <p>Based on: Reference processes for enterprise service management (ESM / BSM), IT service management (ITSM) and ISO 20000 from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p> | ||
<p>By:  Stefan Kempter <a | <p>By:  Stefan Kempter <a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.<br /><br/>Trademarks: ITIL® is a registered trademark of AXELOS Limited.</p> | ||
<p style="clear:both;"> </p> | <p style="clear:both;"> </p> | ||
Revision as of 18:28, 28 March 2019
Service management processes aim to transform the service provider's resources into valuable customer services. These services are to be made available at agreed levels of quality, cost, and risk.
Process structure
In the YaSM service management processes we distinguish between service lifecycle processes and supporting processes.
The service lifecycle processes are modeled upon a well-established management method for continuous improvement, known for example as the Deming or Plan-Do-Check-Act cycle. The lifecycle processes
- Decide upon the service provider's strategic direction and the range of services to be offered to customers
- Design, build and deploy new or changed services
- Operate the services, including resolve incidents, service requests and problems
- Improve the services.
The supporting processes provide various kinds of support to the service lifecycle processes, such as the management of customer relationships, projects, etc.
Below is a brief introduction to the YaSM processes, highlighting their purpose within the YaSM service management model and the most important activities. We recommend reading this introduction in combination with the YaSM glossary, where you will find definitions of all service management terms.
Service lifecycle processes
The lifecycle processes ('LP') in YaSM service management are directly concerned with managing the service provider's range of services across their lifecycle.
Strategic assessments of the service provider's current situation and future developments provide the basis for deciding which services are to be offered to customers.
Once that decision has been made, the service lifecycle processes will design, build, deploy, operate and constantly improve the services.
These are the five service lifecycle processes and their process objectives:
- LP1: Set the strategic direction
- Process objective: To decide on a strategy to serve customers. Starting from an assessment of customer needs and the market place, the strategic process determines which services the organization is to offer and what capabilities are required.
- LP2: Design new or changed services
- Process objective: To define the expected outcomes and required properties of a new or changed service, to determine the infrastructure and other capabilities which are needed to provide the service, and to develop the approach for its implementation.
- LP3: Build new or changed services
- Process objective: To build and deploy new or significantly changed services. This includes the coordination of development, acquisition and testing of all required service components.
- LP4: Operate the services
- Process objective: To ensure the services are delivered effectively and efficiently, in line with the contractual commitments. This includes fulfilling service requests, resolving incidents and problems, as well as carrying out routine operational tasks.
- The service operation process includes two prominent sub-processes, LP4.6: Resolve incidents and service requests and LP4.7: Resolve problems.
- LP5: Improve the services
- Process objective: To continually check if the services deliver the required outcomes and to identify potentials for improvement in the way the services are being produced.
Supporting processes
The supporting processes ('SP') in YaSM service management provide various kinds of support to the service lifecycle processes.
These are the twelve supporting processes and their process objectives:
- SP1: Set up and maintain the service management system
- Process objective: To establish, operate and continually improve the service management system (SMS). In particular, this process is responsible for managing the service management policies and processes as key components of the SMS.
- SP2: Maintain the service portfolio
- Process objective: To ensure the service portfolio contains consistent and up-to-date information on the services managed by the service provider. This is mainly achieved by controlling changes to the service portfolio and service definitions, as well as performing regular service portfolio reviews.
- SP3: Manage customer relationships
- Process objective: To maintain a positive relationship with the customers. In particular, the customer relationship management process identifies potential new customers and ensures that regular feedback is obtained from existing customers through customer meetings and surveys. This process is also responsible for signing customer service agreements with the service provider's customers.
- SP4: Manage configuration information
- Process objective: To maintain information about configuration items required to deliver the services, including their relationships.
- SP5: Assess and coordinate changes
- Process objective: To control the lifecycle of all changes. The primary concern of the change assessment process is to enable beneficial changes to be made, with minimum disruption to services.
- SP6: Manage projects
- Process objective: To plan and coordinate the resources to complete a project within time, cost and scope.
- SP7: Ensure security
- Process objective: To ensure the security of the service provider's range of services, and to align the security needs of the service provider with those of its customers. This includes ensuring that systems and data are protected from intrusion and only accessed by authorized parties.
- SP8: Prepare for disaster events
- Process objective: To ensure that the service provider can provide minimum agreed service levels in the case of events considered disasters. This is achieved primarily by implementing mechanisms to prevent disasters from happening, and by establishing continuity plans and arrangements for the recovery of services once a disaster event has occurred.
- SP9: Ensure compliance
- Process objective: To ensure that services, processes and systems comply with relevant legal requirements, standards, enterprise policies etc.
- SP10: Manage human resources
- Process objective: To provide the skills and levels of staff required by the service provider to achieve its objectives.
- SP11: Manage suppliers
- Process objective: To ensure that all agreements with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.
- SP12: Manage service financials
- Process objective: To manage the service provider's budgeting, accounting and charging requirements.
Comparison: YaSM and ITIL processes
Those familiar with ITIL® will recognize the similarity between the YaSM process structure and the service lifecycle introduced with ITIL V3 - but also the differences (see also: "How YaSM relates to ITIL V3").
We chose to arrange a set of supporting processes "underneath" the lifecycle processes because this makes the whole process structure a lot easier to understand:
Some of the complexity in ITIL V3 results from the fact that ITIL places every process in one of five service lifecycle stages. Configuration management, for instance, is part of the service transition stage. But configuration management activities take place at various points across the service lifecycle, and configuration information is needed as an input for virtually every ITIL process. It is thus more straightforward and intuitive to treat the management of configuration information as a "supporting" process outside the service lifecycle.
Notes
Based on: Reference processes for enterprise service management (ESM / BSM), IT service management (ITSM) and ISO 20000 from the YaSM Process Map.
By: Stefan Kempter 
and Andrea Kempter , IT Process Maps.
Trademarks: ITIL® is a registered trademark of AXELOS Limited.
Process structure › Service lifecycle processes › Supporting processes
