Misplaced Pages

ITIL v3: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 19:20, 9 October 2008 editKimchojhang (talk | contribs)45 editsNo edit summary← Previous edit Latest revision as of 22:21, 4 July 2022 edit undoLe Deluge (talk | contribs)Extended confirmed users, Pending changes reviewers85,527 editsm Update section linkTag: Redirect target changed 
(45 intermediate revisions by 30 users not shown)
Line 1: Line 1:
#REDIRECT ]
] (IT Infrastructure Library v3): ITIL v3 defines a process with an agnostic platform and holistic framework for changing product development processes into to a service development processes. This is particularly important in SaaS environments such Help Desks. IT infrastructure developers use this framework to align products, services or application with the needs of customers thus proactively changing the product or service production environment.
{{R from merge}}

'''What is the Noteworthy difference between ITIL v2 and ITIL v3'''
ITIL v3 focuses on on continual and collaborative development as opposed ITIL v2 which only focused on implementing processes. ITIL v3 establishes the framework for the developement of a continual or "living" design for an IT infrastructure strategy.

'''How ITIL v3 Developed'''
In December 2005, the OGC issued notice of an ITIL refresh,<ref>''Office of Government Commerce''. </ref> commonly known as ''Information Technology Infrastructure Library v3'' (''ITIL v3''). The project culminated in the publication of five new core texts and a web based glossary on ] ]. The ITIL Refresh project is being led by ], chief architect of the ], and president of the ].

== Five New Core Texts ==
'''ITIL v3 Core Volumes:'''
<!-- RHaworth strongly recommends that descriptions of these volumes should be within this article; not separate articles -->
*'''Service Strategy''' focuses on the identification of market opportunities for which services could be developed in order to meet a requirement on the part of internal or external customers. The output is a strategy for the design, implementation, maintenance and continual improvement of the service as an organizational capability and a strategic asset. Key areas of this volume are Service Portfolio Management and Financial Management.<br />
*'''Service Design''' focuses on the activities that take place in order to develop the strategy into a design document which addresses all aspects of the proposed service, as well as the processes intended to support it. Key areas of this volume are Availability Management, Capacity Management, Continuity Management and Security Management.<br />
*'''Service Transition''' focuses on the implementation of the output of the service design activities and the creation of a production service or modification of an existing service. There is an area of overlap between Service Transition and Service Operation. Key areas of this volume are Change Management, Release Management, Configuration Management and Service Knowledge Management.<br />
*'''Service Operation''' focuses on the activities required to operate the services and maintain their functionality as defined in the Service Level Agreements with the customers. Key areas of this volume are Incident Management, Problem Management and Request Fulfillment. A new process added to this area is Event Management, which is concerned with normal and exception condition events. Events have been defined into three categories:<br />
** Informational events -- which are logged<br />
** Warning events -- also called alerts, where an event exceeds a specified threshold<br />
** Critical events -- which typically will lead to the generation of Incidents<br />
*'''Continual Service Improvement''' focuses on the ability to deliver ] to the quality of the services that the IT organization delivers to the business. Key areas of this volume are Service Reporting, Service Measurement and Service Level Management.<br />

== Note ==

'''"Continual" as opposed to ITIL v2's references to "Continuous" service'''
ITIL v3 uses the word "continual" as opposed to ITIL v2's references to "continuous" service improvement (CSIP). Continual implies an activity that is undertaken on a phased, regular basis as part of a process. Continuous is more suitable for the definition of activities intended to operate without pause, such as the ultimate goal of ].

==References==
The names ''ITIL'' and ''IT Infrastructure Library'': trademark and copy right of the ] (OGC), which is an Office of the ]'s ]

==External links==
*

]
]

]

Latest revision as of 22:21, 4 July 2022

Redirect to:

  • From a merge: This is a redirect from a page that was merged into another page. This redirect was kept in order to preserve the edit history of this page after its content was merged into the content of the target page. Please do not remove the tag that generates this text (unless the need to recreate content on this page has been demonstrated) or delete this page.