MIL-HDBK-61A: Scope

1.3.1 Government and Contractor Roles in the CM Process.

Both the Government and the contractor participate in the CM process. However, depending on the agencies involved in a particular “contracting “ arrangement, there are several other terms that may also be used. (See the list below.) In the context of this handbook, a Government activity engaged in design, development or production of hardware or software items is referred to as if it were a “contractor.”

	Alias Terms Used in:
Term Used in MIL-HDBK-61	Government to Commercial Environment	Government to Government Environment
Contractor	Contractor Design Activity Performing Activity	Design Activity Performing Activity
Government	Government Managing Activity Tasking Activity	Managing Activity Tasking Activity
Contract	Contract Purchase Order	Tasking Directive Memo of Agreement Military Interdepartmental Purchase Request (MIPR)

Since, the Government has ultimate responsibility for the performance and configuration of the systems and equipment it acquires and operates, the Government is always the configuration control authority for the top-level performance attributes, and for selected lower level performance and design attributes that it specifies and contracts for. A significant degree of authority for configuration control may be exercised by contractors during any or all phases of the life cycle, depending on such factors as type of acquisition, contractual requirements, and ownership of the data.

For a specific acquisition, configuration control authority means that the activity or organization exercising that authority controls the configuration of the product and determines what changes are to be installed or incorporated in that product. The configuration control authority to effect a product configuration change under a contract does not automatically mean that a change can be directed or made to a document for which another organization is the controlling design activity and has content responsibility. Each configuration document has a current document change authority (CDCA), i.e. an agency or activity or organizational entity that is responsible for the content of the document and is the only authority that can effect changes to the document. . An activity that uses a product and its documentation, but is not the CDCA, is referred to as an Application Activity (AA). An AA can only approve for use (adopt) the document, but cannot direct changes to it. These concepts become increasingly more important as DoD acquisition looks to the commercial industrial base, and it is central to the management of an automated information system concerning documentation used by different application activities. [Details: 6.1.1.1]

The CM process is applicable both to development of new systems and items and to modifications of existing systems and items. A typical distribution of CM-related roles is shown in Table 1-1; italicized responsibilities are not primarily configuration management activity but are included for continuity.

Applies to Development of New Systems and to Modifications of Existing Systems

Government

Contractor(s) or Government Performing Activities

Solicits concept (Systems Engineering) studies. May participate on Integrated Product Team (IPT)

Specifies desired performance attributes for a system/CI

Selects Contractor or approves engineering change proposal or modification request

Approves and baselines top level performance configuration documentation (specifications) and acts as current document control authority (CDCA) for those performance specifications and configuration control authority for the System/CI

Monitors contractor CM process via:
- IPT participation
- Metrics
- Performance reviews

Baselines selected product performance configuration documentation after verifying (e.g. FCA) that performance requirements have been achieved

Continues as CDCA for selected performance configuration documentation; may become CDCA for other documentation as contractually established

Consistent with support approach for selected CIs, baselines selected product (design) configuration documentation after verifying (e.g. at a PCA for the CI) that the design documentation matches the delivered configuration.

Continues as configuration control authority for the System/CI during its life as a Government asset and CDCA for selected performance and design documentation, as contractually established.

Similar cycle repeats for modifications

Performs system engineering studies. Determines alternative system approaches

Proposes Items or Design Solution

Prepares and submits performance specification for approval. May participate with Government on IPT.

Initiates development. Incrementally baselines design solution and acts as current document control authority (CDCA) for released configuration documentation, e.g. performance and detail specifications (below the level controlled by the Government), engineering drawings, engineering models, etc. for which another Government activity or commercial organization is not already the CDCA)

Baselines product (design) configuration documentation after verifying performance attributes and consistency between item and configuration documentation. (FCA & PCA)

Continues as CDCA for configuration documentation which it does not transition to the Government

Similar cycle repeats for modifications

Rev 2006-11-18 12:04:03 -0700

For correct application of this information, see NOTE on Contents page