What are the differences and contacts between the configuration management system and the overall change system?

1. Configuration Management System (CMS)

   A sub-system of the project management system. It consists of a series of formal written procedures that contain documents and tracking systems and understand the approval levels required for approval and control of changes.

   The Configuration Management System is a subsystem of the PMIS system. The system identifies the status of deliverables and provides guidance on recording changes. In project management, its functions are part of the overall change control process.

   1. Configuration object:

    The configuration objects are either deliverables or technical specifications of each process.

   2. Purpose of Configuration Management:

   <1> establish an advanced method to identify and propose changes to the established benchmark in a standardized manner, and evaluate the value and effectiveness of changes;

   <2> by analyzing the impact of various changes, it creates opportunities for continuous verification and improvement projects;

   <3> establish a mechanism for the project management team to communicate with stakeholders about the approval and rejection of changes in a standardized manner.

 3. Configuration Management Methods:

   <1> identifies and records the functional and physical features of products, achievements, services, or components;

   <2> control any changes to the above features;

   <3> record and report each change and actual application;

   <4> support review of products, results or components to ensure they meet requirements

    Note: identify the target and the means. The purpose and means of configuration management are a common test site, which is also prone to errors.

  4. configuration management steps:

   <1> Configuration recognition. Select and identify configuration items to define and verify product configurations, mark products and documents, manage changes, and understand responsibilities. (Equivalent to a named planning process)

   <2> Configuration status record. Includes the approved configuration identification list, configuration change request status, and approval change implementation status. (Equivalent to running process)

   <3> Configuration verification and audit. Make sure that all the functional requirements specified in the configuration file are met. (Equivalent to the monitoring process)

 

2. Change Control System (CCS)

    The change control system is a sub-system of the Configuration Management System.

    <1> A sub-system is usually used as a configuration management system.

    <2> overall change control is completed through the change control system.

    <3> a series of formal written procedures, including documents, tracking systems, and approval levels.

    <4> Any change request must be formally submitted.

    <5> the system focuses on changes to the performance benchmark, such as scope, progress, and cost.

    Detailed change control work process follows the Universal Formula

Iii. Differences between the Configuration Management System and the Change Control System 

    <1> the change control system is a sub-system of the configuration management system, including the relationship.

    <2> different objects:

       A. Target of the Configuration Management System: either deliverables or technical specifications of each process. Configuration Management focuses on technical specifications.

       B. Management Objects of the change control system: Project and product benchmark (change ). It can be the product features and performance (that is, the product scope), and can be a variety of detailed project work (that is, the project scope) to implement these features and functions ). The change control system focuses on benchmark changes.