07_TO0001_Attachment_2_CDRL.pdf

Rev.: 05/2026

Task Order 0001 Attachment 2 — Contract Data Requirements List Solicitation 80ARC026R0007

CONTRACT DATA REQUIREMENTS LIST

National Aeronautics and Space Administration

Ames Research Center

Task Order 0001 — Snow4Flow 2027 Campaign Startup, under the Commercial Aviation Services IDIQ

DOCUMENT CHANGE LOG

DRD No. DRD Title Revision Date

— Baseline issue Basic [date of award]

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 must govern that data required by the contract.

The contractor must 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 must be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this document. In cases where data requirements are covered by a Federal

Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) clause or other term (e.g., requirements statement), that clause or term must 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. The DRDs included in this CDRL are ordered sequentially as listed in the CDRL page(s) that precede(s) the actual DRDs.

Data Type Description: Each DRD is classified by data type as defined below:

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

Type 2 — NASA reserves a time-limited right to disapprove in writing any submittal of and interim changes to Type 2

DRDs. The contractor must 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 must clearly identify the release target date. If the data is unacceptable, the contracting officer 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 must 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.

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

STATEMENT OF GENERAL REQUIREMENTS

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.

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 must be printable. Data deliverables must be delivered to NASA in the format specified below unless a specific format is required by a DRD. Data submittals must 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 must be transmitted to NASA by email to the Contracting Officer and the Contracting Officer’s

Representative, or by another mechanism agreed to by the CO, the COR, and the project representatives responsible to receive, index, and store the data deliverables. If email is used to transmit data deliverables, the email size must be 10 megabytes or less to ensure receipt by the NASA email servers. Encrypted email format must be used to transmit data.

Data Transmittal Package: Each data transmittal package must include a transmittal memorandum that specifies the following:

● Contract number

● Data Requirements Description (DRD) number

● DRD data type

● Submission date or milestone being satisfied

● Document number and revision

● Document title

● File names of all files being delivered; file naming convention must clearly identify the document being delivered

● NASA Records Retention Schedule (NRRS) number, if applicable (see NRRS 1441.1)

Document Identification: For all data types, the document number, change legend, date, and title constitute the minimum identification of the specific document and must appear on the cover and title page. The contract number must also appear on the cover and title page as separate markings. The originator and organization must be included on the title page. The document number, change legend, and date must appear on each page of the document. All Type 1 documentation must be marked “PRELIMINARY PENDING NASA APPROVAL,” and once approved must be reissued with “APPROVED BY

NASA” and the date and approval authority annotated on the cover.

Data Restriction Determination and Marking Requirements: The contractor must 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 must 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 must 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 must 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 must 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 must be brought up to date and must incorporate revised pages. All revisions must be recorded. A revision log must identify complete reissues except for periodic reports and documents which are complete within themselves as final. Individual page revisions must 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, and similar matters must only be made when a substantial change is made, unless the accuracy of the document is affected. All revised pages must be identified by a revision identifier and a new date. Each document must contain a log of revised pages that identify the revision status of each page with the revision symbol. This list must follow the table of contents in each document. The line or lines revised on a given page must be designated using a vertical line in the margin of the page, and the change authority must be indicated adjacent to the change.

CDRL/DRD MAINTENANCE PROCEDURES

NASA-Initiated Change: New and/or revised data requirements must be incorporated by contract modification to which the new or revised portion must be appended. The contractor must 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.

TASK ORDER 0001 CONTRACT DATA REQUIREMENTS LIST

The data items below are ordered under Task Order 0001. Content, data type, and OPR for each DRD are governed by

Attachment J-2 of the basic contract, which controls in the event of any conflict; the submission events stated below apply to this task order.

DRD No. DRD

Type DRD Title OPR Submission event — Task Order 0001

DRD-01 3 Flight Operations Report GSFC Code 615

(COR)

Within 10 calendar days after completion of

Phase 2; supports milestone M2 acceptance.

DRD-02 3 Flight and Maintenance Logs GSFC Code 615

(COR)

With each milestone invoice under this task order.

DRD-03 2 Safety and Health Plan ARC Code SG (CO) /

COR

Contract-level deliverable under Attachment

J-2; must be in place before any flight operation under this task order.

