1、 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED NASA TECHNICAL STANDARD NASA-STD-0005 National Aeronautics and Space Administration Washington, DC 20546-0001 Approved: 09-29-2008 Expiration Date: 09-28-2013 NASA Configuration Management (CM) Standard MEASUREMENT SYSTEM IDENTIFICATION: NOT MEAS
2、UREMENT SENSITIVE Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 2 of 143 DOCUMENT HISTORY LOG Status Document Revision Approval Date Description Baseline 09-29-2008 Initial Release
3、Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 3 of 143 FOREWORD This Standard is published by the National Aeronautics and Space Administration (NASA) to provide uniform engineering
4、 and technical requirements for processes, procedures, practices, and methods that have been endorsed as standard for NASA programs and projects, including requirements for selection, application, and design criteria of an item. This Standard is approved for use by NASA Headquarters and NASA Centers
5、, including Component Facilities. This Standard establishes a common framework for consistent and acceptable Configuration Management (CM) practices across NASA. Requests for information, corrections, or additions to this Standard should be submitted via “Feedback” in the NASA Standards and Technica
6、l Assistance Resource Tool at http:/standards.nasa.gov. The principles from EIA-649, National Consensus Standard for Configuration Management, Revision A, were adopted and incorporated into this standard; and each Standard requirement is related to an EIA-649 principle within the text of the Standar
7、d. Excerpts of principles were taken from EIA-649, Revision A, National Consensus Standard for Configuration Management, Copyright 2004 Government Electronics and Information Technology Association, a Sector of the Electronic Industries Alliance. All Rights Reserved, Reprinted by Permission. Origina
8、l Signed By 09/29/2008 Michael G. Ryschkewitsch NASA Chief Engineer Approval Date Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 4 of 143 TABLE OF CONTENTS SECTION PAGE DOCUMENT HIST
9、ORY LOG . 2 FOREWORD . 3 TABLE OF CONTENTS. 4 LIST OF FIGURES . 5 LIST OF TABLES . 5 1. SCOPE . 6 1.1 Purpose. 6 1.2 Applicability 6 1.3 NASA Configuration Management (CM) Requirements and Planning Hierarchy . 7 1.4 Key Terminology Used in This Standard 8 2. APPLICABLE DOCUMENTS 9 2.1 General . 9 2.
10、2 Government Documents 9 2.3 Non-Government Documents 10 2.4 Order of Precedence. 11 3. ACRONYMS AND DEFINITIONS 11 3.1 Acronyms . 11 3.2 Definitions 11 4. REQUIREMENTS. 11 4.1 Planning . 12 4.2 Configuration Identification. 19 4.3 Configuration Control . 35 4.4 Configuration Status Accounting (CSA)
11、 and Release System 49 4.5 Configuration Verification and Audits . 61 5. GUIDANCE 64 5.1 Reference Documents 64 5.2 Keyword Listing 65 5.3 Supplemental Guidance for Configuration Management (CM) Planning . 65 5.4 Supplemental Guidance for Configuration Management (CM) Identification 68 5.5 Supplemen
12、tal Guidance for Configuration Control . 69 5.6 Supplemental Guidance for Configuration Status Accounting (CSA) 70 5.7 Supplemental Guidance for Verification/Audits 72 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC
13、RELEASEDISTRIBUTION IS UNLIMITED 5 of 143 TABLE OF CONTENTS (Continued) SECTION PAGE Appendix A Acronyms and Definitions 73 Appendix B NASA Project or Supplier Configuration Management Plan (CMP) Requirements. 89 Appendix C Configuration Management (CM) Principles. 96 Appendix D Guidelines for the P
14、reparation and Processing of Engineering Change Proposals (ECPs) 99 Appendix E Guidelines and Instructions for Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs). 111 Appendix F Guidelines and Instructions for the Preparation of Request for Waiver 141 LIST OF FIGURES Fig
15、ure Page 1 NASA Configuration Management (CM) Requirements 7 2 Configuration Management (CM) Plan Development. 8 3 Sample Audit Action Item List 114 4 Sample Functional Configuration Audit (FCA) Checklist 118 5 Sample Functional Configuration Audit (FCA) Certification Package . 119 6 Sample Physical
16、 Configuration Audit (PCA) Checklist 126 7 Sample Physical Configuration Audit (PCA) Certification Package. 130 LIST OF TABLES Table Page 1 Computer-Aided Design (CAD) Product Structure . 27 2 Target Timeframe for Class I ECPs and RFCs 41 3 Configuration Status Accounting (CSA) Products 59 4 Class I
17、 Change Definition 71 5 Content of Engineering Change Proposals (ECPs) 101 6 Request for Waiver (RFW) Content 142 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 6 of 143 NASA CONFIGU
18、RATION MANAGEMENT (CM) STANDARD 1. SCOPE 1.1 Purpose This Standard provides a consistent and systematic method for configuration management of products delivered to or produced by the Agency under configuration control to (a) identify the configuration of a product at various points in time; (b) sys
19、tematically control changes to the configuration of the product; (c) maintain the integrity and traceability of the configuration of the product throughout its life; and (d) preserve the records of the product configuration throughout its life cycle, properly dispositioning the records. NASA CM requ
20、irements originate in NPR 7123.1, NASA Systems Engineering Processes and Requirements. This standard addresses the planning and implementation of the following basic CM functions based on EIA-649A, National Consensus Standard for Configuration Management principles. These functions are described as:
21、 CM planning, configuration identification (including interface management), configuration control, configuration accounting (including configuration traceability), and configuration verification and audits. 1.2 Applicability This standard applies to NASA Headquarters and NASA Centers, including com
22、ponent Facilities and the Jet Propulsion Laboratory, and contractors/service providers to the extent specified in their contracts with NASA. This standard may be cited in the CM requirements of NASA Headquarters, NASA Centers, Programs, Projects, and Supplier contracts/agreements. This Standard is a
23、pplicable to NASA investment areas covered under NPR 7120.5, NASA Space Flight Program and Project Management Requirements; NPR 7120.7 (Draft), NASA Information Technology and Institutional Infrastructure Program and Project Requirements; and NPR 7120.8, NASA Research and Technology Program and Proj
24、ect Management Requirements. This standard may be applied to other NASA investments at the discretion of NASA management. This standard applies throughout all phases of the program and project life cycle. Requirements are numbered and indicated by the word “shall.” Explanatory or guidance text is in
25、dicated in italics beginning in section 4. 1.2.1 Tailoring of this standard for application to a specific program or project shall be formally documented as part of program or project requirements. The requirements of this Standard may be tailored based on the type and content of an activity. 1.2.2
26、Tailoring concepts that delete or significantly modify implementing the EIA-649 principles in this Standard shall be assessed on a risk analysis basis in accordance with NPR 8000.4, Risk Management Procedural Requirements. Provided by IHSNot for ResaleNo reproduction or networking permitted without
27、license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 7 of 143 1.2.3 The basis of assessment shall be “What is the risk associated with not following the EIA-649 principle?” 1.2.4 The acceptance of the resulting risk shall be approved or disapproved by the responsib
28、le Programmatic or Institutional Authority. 1.3 NASA Configuration Management (CM) Requirements and Planning Hierarchy Figure 1 shows the flowdown of NASA CM policy including the requirements in NASA-STD-0005 and its implementing guidance in the handbooks. NASA Programs/Projects/Centers have the res
29、ponsibility for developing requirements, and Suppliers shall develop CMPs to meet these requirements as illustrated in Figure 2. NPR 7120.5 NPR 7123.1 Center and Program/Project CM Requirements Implementation Guidance in NASA-STD-0005 and DoD and Industry Consensus Handbooks Figure 1NASA Configurati
30、on Management (CM) Requirements NASA CM Policy NASA CM Standard NASA-STD-0005Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 8 of 143 1.4 Key Terminology Used in This Standard a. Supp
31、lier: The organization that applies the CM discipline. The supplier may be a contractor, academia, or the Government. The supplier may be the design agency involved in production of a product, or be limited to producing documentation. Note: The role of “contractor” is not defined in this document an
32、d is assumed to be included within the role of “supplier.” b. Program/Project/Center: The NASA management function for the activity. c. Configuration Management Organization (CMO): The collaborative CM effort shared between the Program/Project/Center and the Supplier. d. Prescribed Requirement: A re
33、quirement levied on a lower organizational entity by a higher organizational entity. These requirements are distinguished from requirements that are derived at the lower level in order to implement the higher level prescribed requirements. e. Deviation: A documented authorization releasing a program
34、 or project from meeting a requirement before the requirement is put under configuration control at the level the requirement will be implemented. f. Waiver: A documented authorization releasing a program or project from meeting a requirement after the requirement is put under configuration control
35、at the level the requirement will be implemented. Figure 2Configuration Management (CM) Plan Development Overall CM Objectives Program/Project CM Processes Supplier CM Processes and IT Systems NASA CM Policy Program/Project CMP Supplier CMP Provided by IHSNot for ResaleNo reproduction or networking
36、permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 9 of 143 g. Contract, Agreement: Terms utilized interchangeably in this standard to indicate an agreement between a Supplier and a Program/Project/Center. This agreement could be between governm
37、ent organizations (e.g., task agreement) or between the Government and a business enterprise or academia (e.g., contract). h. Shall: The verb “shall” indicates a Supplier requirement. The collaborative CMO tasks use the emphatic “shall” to indicate an obligation or requirement on the part of the Sup
38、plier. (An exception is when the Supplier and Program/Project/Center and/or CMO are involved in a collaborative requirement. The emphatic “shall” is used as a grammatical convenience and does not imply special expectation on the Program/Project/Center. Example: The Program/Project/Center and the Sup
39、plier shall perform.) i. Should, May, Can: Good practices, guidance, or options are specified with the non-emphatic verbs “should,” “may,” or “can.” j. Will: The verb “will” describes a fact, expectation, or premise of accomplishment by a Program/Project/Center. k. Is: The verb “is” or verbs without
40、 emphatic auxiliaries are used in descriptive material. 2. APPLICABLE DOCUMENTS 2.1 General The documents listed in paragraphs 2.2 and 2.3 contain provisions that constitute requirements of this Standard as cited in the text of section 4. They form a part of this document to the extent specified in
41、this Standard. The latest issuances of cited documents shall be used unless otherwise approved by the assigned Technical Authority. The applicable documents are accessible via the NASA Standards and Technical Assistance Resource Tool at http:/standards.nasa.gov, directly from the Standards Developin
42、g Organizations, or from other document distributors. 2.2 Government Documents Department of Defense (DoD) DD Form 250 Material Inspection and Receiving Report DD Form 254 Department of Defense Contract Security Classification Specification Defense Logistics Agency (DLA) Cataloging Handbook H4/H8 Se
43、ries MIL-STD-130 Identification Marking of U.S. Military Property Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 10 of 143 National Aeronautics and Space Administration NASA-STD-6002
44、 Applying Data Matrix Identification Symbols on Aerospace Parts NASA-HDBK-6003 Application of Data Matrix Identification Symbols to Aerospace Parts Using Direct Part Marking Methods/Techniques NPR 1441.1 NASA Records Retention Schedules NPR 7120.5 NASA Spaceflight Program and Project Management Requ
45、irements NPR 7120.7 NASA Information Technology and Institutional Infrastructure Program and Project Requirements (Draft) NPR 7120.8 NASA Research and Technology Program and Project Management Requirements NPR 7123.1 NASA Systems Engineering Processes and Requirements NPR 7150.2 NASA Software Engine
46、ering Requirements NPR 8000.4 Risk Management Procedural Requirements 2.3 Non-Government Documents ASME ASME Y14.24 Types and Applications of Engineering Drawings ASME Y14.100 Engineering Drawing Practices IEEE IEEE-STD-828 Software Configuration Management Plans NDIA ANSI/GEIA-EIA-649 National Cons
47、ensus Standard for Configuration Management (referred to in this Standard as EIA-649) GEIA-859 Data Management Standard Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-STD-0005 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 11 of 143 2.4 O
48、rder of Precedence When this Standard is applied as a requirement or imposed by contract and/or agreement on a program or project, the technical requirements of this Standard take precedence, in the case of conflict, over the technical requirements cited in applicable documents or referenced guidance documents.
