ITIL Service Design: Difference between revisions
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
<p> </p> | <p> </p> | ||
'''<span id="ITIL_Service_Design_definition">Objective:</span>''' <html><span itemprop="description">The objective of <i | '''<span id="ITIL_Service_Design_definition">Objective:</span>''' <html><span id="md-webpage-description" itemprop="description">The objective of <i>ITIL Service Design</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 | <p><b>Part of</b>: <a 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> | ||
Line 52: | Line 51: | ||
</p> | </p> | ||
<dl><dt><a href="/index.php/Service_Catalogue_Management" title="Service Catalogue Management" itemprop="itemListElement">Service Catalogue Management</a> | <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 | </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> | </dd></dl> | ||
<p><br /> | <p><br /> | ||
</p> | </p> | ||
<dl><dt><a href="/index.php/Service_Level_Management" title="Service Level Management" itemprop="itemListElement">Service Level Management</a> | <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 | </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> | </dd></dl> | ||
<p><br /> | <p><br /> | ||
Line 72: | Line 71: | ||
</p> | </p> | ||
<dl><dt><a href="/index.php/Availability_Management" title="Availability Management" itemprop="itemListElement">Availability Management</a> | <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 | </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> | </dd></dl> | ||
<p><br /> | <p><br /> | ||
</p> | </p> | ||
<dl><dt><a href="/index.php/IT_Service_Continuity_Management" title="IT Service Continuity Management" itemprop="itemListElement">IT Service Continuity Management</a> | <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 | </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> | </dd></dl> | ||
<p><br /> | <p><br /> | ||
Line 119: | Line 118: | ||
* [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" | | |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|link=https://wiki.en.it-processmaps.com/index.php/File:Itil-service-design.jpg|The ITIL discipline Service Design at a glance]] | ||
|- | |- | ||
|} | |} | ||
Line 125: | Line 124: | ||
<p> </p> | <p> </p> | ||
== | ==Notes== | ||
<html> | <html>By:  Stefan Kempter <a rel="author" href="https://plus.google.com/111925560448291102517/about"><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>, IT Process Maps.</p> | ||
<p> </p> | |||
< | |||
</ | |||
<p><small> | <p><small> | ||
Line 160: | Line 144: | ||
</span> | </span> | ||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | <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> › | <a href="https://wiki.en.it-processmaps.com/index.php/Capacity_Management" itemprop="url"><span itemprop="title">Capacity Mgmt.</span></a> › [...] › | ||
</span> | </span> | ||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | <span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | ||
Line 166: | Line 150: | ||
</span> | </span> | ||
</small></p> | </small></p> | ||
</ | |||
<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description"> | |||
<meta itemprop="name" content="ITIL Service Design" /> | |||
<meta itemprop="alternativeHeadline" content="Service Design" /> | |||
<link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" /> | |||
<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.es.it-processmaps.com/index.php/ITIL_Dise%C3%B1o_del_Servicio" /> | |||
<meta itemprop="Headline" content="ITIL Service Design" /> | |||
<link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_2011" /> | |||
<link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/9/9b/Overview_service_design_itilv3_thumb.jpg" /> | |||
<link itemprop="author" href="https://plus.google.com/111925560448291102517/about" /> | |||
<meta itemprop="author" content="Stefan Kempter" /> | |||
<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | |||
</span><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 11:43, 15 May 2016
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: |
Notes
By: Stefan Kempter , IT Process Maps.
Design Coordination › Service Catalogue Mgmt. › SLM › Risk Mgmt. › Capacity Mgmt. › [...] › Supplier Mgmt.