YaSM and ITIL V3: Difference between revisions
No edit summary |
No edit summary |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 5: | Line 5: | ||
<meta property="og:title" content="Comparison: YaSM and ITIL® V3 | YaSM Service Management Wiki" /> | <meta property="og:title" content="Comparison: YaSM and ITIL® V3 | YaSM Service Management Wiki" /> | ||
<meta property="og:description" content="YaSM® vs. ITIL® V3 (ITIL 2011). - Differences and similarities of the two service management frameworks." /> | <meta property="og:description" content="YaSM® vs. ITIL® V3 (ITIL 2011). - Differences and similarities of the two service management frameworks." /> | ||
<meta property="og:site_name" content="YaSM"> | <meta property="og:site_name" content="YaSM Service Management"> | ||
<meta property="og:type" content="article | <meta property="og:type" content="article" /> | ||
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/itil/16x9/yasm-and-itil-v3.jpg" /> | <meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/itil/16x9/yasm-and-itil-v3.jpg" /> | ||
<meta property="og:image:width" content="1200" /> | <meta property="og:image:width" content="1200" /> | ||
<meta property="og:image:height" content="675" /> | <meta property="og:image:height" content="675" /> | ||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
Line 25: | Line 15: | ||
<p> </p> | <p> </p> | ||
<p><b>Comparison:</b> YaSM and the IT Infrastructure Library ITIL<sup><small>®</small></sup> V3 (ITIL 2011)</p> | <p><b>Comparison:</b> YaSM and the IT Infrastructure Library ITIL<sup><small>®</small></sup> V3 (ITIL 2011)</p> | ||
<p><b>Part of</b>: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></p> | <p><b>Part of</b>: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></html> | ||
<p> </p> | |||
< | [[What is YaSM|YaSM]]<sup><small>®</small></sup> was designed to be well aligned with the [[ITIL|IT Infrastructure Library ITIL]]<sup><small>®</small></sup> [[#ITIL|[1]]] so that users familiar with ITIL will instantly recognize the common principles.</span> | ||
<html> | * <span id="md-webpage-description" itemprop="description">This page provides a detailed account of <span id="md-webpage-educationalUse" itemprop="educationalUse">how the YaSM service management model relates to the previous version of ITIL V3 (ITIL 2011)</span>.</span> | ||
<div itemid="https://yasm.com/wiki/en/img/yasm-frameworks/itil/yasm-and-itil-v3.jpg" itemscope itemtype="https://schema.org/ImageObject | * There is another page with a [[YaSM and ITIL|detailed mapping between YaSM and the latest edition of ITIL 4]]. | ||
<p> </p> | |||
<html><div itemid="https://yasm.com/wiki/en/img/yasm-frameworks/itil/yasm-and-itil-v3.jpg" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="caption" content="ITIL V3 and YaSM service management: Comparison." /> | <meta itemprop="caption" content="ITIL V3 and YaSM service management: Comparison." /> | ||
<meta itemprop="width" content="1200" /> | <meta itemprop="width" content="1200" /> | ||
Line 37: | Line 30: | ||
<meta itemprop="dateCreated" content="2019-03-24" /> | <meta itemprop="dateCreated" content="2019-03-24" /> | ||
<meta itemprop="datePublished" content="2019-03-24" /> | <meta itemprop="datePublished" content="2019-03-24" /> | ||
<meta itemprop="dateModified" content="2023-10-28" /> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | <span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | ||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/itil/yasm-and-itil-v3.jpg" /> | <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/itil/yasm-and-itil-v3.jpg" /> | ||
Line 43: | Line 37: | ||
<meta itemprop="dateCreated" content="2019-03-24" /> | <meta itemprop="dateCreated" content="2019-03-24" /> | ||
<meta itemprop="datePublished" content="2019-03-24" /> | <meta itemprop="datePublished" content="2019-03-24" /> | ||
<meta itemprop="dateModified" content="2023-10-28" /> | |||
</span> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/itil/480px/yasm-and-itil-v3.jpg" /> | |||
<meta itemprop="width" content="480" /> | |||
<meta itemprop="height" content="360" /> | |||
<meta itemprop="dateCreated" content="2022-06-30" /> | |||
<meta itemprop="datePublished" content="2022-06-30" /> | |||
<meta itemprop="dateModified" content="2023-10-28" /> | |||
</span> | </span> | ||
<meta itemprop="keywords" content="ITIL V3 YaSM" /> | <meta itemprop="keywords" content="ITIL V3 YaSM" /> | ||
<meta itemprop="keywords" content="ITIL 2011 YaSM" /> | <meta itemprop="keywords" content="ITIL 2011 YaSM" /> | ||
<meta itemprop="keywords" content="ITIL service lifecycle" /> | <meta itemprop="keywords" content="ITIL service lifecycle" /> | ||
<img | <figure class="mw-halign-right" typeof="mw:File/Thumb"><a itemprop="contentUrl"href="https://yasm.com/wiki/en/img/yasm-frameworks/itil/yasm-and-itil-v3.jpg" title="YaSM and ITIL V3 (ITIL 2011)"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/itil/480px/yasm-and-itil-v3.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/itil/yasm-and-itil-v3.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/itil/yasm-and-itil-v3.jpg" fetchpriority="high" decoding="async" width="480" height="360" class="mw-file-element" alt="Comparison: ITIL V3 service lifecycle and related YaSM service management processes." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/itil/yasm-and-itil-v3.jpg" title="YaSM and ITIL V3 (ITIL 2011)">ITIL V3 and the YaSM model - Comparison</a></b><br />ITIL V3 service lifecycle processes vs. YaSM service management processes.</a></span></figcaption></figure></div></html> | ||
< | |||
__TOC__ | |||
<p style="clear:both;"> </p> | |||
<i>Notes:</i> | |||
<html><ul><li>YaSM is an independent process model and is not officially endorsed by the owners of ITIL.</li> | <html><ul><li>YaSM is an independent process model and is not officially endorsed by the owners of ITIL.</li> | ||
<li>All ITIL processes in the following tables are linked to IT Process Map's "<a class="external text" href="https://wiki.en.it-processmaps.com/index.php/Main_Page">ITIL® Wiki</a>", where you can find the relevant descriptions of the <a class="external text" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes">ITIL processes</a>.</li></ul></html> | <li id="comparison-yasm-itil">All ITIL processes in the following tables are linked to IT Process Map's "<a class="external text" href="https://wiki.en.it-processmaps.com/index.php/Main_Page">ITIL® Wiki</a>", where you can find the relevant descriptions of the <a class="external text" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes">ITIL processes</a>.</li></ul></html> | ||
<p> </p> | <p> </p> | ||
Line 67: | Line 63: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|+style="background:# | |+style="background:#465674;"|<span style="color:#ffffff; font-size: 110%;">ITIL<sup><small>®</small></sup> V3 Service Strategy vs. YaSM Service Management</span> | ||
|- | |- | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|ITIL<sup><small>®</small></sup> V3 pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Related YaSM pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Comparison: YaSM and ITIL V3 (ITIL 2011) | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|1.1 [https://wiki.en.it-processmaps.com/index.php/ITIL_Strategy_Management Strategy | |1.1 [https://wiki.en.it-processmaps.com/index.php/ITIL_Strategy_Management Strategy manage­ment for IT services] | ||
| | | | ||
*[[LP1: Set the strategic direction]] | *[[LP1: Set the strategic direction|LP1: Set the strategic direc­tion]] | ||
| | | | ||
*YaSM contains a streamlined strategic process which is broadly in line with ITIL, describing the activities for performing strategic assessments as well as crafting and executing the service strategy. | *YaSM contains a streamlined strategic process which is broadly in line with ITIL, describing the activities for performing strategic assessments as well as crafting and executing the service strategy. | ||
*ITIL provides additional guidance and background information, for example about analyzing the internal and external environments and defining the service provider's position in the market spaces to be served. | *ITIL provides additional guidance and background information, for example about analyzing the internal and external environments and defining the service provider's position in the market spaces to be served. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|1.2 [https://wiki.en.it-processmaps.com/index.php/Service_Portfolio_Management Service | |1.2 [https://wiki.en.it-processmaps.com/index.php/Service_Portfolio_Management Service port­folio manage­ment] | ||
| | | | ||
*[[LP1: Set the strategic direction]] | *[[LP1: Set the strategic direction|LP1: Set the strategic direc­tion]] | ||
*[[SP2: Maintain the service portfolio]] | *[[SP2: Maintain the service portfolio|SP2: Maintain the service port­folio]] | ||
| | | | ||
*Like ITIL, YaSM stipulates that the service provider's complete set of customer and supporting services is to be managed through the service portfolio. | *Like ITIL, YaSM stipulates that the service provider's complete set of customer and supporting services is to be managed through the service portfolio. | ||
Line 89: | Line 85: | ||
*Decisions about the composition of the service portfolio (i.e. the mix of services to be offered to customers) are the responsibility of YaSM's strategic process. | *Decisions about the composition of the service portfolio (i.e. the mix of services to be offered to customers) are the responsibility of YaSM's strategic process. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|1.3 [https://wiki.en.it-processmaps.com/index.php/Financial_Management | |1.3 [https://wiki.en.it-processmaps.com/index.php/Financial_Management Finan­cial manage­ment for IT services] | ||
| | | | ||
*[[SP12: Manage service financials]] | *[[SP12: Manage service financials|SP12: Manage service finan­cials]] | ||
| | | | ||
*Both ITIL and YaSM contain financial management processes which do not aim to describe all aspects of financial management, but are meant to highlight a number of financial management practices as related to service management. | *Both ITIL and YaSM contain financial management processes which do not aim to describe all aspects of financial management, but are meant to highlight a number of financial management practices as related to service management. | ||
*ITIL offers more detailed advice in a number of areas: for example, it explains commonly used cost models and charging methods. | *ITIL offers more detailed advice in a number of areas: for example, it explains commonly used cost models and charging methods. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|1.4 [https://wiki.en.it-processmaps.com/index.php/ITIL_Demand_Management Demand | |1.4 [https://wiki.en.it-processmaps.com/index.php/ITIL_Demand_Management Demand manage­ment] | ||
| | | | ||
*-/- | *-/- | ||
Line 103: | Line 99: | ||
*The ITIL publications provide additional guidance, for example on the concept of patterns of business activity. | *The ITIL publications provide additional guidance, for example on the concept of patterns of business activity. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|1.5 [https://wiki.en.it-processmaps.com/index.php/Business_Relationship_Management Business | |1.5 [https://wiki.en.it-processmaps.com/index.php/Business_Relationship_Management Business relation­ship manage­ment] | ||
| | | | ||
*[[SP3: Manage customer relationships]] | *[[SP3: Manage customer relationships|SP3: Manage custo­mer relation­ships]] | ||
| | | | ||
*YaSM's customer relationship management process is well aligned with the ITIL | *YaSM's customer relationship management process is well aligned with the ITIL recommen­dations: It is responsible for maintaining a business relationship between the service provider and the customer and for understanding customer needs. | ||
*This includes communicating with customers on a regular basis, measuring customer satisfaction and dealing with customer complaints. | *This includes communicating with customers on a regular basis, measuring customer satisfaction and dealing with customer complaints. | ||
|} | |} | ||
Line 118: | Line 114: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|+style="background:# | |+style="background:#465674;"|<span style="color:#ffffff; font-size: 110%;">ITIL<sup><small>®</small></sup> V3 Service Design vs. YaSM Service Management</span> | ||
|- | |- | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|ITIL<sup><small>®</small></sup> V3 pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Related YaSM pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Comparison: YaSM and ITIL V3 (ITIL 2011) | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|2.1 [https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination Design | |2.1 [https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination Design coordi­nation] | ||
| | | | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
*[[SP6: Manage projects]] | *[[SP6: Manage projects]] | ||
| | | | ||
Line 132: | Line 128: | ||
*A key output from YaSM's service design process is the "service implementation blueprint", which describes what capabilities are required in order to be able to offer a new or changed service, and outlines the approach to creating the required service infrastructure and other capabilities. The equivalent in ITIL is the "service design package (SDP)". The SDP is supposed to contain a considerable amount of additional information, such as various policies and plans. YaSM keeps such information in other documents. | *A key output from YaSM's service design process is the "service implementation blueprint", which describes what capabilities are required in order to be able to offer a new or changed service, and outlines the approach to creating the required service infrastructure and other capabilities. The equivalent in ITIL is the "service design package (SDP)". The SDP is supposed to contain a considerable amount of additional information, such as various policies and plans. YaSM keeps such information in other documents. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|2.2 [https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management Service | |2.2 [https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management Service cata­logue manage­ment] | ||
| | | | ||
*[[SP2: Maintain the service portfolio]] | *[[SP2: Maintain the service portfolio|SP2: Maintain the service port­folio]] | ||
| | | | ||
*Both ITIL and YaSM define service catalogs as specific views of the information contained in the service portfolio, but ITIL practitioners often seem to use the terms service catalog and service portfolio | *Both ITIL and YaSM define service catalogs as specific views of the information contained in the service portfolio, but ITIL practitioners often seem to use the terms service catalog and service portfolio inter­changeably. YaSM tries to avoid this confusion by mostly relating to the service portfolio. | ||
*The YaSM process for maintaining the service portfolio contains activities for publishing service catalogs and keeping them consistent and up to date, in line with updates to the service portfolio. | *The YaSM process for maintaining the service portfolio contains activities for publishing service catalogs and keeping them consistent and up to date, in line with updates to the service portfolio. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|2.3 [https://wiki.en.it-processmaps.com/index.php/Service_Level_Management Service level | |2.3 [https://wiki.en.it-processmaps.com/index.php/Service_Level_Management Service level manage­ment] | ||
| | | | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
*[[LP4: Operate the services]] | *[[LP4: Operate the services]] | ||
*[[LP5: Improve the services]] | *[[LP5: Improve the services]] | ||
*[[SP3: Manage customer relationships]] | *[[SP3: Manage customer relationships|SP3: Manage custo­mer relation­ships]] | ||
| | | | ||
*YaSM takes the view that several processes need to cooperate to manage service levels throughout the service lifecycle. Therefore, YaSM does not include a specific process for managing service levels. | *YaSM takes the view that several processes need to cooperate to manage service levels throughout the service lifecycle. Therefore, YaSM does not include a specific process for managing service levels. | ||
Line 154: | Line 150: | ||
*See also: [[Service Level Management|Service level management in YaSM]] | *See also: [[Service Level Management|Service level management in YaSM]] | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|<span id="yasm-vs-itil-availability-management">2.4 [https://wiki.en.it-processmaps.com/index.php/Availability_Management | |<span id="yasm-vs-itil-availability-management">2.4 [https://wiki.en.it-processmaps.com/index.php/Availability_Management Availa­bility manage­ment]</span> | ||
| | | | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
*[[LP3: Build new or changed services]] | *[[LP3: Build new or changed services]] | ||
*[[LP4: Operate the services]] | *[[LP4: Operate the services]] | ||
*[[LP5: Improve the services]] | *[[LP5: Improve the services]] | ||
| | | | ||
Line 166: | Line 162: | ||
*See also: [[Availability Management|Availability management in YaSM]] | *See also: [[Availability Management|Availability management in YaSM]] | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|<span id="yasm-vs-itil-capacity-management">2.5 [https://wiki.en.it-processmaps.com/index.php/Capacity_Management Capacity | |<span id="yasm-vs-itil-capacity-management">2.5 [https://wiki.en.it-processmaps.com/index.php/Capacity_Management Capacity manage­ment]</span> | ||
| | | | ||
*[[LP2: Design new or changed services]] | *[[LP2: Design new or changed services]] | ||
*[[LP3: Build new or changed services]] | *[[LP3: Build new or changed services]] | ||
*[[LP4: Operate the services]] | *[[LP4: Operate the services]] | ||
*[[LP5: Improve the services]] | *[[LP5: Improve the services]] | ||
| | | | ||
Line 178: | Line 174: | ||
*See also: [[Capacity Management|Capacity management in YaSM]] | *See also: [[Capacity Management|Capacity management in YaSM]] | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|2.6 [https://wiki.en.it-processmaps.com/index.php/IT_Service_Continuity_Management IT service | |2.6 [https://wiki.en.it-processmaps.com/index.php/IT_Service_Continuity_Management IT service conti­nuity manage­ment (ITSCM)] | ||
| | | | ||
*[[SP8: | *[[SP8: Ensure continuity]] | ||
| | | | ||
*Both processes ("ITSCM" in ITIL and " | *Both processes ("ITSCM" in ITIL and "Ensure continuity" in YaSM) focus on critical, disruptive events or disasters. | ||
*YaSM recommends that the | *YaSM recommends that the critical events against which the service provider has decided to set up some kind of protection are documented in a register of managed critical events. | ||
*Service continuity plans describe how service continuity is ensured with regards to particular types of | *Service continuity plans describe how service continuity is ensured with regards to particular types of critical events. The implementation of the required continuity arrangements is managed through the continuity improvement plan. | ||
*Once a | *Once a disruptive event occurs, YaSM deals with it through the major incident resolution process. This process will establish a major incident team which is authorized to invoke suitable service continuity plans. | ||
*ITIL offers additional advice, such as examples of potential risks and threats as well as recovery options. | *ITIL offers additional advice, such as examples of potential risks and threats as well as recovery options. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|2.7 [https://wiki.en.it-processmaps.com/index.php/IT_Security_Management | |2.7 [https://wiki.en.it-processmaps.com/index.php/IT_Security_Management Infor­mation security manage­ment] | ||
| | | | ||
*[[SP7: Ensure security]] | *[[SP7: Ensure security]] | ||
Line 196: | Line 192: | ||
*The ITIL publications contain additional advice, such as a list of recommended (supporting) security policies, and an overview of risk assessment and management methods. | *The ITIL publications contain additional advice, such as a list of recommended (supporting) security policies, and an overview of risk assessment and management methods. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|2.8 [https://wiki.en.it-processmaps.com/index.php/Supplier_Management Supplier | |2.8 [https://wiki.en.it-processmaps.com/index.php/Supplier_Management Supplier manage­ment] | ||
| | | | ||
*[[SP11: Manage suppliers]] | *[[SP11: Manage suppliers]] | ||
| | | | ||
*The supplier management process described in YaSM is in line with the ITIL | *The supplier management process described in YaSM is in line with the ITIL recommen­dations, with the following qualifications: | ||
*YaSM puts the service design process in charge of defining the requirements and deciding whether a supporting service should be provided by an internal or external party. Once this decision is taken, supplier management is called upon to select and establish suitable suppliers and to set up the external services. | *YaSM puts the service design process in charge of defining the requirements and deciding whether a supporting service should be provided by an internal or external party. Once this decision is taken, supplier management is called upon to select and establish suitable suppliers and to set up the external services. | ||
*The service operation process is responsible for monitoring the achieved service quality and producing service quality reports. This includes the monitoring of externally provided supporting services. | *The service operation process is responsible for monitoring the achieved service quality and producing service quality reports. This includes the monitoring of externally provided supporting services. | ||
*YaSM's service improvement process ensures that external services are reviewed on a regular basis. The findings from service reviews may lead to the identification and implementation of service improvements through a service improvement plan. | *YaSM's service improvement process ensures that external services are reviewed on a regular basis. The findings from service reviews may lead to the identification and implementation of service improvements through a service improvement plan. | ||
*ITIL offers additional | *ITIL offers additional recommen­dations, for example criteria for the selection of new suppliers and suggestions for supplier categorization. | ||
|} | |} | ||
Line 214: | Line 210: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|+style="background:# | |+style="background:#465674;"|<span style="color:#ffffff; font-size: 110%;">ITIL<sup><small>®</small></sup> V3 Service Transition vs. YaSM Service Management</span> | ||
|- | |- | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|ITIL<sup><small>®</small></sup> V3 pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Related YaSM pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Comparison: YaSM and ITIL V3 (ITIL 2011) | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|3.1 [https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Transition_Planning_and_Support | |3.1 [https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Transition_Planning_and_Support Transi­tion planning and support] | ||
| | | | ||
*[[SP6: Manage projects]] | *[[SP6: Manage projects]] | ||
Line 227: | Line 223: | ||
*ITIL takes a slightly different approach: The transition planning and support process is specifically meant to provide "overall planning for service transition projects". Some detailed transition planning is performed by two other ITIL processes, change management and release and deployment management. | *ITIL takes a slightly different approach: The transition planning and support process is specifically meant to provide "overall planning for service transition projects". Some detailed transition planning is performed by two other ITIL processes, change management and release and deployment management. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|3.2 [https://wiki.en.it-processmaps.com/index.php/Change_Management Change | |3.2 [https://wiki.en.it-processmaps.com/index.php/Change_Management Change manage­ment] | ||
| | | | ||
*[[SP5: Assess and coordinate changes]] | *[[SP5: Assess and coordinate changes|SP5: Assess and coor­dinate changes]] | ||
| | | | ||
*The change assessment process described in YaSM is in line with the ITIL | *The change assessment process described in YaSM is in line with the ITIL recommen­dations, with the following qualifications: | ||
*YaSM defines requests for change (RFCs) not as a separate data object type, but as the initial state of a change record that contains all information required to assess a proposed change. More information is added to the change record as it progresses through its life cycle. | *YaSM defines requests for change (RFCs) not as a separate data object type, but as the initial state of a change record that contains all information required to assess a proposed change. More information is added to the change record as it progresses through its life cycle. | ||
*YaSM does not distinguish between changes and change proposals. | *YaSM does not distinguish between changes and change proposals. | ||
Line 238: | Line 234: | ||
*While ITIL stipulates that the change manager produce a list of projected service outages (PSO), YaSM suggests that operational staff is in a better position to maintain a "calendar of planned service outages". This calendar takes into account outages due to various reasons, such as change deployments, operational activities, security tests, ... | *While ITIL stipulates that the change manager produce a list of projected service outages (PSO), YaSM suggests that operational staff is in a better position to maintain a "calendar of planned service outages". This calendar takes into account outages due to various reasons, such as change deployments, operational activities, security tests, ... | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|3.3 [https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management Service asset and | |3.3 [https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management Service asset and configu­ration manage­ment] | ||
| | | | ||
*[[SP4: Manage configuration information]] | *[[SP4: Manage configuration information|SP4: Manage config. infor­mation]] | ||
| | | | ||
*The configuration management process described in YaSM is in line with the ITIL | *The configuration management process described in YaSM is in line with the ITIL recommen­dations, with the following qualifications: | ||
*YaSM's process for managing configuration information provides the framework for controlling configu-ration items and the related configuration information. In particular, the configuration manager is responsible for specifying what types of CIs are to be controlled, and who is authorized to modify those CIs and the related contents of the CMS. | *YaSM's process for managing configuration information provides the framework for controlling configu-ration items and the related configuration information. In particular, the configuration manager is responsible for specifying what types of CIs are to be controlled, and who is authorized to modify those CIs and the related contents of the CMS. | ||
*The actual modifications to the CMS are mostly performed by other service management processes. The configuration manager will track and verify the modifications and perform regular audits of the information in the CMS. | *The actual modifications to the CMS are mostly performed by other service management processes. The configuration manager will track and verify the modifications and perform regular audits of the information in the CMS. | ||
*With regards to status accounting, YaSM's configuration management process defines a suitable set of allowed states for each CI type, and relies on other service management processes to record the status changes. | *With regards to status accounting, YaSM's configuration management process defines a suitable set of allowed states for each CI type, and relies on other service management processes to record the status changes. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|3.4 [https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management Release and | |3.4 [https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management Release and deploy­ment manage­ment] | ||
| | | | ||
*[[LP3: Build new or changed services]] | *[[LP3: Build new or changed services]] | ||
*[[SP6: Manage projects]] | *[[SP6: Manage projects]] | ||
| | | | ||
Line 256: | Line 252: | ||
*ITIL offers additional advice, for example on the design of release packages and deployment options for IT infrastructure. | *ITIL offers additional advice, for example on the design of release packages and deployment options for IT infrastructure. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|3.5 [https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing Service | |3.5 [https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing Service vali­dation and testing] | ||
| | | | ||
*[[LP3: Build new or changed services]] | *[[LP3: Build new or changed services]] | ||
Line 263: | Line 259: | ||
*The ITIL books contain additional information, such as an explanation of commonly used testing strategies and test types. | *The ITIL books contain additional information, such as an explanation of commonly used testing strategies and test types. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|3.6 [https://wiki.en.it-processmaps.com/index.php/ITIL_Change_Evaluation Change | |3.6 [https://wiki.en.it-processmaps.com/index.php/ITIL_Change_Evaluation Change evalu­ation] | ||
| | | | ||
*[[SP5: Assess and coordinate changes]] | *[[SP5: Assess and coordinate changes|SP5: Assess and coor­dinate changes]] | ||
| | | | ||
*ITIL stipulates that certain types of (significant) changes should be subjected to a formal change evaluation process. There is no separate change evaluation process in YaSM. Instead, YaSM treats change evaluation as part of its change assessment process. | *ITIL stipulates that certain types of (significant) changes should be subjected to a formal change evaluation process. There is no separate change evaluation process in YaSM. Instead, YaSM treats change evaluation as part of its change assessment process. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|3.7 [https://wiki.en.it-processmaps.com/index.php/Knowledge_Management | |3.7 [https://wiki.en.it-processmaps.com/index.php/Knowledge_Management Know­ledge manage­ment] | ||
| | | | ||
*-/- | *-/- | ||
Line 283: | Line 279: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|+style="background:# | |+style="background:#465674;"|<span style="color:#ffffff; font-size: 110%;">ITIL<sup><small>®</small></sup> V3 Service Operation vs. YaSM Service Management</span> | ||
|- | |- | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|ITIL<sup><small>®</small></sup> V3 pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Related YaSM pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Comparison: YaSM and ITIL V3 (ITIL 2011) | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|4.1 [https://wiki.en.it-processmaps.com/index.php/Event_Management Event | |4.1 [https://wiki.en.it-processmaps.com/index.php/Event_Management Event manage­ment] | ||
| | | | ||
*[[LP4: Operate the services]] | *[[LP4: Operate the services]] | ||
Line 297: | Line 293: | ||
*The ITIL publications contain additional guidance, for example on event filtering and correlation rules. | *The ITIL publications contain additional guidance, for example on event filtering and correlation rules. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|4.2 [https://wiki.en.it-processmaps.com/index.php/Incident_Management Incident | |4.2 [https://wiki.en.it-processmaps.com/index.php/Incident_Management Incident manage­ment] | ||
| | | | ||
*[[LP4.6: Resolve incidents and service requests]] | *[[LP4.6: Resolve incidents and service requests]] | ||
| | | | ||
*The process for resolving incidents and service requests described in YaSM is in line with the ITIL | *The process for resolving incidents and service requests described in YaSM is in line with the ITIL recommen­dations, with the following qualifications: | ||
*While ITIL suggests implementing two separate processes for managing incidents and service requests, YaSM takes the view that these processes are very similar in nature. There is thus one process in YaSM to deal with both incidents and service requests. | *While ITIL suggests implementing two separate processes for managing incidents and service requests, YaSM takes the view that these processes are very similar in nature. There is thus one process in YaSM to deal with both incidents and service requests. | ||
*ITIL states that incident management is about restoring services as quickly as possible, while problem management is about diagnosing and resolving the underlying causes of incidents. Individual organizations, however, are given some freedom regarding the precise rules on when to invoke problem management from incident management. In this respect, YaSM adopts a simple approach: The incident resolution process takes all necessary action to resolve an incident, possibly by applying a workaround and involving experts in 2nd and 3rd level support. The problem resolution process is called upon only after the incident has been closed, for example in cases where the underlying cause of an incident is unresolved or unclear. | *ITIL states that incident management is about restoring services as quickly as possible, while problem management is about diagnosing and resolving the underlying causes of incidents. Individual organizations, however, are given some freedom regarding the precise rules on when to invoke problem management from incident management. In this respect, YaSM adopts a simple approach: The incident resolution process takes all necessary action to resolve an incident, possibly by applying a workaround and involving experts in 2nd and 3rd level support. The problem resolution process is called upon only after the incident has been closed, for example in cases where the underlying cause of an incident is unresolved or unclear. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|4.3 [https://wiki.en.it-processmaps.com/index.php/Request_Fulfilment Request | |4.3 [https://wiki.en.it-processmaps.com/index.php/Request_Fulfilment Request fulfill­ment] | ||
| | | | ||
*[[LP4.6: Resolve incidents and service requests]] | *[[LP4.6: Resolve incidents and service requests]] | ||
| | | | ||
*The process for resolving incidents and service requests described in YaSM is in line with the ITIL | *The process for resolving incidents and service requests described in YaSM is in line with the ITIL recommen­dations, with the following qualifications: | ||
*While ITIL suggests implementing two different processes for managing incidents and service requests, YaSM suggests that these processes are very similar in nature. There is thus one process in YaSM to deal with both incidents and service requests. | *While ITIL suggests implementing two different processes for managing incidents and service requests, YaSM suggests that these processes are very similar in nature. There is thus one process in YaSM to deal with both incidents and service requests. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|4.4 [https://wiki.en.it-processmaps.com/index.php/Problem_Management Problem | |4.4 [https://wiki.en.it-processmaps.com/index.php/Problem_Management Problem manage­ment] | ||
| | | | ||
*[[LP4.7: Resolve problems]] | *[[LP4.7: Resolve problems]] | ||
| | | | ||
*The problem resolution process described in YaSM is in line with the ITIL | *The problem resolution process described in YaSM is in line with the ITIL recommen­dations, with the following qualifications: | ||
*Since according to ITIL known errors are "problems with an identified underlying cause and a workaround", YaSM recommends storing information about underlying causes and possible workarounds as part of the problem records. ITIL advocates managing known errors in a "known error database (KEDB)". | *Since according to ITIL known errors are "problems with an identified underlying cause and a workaround", YaSM recommends storing information about underlying causes and possible workarounds as part of the problem records. ITIL advocates managing known errors in a "known error database (KEDB)". | ||
*If a problem resolution requires a change, YaSM's problem resolution process will describe the change and prepare a business case; the change is then typically implemented through a service or process improvement plan under the responsibility of a service or process owner. | *If a problem resolution requires a change, YaSM's problem resolution process will describe the change and prepare a business case; the change is then typically implemented through a service or process improvement plan under the responsibility of a service or process owner. | ||
*ITIL offers additional background information, especially on problem analysis techniques. | *ITIL offers additional background information, especially on problem analysis techniques. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|4.5 [https://wiki.en.it-processmaps.com/index.php/Access_Management Access | |4.5 [https://wiki.en.it-processmaps.com/index.php/Access_Management Access manage­ment] | ||
| | | | ||
*[[LP4: Operate the services]] | *[[LP4: Operate the services]] | ||
*[[SP7: Ensure security]] | *[[SP7: Ensure security]] | ||
| | | | ||
Line 338: | Line 334: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|+style="background:# | |+style="background:#465674;"|<span style="color:#ffffff; font-size: 110%;">ITIL<sup><small>®</small></sup> V3 Continual Service Improvement vs. YaSM Service Management</span> | ||
|- | |- | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|ITIL<sup><small>®</small></sup> V3 pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Related YaSM pro­cesses | ||
!style="background:# | !style="background:#eeeeee; color:#465674;"|Comparison: YaSM and ITIL V3 (ITIL 2011) | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|5.1 [https://wiki.en.it-processmaps.com/index.php/Process_Evaluation The seven-step | |5.1 [https://wiki.en.it-processmaps.com/index.php/Process_Evaluation The seven-step improve­ment process] | ||
| | | | ||
*[[LP5: Improve the services]] | *[[LP5: Improve the services]] | ||
Line 357: | Line 353: | ||
==<span id="yasm-goes-beyond-itil">Where YaSM goes beyond ITIL</span>== | ==<span id="yasm-goes-beyond-itil">Where YaSM goes beyond ITIL</span>== | ||
While YaSM is somewhat more streamlined than ITIL in many areas, there are also a number of YaSM processes which go beyond the ITIL | While YaSM is somewhat more streamlined than ITIL in many areas, there are also a number of YaSM processes which go beyond the ITIL recommen­dations. These processes were mostly introduced to improve the alignment of YaSM with other service management standards and frameworks, such as [[YaSM and ISO 20000|ISO 20000]], [[YaSM and COBIT|COBIT]]<sup><small>®</small></sup> [[#COBIT|[3]]], [[YaSM and USMBOK|USMBOK]]™ [[#USMBOK|[4]]] and [[YaSM and CMMI for Services - CMMI-SVC|CMMI-SVC]]<sup><small>®</small></sup> [[#CMMI|[5]]]. | ||
The following table provides an overview of the additional processes and explains their purpose within the YaSM model: | The following table provides an overview of the additional processes and explains their purpose within the YaSM model: | ||
Line 363: | Line 359: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|+style="background:# | |+style="background:#465674;"|<span style="color:#ffffff; font-size: 110%;">YaSM processes which go beyond the ITIL<sup><small>®</small></sup> recommen­dations</span> | ||
|- | |- | ||
!style="background:# | !style="background:#eeeeee; color:#465674; width:25%"|YaSM processes not specified in ITIL<sup><small>®</small></sup> | ||
!style="background:# | !style="background:#eeeeee; color:#465674; width:75%"|Notes | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[[SP1: Set up and maintain the service management system]] | |[[SP1: Set up and maintain the service management system|SP1: Set up and maintain the service mgmt. system]] | ||
| | | | ||
*ITIL focuses on managing services throughout their lifecycle, but is somewhat vague about how the service management processes come into existence. | *ITIL focuses on managing services throughout their lifecycle, but is somewhat vague about how the service management processes come into existence. | ||
Line 380: | Line 376: | ||
*YaSM's project management process is also more versatile, because it can be applied not only when new services are being introduced, but also when other significant initiatives are to be managed (for example an upgrade to the service provider’s technical infrastructure on a bigger scale). | *YaSM's project management process is also more versatile, because it can be applied not only when new services are being introduced, but also when other significant initiatives are to be managed (for example an upgrade to the service provider’s technical infrastructure on a bigger scale). | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[[SP9: Ensure compliance]] | |[[SP9: Ensure compliance|SP9: Ensure com­plianc]] | ||
| | | | ||
*Compliance is becoming increasingly important for many organizations. For this reason, YaSM contains a specific process for ensuring compliance with laws, regulations, industry standards, etc., which highlights the most important compliance management activities and identifies the interfaces with the other YaSM processes. | *Compliance is becoming increasingly important for many organizations. For this reason, YaSM contains a specific process for ensuring compliance with laws, regulations, industry standards, etc., which highlights the most important compliance management activities and identifies the interfaces with the other YaSM processes. | ||
Line 407: | Line 403: | ||
==<span id="video-itil-yasm">Video: ITIL V3 vs. YaSM</span>== | ==<span id="video-itil-yasm">Video: ITIL V3 vs. YaSM</span>== | ||
<html><a href="https://yasm.com/en/videos/yasm-itil-v3" ><img src="https://yasm.com/en/content/videos/yasm-itil-v3/yasm-itil-v3-video.jpg" width=" | <html><figure class="mw-halign-right" typeof="mw:File/Thumb"><a href="https://yasm.com/en/videos/yasm-itil-v3" title="Watch the video: YaSM and ITIL V3 2011"><img srcset="https://yasm.com/en/content/videos/yasm-itil-v3/480px/yasm-itil-v3-video.jpg 480w, https://yasm.com/en/content/videos/yasm-itil-v3/yasm-itil-v3-video.jpg 1280w" sizes="100vw" src="https://yasm.com/en/content/videos/yasm-itil-v3/yasm-itil-v3-video.jpg" decoding="async" width="480" height="270" class="mw-file-element" alt="Video: YaSM and the IT Infrastructure Library ITIL V3 (ITIL 2011)" /></a><figcaption><span style="font-variant:small-caps;"><b><a href="https://yasm.com/en/videos/yasm-itil-v3" title="Start the video: YaSM and the IT Infrastructure Library ITIL V3 (ITIL 2011)">Start the video: YaSM und ITIL V3</a></b></span></figcaption></figure> | ||
<p style="margin-top: 10px;">In this video Stefan Kempter gives you a better understanding of the similarities and differences between YaSM and ITIL® V3 by taking you through a couple of examples. | <p style="margin-top: 10px; word-wrap:normal;">In this video Stefan Kempter gives you a better understanding of the similarities and differences between YaSM and ITIL® V3 by taking you through a couple of examples. | ||
<p>He shows you how we managed to create a streamlined framework that is in line with ITIL® and covers all key aspects of service management best practice.</p> | <p>He shows you how we managed to create a streamlined framework that is in line with ITIL® and covers all key aspects of service management best practice.</p> | ||
<ul style="list-style-image: URL('/wiki/en/img/yasm-wiki/icon-arrow-right.png');padding-left: | <p>Watch the video:</p> | ||
<ul style="list-style-image: URL('/wiki/en/img/yasm-wiki/icon-arrow-right.png');padding-left: 15px;"> | |||
<li>Watch the video: <a href="https://yasm.com/en/videos/yasm-itil-v3" title="Video: YaSM and ITIL V3 2011">YaSM and ITIL V3</a> (9:28 min.)</li></ul> | <li>Watch the video: <a href="https://yasm.com/en/videos/yasm-itil-v3" title="Video: YaSM and ITIL V3 2011">YaSM and ITIL V3</a> (9:28 min.)</li></ul> | ||
<br style="clear:both;"/></html> | <br style="clear:both;"/><p> </p></html> | ||
==Related articles== | ==Related articles== | ||
<html><a href="https://yasm.com/wiki/en/index.php/Alternatives_to_ITIL"><img | <html><figure class="mw-halign-left" typeof="mw:File/Thumb"><a href="https://yasm.com/wiki/en/index.php/Alternatives_to_ITIL" title="YaSM - an alternative to ITIL oder ITIL 4?"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/itil/400px/itil-alternatives.jpg 400w, https://yasm.com/wiki/de/img/yasm-frameworks/itil/480px/itil-alternativen.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/itil/itil-alternatives.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/itil/480px/itil-alternatives.jpg" decoding="async" width="400" height="225" class="mw-file-element" alt="ITIL framework alternative: The YaSM Framework" /></a><figcaption><span style="font-variant:small-caps;">YaSM - an alternative to ITIL® or ITIL 4?</span></figcaption></figure> | ||
< | <p><a href="https://yasm.com/wiki/en/index.php/Alternatives_to_ITIL">YaSM - an alternative to ITIL<sup><small>®</small></sup>?</a></p> | ||
<p | <p>Once in a while I get asked during our webinars if YaSM is an alternative to ITIL. It almost seems quite a few people would like to avoid having to deal with ITIL - but is it a good idea to ignore it? <br /><a href="https://yasm.com/wiki/en/index.php/Alternatives_to_ITIL">[ ... Read more ]</a></p> | ||
<p>Once in a while I get asked during our webinars if YaSM is an alternative to ITIL. It almost seems quite a few people would like to avoid having to deal with ITIL - but is it a good idea to ignore it? <a href="https://yasm.com/wiki/en/index.php/Alternatives_to_ITIL">[...]</a></p | |||
<p style="clear:both;"> </p> | <p style="clear:both;"> </p> | ||
<a href="https://yasm.com/wiki/en/index.php/ITIL_Lite_and_YaSM"><img | <figure class="mw-halign-left" typeof="mw:File/Thumb"><a href="https://yasm.com/wiki/en/index.php/ITIL_Lite_and_YaSM" title="Is YaSM 'ITIL lite' or 'lean ITIL'?"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/itil-lite/400px/itil-lite-itil4-light.jpg 400w, https://yasm.com/wiki/en/img/yasm-frameworks/itil-lite/480px/itil-lite-itil4-light.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/itil-lite/itil-lite-itil4-light.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/itil-lite/480px/itil-lite-itil4-light.jpg" decoding="async" width="400" height="225" class="mw-file-element" alt="YaSM: A Lightweight ITIL or ITIL 4?" /></a><figcaption><span style="font-variant:small-caps;">Is YaSM 'ITIL lite' or 'lean ITIL'?</span></figcaption></figure> | ||
< | |||
<p | <p><a href="https://yasm.com/wiki/en/index.php/ITIL_Lite_and_YaSM">Is YaSM 'ITIL lite' or 'lean ITIL'?</a></p> | ||
<p>YaSM is definitely lighter than ITIL (actually we decided to create YaSM because many of our customers looked for something lighter). But we don't want YaSM to be confused with what is often called "ITIL lite" or "lean ITIL" because we think the existing approaches are often flawed: <a href="https://yasm.com/wiki/en/index.php/ITIL_Lite_and_YaSM">[...]</a></p></ | <p>YaSM is definitely lighter than ITIL (actually we decided to create YaSM because many of our customers looked for something lighter). But we don't want YaSM to be confused with what is often called "ITIL lite" or "lean ITIL" because we think the existing approaches are often flawed: <br /><a href="https://yasm.com/wiki/en/index.php/ITIL_Lite_and_YaSM">[ ... Read more ]</a></p></html> | ||
<p style="clear:both;"> </p> | <p style="clear:both;"> </p> | ||
==References== | ==References== | ||
Line 446: | Line 441: | ||
== Notes == | == Notes == | ||
[1] <span id="ITIL">ITIL<sup><small>®</small></sup> is a registered trade mark of AXELOS Limited. - IT Infrastructure Library<sup><small>®</small></sup> is a registered trade mark of AXELOS Limited.</span> The official ITIL site by AXELOS: [https://www.axelos.com/ | [1] <span id="ITIL">ITIL<sup><small>®</small></sup> is a registered trade mark of AXELOS Limited. - IT Infrastructure Library<sup><small>®</small></sup> is a registered trade mark of AXELOS Limited.</span> The official ITIL site by AXELOS: [https://www.axelos.com/certifications/itil-service-management axelos.com/certifications/itil-service-management]<br /> | ||
[2] <span id="ISO20000">ISO 20000 refers to the service management processes - and other elements like service management policies and plans - as the "service management system (SMS)".</span><br /> | [2] <span id="ISO20000">ISO 20000 refers to the service management processes - and other elements like service management policies and plans - as the "service management system (SMS)".</span><br /> | ||
[3] <span id="COBIT">COBIT<sup><small>®</small></sup> is a registered trademark of ISACA (Information Systems Audit and Control Association).</span><br /> | [3] <span id="COBIT">COBIT<sup><small>®</small></sup> is a registered trademark of ISACA (Information Systems Audit and Control Association).</span><br /> |
Latest revision as of 16:14, 29 July 2024
Comparison: YaSM and the IT Infrastructure Library ITIL® V3 (ITIL 2011)
Part of: YaSM vs. other service management frameworks and standards
YaSM® was designed to be well aligned with the IT Infrastructure Library ITIL® [1] so that users familiar with ITIL will instantly recognize the common principles.
- This page provides a detailed account of how the YaSM service management model relates to the previous version of ITIL V3 (ITIL 2011).
- There is another page with a detailed mapping between YaSM and the latest edition of ITIL 4.
Notes:
- YaSM is an independent process model and is not officially endorsed by the owners of ITIL.
- All ITIL processes in the following tables are linked to IT Process Map's "ITIL® Wiki", where you can find the relevant descriptions of the ITIL processes.
YaSM vs. ITIL Service Strategy
ITIL® V3 processes | Related YaSM processes | Comparison: YaSM and ITIL V3 (ITIL 2011) |
---|---|---|
1.1 Strategy management for IT services |
| |
1.2 Service portfolio management |
| |
1.3 Financial management for IT services |
| |
1.4 Demand management |
|
|
1.5 Business relationship management |
|
References: [Cabinet Office, 2011a] and [IT Process Wiki - ITIL Service Strategy]
YaSM vs. ITIL Service Design
ITIL® V3 processes | Related YaSM processes | Comparison: YaSM and ITIL V3 (ITIL 2011) |
---|---|---|
2.1 Design coordination |
| |
2.2 Service catalogue management |
| |
2.3 Service level management |
| |
2.4 Availability management |
| |
2.5 Capacity management |
| |
2.6 IT service continuity management (ITSCM) |
| |
2.7 Information security management |
| |
2.8 Supplier management |
|
References: [Cabinet Office, 2011b] and [IT Process Wiki - ITIL Service Design]
YaSM vs. ITIL Service Transition
ITIL® V3 processes | Related YaSM processes | Comparison: YaSM and ITIL V3 (ITIL 2011) |
---|---|---|
3.1 Transition planning and support |
| |
3.2 Change management |
| |
3.3 Service asset and configuration management |
| |
3.4 Release and deployment management |
| |
3.5 Service validation and testing |
| |
3.6 Change evaluation |
| |
3.7 Knowledge management |
|
|
References: [Cabinet Office, 2011c] and [IT Process Wiki - ITIL Service Transition]
YaSM vs. ITIL Service Operation
ITIL® V3 processes | Related YaSM processes | Comparison: YaSM and ITIL V3 (ITIL 2011) |
---|---|---|
4.1 Event management |
| |
4.2 Incident management |
| |
4.3 Request fulfillment |
| |
4.4 Problem management |
| |
4.5 Access management |
|
References: [Cabinet Office, 2011d] and IT Process Wiki - ITIL Service Operation]
YaSM vs. ITIL Continual Service Improvement
ITIL® V3 processes | Related YaSM processes | Comparison: YaSM and ITIL V3 (ITIL 2011) |
---|---|---|
5.1 The seven-step improvement process |
|
References: [Cabinet Office, 2011e] and [IT Process Wiki - ITIL CSI - Continual Service Improvement]
Where YaSM goes beyond ITIL
While YaSM is somewhat more streamlined than ITIL in many areas, there are also a number of YaSM processes which go beyond the ITIL recommendations. These processes were mostly introduced to improve the alignment of YaSM with other service management standards and frameworks, such as ISO 20000, COBIT® [3], USMBOK™ [4] and CMMI-SVC® [5].
The following table provides an overview of the additional processes and explains their purpose within the YaSM model:
YaSM processes not specified in ITIL® | Notes |
---|---|
SP1: Set up and maintain the service mgmt. system |
|
SP6: Manage projects |
|
SP9: Ensure complianc |
|
SP10: Manage human resources |
|
ITIL functions and YaSM
Apart from a set of processes ITIL also describes a number of "functions". For instance, incident management is introduced as a process and facilities management as a function.
By definition, a function is an organizational entity, often characterized by a special area of knowledge or experience. Examples would be the human resources department or a team of experts operating a certain part of the technical infrastructure. Processes, in contrast, are clusters of activities which produce a defined outcome, like the incident resolution process. Several functions may play their part in a process (the team of technical experts may have to perform some activities within the incident resolution process).
Much confusion stems from the fact that in the real world there are often functions and processes with identical names: For example, the human resources management team (a "function") will perform a set of HR-related activities, which as a whole are called the human resources process.
In this context, YaSM consists of a set of processes and does not specifically relate to functions or organizational structures.
Roles are the only type of organizational information described in the YaSM model: For example, the role of 1st level support figures in the incident resolution process, because 1st level support needs to perform a number of activities in this process. This notwithstanding, 1st level support agents will typically belong to an organizational unit or function, such as a support team headed by a support manager.
Video: ITIL V3 vs. YaSM
In this video Stefan Kempter gives you a better understanding of the similarities and differences between YaSM and ITIL® V3 by taking you through a couple of examples.
He shows you how we managed to create a streamlined framework that is in line with ITIL® and covers all key aspects of service management best practice.
Watch the video:
- Watch the video: YaSM and ITIL V3 (9:28 min.)
Related articles
YaSM - an alternative to ITIL®?
Once in a while I get asked during our webinars if YaSM is an alternative to ITIL. It almost seems quite a few people would like to avoid having to deal with ITIL - but is it a good idea to ignore it?
[ ... Read more ]
Is YaSM 'ITIL lite' or 'lean ITIL'?
YaSM is definitely lighter than ITIL (actually we decided to create YaSM because many of our customers looked for something lighter). But we don't want YaSM to be confused with what is often called "ITIL lite" or "lean ITIL" because we think the existing approaches are often flawed:
[ ... Read more ]
References
- [Cabinet Office, 2011a]. -- The Cabinet Office: ITIL® Service Strategy (2011 Edition). - The Stationery Office; London, UK, July 2011.
- [Cabinet Office, 2011b]. -- The Cabinet Office: ITIL® Service Design (2011 Edition). - The Stationery Office; London, UK, July 2011.
- [Cabinet Office, 2011c]. -- The Cabinet Office: ITIL® Service Transition (2011 Edition). - The Stationery Office; London, UK, July 2011.
- [Cabinet Office, 2011d]. -- The Cabinet Office: ITIL® Service Operation (2011 Edition). - The Stationery Office; London, UK, July 2011.
- [Cabinet Office, 2011e]. -- The Cabinet Office: ITIL® Continual Service Improvement (2011 Edition). - The Stationery Office; London, UK, July 2011.
External links
- [IT Process Wiki]. -- S. Kempter & Kempter, A.: "IT Process Wiki. -- The Wiki about the IT Infrastructure Library ITIL® (ITIL 4, ITIL V3 & V2), ISO 20000 and IT Service Management (ITSM). - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL Service Strategy]. -- S. Kempter: IT Process Wiki, "ITIL Service Strategy. - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL Service Design]. -- S. Kempter: IT Process Wiki, "ITIL Service Design. - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL Service Transition]. -- S. Kempter: IT Process Wiki, "ITIL Service Transition. - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL Service Operation]. -- S. Kempter: IT Process Wiki, "ITIL Service Operation. - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL CSI]. -- S. Kempter: IT Process Wiki, "ITIL CSI - Continual Service Improvement. - IT Process Maps; Lindau (Bodensee), Germany.
Notes
[1] ITIL® is a registered trade mark of AXELOS Limited. - IT Infrastructure Library® is a registered trade mark of AXELOS Limited. The official ITIL site by AXELOS: axelos.com/certifications/itil-service-management
[2] ISO 20000 refers to the service management processes - and other elements like service management policies and plans - as the "service management system (SMS)".
[3] COBIT® is a registered trademark of ISACA (Information Systems Audit and Control Association).
[4] USMBOK™ is a Registered Trade Mark of Virtual Knowledge Solutions International Incorporated (VKSII).
[5] CMMI® and Capability Maturity Model® are registered trademarks of Carnegie Mellon University.
Is based on: The YaSM Process Map - Document: "YaSM and ITIL® V3 (ITIL 2011)".
By: Andrea Kempter and Stefan Kempter , IT Process Maps.
Service Strategy › Service Design › Service Transition › Service Operation › Video: ITIL vs. YaSM