NASA Procedures and Guidelines
This Document is Obsolete and Is No Longer Used. Check the NODIS Library to access the current version: http://nodis3.gsfc.nasa.gov
NPR 7123.1B Eff. Date: April 18, 2013 Cancellation Date:	NASA Systems Engineering Processes and Requirements (Updated w/Change 4)
| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | ALL |

Chapter 4. NASA Systems Engineering Activities on Contracted Projects

4.1 Introduction

4.1.1 Oversight/insight of projects where prime or other external contractors do the majority of the development effort has always been an important part of NASA programs and projects. "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 only be delegated by the contracting officer. The activities listed in Paragraph 4.2 will be coordinated with the cognizant contracting officer. Detailed definitions for insight and oversight are provided in the NASA Federal Acquisition Regulation Supplement, subpart 1846.4, Government Contract Quality Assurance.

4.1.2 This chapter defines a minimum set of technical activities and requirements for a NASA project technical team to perform before contract award, during contract performance, and upon completion of the contract on projects where prime or external contractors do the majority of the development effort. 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.

4.2 Activities 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 [SE-24]. The content of Appendix D should be used as a guide.

4.2.2 The NASA technical team shall use common technical processes, as implemented by the Center's documentation, to establish the technical inputs to the Request for Proposal (RFP) appropriate for the product to be developed, including product requirements and Statement of Work tasks [SE-25].

4.2.3 The NASA technical team shall determine the technical work products to be delivered by the offeror or contractor, to include a contractor SEMP that specifies the contractor's systems engineering approach for requirements development; technical solution definition; design realization; product evaluation; product transition; and technical planning, control, assessment, and decision analysis [SE-26].

4.2.4 The NASA technical team shall provide the requirements for technical insight and oversight activities planned in the NASA SEMP to the contracting officer for inclusion in the RFP [SE-27].

Note: Care should be taken that no requirements or solicitation information is divulged prior to the release of the solicitation by the contracting officer.

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

4.3 During Contract Performance

DISTRIBUTION:
NODIS