Configuration Management Glossary

The means by which an approved Change Request is planned and implemented.
_{Source: mdux.net}

The means by which a proposal to alter an item is described, analyzed and dispositioned.
_{Source: mdux.net}

A rolling or moving baseline that is updated with every released dataset and includes visibility on both the released and planned changes to the datasets and items in the baseline. Also known as As Planned/As Released Baseline.

The concept of standardizing product and process designs resulting in e.g. use of common parts and/or common build sequences.
_{Source: mdux.net}

1.The functional and physical characteristics of existing or planned hardware, firmware, software or a combination thereof, as detailed in requirements and technical documentation and ultimately achieved in a product.
_{Source: MIL-STD-3046(ARMY)}

2. A collection of an item’s descriptive and governing characteristics that can be expressed in functional terms (i.e., what performance the item is expected to achieve) and in physical terms (i.e., what the item should look like and consist of when it is built). Configuration represents the requirements, architecture, design, and implementation that define a particular version of a system or system component.
_{Source: MIL-HDBK-61B}

1. A product or an aggregation of products that accomplishes an end-use function and requires separate identification. An item is designated as a CI for purposes of additional configuration management focus due to its complexity, logistic support requirements, acquisition strategy, or because it is intended to undergo configuration status accounting or verification and audit separately from other items. Configuration items are end items or major components of end items, which typically have performance requirements allocated to them and documented in their own specification.
_{Source: MIL-STD-3046(ARMY)}

2. a. An aggregation of hardware, software, or both that is designated for CM and treated as a single entity in the CM process.
b. The entity within a configuration that satisfies an end use function and that can be uniquely identified at a given reference point.
_{Source: MIL-HDBK-61B}

The process of tracking, recording, and reporting the current state of your configuration items. It gives you a clear picture of (not exhaustive):

• Which items are in use and which are obsolete.
• What changes have been proposed, approved, or implemented.
• Whether all parts and documents are properly aligned.

_{Source: mdux.net}

The activity to determine that the part conforms to its requirements, including the incorporation of approved changes.
_{Source: mdux.net}

The ability to control how and when changes will be applied to a part or unit. This includes which changes will be applied and when, but also changes to the location of a unit or an application order that is executed against the unit.
_{Source: The Essential Guide to Part Re-Identification}