Table of Contents
FOREWORD
1SCOPE/PURPOSE
1.1Scope/Purpose
1.2Applicability
2APPLICABLEANDREFERENCEDOCUMENTS
2.1ApplicableDocuments
2.2ReferenceDocuments
3ACRONYMS/DEFINITIONS
4GENERALREQUIREMENTS
5CONFIGURATIONMANAGEMENTPLANNING
5.1General
5.2Contractor'sCMPlans
6IDENTIFICATION
6.1ConfigurationIdentification
6.2Specifications
6.3InterfaceIdentification
6.4DrawingandModels
6.5IdentificationNumbering
6.6LotandSerialNumbering
7ENGINEERINGRELEASEINFORMATION
7.1EngineeringRelease
7.2ElementsofDataRequiredforHardwareItems
7.3ElementsofDataRequiredforSoftwareItems
7.4ProductionReleaseFunctionalCapabilities
7.5ReleaseofEngineeringChanges
7.6FieldReleaseFunctionalCapabilities
8CONFIGURATIONCONTROL
8.1General
8.2ConfigurationControlBoards
8.3Changes,Deviations,andWaivers
8.4EngineeringChangeProposal
8.5RecordEngineeringChangeProposal
8.6FieldEngineeringChange(FEC)
8.7Software/FirmwareFieldEngineeringChange
8.8DeviationandWaiverRequest
8.9ModificationKitandInstructions
9CONFIGURATIONACCOUNTING
9.1General
9.2ConfigurationAccountingRequirements
9.3ConfigurationAccountingRecords
10CONFIGURATIONVERIFICATIONANDAUDIT
10.1General
10.2Planning
10.3ContractorSupport
10.4Objectives
10.5ContractorResponsibilities
10.6In-processConfigurationManagementAudits
10.7"Other"Reviews
11SOFTWARECONFIGURATIONMANAGEMENT
11.1
11.2IndependentVerificationandValidation(IV11.3Delivery
11.4Software/FirmwaremarkingandLabeling
Table
IClassIChangeDefinition
Appendix
AConfigurationManagementPlan
BSoftwareConfigurationPlan
CSpecificationChangeNoticeandInstructions
DInterfaceControl
EChangeControl
FAcceptanceDataPackage
GDefinitions,AbbreviationsandAcronyms
HGuidanceforProcessingUrgent-EmergencySoftwareChanges
IDocumentationGuidanceforFCA/PCA Abstract
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.
