ITIL Service Design: Difference between revisions
m (Andrea moved page ITIL V3 Service Design to ITIL Service Design: More generic name of the page.) |
No edit summary |
||
Line 1: | Line 1: | ||
< | <itpmch><title>ITIL Service Design | IT Process Wiki</title> | ||
<meta name="keywords" content="itil service design, service design itil, itil v3 service design, service design processes" /> | |||
<meta name="description" content="ITIL Service Design: Definition - Processes - Additional information on Service Design: ITIL Roles, Checklists, KPIs..." /> | |||
</itpmch> | |||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-de-es.jpg|DE - ES - Service Design|100px | Image:ITIL-Wiki-de-es.jpg|DE - ES - Service Design|100px | ||
rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/ | rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Design diese Seite auf Deutsch] | ||
rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/ITIL_Dise%C3%B1o_del_Servicio esta página en español] | rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/ITIL_Dise%C3%B1o_del_Servicio esta página en español] | ||
desc none | desc none | ||
Line 8: | Line 11: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
== | <html><div itemscope="itemscope" itemtype="https://schema.org/WebPage"><!-- define schema.org/WebPage --><p></html> | ||
<p> </p> | |||
''' | '''<span id="ITIL_Service_Design_definition">Objective:</span>''' <html><span itemprop="description">The objective of <i><span itemprop="name Headline">ITIL <span itemprop="alternativeHeadline">Service Design</span></span></i> is to design new IT services. The scope of Service Design includes the design of new services, as well as changes and improvements to existing ones.</span></p> | ||
<p><b>Part of</b>: <a itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_2011" title="ITIL Processes">IT Service Management | ITIL 2011 processes</a></html> | |||
<p> </p> | <p> </p> | ||
== Processes: ITIL Service Design == | __TOC__ | ||
==Processes: ITIL Service Design== | |||
<imagemap> | <imagemap> | ||
Image:overview_service_design_itilv3_thumb.jpg|| | Image:overview_service_design_itilv3_thumb.jpg||right|[[#Processes:_ITIL_Service_Design|ITIL Service Design]] - Click on a process for more details|450px|thumb|alt=ITIL Service Design | ||
rect 184 71 269 132 [[Service Catalogue Management|Service Catalogue Management - Service Design]] | rect 184 71 269 132 [[Service Catalogue Management|Service Catalogue Management - Service Design]] | ||
rect 184 158 268 217 [[Risk Management|Risk Management - Service Design]] | rect 184 158 268 217 [[Risk Management|Risk Management - Service Design]] | ||
Line 33: | Line 39: | ||
</imagemap> | </imagemap> | ||
Service Design identifies service requirements and devises new service offerings as well as changes and improvements to existing ones. | |||
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | |||
<meta itemprop="itemListOrder" content="Ascending" /> | |||
<p><span itemprop="name" content="Service Design main processes:">As per ITIL 2011, the following <strong>main processes</strong> are part of the ITIL stage <strong class="selflink">Service Design</strong>:</span> | |||
</p> | |||
<p> </p> | |||
<dl><dt><a href="/index.php/ITIL_Design_Coordination" title="ITIL Design Coordination" itemprop="itemListElement">Design Coordination</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/Service_Catalogue_Management" title="Service Catalogue Management" itemprop="itemListElement">Service Catalogue Management</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/Service_Level_Management" title="Service Level Management" itemprop="itemListElement">Service Level Management</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/Risk_Management" title="Risk Management" itemprop="itemListElement">Risk Management</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/Capacity_Management" title="Capacity Management" itemprop="itemListElement">Capacity Management</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/Availability_Management" title="Availability Management" itemprop="itemListElement">Availability Management</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/IT_Service_Continuity_Management" title="IT Service Continuity Management" itemprop="itemListElement">IT Service Continuity Management</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/IT_Security_Management" title="IT Security Management" itemprop="itemListElement">Information Security Management</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/Compliance_Management" title="Compliance Management" itemprop="itemListElement">Compliance Management</a> | |||
</dt><dd itemprop="description">Process Objective: To ensure IT services, processes and systems comply with enterprise policies and legal requirements. | |||
</dd></dl> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/IT_Architecture_Management" title="IT Architecture Management" itemprop="itemListElement">Architecture Management</a> | |||
</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> | |||
<p><br /> | |||
</p> | |||
<dl><dt><a href="/index.php/Supplier_Management" title="Supplier Management" itemprop="itemListElement">Supplier Management</a> | |||
</dt><dd itemprop="description">Process Objective: To ensure that all contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments. | |||
</dd></dl> | |||
</div><!-- end of schema.org/ItemList --><p></html> | |||
<p> </p> | <p> </p> | ||
== | ==<span id="Additional_Information_on_Service_Design">KPIs | Templates | Roles</span>== | ||
* [[ITIL KPIs Service Design|KPIs for Service Design]] | * [[ITIL KPIs Service Design|KPIs for Service Design]] | ||
* [[ITIL-Checklists#ITIL Service Design Templates| | * [[ITIL-Checklists#ITIL Service Design Templates|Service Design templates and checklists]] | ||
* [[ITIL Roles#ITIL roles - Service Design|ITIL | * [[ITIL Roles#ITIL roles - Service Design|ITIL roles within Service Design]] | ||
<p> </p> | <p> </p> | ||
== Downloads | ==Downloads== | ||
{| | {| | ||
| | |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" | | ||
[[Image:Itil-service-design.jpg|thumb|175px|left|none|alt=Service Design ITIL|The ITIL discipline Service Design at a glance]] | [[Image:Itil-service-design.jpg|thumb|175px|left|none|alt=Service Design ITIL|The ITIL discipline Service Design at a glance]] | ||
|- | |- | ||
|} | |} | ||
< | <p> </p> | ||
==[ Infobox ]== | |||
<html><table class="wikitable"> | |||
<tr> | |||
<td>Link to this page:</td> | |||
<td><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design">https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design</a></td> | |||
</tr> | |||
<tr> | |||
<td>Languages:</td> | |||
<td><span itemprop="inLanguage" content="en">English</span> | <span><a itemprop="citation" class="external text" href="https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Design" title="ITIL Service Design">Deutsch</a></span> | <span><a itemprop="citation" class="external text" href="https://wiki.es.it-processmaps.com/index.php/ITIL_Dise%C3%B1o_del_Servicio" title="Diseño del Servicio">español</a></span></td> | |||
</tr> | |||
<tr> | |||
<td>Image:</td> | |||
<td style="vertical-align:top"><a itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/9/9b/Overview_service_design_itilv3_thumb.jpg" title="ITIL Service Design">ITIL 2011 Service Design processes (.JPG)</a></td> | |||
</tr> | |||
<tr> | |||
<td>Author:</td> | |||
<td><span itemprop="author">Stefan Kempter</span>, <span itemprop="creator copyrightHolder publisher">IT Process Maps</span> <a rel="author" href="https://plus.google.com/111925560448291102517"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a></td> | |||
</tr> | |||
</table> | |||
< | <p><small> | ||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination" itemprop="url"><span itemprop="title">Design Coordination</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management" itemprop="url"><span itemprop="title">Service Catalogue Mgmt.</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Service_Level_Management" itemprop="url"><span itemprop="title">SLM</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Risk_Management" itemprop="url"><span itemprop="title">Risk Mgmt.</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Capacity_Management" itemprop="url"><span itemprop="title">Capacity Mgmt.</span></a> › [...] › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Supplier_Management" itemprop="url"><span itemprop="title">Supplier Mgmt.</span></a> | |||
</span> | |||
</small></p> | |||
</div><!-- end of schema.org/WebPage --><p></html> | |||
<!-- 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 V3]][[Category:ITIL 2011]][[Category:ITIL stage]][[Category:ITIL process|2]][[Category:Service Design|!]] | ||
<!-- --- --> | <!-- --- --> |
Revision as of 14:28, 11 December 2013
Objective: The objective of ITIL Service Design is to design new IT services. The scope of Service Design includes the design of new services, as well as changes and improvements to existing ones.
Part of: IT Service Management | ITIL 2011 processes
Processes: ITIL Service Design
Service Design identifies service requirements and devises new service offerings as well as changes and improvements to existing ones.
As per ITIL 2011, the following main processes are part of the ITIL stage Service Design:
- Design Coordination
- 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.
- Service Catalogue Management
- 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.
- Service Level Management
- 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.
- Risk Management
- 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.
- Capacity Management
- 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.
- Availability Management
- 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.
- IT Service Continuity Management
- 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.
- Information Security 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.
- Compliance Management
- Process Objective: To ensure IT services, processes and systems comply with enterprise policies and legal requirements.
- Architecture Management
- Process Objective: To define a blueprint for the future development of the technological landscape, taking into account the service strategy and newly available technologies.
- Supplier Management
- Process Objective: To ensure that all contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.
KPIs | Templates | Roles
Downloads
Use the following links to open the process overview of Service Design showing the most important interfaces: |
[ Infobox ]
Link to this page: | https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design |
Languages: | English | Deutsch | español |
Image: | ITIL 2011 Service Design processes (.JPG) |
Author: | Stefan Kempter, IT Process Maps |
Design Coordination › Service Catalogue Mgmt. › SLM › Risk Mgmt. › Capacity Mgmt. › [...] › Supplier Mgmt.