This standard defines five CM functions and their underlying principles. The functions are detailed in

Section 5

. The principles, highlighted in text boxes, are designed to individually identify the essence of the related CM function and can be used to collectively create a checklist of "best practice" criteria to evaluate a CM program.

The CM principles defined in this standard apply equally to internally focused enterprise information, processes, and supporting systems (i.e., Enterprise CM - policy driven, supporting the internal goals needed to achieve an efficient, effective and lean enterprise), as well as to the working relationships supported by the enterprise (i.e., Acquirer/Supplier CM - contracted relationship to support external trusted interaction with suppliers).

In an Enterprise CM context there are several methodologies for principle use by the enterprise:

The principles of this standard provide direction for developing enterprise or functional CM plans focused on identifying, defining, authorizing, and managing CM activities.

These plans identify the participants involved in activities, their responsibilities, their authority, and how accountability is administered to serve enterprise/activity objectives.

The Enterprise uses CM's integrity-based traceability and management capabilities as a foundation to support the "best practice" initiatives of data/information management, quality assurance, program/project management, systems engineering and life cycle logistics, by providing principle-guided functions to achieve a more efficient, effective and lean enterprise.

In the Acquirer/Supplier CM context there are several methodologies for conformance by a supplier:

Acquirer requires a CM plan consistent with the principles of this standard from the supplier.

Acquirer uses this standard to develop a checklist with which to evaluate supplier CM plans.

Acquirer reviews and approves the supplier CM plan and makes it a requirement of the contract. This method requires both parties to the acquisition to understand both the concepts and the tailoring.

Acquirer uses the principles of this standard as the basis for developing either or both an enterprise CM requirements document or a specific project CM requirements document to impose on suppliers. The requirements documents may state this standard's principles as requirements and reference this standard's paragraphs. Compliance with the contractual requirements constitutes conformance with this standard.

In describing each CM function and its principles, this standard utilizes neutral Configuration Management terminology, while also providing equivalent terms, that have historically been used in various product environments (see

Table 2

). There is no intent to express a preference for any particular set of terminology.

Similarly, this standard uses a neutral set of names for the phases of a product's life cycle, which are generic enough to be easily mapped to the myriad of different life cycle models in use.

Table 1 illustrates some of the aliases for each phase name and identifies characteristics that apply to each one.

Regardless of the titles chosen for these phases, or what the product is (i.e., a facility, software, an airplane or a machine screw), at some point in its history a product will go through all or most of these phases. The phases can have considerable overlap, or the sequence of the phases might change or be repeated, e.g., for product improvements and enhancements. Approved configurations of a product can be in the build, distribution, operation, and disposal phases simultaneously, and changes to those configurations may occur during all life cycle phases.

Appropriate application of CM functions enables a user of this standard to plan and implement a CM program for a product, project, or enterprise. All functions apply during every phase of the product's life cycle but the degree to which each of the CM principles applies may vary. A scalable CM process should be defined, measured, continuously improved, and adhered to, that is commensurate with the product's complexity, its intended use, and its value over the product life cycle.

An organization that has the responsibility for performing Configuration Management for a product during any period of its life cycle could be a commercial enterprise, e.g., contractor, subcontractor, supplier, or government agency. References in this standard to the acquirer (i.e., customer) should be interpreted as the entity that specifies requirements (functional and performance attributes) for the product or that acquires and uses the product. An acquirer may be external to the developing and producing organization or may be internal such as marketing, management, or the using department.

Configuration Management functions related to a product may be the responsibility of several organizations during its life cycle. For example, an organization with the responsibility to design and build a product will perform Configuration Management during the definition and build phases; other organizations or government activities with responsibility for upgrading the product and servicing units will perform Configuration Management during the operation phase.

GEIA-HB-649 "Configuration Management Standard Implementation Guide," provides additional "how to" guidance for planning, managing, and implementing CM functions and principles.