NASA Configuration Management (CM) Standard
|Publication Date:||9 March 2015|
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) systematically 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 requirements 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: CM planning, configuration identification (including interface management), configuration control, configuration accounting (including configuration traceability), and configuration verification and audits.
This standard applies to NASA Headquarters and NASA Centers, including component 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 applicable 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 Project 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 indicated in italics beginning in section 4.
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.
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.
The basis of assessment shall be "What is the risk associated with not following the EIA- 649 principle?"
The acceptance of the resulting risk shall be approved or disapproved by the responsible Programmatic or Institutional Authority.
NASA Configuration Management (CM) Requirements and Planning Hierarchy
the flowdown of NASA CM policy including the requirements in NASA-STD- 0005 and its implementing guidance in the handbooks.
Key Terminology Used in This Standard
a. Supplier: 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 and is assumed to be included within the role of "supplier."
c. Configuration Management Organization (CMO): The collaborative CM effort shared between the Program/Project/Cent
d. Prescribed Requirement: A requirement 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 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 at the level the requirement will be implemented.
g. Contract, Agreement: Terms utilized interchangeably in this standard to indicate an agreement between a Supplier and a Program/Project/Cent
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 Supplier. (An exception is when the Supplier and Program/Project/Cent
i. Should, May, Can: Good practices, guidance, or options are specified with the nonemphatic verbs "should," "may," or "can."
j. Will: The verb "will" describes a fact, expectation, or premise of accomplishment by a Program/Project/Cent
k. Is: The verb "is" or verbs without emphatic auxiliaries are used in descriptive material.