DS9  Manage the Configuration
Control over the IT process of ...
managing the configuration
    with the business goal
    of accounting for all IT components, prevent unauthorised alteration, verify physical existence and provide a basis for sound change management
     
      is enabled by
      • controls which identify and record all IT assets and their physical location, and a regular verification programme which confirms their existence

        and takes consideration

        • Critical Success Factors that leverage
        • specific IT Resources and is measured by
        • Key Performance Indicators

Record of Assessment
Assignment ID:  * Enter Name: *
Reference Code:  * Enter Location: * Tel. Num: *
Enter Full e-mail Address: *
  Control Objective:

Manage the configuration. 
CRITICAL SUCCESS FACTORS
Selected
Status
Description
*
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
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
*
*
*
*
*
*
*
*
*
*
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
*
*
*
*
*
*
*
*
  Conclusions:
* Non-existent 
Management does not have an appreciation of the benefits of having a process in place that is capable of reporting on and managing the IT infrastructure, for either hardware or software configurations.
* Optimised 
All infrastructure components are managed within the configuration management system, which contains all necessary information about components and their interrelationships. The configuration data is aligned with vendor catalogues. Interrelated processes are fully integrated and use as well as update configuration data. Baseline audit reports provide essential hardware and software data for repair, service, warranty, upgrade and technical assessments of each individual unit. Authorised software installation rules are enforced. Management forecasts repairs and upgrades from analysis reports providing scheduled upgrades and technology refreshment capabilities. Asset tracking and monitoring of individual workstations protects assets and prevents theft, misuse and abuse.
* Managed and Measurable 
The need to manage the configuration is recognised at all levels of the organisation and best practices continue to evolve. Procedures and standards are communicated and incorporated into training and deviations are monitored, tracked and reported. Automated tools are utilised, such as 'push' technology, to enforce standards and improve stability. Configuration management systems do cover most of the IT infrastructure and allow for proper release management and distribution control. Exception analysis, as well as physical verifications, are consistently applied and their root causes are investigated.
* Defined Process 
The need for accurate and complete configuration information is understood and enforced. The procedures and working practices have been documented, standardised and communicated, but training and application of the standards is up to the individual. In addition, similar configuration management tools are being implemented across platforms. Deviations from procedures are unlikely to be detected and physical verifications are performed inconsistently. Some automation occurs to assist in tracking equipment and software changes. Configuration data is being used by interrelated processes.
* Repeatable but Intuitive 
Management is aware of the benefits of controlling the IT configuration but there is implicit reliance on technical personnel knowledge and expertise. Configuration management tools are being employed to a certain degree, but differ among platforms. Moreover, no standard working practices have been defined. Configuration data content is limited and not used by interrelated processes, such as change management and problem management.  
* Initial / Adhoc 
The need for configuration management is recognised. Basic configuration management tasks, such as maintaining inventories of hardware and software, are performed on an individual basis. No standard practices are applied.
Settings will expire on: 

(Do NOT edit.) Field set by Form.
Save and E-mail this form. (Saves only "*" fields & sends E-mail to address above):


Maintenance Functions

Note: If using Netscape on a Macintosh you may have to submit twice, the first will fail, or you can push the "Save Changes and/or Set New Expiration" then Submit.