DS09 Configuration Management

1. Description

Identify and record all IT assets, their physical location, interdependencies and reliability history, and a regular verification programme which confirms their existence.

2. Service Activities

Configuration Guidelines: Procedures should be maintained to keep track of changes to the configuration (new item, status change from development to prototype).
Configuration Recording: Logging and control should be an integrated part of the configuration recording system including reviews of changed records.
Configuration Control: Periodically check the existence and consistency of recording of the configuration database.
Software Storage: A file storage area (library) should be defined and maintained for all valid software items in appropriate phases of the system development life cycle.

3. Key Goal Indicators

Percent of IT configuration identified and accounted for
Reduction in number of variances between accounts and physical situation
Quality index of information, including interrelationships, age, changes applied, status and related problems criteria
Usage index of information for proactive actions, including preventive maintenance and upgrade criteria

ebc Service Commitments

Development and implementation of a documented and trackable service in corporate office for all four ministries desktops and related assets
development and implementation of the ITIL configuration management process, with effective measurements to align with asset management initiative in BMS

4. Key Performance Indicators

Percent of configuration components for which data is kept and updated automatically
Frequency of physical verifications
Frequency of exception analysis, addressing redundancy, obsolescence and correction of configuration
Time lag between modification to the configuration and the update of records
Number of releases
Percent of reactionary changes

ebc Service Commitments

5. Critical Success Factors

Owners are established for all configuration elements and are responsible for maintaining the inventory and controlling change
Configuration information is maintained and accessible, based on up-to-date inventories and a comprehensive naming convention
An appropriate software library structure is in place, addressing the needs of development, testing and production environments
There exists a release management policy and a system to enforce it
Record keeping and physical custody duties are kept segregated
There is integration with procurement and change management processes
Vendor catalogues and configuration are aligned
Configuration baselines exist, identifying the minimum standard components and integration requirements, consistency and integration criteria
An automatic configuration detection and checking mechanism is available
An automatic distribution and upgrade process is implemented
There is zero tolerance for illegal software

6. Additional Information

Maturity Level Characteristics


0	1	2	3	4	5