ITIL Introduction in Stages: Difference between revisions
mNo edit summary |
|||
| Line 1: | Line 1: | ||
<seo metakeywords="itil stages, itil introduction" metadescription="ITIL Introduction in Stages. Rather than introducing the full set of ITIL recommendations at once, most organizations start with a ..." /> | |||
<imagemap> | |||
Image:ITIL-Wiki-de-es.jpg|DE - ES - ITIL Introduction in Stages|100px | |||
rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/Schrittweise_ITIL-Einf%C3%BChrung diese Seite auf Deutsch] | |||
rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/Introducci%C3%B3n_de_ITIL_por_etapas esta página en español] | |||
desc none | |||
</imagemap> | |||
<br style="clear:both;"/> | |||
Rather than introducing the full set of ITIL recommendations at once, most organizations start with a subset of ITIL processes. | |||
The prevailing motivation for the introduction of ITIL is often a desire to be able to deal with Incidents more professionally. This requires the availability of a central point-of-contact for the user, where calls are received and the necessary steps for the correction of the error taken | The prevailing motivation for the introduction of ITIL is often a desire to be able to deal with Incidents more professionally. This requires the availability of a central point-of-contact for the user (known in ITIL as the “Service Desk”), where calls are received and the necessary steps for the correction of the error taken. | ||
==== Step One: Taking Care of Incidents and Problems ==== | ==== Step One: Taking Care of Incidents and Problems ==== | ||
In order to realise this, an ITIL introduction frequently begins with the processes „[[Incident Management]]“, supplemented by „[[Problem Management]]“, which takes care of errors that are only able to be corrected with considerable effort. In the course of this, the process „[[Configuration Management]]“ should | In order to realise this, an ITIL introduction frequently begins with the processes „[[Incident Management|Incident Management]]“, supplemented by „[[Problem Management|Problem Management]]“, which takes care of errors that are only able to be corrected with considerable effort. In the course of this, the process „[[Service Asset and Configuration Management|Service Asset and Configuration Management]]“ should be included, because reliable data on the IT infrastructure will significantly improve the effectiveness of Incident and Problem Management. Configuration Management is the pre-condition for the efficient processing of Incidents, as well as for the identification of underlying trends, like e.g. recurring defects on a certain type of PC. | ||
==== Change and Release Management as a Second Step ==== | ==== Change and Release Management as a Second Step ==== | ||
| Line 25: | Line 29: | ||
==== Third Step: Focus on the Client ==== | ==== Third Step: Focus on the Client ==== | ||
In a third step, the conditions are created for | In a third step, the conditions are created for agreeing and monitoring service levels. This will mainly require a “[[Service Level Management|Service Level Management]]” process, but also “[[Capacity Management|Capacity Management]]”, “[[Availability Management|Availability Management]]” and “[[IT Service Continuity Management|IT Service Continuity Management]]” to make sure that the relevant service level targets are actively managed. | ||
Taking the example further, in the case of our defective PC there would now be a binding rule as to how swiftly the problem must be resolved. | Taking the example further, in the case of our defective PC there would now be a binding rule as to how swiftly the problem must be resolved. | ||
| Line 32: | Line 36: | ||
In the same way as ITIL processes can be introduced as subsets, a certification according to [[ISO 20000]] is also possible for parts of the entire scope. | In the same way as ITIL processes can be introduced as subsets, a certification according to [[ISO 20000]] is also possible for parts of the entire scope. | ||
''' Back to: ''' | |||
→ '''[[ITIL Implementation|ITIL Implementation - ITIL Implementation in 10 Steps]]''' | |||
<!-- This page is assigned to the following categories: --> | |||
[[Category:ITIL implementation]][[Category:ITIL process]] | |||
<!-- --- --> | |||
Revision as of 20:32, 26 July 2011
<seo metakeywords="itil stages, itil introduction" metadescription="ITIL Introduction in Stages. Rather than introducing the full set of ITIL recommendations at once, most organizations start with a ..." />
Rather than introducing the full set of ITIL recommendations at once, most organizations start with a subset of ITIL processes.
The prevailing motivation for the introduction of ITIL is often a desire to be able to deal with Incidents more professionally. This requires the availability of a central point-of-contact for the user (known in ITIL as the “Service Desk”), where calls are received and the necessary steps for the correction of the error taken.
Step One: Taking Care of Incidents and Problems
In order to realise this, an ITIL introduction frequently begins with the processes „Incident Management“, supplemented by „Problem Management“, which takes care of errors that are only able to be corrected with considerable effort. In the course of this, the process „Service Asset and Configuration Management“ should be included, because reliable data on the IT infrastructure will significantly improve the effectiveness of Incident and Problem Management. Configuration Management is the pre-condition for the efficient processing of Incidents, as well as for the identification of underlying trends, like e.g. recurring defects on a certain type of PC.
Change and Release Management as a Second Step
The enterprise as a whole depends on an up-to-date, reliable and secure IT infrastructure in order to support its business processes.
The effects caused by unauthorised or un-coordinated changes to this infrastructure are often not only undesired, but can also lead to business disruptions.
For this reason it is of particular importance to many businesses, that changes to the IT infrastructure only take place in a coordinated way. The second phase of an ITIL introduction therefore often seeks to establish the Change and Release and Deployment Management processes.
Continuing the above example of a defective PC, the user can be assisted far sooner if Change and Release Management are in place. The key here is to block changes of which Change Management (and therefore, the Service Desk) is not aware, so that it is known without doubt at any time what programs are installed on the PC, what are its hardware components, etc.
Third Step: Focus on the Client
In a third step, the conditions are created for agreeing and monitoring service levels. This will mainly require a “Service Level Management” process, but also “Capacity Management”, “Availability Management” and “IT Service Continuity Management” to make sure that the relevant service level targets are actively managed.
Taking the example further, in the case of our defective PC there would now be a binding rule as to how swiftly the problem must be resolved.
Modular ISO Certification
In the same way as ITIL processes can be introduced as subsets, a certification according to ISO 20000 is also possible for parts of the entire scope.
Back to:
