
During system development, CM allows program management to track requirements throughout the life-cycle through acceptance and operations and maintenance. 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. 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. Some treat CM as being similar to a librarian activity, and break out change control or change management as a separate or stand alone discipline.ĬM is the practice of handling changes systematically so that a system maintains its integrity over time. Many of these functions and models have redefined CM from its traditional holistic approach to technical management.

#Cs1 6 Pro Config iso
Now widely adopted by numerous organizations and agencies, the CM discipline's concepts include systems engineering (SE), Integrated Logistics Support (ILS), Capability Maturity Model Integration (CMMI), ISO 9000, Prince2 project management method, COBIT, ITIL, product lifecycle management, and Application Lifecycle Management.

This marked the beginning of what has now evolved into the most widely distributed and accepted standard on CM, ANSI–EIA–649–1998. In 1991, the "480 series" was consolidated into a single standard known as the MIL–STD–973 that was then replaced by MIL–HDBK–61 pursuant to a general DoD goal that reduced the number of military standards in favor of industry technical standards supported by standards developing organizations (SDO).
#Cs1 6 Pro Config series
The CM process became its own technical discipline sometime in the late 1960s when the DoD developed a series of military standards called the "480 series" (i.e., MIL-STD-480, MIL-STD-481 and MIL-STD-483) that were subsequently issued in the 1970s. This reverse engineering process is wasteful in terms of human and other resources and can be minimized or eliminated using CM.Ĭonfiguration Management originated in the United States Department of Defense in the 1950s as a technical management discipline for hardware material items-and it is now a standard practice in virtually every industry. For this reason, engineers, contractors, and management are frequently forced to develop documentation reflecting the actual status of the item before they can proceed with a change. In many cases, without CM, the documentation exists but is not consistent with the item itself. Ī structured CM program ensures that documentation (e.g., requirements, design, test, and acceptance documentation) for items is accurate and consistent with the actual physical design of the item. A complete CM program includes provisions for the storing, tracking, and updating of all system information on a component, subsystem, and system basis. CM verifies that changes are carried out as prescribed and that documentation of items and systems reflects their true configuration. Changes to the system are proposed, evaluated, and implemented using a standardized, systematic approach that ensures consistency, and proposed changes are evaluated in terms of their anticipated impact on the entire system. It helps to verify that proposed changes are systematically considered to minimize adverse effects.


The lack of CM, or its ineffectual implementation, can be very expensive and sometimes can have such catastrophic consequences such as failure of equipment or loss of life.ĬM emphasizes the functional relation between parts, subsystems, and systems for effectively controlling system change. The relatively minimal cost of implementing CM is returned manyfold in cost avoidance. The CM process facilitates orderly management of system information and system changes for such beneficial purposes as to revise capability improve performance, reliability, or maintainability extend life reduce cost reduce risk and liability or correct defects. CM verifies that a system performs as intended, and is identified and documented in sufficient detail to support its projected life cycle. 5.1 Operating system configuration managementĬM applied over the life cycle of a system provides visibility and control of its performance, functional, and physical attributes.
