Amendment 08 Questions and Answers.docx
DOCX document 16 KB Posted
- Attached to
- Broad Agency Announcement Emerging Technologies Federal contract opportunity
- Solicitation number
- W15QKN-21-R-0ER7
About this file
This document is an Amendment 08 Questions and Answers for Broad Agency Announcement (BAA) W15QKN-21-R-0ER7, issued by the U.S. Army's Combat Capabilities Development Command (DEVCOM) Armaments Center. The Q&A provides guidance to potential offerors about submitting white papers for emerging technologies research and development. Key details include instructions that white papers should focus on describing technical capabilities and potential Army applications, with an emphasis on connecting proposed technologies to broad needs like situational awareness or target identification.
The document clarifies cost expectations for white papers, noting that the Army is seeking rough estimated costs for Proof-of-Concept/Lab Demonstration or Early Prototype Developmental Test levels. Offerors are not expected to provide fully ruggedized hardware at the white paper stage. The BAA is a continuously open announcement for scientific study and experimentation aimed at advancing armament and associated systems technologies, with proposals evaluated for their potential to increase knowledge and understanding within the Armaments Center's technical community. Interested parties can submit white papers throughout the BAA's validity period, with technical questions directed to William R. Sharpe and administrative inquiries to Marcus Edmundson.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| BAA_EMERGING_TECHNOLOGIES_Amendment_10.docx | DOCX document | |
| BAA_EMERGING_TECHNOLOGIES_Amendment_09.pdf | ||
| BAA_EMERGING_TECHNOLOGIES_Amendment_07.pdf | ||
| W15QKN-21-R-0ER7 Amendment 06 Questions and Answers.pdf | ||
| BAA_EMERGING_TECHNOLOGIES_Amendment_05.pdf | ||
| W15QKN-21-R-0ER7 - Amendment 04 Questions-Answers.docx | DOCX document | |
| BAA_EMERGING_TECHNOLOGIES_Amendment_03.docx | DOCX document | |
| BAA_EMERGING_TECHNOLOGIES_Amendment_02_Updated.docx | DOCX document | |
| BAA_EMERGING_TECHNOLOGIES_Amendment_01_Email_Change.DOCX | DOCX document | |
| BAA EMERGING TECHNOLOGIES.DOCX | DOCX document |
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
BAA W15QKN-21-R-0ER7
Questions & Answers:
1. QUESTION: We are developing a system, and think it could be relevant to the AC mission, like fire control, but we don’t have a firm understanding of pain points or how we would be utilized. For the white paper, are we able to just describe technical capabilities, and your team will assess applicability to a variety of your known needs? Or should we establish specific technology insertion points/uses prior to white paper submission?
RESPONSE: You are welcome to focus the white paper on describing the technical capabilities of your system. However, please keep in mind that the more you can connect those capabilities to potential Army needs – even broadly, such as improved situational awareness or target identification – the easier it will be for us to evaluate its relevance.
QUESTION: The white paper calls for a cost portion. We’re unsure how to scope the project; what are representative trajectories of successful programs? Are they laboratory demonstrations? Fully ruggedized hardware? Anything you can provide us to help us understand the types of projects that are appropriate for funding under this BAA would be helpful so that we can craft a responsive white paper!
RESPONSE: We generally look for a rough estimated cost to deliver said capability at the Proof-of-Concept/Lab Demonstration level or at the Early Prototype Developmental Test level. We are not expecting fully ruggedized hardware at the white paper stage. Focus on outlining the costs associated with demonstrating the core functionality and potential of your technology.
File details come from the government source that posted it. Updated .