QuestionAnswerSheet8Oct2026.xlsx
XLSX spreadsheet 13 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 is a Question and Answer sheet addressing inquiries from potential offerors regarding Call 03 M-DASH, a solicitation (FA2384-26-S-B007) for the Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) program. The document clarifies key administrative and technical requirements for an event-based demonstration scheduled for January 25 - February 4, 2027, in Las Vegas. Success will be measured by delivering a working Minimum Viable Product (MVP) with associated lessons learned rather than specific performance metrics. Future calls may vary in vignettes and decision functions, with Ask Me Anything (AMA) sessions scheduled to provide overview of the Transformational Model and specific decision functions. The AMA is confirmed for October 15, 2026, at 12:00 EST via the provided Teams link. Selected offerors will be notified around November 5, 2026, with the Digital Orchestrator schema and sample data provided at the event. The event is held at a commercial facility (not a government installation) requiring no base access.
The solicitation imposes specific administrative and data requirements: no Tier 1 (SF85) security clearance is required as the event is unclassified; Unlimited Rights data clauses apply only to CDRL A001 deliverables and recorded outputs; the corrected CDRL is Technical Review Presentation Package (DI-SESS-82168/T); proposals are limited to five pages (excluding the five-page Statement of Work), with tables exempt from font and spacing requirements; resume name omission is acceptable but not required; and references should specify FA2384-26-S-B007. Payment will be structured as a single firm fixed price upon event conclusion and deliverable receipt, processed through WAWF in PIEE. The Section 7.1 commercial-item notice may be submitted with the proposal rather than separately. Email submissions can be divided across multiple emails, with large files accommodated through DoD Safe drop-off if necessary.
View the file
Other files
Show all 18
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) |
https://sam.gov/workspace/contract/opp/d47fe005062f4ffbb72cb2ee4fb550db/view
File details come from the government source that posted it. Updated .