DRD-04 3 Certificates of Insurance ARC Code SG (CO) Before the first flight under this task order.

DRD-05 2 Aircraft Modification and

Airworthiness Documentation GSFC Code 615

(COR)

Before Phase 2 transit; supports milestone

M1 acceptance.

DRD-06 3 Use, Maintenance, Repair

Data and Instructions

(UMRDI)

OP Applies upon delivery of any covered items;

no deliveries anticipated under this task order.

DRD-07 3 Post-Deployment Report GSFC Code 615

(COR)

Within 15 calendar days after March 2, 2027.

DRD-08 2 Information Technology

Security Plan or Attestation ARC Code SG (CO), with Center CISO Contract-level deliverable under

Attachment J-2; initial submission within

30 calendar days after contract award.

DATA REQUIREMENTS DESCRIPTIONS — TASK ORDER 0001

DRD-01 — Flight Operations Report

1. DRD Title: Flight Operations Report

2. DRD No.: DRD-01 3. Data Type: Type 3 4. OPR: GSFC Code 615 (COR)

5. Solicitation No.: 80ARC026R0007 6. Contract No.: [at award]

7. Date Issued: [date of award] 8. Date Revised: — 9. DRD Category: Technical ☒

Administrative ☐ S&MA ☐

10. Description/Use: Summary of flight operations conducted under each active task order, used by the Government to monitor performance, verify quantities invoiced against catalog rates, and support task order acceptance.

11. Distribution: Contracting Officer and Contracting Officer’s Representative. Initial Submission: Within 10 calendar days after completion of Phase 2; supports milestone M2 acceptance. Submission Frequency: Per task order as specified in the task order; at minimum upon completion of each campaign segment. Format: Contractor format. Interrelationship: Attachment J-1

Statement of Work paragraphs 3 and 5; CLIN 0001. Task Order 0001; Attachment J-2 Payment Milestone Schedule.

Applicable Documents: Applicable task order.

12. Scope: All flight operations performed under the applicable task order.

13. Contents: Flights conducted with dates; flight hours by category; aircraft days by category (home base and away/deployed);

science flight lines completed; significant events, deviations, and weather or maintenance aborts; and the upcoming schedule.

14. Remarks: Quantities reported must reconcile to quantities invoiced under CLIN 0001. Content per Attachment J-2, DRD-

01.

15. Maintenance: Changes incorporated by complete reissue of the affected report.

DRD-02 — Flight and Maintenance Logs

1. DRD Title: Flight and Maintenance Logs

2. DRD No.: DRD-02 3. Data Type: Type 3 4. OPR: GSFC Code 615 (COR)

5. Solicitation No.: 80ARC026R0007 6. Contract No.: [at award]

7. Date Issued: [date of award] 8. Date Revised: — 9. DRD Category: Technical ☒

Administrative ☐ S&MA ☐

10. Description/Use: Copies of aircraft flight and maintenance log entries for the period of performance, used to substantiate flight hours and aircraft days invoiced and to document airworthiness status during NASA-supported operations.

11. Distribution: Contracting Officer’s Representative; Contracting Officer upon request. Initial Submission: With each milestone invoice under this task order. Submission Frequency: With each invoice. Format: Contractor standard commercial format. Interrelationship: Attachment J-1 Statement of Work paragraphs 3 and 4; CLIN 0001; FAR 52.212-4(i). Task Order

0001; Attachment J-2 Payment Milestone Schedule. Applicable Documents: Operator’s approved maintenance program;

applicable civil aviation authority requirements.

12. Scope: Aircraft assigned to performance under the contract for the period covered by the invoice.

13. Contents: Flight log entries showing date, route, block and flight times, and crew; maintenance log entries showing inspections performed, discrepancies, and corrective actions affecting availability during the period.

14. Remarks: Proprietary or personally identifiable information may be redacted provided the redaction does not impair verification of invoiced quantities. Content per Attachment J-2, DRD-02.

15. Maintenance: Delivered as generated; no reissue required.

DRD-03 — Safety and Health Plan

1. DRD Title: Safety and Health Plan

2. DRD No.: DRD-03 3. Data Type: Type 2 4. OPR: ARC Code SG (CO) / COR

1. DRD Title: Safety and Health Plan

5. Solicitation No.: 80ARC026R0007 6. Contract No.: [at award]

