|
Updating the
configuration
management database
|
The frequency of updates to the configuration management
database will depend on the volume of configuration changes
carried out at your particular school.
The important thing to remember is to update the database as
soon as possible following a change to ensure that the
database is as up to date as possible at all times. It may be
more convenient to gather requests for change and
incident/request forms into batches for processing, but this will
detract from the value of the data you are holding as it will often
be out of date.
|
|
Auditing and verifying
configuration items
|
Audit and verification can be time consuming and may
therefore be difficult to schedule in a busy environment.
However, it is an important part of the process, so allow time for
it.
In the early stages of implementation, auditing will need to be
more frequent until participants in the process become familiar
with it and the tasks become automatic. We recommend that
you carry out an audit at the end of the first couple of months
after implementation to ensure that there are no issues with the
process.
Once the process has become automatic, audits may be less
frequent - but this will depend on the individual circumstances of
the school and what other factors you may need to consider.
For example, new staff may have been trained in the process
recently or a new supplier may be involved.
|
|
Monitoring the
Configuration
Management process
|
The configuration management audit report should be
produced after every audit. Regularity is less important than the
ability to monitor progress since the previous audit.
|
|
Making decisions
|
Reports should be reviewed as frequently as they are issued
and trends identified as they appear. Actual causes of trends
will be easier to identify if the data is recent.
|
|
|
|
|
|
