ITIL 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
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".
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.
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.
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.
|ITIL Role / Sub-Process||Service Design Manager||Project Manager||IT Operations Manager||Financial Manager||Other roles involved|
|Design Coordination Support||AR||-||-||-||-|
|Service Design Planning||AR||R||-||-||-|
|Service Design Coordination and Monitoring||A||-||R||R||-|
|Technical and Organizational Service Design||A||-||-||-||R|
|Service Design Review and RFC Submission||AR||-||-||-||-|
 A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Change Evaluation process.
 R: Responsible according to the RACI Model: Those who do the work to achieve a task within Change Evaluation.
 see → Role descriptions
 Applications Analyst, Technical Analyst, IT Operations Manager, Process Architect, Process Owner and others, depending on the expertise required (see → Role descriptions)
By: Stefan Kempter , IT Process Maps.
Process Description › Sub-Processes › Definitions › SDP Template › Roles