ITIL Implementation - Process Structure: Difference between revisions

From IT Process Wiki
No edit summary
Line 1: Line 1:
<seo metakeywords="itil process structure, itil structure, it process structure" metadescription="Definition of the To-Be Process Structure - Fig. 1: Selection of Relevant ITIL Processes from the Reference Process Structure." />
<seo metakeywords="itil process structure, itil structure, it process structure" metadescription="Determination of the ITIL processes to be introduced (To-Be Process Structure) - Selection of relevant ITIL processes from the reference process structure..." />
<imagemap>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|DE - ES - ITIL To-Be Process Structure|100px
Image:ITIL-Wiki-de-es.jpg|DE - ES - ITIL To-Be Process Structure|100px
Line 13: Line 13:
|}
|}


Following the analysis of the initial situation, it can be decided in more detail where the ITIL project will put its focus. In practice this means to determine which ITIL processes are to be introduced, resulting in in a structured process breakdown.
Following the analysis of the initial situation, it can be decided in more detail where the ITIL project will put its focus. In practice this means to determine which ITIL processes are to be introduced, resulting in a structured process breakdown.


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 26: Line 26:
==== Description ====
==== Description ====


[[image:Thumb_to_be_process_structure.jpg|frame|right|alt=ITIL Process Structure|Figure 1: Selection of Relevant ITIL Processes from the Reference Process Structure]]
[[image:Thumb_to_be_process_structure.jpg|frame|right|alt=ITIL Process Structure|Figure 1: Selection of Relevant ITIL Processes from the [https://wiki.en.it-processmaps.com/images/pdf/generic-itil-process-structure.pdf ITIL Reference Process Structure (.pdf)]]]
The [[ITIL Processes|ITIL processes]] to be introduced often result in a direct way from the project objectives:
The [[ITIL Processes|ITIL processes]] to be introduced often result in a direct way from the project objectives:


If the project serves the objective of enhancing user support, the "[[Incident Management|Incident Management]]" process is to be established or improved. Because of their close links with Incident Management, the "[[Problem Management|Problem Management]]" and "[[Service Asset and Configuration Management|Service Asset and Configuration Management]]" processes should also be included in the project scope.  
If the project serves the objective of enhancing user support, the "[[Incident Management]]" process is to be established or improved. Because of their close links with Incident Management, the "[[Problem Management]]" and "[[Service Asset and Configuration Management|Configuration Management]]" processes should also be included in the project scope.  


The aim of this project step is primarily to choose the ITIL processes and sub-processes. The to-be process structure does not contain detailed process descriptions - these are developed at a later stage.
The aim of this project step is primarily to choose the ITIL processes and sub-processes. The to-be process structure does not contain detailed process descriptions - these are developed at a later stage.


ITIL process templates (e.g. the [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3]) can be used to support this step because they contain a generic process structure.
ITIL process templates (e.g. the [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map]) can be used to support this step because they contain a generic process structure.


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 55: Line 55:


<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
==== <span style="color:#5d5d5d">Relevant Views of the ITIL Process Map</span>====


[[image:thumb-itil-process-overview.jpg|frame|right|alt=ITIL overview diagram|Figure 2: Overview diagram, depicting ITIL process interdependencies]]
[[image:thumb-itil-process-overview.jpg|frame|right|alt=ITIL overview diagram|Figure 2: Overview diagram, depicting ITIL process interdependencies]]
==== <span style="color:#5d5d5d">Relevant Views of the ITIL Process Map V3</span>====
<span style="color:#5d5d5d">The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map] contains a complete ITIL-compliant process structure, arranged in a hierarchical way ''(see Figure 1: [https://wiki.en.it-processmaps.com/images/pdf/generic-itil-process-structure.pdf Reference Process Structure (.pdf)])''. This generic process structure can be used in many cases with only minor changes.</span>
 
<span style="color:#5d5d5d">Process overviews ''(see [[media:thumb-itil-process-overview.jpg|Figure 2]])'' depict the process interdependencies and help to choose an adequate to-be process structure.</span>


<span style="color:#5d5d5d">The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3] contains a complete ITIL-compliant process structure, arranged in a hierarchical way ''(see Figure 1)''. This generic process structure can be used in many cases with only minor changes.</span>
<br style="clear:both;"/>


<span style="color:#5d5d5d">Process overviews ''(see Figure 2)'' depict the process interdependencies and help to choose an adequate to-be process structure.</span>
==== Resources ====
* [1] [[ITIL Processes#ITIL Processes according to ITIL 2011|ITIL processes - ITIL process descriptions according to ITIL 2011]]
* [2] [https://wiki.en.it-processmaps.com/images/pdf/generic-itil-process-structure.pdf Generic ITIL process structure (.pdf)] - Example: ITIL Service Operation


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 69: Line 76:
&#8594; ITIL Implementation - Step 6: '''[[ITIL Implementation - Process Interfaces|Definition of Process Interfaces]]'''
&#8594; ITIL Implementation - Step 6: '''[[ITIL Implementation - Process Interfaces|Definition of Process Interfaces]]'''


<br style="clear:both;"/>
<p>&nbsp;</p>


<p>&nbsp;</p>
<html><a rel="author" href="https://plus.google.com/113316270668629760475"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a></html>


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3]][[Category:ITIL implementation]]
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL implementation]]
<!-- --- -->
<!-- --- -->

Revision as of 11:18, 30 June 2013

<seo metakeywords="itil process structure, itil structure, it process structure" metadescription="Determination of the ITIL processes to be introduced (To-Be Process Structure) - Selection of relevant ITIL processes from the reference process structure..." />

DE - ES - ITIL To-Be Process Structurediese Seite auf Deutschesta página en español
DE - ES - ITIL To-Be Process Structure


Step 5: Definition of the To-Be Process Structure

Following the analysis of the initial situation, it can be decided in more detail where the ITIL project will put its focus. In practice this means to determine which ITIL processes are to be introduced, resulting in a structured process breakdown.

 

Objective of this Project Step

  • Determination of the Service Management processes which are to be introduced
  • Breakdown of processes into sub-processes

 

Description

ITIL Process Structure
Figure 1: Selection of Relevant ITIL Processes from the ITIL Reference Process Structure (.pdf)

The ITIL processes to be introduced often result in a direct way from the project objectives:

If the project serves the objective of enhancing user support, the "Incident Management" process is to be established or improved. Because of their close links with Incident Management, the "Problem Management" and "Configuration Management" processes should also be included in the project scope.

The aim of this project step is primarily to choose the ITIL processes and sub-processes. The to-be process structure does not contain detailed process descriptions - these are developed at a later stage.

ITIL process templates (e.g. the ITIL Process Map) can be used to support this step because they contain a generic process structure.

 

Prerequisites

  • Results of the as-is process assessment
  • Project objectives ("What is the motivation for introducing ITIL Best Practice?").

 

Results/ Deliverables

  • Structured breakdown of the ITIL processes to be introduced

 

Success Factors

  • The definition of the process structure should not try to anticipate later project steps; the aim of this step is to identify the processes and sub-processes to be introduced, not to specify processes in great detail.

 

 

Relevant Views of the ITIL Process Map

ITIL overview diagram
Figure 2: Overview diagram, depicting ITIL process interdependencies

The ITIL Process Map contains a complete ITIL-compliant process structure, arranged in a hierarchical way (see Figure 1: Reference Process Structure (.pdf)). This generic process structure can be used in many cases with only minor changes.

Process overviews (see Figure 2) depict the process interdependencies and help to choose an adequate to-be process structure.


Resources

 

Following Project Activity:

→ ITIL Implementation - Step 6: Definition of Process Interfaces