| Revision as of 19:34, 9 October 2008 editKimchojhang (talk | contribs)45 edits →ITIL Exam← Previous edit | Revision as of 19:36, 9 October 2008 edit undoHipal (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers137,861 edits rv to last by Charles T. Betz - please discuss - hard to tell what Kimchojhang is trying to do other than promote trainingNext edit → | ||
| Line 1: | Line 1: | ||
| {{Advert|date=December 2007}} | |||
| ] (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. | |||
| {{merge|ITIL|Talk:ITIL_v3#Merge?|date=August 2007}} | |||
| The ] (ITIL) is a customizable framework of good practices designed to promote quality computing services in the information technology (IT) sector. As an ] (ITSM) framework, ITIL provides a systematic approach to the provisioning and management of IT services, from inception through '''design, implementation, operation and continual improvement'''.'''The processes identified and described within ITIL are supplier and platform independent and apply to all aspects of IT infrastructure. Since the mid 1990s, ITIL has been generally considered a de facto international ] for ].<ref>Van Bon, Jan: "The Guide to IT Service Management, Vol. I", page 131. Addison-Wesley, 2002</ref> | |||
| '''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. | |||
| ⚫ | The names ''ITIL'' and ''IT Infrastructure Library'' are ] of the ] (OGC), which is an Office of the ]'s ]. The content of the books is protected by ]. | ||
| '''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 |
||
| As part of the overall OGC suite of publications, ITIL does not provide guidance or best practices on project or program management. It does, however, recognize that they are key to a successful ITIL implementation. | |||
| == 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. |
||
| ⚫ | *'''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. |
||
| ⚫ | *'''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. |
||
| ⚫ | *'''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: |
||
| ⚫ | ** Informational events -- which are logged |
||
| ⚫ | ** Warning events -- also called alerts, where an event exceeds a specified threshold |
||
| ⚫ | ** Critical events -- which typically will lead to the generation of Incidents |
||
| ⚫ | *'''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. |
||
| ITIL has recently undergone a refresh, and this page presents information about the newly published version 3 (ITIL v3), the core books for which were published on 30 June 2007. The major difference between v3 and its predecessor ], is that v3 has adopted an integrated service lifecycle approach to IT Service Management, as opposed to organising itself around the concepts of IT Service Delivery and Support. | |||
| == ITIL Credentials == | |||
| ] | |||
| The ITIL Foundation certification credential validates the skills needed to deliver customer-centric and cost-justified, IT services.<br /> | |||
| ] | |||
| Focuses on ITIL v3 policy Change and Release, Support and Restore, Agree and Define. Emphasizes continual strategy development.<br /> | |||
| ] | |||
| Focuses on the ability to plan and execute an ITIL implementation strategy as a Service Manager.<br /> | |||
| ==ITIL Service Management Practices ('ITIL v3')== | |||
| == ITIL Training == | |||
| {{main|Information Technology Infrastructure Library}} | |||
| EXIN certified ITIL v3 training is required to take the ITIL v3 Exams.<br /> | |||
| ⚫ | 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 Sharon Taylor, chief architect of the ITIL Refresh, and president of the Aspect Group. | ||
| EXIN certified training is usually 24 hours or 3 days of training focused on case studies.<br /> | |||
| A key change to ITIL under version 3 has been a repositioning of the framework from the previous emphasis on process lifecycle and alignment of IT to "the business", to the management of the lifecycle of the services provided by IT, and the importance of creating business value rather than just the execution of processes. Consequently, it was rebranded ITIL Service Management Practices in order to represent service management 'best practice'. It is a publicly stated aim of the refresh to include more reference to ]. | |||
| '''EXIN certified ITIL v3 Course:''' | |||
| ITIL® v2-to-v3 Foundation Bridge Exam Prep Boot Camp<br /> | |||
| ITIL® v2-to-v3 Service Manager Bridge Exam Prep Boot Camp<br /> | |||
| ITIL® v3 Foundation Exam Prep Boot Camp<br /> | |||
| ===Version 3 structure=== | |||
| == ITIL Exam == | |||
| ITIL v3 comprises a set of core texts supported by additional complementary and web based materials. While the version 2 volumes were only available in English, limiting their use in non-English speaking countries, the core titles in version 3 are being translated into other languages. Among the initial target languages are Portuguese, Spanish, Japanese, Hindi/Urdu, Arabic, Mandarin and Dutch. This initiative is being led by the ], with resources and support from OGC. | |||
| ] : ITIL® V3 Foundation<br /> | |||
| ] : ITIL® V3 Foundation Bridge<br /> | |||
| ] : ITIL® V3 Intermediate: Operational Support & Analysis<br /> | |||
| ] :ITIL® V3 Intermediate: Release, Control & Validation<br /> | |||
| ] :ITIL® V3 Intermediate: Service Operation<br /> | |||
| ] :ITIL® V3 Intermediate: Service Offerings & Agreements <br /> | |||
| ] :ITIL® V3 Intermediate: Service Transition<br /> | |||
| ] :ITIL® V3 Managers Bridge <br /> | |||
| * Proctored by EXIN Exams | |||
| ====ITIL v3 core volumes==== | |||
| == Note == | |||
| ⚫ | <!-- 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. | ||
| ⚫ | *'''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. | ||
| ⚫ | *'''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. | ||
| ⚫ | *'''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: | ||
| ⚫ | ** Informational events -- which are logged | ||
| ⚫ | ** Warning events -- also called alerts, where an event exceeds a specified threshold | ||
| ⚫ | ** Critical events -- which typically will lead to the generation of Incidents | ||
| ⚫ | *'''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. | ||
| '''"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 ]. | 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 ]. | ||
| Some people may find the language ITIL uses to be obtuse. | |||
| For example below is a quote for the Service Delivery Section of the Foundation course. | |||
| SERVICE AVAILABILITY: involves all aspects of service availability and unavailability, and the impact of component availability, or the potential impact of component availability on service availability. | |||
| ==References== | ==References== | ||
| <references/> | |||
| ⚫ | The names ''ITIL'' and ''IT Infrastructure Library'' |
||
| ==External links== | ==External links== | ||
| * | |||
| * | * | ||
| ] | ] | ||
| ] | ] | ||
| ] | |||
| ] | ] | ||
Revision as of 19:36, 9 October 2008
 | This article contains promotional content. Please help improve it by removing promotional language and inappropriate external links, and by adding encyclopedic text written from a neutral point of view. (December 2007) (Learn how and when to remove this message) |
 | It has been suggested that this article be merged with ITIL and Talk:ITIL_v3#Merge?. (Discuss) Proposed since August 2007. |
