QuestionAnswerSheet16Oct2026 (1).xlsx
XLSX spreadsheet 25 KB Posted
- Attached to
- Call 03 M-DASH - Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II)
- Solicitation number
- FA238426SB007
About this file
This file is a Question and Answer sheet addressing inquiries regarding the JADPACT II M-DASH Closed Call 3 solicitation (FA2384-26-S-B007). The document clarifies technical, administrative, and procedural requirements for vendors proposing solutions to support Battle Management decision functions within the unclassified M-DASH event scheduled for January 25 – February 4, 2027, in Las Vegas.
Key technical requirements specify that vendors must provide three integrated decision services—PAE (Apply Objective Priorities), MEF (Evaluate BattleCOA Impacts), and GBC—as a complete Battle COA ensemble, though vendors may employ alternative architectures beyond the government's reference three-module model provided they perform required functions equivalently. Vendors are responsible for acquiring AI models and tokens, bringing their own development and hosting hardware, and building translation layers to handle diverse data formats including text documents, formatted databases, IRC, and REST-based track/area/entity data. The government will provide a UI and schema details after vendor selection; no vendor-provided UI is required. Success metrics emphasize a working MVP and associated lessons learned rather than specific performance benchmarks. Solutions must be usable and demonstrate functional relevance by the second week of the event. Selected offerors will be notified around November 5, 2026, with all remaining data provided at the event. Payment is structured as a single firm fixed price payment upon event conclusion and deliverable receipt through WAWF in PIEE.
Administrative requirements mandate that proposals remain limited to five pages for the Technical/Management section and five pages for the Statement of Work, with supporting attachments including resumes, equipment descriptions, security forms, Senior/Key Person profiles (Appendix 2), and Privacy Act consents (Appendix 3) excluded from the page count. A CMMC Level 1 self-assessment is required by proposal submission and may impact selectability. All participants supporting the event must complete Appendix 2 and signed Appendix 3 forms; the government will not accept personnel changes post-award. SAM registration must be active by award, though proposals may be submitted while registration is pending. Canadian-owned firms may submit without restrictions. Foreign nationals from allied countries (Canada, UK, Japan, Germany, Netherlands, etc.) will participate in the event, making ITAR-controlled technology a consideration. Planned travel dates are Sunday, January 24, and Friday, February 6, 2027, with the event held at a commercial facility requiring no base access.
View the file
Other files
Show all 19
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) M-DASH Closed Call 3 | ||||
| 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.)? | 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. | |
| 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 | BAA | What is the link to the BAA? | https://sam.gov/workspace/contract/opp/d47fe005062f4ffbb72cb2ee4fb550db/view | |
| 7 | Call | Attachment 5 is a protected document and cannot be accessed | Attachment 5 was re-uploaded without DoD security label on 10/7/26 and is accessible. | |
| 8 | Call | Call section 6.1.1 gives a notification date of "on or about 18 June 2026". When will selected offerors be notified, and when will the Digital Orchestrator schema and any sample data be provided? | This has been corrected in the call. Offerors will be notified around 5 November 2026. All other data will be provided at the event. | |
| 8 | Call | The Ask Me Anything is listed as 1200 to 1300 EST on SAM and as 1100 to 1230 in the Call. Does it start at 12:00 Eastern Daylight Time on 15 October, and is the SAM Teams link the correct one? | This has also been corrected in the call. The AMA is on 15 October 2026 at 1200 EST and the link is: https://dod.teams.microsoft.us/dl/launcher/launcher.html?url=%2F_%23%2Fmeet%2F993760972936%3Fp%3Dusjy0trBo5QNafEsb5%26anon%3Dtrue&type=meet&deeplinkId=0956d2ef-f522-4f5b-a074-7941ed58b99f&directDl=true&msLaunch=true&enableMobilePage=true&suppressPrompt=true | |
| 9 | Call | SOO section 4.1.1 requires a Tier 1 investigation for "any position that requires access to the internet", while the same paragraph ties Tier 1 to CUI access. Is a Tier 1 (SF85) required for this unclassified event, and if so, by when? | A Tier 1 investigation is only required for classified information. This M-DASH Event is Unclassified, therefore a Tier 1 (SF85) is not required. | |
| 10 | Call | Is the event venue a Government installation or a commercial facility? Will a visit request or base access be needed? | The event is not held at a government installation and no base access is needed. | |
| 11 | Call | The SOO says no code is delivered and participants keep their intellectual property. Does the Unlimited Rights clause reach anything beyond CDRL A001 and the recorded messaging outputs? Should the DFARS 252.227-7017 table list pre-existing software that runs at the event but is not delivered, or is "none" correct? | The Data Rights Clause reaches only the A001 Deliverables. Listing pre-existing software that runs at the event is not required. Offerors may choose their own asserts based on the DFARS 252.227-7017 table. | |
| 12 | Call | The CDRL cites DI-MISC-80711A/T, but the attached Data Item Description is DI-MISC-80048, and the SOO calls the deliverable a "Technical Review Presentation Package". Which governs? | There has been a correction in the attachments of the call; Technical Review Presentation Package (DI-SESS-82168/T) is the correct CDRL and has been updated as of 8 October 2026. | |
| 13 | Call | How will payment be structured under the anticipated firm fixed price award: a single payment at the end, or milestones? Will invoicing be through WAWF in PIEE? | Payment is a single payment at the conclusion of the event and upon receipt of deliverable. Payment will be though WAWF in PIEE. | |
| 14 | Call | Should resumes in the proposal omit names, as in the MASH Call 01 answers? | Omiting names is acceptable, but not required. | |
| 15 | Call | Are tables exempt from the font and spacing rules, and do the vignette and the maturity statement count within the 5 pages? | Tables are exempt from spacing requirements. The page number limit is firm at 5 pages. Font and line spacing requirements do not have to be followed for tables, charts, drawings, etc. The proposal page limit does not include the proposed Statement of Work, but this is also limited to 5 pages. | |
| 16 | Call | Should the proposal reference both FA2384-26-S-B004 and FA2384-26-S-B007? Is there a size limit for the emailed submission, and may the volumes be sent in separate emails? | You may reference both, but please reference FA2384-26-S-B007 specifically. Email submissions can be broken into separate emails if needed. Please contact the POC if file sizes are too large to arrange a DoD Safe drop off. | |
| 17 | Call | Does the Section 7.1 commercial-item notice need to be sent separately, ahead of the proposal, for software offered as commercial? | This does not need to be sent separately ahead of the proposal. Submitting with the proposal is fine. | |
| 18 | Call | When will the schema be provided? | The Schema will be described and given out to those selected after the first optional office hours session. (if they can't attend the sessions, no worries we intend to send it to those notified of selection) | |
| 19 | Call | Must a proposal address all three decision services? | Yes. Each vendor or group must be able to provide all three services—PAE, MEF, and GBC—as a complete Battle COA ensemble. | |
| 20 | Call | Must the solution use the government’s three-module architecture? | No. The government model is a reference model. Vendors may use a different architecture, including an integrated solution, provided it performs the required functions at least as well and makes the relevant outputs available. | Q/A From AMA |
| 21 | Call | What outputs must be visible to the government? | The government expects access to the candidate Battle COAs, not only the top recommendations, plus the associated battle effects and effect-effector matches supporting the recommendations. | Q/A From AMA |
| 22 | Call | Are vendors required to provide a user interface? | No. A government-owned UI will be used. Vendor services must provide data in the required API/schema format so the UI can present the results. | Q/A From AMA |
| 23 | Call | How will solutions be assessed? | The event will collect a human-only baseline, then examine comparable decision speed and quality measures with vendor solutions in use. The government stated the event is not intended as a vendor-versus-vendor competition. | Q/A From AMA |
| 24 | Call | Is there a required maturity level on arrival? | No specific maturity level was stated. However, the solution must be usable and demonstrate functional relevance by the second week of the event. | Q/A From AMA |
| 25 | Call | When will API and data-source details be available? | Detailed API, schema, and data-source information are expected after vendor selection, with optional office hours available before the event and support available on site. | Q/A From AMA |
| 26 | Call | What data formats/sources should vendors expect? | Data may include text documents, formatted databases, Internet Relay Chat (IRC), and track/area/entity data accessible through REST-based methods. Vendors may need to build translation layers. | Q/A From AMA |
| 27 | Call | Will the government provide AI models or tokens? | No. Vendors are responsible for any models or tokens used by their solution. | Q/A From AMA |
| 28 | Call | What are the hardware and network expectations? | Vendors should bring their own development and hosting hardware. The government’s on-site hardware is intended for the scenario/operator stations. Commercial Wi-Fi and local network connectivity are expected; external hosting may be possible, subject to network considerations. | Q/A From AMA |
| 29 | Call | Is the event classified? | No, the event is unclassified. | Q/A From AMA |
| 30 | Call | What team size is expected? | Teams should be sized to execute required deliverables, while accounting for limited workspace; the government specifically discouraged very large teams. | Q/A From AMA |
| 31 | Call | For vendor technology that is ITAR controlled- Are all participants in the event confirmed to be US persons and vetted against the applicable denied parties lists ? | There will be foreign nationals from allied countries (Canada, UK, Japan, Germany, Netherlands, etc.) at the event. | Q/A From AMA |
| 32 | Call | Can we assume that Sunday Jan 24 and Feb 5 are travel days for the event ? | Current planned travel days are Sun 24 Jan and Fri 06 Feb | Q/A From AMA |
| 33 | Call | Please confirm whether resumes, prior-work information, and equipment/facility descriptions count toward the five-page Technical/Management limit. | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | Q/A From AMA |
| 34 | Call | Please confirm that Section K, the signed data-rights assertion table, Security Program Questionnaire, Senior/Key Person profiles, research-support disclosures, and Privacy Act consents are excluded from the five-page Technical/Management limit. Should these be included in the Cost/Business volume or submitted as separate administrative attachments? | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | Q/A From AMA |
| 35 | Call | Please confirm whether the Appendix 02- Research and Related Senior and Key Person Profile Worksheet should be submitted within Volume II- Cost/Business Proposal or as a separate administrative/security attachment, and whether it is excluded from the five-page Technical/Management proposal limit. | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | Q/A From AMA |
| 36 | Call | Are mandatory administrative forms excluded from the five-page limit, and where should they be submitted? | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | Q/A From AMA |
| 37 | Call | Are Senior/Key Person profiles and research-support disclosures required for all participants or only designated covered individuals? | Any/all participants that will support the event if selected require Senior/Key Person profiles and research-support disclosures | Q/A From AMA |
| 38 | Call | Follow up question to - Answer for Answer 37: Any/all participants that will support the event if selected require Senior/Key Person profiles and research-support disclosures. Appendix 2 is Key Personnel. Is Appendix 3 research-support disclosure? | Correct | Q/A From AMA |
| 39 | Call | What does AOP and EBI stand for? | AOP=Apply Objective Priorities, EBI=Evaluate BattleCOA Impacts | Q/A From AMA |
| 40 | Call | The Sam.gov links in the SOO direct to wrong postings; can this be updated and SOO reploaded? | Corrected links were provided in the chat of the meeting and an updated SOO with corrected links will be posted on Sam.gov call. | Q/A From AMA |
| 41 | Must a proposal address all three decision services? | Yes. Each vendor or group must be able to provide all three services—PAE, MEF, and GBC—as a complete Battle COA ensemble. | ||
| 42 | Must the solution use the government’s three-module architecture? | No. The government model is a reference model. Vendors may use a different architecture, including an integrated solution, provided it performs the required functions at least as well and makes the relevant outputs available. | ||
| 43 | What outputs must be visible to the government? | The government expects access to the candidate Battle COAs, not only the top recommendations, plus the associated battle effects and effect-effector matches supporting the recommendations. | ||
| 44 | Are vendors required to provide a user interface? | No. A government-owned UI will be used. Vendor services must provide data in the required API/schema format so the UI can present the results. | ||
| 45 | How will solutions be assessed? | The event will collect a human-only baseline, then examine comparable decision speed and quality measures with vendor solutions in use. The government stated the event is not intended as a vendor-versus-vendor competition. | ||
| 46 | Is there a required maturity level on arrival? | No specific maturity level was stated. However, the solution must be usable and demonstrate functional relevance by the second week of the event. | ||
| 47 | When will API and data-source details be available? | Detailed API, schema, and data-source information are expected after vendor selection, with optional office hours available before the event and support available on site. | ||
| 48 | What data formats/sources should vendors expect? | The government indicated that data may include text documents, formatted databases, Internet Relay Chat (IRC), and track/area/entity data accessible through REST-based methods. Vendors may need to build translation layers. | ||
| 49 | Will the government provide AI models or tokens? | No. Vendors are responsible for any models or tokens used by their solution. | ||
| 50 | What are the hardware and network expectations? | Vendors should bring their own development and hosting hardware. The government’s on-site hardware is intended for the scenario/operator stations. Commercial Wi-Fi and local network connectivity are expected; external hosting may be possible, subject to network considerations. | ||
| 51 | Is the event classified? | The event is unclassified and uses information at the distribution level described in the session. Users should validate all handling and release requirements through the official event documentation. | ||
| 52 | What team size is expected? | No formal minimum or maximum was stated. Teams should be sized to execute required deliverables, while accounting for limited workspace; the government specifically discouraged very large teams. | ||
| 53 | Our technology is ITAR controlled. Are all participants in the event confirmed to be US persons and vetted against the applicable denied parties lists? | There will be foreign nationals from allied countries (Canada, UK, Japan, Germany, Netherlands, etc.). | ||
| 54 | Are Sunday Jan 24 and Feb 5 are travel days for the event? | Current planned travel days are Sun 24 Jan and Fri 06 Feb | ||
| 55 | Do resumes, prior-work information, and equipment/facility descriptions count toward the five-page Technical/Management proposal limit? | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | ||
| 56 | Are the following mandatory administrative documents excluded from the five-page Technical/Management proposal limit: Section K; the signed data-rights assertion table; Security Program Questionnaire; Senior/Key Person profiles; research-support disclosures; and Privacy Act consents? | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | ||
| 57 | Should mandatory administrative documents be included in Volume II, Cost/Business Proposal, or submitted as separate administrative attachments? | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | ||
| 58 | Should Appendix 02, Research and Related Senior and Key Person Profile Worksheet, be submitted in Volume II, Cost/Business Proposal, or as a separate administrative or security attachment? | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | ||
| 59 | Is Appendix 02 excluded from the five-page Technical/Management proposal limit? | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | ||
| 60 | If administrative forms are excluded from the five-page limit, are there specific file-naming, formatting, or submission instructions for those attachments? | This information should be submitted as attachments to the tech/mgmt. proposal None of these documents count toward page limitation. | ||
| 61 | Are Senior/Key Person profiles and research-support disclosures required for all participants or only designated covered individuals? | Any/all participants that will support the event if selected require Senior/Key Person profiles and research-support disclosures | ||
| 62 | Is Appendix 3 research-support disclosure? | Yes | ||
| 63 | May we submit a proposal while our SAM registration is pending, as long as it is active before award? | Yes, you may submit a proposal. If you are not active in SAM at award you will not be eligible to receive an award. | ||
| 64 | Is a CMMC Level 1 self-assessment in SPRS required by the proposal due date, or by award? | Required by proposal as the information in the assessment could impact selectability. | ||
| 65 | If our SAM representations and certifications are not active yet, how should we complete the Section K representations and certifications? | If you are not active in SAM at award and able to complete the Sec K Reps & Certs you will not be eligible to receive an award. | ||
| 66 | For CALL 03 if selected, will be permitted to add personnel to participate or are we firm on the key personnel identified in appendix 2 and 3? | We will not be able to accept personnel changes after the fact as it could potentially change the selection determination. | ||
| 67 | for every person that fills and signs appendix 3, assumably should be on appendix 2, if we exceed the allotted 5 can I submit two appendix 2 docs to account for all personnel or is appendix 2 a max of 5? | Appendix 2 Research & Related Senior/Key Person Profile: 6 spaces (Principal Investigator + 5 Key Personnel) however if you propose more individuals you would simply need to provide the names and all information within Appendix 2 in an additional document. The BAA and the Call do not have a specified limit on personnel. The document is just a template of the information. | ||
| Appendix 3 AFRL Privacy Act Statement every proposed individual from Appendix 2 must complete this form and sign it and each signed document submitted as part of the proposal. | ||||
| 68 | Whether a Canadian-owned firm may submit a proposal to Call 03, and any restrictions that would apply | No restrictions | ||
| 69 | Whether the Distribution D / CUI attachments can be released to us, and the process for requesting them. | Dsitro D documentation is unlikely to be required. However, in the event that it is we will provide Govt review on a case by case basis | ||
| 70 | How will future DASH sprint calls be announced, and which one would fit? | All DASH events will be announced via SAM.gov. Interested parties can review the solicitation and submit a proposal for consideration. | ||
| 71 | Section 5.2(c)(1) of the parent BAA establishes a five-page limit for the Technical/Management Proposal, including the cover page, and states that the limitation covers all information. However, Section 5.2(c)(2) directs offerors to include resumes, prior work, equipment descriptions, and other supporting information as attachments. | Supporting attachments are excluded from the 5 page count and do not have a set page limit | ||
| Are these supporting attachments excluded from the five-page technical proposal limit, or must they be included within the five pages? | Supporting attachments are excluded from the 5 page count and do not have a set page limit | |||
| If excluded, is there a separate page limit for supporting attachments? | Supporting attachments are excluded from the 5 page count and do not have a set page limit | |||
| 72 | Section 5.2(c)(1) excludes the contractor's proposed SOW from the five-page technical proposal limit and establishes a separate five-page allowance. However, Section 5.2(c)(2) states that the technical volume shall include the SOW. | The SOW may be submitted as a separate document | ||
| 73 | We identified differences between the attachment references in the Closed Call's body and its final attachment list, particularly concerning the Statement of Objectives, SOW Supplemental Requirements, CDRL, and Security Risk Review. The parent BAA also uses different attachment numbering for Section K. • | Which security-risk review forms and appendices must accompany the initial proposal, versus those required during pre-award review? | All security forms and appendices are required with the proposal submission. Yes, the documents with CMMC 1 are required with initial proposal submission | |
| 74 | Confirming Attachment 2 (CDRL) is not something we need to submit as part of the proposal? | Correct, this is a draft example of the CDRL's that will be on awarded contracts | ||
| 75 | Is it acceptable to submit the SOW and Technical Proposal as two separate Word files, each with a five page maximum? or must we combine them into one 10 page max technical proposal, structed with two 5-page sections | The SOW is a supplemetal attachment to the Technical Proposal and does not count toward the 5 page limit |
https://sam.gov/workspace/contract/opp/d47fe005062f4ffbb72cb2ee4fb550db/view Sheet2
File details come from the government source that posted it. Updated .