ITIL Service Design: Difference between revisions
From IT Process Wiki
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<itpmch><title>ITIL Service Design | IT Process Wiki</title> | <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="keywords" content="itil service design, service design itil, itil v3 service design, service design processes" /> | ||
<meta name="description" content="ITIL Service Design | <meta name="description" content="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." /> | ||
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" /> | <meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" /> | ||
<meta property="og:title" content="ITIL Service Design | IT Process Wiki" /> | <meta property="og:title" content="ITIL Service Design | IT Process Wiki" /> | ||
| Line 142: | Line 142: | ||
==Notes== | ==Notes== | ||
<html>By:  Stefan Kempter <a rel="author" href="https:// | <html>By:  Stefan Kempter <a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | ||
<p> </p> | <p> </p> | ||
<p><small> | <p><small> | ||
<span itemscope="itemscope | <span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
</span> | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination"> | ||
<span | <span itemprop="name">Design Coordination</span></a> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management | <meta itemprop="position" content="1"></span> › | ||
</span> | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<span | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management"> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/Service_Level_Management | <span itemprop="name">Service Catalogue Mgmt.</span></a> | ||
</span> | <meta itemprop="position" content="2"></span> › | ||
<span | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<a href="https://wiki.en.it-processmaps.com/index.php/Risk_Management | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Level_Management"> | ||
</span> | <span itemprop="name">SLM</span></a> | ||
<span | <meta itemprop="position" content="3"></span> › | ||
<a href="https://wiki.en.it-processmaps.com/index.php/Capacity_Management | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
< | <a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Risk_Management"> | ||
<span itemprop="name">Risk Mgmt.</span></a> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/Supplier_Management | <meta itemprop="position" content="4"></span> › | ||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Capacity_Management"> | |||
<span itemprop="name">Capacity Mgmt.</span></a> | |||
<meta itemprop="position" content="5"></span> › [...] › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Supplier_Management"> | |||
<span itemprop="name">Supplier Mgmt.</span></a> | |||
<meta itemprop="position" content="6" /></span> | |||
</span> | </span> | ||
</small></p> | </small></p> | ||
| Line 177: | Line 185: | ||
<link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_2011" /> | <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="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/9/9b/Overview_service_design_itilv3_thumb.jpg" /> | ||
<link itemprop="author" href="https:// | <link itemprop="author" href="https://www.linkedin.com/in/stefankempter" /> | ||
<meta itemprop="author" content="Stefan Kempter" /> | <meta itemprop="author" content="Stefan Kempter" /> | ||
<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" /> | ||
Revision as of 12:22, 27 February 2018
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 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.
