ITIL Service Design: Difference between revisions

From IT Process Wiki
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 13: Line 13:
<meta property="og:image:width" content="558" />
<meta property="og:image:width" content="558" />
<meta property="og:image:height" content="931" />
<meta property="og:image:height" content="931" />
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@itprocessmaps">
<meta name="twitter:creator" content="@itprocessmaps">
<meta name="twitter:title" content="ITIL Service Design | IT Process Wiki">
<meta name="twitter:description" content="The scope of the Service Design lifecycle stage includes the design of new services, as well as changes and improvements to existing ones.">
<meta name="twitter:image" content="https://wiki.en.it-processmaps.com/images/9/9b/Overview_service_design_itilv3_thumb.jpg">
<meta name="twitter:image:alt" content="Overview of the processes in ITIL Service Design: Design Coordination, Service Catalogue Management (SCM), Service Level Management (SLM), Risk Management, Capacity Management, Availability Management, IT Service Continuity Management, Information Security Management, Compliance Management, Architecture Management and Supplier Management.">
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
</itpmch>
</itpmch>
<imagemap>
<imagemap>
Image:ITIL-Wiki-share.jpg|right|share this page|141px
Image:ITIL-Wiki-de-es.jpg|right|DE - ES - Service Design|163px
rect 55 0 99 36 [https://www.linkedin.com/shareArticle?url=https%3A%2F%2Fwiki.en.it-processmaps.com%2Findex.php%2FITIL_Service_Design&hl=en_US&source=IT%20Process%20Wiki share this page on LinkedIn]
rect 97 0 141 36 [https://twitter.com/intent/tweet?url=https%3A%2F%2Fwiki.en.it-processmaps.com%2Findex.php%2FITIL_Service_Design&text=%23ITILwiki%20%7C%20ITIL%20Service%20Design%20-%20Process%20description%0A%E2%96%BA&lang=en&via=itprocessmaps share this page on Twitter]
desc none
</imagemap>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|DE - ES - Service Design|163px
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Design diese Seite auf Deutsch]
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Design diese Seite auf Deutsch]
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Dise%C3%B1o_del_Servicio esta página en español]
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Dise%C3%B1o_del_Servicio esta página en español]
Line 47: Line 34:
Service Design identifies service requirements and devises new service offerings as well as changes and improvements to existing ones.
Service Design identifies service requirements and devises new service offerings as well as changes and improvements to existing ones.


