About this file

This document is a set of questions and answers related to the Commercial SmallSat Data Acquisition (CSDA) Indefinite Delivery Indefinite Quantity (IDIQ) On-Ramp 1 Request for Proposals (RFP) issued by NASA.

The key details are:

  • NASA is conducting an on-ramp to the existing CSDA IDIQ contract to allow new vendors to propose and for existing vendors to propose new data products.
  • Vendors must provide a comprehensive digital catalog of their available data products, including metadata and ancillary information. NASA is interested in data products covering at least 9 continuous months starting after June 1, 2016.
  • Vendors must agree to NASA's defined End User License Agreements (EULAs) to enable broad dissemination and shareability of the data with government agencies and partners.
  • NASA is not currently requiring Federal Information Security Management Act (FISMA) reporting or FIPS 140-2/140-3 encryption from vendors, as the data acquisition is viewed as Software-as-a-Service (SaaS).
  • Vendors can propose future/planned satellites and data products, but the price volume should only include currently available products.
  • The response date for this on-ramp solicitation remains unchanged.

View the file

Other files

Show all 16

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

No. RFP Reference Requirement Question Government Response RFP Change?

1 General General

How exactly are we gathering user requests for data that then translates to a task order and what is the minimum data threshold requested by a single user/multiple users to reach a task order threshold? Is there a defined request threshold ?

Will IDIQ be expanded to include a new form where people will be able to submit the data request? The reason I ask is because sometimes, if researchers are expanding their research work, they have to wait for these requests to be addressed and it impacts their research timeline

In the evaluation period, Principal Investigators (PIs) have been selected to make requests For the future, NASA is evaluating this process to establish minimum data

NASA will still have the authorization form and the initial user request but in the future will modify to add a process to add data requests NASA is also improving communication with the different science teams and will be exploring improvements to the program in the future

No

2 RFP III 11 Technical Volume 2(3), Pg 56

3) The offeror shall demonstrate its ability to provide a comprehensive catalog of its commercial Earth Observation data products in accordance with Section 2 0 of the CSDA IDIQ SOW At a minimum, the data catalog shall include data sets, associated metadata, and ancillary information

For the Comprehensive Data Catalog of Earth Observation Imagery, is an acceptable delivery a Shapefile with image footprints and metadata that show historical archive collections to demonstrate geographic coverage/sampling cadence? The Shape file question relates to the size of the files for very large archives that may extend for over 10 years of collection

Yes, the catalog needs to represent, at the time of proposal submission, all available imagery that is available for NASA to purchase This will be used by NASA to identify utility for specific Earth Science applications

No

3 Attachment B - EULA's Attachment B - EULA's

In the past NASA has allowed other orgs and funding agencies like NSF, DOE, BLM and others to access CSDA data for some vendors will IDIQ expand to these too?

This depends on the EULA requirement explicitly referred to in the requirements in the task order In IDIQ, we have three EULAs; depending on which one is exercised, that will determine who will be allowed access to the data program

No

4 Enclosure 1_ITSMP_Template pdf 1 5 1 Information System Does NASA consider that selected providers are managing an 'external information system containing NASA data' given the earlier definition of NASA data?

NASA is acquiring and purchasing the data but it is not considered NASA funded data that is in the vendor holdings Once the data is purchased from the vendor archive or through tasking and ingested into the NASA system, then the data becomes NASA data See item 7 pertaining to the ITSMP and viewing the vendors as providing Software as a Service (SaaS)

No

5 General General You mention that you may decide to start tasking at some point Can you say a bit more about that? when? or what does it depend on?

At this time, NASA cannot provide any additional information The program is going through a period of reevaluation and determining its direction in the future NASA envisions this as part of our data calls and will communcate to the vendors our program goals as they evolve

No

6 Enclosure 1_ITSMP_Template

3 Federal Information Security Management Act (FISMA) Reporting The contractor shall adhere to the NASA FISMA reporting requirements and provide inputs upon request

Please provide reference information about these reporting requirements

Since there will not be IT systems managed by the vendor, they will not be requested to provide reporting requirements at this time NASA reserves the right to revisit these reporting requirements at which time any expectation to contribute to IT reporting requirements will be conveyed to the vendor

