Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) MASH_QA_02_26_26.xlsx
XLSX spreadsheet 12 KB Posted
- Attached to
- Call 01 MASH - Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) Federal contract opportunity
- Solicitation number
- FA238426SB005
About this file
This file is a Questions and Answers document for the Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) Broad Agency Announcement (BAA FA238426SB004) and its associated Call 01 MASH solicitation (FA238426SB005). The Q&A addresses 13 key questions from potential proposers regarding participation, submission requirements, evaluation criteria, and technical scope.
Key details include: participation is open to all interested vendors, not limited to prior DASH event participants; proposals must include technical and cost components along with a Statement of Work (SOW); required attachments are Appendix 2 (Security Program Questionnaire), Appendix 3 (Research and Related Senior Key Personnel Profile Worksheet), Appendix 4 (AFRL Privacy Act for Covered Individuals), and Attachment 4 (Reps and Certs); success will be measured by a working Minimum Viable Product (MVP) and associated lessons learned rather than specific performance metrics; and the event scenario focuses on Control and Reporting Center/Contingency Response Element (CRC/CRE) Battle Management operations. The Multi Decision Advantage Sprint for Human-Machine Teaming (MASH) event is tentatively scheduled for May 4-15, 2026 at the Howard Hughes Operations (H2O) Center in Las Vegas, Nevada. The government indicated that specific details regarding the Transformational Model, representative data, baseline toolchain, integration environment, and vignettes will be provided through Ask Me Anything (AMA) sessions prior to or after the submission deadline.
View the file
Other files for this federal contract opportunity
Show all 12
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
Sheet1
| Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) MASH | |||||
| Question Number | Document (BAA or Call) | Section | Page Number | Question | Gov't Answer |
| 1 | Call | How does a company respond to the call? | Review the Proposal Submission Section within the Announcement: Joint All Domain Persistent Adaptive Collaborative Technologies II | ||
| 2 | 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.)? | Regrading 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. | ||
| 3 | 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. | ||
| 4 | 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. | ||
| 5 | 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. | ||
| 6 | 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. | ||
| 7 | Call | Is participation limited to vendors who previously participated in the DASH events or are otherwise part of an existing cohort under the parent BAA. | Participation is NOT limited to vendors who previously participated in the DASH events or are otherwise part of an existing cohort under the parent BAA. We encourage any who are interested to submit a proposal in accordance with the BAA and the Call. | ||
| 8 | Call | What is a Closed Call? | A Closed Call is a 1-step request for proposals that allow for submittal at a specified date and time as specified in the Call. To clarify, a full technical and cost proposal is due at the specified date and time as outlined in the Call. |
Please read through the BAA and Call, specifically the Proposal and Submission Information to read through the information required.
| 9 | Call | Please confirm the “Joint All-Domain Transformational Model II BAA” is the same thing as “Broad Agency Announcement: Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II)” (FA238426SB004). | Confirm, this is correct. |
| 10 | Call | Please confirm that “resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal” in addition to Appendix 3, Research and Related Senior and Key Personnel Profile Worksheet. | Confirm, this is correct. |
| 11 | Call | Please confirm that a SOW is not required for this response, understanding the request for “technical and cost proposals” within Section 2.1 of the Call for Proposals document. | SOW is required for evaluation of effort proposed |
| 12 | Call | Scenario Focus: Will the evaluation focus on deliberate, ground-based planning (e.g., AOC Strategy and Combat Plans Division functions)? |
| Operational Context: Or is the scenario centered on dynamic, in-flight engagement and execution (e.g., E-3 AWACS/CRC battle management) | Scenario subject to change but current focus is on Control and Reporting Center/Contingency response element (CRC/CRE) Battle Management | |||
| 13 | Call | What attachments are required when proposals are due? | Along with a technical and cost proposal the following attachments are required: |
Appendix 2 – Security Program Questionnaire Appendix 3 – Research and Related Senior and Key Person Worksheet Appendix 4 – AFRL Privacy Act For Covered Individuals Attachment 4 – Reps and Certs
File details come from the government source that posted it. Updated .