MIL-STD-973 Base Document:1992

Paragraph
1 Scope
1.1 Scope
1.2 Applicability
1.3 Tailoring of requirements
2 Applicable documents
2.1 Government documents
2.1.1 Specifications, standards, and handbooks
2.1.2 Other Government documents
2.2 Order of precedence
3 Definitions
3.1 Acronyms used in this standard
3.2 Advance Change Study Notice (ACSN)
3.3 Allocated Baseline (ABL)
3.4 Allocated Configuration Documentation (ACD)
3.5 Approval/contractual implementation
3.6 Block change concept
3.7 Classification of defects
3.8 Commercial and Government Entity (CAGE) code
3.9 Computer data base
3.10 Computer software
3.11 Computer Software Configuration Item (CSCI)
3.12 Computer software documentation
3.13 Configuration
3.14 Configuration audit
3.15 Configuration baseline
3.16 Configuration control
3.17 Configuration Control Board (CCB)
3.18 Configuration documentation
3.19 Configuration identification
3.20 Configuration Item (CI)
3.21 Configuration Management (CM)
3.22 Configuration Management Plan (CMP)
3.23 Configuration Status Accounting (CSA)
3.24 Contractor
3.25 Data
3.26 Database
3.27 Defect
3.28 Deficiencies
3.29 Design change
3.30 Developmental configuration
3.31 Deviation
3.32 Engineering change
3.33 Engineering change justification code
3.34 Engineering change priorities
3.35 Engineering Change Proposal (ECP)
3.36 Engineering Change Proposal types
3.37 Engineering release
3.38 Engineering Release Record (ERR)
3.39 Evaluation
3.40 Exchangeability of items
3.41 Firmware
3.42 Fit
3.43 Form
3.44 Function
3.45 Functional area
3.46 Functional Baseline (FBL)
3.47 Functional characteristics
3.48 Functional Configuration Audit (FCA)
3.49 Functional Configuration Documentation (FCD)
3.50 Hardware
3.51 Hardware Configuration Item (HWCI)
3.52 Integrated Logistics Support (ILS)
3.53 Interchangeable item
3.54 Interface
3.55 Interface control
3.56 Interface Control Drawing (ICD)
3.57 Interface Control Working Group (ICWG)
3.58 Interoperability
3.59 Item
3.60 Life cycle
3.61 Life cycle cost
3.62 Manufacturer's code
3.63 Material
3.64 Non-conformance
3.65 Non-developmental Item (NDI)
3.66 Non-recurring costs
3.67 Notice of Revision (NOR)
3.68 Original
3.69 Physical characteristics
3.70 Physical Configuration Audit (PCA)
3.71 Product Baseline (PBL)
3.72 Product Configuration Documentation (PCD)
3.73 Recurring costs
3.74 Release
3.75 Repair
3.76 Replacement item
3.77 Retrofit
3.78 Rework
3.79 Software
3.80 Software unit
3.81 Specification
3.82 Specification Change Notice (SCN)
3.83 Substitute item
3.84 Support equipment
3.85 Survivability
3.86 System, general
3.87 Technical data
3.88 Technical data package
3.89 Technical documentation
3.90 Technical reviews
3.91 Training equipment
3.92 Unit
3.93 Version
3.94 Waiver
3.95 Work Breakdown Structure (WBS)
3.96 Work breakdown structure element
4 General requirements
4.1 Basic requirements
4.2 Planning
4.3 Computer-aided Acquisition and Logistic Support
         (CALS)
4.3.1 Data distribution/access
4.3.2 Automated processing and submittal of data
4.3.3 Interactive access to digital data
4.4 Configuration identification
4.5 Configuration control
4.6 Configuration Status Accounting (CSA)
4.7 Configuration audits
5 Detailed requirements
5.1 Purpose
5.2 Configuration management administration
5.2.1 Contractor's CM plan
5.2.2 Work Breakdown Structure (WBS)
5.2.3 Technical reviews
5.3 Configuration identification
5.3.1 Purpose of configuration identification
5.3.2 Configuration Item selection
5.3.3 Developmental configuration
5.3.4 Configuration baselines
5.3.4.1 Configuration baselines and their configuration
         documentation
5.3.4.1.1 Functional configuration documentation (FCD)
5.3.4.1.2 Allocated configuration documentation
5.3.4.1.3 Product configuration documentation
5.3.5 Engineering release and correlation of
         manufacturing products
5.3.6 Configuration identifiers
5.3.7 Interface management
5.4 Configuration control
5.4.1 Purpose of configuration control
5.4.2 Requirements for Engineering Change Proposals
6 Notes
6.1 Intended use
6.2 Tailoring guidance for contractual application
6.2.1 Use of Table II
6.2.2 Use of Table III
6.3 Data requirements
6.4 Supersession data
6.5 Subject term (key word) listing
Figures
1. Advance Change Study Notice
2. Sample Engineering Change Proposal Message
         Format
3a.-3b. Sample Audit Action Items List
4. Sample FCA Checklist
5a.-5g. Sample FCA Certification Package
6. Sample PCA Checklist
7a.-7k. Sample PCA Certification Package
8a. Engineering Release Record
8b. Engineering Release Record Continuation Page
9a. Engineering Change Proposal - Page 1
9b. Engineering Change Proposal - Page 2
9c. Engineering Change Proposal - Page 3
9d. Engineering Change Proposal - Page 4
9e. Engineering Change Proposal - Page 5
9f. Engineering Change Proposal - Page 6
9g. Engineering Change Proposal - Page 7
10. Request for Deviation/Waiver
11. Specification Change Notice
12. Notice of Revision
Tables
I Appendix D block number content requirements for
      an ECP
II Tailoring guide for use with MIL-STD-973
III Application of CSA tasks
IV Cross reference from MIL-STD-480B (15 July 1988)
V Cross reference from MIL-STD-481B (15 July 1988)
VI Cross reference from MIL-STD-482A (1 April 1974)
VII Cross reference from MIL-STD-483A (5 June 1985)
VIII Cross reference from MIL-STD-1456A (11 Sept 1989)
IX Cross reference from MIL-STD-1521B (5 June 1985)
X Cross reference from MIL-STD-2167A (29 Feb 1988)
Appendixes
A Contractor's configuration management (CM) plan
B Engineering release records and correlation of
   manufactured products
C Instruction for the preparation of an engineering
   released record (ERR)
D Instructions for the preparation of an ECP
E Instructions for the preparation of request for
   deviation/waiver
F Instructions for the preparation of specification
   change notice
G Instructions for the preparation of notice of
   revision
H Configuration Status Accounting (CSA) requirements
   and records
I CSA data elements

Defines configuration management requirements that are to be selectively applied, as required, throughout the life cycle of ny configuration item (CI). Applies to Department of Defense activities and contractors who are tasked with the application of configuration management. Coverage includes detailed definitions, configuration control, configuration audits, data distribution/access, interactive access to digital data, documentation library, development configuration, interface management, and reuse of serial numbers.