Exhibit C - Contract Data Requirements List.pdf

Exhibit C Contract Data Requirements List Final RFP: 80LARC23R0015

1-1

Exhibit C

CONTRACT DATA REQUIREMENTS LIST

National Aeronautics and Space Administration

Langley Research Center

1-2

DOCUMENT CHANGE LOG

DRD

No.

DRD Title Revision Date

1 INTRODUCTION

This document defines the requirements for contractual data to be delivered by the Contractor to the Government. The data requirements are set forth in each Data Requirements Description (DRD) and shall govern that data required by the contract. The Contractor shall furnish data defined by the DRDs as listed on the Contract Data Requirements List (CDRL) by category of data, attached hereto, and made a part of this contract. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this document and each task order. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR), NASA FAR Supplement (NFS) clause or other terms (e.g., ITAR/EAR), that clause or classification shall take precedence over the DRD.

Contract Data Requirements List (CDRL): Throughout the performance of the contract, the CDRL provides a listing by number, data type, title, and Office of Primary Responsibility (OPR).

Data Requirements Description (DRD): Each DRD included in this CDRL prescribes content, format, and submittal requirements.

1.1 Data Type Description:

Each DRD is classified by data type as defined below:

Table 1: DRD Classification

Type Description

All submittals of and interim changes to Type 1 DRDs require written approval from the Contracting Officer before formal release for use or implementation.

NASA reserves a time-limited right to disapprove in writing any submittal of and interim changes to Type 2 DRDs. The Contractor shall submit the required data to NASA for review within the time period established in the DRD prior to its release for use or implementation. The Contractor shall clearly identify the release target date. If the data is unacceptable, the

Contracting Officer or Contracting Officer's Representative will notify the Contractor within the time period established in the DRD from the date of submission, regardless of the intended release date. The Contractor shall resubmit the information for reevaluation if disapproved. The submittal is considered approved if the Contractor does not receive disapproval or an extension request from the Contracting Officer within the time period established in the DRD.

3 Type 3 DRDs shall be delivered as required by the contract and do not require NASA approval.

2 STATEMENT OF GENERAL REQUIREMENTS

2.1 Subcontractor Data Requirement

The Prime Contractor is responsible for flowing down any specific data requirements that apply to subcontracts and vendor agreements.

Reference to subcontractor data in the Contractor’s responses is permissible and a copy of the referenced subcontractor data must be supplied with the response document at time of delivery to NASA.

2.2 Data Distribution, Format, and Transmittal

Distribution: Distribution recipients and number of copies are identified within each DRD, provided within the contract, or as directed by the Contracting Officer (CO).

Electronic Format: Electronic submission of data deliverables is required. Electronic deliverables shall be printable. Data deliverables shall be delivered to NASA in the format specified below unless a specific format is required by a task order. Data submittals shall consist of a single Adobe Acrobat PDF file and the native format electronic file(s). The preferred native formats include Microsoft Word, Excel, or PowerPoint, as appropriate.

Hardcopy Format: Hardcopy of data deliverables is not required unless electronic delivery is not possible OR practical.

Transmittal: Data shall be transmitted to NASA via the method specified within each task order. These methods include email transmission and/or file sharing services (FSS) such as: (1) the Digital Balance Library (DBL) via aeroCOMPASS, (2) the Balance Server via aeroCOMPASS, (3) Microsoft 365© OneDrive, or (4) Enterprise File and Sync Share (EFSS) Box. See Table 2 for the delivery method for each DRD.

If email is used to transmit data deliverables, the email size shall be 10 megabytes or less to ensure receipt by the NASA email servers. Encrypted email format shall be used to transmit data.

2.3 Document Identification:

For all data types, the document number, change legend, date, and title constitute the minimum identification of the specific document and shall appear on the cover and title page. The contract number shall also appear on the cover and title page as separate markings. The originator and organization shall be included on the title page. The document number, change legend, and date shall appear on each page of the document.

All Type 1 and 2 documentation shall be marked (watermark or otherwise) “PRELIMINARY PENDING NASA APPROVAL,” and once approved shall be reissued with “APPROVED BY NASA” and the date and approval authority annotated on the cover.

2.4 Data Restriction Determination and Marking Requirements

The Contractor shall properly mark data in accordance with the controlled unclassified information (CUI) and data rights clause(s) included in the contract. The Contractor must make a determination for each individual data deliverable, and shall not apply a default or blanket data restriction marking to all data deliverables (e.g., “data may be export restricted”). If NASA does not agree with the Contractor-applied data restriction, the CO or COR will return the data to the Contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the CUI or data rights clause(s) contained in the contract.

Reference to Other Documents and Data Deliverables in Data Submittals: All referenced documents shall be made readily available to the cognizant NASA organization upon request.

2.5 Document Revisions

Revisions of documentation previously submitted may be accomplished either by individual page revision or by a complete reissue of the document.

A document shall be completely reissued when, in the opinion of the Contractor and/or NASA, the document has been revised to the extent that it is unusable in its present state, or when directed by the CO. When complete reissues are made, the entire contents of the document shall be brought up to date and shall incorporate revised pages. All revisions shall be recorded. A revision log shall identify complete reissues except for periodic reports and documents which are complete within themselves as final.

Individual page revisions shall be made as deemed necessary by the Contractor or as directed by the CO.

Changes of a minor nature to correct obvious typing errors, misspelled words, etc., shall only be made when a substantial change is made, unless the accuracy of the document is affected.

All revised pages shall be identified by a revision identifier and a new date. Each document shall contain a log of revised pages that identify the revision status of each page with the revision symbol. This list shall follow the table of contents in each document. The line or lines revised on a given page shall be designated using vertical line in the margin of the page, and the change authority shall be indicated adjacent to the change.

3 CDRL/DRD MAINTENANCE PROCEDURES

NASA-Initiated Change: New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion shall be appended. The Contractor shall notify the CO in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision is appended.

3.1 CDRL or DRD Change Procedures

Revisions to the CDRL or DRDs will be identified by NASA in the Document Change Log.

The date of the revision, DRD number, title, and revision description will be annotated in the Document Change Log. Revision descriptions will include the modification number, which implements the change, and a brief description of the portions of the CDRL and/or DRD affected within the “Revision” column of the Document Change Log.