ITIL Implementation - Process Structure
|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.
- Determination of the service management processes which are to be introduced
- Breakdown of processes into sub-processes
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.
- Results of the as-is process assessment
- Project objectives ("What is the motivation for introducing ITIL best practice?").
- Structured breakdown of the ITIL processes to be introduced
- 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
Process overviews (see fig. 2) depict the process interdependencies and help to choose an adequate to-be process structure.
-  ITIL processes - ITIL process descriptions
-  Generic ITIL process structure (.pdf) - Example: ITIL Service Operation
Following project activity
→ ITIL Implementation - Step 6: Definition of Process Interfaces