Change management

 

 Back

 

Changes in the infrastruture of an organisation occur regularly. Change management is geared towards ensuring that changes within company processes are kept under control. A change can be renewing or improving company processes, changing existing objects or correcting a (structural) error. The Change management module helps you to carry through changes via phases and activities. You can make this change route as simple or extensive as you wish.

 


Request for change

A request for change can arrive for instance as a result of an incident in Incident management or a problem recorded in Problem management. The Change management module fits perfectly together with these other ITIL modules.

For every change you need to appoint a manager to carry it through. You can also indicate a duration for the change. In addition you can determine which incidents, branches, objects, etc. should be involved in the change. Finally you can choose a route for the change. 

Change route

The route of the change process is divided up into a number of steps or phases including preparation, current change and change under review. Within this route activities are scheduled to be carried out by operators. The operator is the person responsible for carrying out each component of the change in a practical sense. The change route can be filled in according to your own insight and requirements.



Advantages

  • The Change management module follows the ITIL process flow 
  • The Change route can be filled in according to your own insight and requirements, with or without using a template
  • Each change can be divided up into phases, within which activities are planned
  • Distinguish between managers and operators with extensive authorisation management system
  • Plan change meetings with guests
  • Link changes to a release in Release management
  • Works well together with other modules

Templates and authorisation management

By using templates for changes you can ensure that standard changes are carried out according to a fixed procedure. The risk of missing a vital step during this process will then be very low. An extensive authorisation management is present within the Change management module, whereby it is possible to organise the authorisation in detail for large and consequential changes. It is also possible to run through simpler change routes, by planning fewer phases and activities.


Dependencies between activities

In order for the process flow of a change to run more structurally, dependencies between different activities within a phase can be created. These dependencies ensure that the starting up of and completion of activities are attuned to each other. 

Integration

Configuration management and Release management are integrated within the Change management module. This means that configuration items (objects) can be linked to changes. In addition it is also possible to link the planned final date of a change to the release of a new version of a software application for example.

 

 Back

print