Attachment 7 - Call 2_DASH QA 1 June 2026.xlsx
XLSX spreadsheet 14 KB Posted
- Attached to
- Call 02 DASH - Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II)
- Solicitation number
- FA238426SB006
About this file
This file is a Question and Answer (Q&A) document addressing inquiries from industry regarding the Decision Advantage Sprint for Human Machine Teaming (DASH) Event, a closed Call 2 under BAA FA2384-26-S-B004 (Solicitation FA2384-26-S-B006). The Q&A clarifies proposal requirements, event logistics, technical specifications, and contract parameters for this Air Force initiative focused on developing Human-Machine Teaming concepts leveraging AI/automation to support Battle Managers.
Key proposal and submission requirements include: full technical and cost proposals (not white papers or rough order of magnitudes) due June 3, 2026, with selections notified around June 18, 2026; the DASH event execution occurs July 13-23, 2026 in Las Vegas and proposals should address only the two-week event demonstration and prototype development, not post-event scaling or lifecycle capability; mandatory attachments include a Technical/Management proposal with Statement of Work, Cost/Business volume, Security Program Questionnaire (Appendix 1), Senior Key Person Profile Worksheet (Appendix 2), Privacy Act forms (Appendix 3), and Section K Representations and Certifications (Attachment 4); proposals must reference both the BAA number and specific Call number; and foreign industry participation is not authorized at the prime contractor level. Event logistics specify that vendors must provide their own compute hardware or use cloud services, with vendors responsible for deploying containerized microservices via their choice of container deployment (including Kubernetes/GKE clusters), accessing scenario information onsite through various methods, and submitting outputs via REST API to the Digital Orchestrator; commercial Wi-Fi is available; and fewer than 10 participants per vendor is preferable due to facility space constraints. Success metrics focus on delivering a working Minimum Viable Product (MVP) with associated lessons learned rather than specific performance targets, with output schemas to be provided by the government.
View the file
Other files
Show all 12
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
Sheet1
| Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) MASH | |||
| Question Number | Document (BAA or Call) | Question | Gov't Answer |
| 1 | BAA | What does success look like for the event demonstrations: which performance measures or evaluation criteria matter most (tempo, accuracy, workload reduction, decision quality, trust, etc.)? | Regarding what success looks like, although we may ask for performance metrics (for example number, time, and quality of solution) success will be a working MVP and associated lesson learned. |
| 2 | BAA | How are you thinking about scoping the first Call(s): specific mission threads, vignettes, or operator workflows you plan to emphasize? | Any potential future calls may vary in the vignettes and decision functions. When relevant, calls may have an Ask Me Anything (AMA) either prior or after the submission deadline that will give an overview of the Transformational Model, specific decision function, and answer any BA technical questions. |
| 3 | BAA | Will the government provide the Transformational Model artifacts, representative data, and any baseline toolchain for teams to integrate against? If so, when and in what form? | Any potential future calls may vary in the vignettes and decision functions. When relevant, calls may have an Ask Me Anything (AMA) either prior or after the submission deadline that will give an overview of the Transformational Model, specific decision function, and answer any BA technical questions. |
| 4 | BAA | What is the expected integration environment for the events (network constraints, data formats, interfaces, any required standards), and what constraints should we design around? | Any potential future calls may vary in the vignettes and decision functions. When relevant, calls may have an Ask Me Anything (AMA) either prior or after the submission deadline that will give an overview of the Transformational Model, specific decision function, and answer any BA technical questions. |
| 5 | BAA | Are there common pitfalls you have seen in prior events that you want performers to avoid? | Any potential future calls may vary in the vignettes and decision functions. When relevant, calls may have an Ask Me Anything (AMA) either prior or after the submission deadline that will give an overview of the Transformational Model, specific decision function, and answer any BA technical questions. |
| 6 | Call | Should the technical and cost proposals for FA2384-26-S-B006 (DASH – PSA Decision Function) be developed strictly for the 2-week DASH event execution and prototype demonstration, or are we expected to propose a full program-level solution (post-event development, scaling, and lifecycle capability) within the submission? | They should be developed strictly for the two week DASH event execution and prototype demonstration. |
| 7 | Call | What are the limitations for foreign companies to participate in this effort? | Foreign industry participation is not authorized at the prime contractor level. |
| 8 | Call | Are offerors expected to submit a full technical and cost proposal, or is submission of the referenced appendices/forms is sufficient for initial consideration? | Offerors are expected to submit a full technical and cost proposal in response to this solicitation. See the Joint All-Domain Transformational Model II BAA announcement on SAM.gov (BAA No. FA2384-26-S-B004) for proposal instructions (in particular, section 5.2). |
| 9 | Call | Which attachments/forms are mandatory at proposal submission (e.g., Appendix 1, Appendix 2, Appendix 3, cost information, technical narrative, etc.). | In addition to the technical/management and cost business volumes, the following attachments are required: Appendix 1 (Security Program Questionnaire), Appendix 2 (Research and Related Senior Key Person Profile Worksheet), Appendix 3 (Privacy Act for Covered Individuals Fillable), and attachment 4 (Section K Representations and Certifications). |
| 10 | Call | Is a Rough Order of Magnitude (ROM) cost estimate acceptable for travel and participation costs? | No. Offerors are expected to submit a full technical and cost proposal in response to this solicitation. |
| 11 | Call | Are there any page limits, preferred formats, or evaluation criteria for technical submission? | See the Joint All-Domain Transformational Model II BAA announcement on SAM.gov (BAA No. FA2384-26-S-B004) sections 5.0 and 6.0. |
| 12 | Call | For the containerized microservices evaluated during the DASH sprint, does the target environment support standard OCI-compliant container deployments (such as a local Kubernetes/GKE cluster) where we can orchestrate a localized application pipeline, and will the local generative AI endpoints be accessible via a standard OpenAI-compatible or REST API gateway? | Vendors will be responsible for the deployment of their developed solution, via their own hardware (such as laptops brought with them). Vendors can utilize the container deployment of their choice. Commercial wifi is available in the facility for vendors to connect to any services they have available to them. Vendors will need to consume scenario information available onsite via various methods and outputs will be submitted to the Digital Orchestrator via a REST API. |
| 13 | Call | What documents are required exactly? | The call was amended 5.26.26 to clearly lay out required documents. These are as follows: |
- Technical/Management proposal (include SOW)
- Cost/Business volume
- Appendix 1 (Security Program Questionnaire)
- Appendix 2 (Research and Related Senior Key Person Profile Worksheet)
- Appendix 3 (Privacy Act for Covered Individuals (1 signed copy for each individual participating in DASH event)
- Attachment 4 (Section K Reps and Certs)
| 14 | Call | What is the vision for the completeness of the services after the two-week event, and is there any follow-on work planned? | The focus is solely on the two-week event. There are no current plans for follow-on work. The developed service should be mature enough for warfighters to use and provide feedback on, but there is no specific Technology Readiness Level (TRL) required. |
| 15 | Call | Could you clarify the dates for the event? | Submissions are due June 3rd. Selection notifications will be sent around June 18th. The DASH event will be held from July 13th to July 23rd in Las Vegas. |
| 16 | Call | Are white papers or Rough Order of Magnitudes (ROMs) required for the submission? | No, full proposals are required. An amendment to the solicitation provides a clear list of all necessary documents. |
| 17 | Call | Is there a limit on the number of participants per vendor? | There is no strict limit, but there are space constraints at the facility. Fewer than 10 participants per vendor is preferable. |
| 18 | BAA | Is there a standard format or page count for the Broad Agency Announcement (BAA) response? | The response should follow the instructions in the JADPACT BAA, referenced in the call. |
| 19 | Call | What is the compute environment at the event location? Do vendors need to bring their own hardware? | Vendors must provide their own compute hardware (e.g., servers) or use cloud services. The facility provides peripherals like monitors and keyboards, as well as commercial Wi-Fi. It is not necessary to detail the compute plan in the proposal, as this will be coordinated after selection. |
| 20 | Call | What is the difference between Posture and Sustain Assets (PSA) and Battle Course of Action (COA) production? | PSA focuses on positioning assets to be ready for potential future (latent) goals and reacting to an unpredictable environment, much like managing "potential energy." Battle COA production is about creating and executing plans for active goals, which is like "kinetic energy." PSA is not a scheduler or a route planner; it determines the desired state for assets to be in. |
| 21 | Call | Will the input and output schemas be provided? | Yes, the government will provide the required output schema for the services. |
| 22 | Call | Will the slides from the presentation be made available? | Yes, the slides will be added as an amendment to the solicitation. |
| 23 | Call | What constitutes a "battle resource"? | A battle resource is anything that can perform work in the operational environment. This includes not just physical platforms like aircraft, but also their specific components like fuel, missiles, sensors, and even non-physical elements like communication paths. |
| 24 | Call | Under the Overview Information section of the BAA 2.0 Solicitation, the Contract/Instrument Types section states: “A Firm Fixed Price Contract is anticipated, however, the Air Force reserves the right to award the instrument best suited to the nature of research proposed, such as any appropriate contract type under the FAR or Other Transaction (OT) for Prototype, grant, cooperative agreement, or OT for Research.” Being that this effort is currently being solicited as an FFP contract type, would contractors still have to include indirect rates and fee? | As stated in section 5.2.1, please follow the proposal instructions in the Joint All-Domain Transformational Model II BAA Announcement (FA2384-26-S-B004) on SAM.gov (which does require a cost element breakdown). |
| 25 | Call | in the narrative, should we be using the BAA number and Title “FA2384-26-S-B004, Joint All-Domain Transformational Model II” or the Solicitation Number and Title “Closed Call No. 2 -- FA2384-26-S-B006, Decision Advantage Sprint for Human Machine Teaming (DASH) Event”? | In the narrative part of your proposal, please reference both the BAA and this specific Call. |
File details come from the government source that posted it. Updated .