USAF ILA Handbook - ACC Practice Center - Defense Acquisition ...

D-15. Configuration Management
Configuration Management (CM) is the application of sound business practices to establish and
maintain consistency of a product's attributes with its requirements and product configuration
information. It involves interaction among Government and contractor program functions such as
systems engineering, design engineering, logistics, contracting, and manufacturing in an IPT
environment. CM includes system hardware, software, and documentation (data). A CM process
guides the system products, processes, and related documentation, and facilitates the development
of open systems. CM efforts result in a complete audit trail of decisions and design modifications.
See MIL-HDBK-61A, Figure 4-5, Page 4-10 for an illustration showing how CM objectives are
related to Program activity and Program objectives for each phase of the life cycle.
Evaluation Criteria
Milestone
B C FRP
1. Configuration Baseline
• CM decisions are based on factors that best support implementation of X U U
performance-based strategies throughout the product life cycle.
• Requirements for the configuration identification, control, status accounting, X
waivers/deviations, engineering changes and verification/audit functions are
established for hardware, software and product/technical data.
• Is EIA-836 being used for CM implementation X
• At the appropriate milestones, the functional, allocated and product baselines X
have been established and approved from development through disposal.
• Nomenclature has been established where appropriate. X
• Interfaces are defined using interface control documents as applicable. X U U
• The hardware/software requirements and product/technical data specification X U U
and interface requirements specification have been prepared and approved.
• Physical and functional characteristics are accurately reflected in design X U U
documentation.
• Have functional, allocated and product baselines been developed X U U
• Each computer software configuration item and its corresponding computer X
software components and computer software units have been identified.
• A software design document has been written for each computer software
X U
configuration item.
• The version, release, change status and other identification details of each
X U
deliverable item of software are known.
• For COTS/NDI and form/fit/function, information has been required/provided X U
for refreshment.
• Subcontractor CM requirements including information, data and metrics are
established.
X U
Version 1: Jan 2006 91
Air Force Independent Logistics Assessment Handbook