Service Management Processes: Difference between revisions
From YaSM Service Management Wiki
No edit summary |
No edit summary |
||
| Line 55: | Line 55: | ||
<img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-structure/Yasm-processes-thumb.jpg" width="480" height="480" title="Service management processes: The YaSM process structure" alt="The YaSM service management process model distinguishes between service lifecycle processes and supporting processes." /></a></div> | <img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-structure/Yasm-processes-thumb.jpg" width="480" height="480" title="Service management processes: The YaSM process structure" alt="The YaSM service management process model distinguishes between service lifecycle processes and supporting processes." /></a></div> | ||
<p id="md-service-management-process-structure-description" itemprop="description">In the YaSM service management | <p style=" word-wrap:normal;" id="md-service-management-process-structure-description" itemprop="description">In the YaSM service management model we distinguish between <i>service lifecycle processes</i> and <i>supporting processes</i>.</p> | ||
<p id="YaSM_process_structure"> </p> | <p id="YaSM_process_structure"> </p> | ||
| Line 63: | Line 63: | ||
<li>Operate the services, including resolve incidents, service requests and problems</li> | <li>Operate the services, including resolve incidents, service requests and problems</li> | ||
<li>Improve the services.</li></ul> | <li>Improve the services.</li></ul> | ||
<p>The <a href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Supporting_processes" title="Supporting processes in YaSM service management">supporting processes</a> provide various kinds of support to the service lifecycle processes, such as the management of customer relationships, projects, etc.</p> | <p>The <a href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Supporting_processes" title="Supporting processes in YaSM service management">supporting processes</a> provide various kinds of support to the service lifecycle processes, such as the management of customer relationships, projects, etc.</p> | ||
<p>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 <a href="https://yasm.com/wiki/en/index.php/YaSM_Glossary">YaSM glossary</a>, where you will find definitions of all service management terms.<br style="clear:both;"/></html> | <p>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 <a href="https://yasm.com/wiki/en/index.php/YaSM_Glossary">YaSM glossary</a>, where you will find definitions of all service management terms.<br style="clear:both;"/></html> | ||
| Line 97: | Line 95: | ||
<img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-structure/service-lifecycle-processes-thumb.jpg" width="480" height="480" title="Service lifecycle processes in YaSM" alt="The service lifecycle in the YaSM Service Management Model ('LP processes')." /></a></div> | <img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-structure/service-lifecycle-processes-thumb.jpg" width="480" height="480" title="Service lifecycle processes in YaSM" alt="The service lifecycle in the YaSM Service Management Model ('LP processes')." /></a></div> | ||
<div id="md-service-management-processes-lp-description" itemprop="description"><p>The lifecycle processes ('LP') in YaSM service management are directly concerned with managing the service provider's range of services across their lifecycle.</p> | <div id="md-service-management-processes-lp-description" itemprop="description"><p style=" word-wrap:normal;">The lifecycle processes ('LP') in YaSM service management are directly concerned with managing the service provider's range of services across their lifecycle.</p> | ||
<p>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.</p> | <p>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.</p> | ||
<p>Once that decision has been made, the service lifecycle processes will design, build, deploy, operate and constantly improve the services.</p></div> | <p>Once that decision has been made, the service lifecycle processes will design, build, deploy, operate and constantly improve the services.</p></div> | ||
| Line 109: | Line 107: | ||
<link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-structure/service-lifecycle-processes.jpg" /> | <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-structure/service-lifecycle-processes.jpg" /> | ||
<p>These are the <i>five service lifecycle processes</i> and their process objectives:</p> | <p>These are the <i>five service lifecycle processes</i> and their process objectives:</p> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP1:_Set_the_strategic_direction" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP1:_Set_the_strategic_direction" itemscope itemtype="https://schema.org/CreativeWork"> | ||
| Line 116: | Line 113: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP2:_Design_new_or_changed_services" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP2:_Design_new_or_changed_services" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM service design process" /> | <meta itemprop="alternateName" content="YaSM service design process" /> | ||
| Line 122: | Line 118: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP3:_Build_new_or_changed_service" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP3:_Build_new_or_changed_service" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM service transition process" /> | <meta itemprop="alternateName" content="YaSM service transition process" /> | ||
| Line 128: | Line 123: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM service operation process" /> | <meta itemprop="alternateName" content="YaSM service operation process" /> | ||
| Line 135: | Line 129: | ||
<dd>The service operation process includes two prominent sub-processes, <a href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests">LP4.6: Resolve incidents and service requests</a> and <a href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems">LP4.7: Resolve problems</a>.</dd></dl> | <dd>The service operation process includes two prominent sub-processes, <a href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests">LP4.6: Resolve incidents and service requests</a> and <a href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems">LP4.7: Resolve problems</a>.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP5:_Improve_the_services" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/LP5:_Improve_the_services" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM CSI process" /> | <meta itemprop="alternateName" content="YaSM CSI process" /> | ||
| Line 171: | Line 164: | ||
<img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-structure/supporting-service-management-processes-thumb.jpg" width="480" height="480" title="Supporting processes in YaSM" alt="The supporting processes in the YaSM Service Management Model ('SP processes')." /></a></div> | <img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-structure/supporting-service-management-processes-thumb.jpg" width="480" height="480" title="Supporting processes in YaSM" alt="The supporting processes in the YaSM Service Management Model ('SP processes')." /></a></div> | ||
<p id="Supporting_service_management_processes"><span id="md-service-management-processes-sp-description" itemprop="description">The supporting processes ('SP') in YaSM service management provide various kinds of support to the <a href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Service_lifecycle_processes" title="Service lifecycle processes in YaSM service management">service lifecycle processes</a>.</span></p> | <p style=" word-wrap:normal;" id="Supporting_service_management_processes"><span id="md-service-management-processes-sp-description" itemprop="description">The supporting processes ('SP') in YaSM service management provide various kinds of support to the <a href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Service_lifecycle_processes" title="Service lifecycle processes in YaSM service management">service lifecycle processes</a>.</span></p> | ||
<div itemid="https://yasm.com/wiki/en/index.php/Service_Management_Processes#supporting-processes" itemscope="itemscope" itemtype="https://schema.org/CreativeWork" itemref="md-service-management-processes-sp-description"><!-- define schema.org/CreativeWork --> | <div itemid="https://yasm.com/wiki/en/index.php/Service_Management_Processes#supporting-processes" itemscope="itemscope" itemtype="https://schema.org/CreativeWork" itemref="md-service-management-processes-sp-description"><!-- define schema.org/CreativeWork --> | ||
| Line 180: | Line 173: | ||
<link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-structure/supporting-service-management-processes.jpg" /> | <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-structure/supporting-service-management-processes.jpg" /> | ||
<p>These are the <i>twelve supporting processes</i> and their process objectives:</p> | <p>These are the <i>twelve supporting processes</i> and their process objectives:</p> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP1:_Set_up_and_maintain_the_service_management_system" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP1:_Set_up_and_maintain_the_service_management_system" itemscope itemtype="https://schema.org/CreativeWork"> | ||
| Line 187: | Line 179: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP2:_Maintain_the_service_portfolio" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP2:_Maintain_the_service_portfolio" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM service portfolio management process" /> | <meta itemprop="alternateName" content="YaSM service portfolio management process" /> | ||
| Line 193: | Line 184: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM customer relationship management process" /> | <meta itemprop="alternateName" content="YaSM customer relationship management process" /> | ||
| Line 199: | Line 189: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP4:_Manage_configuration_information" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP4:_Manage_configuration_information" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM configuration management process" /> | <meta itemprop="alternateName" content="YaSM configuration management process" /> | ||
| Line 205: | Line 194: | ||
</dt><dd itemprop="description">Process objective: To maintain information about configuration items required to deliver the services, including their relationships.</dd></dl> | </dt><dd itemprop="description">Process objective: To maintain information about configuration items required to deliver the services, including their relationships.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM change management process" /> | <meta itemprop="alternateName" content="YaSM change management process" /> | ||
| Line 211: | Line 199: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP6:_Manage_projects" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP6:_Manage_projects" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM project management process" /> | <meta itemprop="alternateName" content="YaSM project management process" /> | ||
| Line 217: | Line 204: | ||
</dt><dd itemprop="description">Process objective: To plan and coordinate the resources to complete a project within time, cost and scope.</dd></dl> | </dt><dd itemprop="description">Process objective: To plan and coordinate the resources to complete a project within time, cost and scope.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP7:_Ensure_security" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP7:_Ensure_security" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM security management process" /> | <meta itemprop="alternateName" content="YaSM security management process" /> | ||
| Line 223: | Line 209: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP8:_Prepare_for_disaster_events" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP8:_Prepare_for_disaster_events" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM service continuity management process" /> | <meta itemprop="alternateName" content="YaSM service continuity management process" /> | ||
| Line 229: | Line 214: | ||
</dt><dd itemprop="description">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.</dd></dl> | </dt><dd itemprop="description">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.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP9:_Ensure_compliance" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP9:_Ensure_compliance" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM compliance management process" /> | <meta itemprop="alternateName" content="YaSM compliance management process" /> | ||
| Line 235: | Line 219: | ||
</dt><dd itemprop="description">Process objective: To ensure that services, processes and systems comply with relevant legal requirements, standards, enterprise policies etc.</dd></dl> | </dt><dd itemprop="description">Process objective: To ensure that services, processes and systems comply with relevant legal requirements, standards, enterprise policies etc.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP10:_Manage_human_resources" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP10:_Manage_human_resources" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM HR management process" /> | <meta itemprop="alternateName" content="YaSM HR management process" /> | ||
| Line 241: | Line 224: | ||
</dt><dd itemprop="description">Process objective: To provide the skills and levels of staff required by the service provider to achieve its objectives.</dd></dl> | </dt><dd itemprop="description">Process objective: To provide the skills and levels of staff required by the service provider to achieve its objectives.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP11:_Manage_suppliers" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP11:_Manage_suppliers" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM supplier management process" /> | <meta itemprop="alternateName" content="YaSM supplier management process" /> | ||
| Line 247: | Line 229: | ||
</dt><dd itemprop="description">Process objective: To ensure that all agreements with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.</dd></dl> | </dt><dd itemprop="description">Process objective: To ensure that all agreements with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.</dd></dl> | ||
</div> | </div> | ||
<div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP12:_Manage_service_financials" itemscope itemtype="https://schema.org/CreativeWork"> | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP12:_Manage_service_financials" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM financial management process" /> | <meta itemprop="alternateName" content="YaSM financial management process" /> | ||
| Line 259: | Line 240: | ||
==<span id="Comparison:_YaSM_and_ITIL_processes">Comparison: YaSM vs ITIL practices and processes</span>== | ==<span id="Comparison:_YaSM_and_ITIL_processes">Comparison: YaSM vs ITIL practices and processes</span>== | ||
<html>YaSM and <a href="https://yasm.com/wiki/en/index.php/ITIL" title="ITIL (IT Infrastructure Library)">ITIL</a><sup><small>®</small></sup> have common roots and share the same principles, so users familiar with ITIL will find the YaSM processes easy to read.</p> | <html>YaSM and <a href="https://yasm.com/wiki/en/index.php/ITIL" title="ITIL (IT Infrastructure Library)">ITIL</a><sup><small>®</small></sup> have common roots and share the same principles, so users familiar with ITIL will find the YaSM service management processes easy to read.</p> | ||
<p> </p> | <p> </p> | ||
<p style="font-size: | <p style="font-size: 110%;">ITIL 4</p> | ||
<p><a href="https://yasm.com/wiki/en/index.php/ITIL#ITIL_4" title="ITIL 4 ('ITIL 4')">ITIL 4</a> describes a service value system and service management practices. It is not prescriptive about processes, but service providers that wish to follow the guidance in ITIL V4 ultimately need to translate that guidance into clear-cut processes.</p> | <p><a href="https://yasm.com/wiki/en/index.php/ITIL#ITIL_4" title="ITIL 4 ('ITIL 4')">ITIL 4</a> describes a service value system and service management practices. It is not prescriptive about processes, but service providers that wish to follow the guidance in ITIL V4 ultimately need to translate that guidance into clear-cut processes.</p> | ||
| Line 271: | Line 252: | ||
<p> </p> | <p> </p> | ||
<p style="font-size: | <p style="font-size: 110%;">ITIL V3</p> | ||
<p>Those who are trained in the earlier edition | <p>Those who are trained in the earlier edition of <a href="https://yasm.com/wiki/en/index.php/ITIL#ITIL_V3" title="ITIL V3 (ITIL 2011)">ITIL V3</a> will recognize the similarity between the YaSM process structure and the service lifecycle introduced with ITIL V3 - but also the differences:</p> | ||
<ul style="list-style-image: URL('/wiki/en/img/yasm-wiki/icon-arrow-right.png');padding-left: 18px;"> | <ul style="list-style-image: URL('/wiki/en/img/yasm-wiki/icon-arrow-right.png');padding-left: 18px;"> | ||
<li><a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL_V3" title="ITIL V3 vs. YaSM service management">YaSM vs ITIL V3</a></li></ul></html> | <li><a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL_V3" title="ITIL V3 vs. YaSM service management">YaSM vs ITIL V3</a></li></ul></html> | ||
In the YaSM model, we chose to arrange a set | In the YaSM model, 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 easier to understand. | ||
<html>Some of the complexity in ITIL V3 results from the fact that ITIL places every process in one | <html>Some of the complexity in ITIL V3 results from the fact that ITIL places every process in one of <a class="external text" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_V3" title="ITIL Processes (ITIL V3)| IT Process Wiki - the ITIL® Wiki">five service lifecycle stages</a>: 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 define the management of configuration information as a "supporting" process outside the service lifecycle.</html> | ||
<p> </p> | <p> </p> | ||
| Line 298: | Line 279: | ||
<meta itemprop="keywords" content="ITSM processes" /> | <meta itemprop="keywords" content="ITSM processes" /> | ||
<meta itemprop="keywords" content="ESM processes" /> | <meta itemprop="keywords" content="ESM processes" /> | ||
<img itemprop="thumbnailUrl" style=" | <img itemprop="thumbnailUrl" style="display: block; float: left; margin-left: 10px; margin-right: 20px;" src="https://yasm.com/wiki/en/img/yasm-structure/service-management-processes-yasm.jpg" width="320" height="160" title="Service management processes" alt="YaSM service management reference processes for enterprise service management (ESM) / business service management (BSM), IT service management (ITSM) and ISO 20000 initiatives." /></a></div> | ||
<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 style="word-wrap:normal;">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 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>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> | ||
| Line 306: | Line 287: | ||
<p><small> | <p><small> | ||
<span itemprop="breadcrumb" itemscope itemtype=" | <span itemprop="breadcrumb" itemscope itemtype="https://schema.org/BreadcrumbList"> | ||
<span itemprop="itemListElement" itemscope itemtype=" | <span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem"> | ||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Process_structure"> | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Process_structure"> | ||
<span itemprop="name">Process structure</span></a> | <span itemprop="name">Process structure</span></a> | ||
<meta itemprop="position" content="1" /></span> › | <meta itemprop="position" content="1" /></span> › | ||
<span itemprop="itemListElement" itemscope itemtype=" | <span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem"> | ||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Service_lifecycle_processes"> | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Service_lifecycle_processes"> | ||
<span itemprop="name">Service lifecycle processes</span></a> | <span itemprop="name">Service lifecycle processes</span></a> | ||
<meta itemprop="position" content="2" /></span> › | <meta itemprop="position" content="2" /></span> › | ||
<span itemprop="itemListElement" itemscope itemtype=" | <span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem"> | ||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Supporting_processes"> | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#Supporting_processes"> | ||
<span itemprop="name">Supporting processes</span></a> | <span itemprop="name">Supporting processes</span></a> | ||
| Line 330: | Line 311: | ||
<meta itemprop="dateCreated" content="2014-06-04" /> | <meta itemprop="dateCreated" content="2014-06-04" /> | ||
<meta itemprop="datePublished" content="2014-08-03" /> | <meta itemprop="datePublished" content="2014-08-03" /> | ||
<meta itemprop="dateModified" content=" | <meta itemprop="dateModified" content="2021-08-04" /> | ||
<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-structure/Yasm-processes.jpg" /> | <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-structure/Yasm-processes.jpg" /> | ||
<span itemid="https://yasm.com/wiki/en/index.php/Service_Management_Processes#service-management-processes" itemscope="itemscope" itemtype="https://schema.org/CreativeWork" itemref="md-service-management-process-structure-description"><!-- define schema.org/CreativeWork --> | <span itemid="https://yasm.com/wiki/en/index.php/Service_Management_Processes#service-management-processes" itemscope="itemscope" itemtype="https://schema.org/CreativeWork" itemref="md-service-management-process-structure-description"><!-- define schema.org/CreativeWork --> | ||
| Line 353: | Line 334: | ||
[[Category:YaSM process|!]] | [[Category:YaSM process|!]] | ||
<!-- --- --> | <!-- --- --> | ||
Revision as of 11:49, 13 June 2020
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 model 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 vs ITIL practices and processes
YaSM and ITIL® have common roots and share the same principles, so users familiar with ITIL will find the YaSM service management processes easy to read.
ITIL 4
ITIL 4 describes a service value system and service management practices. It is not prescriptive about processes, but service providers that wish to follow the guidance in ITIL V4 ultimately need to translate that guidance into clear-cut processes.
YaSM is well aligned with ITIL 4 and the YaSM service management processes are a good starting point for organizations that seek to adopt this latest edition of ITIL. For a detailed comparison of the YaSM processes model and the various ITIL 4 components, see
ITIL V3
Those who are trained in the earlier edition of ITIL V3 will recognize the similarity between the YaSM process structure and the service lifecycle introduced with ITIL V3 - but also the differences:
In the YaSM model, we chose to arrange a set of supporting processes "underneath" the lifecycle processes because this makes the whole process structure 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 define 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
