ITIL Design Coordination: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
< | <itpmch><title>ITIL Design Coordination | IT Process Wiki</title> | ||
<meta name="keywords" content="itil design coordination, design coordination itil" /> | |||
<meta name="description" content="Design Coordination: ITIL process definition - Sub-processes - Terms - Additional information on ITIL Design Coordination." /> | |||
</itpmch> | |||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-deutsch.jpg|right|Design Coordination | Image:ITIL-Wiki-deutsch.jpg|right|Design Coordination | ||
Line 7: | Line 10: | ||
<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> | <p> </p> | ||
'''<span id="Overview">Objective:</span>''' <html><span itemprop="description"><i><span itemprop="name Headline">ITIL <span itemprop="alternativeHeadline">Design Coordination</span></span></i> aims 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.</span></p> | |||
<p><b>Part of</b>: <a itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" title="ITIL Service Design">Service Design</a></html> | |||
''' | |||
'''Process Owner''': [[ITIL Design Coordination#Service Design Manager|Service Design Manager]] | '''Process Owner''': [[ITIL Design Coordination#Service Design Manager|Service Design Manager]] | ||
Line 19: | Line 20: | ||
<p> </p> | <p> </p> | ||
== Process Description == | ==Process Description== | ||
[[Image:Itil-design-coordination.jpg|right|thumb|370px|alt=Design Coordination ITIL|[https://wiki.en.it-processmaps.com/images/pdf/process-overview-design-coordination-itil.pdf ITIL Design Coordination]]] | [[Image:Itil-design-coordination.jpg|right|thumb|370px|alt=Design Coordination ITIL|[https://wiki.en.it-processmaps.com/images/pdf/process-overview-design-coordination-itil.pdf ITIL Design Coordination]]] | ||
Line 30: | Line 31: | ||
<p> </p> | <p> </p> | ||
== Sub-Processes == | ==Sub-Processes== | ||
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | |||
<meta itemprop="itemListOrder" content="Ascending" /> | |||
<p><span itemprop="name" content="Design Coordination sub-processes:">These are the <strong class="selflink">ITIL Design Coordination</strong> sub-processes and their process objectives:</span> | |||
</p> | |||
<p> </p> | |||
<p><b><span id="ITIL_Design_Coordination_Support" itemprop="itemListElement">Design Coordination Support</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To coordinate and develop Service Design resources and capabilities, and to ensure that a consistent approach to designing new or changed services is adopted across all service transition projects. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Design_Coordination_Planning" itemprop="itemListElement">Service Design Planning</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To plan design activities in detail, making sure that <a href="/index.php/ITIL_Design_Coordination#Service_Design_Policy" title="ITIL Design Coordination">all relevant aspects</a> are considered during service design. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="ITIL_Design_Coordination_and_Monitoring" itemprop="itemListElement">Service Design Coordination and Monitoring</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To coordinate the design activities performed by various Service Design processes, and to determine if the new or changed service can be provided economically. This process is also responsible for deciding if the <a href="/index.php/ITIL_Design_Coordination#SDP" title="ITIL Design Coordination">clients' requirements</a> can be fulfilled or must be renegotiated. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Technical_and_Organizational_Service_Design" itemprop="itemListElement">Technical and Organizational Service Design</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To determine how a new service will be provided from an IT perspective. In particular, this means to specify any technical infrastructure to be created, as well as required organizational changes. The resulting <a href="/index.php/ITIL_Design_Coordination#SDP" title="ITIL Design Coordination">Service Design Package</a> contains all relevant information for Service Transition. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Design_Coordination_Review_RFC" itemprop="itemListElement">Service Design Review and RFC Submission</span></b> | |||
</p> | |||
<ul><li itemprop="description">Process Objective: To submit the <a href="/index.php/ITIL_Design_Coordination#SDP" title="ITIL Design Coordination">Service Design Package</a> to a final review and initiate the implementation of the service by submitting a formal <a href="/index.php/Change_Management#ITIL-RFC" title="Change Management">Request for Change</a>. | |||
</li></ul> | |||
</div><!-- end of schema.org/ItemList --><p></html> | |||
<p> </p> | <p> </p> | ||
==Definitions== | |||
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | |||
<meta itemprop="itemListOrder" content="Ascending" /> | |||
<p><span itemprop="name">The following <a href="/index.php/ITIL%20Glossary#ITIL%20Glossary%20A-Z" title="ITIL Glossary">ITIL terms and acronyms</a> (<i>information objects</i>) are used in ITIL Design Coordination to represent process outputs and inputs:</span> | |||
</p> | |||
<p> </p> | |||
<p><b><span id="SDP" itemprop="itemListElement">Service Design Package (SDP)</span></b> | |||
</p> | |||
<ul><li itemprop="description">The Service Design Package builds upon the Service Level Requirements. It further specifies the requirements from the viewpoint of the client and defines how these are actually fulfilled from a technical and organizational point of view <i>(see also: <a href="/index.php/Checklist_Service_Design_Package_SDP" title="Checklist Service Design Package SDP">ITIL Checklist Service Design Package</a>)</i>. | |||
</li></ul> | |||
<p><br /> | |||
</p><p><b><span id="Service_Design_Policy" itemprop="itemListElement">Service Design Policy</span></b> | |||
</p> | |||
<ul><li itemprop="description">The Service Design Policy provides guidance on how to ensure that a consistent approach is applied to all design activities. In particular, the Service Design Policy specifies which projects or Changes are required to undergo the formal Service Design stage, and who needs to be involved in Service Design to ensure that all relevant aspects are considered. | |||
</li></ul> | |||
</div><!-- end of schema.org/ItemList --><p></html> | |||
<p> </p> | <p> </p> | ||
== Checklists == | ==<span id="Checklists">Templates</span>== | ||
<html><ul><li><a itemprop="significantLinks" href="https://wiki.en.it-processmaps.com/index.php/Checklist_Service_Design_Package_SDP" title="Service Design Package SDP">Service Design Package - SDP template</a> | |||
</li></ul><p></html> | |||
<p> </p> | <p> </p> | ||
== Roles | Responsibilities == | ==Roles | Responsibilities== | ||
'''<span id="Service Design Manager">Service Design Manager - Process Owner</span>''' | |||
*The Service Design Manager is responsible for producing quality, secure and resilient designs for new or improved services. This includes producing and maintaining all design documentation. | |||
<p> </p> | <p> </p> | ||
{| border="1" cellpadding="5" cellspacing="0" style="text-align:center;" valign="top" | {| border="1" cellpadding="5" cellspacing="0" style="margin-left: auto; margin-right: auto; text-align:center;" valign="top" | ||
|- | |- | ||
| | |style="vertical-align:top; text-align:center" colspan="6" style="background:#ffffdd;"| '''Responsibility Matrix: ITIL Design Coordination''' | ||
|- | |- | ||
! | !style="background:#ffffee; width: 50%; text-align:center"| ITIL Role | Sub-Process | ||
! style="background:#ffffee;" | [[ITIL Design Coordination#Service Design Manager|Service Design Manager]] | ! style="background:#ffffee;" | [[ITIL Design Coordination#Service Design Manager|Service Design Manager]] | ||
! style="background:#ffffee;" | Project Manager[[ITIL Design Coordination#Team|<small>[3]</small>]] | ! style="background:#ffffee;" | Project Manager[[ITIL Design Coordination#Team|<small>[3]</small>]] | ||
Line 91: | Line 108: | ||
! style="background:#ffffee;" | Other roles involved | ! style="background:#ffffee;" | Other roles involved | ||
|- | |- | ||
| | |style="text-align:left;" |[[#ITIL Design Coordination Support|Design Coordination Support]] | ||
| A[[ITIL Design Coordination#Accountable|<small>[1]</small>]]R[[ITIL Design Coordination#Responsible|<small>[2]</small>]] | | A[[ITIL Design Coordination#Accountable|<small>[1]</small>]]R[[ITIL Design Coordination#Responsible|<small>[2]</small>]] | ||
| | | - | ||
| | | - | ||
| | | - | ||
| | | - | ||
|- | |- | ||
| | |style="text-align:left;" |[[#Design Coordination Planning|Service Design Planning]] | ||
| AR | | AR | ||
| R | | R | ||
| | | - | ||
| | | - | ||
| | | - | ||
|- | |- | ||
| | |style="text-align:left;" |[[#ITIL Design Coordination and Monitoring|Service Design Coordination and Monitoring]] | ||
| A | | A | ||
| | | - | ||
| R | | R | ||
| R | | R | ||
| | | - | ||
|- | |- | ||
| | |style="text-align:left;" |[[#Technical and Organizational Service Design|Technical and Organizational Service Design]] | ||
| A | | A | ||
| | | - | ||
| | | - | ||
| | | - | ||
|R[[#ITIL Design Coordination Group|<small>[4]</small>]] | |R[[#ITIL Design Coordination Group|<small>[4]</small>]] | ||
|- | |- | ||
| | |style="text-align:left;" |[[#Design Coordination Review RFC|Service Design Review and RFC Submission]] | ||
| AR | | AR | ||
| | | - | ||
| | | - | ||
| | | - | ||
| | | - | ||
|- | |- | ||
|} | |} | ||
Line 136: | Line 153: | ||
<span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within Change Evaluation.</span> | <span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within Change Evaluation.</span> | ||
<span id="Team">[3] see [[Roles | <span id="Team">[3] see [[ITIL Roles|→ Role descriptions]]</span> | ||
<span id="ITIL Design Coordination Group">[4] Applications Analyst, Technical Analyst, IT Operations Manager, Process Architect, Process Owner | <span id="ITIL Design Coordination Group">[4] Applications Analyst, Technical Analyst, IT Operations Manager, Process Architect, Process Owner and others, depending on the expertise required (see [[ITIL Roles|→ Role descriptions]])</span> | ||
<p> </p> | <p> </p> | ||
<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_Design_Coordination">https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination</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_Design-Koordinierung" title="Risikomanagement">Deutsch</a></span></td> | |||
</tr> | |||
<tr> | |||
<td>Image:</td> | |||
<td style="vertical-align:top"><a itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/2/20/Itil-design-coordination.jpg" title="Design Coordination">ITIL Design Coordination (.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#Process_Description" itemprop="url"><span itemprop="title">Process Description</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination#Sub-Processes" itemprop="url"><span itemprop="title">Sub-Processes</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination#Definitions" itemprop="url"><span itemprop="title">Definitions</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination#Templates" itemprop="url"><span itemprop="title">SDP Template</span></a> › | |||
</span> | |||
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb"> | |||
<a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination#Roles_.7C_Responsibilities" itemprop="url"><span itemprop="title">Roles</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 process]][[Category:Service | [[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Design|Design Coordination]][[Category:Design Coordination|!]] | ||
<!-- --- --> | <!-- --- --> |
Revision as of 13:22, 25 December 2013
![Design Coordination](/images/f/f8/ITIL-Wiki-deutsch.jpg)
Objective: ITIL Design Coordination aims 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.
Part of: Service Design
Process Owner: Service Design Manager
Process Description
![Design Coordination ITIL](/images/thumb/2/20/Itil-design-coordination.jpg/370px-Itil-design-coordination.jpg)
Design Coordination has been added as a new process, in line with the latest ITIL 2011 guidance. Design Coordination is now responsible for coordinating the design activities carried out by other Service Design processes.
In the previous ITIL version, some of these tasks were carried out as part of Service Level Management, which is why the sub-processes Decomposition of Business Service into Supporting Services, Technical and Organizational Service Design and RFC Compilation and Submission have been moved from Service Level Management to Design Coordination.
The process overview of ITIL Design Coordination is showing the most important interfaces (see Figure 1).
Sub-Processes
These are the ITIL Design Coordination sub-processes and their process objectives:
Design Coordination Support
- Process Objective: To coordinate and develop Service Design resources and capabilities, and to ensure that a consistent approach to designing new or changed services is adopted across all service transition projects.
Service Design Planning
- Process Objective: To plan design activities in detail, making sure that all relevant aspects are considered during service design.
Service Design Coordination and Monitoring
- Process Objective: To coordinate the design activities performed by various Service Design processes, and to determine if the new or changed service can be provided economically. This process is also responsible for deciding if the clients' requirements can be fulfilled or must be renegotiated.
Technical and Organizational Service Design
- Process Objective: To determine how a new service will be provided from an IT perspective. In particular, this means to specify any technical infrastructure to be created, as well as required organizational changes. The resulting Service Design Package contains all relevant information for Service Transition.
Service Design Review and RFC Submission
- Process Objective: To submit the Service Design Package to a final review and initiate the implementation of the service by submitting a formal Request for Change.
Definitions
The following ITIL terms and acronyms (information objects) are used in ITIL Design Coordination to represent process outputs and inputs:
Service Design Package (SDP)
- The Service Design Package builds upon the Service Level Requirements. It further specifies the requirements from the viewpoint of the client and defines how these are actually fulfilled from a technical and organizational point of view (see also: ITIL Checklist Service Design Package).
Service Design Policy
- The Service Design Policy provides guidance on how to ensure that a consistent approach is applied to all design activities. In particular, the Service Design Policy specifies which projects or Changes are required to undergo the formal Service Design stage, and who needs to be involved in Service Design to ensure that all relevant aspects are considered.
Templates
Roles | Responsibilities
Service Design Manager - Process Owner
- The Service Design Manager is responsible for producing quality, secure and resilient designs for new or improved services. This includes producing and maintaining all design documentation.
Responsibility Matrix: ITIL Design Coordination | |||||
ITIL Role | Sub-Process | Service Design Manager | Project Manager[3] | IT Operations Manager[3] | Financial Manager[3] | Other roles involved |
---|---|---|---|---|---|
Design Coordination Support | A[1]R[2] | - | - | - | - |
Service Design Planning | AR | R | - | - | - |
Service Design Coordination and Monitoring | A | - | R | R | - |
Technical and Organizational Service Design | A | - | - | - | R[4] |
Service Design Review and RFC Submission | AR | - | - | - | - |
Remarks
[1] A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Change Evaluation process.
[2] R: Responsible according to the RACI Model: Those who do the work to achieve a task within Change Evaluation.
[3] see → Role descriptions
[4] Applications Analyst, Technical Analyst, IT Operations Manager, Process Architect, Process Owner and others, depending on the expertise required (see → Role descriptions)
[ Infobox ]
Link to this page: | https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination |
Languages: | English | Deutsch |
Image: | ITIL Design Coordination (.JPG) |
Author: | Stefan Kempter, IT Process Maps ![]() |
Process Description › Sub-Processes › Definitions › SDP Template › Roles