Configuration Management Plan

Configuration Management Plan is template to use for putting together a CM Plan.

Configuration Management, CM, is a process model established to maintain the consistency and integrity of a system or software product throughout it's lifecycle.

CM can be defined as the control of changes made to a product's hardware, software and documentation.

1-2 pages on the future of Configuration Management

How to attack the consolidation of data in the enterprise

• Identify all Configuration Data Sources
• Gather Reporting Requirements
• Identify Business Owners of Application and Server data
• Make CMDB Recommendation

12 Month Plan

• Consolidate CMDB Data Sources where feasible
• Develop CMDB Audit Processes
• Provide Real-time Data Reports from the CMDB
• Create on-going CMDB Process Improvement

Configuration Management Links

• Configuration Management
• CMDB Best Practices
• Configuration Management Plan
• CM Audit

A CMDB is a repository of all the metadata related to systems and software in an organization.

It holds information such as owner, version number, server names, dependency information and much more.

A key success factor in implementing a CMDB is the automation of the collection of the information and on-going updates to the database.

Change Management

Objective
The objective of the CM Plan is to ensure that the organization has adequate controls over all processes and project artifacts.
Scope
A CM Plan is required for all large system and software projects.
Process Description
Change Management - [Link to Change Management Documents] Release Management - [Link to Release Management Documents] CMDB - [Links to CMDB Documents]
Definition of Terms
Glossary of Definitions
CM Organization
Organizational Charts and Structures
CM Responsibility
Explanation of Responsibilities
CMDB
CMDB Data Model CMDB Relationship Diagram