ITIL Implementation - Process Structure: Difference between revisions

From IT Process Wiki
No edit summary
 
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
<itpmch><title>ITIL Implementation - Process Structure | IT Process Wiki</title>
<meta name="keywords" content="itil process structure, itil structure, it process structure" />
<meta name="description" content="The conclusions drawn from the analysis of the current situation provide the basis for developing the to-be process structure." />
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_Process_Structure" />
<meta property="og:title" content="ITIL Implementation - Process Structure | IT Process Wiki" />
<meta property="og:description" content="The conclusions drawn from the analysis of the current situation provide the basis for developing the to-be process structure." />
<meta property="og:site_name" content="IT Process Wiki - the ITIL&#174; Wiki">
<meta property="og:type" content="article" />
<meta property="fb:admins" content="100002035253209" />
<meta property="fb:admins" content="100002592864414" />
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/6/63/5-itil-implementation-to-be-process-structure.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="600" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
</itpmch>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|right|DE - ES - ITIL To-Be Process Structure|163px
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_Prozess-Struktur diese Seite auf Deutsch]
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/Implementaci%C3%B3n_de_ITIL_-_Definici%C3%B3n_de_la_estructura_de_procesos esta página en español]
desc none
</imagemap>
<br style="clear:both;"/>
[[image:Defining-the-to-be-process-structure-itil-step-5.jpg|thumb|285px|right|alt=Definition of the To-Be Process Structure. ITIL implementation, step 5.|link=https://wiki.en.it-processmaps.com/index.php/File:Defining-the-to-be-process-structure-itil-step-5.jpg|[[Media:Defining-the-to-be-process-structure-itil-step-5.jpg|Infographic: Definition of the to-be process structure. - ITIL implementation, step 5.]]]]
{|
{|
! align="right" width="80%"|
|-
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_Prozess-Struktur diese Seite auf Deutsch]
|style="border-bottom:1px solid grey; font-size:130%"|<strong>Step 5: Definition of the To-Be Process Structure</strong>
|}
|}


'''''Step 5: Definition of the To-Be Process Structure'''''
<p>&nbsp;</p>
 
The conclusions drawn from the analysis of the current situation provide the basis for developing the to-be process structure.
 
As a first step, a list should be drawn up with the processes and sub-processes which are to be introduced or improved, resulting in a structured process breakdown.
 
__TOC__
 
===<span id="Objective of this Project Step">Objectives</span>===
 
*Determination of the service management processes which are to be introduced
*Breakdown of processes into sub-processes
<br style="clear:both;"/>
 
==Description==


Following the analysis of the initial situation, it can be decided in more detail where the ITIL project will put its focus. In other words, a decision needs to be taken as to which Service Management processes are to be introduced, resulting in an overview and breakdown of the processes.
[[image:Thumb_to_be_process_structure.jpg|thumb|200px|right|alt=ITIL Process Structure|link=https://wiki.en.it-processmaps.com/index.php/File:Thumb_to_be_process_structure.jpg|Fig. 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 to-be process structure does not contain detailed process descriptions - these are developed at a later stage, after establishing a framework of process controlling and process interfaces.
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.  


==== Objective of this Project Step ====
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.


* Determination of the Service Management processes which are to be introduced
The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map] contains a generic process structure so it can be used to support this step.
* Breakdown of processes into sub-processes
<br style="clear:both;"/>


==== Prerequisites ====
==Prerequisites==


* Results of the ITIL assessment
*Results of the [[ITIL Implementation - ITIL Assessment|as-is process assessment]]
* Project objectives („What is to be achieved by the alignment of the IT organisation with ITIL principles?).
*Project objectives ("What is the motivation for introducing ITIL best practice?").


==== Results/ Deliverables ====
==Results/ Deliverables==


* Structure of the Service Management processes to be introduced
*Structured breakdown of the ITIL processes to be introduced
* Process overviews (process breakdown)
 
[[image:Thumb_to_be_process_structure.jpg|frame|left|Selection of Relevant ITIL Processes from the Reference Process Structure]]
==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==
 
[[image:thumb-itil-process-overview.jpg|thumb|400px|right|alt=ITIL overview diagram|link=https://wiki.en.it-processmaps.com/index.php/File:Thumb-itil-process-overview.jpg|Fig. 2: Overview diagram, depicting ITIL process interdependencies]]
The [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map] contains a hierarchical structure of ITIL processes - see fig.&nbsp;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 as a starting point.
 
Process overviews (see [[media:thumb-itil-process-overview.jpg|fig. 2]]) depict the process interdependencies and help to choose an adequate to-be process structure.
<br style="clear:both;"/>
<br style="clear:both;"/>
==== Description ====


The Processes to be introduced often result in a direct way from the project objectives:
<html>
If the project serves the objective of enhancing user support and dealing more professionally with the elimination of repeatedly occurring interruptions, then the ITIL discipline „Service Desk and Incident Management“ is to be established or improved, ideally in combination with „Problem Management“ and „Configuration Management“. The Service Management project would therefore set its focus on these three processes.
<a href="https://demo.it-processmaps.com/howto_en/navigating-the-itil-process-model.html" ><img src="https://demo.it-processmaps.com/howto_en/video-navigating-the-itil-process-model.jpg" width="253" height="150" class="thumbimage" alt="Video: Navigating the ITIL process model" title="Watch the video: Navigating the ITIL process model" style="display: block; float: left; margin-left: 10px; margin-bottom: 10px; margin-right: 30px" /></a>
<p style="margin-top: 0; word-wrap:normal;">Recommended&nbsp;ways of navigating the contents of our ITIL process model - the ITIL&reg; Process Map.</p>
<p>Watch the video: <a href="https://demo.it-processmaps.com/howto_en/navigating-the-itil-process-model.html" title="Start video: Navigating the ITIL process model">Navigating the ITIL process model</a> (5:40 min.)
<br style="clear:both;"/></html>
 
==Resources==
*[1] [[ITIL_Processes#ITIL_Processes_according_to_ITIL_V3|ITIL processes - ITIL process descriptions]]
*[2] [https://wiki.en.it-processmaps.com/images/pdf/generic-itil-process-structure.pdf Generic ITIL process structure (.pdf)] - Example: ITIL Service Operation
 
==Following project activity==


Additional considerations are, however, in place in some cases:
&#8594; ITIL Implementation - Step 6: '''[[ITIL Implementation - Process Interfaces|Definition of Process Interfaces]]'''


If the objective is to introduce pro­per change management, in order to rule out unauthorised alterations to the IT infrastructure and better avoid side-effects caused by changes, then the focus will be on the Change Management process.
==Notes==


In order for any Change Management to function effectively, the availability of reliable data on the IT infrastructure (Configuration Items and their interrelations) is an important prerequisite.
<html>By:&#160;&#160;Andrea Kempter&#160;<a rel="author" href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.
This calls for a well-functioning Configuration Management, so any project aiming at improving Change Management must also include in its scope the Configuration Management process.


==== Success Factors ====
<p>&nbsp;</p>


* The aim of this project step is to choose the ITIL processes and sub-processes; this will also further detail the project scope
<p><small>
* Details of the process interfaces  will be the subject of the following project steps
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_Process_Structure#Objectives">
<span itemprop="name">Objectives</span></a>
<meta itemprop="position" content="1"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_Process_Structure#Description">
<span itemprop="name">Description</span></a>
<meta itemprop="position" content="2"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_Process_Structure#Prerequisites">
<span itemprop="name">Prerequisites</span></a>
<meta itemprop="position" content="3"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_Process_Structure#Results.2F_Deliverables">
<span itemprop="name">Results/ Deliverables</span></a>
<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/ITIL_Implementation_-_Process_Structure#Success_Factors">
<span itemprop="name">Success Factors</span></a>
<meta itemprop="position" content="5"></span>
</span>
</small></p>


<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage">
  <meta itemprop="name" content="ITIL Implementation - Process Structure" />
  <meta itemprop="description" content="The conclusions drawn from the analysis of the current situation provide the basis for developing the to-be process structure." />
  <link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Implementation_-_Process_Structure" />
  <meta itemprop="inLanguage" content="en" />
  <link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL-Implementierung_-_Prozess-Struktur" />
  <link itemprop="citation" href="https://wiki.es.it-processmaps.com/index.php/Implementaci%C3%B3n_de_ITIL_-_Definici%C3%B3n_de_la_estructura_de_procesos" />
  <meta itemprop="Headline" content="ITIL Implementation - Process Structure" />
  <meta itemprop="alternativeHeadline" content="Step 5: Definition of the To-Be Process Structure" />
  <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/1/1f/Thumb_to_be_process_structure.jpg" title="Selection of Relevant ITIL Processes" />
  <link itemprop="author" href="https://www.linkedin.com/in/andreakempter" />
  <meta itemprop="author" content="Andrea Kempter" />
  <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />
</span><p></html>


==== Following Process Activity ====
<!-- This page is assigned to the following categories: -->
''Step 6:'' '''''[[ITIL Implementation - Process Interfaces|Definition of the Process Interfaces]]'''''
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL implementation]]
<!-- --- -->

Latest revision as of 14:35, 5 April 2022

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


Definition of the To-Be Process Structure. ITIL implementation, step 5.
Infographic: Definition of the to-be process structure. - ITIL implementation, step 5.
Step 5: Definition of the To-Be Process Structure

 

The conclusions drawn from the analysis of the current situation provide the basis for developing the to-be process structure.

As a first step, a list should be drawn up with the processes and sub-processes which are to be introduced or improved, resulting in a structured process breakdown.

Objectives

  • Determination of the service management processes which are to be introduced
  • Breakdown of processes into sub-processes


Description

ITIL Process Structure
Fig. 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.

The ITIL Process Map contains a generic process structure so it can be used to support this step.

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
Fig. 2: Overview diagram, depicting ITIL process interdependencies

The ITIL Process Map contains a hierarchical structure of ITIL processes - see fig. 1: Reference process structure (.pdf). This generic process structure can be used as a starting point.

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

Video: Navigating the ITIL process model

Recommended ways of navigating the contents of our ITIL process model - the ITIL® Process Map.

Watch the video: Navigating the ITIL process model (5:40 min.)

Resources

Following project activity

→ ITIL Implementation - Step 6: Definition of Process Interfaces

Notes

By:  Andrea Kempter , IT Process Maps.

 

Objectives  › Description  › Prerequisites  › Results/ Deliverables  › Success Factors