<imagemap>
[[Image:Overview_service_design_itilv3_thumb.jpg|right|thumb|450px|alt=ITIL Service Design|link=https://wiki.en.it-processmaps.com/index.php/File:Overview_service_design_itilv3_thumb.jpg|Fig. 1: [[#Processes:_ITIL_Service_Design|ITIL Service Design]]]]
Image:overview_service_design_itilv3_thumb.jpg||right|Fig. 1: [[#Processes:_ITIL_Service_Design|ITIL Service Design]]|450px|thumb|alt=ITIL Service Design
rect 230 91 332 162 [[Service Catalogue Management|Service Catalogue Management - Service Design]]
rect 230 198 332 270 [[Risk Management|Risk Management - Service Design]]
rect 60 311 159 377 [[Compliance Management|Compliance Management - Service Design]]
rect 60 384 158 453 [[Service Level Management|Service Level Management - Service Design]]
rect 218 385 318 456 [[ITIL Design Coordination|Design Coordination - Service Design]]
rect 356 383 458 454 [[Supplier Management|Supplier Management - Service Design]]
rect 356 462 458 529 [[Capacity Management|Capacity Management - Service Design]]
rect 356 536 458 608 [[Availability Management|Availability Management - Service Design]]
rect 356 614 458 683 [[IT Service Continuity Management|IT Service Continuity Management (ITSCM) - Service Design]]
rect 356 691 458 760 [[IT Security Management|Information Security Management - Service Design]]
rect 230 823 332 891 [[IT Architecture Management|Architecture Management - Service Design]]
desc bottom-left
</imagemap>


<html><div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design#Processes:_ITIL_Service_Design" itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<html><div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design#Processes:_ITIL_Service_Design" itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
Line 67: Line 40:
<p><span itemprop="name" content="Service Design main processes"><span id="ITIL-Service-Design-Processes">The ITIL service lifecycle stage of <strong class="selflink">Service Design</strong> (<a href="https://wiki.en.it-processmaps.com/images/9/9b/Overview_service_design_itilv3_thumb.jpg" title="ITIL Service Design">see fig. 1</a>) includes the following <strong>main processes</strong></span></span>:
<p><span itemprop="name" content="Service Design main processes"><span id="ITIL-Service-Design-Processes">The ITIL service lifecycle stage of <strong class="selflink">Service Design</strong> (<a href="https://wiki.en.it-processmaps.com/images/9/9b/Overview_service_design_itilv3_thumb.jpg" title="ITIL Service Design">see fig. 1</a>) includes the following <strong>main processes</strong></span></span>:
</p>
</p>
<p>&#160;</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="1" />
<meta itemprop="position" content="1" />
Line 74: Line 45:
</dt><dd itemprop="description">Process Objective: To coordinate all service design activities, processes and resources. Design coordination ensures the consistent and effective design of new or changed IT services, service management information systems, architectures, technology, processes, information and metrics.
</dt><dd itemprop="description">Process Objective: To coordinate all service design activities, processes and resources. Design coordination ensures the consistent and effective design of new or changed IT services, service management information systems, architectures, technology, processes, information and metrics.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="2" />
<meta itemprop="position" content="2" />
Line 82: Line 50:
</dt><dd itemprop="description">Process Objective: To ensure that a Service Catalogue is produced and maintained, containing accurate information on all operational services and those being prepared to be run operationally. Service Catalogue Management provides vital information for all other Service Management processes: Service details, current status and the services' interdependencies.
</dt><dd itemprop="description">Process Objective: To ensure that a Service Catalogue is produced and maintained, containing accurate information on all operational services and those being prepared to be run operationally. Service Catalogue Management provides vital information for all other Service Management processes: Service details, current status and the services' interdependencies.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Service_Level_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Service_Level_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="3" />
<meta itemprop="position" content="3" />
Line 90: Line 55:
</dt><dd itemprop="description">Process Objective: To negotiate Service Level Agreements with the customers and to design services in accordance with the agreed service level targets. Service Level Management is also responsible for ensuring that all Operational Level Agreements and Underpinning Contracts are appropriate, and to monitor and report on service levels.
</dt><dd itemprop="description">Process Objective: To negotiate Service Level Agreements with the customers and to design services in accordance with the agreed service level targets. Service Level Management is also responsible for ensuring that all Operational Level Agreements and Underpinning Contracts are appropriate, and to monitor and report on service levels.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Risk_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Risk_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="4" />
<meta itemprop="position" content="4" />
Line 98: Line 60:
</dt><dd itemprop="description">Process Objective: To identify, assess and control risks. This includes analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.
</dt><dd itemprop="description">Process Objective: To identify, assess and control risks. This includes analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Capacity_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Capacity_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="5" />
<meta itemprop="position" content="5" />
Line 106: Line 65:
</dt><dd itemprop="description">Process Objective: To ensure that the capacity of IT services and the IT infrastructure is able to deliver the agreed service level targets in a cost effective and timely manner. Capacity Management considers all resources required to deliver the IT service, and plans for short, medium and long term business requirements.
</dt><dd itemprop="description">Process Objective: To ensure that the capacity of IT services and the IT infrastructure is able to deliver the agreed service level targets in a cost effective and timely manner. Capacity Management considers all resources required to deliver the IT service, and plans for short, medium and long term business requirements.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Availability_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Availability_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="6" />
<meta itemprop="position" content="6" />
Line 114: Line 70:
</dt><dd itemprop="description">Process Objective: To define, analyze, plan, measure and improve all aspects of the availability of IT services. Availability Management is responsible for ensuring that all IT infrastructure, processes, tools, roles etc. are appropriate for the agreed availability targets.
</dt><dd itemprop="description">Process Objective: To define, analyze, plan, measure and improve all aspects of the availability of IT services. Availability Management is responsible for ensuring that all IT infrastructure, processes, tools, roles etc. are appropriate for the agreed availability targets.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/IT_Service_Continuity_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/IT_Service_Continuity_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="7" />
<meta itemprop="position" content="7" />
Line 122: Line 75:
</dt><dd itemprop="description">Process Objective: To manage risks that could seriously impact IT services. ITSCM ensures that the IT service provider can always provide minimum agreed Service Levels, by reducing the risk from disaster events to an acceptable level and planning for the recovery of IT services. ITSCM should be designed to support Business Continuity Management.
</dt><dd itemprop="description">Process Objective: To manage risks that could seriously impact IT services. ITSCM ensures that the IT service provider can always provide minimum agreed Service Levels, by reducing the risk from disaster events to an acceptable level and planning for the recovery of IT services. ITSCM should be designed to support Business Continuity Management.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/IT_Security_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/IT_Security_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="8" />
<meta itemprop="position" content="8" />
Line 130: Line 80:
</dt><dd itemprop="description">Process Objective: To ensure the confidentiality, integrity and availability of an organization's information, data and IT services. Information Security Management usually forms part of an organizational approach to security management which has a wider scope than the IT Service Provider.
</dt><dd itemprop="description">Process Objective: To ensure the confidentiality, integrity and availability of an organization's information, data and IT services. Information Security Management usually forms part of an organizational approach to security management which has a wider scope than the IT Service Provider.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Compliance_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Compliance_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="9" />
<meta itemprop="position" content="9" />
Line 138: Line 85:
</dt><dd itemprop="description">Process Objective: To ensure IT services, processes and systems comply with enterprise policies and legal requirements.
</dt><dd itemprop="description">Process Objective: To ensure IT services, processes and systems comply with enterprise policies and legal requirements.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/IT_Architecture_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="10" />
<meta itemprop="position" content="10" />
Line 146: Line 90:
</dt><dd itemprop="description">Process Objective: To define a blueprint for the future development of the technological landscape, taking into account the service strategy and newly available technologies.
</dt><dd itemprop="description">Process Objective: To define a blueprint for the future development of the technological landscape, taking into account the service strategy and newly available technologies.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Supplier_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Supplier_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="11" />
<meta itemprop="position" content="11" />
Line 155: Line 96:
</dd></dl></div>
</dd></dl></div>
</div><!-- end of schema.org/ItemList --><p></html>
</div><!-- end of schema.org/ItemList --><p></html>
<p>&nbsp;</p>
 
==ITIL 4 Service Design==
 
The [[#Processes:_ITIL_Service_Design|Service Design processes described here]] ([[Media:Overview_service_design_itilv3_thumb.jpg|fig. 1]]) follow the specifications of ITIL V3, where Service Design is the second stage in the Service Lifecycle.
 
ITIL V4 has moved from the Service Lifecycle concept to a more holistic approach that includes key concepts, the [[ITIL_4#Four_dimensions_model|Four Dimensions Model]] and the [[ITIL_4#Service_value_system|Service Value System (SVS)]]
 
Instead of processes, [[ITIL_4#ITIL_4_management_practices|ITIL 4 describes 34 'practices']], and many of the 26 processes specified in ITIL V3 can be found in ITIL 4 as practices.
 
ITIL 4 therefore refers to Service Design as a practice and describes Service Design key concepts. In addition, ITIL 4 includes some practices that correspond to ITIL V3 Service Design processes, such as Service Level Management and Service Catalogue Management.
 
The shift from processes to practices means ITIL V4 is no longer prescriptive about processes and gives organizations more freedom to define tailor-made Service Design processes.
 
<html>Since the processes specified in ITIL V3 have not been invalidated with the introduction of ITIL V4, organizations that need to define their Service Design processes can still use the processes specified in ITIL V3 as templates.</p>
 
<p style="border: 8px solid #cef6e3; padding: 0.5em 1em;"><i><u>Note</u>:</i><br /> In our <i>YaSM Service Management Wiki</i> we describe a <a class="external" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes" title="Service management processes">leaner set of 19 service management processes</a> that are more in tune with ITIL 4 and its focus on simplicity and "just enough process".<br /><br /> The YaSM service management model includes a <a class="external" href="https://yasm.com/wiki/en/index.php/LP2:_Design_new_or_changed_services" title="YaSM service design processes">Service Design process</a> that is a good starting point for organizations that wish to adopt ITIL 4.</html>


==<span id="Additional_Information_on_Service_Design">KPIs | Templates | Roles</span>==
==<span id="Additional_Information_on_Service_Design">KPIs | Templates | Roles</span>==
Line 162: Line 118:
* [[ITIL-Checklists#ITIL Service Design Templates|Service Design templates and checklists]]
* [[ITIL-Checklists#ITIL Service Design Templates|Service Design templates and checklists]]
* [[ITIL Roles#ITIL roles - Service Design|ITIL roles within Service Design]]
* [[ITIL Roles#ITIL roles - Service Design|ITIL roles within Service Design]]
<p>&nbsp;</p>


==Downloads==
==Downloads==


{|
[[Image:Itil-service-design.jpg|thumb|320px|right|none|alt=Service Design ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Itil-service-design.jpg|The ITIL discipline Service Design at a glance]]
|style="vertical-align:top" |
Use the following links to open the process overview of Service Design showing the most important interfaces:
Use the following links to open the process overview of Service Design showing the most important interfaces:
* [[Media:Itil-service-design.jpg|ITIL Service Design (.JPG)]]
* [[Media:Itil-service-design.jpg|ITIL Service Design (.JPG)]]
* [https://wiki.en.it-processmaps.com/images/pdf/service-design-itil-v3.pdf ITIL Service Design (.PDF)]''
* [https://wiki.en.it-processmaps.com/images/pdf/service-design-itil-v3.pdf ITIL Service Design (.PDF)]
|style="vertical-align:top" |
<br style="clear:both;"/>
[[Image:Itil-service-design.jpg|thumb|175px|left|none|alt=Service Design ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Itil-service-design.jpg|The ITIL discipline Service Design at a glance]]
|-
|}
 
<p>&nbsp;</p>


==Notes==
==Notes==
Line 188: Line 135:
<p><small>
<p><small>
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design#ITIL_4_Service_Design">
<span itemprop="name">ITIL 4 Service Design</span></a>
<meta itemprop="position" content="1"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination">
<span itemprop="name">Design Coordination</span></a>
<span itemprop="name">Design Coordination</span></a>
<meta itemprop="position" content="1"></span> ›
<meta itemprop="position" content="2"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management">
<span itemprop="name">Service Catalogue Mgmt.</span></a>
<span itemprop="name">Service Catalogue Mgmt.</span></a>
<meta itemprop="position" content="2"></span> ›
<meta itemprop="position" content="3"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Level_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Level_Management">
<span itemprop="name">SLM</span></a>
<span itemprop="name">SLM</span></a>
<meta itemprop="position" content="3"></span> ›
<meta itemprop="position" content="4"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Risk_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Risk_Management">
<span itemprop="name">Risk Mgmt.</span></a>
<span itemprop="name">Risk Mgmt.</span></a>
<meta itemprop="position" content="4"></span> ›
<meta itemprop="position" content="5"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Capacity_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Capacity_Management">
<span itemprop="name">Capacity Mgmt.</span></a>
<span itemprop="name">Capacity Mgmt.</span></a>
<meta itemprop="position" content="5"></span> › [...] ›
<meta itemprop="position" content="6"></span> › [...] ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Supplier_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Supplier_Management">
<span itemprop="name">Supplier Mgmt.</span></a>
<span itemprop="name">Supplier Mgmt.</span></a>
<meta itemprop="position" content="6" /></span>
<meta itemprop="position" content="7" /></span>
</span>
</span>
</small></p>
</small></p>
Line 230: Line 181:
   <meta itemprop="keywords" content="Service Design" />
   <meta itemprop="keywords" content="Service Design" />
   </span>
   </span>
  <meta itemprop="mentions" content="https://yasm.com/wiki/en/index.php/LP2:_Design_new_or_changed_services" />
   <meta itemprop="inLanguage" content="en" />
   <meta itemprop="inLanguage" content="en" />
   <link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Design" />
   <link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Design" />
Line 240: Line 192:


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL stage]][[Category:ITIL process|2]][[Category:Service Design|!]]
[[Category:ITIL 4]][[Category:ITIL 2011]][[Category:ITIL V3]][[Category:ITIL practice]][[Category:ITIL stage]][[Category:ITIL process|2]][[Category:Service Design|!]]
<!-- --- -->
<!-- --- -->

Latest revision as of 11:47, 31 December 2023

DE - ES - Service Designdiese Seite auf Deutschesta página en español
DE - ES - Service Design


Objective: The objective of ITIL Service Design is to design new IT services. The scope of the Service Design lifecycle stage includes the design of new services, as well as changes and improvements to existing ones.

Part of: IT Service Management | ITIL processes

 

Processes: ITIL Service Design

Service Design identifies service requirements and devises new service offerings as well as changes and improvements to existing ones.

ITIL Service Design
Fig. 1: ITIL Service Design

The ITIL service lifecycle stage of Service Design (see fig. 1) includes the following main processes:

Process Objective: To coordinate all service design activities, processes and resources. Design coordination ensures the consistent and effective design of new or changed IT services, service management information systems, architectures, technology, processes, information and metrics.
Process Objective: To ensure that a Service Catalogue is produced and maintained, containing accurate information on all operational services and those being prepared to be run operationally. Service Catalogue Management provides vital information for all other Service Management processes: Service details, current status and the services' interdependencies.
Process Objective: To negotiate Service Level Agreements with the customers and to design services in accordance with the agreed service level targets. Service Level Management is also responsible for ensuring that all Operational Level Agreements and Underpinning Contracts are appropriate, and to monitor and report on service levels.
Process Objective: To identify, assess and control risks. This includes analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.
Process Objective: To ensure that the capacity of IT services and the IT infrastructure is able to deliver the agreed service level targets in a cost effective and timely manner. Capacity Management considers all resources required to deliver the IT service, and plans for short, medium and long term business requirements.
Process Objective: To define, analyze, plan, measure and improve all aspects of the availability of IT services. Availability Management is responsible for ensuring that all IT infrastructure, processes, tools, roles etc. are appropriate for the agreed availability targets.
Process Objective: To manage risks that could seriously impact IT services. ITSCM ensures that the IT service provider can always provide minimum agreed Service Levels, by reducing the risk from disaster events to an acceptable level and planning for the recovery of IT services. ITSCM should be designed to support Business Continuity Management.
Process Objective: To ensure the confidentiality, integrity and availability of an organization's information, data and IT services. Information Security Management usually forms part of an organizational approach to security management which has a wider scope than the IT Service Provider.
Process Objective: To ensure IT services, processes and systems comply with enterprise policies and legal requirements.
Process Objective: To define a blueprint for the future development of the technological landscape, taking into account the service strategy and newly available technologies.
Process Objective: To ensure that all contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.

ITIL 4 Service Design

The Service Design processes described here (fig. 1) follow the specifications of ITIL V3, where Service Design is the second stage in the Service Lifecycle.

ITIL V4 has moved from the Service Lifecycle concept to a more holistic approach that includes key concepts, the Four Dimensions Model and the Service Value System (SVS)

Instead of processes, ITIL 4 describes 34 'practices', and many of the 26 processes specified in ITIL V3 can be found in ITIL 4 as practices.

ITIL 4 therefore refers to Service Design as a practice and describes Service Design key concepts. In addition, ITIL 4 includes some practices that correspond to ITIL V3 Service Design processes, such as Service Level Management and Service Catalogue Management.

The shift from processes to practices means ITIL V4 is no longer prescriptive about processes and gives organizations more freedom to define tailor-made Service Design processes.

Since the processes specified in ITIL V3 have not been invalidated with the introduction of ITIL V4, organizations that need to define their Service Design processes can still use the processes specified in ITIL V3 as templates.

Note:
In our YaSM Service Management Wiki we describe a leaner set of 19 service management processes that are more in tune with ITIL 4 and its focus on simplicity and "just enough process".

The YaSM service management model includes a Service Design process that is a good starting point for organizations that wish to adopt ITIL 4.

KPIs | Templates | Roles

Downloads

Service Design ITIL
The ITIL discipline Service Design at a glance

Use the following links to open the process overview of Service Design showing the most important interfaces:


Notes

By:  Stefan Kempter , IT Process Maps.

 

ITIL 4 Service Design  › Design Coordination  › Service Catalogue Mgmt.  › SLM  › Risk Mgmt.  › Capacity Mgmt.  › [...] › Supplier Mgmt.

Retrieved from "https://wiki.en.it-processmaps.com/index.php?title=ITIL_Service_Design&oldid=9587"