General Comparison and Changes between ITIL V3 and ITIL V2

Most importantly, a detailed comparison between ITIL V3 and V2 reveals that all the main processes known from ITIL V2 are still there, with only few substantial changes. In many instances, however, ITIL V3 offers revised and enhanced process descriptions.

New ITIL Structure: The ITIL V3 Service Lifecycle

The main difference between ITIL V3 and V2 is the new ITIL V3 Service Lifecycle structure: ITIL V3 is best understood as seeking to implement feedback-loops by arranging processes in a circular way.

This means the old structure of Service Support and Service Delivery was replaced by a new one consisting of the five ITIL V3 core disciplines:

• Service Strategy determines which types of services should be offered to which customers or markets
• Service Design identifies service requirements and devises new service offerings as well as changes and improvements to existing ones
• Service Transition builds and deploys new or modified services
• Service Operation carries out operational tasks
• Continual Service Improvement Improvement learns from past successes and failures and continually improves the effectiveness and efficiency of services and processes.

ITIL V3 complements the processes known from ITIL V2 with a number of new processes and puts more emphasis on producing value for the business.

Modifications to Process Interfaces

Due to the new Service Lifecycle structure, all interfaces between the ITIL processes were changed in order to reflect the new ITIL V3 process structure; so even if processes in ITIL V3 and V2 are broadly identical, their interfaces have changed. Example: The Incident Management process must now link to the Service Design processes, although a comparison between Incident Management in ITIL V2 and V3 reveals that the process itself did not change substantially.

http://wiki.en.it-processmaps.com/index.php/Comparison_between_ITIL_V3_and_ITIL_V2_-_The_Main_Changes

ITIL - The CMDB - The central IT repository

The configuration management database (CMDB) is not a database in the technical sense but a
conceptual IT model, which is indispensable for efficient IT service management. All IT components and inventories are managed in the CMDB.

Configuration management exceeds asset management, often incorrectly used as a synonym, as it does not only document assets from a financial point of view, but captures information regarding the relationship between components, specifications or their location.

Thus IT support can quickly access information on the interdependence of IT services and the IT components (= configuration items = CIs) necessary for them.

According to ITIL, a CMDB must feature the following functionalities:
• manual and, where applicable, automatic recording and modification of configuration items
• description of the relationship and/or interdependence between CIs
• change of CI attributes (e.g. serial numbers)
• location and user management for CIs
• integration via the ITIL processes represented in the system

What has changed in ISO 9001:2008?

Here's a summary of the changes to ISO 9001 in 2008.

1. There are no new requirements in this version. This is significant, because a 'requirement' is something you must do.
2. All the changes are minor. They consist of changes of wording: clarifications and modifications to words or phrases and a few extra notes or examples (see below). Most are small additions or changes, with a few deletions.
   The intent is to make the meaning of a requirement clearer, to improve compatibility with ISO 14001 and/or assist translation to other languages.
3. The new version was published in mid-November 2008.
4. From that date, for a new certification you can choose certification to the 2000 or 2008 version.
5. After one year (from Nov 2008) all recertifications/new certifications will be to the 2008 version. Two years later, certifications to the 2000 version will no longer be valid.

Some examples of the changes, with clause numbers are:

4.2.1: modified to clarify that a single document can cover requirements for one or more procedures (eg, combine requirements for corrective action & preventive action into 1 procedure, or cover 'nonconformity' within another procedure rather than having a separate one)

6.4 Now clarifies what 'work environment' includes, and gives examples such as noise, temperature, humidity

8.2.1 Note added with some ideas on how customer satisfaction can be measured.

General advice: Get a copy of the new version, study the changes, and think about how (or if) the changes affect your system. Note, for example, the advice that you can address multiple requirements in a single procedure (we already have). Notice how the Standard has made it very clear that if you subcontract any part of your service or product out, this doesn't in any way remove or alter your responsibility to meet your customers' requirements.