MIL-STD-973 was the U.S. Department of Defense standard that governed configuration management for defense systems, setting uniform rules for how contractors and program offices identified configuration items, controlled changes to them, and documented their technical baselines across the life cycle. The DoD canceled it on September 20, 2000, and its role now sits with the commercial EIA-649 family (EIA-649-1 for defense contracts) and the guidance handbook MIL-HDBK-61.1Federal Register. Defense Federal Acquisition Regulation Supplement – Cancellation of MIL-STD-973, Configuration Management
What the Standard Did
MIL-STD-973 applied to any configuration item developed with government funds, or any item designated for configuration management because of integration, logistics, or interface needs. A configuration item could be hardware, a software module, or a critical technical document.2EverySpec. MIL-STD-973 Configuration Management
The point was to keep a system’s documented technical identity aligned with the hardware and software actually being built and fielded. On a weapons platform or a communications system, a mismatch between the product and its technical data package is a safety and readiness problem, not a paperwork problem. The standard was the discipline that kept the two in sync.
The Framework It Established
MIL-STD-973 organized configuration management around five functions that worked together: configuration identification (choosing items for control and documenting their approved characteristics), configuration control (the formal change-approval process), configuration status accounting (the audit trail of every change), configuration audits (verifying that a product matches its documentation and meets its requirements), and configuration data management (governing the CM documentation itself).
The Three Baselines
The standard defined three baselines that a program established as a system matured. The Functional Baseline captured top-level performance requirements in a system performance specification under government authority. The Allocated Baseline broke those requirements down to individual configuration items through item performance specifications, with authority shifting to the contractor. The Product Baseline, set at the end of development, documented the detailed physical and form-fit-function characteristics needed for manufacturing and acceptance; its final version returned to government control.3Defense Acquisition University. Technical Baselines
Engineering Change Proposals
Changes to any established baseline moved through the Engineering Change Proposal process on DD Form 1692, with technical justification, cost and schedule impact, and supporting data.4Defense Acquisition Regulations System. DFARS 252.243-7000 – Engineering Change Proposals A Class I (Major) ECP touched approved functional or performance requirements, cost, warranties, or contract milestones and required government approval through a Configuration Control Board. A Class II (Minor) ECP covered documentation changes that did not affect performance, cost, or schedule.5Defense Acquisition University. Engineering Change Proposals (ECP)
What Replaced It
When the DoD canceled MIL-STD-973 in 2000, there was no direct military replacement.1Federal Register. Defense Federal Acquisition Regulation Supplement – Cancellation of MIL-STD-973, Configuration Management The department moved to commercial standards instead, and two documents inherited the role MIL-STD-973 had played.
EIA-649 and EIA-649-1
The primary successor is EIA-649, the National Consensus Standard for Configuration Management, currently at Revision C. It was developed by an international group of aerospace and defense contractors, government agencies, and independent experts, and the DoD formally adopted it.
For defense contracts specifically, the DoD uses EIA-649-1, a companion standard that translates EIA-649’s principles into contractual requirements. EIA-649-1 defines CM requirements for products and designs during the contract period, and it is written to be tailored by the acquirer and incorporated into individual contracts. Its scope matches what MIL-STD-973 covered: configuration items developed with acquirer funds or designated for CM because of integration, logistics, or interface needs.6Defense Standardization Program. EIA-649-1 Configuration Management Requirements for Defense Contracts
When EIA-649-1 was released, the Configuration Management Standards Working Group updated five DD Forms to support consistent implementation under the new standard: DD Form 1692 (Engineering Change Proposal), DD Form 1694 (Request for Variance), DD Form 1695 (Notice of Revision), DD Form 1696 (Specification Change Notice), and DD Form 2617 (Engineering Release Record).6Defense Standardization Program. EIA-649-1 Configuration Management Requirements for Defense Contracts The forms survived the cancellation largely intact; the standard behind them changed.
MIL-HDBK-61
The second document is MIL-HDBK-61, the DoD’s Configuration Management Guidance handbook. It is guidance only and cannot be cited as a contractual requirement, which is the key difference from the standard it followed.7ASSIST-QuickSearch. Document Details – MIL-HDBK-61 It gives program managers, systems engineers, and logistics managers best practices for planning and implementing CM activities across a system’s life cycle.
The handbook has been maintained continuously since the standard was canceled. Revision A was published on February 7, 2001. Revision B followed on April 7, 2020, with Change 1 issued on August 15, 2025.7ASSIST-QuickSearch. Document Details – MIL-HDBK-61
Why It Still Comes Up
The concepts MIL-STD-973 codified did not disappear with the standard. The five-function framework, the three baselines, and the Class I / Class II ECP distinction all carried into EIA-649 and EIA-649-1 in modernized language. Anyone reading current defense CM documentation will recognize the structure.
The more concrete reason the standard still matters is legacy programs. Long-lived weapons platforms carry technical data packages and configuration records built under MIL-STD-973 rules. Engineers performing sustainment or modification work on those systems have to read the original documentation on its own terms, even when new changes follow EIA-649-1. The DD Forms that programs still use daily for change proposals and variance requests trace their structure and data requirements directly to MIL-STD-973.