NASA MSFC STD 3394 : 2005

FOREWORD
1 SCOPE/PURPOSE
   1.1 Scope/Purpose
   1.2 Applicability
2 APPLICABLE AND REFERENCE DOCUMENTS
   2.1 Applicable Documents
   2.2 Reference Documents
3 ACRONYMS/DEFINITIONS
4 GENERAL REQUIREMENTS
5 CONFIGURATION MANAGEMENT PLANNING
   5.1 General
   5.2 Contractor's CM Plans
6 IDENTIFICATION
   6.1 Configuration Identification
   6.2 Specifications
   6.3 Interface Identification
   6.4 Drawing and Models
   6.5 Identification Numbering
   6.6 Lot and Serial Numbering
7 ENGINEERING RELEASE INFORMATION
   7.1 Engineering Release
   7.2 Elements of Data Required for Hardware Items
   7.3 Elements of Data Required for Software Items
   7.4 Production Release Functional Capabilities
   7.5 Release of Engineering Changes
   7.6 Field Release Functional Capabilities
8 CONFIGURATION CONTROL
   8.1 General
   8.2 Configuration Control Boards
   8.3 Changes, Deviations, and Waivers
   8.4 Engineering Change Proposal
   8.5 Record Engineering Change Proposal
   8.6 Field Engineering Change (FEC)
   8.7 Software/Firmware Field Engineering Change
   8.8 Deviation and Waiver Request
   8.9 Modification Kit and Instructions
9 CONFIGURATION ACCOUNTING
   9.1 General
   9.2 Configuration Accounting Requirements
   9.3 Configuration Accounting Records
10 CONFIGURATION VERIFICATION AND AUDIT
   10.1 General
   10.2 Planning
   10.3 Contractor Support
   10.4 Objectives
   10.5 Contractor Responsibilities
   10.6 In-process Configuration Management Audits
   10.7 "Other" Reviews
11 SOFTWARE CONFIGURATION MANAGEMENT
   11.1
   11.2 Independent Verification and Validation (IV&V)
   11.3 Delivery
   11.4 Software/Firmware marking and Labeling
Table
I Class I Change Definition
Appendix
A Configuration Management Plan
B Software Configuration Plan
C Specification Change Notice and Instructions
D Interface Control
E Change Control
F Acceptance Data Package
G Definitions, Abbreviations and Acronyms
H Guidance for Processing Urgent-Emergency Software Changes
I Documentation Guidance for FCA/PCA

The purpose of this document is to establish requirements for implementing Configuration Management (CM) on MSFC contracts to design, develop, fabricate, integrate, operate, or provide logistical support to hardware, software, and firmware items.