|
Change and
Configuration Management have an interesting relationship! It is my
experience that these two processes (if not implemented well) can be
the total undoing of the other. Change and Configuration Management
can almost be regarded as symbiotic.
Change and
Configuration Management – really are an integral
part!
With current, accurate
and comprehensive information about all components in the
infrastructure the management of Change, in particular, is more
effective and efficient. Change Management can be (and for my mind –
should be) integrated with Configuration Management.
Change and
Configuration Management – as a
minimum
As a minimum it is
recommended that the logging and implementation of Changes be done
under the control of a comprehensive Configuration Management system
and that the impact assessment of Changes is done with the aid of
the Configuration Management system.
All Change requests
should therefore be entered in the Configuration Management Database
(CMDB) and the records updated as the Change request progresses
through to implementation.
Change and
Configuration Management – how this
works
The Configuration
Management system identifies relationships between an item that is
to be changed and any other components of the infrastructure, this
allows for the owners of these components to be involved in the
impact assessment process.
Whenever a Change is
made to the infrastructure, associated Configuration Management
records should be updated in the CMDB. Where possible, this is best
accomplished by use of integrated tools that update records
automatically as Changes are made.
THE ASSET MANAGEMENT TOOLKIT
Each item
included is of the highest quality, tailor made to cover a different
aspect and issue. It includes presentations, questionnaires,
guidelines, fact sheets.... and whole gamut of material specifically
put together to both introduce and take you through Asset
Management.
It comprises the
following components (click
here)
|