Editing Configuration management (section)

==Overview==
CM is the practice of handling changes systematically so that a [[system]] maintains its [[system integrity|integrity]] over time. CM implements the policies, procedures, techniques, and tools that manage, evaluate proposed changes, track the status of changes, and maintain an inventory of system and support documents as the system changes. CM programs and plans provide technical and administrative direction to the development and implementation of the procedures, functions, services, tools, processes, and resources required to successfully develop and support a complex system. During system development, CM allows [[program management]] to track requirements throughout the life-cycle through acceptance and operations and maintenance. As changes inevitably occur in the requirements and design, they must be approved and documented, creating an accurate record of the system status. Ideally the CM process is applied throughout the [[system lifecycle]]. Most professionals mix up or get confused with [[Asset management]] (AM, see also [[ISO/IEC 19770]]), where it inventories the assets on hand. The key difference between CM and AM is that the former does not manage the financial accounting aspect but on service that the system supports or in other words, that the later (AM) is trying to realize value from an IT asset.<ref>{{cite web|last=Atlassian|title=Guide to configuration management databases (CMDBs)|url=https://www.atlassian.com/itsm/it-asset-management/cmdb|access-date=2021-07-20|website=Atlassian|language=en}}</ref><ref>{{Cite journal|last=Galusha|first=C.|date=June 2001|title=Getting started with IT asset management|url=https://ieeexplore.ieee.org/document/939973|journal=IT Professional|volume=3|issue=3|pages=37–40|doi=10.1109/6294.939973|url-access=subscription}}</ref><ref>{{cite web|date=2018-01-30|title=The ISO 19770-1 standard: A guide to implementing IT asset management|url=https://blog.shi.com/business-of-it/iso-19770-1-standard-guide-implementing-asset-management/|access-date=2021-07-20|website=The SHI Hub|language=en-US}}</ref>

The CM process for both hardware- and software-configuration items comprises five distinct disciplines as established in the MIL–HDBK–61A<ref>{{cite web|url=http://www.product-lifecycle-management.com/download/MIL-HDBK-61B%20%28Draft%29.pdf|title=Military Handbook: Configuration Management Guidance|publisher=Department of Defense: United States of America|page=iii–iv|access-date=2016-07-21|quote=4. CM LIFE CYCLE MANAGEMENT AND PLANNING [...] 5. CONFIGURATION IDENTIFICATION [...] 6. CONFIGURATION CONTROL [...] 7. CONFIGURATION STATUS ACCOUNTING [...] 8. CONFIGURATION VERIFICATION AND AUDIT [...] 9. DATA MANAGEMENT [...]}}</ref> and in ANSI/EIA-649. Members of an organization interested in applying a standard [[change management|change-management]] process will employ these disciplines as policies and procedures for establishing [[Baseline (configuration management)|baselines]], manage and control change, and monitor and assess the effectiveness and correctness of progress. The [[IEEE 12207]] process IEEE 12207.2 also has these activities and adds "Release management and delivery".
{{anchor|Configuration identification}}
{{anchor|Configuration Status Accounting}}
The five disciplines are:

# CM Planning and Management: a formal document and plan to guide the CM program that includes items such as:
#* Personnel
#* Responsibilities and resources
#* Training requirements
#* Administrative meeting guidelines, including a definition of procedures and tools
#* Baselining processes
#* Configuration control and configuration-status accounting
#* Naming conventions
#* Audits and reviews
#* Subcontractor/vendor CM requirements
# Configuration Identification (CI): consists of setting and maintaining baselines, which define the system or subsystem architecture, components, and any developments at any point in time. It is the basis by which changes to any part of a system are identified, documented, and later tracked through design, development, testing, and final delivery. CI incrementally establishes and maintains the definitive current basis for Configuration Status Accounting (CSA) of a system and its [[configuration item]]s (CIs) throughout their lifecycle (development, production, deployment, and operational support) until disposal.
# Configuration Control: includes the evaluation of all change-requests and change-proposals, and their subsequent approval or disapproval. It covers the process of controlling modifications to the system's design, hardware, firmware, software, and documentation.
# Configuration Status Accounting: includes the process of recording and reporting configuration item descriptions (e.g., hardware, software, firmware, etc.) and all departures from the baseline during design and production. In the event of suspected problems, the verification of baseline configuration and approved modifications can be quickly determined.
# Configuration Verification and Audit: an independent review of hardware and software for the purpose of assessing compliance with established performance requirements, commercial and appropriate military standards, and functional, allocated, and product baselines. Configuration audits verify that the system and subsystem configuration documentation complies with the functional and physical performance characteristics before acceptance into an architectural baseline.