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

NASA Ball NASA
Procedural
Requirements
NPR 7123.1D
Effective Date: July 05, 2023
Expiration Date: July 05, 2028
COMPLIANCE IS MANDATORY FOR NASA EMPLOYEES
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 |

Chapter 4. NASA Systems Engineering Activities on Contracted Projects

4.1 Introduction

4.1.1 Work contracted in support of programs and projects is critical to mission success. Inputs or requirements in support of a solicitation (such as Requests for Proposals) typically include a Statement of Work, product requirements, Independent Government Estimate, Data Requirements List, Deliverables List, and Surveillance Plan. These should be developed considering the risk posture of the program/project and fit within the cost and schedule constraints. In addition to developing the product requirements, a critical aspect of the solicitation is for the technical team to define the insight and oversight requirements. "Insight" is a monitoring activity, whereas "oversight" is an exercise of authority by the Government. The Federal Acquisition Regulation and the NASA Supplement to the Federal Acquisition Regulation govern the acquisition planning, contract formation, and contract administration process. Authority to interface with the contractor can be delegated only by the contracting officer. The activities listed in Section 4.2 will be coordinated with the cognizant contracting officer. Detailed definitions for insight and oversight are provided per Government Contract Quality Assurance, 48 CFR, subpt. 1846.4. As stated in Section 1.1.3, the requirements should be appropriately tailored and customized for system/product size, complexity, criticality, acceptable risk posture, and architectural level.

4.1.2 This chapter defines a minimum set of technical activities and requirements for a NASA program/project technical team to perform before contract award, during contract performance, and upon completion of the contract on program/projects. These activities and requirements are intended to supplement the common technical process activities and requirements of Chapter 3 and thus enhance the outcome of the contracted effort and ensure the required integration between work performed by the contractor and the program or project.

4.2 Prior to Contract Award

4.2.1 The NASA technical team shall define the engineering activities for the periods before contract award, during contract performance, and upon contract completion in the SEMP or other equivalent program/project documentation [SE-24].

4.2.2 The content of Appendix J of NASA/SP-6105 should be used as a guide in the development of the SEMP or other equivalent program/project documentation.

4.2.3 The NASA technical team shall establish the technical inputs to the solicitation appropriate for the product(s) to be developed, including product requirements and Statement of Work tasks [SE-25].

4.2.3.1 The technical team uses knowledge of the 17 common technical processes to identify products and desired practices to include in the solicitation.

4.2.4 The NASA technical team shall determine the technical work products to be delivered by the offeror or contractor, to include contractor documentation that specifies the contractor's SE approach to the scope of activities described by the 17 common technical processes [SE-26].

4.2.5 The NASA technical team shall provide the requirements for technical insight and oversight activities planned in the NASA SEMP or other equivalent program/project documentation to the contracting officer for inclusion in the solicitation [SE-27].

4.2.6 Care should be taken that no requirements or solicitation information is divulged prior to the release of the solicitation.

4.2.7 The NASA technical team shall participate in the evaluation of offeror proposals in accordance with applicable NASA and Center source selection procedures [SE-28].

4.2.7.1 This requirement ensures that the proposal addresses the requirements, products, and processes specified in the solicitation.

4.3 During Contract Performance

4.3.1 The NASA technical team, under the authority of the contracting officer, shall perform the technical insight and oversight activities established in the contract including modifications to the original contract [SE-29].

4.3.2 The requirements levied on the technical team in Section 4.2 for establishing the contract applies to any modifications or additions to the original contract.

4.4 Contract Completion

4.4.1 The NASA technical team shall participate in the review(s) to finalize Government acceptance of the deliverables [SE-30].

4.4.2 The NASA technical team shall participate in product transition as defined in the NASA SEMP or other equivalent program/project documentation [SE-31].



| 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 |

DISTRIBUTION:
NODIS


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.