Final RFP Attachment J - Contract Data Requirements List (CD.pdf
PDF 333 KB Posted
- Attached to
- Program and Analysis Control (PAAC VI) Support Services - Final Request for Propopsal (RFP) Federal contract opportunity
- Solicitation number
- 80GSFC24R0042
About this file
This document is a Contract Data Requirements List (CDRL) for a NASA Goddard Space Flight Center contract (RFP Number: 80GSFC24R0042). The CDRL outlines four specific data deliverables required from the contractor, categorized by data type and office of primary responsibility: 1) Organizational Conflicts of Interest (OCI) Plan (Office of Procurement), 2) Security Requirements for Unclassified IT Resources (OCIO), 3) Commercial Information Technology Authorizations Report (CITAR) (OCIO), and 4) Limitations on Subcontracting Report (Office of Procurement).
The document provides detailed guidelines for data submission, including electronic format preferences (PDF and native Microsoft file formats), transmittal procedures, and documentation requirements. Key specifications include using encrypted email for transmission, limiting email size to 10 megabytes, and including a comprehensive transmittal memorandum with each data package. The CDRL also establishes procedures for document revisions, data restriction markings, and NASA-initiated changes to the requirements, with different approval levels for Type 1, 2, and 3 data deliverables.
View the file
Other files for this federal contract opportunity
Show all 50
Program and Analysis Control (PAAC VI) Support Services - Final Request for Propopsal (RFP) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ATTACHMENT J
CONTRACT DATA REQUIREMENTS LIST
NATIONAL AERONAUTICS AND SPACE ADMINISTRATION
GODDARD SPACE FLIGHT CENTER
APRIL 2025
RFP NUMBER: 80GSFC24R0042
CONTRACT NUMBER: TBD
J-3
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.
Format
Electronic Format: Electronic submission of data deliverables is preferred. 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 DRD. 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.
Transmittal: Data shall be transmitted to NASA by email or other mechanism agreed to by the Contracting Officer, Contracting Officer’s Representative (COR), and project representatives who are responsible to receive, index, and store the data deliverables.
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.
Data Transmittal Package: Each data transmittal package shall include a transmittal memorandum that specifies the following:
1. Contract number
2. Data Requirements Description (DRD) number
3. DRD data type
4. Submission date or milestone being satisfied
5. Document number and revision
6. Document title
7. File names of all files being delivered; file naming convention shall clearly identify the document being delivered
8. NASA Records Retention Schedule (NRRS) number, if applicable (See NRRS 1441.1, NASA Records
Retention Schedules)
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 documentation shall be marked “PRELIMINARY PENDING NASA APPROVAL,” and once approved shall be reissued with “APPROVED BY NASA” and the date and approval authority annotated on the cover.
Data Restriction Determination and Marking Requirements: The Contractor shall properly mark data in accordance with the 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
J-4 restriction, the CO shall return the data to the Contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the “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.
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.
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.
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.
File details come from the government source that posted it. Updated .