SATPC0040453 Tab 10 Vendor Question_Customer Response.pdf
PDF 70 KB Posted
- Solicitation number
- 80NSSC26926094Q-R1
About this file
This document is a Questions and Answers response file for NASA contract 80NSSC26926094Q-R1 titled "Technology Research in Horizon Scanning for Strategic Foresight." The file contains clarifications from NASA addressing vendor inquiries regarding data submission requirements, interview protocols, subject matter expert compensation, technical acceptability standards, and proposal formatting expectations. Regarding data submission, NASA clarified that "existing data" refers to any data already collected from sources such as Reddit or Ground News that align with Statement of Work requirements, rather than NASA-provided data or pre-award contractor collection. Data can be submitted in any format provided metadata is included and the schema allows traceability for source, veracity, bias, and future fields. For briefing production, at least three interviews per relevant topic are typically conducted, sufficient to capture variability and multiple perspectives. NASA confirmed it has no additional budget for subject matter expert interviews, indicating they must be conducted with volunteers.
Technical acceptability is established through five primary criteria: representation of sources through collection from multiple platforms to reduce demographic bias with documented over- and under-representation analysis; protection of vulnerable groups by using only public, intentionally published content and avoiding private or semi-private communities; sensitive attribute constraints requiring personal identifier stripping at ingestion; documentation and transparency maintaining clear records of data collection sources, exclusions, and known limitations; and availability of collection methods. NASA specified that no specific proposal format, past performance documentation, or preferred technical architectures are required—only sufficient information to clearly convey methodology. The customer indicated preference for direct engagement without multiple subcontracting interfaces due to operating in a lean environment, and emphasized that a production-ready data solution, not a prototype or pilot, is expected.
View the file
Other files
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
Vendor Questions and Customer Response - 80NSSC26926094Q-R1
Technology Research in Horizon Scanning for Strategic Foresight
Vendor 1 Questions:
1. Please provide details on the MADI format and preferred data submission method and desired visualization support.
a. Data can be in any format as long as meta data is included and the schema allows for traceability for source, veracity, bias and other fields that may be added later.
2. Historically, how many interviews are typically conducted in the production of a “briefing”?
a. At least 3 per relevant topic but sufficient to cover the variability in the topic (to capture multiple perspectives).
3. Are the subject matter experts who are interviewed paid or volunteers?
a. NASA does not have additional budget for interviews.
4. What is the “existing data” referenced the deliverables section that must be submitted by 6/19/2026?
a. Any data that already exists from scrapes of Reditt or Ground News or similar sources that align with the statement of work requirements for data. See 5.
5. How will technically acceptable be established?
a. Representation of Sources
i. Collect data from multiple platforms to reduce demographic bias.
ii. Document who is likely over-represented or under-represented on each platform.
iii. Avoid relying on a single social media ecosystem.
b. Protection of Vulnerable Groups
i. Use only public, intentionally published content.
ii. Do not scrape private, closed, or semi-private communities.
iii. Avoid collecting data that could identify or expose at-risk individuals or groups.
c. Sensitive Attribute Constraints
i. Strip personal identifiers at the point of ingestion when possible.
d. Documentation and Transparency
i. Maintain clear records of what data was collected and from where.
ii. Document exclusions, gaps in representation, and known limitations of each source.
e. Make collection methods available
6. What proposal format, past performance etc is requested or required?
a. No requirement – minimum required to convey method clearly
7. If we do not have the “existing data” referenced in question 4, will that make our quote unacceptable?
a. See 4.
8. Are there any publicly available briefings that you can share or direct me to?
Vendor 2 Questions:
1. For the deliverable labeled "Existing data (by 6/19/2026)," does "existing data" refer to NASA-provided data, contractor-collected public-source data gathered after award, or existing public-source datasets the contractor is expected to identify and prepare for Madi ingestion prior to award?
a. Any data that already exists from scrapes of Reditt or Ground News or similar sources (social listening) that align with the statement of work requirements for data.
b. Representation of Sources
i. Collect data from multiple platforms to reduce demographic bias.
ii. Document who is likely over-represented or under-represented on each platform.
iii. Avoid relying on a single social media ecosystem.
c. Protection of Vulnerable Groups
i. Use only public, intentionally published content.
ii. Do not scrape private, closed, or semi-private communities.
iii. Avoid collecting data that could identify or expose at-risk individuals or groups.
d. Sensitive Attribute Constraints
i. Strip personal identifiers at the point of ingestion when possible.
e. Documentation and Transparency
i. Maintain clear records of what data was collected and from where.
ii. Document exclusions, gaps in representation, and known limitations of each source.
f. Make collection methods available
2. Is there a required Madi ingestion schema, API specification, file format, metadata field list, or sample template available to offerors? If not available pre-award, should offerors propose a standards-based export format with source traceability, PESTELE tags, capability-domain tags, and Maslow-alignment fields?
g. Data can be in any format as long as meta data is included and the schema allows for traceability for source, veracity, bias and other fields that may be added later.
Vendor 3 Question:
1. Inquiring if you are currently seeking data providers who can offer the intelligence required to meet the specifications outlined in this RFQ. If so, I would appreciate any details you can share about the types of intelligence or data you are looking for, as well as any specific requirements or preferred criteria for providers. This information will help us determine how best we can support your objectives.
Customer Response: The requirements for intelligence are as described in the SOW.
Vendor 4 Questions:
1. Are there any preferred technical architectures, platforms, or interoperability standards the customer expects vendors to align with?
h. Data can be in any format as long as meta data is included and the schema allows for traceability for source, veracity, bias and other fields that may be added later.
i. Representation of Sources
i. Collect data from multiple platforms to reduce demographic bias.
ii. Document who is likely over-represented or under-represented on each platform.
iii. Avoid relying on a single social media ecosystem.
j. Protection of Vulnerable Groups
i. Use only public, intentionally published content.
ii. Do not scrape private, closed, or semi-private communities.
iii. Avoid collecting data that could identify or expose at-risk individuals or groups.
k. Sensitive Attribute Constraints
i. Strip personal identifiers at the point of ingestion when possible.
l. Documentation and Transparency
i. Maintain clear records of what data was collected and from where.
ii. Document exclusions, gaps in representation, and known limitations of each source.
m. Make collection methods available
9. Is the customer prioritizing a prototype, pilot capability, or production-ready operational solution
a. we are asking for a production ready solution (data).
10. Are there any anticipated security, compliance, or accreditation requirements beyond standard federal contracting expectations? 4. Does the customer anticipate future scalability or follow-on phases associated with this requirement?
a. Refer to answers for 2.
11. Are teaming arrangements or subcontracting structures acceptable within this procurement?
a. We are operating in a lean environment so would prefer fewer interfaces.
File details come from the government source that posted it. Updated .