scope:

Purpose

The purpose of this standard is to establish a consistent set of requirements to control risk and enhance reliability in NASA space flight hardware and critical ground support equipment, in part, by managing the selection, acquisition, traceability, testing, handling, packaging, storage, and application of EEE parts as required by NASA Policy Directive (NPD) 8730.2, NASA Parts Policy. The requirements contained in this standard are not applicable to aeronautics systems, unless specifically cited in governing documents.

While this document may give guidance with respect to processes and selection criteria associated with EEE parts, it is generally not the intent of this standard to mandate specific reliability grade parts in particular applications, rather to allow programs and projects to make these decisions based on the guidance contained herein, Center EEE Parts input, and program and project requirements. Sections 4.2 (including table 2) and 5.2.4 are included as qualitative guidance and are not to be considered requirements.

Applicability

This standard is approved for use by NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers, and may be cited in contract, program, and other Agency documents as a technical requirement. This standard may also apply to the Jet Propulsion Laboratory or to other contractors, grant recipients, or parties to agreements only to the extent specified or referenced in their contracts, grants, or agreements.

This standard is applicable to space flight hardware, launch vehicles, critical ground support equipment (GSE), projects governed by NPR 7120.5, NASA Space Flight Program and Project Management Requirements.

This standard does not apply to institutional projects as defined by NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Requirements, or to Research and Technology Development Programs and Projects as defined by NPR 7120.8, NASA Research and Technology Program and Project Management Requirements unless explicitly specified in project requirements documents.

All mandatory actions (i.e., requirements) are denoted by statements containing the term "shall." The terms: "may" or "can" denote discretionary privilege or permission, "should" denotes a good practice and is recommended but not required, "will" denotes expected outcome, and "are/is" denotes descriptive material.