| NODIS Library | Program Formulation(7000s) | Search |

NPR 7123.1D
Effective Date: July 05, 2023
Expiration Date: July 05, 2028
Printable Format (PDF)

Subject: NASA Systems Engineering Processes and Requirements Updated w/Change 2

Responsible Office: Office of the Chief Engineer

| TOC | ChangeLog | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | ALL |


P.1 Purpose

This document establishes the NASA processes and requirements for implementation of Systems Engineering (SE) by programs/projects. NASA SE is a logical systems approach performed by multidisciplinary teams to engineer and integrate NASA's systems to ensure NASA products meet customers' needs. Implementation of this systems approach will enhance NASA's core engineering capabilities while improving safety, mission success, and affordability. This systems approach is applied to all elements of a system (i.e., hardware, software, and human) and all hierarchical levels of a system over the complete program/project life cycle.

P.2 Applicability

a. This NASA Procedural Requirement (NPR) applies to NASA Headquarters and NASA Centers, including component facilities and technical and service support centers. This NPR applies to NASA employees and NASA support contractors that use NASA processes to augment and support NASA technical work. This NPR applies to the Jet Propulsion Laboratory (JPL), a Federally Funded Research and Development Center, other contractors, grant recipients, or parties to agreements only to the extent specified or referenced in the appropriate contracts, grants, or agreements. (See Chapter 4.)

b. This NPR applies to air and space flight, research and technology, information technology (IT), and institutional programs and projects. Tailoring the requirements in this NPR and customizing practices, based on criteria such as system/product size, complexity, criticality, acceptable risk posture, and architectural level, are necessary and expected. See Section 2.2 for tailoring and customizing descriptions. For IT programs and projects and applicable SE tailoring for IT, see NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements.

c. In this document, projects are viewed as a specific investment with defined goals, objectives, and requirements, with the majority containing a life-cycle cost, a beginning, and an end. Projects normally yield new or revised products or services that directly address NASA strategic needs. They are performed through a variety of means, such as wholly in-house, by Government, industry, international or academic partnerships, or through contracts with private industry.

d. The requirements enumerated in this document are applicable to all new programs and projects, as well as to all programs and projects currently in the Formulation Phase, as of the effective date of this document. (See NPR 7120.5, NASA Space Flight Program and Project Management Requirements; or NPR 7120.8, NASA Research and Technology Program and Project Management Requirements for definitions of program phases.) This NPR also applies to programs and projects in their Implementation Phase as of the effective date of this document. For existing programs/projects regardless of their current phase, waivers or deviations allowing continuation of current practices that do not comply with one or more requirements of this NPR, may be granted using the Center's Engineering Technical Authority (ETA) Process.

e. Many other discipline areas perform functions during the program/project life cycle and influence or are influenced by the engineering functions performed and, therefore, need to be fully integrated into the SE processes. These discipline areas include but are not limited to health and medical, safety, reliability, maintainability, quality assurance, IT, system security (including cybersecurity), logistics, operations, training, human systems integration, planetary protection, and environmental protection. The description of these disciplines and their relationship to the overall program/project management life cycle are defined in other NASA directives; for example, the safety, reliability, maintainability, and quality assurance requirements and standards are defined in the Office of Safety and Mission Assurance (OSMA) directives and standards, and health and medical requirements are defined in the Office of the Chief Health and Medical Officer (OCHMO) directives and standards.

f. In this NPR, all mandatory actions (i.e., requirements) are denoted by statements containing the term "shall." The requirements are explicitly shown as [SE-XX] for clarity and tracking purposes as indicated in Appendix H. 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.

g. In this NPR, all document citations are assumed to be the latest version, unless otherwise noted.

P.3 Authority

a. National Aeronautics and Space Act, 51 U.S.C. ยง 20113(a).

b. NPD 1000.0, NASA Governance and Strategic Management Handbook.

c. NPD 1000.3, The NASA Organization.

d. NPD 1001.0, NASA Strategic Plan.

P.4 Applicable Documents and Forms

a. Government Contract Quality Assurance, 48 CFR, subpt 1846.4.

b. NPD 2570.5, NASA Electromagnetic Spectrum Management.

c. NPR 1441.1, NASA Records Management Program Requirements.

d. NPR 2810.1, Security of Information and Information Systems.

e. NPR 7120.5, NASA Space Flight Program and Project Management Requirements.

f. NPR 7150.2, NASA Software Engineering Requirements.

g. NASA-HDBK-2203, NASA Software Engineering Handbook.

P.5 Measurement/Verification

a. Compliance with this document is verified by the Office of the Chief Engineer using surveys, audits, reviews, and/or reporting requirements.

b. Compliance, including tailoring, for programs and projects is documented by appending a completed Compliance Matrix for Programs/Projects (see Appendix H) to the Systems Engineering Management Plan (SEMP) or other equivalent program/project documentation and by submitting the review products and plans identified in this document to the responsible NASA officials at the life-cycle and technical reviews. Programs and projects may substitute a matrix that documents compliance with their particular Center implementation of this NPR, if applicable.

P.6 Cancellation

NPR 7123.1C, NASA Systems Engineering Processes and Requirements, dated February 14, 2020.

| TOC | ChangeLog | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | ALL |
| NODIS Library | Program Formulation(7000s) | Search |


This document does not bind the public, except as authorized by law or as incorporated into a contract. This document is uncontrolled when printed. Check the NASA Online Directives Information System (NODIS) Library to verify that this is the correct version before use: https://nodis3.gsfc.nasa.gov.