Configuration Management Plan
Section 1 - Model Text

1. SCOPE

1.1 Identification.

This Configuration Management Plan (CMP) establishes the overall plan for the Configuration Management requirement for the System, subsystems, Computer Software Configuration Items (CSCIs) and Hardware Configuration Items (HWCIs) during total system life cycle * of the project. For CSCIs during the Engineering and manufacturing phase, the criteria identified in Software Development Plan (Overall) for the project will be observed.
The CMP meets the requirement, as requested by the SOW and System Specification(s) to the applicable Standards (for example, MIL-STD-973, DEF STAN 05-57, DO-178B, DEF STAN 00-31/1, ISO 12207, ISO 15288, and MIL-STD-498) to establish a Configuration Management Program Plan for the Project.
This CMP will support the Configuration Control Procedures and will be applicable to all acquisition authorities and prime suppliers through the latter to the First Level suppliers (sub-contractors) associated with the project.

1.2 Purpose.

The purpose of this document is to identify and describe the overall policies and methods for Configuration Management (CM) to be used during the system life cycle of the System/subsystem, CSCIs and HWCIs for the project, and will be updated progressively as the work proceeds and the necessity arises.
This will CMP establish and provide the basis for a uniform and concise Configuration Management practice for the system/subsystem, CSCIs and HWCIs during the total system life cycle of the project.
This CMP will be used in conjunction with the Systems Engineering Management Plan (SEMP) and the Technical Documentation Standard to meet the requirement for Engineering Management by the Project Management System for the system.
The primary intention of this CMP is to provide information on the Configuration Management policy and methods to be adopted and implemented for the project.

1.3 Document overview.

The Project/Programme Management System (PMS) requires the implementation of a Configuration Management Plan (CMP) that provides for overall technical and administrative direction and surveillance for the project during the total system life cycle.
Starting with the functional configuration identification defined and frozen at the beginning of the Engineering and Manufacturing Development phase, the configuration will be protected from uncoordinated and unauthorised change. This protection will be provided by Formal Configuration Management operated within the purchaser, his agent, and design authorised suppliers.
The following provides a summary of each section contained within this Configuration Management Plan.

Section 1 identifies, describes the purpose, introduces the objectives and summarises the contents of the document.
Section 2 lists the referenced documentation to which this document refers for further information.
Section 3 outlines and describes the Organizational structure for performing Project/Programme to Configuration Management.
Section 4 identifies the Baselines and the Configuration Items (CIs) comprising the Baselines.
Section 5 defines the policies and methods used to establish and control the Configuration Items identified in section 4 by the formally constituted Configuration Control Boards (CCBs).
Section 6 describes the plans for the application of configuration index, matrix and status accounting records and procedures.
Section 7 defines the proposed methods for control and monitoring of subcontractors and vendors.
Section 8 establishes the major milestones for implementation of configuration management, that is, establishment of the CCB, each of the Baselines, interface control agreements with supplier companies, configuration index, matrix and status accounting procedures.
Section 9 describes the integration of configuration management activities with other project and program/management activities.
Section 10 describes the plans for conducting/supporting the Functional and Physical Configuration Audits.
Section 11 identifies and outlines the Software Configuration Management Plan to be used during the Engineering and Manufacturing phase of the CSCIs.
Section 12 lists the abbreviations, acronyms, definitions used, and other non-mandatory information; together with the figures referenced within the document.

The project plans and organization structure for the Configuration Management and control and monitoring of the system/segment, CSCIs and HWCIs.
Figure 3 illustrates in general terms the flow of change information between the various organizations involved in the project.
This document is based on the requirement for Configuration Management Plan as identified in MIL-STD-973 or MIL-STD-483A prepared in accordance with the criteria identified therein.
The application of this CMP will be within the policy statement as follows:

The aim is to keep the number of configuration changes to a minimum, and in this connection, it must be borne in mind that technical or engineering feasibility are not in themselves sufficient grounds for change authorisation.
Improvements not required to meet requirements will be approved and authorised only if they can be justified on cost/effectiveness grounds.

The CMP is living document and as a result additions, deletions, and modifications will occur as it is utilised. It will be updated as additional configuration activities are defined as the work proceeds and the necessity arises. Therefore, to provide configuration identification this standard will be identified with an issue or version number and released via configuration control to the relevant authorities.

1.4 Relationship to other standards and plans.

This configuration management plan has been prepared in conformance to the requirements of the project management system. This plan shall be used in conjunction with the System Engineering Management plan, Data Management Plan, Risk Management Plan, and all the identified applicable specialty program plans identified.
This document provides a means of achieving the concept of minimum documentation as required by Engineering Management or Systems Engineering (MIL-STD-499 and applicable equivalent, i.e., ISO/IEC 15288, etc.) by identifying the necessary plans, reports and other pertinent data items.

Documents are now available in .pdf format: See PDFDOCUMENTS.

TO BUY “Software Configuration Management Plan - Template” FROM AMAZON CLICK HERE

The total number of visitors to this site since the 15^th of March 1998

LE FastCounter

Back to Home page MANAGING STANDARDS Home page

Back to CMP CMP overview