No

7 Enclosure 1_ITSMP_Template Are FIPS 140-2 or FIPS 140-3 required in any way? For Satellite encryption? for all encrypted traffic, including VPNs, WiFi, and SSL web and APIs? for cloud storage?

FIPS certification of cryptographic modules is an absolute requirement for NIST 800-53, NIST 800-171/172 and derived specifications We are not sure of FAR 52 204 21 requires it, and if so, to what crypto it applies

The FIPS 140-2/FIPS 140-3 are not required at this time, since the data acquisition is viewed as a SaaS If NASA makes modifications in the future, this will be revisited No

8 RFP III 11 Technical Volume 2(3)(a), Pg 56 The offeror shall provide a Comprehensive Digital Catalog of its data holdings

If vendor has, say 400 images in an archive, and there are 50 Metadata fields, is NASA expecting a table of 400 rows and 50 columns expressing the holdings?

Yes, the catalog needs to represent all available imagery and metadata that is available for NASA to purchase at the time of proposal submission This will be used by NASA to identify utility for specific Earth Science applications

No

CSDA On-Ramp 1 - RFP Industry Questions (PART II)

9 Attachment B - EULA's Attachment B - EULA's

Does the Government require a company to provide all three EULAs in their RFP submission (US Government, US Government + Partners, and Public Release)? We have concerns about Listed Countries of Particular Concern and/or Special Watch List countries gaining access to Licensed products under the Public Release EULA terms and conditions

All products proposed/incorporated into the contract must be available under all three EULAs If NASA were to exercise the public release EULA, Export ITAR regulations shall apply when applicable This should not affect the data provided The license simply provides us the ability to release from the licensor’s perspective

No

10 General General The size of our Digital Archive file will be very large Are there file size upload restrictions on the NASA website designated for RFP response upload?

Pertaining to the actual data delivery, data shall be delivered in common, community-accepted formats (e g Shapefiles, csv) for easy ingestion into publicly available tools Individual files cannot exceed 150GB per file (see RFP Section III 8 General Instructions (b)(1) and Section III 9 Electronic Submission of Proposals, Paragraph (d))

No

11 RFP III 11 Technical Volume 2(2)(a) & 2(2)(a)(vii), Pg

a) The offeror shall provide detailed information to demonstrate that the data from the satellite constellation cover a period of at least nine (9) continuous months, starting after June 1, 2016 –

For the purposes of this solicitation, should offerors provide detailed technical information and pricing on future/planned satellites and data products, or should the narrative in the response volume only be limited to the satellite(s) meeting the 9 month eligibility requirement?

In accordance with RFP / III 11 Technical Volume 2(2)(a) (vii), "the offeror shall describe in detail plans for future satellites" that will meet the requirements outlined in the

RFP

Pertaining to the Price Volume, the Contract Price List should only include the price for products that are available for purchase at the time of proposal submission

No

12 Attachment A - SOW III Requirements 3 0 3 0 Professional Services and Support Can you please indicate whether response to this SOW component is to be addressed and evaluated?

The offeror needs to demonstrate its competence to successfully complete the requirements specified in the Statement of Work

The evaluation factors are listed in RFP Section IV

No

13 RFP I 23 CSDA On-Ramping (b), Pg 28

(b) " Proposals shall be subject to the same proposal instructions and evaluation procedures as the CSDA Request for Proposal No 80HQTR23R0007 dated March 21, 2023, and its subsequent Amendments dated April 12, 2023, April 21, 2023, and July 18, 2023 "

Can you please direct me to Amendment 3 of solicitation 80HQTR23R0007? I can't seem to locate it on SAM gov

Amendment No 003 dated July 18, 2023, is from the original solicitation No 80HQTR23R0007 and is not provided as it was only for offerors in the competitive range under the original solicitation All applicable changes to the Amendment No 003 solicitation were incorporated into the On-Ramp 1 RFP

No

14 General General We respectfully request the due date be extended to 8 April 2024 At this time, the response date/time remains unchanged No

File details come from the government source that posted it. Updated .