7. Date Issued: [date of award] 8. Date Revised: — 9. DRD Category: Technical ☐

Administrative ☐ S&MA ☒

10. Description/Use: The contractor’s plan for the safe conduct of flight and ground operations under the contract, including operations with NASA personnel aboard the aircraft as qualified non-crewmembers and operations at remote Arctic deployment locations.

11. Distribution: Contracting Officer and Contracting Officer’s Representative. Initial Submission: Contract-level deliverable under Attachment J-2; must be in place before any flight operation under this task order. Submission Frequency: Once after award; updated when operations, aircraft configuration, or deployment locations change materially. Format: Contractor format addressing the content elements below. Interrelationship: Attachment J-1 Statement of Work paragraph 4; NPR 7900.3; NAII

7900.3. Task Order 0001; Attachment J-2 Payment Milestone Schedule. Applicable Documents: Operator’s safety management system documentation; applicable civil aviation authority requirements; NPR 7900.3.

12. Scope: All flight and ground operations performed under the contract, including deployed operations.

13. Contents: Safety management system summary; crew qualification, currency, and duty/rest limitations; risk assessment and mitigation for polar and remote-area operations; procedures for carriage of NASA science personnel as qualified non-crewmembers; emergency response, search and rescue coordination, and survival equipment; ground safety at deployment sites including fueling operations; and mishap notification and reporting procedures.

14. Remarks: The Government reserves a 30 calendar day right of disapproval from the date of submission. Flight operations may not commence until the plan is in place. Content per Attachment J-2, DRD-03.

15. Maintenance: Changes incorporated by complete reissue; the Government right of disapproval applies to each reissue.

DRD-04 — Certificates of Insurance

1. DRD Title: Certificates of Insurance

2. DRD No.: DRD-04 3. Data Type: Type 3 4. OPR: ARC Code SG (CO)

5. Solicitation No.: 80ARC026R0007 6. Contract No.: [at award]

7. Date Issued: [date of award] 8. Date Revised: — 9. DRD Category: Technical ☐

Administrative ☒ S&MA ☐

10. Description/Use: Evidence of the aviation liability and hull insurance coverage required by the contract, including coverage applicable to NASA personnel aboard the aircraft as qualified non-crewmembers and to the third-party instrument suite while installed on the aircraft.

11. Distribution: Contracting Officer; copy to the Contracting Officer’s Representative. Initial Submission: Before the first flight under this task order. Submission Frequency: Upon initial submission and upon each policy renewal or material change during the ordering period. Format: Insurer’s standard certificate of insurance. Interrelationship: Attachment J-1 Statement of

Work paragraphs 4.5 and 4.8; FAR 52.212-4. Task Order 0001; Attachment J-2 Payment Milestone Schedule. Applicable

Documents: Applicable policy documents upon request of the Contracting Officer.

12. Scope: All aircraft and operations performed under the contract.

13. Contents: Named insured; policy numbers and effective dates; coverage types and limits including aviation liability, passenger liability, and hull; territorial limits covering the campaign deployment locations; and confirmation of coverage or endorsement addressing the furnished instrument suite in the contractor’s care, custody, and control.

14. Remarks: The contractor must notify the Contracting Officer of cancellation, non-renewal, or material reduction in coverage. Content per Attachment J-2, DRD-04.

15. Maintenance: Superseded certificates replaced upon renewal.

DRD-05 — Aircraft Modification and Airworthiness Documentation

1. DRD Title: Aircraft Modification and Airworthiness Documentation

2. DRD No.: DRD-05 3. Data Type: Type 2 4. OPR: GSFC Code 615 (COR)

1. DRD Title: Aircraft Modification and Airworthiness Documentation

5. Solicitation No.: 80ARC026R0007 6. Contract No.: [at award]

7. Date Issued: [date of award] 8. Date Revised: — 9. DRD Category: Technical ☒

Administrative ☐ S&MA ☐

10. Description/Use: Documentation of the aircraft modifications performed to accommodate the instrument suite and the associated airworthiness approvals, used by the Government to verify the science configuration and to support the NASA airworthiness review process.

11. Distribution: Contracting Officer’s Representative; Contracting Officer; NASA airworthiness review authority as directed.

Initial Submission: Before Phase 2 transit; supports milestone M1 acceptance. Submission Frequency: Upon completion of each modification affecting the science configuration. Format: Contractor and civil aviation authority standard formats.

Interrelationship: Attachment J-1 Statement of Work paragraphs 3 and 4; NAII 7900.3; CLIN 0001. Task Order 0001;

Attachment J-2 Payment Milestone Schedule. Applicable Documents: Instrument interface control documentation furnished as

Government-furnished information; applicable civil aviation authority approval requirements.

12. Scope: All modifications to the contract aircraft performed to accommodate the instrument suite.

13. Contents: Description of modifications performed; drawings or installation data as applicable; weight and balance data for the modified configuration; supplemental type certificate, field approval, or equivalent civil aviation authority approval documentation; interface verification results against the interface control documentation; and airworthiness release or return-to-service documentation for the configured aircraft.

14. Remarks: The Government reserves a 30 calendar day right of disapproval from the date of submission. This DRD supports the NASA Airworthiness Review Board process; it does not substitute for civil aviation authority approval. Content per

Attachment J-2, DRD-05.

15. Maintenance: Changes incorporated by complete reissue of the affected documentation.

DRD-06 — Use, Maintenance, Repair Data and Instructions (UMRDI)

1. DRD Title: Use, Maintenance, Repair Data and Instructions (UMRDI)

2. DRD No.: DRD-06 3. Data Type: Type 3 4. OPR: OP

5. Solicitation No.: 80ARC026R0007 6. Contract No.: [at award]

7. Date Issued: [date of award] 8. Date Revised: — 9. DRD Category: Technical ☒

Administrative ☐ S&MA ☐

10. Description/Use: This DRD is for the delivery of use, maintenance, repair data and instructions (UMRDI) to the

Government.

11. Distribution: As stated in the contract. Initial Submission: Applies upon delivery of any covered items; no deliveries anticipated under this task order. Submission Frequency: Once, upon initial delivery. Format: Standard commercial format

(when applicable). Interrelationship: Attachment J-1 Statement of Work; right to repair requirements of the contract. Task

Order 0001; Attachment J-2 Payment Milestone Schedule. Applicable Documents: As identified in the contract.

12. Scope: Covered items delivered under the contract, if any.

13. Contents: A list of covered items delivered under the contract, and upon request the use, maintenance, repair data and instructions necessary to diagnose, maintain, repair, reconstruct, remanufacture, re-flash, or rebuild the delivered items, in the contractor’s standard commercial format.

14. Remarks: This is an agency-wide DRD. This acquisition is for services; no end items are anticipated to be delivered. The

DRD applies if covered items are delivered under any task order. Content per Attachment J-2, DRD-06.

15. Maintenance: Changes incorporated by complete reissue.

DRD-07 — Post-Deployment Report

1. DRD Title: Post-Deployment Report

2. DRD No.: DRD-07 3. Data Type: Type 3 4. OPR: GSFC Code 615 (COR)

5. Solicitation No.: 80ARC026R0007 6. Contract No.: [at award]

1. DRD Title: Post-Deployment Report

7. Date Issued: [date of award] 8. Date Revised: — 9. DRD Category: Technical ☒

Administrative ☐ S&MA ☐

10. Description/Use: Final report of each campaign deployment, used by the Government to close out the task order, capture lessons learned, and inform planning for subsequent campaigns.

11. Distribution: Contracting Officer’s Representative and Contracting Officer. Initial Submission: Within 15 calendar days after March 2, 2027. Submission Frequency: Once per campaign deployment task order. Format: Contractor format.

Interrelationship: Attachment J-1 Statement of Work paragraphs 3 and 5; applicable task order. Task Order 0001; Attachment

J-2 Payment Milestone Schedule. Applicable Documents: Applicable task order; DRD-01 reports for the deployment.

12. Scope: The complete deployment covered by the applicable task order.

13. Contents: Summary of operations conducted; total flight hours and aircraft days by category; science objectives supported;

maintenance and reliability summary including aborts and delays; issues encountered and resolutions; instrument installation and removal summary and confirmation of instrument return; and recommendations for subsequent campaigns.

14. Remarks: Report supports final invoice acceptance for the task order. Content per Attachment J-2, DRD-07.

15. Maintenance: Changes incorporated by complete reissue.