Home » What is ITIL V3? » Recent Articles:

ITIL BACKGROUND & HISTORY

October 30, 2009 What is ITIL V3? 1 Comment

ITIL Logo

The Information Technology Infrastructure Library (ITIL) provides a systematic approach to the provision and management of IT services, from inception through design, implementation, operation, and continual improvement.

 ITIL was developed by the United Kingdom’s Office of Government Commerce (OGC) in the late 1980s, and its original goal was to help improve IT Service Management in the UK central government.  ITIL was not widely adopted until the mid-1990s.   

 Where possible, the OGC defined processes that are found in an IT service organization.  Because of the broad scope covered by ITIL, it is a useful guide for setting up new service improvement objectives for all functions within the IT organization.

 In June of 2007, ITIL was expanded and reorganized as an IT service management Lifecycle, known as ITIL Version 3 (ITIL V3).  This new version covers the initial conception, development, transition, operations, and improvement of a service.  ITIL V3 views the activity of managing service as a Lifecycle, which is a shift in focus from the individualized process/function view of the previous version. 

ITIL serves as a source of good practice standards in IT Service Management (ITSM).  It is used as a reference by organizations worldwide for managing and improving IT services. 

ITIL defines service management as “a set of specialized organizational capabilities for providing value to customers in the form of services.  The capabilities take the form of functions and processes that are used to manage services over their Lifecycle.” [i]

ITIL V3 Lifecycle and related material Copywrite by Office of Government Commerce, Norwich, UK, 2007

Our Sponsors

IT Support Services Comments

  • Bob Anderson: Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the ...
  • Bob Anderson: Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Compute...
  • Bob Anderson: Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you...
  • Bob Anderson: Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on...
  • Bob Anderson: Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, an...

ITIL V3 Application Support Q & A

If you have any question on the blog content or have some specific question on how ITSM & ITIL can dramatically improve performance and reduce the cost of your Application Support service "Ask Bob"
Question :
Answer :
Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Computer World on "How to create Meaningful IT Support SLA's"  use this link...
Question :
Answer :
Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the folks who developed the original CMM  were not really initially inter...
Question :
Answer :
Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you want to be "proactive" in stopping this practice" you must capture bu...
Question :
Answer :
Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, and how many technical support calls from users you get and the average...
Question :
Answer :
Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on their own without any instruction to do so and it affects other user...