Basic Ideas behind ITIL - Revision history

Andrea at 10:04, 30 March 2019

2019-03-30T10:04:19Z

← Older revision		Revision as of 12:04, 30 March 2019
Line 15:		Line 15:
	</itpmch>		</itpmch>
	<imagemap>		<imagemap>
	Image:ITIL-Wiki-~~share~~.jpg\|right~~\|share this page\|141px~~		Image:ITIL-Wiki-deutsch.jpg\|right\|Basic Ideas behind ITIL
	rect 55 0 99 36 [https://www.linkedin.com/shareArticle?url=https%3A%2F%2Fwiki.en.it-processmaps.com%2Findex.php%2FBasic_Ideas_behind_ITIL&hl=en_US&source=IT%20Process%20Wiki share this page on LinkedIn]
	rect 97 0 141 36 [https://twitter.com/intent/tweet?url=https%3A%2F%2Fwiki.en.it-processmaps.com%2Findex.php%2FBasic_Ideas_behind_ITIL&text=%23ITILwiki%20%7C%20The%20basic%20ideas%20and%20principles%20behind%20ITIL%0A%E2%96%BA&lang=en&via=itprocessmaps share this page on Twitter]
	~~desc none~~
	~~</imagemap>~~
	~~<imagemap>~~
	~~Image:ITIL-Wiki-deutsch.jpg~~\|Basic Ideas behind ITIL
	default [https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken diese Seite auf Deutsch]		default [https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken diese Seite auf Deutsch]
	desc none		desc none
Line 126:		Line 120:
	<p> </p>		<p> </p>

	<html>By:  ~~Stefan~~ Kempter <a rel="author" href="https://~~plus~~.~~google~~.com/~~111925560448291102517~~/~~about~~"><img style="margin:0px 0px 0px 0px;" src="~~/skins/Vector~~/images~~/itpm~~/bookmarking/~~gplus~~.png" width="16" height="16" title="By: ~~Stefan~~ Kempter \| ~~Profil~~ on ~~Google+~~" alt="Author: ~~Stefan~~ Kempter, IT Process Maps GbR" /></a>  and  ~~Andrea~~ Kempter <a href="https://~~plus~~.~~google~~.com/~~113316270668629760475~~/~~about~~"><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="Contributor: ~~Andrea~~ Kempter, IT Process Maps GbR" /></a>, IT Process Maps.		<html>By:  Andrea Kempter <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>  and  Stefan Kempter <a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter \| Profile on LinkedIn" alt="Contributor: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.

	<p><small>		<p><small>
	<span itemscope="itemscope" itemtype="http://~~data-vocabulary~~.org/~~Breadcrumb~~">		<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
	<a href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Strategic_thinking~~" itemprop="url~~"><span itemprop="~~title~~">Strategic thinking</span></a> ›		<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
	</span>		<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Strategic_thinking"> <span itemprop="name">Strategic thinking</span></a><meta itemprop="position" content="1" /></span> ›
	<span ~~itemscope~~="itemscope" itemtype="http://~~data-vocabulary~~.org/~~Breadcrumb~~">		<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
	<a href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Customer_focus~~" itemprop="url~~"><span itemprop="~~title~~">Customer focus</span></a> ›		<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Customer_focus"> <span itemprop="name">Customer focus</span></a><meta itemprop="position" content="2" /></span> ›
	</span>		<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
	<span ~~itemscope~~="itemscope" itemtype="http://~~data-vocabulary~~.org/~~Breadcrumb~~">		<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Service_definitions"> <span itemprop="name">Service definitions</span></a><meta itemprop="position" content="3" /></span> ›
	<a href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Service_definitions~~" itemprop="url~~"><span itemprop="~~title~~">Service definitions</span></a> ›		<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
	</span>		<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Excellent_customer_support"> <span itemprop="name">Excellent customer support</span></a><meta itemprop="position" content="4" /></span> ›
	<span ~~itemscope~~="itemscope" itemtype="http://~~data-vocabulary~~.org/~~Breadcrumb~~">		<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
	<a href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Excellent_customer_support~~" itemprop="url~~"><span itemprop="~~title~~">Excellent customer support</span></a> ›		<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Continual_improvement"> <span itemprop="name">Continual improvement</span></a>
	</span>		<meta itemprop="position" content="5" /></span>
	<span ~~itemscope~~="itemscope" itemtype="http://~~data-vocabulary~~.org/~~Breadcrumb~~">
	<a href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Continual_improvement~~" itemprop="url~~"><span itemprop="~~title~~">Continual improvement</span></a>
	</span>		</span>
	</small></p>		</small></p>
Line 153:		Line 145:
	<meta itemprop="inLanguage" content="en" />		<meta itemprop="inLanguage" content="en" />
	<link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken" />		<link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken" />
	<link itemprop="author" href="https://~~plus~~.~~google~~.com/~~113316270668629760475~~/~~about~~" />		<link itemprop="author" href="https://www.linkedin.com/in/andreakempter" />
	<meta itemprop="author" content="Andrea Kempter" />		<meta itemprop="author" content="Andrea Kempter" />
	<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />		<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />

Andrea at 17:45, 21 January 2017

2017-01-21T17:45:46Z

← Older revision		Revision as of 19:45, 21 January 2017
Line 1:		Line 1:
	<itpmch><title>Basic Ideas behind ITIL \| IT Process Wiki</title>		<itpmch><title>Basic Ideas behind ITIL \| IT Process Wiki</title>
	<meta name="keywords" content="itil basic, basic itil, itil concepts, itil idea" />		<meta name="keywords" content="itil basic, basic itil, itil concepts, itil idea" />
	<meta name="description" content="The key to successfully using ITIL® is a good understanding of the ideas and principles behind ~~ITIL~~." />		<meta name="description" content="The key to successfully using ITIL® is a good understanding of the ideas and principles behind the IT Infrastructure Library." />
	<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL" />		<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL" />
	<meta property="og:title" content="Basic Ideas behind ITIL \| IT Process Wiki" />		<meta property="og:title" content="Basic Ideas behind ITIL \| IT Process Wiki" />
	<meta property="og:description" content="The key to successfully using ITIL® is a good understanding of the ideas and principles behind ITIL." />		<meta property="og:description" content="The key to successfully using ITIL® is a good understanding of the ideas and principles behind the IT Infrastructure Library. Once these principles are understood, service providers are in a position to decide which ITIL processes address their specific requirements, and to adopt those parts of the ITIL advice that solve their particular needs." />
	<meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki">		<meta property="og:site_name" content="IT Process Wiki - the ITIL® Wiki">
	<meta property="og:type" content="website" />		<meta property="og:type" content="website" />
Line 15:		Line 15:
	</itpmch>		</itpmch>
	<imagemap>		<imagemap>
	Image:ITIL-Wiki-~~deutsch~~.jpg\|right\|Basic Ideas behind ITIL		Image:ITIL-Wiki-share.jpg\|right\|share this page\|141px
			rect 55 0 99 36 [https://www.linkedin.com/shareArticle?url=https%3A%2F%2Fwiki.en.it-processmaps.com%2Findex.php%2FBasic_Ideas_behind_ITIL&hl=en_US&source=IT%20Process%20Wiki share this page on LinkedIn]
			rect 97 0 141 36 [https://twitter.com/intent/tweet?url=https%3A%2F%2Fwiki.en.it-processmaps.com%2Findex.php%2FBasic_Ideas_behind_ITIL&text=%23ITILwiki%20%7C%20The%20basic%20ideas%20and%20principles%20behind%20ITIL%0A%E2%96%BA&lang=en&via=itprocessmaps share this page on Twitter]
			desc none
			</imagemap>
			<imagemap>
			Image:ITIL-Wiki-deutsch.jpg\|Basic Ideas behind ITIL
	default [https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken diese Seite auf Deutsch]		default [https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken diese Seite auf Deutsch]
	desc none		desc none
	</imagemap>		</imagemap>
	<br style="clear:both;"/>		<br style="clear:both;"/>
	~~<p> </p>~~

	ITIL® describes several processes, organized around five [[ITIL_Processes#ITIL_Processes_according_to_ITIL_2011\|service lifecycle stages]]. An example would be the [[Incident Management]] process in the [[ITIL Service Operation\|Service Operation]] stage.		ITIL® describes several processes, organized around five [[ITIL_Processes#ITIL_Processes_according_to_ITIL_2011\|service lifecycle stages]]. An example would be the [[Incident Management]] process in the [[ITIL Service Operation\|Service Operation]] stage.
Line 36:		Line 41:
	Organizations that wish to adopt the ITIL approach will have to adapt the ITIL advice to their particular situation and needs. There is no question of implementing every ITIL process to the letter.		Organizations that wish to adopt the ITIL approach will have to adapt the ITIL advice to their particular situation and needs. There is no question of implementing every ITIL process to the letter.

	~~Therefore, the~~ key to successfully using ITIL is a good understanding of the ideas and principles behind ~~ITIL~~. Once these principles are understood, service providers are in a position to decide which ITIL processes address their specific requirements, and to adopt those parts of the ITIL advice that solve their particular needs.		<html><span id="md-webpage-description" itemprop="description">The key to successfully using ITIL® is a good understanding of the ideas and principles behind the IT Infrastructure Library. Once these principles are understood, service providers are in a position to decide which ITIL processes address their specific requirements, and to adopt those parts of the ITIL advice that solve their particular needs.</span></html>

	There is no definitive list of ITIL principles, so the list below should be seen as a summary of some ''important key ideas behind ITIL''.<br />		There is no definitive list of ITIL principles, so the list below should be seen as a summary of some ''important key ideas behind ITIL''.<br />
Line 139:		Line 144:
	<a href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Continual_improvement" itemprop="url"><span itemprop="title">Continual improvement</span></a>		<a href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL#Continual_improvement" itemprop="url"><span itemprop="title">Continual improvement</span></a>
	</span>		</span>
	</small>		</small></p>
	</html>
			<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description">
			<meta itemprop="name Headline" content="Basic Ideas behind ITIL" />
			<meta itemprop="alternativeHeadline" content="ITIL concepts" />
			<link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Basic_Ideas_behind_ITIL" />
			<link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/6/69/Itil-basic-concepts.jpg" />
			<meta itemprop="inLanguage" content="en" />
			<link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken" />
			<link itemprop="author" href="https://plus.google.com/113316270668629760475/about" />
			<meta itemprop="author" content="Andrea Kempter" />
			<meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />
			</span><p></html>

	<!-- This page is assigned to the following categories: -->		<!-- This page is assigned to the following categories: -->
	[[Category:IT Infrastructure Library ITIL]]		[[Category:IT Infrastructure Library ITIL]]
	<!-- --- -->		<!-- --- -->

Andrea at 18:18, 14 December 2016

2016-12-14T18:18:13Z

Show changes

WikiSysop at 16:57, 23 January 2012

2012-01-23T16:57:15Z

← Older revision		Revision as of 18:57, 23 January 2012
Line 1:		Line 1:
	<~~seo metakeywords~~="itil basic, basic itil" ~~metadescription~~="Basic Ideas behind ITIL. The two illustrations below highlight the main issues ITIL seeks to address: ..." />		<itpmch><title>Basic Ideas behind ITIL \| IT Process Wiki</title>
			<meta name="keywords" content="itil basic, basic itil" />
			<meta name="description" content="Basic Ideas behind ITIL. The two illustrations below highlight the main issues ITIL seeks to address: ..." />
			</itpmch>
	<imagemap>		<imagemap>
	Image:ITIL-Wiki-deutsch.jpg\|right\|Basic Ideas behind ITIL		Image:ITIL-Wiki-deutsch.jpg\|right\|Basic Ideas behind ITIL
Line 9:		Line 12:
	The two illustrations below highlight the main issues ITIL seeks to address:		The two illustrations below highlight the main issues ITIL seeks to address:

			<p> </p>

	==Traditional ~~Setup~~ of the IT ~~Organisation~~==		==Traditional setup of the IT organization==

	[[Image:traditional_setup_it_organisation.jpg\|frame\|right\|Traditional Setup of the IT ~~Organisation~~]]		[[Image:traditional_setup_it_organisation.jpg\|frame\|right\|Traditional Setup of the IT Organization]]
	Traditionally, there are two separate channels for the communication between the IT ~~organisation~~ and the client: Agreements concerning new applications or those to be altered are concluded between client and Application Development, whilst issues concerning operations are subsequently settled with the production personnel.		Traditionally, there are two separate channels for the communication between the IT organization and the client: Agreements concerning new applications or those to be altered are concluded between client and Application Development, whilst issues concerning operations are subsequently settled with the production personnel.

	This approach ~~involves~~ two ~~decisive~~ risks:		This approach creates two serious sets of risks:
	* Operational requirements, ensuring the error-free running of an application, are insufficiently considered during the development phase.		* Operational requirements, ensuring the error-free running of an application, are insufficiently considered during the development phase.
	* IT Operations is not fully able to control the release of applications into the productive environment; this might cause unforeseen side effects.		* IT Operations is not fully able to control the release of applications into the productive environment; this might cause unforeseen side effects.
	<br style="clear:both;"/>		<br style="clear:both;"/>

	==Setup of the IT ~~Organisation~~ according to ITIL==		==Setup of the IT organization according to ITIL==

	[[Image:setup_it_organisation_itil.jpg\|frame\|right\|Setup of the IT ~~Organisation~~ according to ITIL]]		[[Image:setup_it_organisation_itil.jpg\|frame\|right\|Setup of the IT Organization according to ITIL]]
	An [[ITIL Implementation\|implementation method based on ITIL]] has to resolve these particular problems by placing IT Service Management after Application Management and ICT Infrastructure Management: Thus, IT Service Management mediates between development and production on the side of the IT ~~organisation~~, and the client on the business-side.		An [[ITIL Implementation\|implementation method based on ITIL]] has to resolve these particular problems by placing IT Service Management after Application Management and ICT Infrastructure Management: Thus, IT Service Management mediates between development and production on the side of the IT organization, and the client on the business-side.

	The activities in Application Development and IT Operations are now co-ordinated and all the communication with the clients is directed via one central channel.		The activities in Application Development and IT Operations are now co-ordinated and all the communication with the clients is directed via one central channel.
	<br style="clear:both;"/>		<br style="clear:both;"/>

			<p> </p>

	<!-- This page is assigned to the following categories: -->		<!-- This page is assigned to the following categories: -->
	[[Category:IT Infrastructure Library ITIL]]		[[Category:IT Infrastructure Library ITIL]]
	<!-- --- -->		<!-- --- -->

Andrea at 08:01, 27 July 2011

2011-07-27T08:01:34Z

← Older revision		Revision as of 10:01, 27 July 2011
Line 1:		Line 1:
	{\|		<seo metakeywords="itil basic, basic itil" metadescription="Basic Ideas behind ITIL. The two illustrations below highlight the main issues ITIL seeks to address: ..." />
	~~! align~~="~~right~~" ~~width~~="~~80%~~"\|		<imagemap>
	~~! style="background~~:~~#DDDDDD;" align="~~right~~" width="20%"~~\| [https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken diese Seite auf Deutsch]		Image:ITIL-Wiki-deutsch.jpg\|right\|Basic Ideas behind ITIL
	\|}		default [https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken diese Seite auf Deutsch]
			desc none
			</imagemap>
			<br style="clear:both;"/>

	The two illustrations below highlight the main issues ITIL seeks to address:		The two illustrations below highlight the main issues ITIL seeks to address:


	==Traditional Setup of the IT Organisation==		==Traditional Setup of the IT Organisation==
Line 23:		Line 27:
	The activities in Application Development and IT Operations are now co-ordinated and all the communication with the clients is directed via one central channel.		The activities in Application Development and IT Operations are now co-ordinated and all the communication with the clients is directed via one central channel.
	<br style="clear:both;"/>		<br style="clear:both;"/>



			<!-- This page is assigned to the following categories: -->
			[[Category:IT Infrastructure Library ITIL]]
			<!-- --- -->

Andrea at 13:20, 2 November 2007

2007-11-02T13:20:44Z

New page

{|
! align="right" width="80%"|
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/ITIL-Leitgedanken diese Seite auf Deutsch]
|}

The two illustrations below highlight the main issues ITIL seeks to address:

==Traditional Setup of the IT Organisation==

[[Image:traditional_setup_it_organisation.jpg|frame|right|Traditional Setup of the IT Organisation]]
Traditionally, there are two separate channels for the communication between the IT organisation and the client: Agreements concerning new applications or those to be altered are concluded between client and Application Development, whilst issues concerning operations are subsequently settled with the production personnel.

This approach involves two decisive risks:
* Operational requirements, ensuring the error-free running of an application, are insufficiently considered during the development phase.
* IT Operations is not fully able to control the release of applications into the productive environment; this might cause unforeseen side effects.
<br style="clear:both;"/>

==Setup of the IT Organisation according to ITIL==

[[Image:setup_it_organisation_itil.jpg|frame|right|Setup of the IT Organisation according to ITIL]]
An [[ITIL Implementation|implementation method based on ITIL]] has to resolve these particular problems by placing IT Service Management after Application Management and ICT Infrastructure Management: Thus, IT Service Management mediates between development and production on the side of the IT organisation, and the client on the business-side.

The activities in Application Development and IT Operations are now co-ordinated and all the communication with the clients is directed via one central channel.
<br style="clear:both;"/>