ITIL Design Coordination: Difference between revisions

From IT Process Wiki
No edit summary
No edit summary
Line 11: Line 11:
<meta property="fb:admins" content="100002592864414" />
<meta property="fb:admins" content="100002592864414" />
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/2/20/Itil-design-coordination.jpg" />
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/2/20/Itil-design-coordination.jpg" />
<meta property="og:image:width" content="960" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="787" />
<meta property="og:image:height" content="1200" />
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@itprocessmaps">
<meta name="twitter:creator" content="@itprocessmaps">
<meta name="twitter:title" content="ITIL Design Coordination | IT Process Wiki">
<meta name="twitter:description" content="Design Coordination aims to coordinate all service design activities, processes and resources. This ITIL process ensures the consistent and effective design of new or changed IT services, service management information systems, architectures, technology, processes, information and metrics.">
<meta name="twitter:image" content="https://wiki.en.it-processmaps.com/images/thumb/2/20/Itil-design-coordination.jpg/600px-Itil-design-coordination.jpg">
<meta name="twitter:image:alt" content="Overview of ITIL Design Coordination: This image illustrates the Design Coordination process according to ITIL, highlighting the most important interfaces of Design Coordination, its sub-processes and their interrelationships.">
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
</itpmch>
</itpmch>
Line 37: Line 44:
==Process Description==
==Process Description==


[[Image:Itil-design-coordination.jpg|right|thumb|370px|alt=Design Coordination ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Itil-design-coordination.jpg|[https://wiki.en.it-processmaps.com/images/pdf/process-overview-design-coordination-itil.pdf ITIL Design Coordination]]]
[[Image:Itil-design-coordination.jpg|right|thumb|500px|alt=Design Coordination ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Itil-design-coordination.jpg|[https://wiki.en.it-processmaps.com/images/pdf/process-overview-design-coordination-itil.pdf ITIL Design Coordination (.pdf)]]]
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.
Design Coordination has been added as a new process, in line with the ITIL 2011 guidance. Design Coordination is 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 [[#Design Coordination Planning|Decomposition of Business Service into Supporting Services]], [[#Technical and Organizational Service Design|Technical and Organizational Service Design]] and [[#Design Coordination Review RFC|RFC Compilation and Submission]] have been moved from Service Level Management to Design Coordination.
In the previous ITIL version, some of these tasks were carried out as part of Service Level Management, which is why the sub-processes '[[#Design Coordination Planning|Decomposition of Business Service into Supporting Services]]', '[[#Technical and Organizational Service Design|Technical and Organizational Service Design]]' and '[[#Design Coordination Review RFC|RFC Compilation and Submission]]' have been moved from Service Level Management to Design Coordination.


The process overview of [[Media:Itil-design-coordination.jpg|ITIL Design Coordination]] shows the key information flows (see Fig. 1).
The process overview of [[Media:Itil-design-coordination.jpg|ITIL Design Coordination]] shows the key information flows (see fig. 1).


<p>&nbsp;</p>
[[ITIL 4]] does not include a design coordination process. Design coordination activities are described in the [[ITIL_4#Service_management_practices|service management practice]] of "service design".
<p style="clear:both;">&nbsp;</p>


==Sub-Processes==
==Sub-Processes==
Line 52: Line 60:
<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><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>&#160;</p>
<p><b><span id="ITIL_Design_Coordination_Support" itemprop="itemListElement">Design Coordination Support</span></b>
<p><b><span id="ITIL_Design_Coordination_Support" itemprop="itemListElement">Design Coordination Support</span></b>
</p>
</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.
<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>
</li></ul>
<p><br />
<p><b><span id="Design_Coordination_Planning" itemprop="itemListElement">Service Design Planning</span></b>
</p><p><b><span id="Design_Coordination_Planning" itemprop="itemListElement">Service Design Planning</span></b>
</p>
</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.
<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>
</li></ul>
<p><br />
<p><b><span id="ITIL_Design_Coordination_and_Monitoring" itemprop="itemListElement">Service Design Coordination and Monitoring</span></b>
</p><p><b><span id="ITIL_Design_Coordination_and_Monitoring" itemprop="itemListElement">Service Design Coordination and Monitoring</span></b>
</p>
</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.
<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>
</li></ul>
<p><br />
<p><b><span id="Technical_and_Organizational_Service_Design" itemprop="itemListElement">Technical and Organizational Service Design</span></b>
</p><p><b><span id="Technical_and_Organizational_Service_Design" itemprop="itemListElement">Technical and Organizational Service Design</span></b>
</p>
</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.
<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>
</li></ul>
<p><br />
<p><b><span id="Design_Coordination_Review_&#82;FC" itemprop="itemListElement">Service Design Review and RFC Submission</span></b>
</p><p><b><span id="Design_Coordination_Review_&#82;FC" itemprop="itemListElement">Service Design Review and RFC Submission</span></b>
</p>
</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>.
<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>
</li></ul>
</div><!-- end of schema.org/ItemList --><p></html>
</div><!-- end of schema.org/ItemList --><p></html>
<p>&nbsp;</p>


==Definitions==
==Definitions==
Line 84: Line 86:
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<meta itemprop="itemListOrder" content="Ascending" />
<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><span itemprop="name">The following <a href="/index.php/ITIL_Glossary#ITIL_Glossary_A-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>&#160;</p>
<p><b><span id="SDP" itemprop="itemListElement">Service Design Package (SDP)</span></b>
<p><b><span id="SDP" itemprop="itemListElement">Service Design Package (SDP)</span></b>
</p>
</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>.
<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>
</li></ul>
<p><br />
<p><b><span id="Service_Design_Policy" itemprop="itemListElement">Service Design Policy</span></b>
</p><p><b><span id="Service_Design_Policy" itemprop="itemListElement">Service Design Policy</span></b>
</p>
</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.
<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>
</li></ul>
</div><!-- end of schema.org/ItemList --><p></html>
</div><!-- end of schema.org/ItemList --><p></html>
<p>&nbsp;</p>


==<span id="Checklists">Templates</span>==
==<span id="Checklists">Templates</span>==
Line 103: Line 102:
<html><ul><li><a 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>
<html><ul><li><a 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>
</li></ul><p></html>
<p>&nbsp;</p>


==Roles | Responsibilities==
==Roles | Responsibilities==
Line 112: Line 110:
<p>&nbsp;</p>
<p>&nbsp;</p>


{| border="1" cellpadding="5" cellspacing="0" style="margin-left: auto; margin-right: auto; text-align:center;" valign="top"
{| class="wikitable" style="background: white;"
|-
|-
|style="vertical-align:top; text-align:center" colspan="6" style="background:#ffffdd;"| '''Responsibility Matrix: ITIL Design Coordination'''
|+ style="background:#013b5e; color:#ffffff; font-size: 120%" colspan="6"|'''Responsibility Matrix: ITIL Design Coordination'''
|-
|-
!style="background:#ffffee; width: 50%; text-align:center"| ITIL Role | Sub-Process
!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:#eeeeee;" | [[ITIL Design Coordination#Service Design Manager|Service Design Manager]]
! style="background:#ffffee;" | Project Manager[[ITIL Design Coordination#Team|<small>[3]</small>]]
! style="background:#eeeeee;" | Project Manager[[ITIL Design Coordination#Team|<small>[3]</small>]]
! style="background:#ffffee;" | IT Operations Manager[[ITIL Design Coordination#Team|<small>[3]</small>]]
! style="background:#eeeeee;" | IT Operations Manager[[ITIL Design Coordination#Team|<small>[3]</small>]]
! style="background:#ffffee;" | Financial Manager[[ITIL Design Coordination#Team|<small>[3]</small>]]
! style="background:#eeeeee;" | Financial Manager[[ITIL Design Coordination#Team|<small>[3]</small>]]
! style="background:#ffffee;" | Other roles involved
! style="background:#eeeeee;" | Other roles involved
|-
|-
|style="text-align:left;" |[[#ITIL Design Coordination Support|Design Coordination Support]]
|style="text-align:left;" |[[#ITIL Design Coordination Support|Design Coordination Support]]
Line 159: Line 157:
|-
|-
|}
|}
<p>&nbsp;</p>


'''Remarks'''
'''Remarks'''
Line 171: Line 167:


<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|&#8594; Role descriptions]])</span>
<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|&#8594; Role descriptions]])</span>
<p>&nbsp;</p>


==Notes==
==Notes==
Line 215: Line 209:
   <link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" />
   <link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" />
   <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/2/20/Itil-design-coordination.jpg" />
   <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/2/20/Itil-design-coordination.jpg" />
  <span id="https://wiki.en.it-processmaps.com/images/2/20/Itil-design-coordination.jpg" itemprop="image" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="caption" content="ITIL Design Coordination">
  <meta itemprop="contentUrl" content="https://wiki.en.it-processmaps.com/images/2/20/Itil-design-coordination.jpg" />
  <meta itemprop="width" content="1200" />
  <meta itemprop="height" content="1200" />
  <meta itemprop="representativeOfPage" content="true"/>
  <meta itemprop="dateCreated" content="2011-11-22" />
  <meta itemprop="dateModified" content="2020-06-20" />
  <span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
    <meta itemprop="url" content="https://wiki.en.it-processmaps.com/images/thumb/2/20/Itil-design-coordination.jpg/600px-Itil-design-coordination.jpg" />
    <meta itemprop="width" content="600" />
    <meta itemprop="height" content="600" />
  </span>
  <meta itemprop="keywords" content="Design Coordination" />
  <meta itemprop="keywords" content="ITIL Design Coordination" />
  </span>
   <link itemprop="author" href="https://www.linkedin.com/in/stefankempter" />
   <link itemprop="author" href="https://www.linkedin.com/in/stefankempter" />
   <meta itemprop="author" content="Stefan Kempter" />
   <meta itemprop="author" content="Stefan Kempter" />
Line 221: Line 231:


<!-- 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 Design|Design Coordination]][[Category:Design Coordination|!]]
[[Category:ITIL 2011]][[Category:ITIL V3]][[Category:ITIL process]][[Category:Service Design|Design Coordination]][[Category:Design Coordination|!]]
<!-- --- -->
<!-- --- -->

Revision as of 15:01, 23 July 2020

share this pageshare this page on LinkedInshare this page on Twitter
share this page
Design Coordination
Design Coordination


Objective: Design Coordination aims to coordinate all service design activities, processes and resources. This ITIL process 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
ITIL Design Coordination (.pdf)

Design Coordination has been added as a new process, in line with the ITIL 2011 guidance. Design Coordination is 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 shows the key information flows (see fig. 1).

ITIL 4 does not include a design coordination process. Design coordination activities are described in the service management practice of "service design".

 

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

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)

Notes

By:  Stefan Kempter , IT Process Maps.

 

Process Description  › Sub-Processes  › Definitions  › SDP Template  › Roles