Configuration management works by identifying configuration items and their inter-
relationships, recording them and keeping them up to date. The Configuration
Management process flowchart illustrates this.
|
|
|
|
|
The configuration management database (CMDB) is where all information on
configuration items is stored. The data is made up of configuration item records
and attributes of those records.
|
Configuration items
|
Configuration items are the different components of the
infrastructure that make up the whole, including associated
items such as documentation, manuals, procedures and
licences. Example Configuration Items can be found in the
toolkit.
It is possible to record configuration items at various levels of
detail. For example, you may choose to capture a large
amount of detail and decide to record each individual
computer base unit, monitor, keyboard, mouse, internal
modem and so on as separate configuration items. You
would do this if it were of importance to know where every
single component is.
Alternatively you may choose to record only computer base
units, as it can be assumed that the peripherals are bound to
be present. You could then limit your records about
peripherals to stock control only.
|
|
Attributes
|
In addition to the multitude of configuration items you will
record, each item has a set of attributes. An attribute is a
piece of information relating to the configuration item and
these attributes can be as many or as few as you wish.
Example attributes can be found in the toolkit.
|
When deciding at what level to record configuration items and how many attributes
to include, the key factors to take into account are maintainability and need.
|
Maintainability
|
The more detail you record, the more there is to keep up to date and
the more likely it is that it will become out of date.
|
|
Need
|
Record only what you need to know. Don't keep records for the sake
of them. If you know that there is a computer base unit in a
classroom, you know that it must have a keyboard, monitor and
mouse. It is only if you have specialist peripherals that you may need
to record more information.
Record only what is individual to each configuration item. If you have
a maintenance contract for all your hardware, the supplier's contact
details will be the same for every item so consider keeping that
information centrally elsewhere.
|
Holding this information all together in a central database enables a number of
different interfaces to be created - for example:
- a call logging screen for recording incidents against configuration items
- a request for change screen for raising requests for change against
configuration items.
This creates a powerful information tool.
|
|
|
Relationship with
Change
Management
|
Change Management is the process for managing the
implementation of changes to the ICT infrastructure including
hardware, software, services or related documentation. It can be
used to help maintain the configuration management database as
the final step in the request for change cycle is to update the
configuration management database following a change.
Change Management is the subject of a separate FITS section.
|
|
Relationship with
Incident
Management
|
Incident Management is the process for handling all user incidents,
including equipment faults, and all requests, including those for new
equipment. It can be used to help maintain the configuration
management database, as the final step in the incident/request
process is to update the configuration management database
following a change.
Incident Management is the subject of a separate FITS section.
|
|
Relationship with
stock control
|
Either the Change Management process or the Incident
Management process should capture most inputs to the configuration
management database.
The only occasion when there may not be a request for change or an
incident/request form may be the procurement of stock items not
initiated by an incident, request or change. It is important that the
goods-in process feeds into configuration management immediately
on receipt, so that new equipment is traceable before it is assigned
to a location or user.
Stock control is discussed in more detail in the implementation guide
for Configuration Management.
|
|
|
|
|
|
