SATPC0040453 Tab 10 Vendor Question_Customer Response.pdf
PDF 63 KB Posted
- Solicitation number
- 80NSSC26926094Q-R1
About this file
This is a Questions and Answers document for NASA contract 80NSSC26926094Q-R1 regarding Technology Research in Horizon Scanning for Strategic Foresight.
The document clarifies requirements for vendors submitting proposals in response to this solicitation. Key requirements include: data may be submitted in any format provided metadata is included with schema allowing traceability for source, veracity, and bias; briefing production typically requires at least 3 interviews per relevant topic, sufficient to capture multiple perspectives; NASA does not have additional budget for subject matter expert interviews, indicating vendors must absorb these costs; "existing data" deliverable due by 6/19/2026 refers to contractor-collected public-source data from scrapes of platforms such as Reddit or Ground News that align with statement of work requirements. Technical acceptability is established through representation of sources (collecting from multiple platforms to reduce demographic bias while documenting over- and under-represented populations), protection of vulnerable groups (using only public intentionally published content, excluding private or semi-private communities, and avoiding data that could identify at-risk individuals), sensitive attribute constraints (stripping personal identifiers at ingestion when possible), documentation and transparency (maintaining clear records of collected data sources and documenting exclusions and limitations), and making collection methods available. Proposals have no specific format requirements—only the minimum necessary to convey methodology clearly is required. Lack of existing data does not render a proposal unacceptable. NASA did not provide publicly available briefing samples in response to vendor inquiries.
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
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
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.
File details come from the government source that posted it. Updated .