The Information Technology Infrastructure Library (ITIL) is a customizable framework of good practices designed to promote quality computing services in the information technology (IT) sector. As an IT Service Management (ITSM) framework, ITIL provides a systematic approach to the provisioning and management of IT services, from inception through design, implementation, operation and continual improvement.The processes identified and described within ITIL are supplier and platform independent and apply to all aspects of IT infrastructure. Since the mid 1990s, ITIL has been generally considered a de facto international standard for IT Service Management.
The names ITIL and IT Infrastructure Library are Registered Trade Marks of the Office of Government Commerce (OGC), which is an Office of the United Kingdom's Treasury. The content of the books is protected by Crown Copyright.
As part of the overall OGC suite of publications, ITIL does not provide guidance or best practices on project or program management. It does, however, recognize that they are key to a successful ITIL implementation.
ITIL has recently undergone a refresh, and this page presents information about the newly published version 3 (ITIL v3), the core books for which were published on 30 June 2007. The major difference between v3 and its predecessor v2, is that v3 has adopted an integrated service lifecycle approach to IT Service Management, as opposed to organising itself around the concepts of IT Service Delivery and Support.
ITIL Service Management Practices ('ITIL v3')
Main article: Information Technology Infrastructure LibraryIn December 2005, the OGC issued notice of an ITIL refresh, 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 30 May 2007. The ITIL Refresh project is being led by Sharon Taylor, chief architect of the ITIL Refresh, and president of the Aspect Group.
A key change to ITIL under version 3 has been a repositioning of the framework from the previous emphasis on process lifecycle and alignment of IT to "the business", to the management of the lifecycle of the services provided by IT, and the importance of creating business value rather than just the execution of processes. Consequently, it was rebranded ITIL Service Management Practices in order to represent service management 'best practice'. It is a publicly stated aim of the refresh to include more reference to ROI.
Version 3 structure
ITIL v3 comprises a set of core texts supported by additional complementary and web based materials. While the version 2 volumes were only available in English, limiting their use in non-English speaking countries, the core titles in version 3 are being translated into other languages. Among the initial target languages are Portuguese, Spanish, Japanese, Hindi/Urdu, Arabic, Mandarin and Dutch. This initiative is being led by the IT Service Management Forum, with resources and support from OGC.
ITIL v3 core volumes
- 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.
- 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.
- 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.
- 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:
- Informational events -- which are logged
- Warning events -- also called alerts, where an event exceeds a specified threshold
- Critical events -- which typically will lead to the generation of Incidents
- Continual Service Improvement focuses on the ability to deliver continual improvement 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.
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 availability.
Some people may find the language ITIL uses to be obtuse. For example below is a quote for the Service Delivery Section of the Foundation course.
SERVICE AVAILABILITY: involves all aspects of service availability and unavailability, and the impact of component availability, or the potential impact of component availability on service availability.
References
- Van Bon, Jan: "The Guide to IT Service Management, Vol. I", page 131. Addison-Wesley, 2002
- Office of Government Commerce. ITIL Refresh Statement