Call 01 MASH - Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II)

Questions & Answers / Clarifications

This document provides clarifications and answers to vendor questions regarding the Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) MASH Call for Proposals.

• Call Response: Companies should review the "Proposal Submission Section" within the Announcement for instructions on responding to the call.
• Success Definition: Success for event demonstrations is defined as a working Minimum Viable Product (MVP) and associated lessons learned, though performance metrics may also be requested.
• Call Scoping & Government Artifacts: Future calls may vary in vignettes and decision functions. "Ask Me Anything" (AMA) sessions may be held to provide overviews and answer technical questions. The government's provision of Transformational Model artifacts, data, or baseline toolchains is not explicitly detailed but may be discussed in AMAs.
• Participation: Participation is open to all interested vendors, not limited to those who participated in prior DASH events.
• Proposal Requirements: A Statement of Work (SOW) is required for evaluation. Resumes of participating personnel and facility information can be submitted as attachments to the technical proposal and do not count towards the page limit. Tables are also exempt from font and spacing requirements.
• Event Focus: The current scenario focus is on Control and Reporting Center/Contingency Response Element (CRC/CRE) Battle Management, though the scenario is subject to change.
• Attachments: Required attachments include Appendix 2 (Security Program Questionnaire), Appendix 3 (Senior and Key Personnel Profile Worksheet), Appendix 4 (Privacy Act For Covered Individuals), and Attachment 4 (Reps and Certs).
• Security: Offerors may be required to submit additional information or a mitigation plan for identified S&T protection risks. Failure to provide adequate information may result in proposal rejection.
• Personnel: While T1 background checks are required for CUI access, they are not required for Public Releasable Information or participation in this Unclassified event. Remote support is an option, but live data will not be streamed outside the facility. Personnel can rotate or substitute during the event.
• Integration: Documentation for the Government Digital Assist Orchestrator, API protocols, message formats, and interface specifications will be provided to selected offerors. Representative data feeds and schemas will also be provided prior to the event. A sandbox or pre-event integration environment will not be provided, but limited sample data may be available.
• Hardware: Offerors should bring contractor-furnished hardware for development and evaluation.
• Due Date: The proposal due date is confirmed as Saturday, March 14, 2026, at 5:00 PM Wright-Patterson AFB, OH local time.

These clarifications address vendor questions regarding proposal content, submission requirements, event logistics, and technical integration, providing essential details for offerors to prepare their submissions accurately. The due date remains unchanged.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding the Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) Broad Agency Announcement (BAA) and associated Calls for Proposals.

• Participation: Participation in the Call is open to all interested vendors and is not limited to those who participated in prior DASH events or are part of an existing cohort under the parent BAA.
• Call Type: A "Closed Call" is a one-step request for proposals with a specified submission date and time, requiring a full technical and cost proposal.
• Proposal Requirements: Resumes of participating personnel and facility information can be submitted as attachments to the technical proposal and do not count towards the page limit. However, a Statement of Work (SOW) is required for evaluation.
• Scenario Focus: The current focus for evaluation is on Control and Reporting Center/Contingency Response Element (CRC/CRE) Battle Management, though the scenario is subject to change.
• Attachments: Required attachments include Appendix 2 (Security Program Questionnaire), Appendix 3 (Senior and Key Personnel Worksheet), Appendix 4 (Privacy Act Form), and Attachment 4 (Reps and Certs). Additional information may be requested regarding Security Risk Review.
• Formatting: Tables are exempt from font and line spacing requirements. Resumes submitted as attachments also do not need to adhere to specific font and spacing rules.
• Due Date: The due date is confirmed as Saturday, March 14, 2026, at 5:00 PM Wright-Patterson AFB, OH local time.
• Organization Charts: Names should not be listed on contractor Organization Charts, consistent with the requirement for resumes.
• Funding: The government does not foresee problems securing funding, but availability of funds and successful negotiations are prerequisites for award.
• New Requirement: This MASH Call is a new requirement issued under the JADPACT II BAA.

This Q&A clarifies submission requirements, acceptable formats, and specific content for proposals related to the JADPACT II initiative. It confirms the scope of participation and key submission elements, ensuring vendors have a clearer understanding of the government's expectations.

Questions & Answers / Clarifications

This document provides answers to vendor questions regarding the Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) Broad Agency Announcement (BAA) and associated Calls.

• Call Response: Companies should review the "Proposal Submission Section" within the Announcement for instructions on how to respond to a Call.
• Event Success: Success for event demonstrations will be defined by a working Minimum Viable Product (MVP) and associated lessons learned, though performance metrics like tempo, accuracy, and workload reduction may be requested.
• Call Scoping: Future Calls may vary in their focus on specific mission threads or decision functions. "Ask Me Anything" (AMA) sessions may be held to provide overviews and answer technical questions.
• Government-Provided Artifacts: Information regarding the provision of Transformational Model artifacts, data, or baseline toolchains is addressed in AMA sessions for future calls.
• Integration Environment: Details on the expected integration environment (network constraints, data formats, interfaces, standards) will be provided during AMA sessions for future calls.
• Prior Event Pitfalls: Guidance on common pitfalls from prior events will be shared during AMA sessions for future calls.
• Participation: Participation in the Call is not limited to vendors who previously participated in DASH events or are part of an existing cohort under the parent BAA. All interested parties are encouraged to submit proposals.
• Closed Call Definition: A Closed Call is a one-step request for proposals with a specified submission date and time, requiring a full technical and cost proposal.
• BAA/Call Confirmation: The "Joint All-Domain Transformational Model II BAA" is confirmed to be the same as "Broad Agency Announcement: Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II)" (FA238426SB004).
• Personnel Resumes: Resumes of participating personnel are required as attachments to the technical proposal, in addition to the "Research and Related Senior and Key Personnel Profile Worksheet" (Appendix 3).
• SOW Requirement: A Statement of Work (SOW) is required for the evaluation of the proposed effort, despite the request for "technical and cost proposals."
• Scenario Focus: While subject to change, the current focus is on Control and Reporting Center/Contingency Response Element (CRC/CRE) Battle Management.
• Required Attachments: Along with technical and cost proposals, bidders must submit Appendix 2 (Security Program Questionnaire), Appendix 3 (Senior and Key Personnel Worksheet), Appendix 4 (AFRL Privacy Act Form), and Attachment 4 (Reps and Certs).

This Q&A document clarifies requirements and submission details for the JADPACT II opportunity. Bidders should ensure all specified attachments and proposal components are included. The SOW is confirmed as a required submission.

Questions & Answers / Clarifications

This document provides clarifications and answers to vendor questions regarding the Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) opportunity, specifically addressing both the Broad Agency Announcement (BAA) and associated Calls.

• Call Response: Companies should review the "Proposal Submission Section" within the Announcement for instructions on how to respond to a Call.
• Event Success: For BAA events, success is defined by a working Minimum Viable Product (MVP) and associated lessons learned, though performance metrics may also be requested.
• Future Calls: The scope of future Calls, including specific mission threads or vignettes, may vary. "Ask Me Anything" (AMA) sessions may be held to provide overviews and answer technical questions.
• Government-Provided Resources: Information regarding the provision of Transformational Model artifacts, representative data, or baseline toolchains for future Calls is addressed in the AMA sessions.
• Integration Environment: Details on the expected integration environment (network constraints, data formats, interfaces, standards) for events will be provided in AMA sessions.
• Prior Event Pitfalls: Guidance on common pitfalls from prior events will be shared during AMA sessions.
• Participation Eligibility: Participation in the Calls is NOT limited to vendors who previously participated in DASH events or are part of an existing cohort under the parent BAA.
• Closed Call Definition: A Closed Call is a one-step request for proposals with a specified submission date and time, requiring a full technical and cost proposal.
• Personnel Resumes: Resumes of participating personnel are required as attachments to the technical proposal, in addition to the specified worksheet.
• SOW Requirement: A Statement of Work (SOW) IS required for the evaluation of proposed efforts, despite the request for technical and cost proposals.
• Scenario Focus: The current scenario focus is on Control and Reporting Center/Contingency Response Element (CRC/CRE) Battle Management, though the subject is subject to change.

This Q&A document clarifies submission requirements, eligibility, and the nature of the effort, impacting how vendors should prepare their proposals and understand the evaluation criteria. Notably, it confirms the requirement for an SOW and broadens participation eligibility.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding the Joint All Domain Persistent Adaptive Collaborative Technologies II (JADPACT II) opportunity, specifically addressing aspects of the BAA and potential future Calls.

• Event Demonstrations Success: Success for event demonstrations will be defined by a working Minimum Viable Product (MVP) and associated lessons learned, though performance metrics (e.g., number, time, quality of solution) may be requested.
• Scoping of Future Calls: Future Calls may vary in their specific mission threads, vignettes, and decision functions. When relevant, an "Ask Me Anything" (AMA) session may be held before or after the submission deadline to provide an overview of the Transformational Model, specific decision functions, and answer technical questions.
• Government-Provided Artifacts: Information regarding whether the government will provide Transformational Model artifacts, representative data, or a baseline toolchain for integration is not explicitly detailed in this Q&A, but future calls may include AMAs to address such technical questions.
• Integration Environment: Details on the expected integration environment (network constraints, data formats, interfaces, standards) for events are not provided here, but future calls may address these through AMAs.
• Common Pitfalls: Guidance on common pitfalls from prior events is not specified in this Q&A, but future calls may address these through AMAs.

This Q&A clarifies aspects of the BAA and potential future Calls. It indicates that specific details regarding future call scoping, government-provided artifacts, integration environments, and common pitfalls may be addressed in "Ask Me Anything" (AMA) sessions associated with those future calls. Responders to the current Call should refer to the "Proposal Submission Section" within the announcement for response instructions.

Form / Attachment / Pricing Sheet

This document contains "Representations, Certifications and Other Statements of Offerors" required for proposals submitted in response to various AFRL/PZL broad announcement solicitations. It supplements the annual representations and certifications found in SAM.gov. Bidders must complete and submit these representations and certifications with their proposals for a complete offer.

• FAR/DFARS Provisions: The document lists numerous Federal Acquisition Regulation (FAR) and Defense Federal Acquisition Regulation Supplement (DFARS) provisions that are incorporated by reference. Some require fill-in information directly in this document, while others are assumed to be completed in SAM.gov.
• Applicability: For each provision, the document indicates its applicability to the solicitation and specifies any required fill-in information or disclosures from the offeror.
• Specific Provisions Requiring Action: Several provisions require specific actions or disclosures from the offeror, including:
  • FAR 52.204-8 (Annual Representations and Certifications): Requires insertion of NAICS code and size standard, and may have specific sub-paragraph applicability.
  • FAR 52.204-24 (Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment): Requires representation on providing or using covered telecommunications equipment/services and potential disclosures.
  • FAR 52.209-7 (Information Regarding Responsibility Matters): Requires indication if the offeror has current active Federal contracts and grants exceeding $10,000,000.
  • FAR 52.209-12 (Certification Regarding Tax Matters): Requires certification regarding federal tax filings, convictions, and unpaid assessments.
  • FAR 52.209-13 (Violation of Arms Control Treaties or Agreements-Certification): Requires certification regarding engagement in activities contributing to violations of arms control agreements.
  • FAR 52.229-11 (Tax on Certain Foreign Procurements—Notice and Representation): Requires representation on being a foreign person and claiming tax exemptions.
  • FAR 52.230-1 (Cost Accounting Standards Notices and Certification): Requires certification regarding disclosure statements, monetary exemptions, or eligibility for modified contract coverage.
  • FAR 52.230-7 (Proposal Disclosure-Cost Accounting Practice Changes): Requires indication if the contract award will result in a required or unilateral change in cost accounting practice.
  • DFARS 252.204-7007 (Alternate A, Annual Representations and Certifications): May require completion of individual representations and certifications.
  • DFARS 252.204-7017 (Prohibition on The Acquisition Of Covered Defense Telecommunications Equipment Or Services—Representation): Requires representation on providing covered defense telecommunications equipment or services and potential disclosures.
  • DFARS 252.225-7010 (Commercial Derivative Military Article – Specialty Metals Compliance Certificate): Requires listing of commercial derivative military articles intended for delivery.
  • DFARS 252.225-7057 (Preaward Disclosure Of Employment Of Individuals Who Work In The People’s Republic Of China): Requires disclosure if the offeror employs individuals working in the PRC.
  • DFARS 252.239-7009 (Representation of Use Of Cloud Computing): Requires representation on the anticipated use of cloud computing services.
  • DFARS 252.227-7017 (Identification and Assertion of Use, Release, Or Disclosure Restrictions): Requires submission of assertions regarding restrictions on the Government's use, release, or disclosure of technical data or computer software.
• Signature Block: A signature block is provided to certify the accuracy and completeness of the representations and certifications, or to confirm that information is current and asserted in SAM.gov.

This document is critical for bidders to ensure their proposals are compliant. Failure to complete and submit these representations and certifications as required may render an offer ineligible for award. Bidders must carefully review each provision's applicability and provide the necessary information or confirm its status in SAM.gov.

Statement of Work (SOW) / Performance Work Statement (PWS)

This document outlines the objectives and scope for the Human-Machine Teaming (HMT) concepts project, specifically focusing on leveraging Artificial Intelligence (AI) and automation capabilities to support Battle Managers and enhance Command and Control (C2) decision advantage. The goal is to integrate industry solutions to meet defined technical requirements and improve warfighter involvement in AI/autonomy development.

• The project aims to develop and adapt cutting-edge AI/automation approaches for Battle Management.

• It involves understanding and aligning with the Transformational Model (TM) for Decision Advantage, which describes military decisions within an HMT.

• The TM-BM (Transformational Model – Battle Management) comprises 13 subfunctions derived from operational environment assumptions.

• The work focuses on emerging C2 solutions that support decision-making and decision advantage, particularly in complex, high-volume battle management scenarios.

• The MASH (Multi-Decision Advantage Sprint for Human-Machine Teaming) events will assess the maturity of software services that complete specific decision functions (PAE, MEF, GBC).

• Key outcomes for participation include successful live integration with the Government Digital Assist Orchestrator, demonstrated functional relevance of the AI tool, and contribution to human-machine team performance by enabling faster and better decisions.

• Government assessors will record performance and integration success.

• The MASH events are described as a series of events, with a specific event mentioned as taking place in Las Vegas.

• The duration of the event is a two-week window.

• Offerors must describe the current maturity level of their proposed tool (conceptual model, lab prototype, or market-ready product).

• Proposals must detail how their tool will function as a containerized service, integrate via a well-defined API, and process dynamic data.

• Contractors must adhere to the government-owned messaging standard and API for integration.

• Security requirements include General Operations Security (OPSEC), a Tier 1 background check for personnel, and clearance of all documents by the Air Force prior to public release.

• Non-U.S. citizen contractors require specific approvals for access to USAF bases and networks.

• Federal holidays are observed and are included in contract costs.

Form / Attachment / Pricing Sheet

This document is a Contract Data Requirements List (CDRL) that specifies the requirements for a "Scientific and Technical Reports Summary" data item (DI-MISC-80048). It outlines the format, content, and submission instructions for these reports, which are acquired to provide the scientific and technical community with descriptions of research, development, test, and evaluation accomplishments.

• Data Item Title: Scientific and Technical Reports Summary
• Data Item Number: DI-MISC-80048
• Authority: DI-MISC-80048/T
• Contract Reference: CSOW
• Frequency: LT (As required)
• Submission: Tailored to allow contractor's format.
• Content Requirements: Reports should be understandable to non-specialists and include task objectives, technical problems, methodology, technical results, important findings, conclusions, implications for further research, significant hardware development, and special comments.
• Cover Page Information: Must include Procuring Activity Designated Order Number, Contractor Name, Contract Number, Effective and Expiration Dates, Reporting Period, Principal Investigator/Engineer contact, and Short Title of Work.
• Disclaimer: A specific disclaimer notice is required on the cover page.
• Reproduction: Reports must be reproduced using processes that provide clear, sharp copies suitable for further reproduction.

This CDRL details the specific reporting requirements for scientific and technical summaries that may be a deliverable under a contract. Bidders should review this document to understand the expected format, content, and submission process for these reports, which will impact proposal preparation and contract performance if awarded.

Solicitation / RFP / RFQ

This is an initial solicitation (FA2384-26-S-B005) for the Joint All-Domain Transformational Model II, issued by the Air Force Research Laboratory, RHW Warfighter Readiness and Interactions Division. The effort aims to develop technical and cost proposals related to the Combined Joint All-Domain Command and Control (CJADC2) Campaign Plan 2030, focusing on enhancing decision advantage over adversaries by improving current command and control (C2) systems. The project will utilize the Transformational Model for Decision Advantage (TM) and model-based systems engineering to analyze C2 decision domains.

• The primary deliverable is data items, as detailed in Attachment #2, Contract Data Requirements List (CDRL).

• Statement of Objectives is provided in Attachment #1.

• Security requirements are governed by AFRLI 61-113, with potential need for additional information or mitigation plans for S&T protection risks (Attachment #3).

• Offerors must adhere to the Joint All-Domain Transformational Model II BAA on SAM.gov, with any deviations noted in the award decision.

• Anticipated Contract Type: Firm Fixed Price, but the Air Force reserves the right to award the instrument best suited to the research nature (e.g., FAR/OT for Prototype, grant, cooperative agreement, OT for Research, or C type contract).

• Estimated Program Cost: $600K.

• Maximum per offeror selected: $100K.

• Period of Performance: Two weeks.

• Data Item Delivery: Conclusion of the period of performance.

• Submission Due Date and Time: March 14, 2026, 5:00 PM Wright-Patterson AFB, OH local time.

• Submission Method: Electronically via E-mail to the Contracting Officer and Contract Specialist.

• Proposals will be reviewed without negotiation/discussion, though the government reserves the right to negotiate with selected offerors.

• Offerors will be notified of award recommendation on or about March 24, 2026.

• This is an unrestricted solicitation; however, small businesses are encouraged to propose.

• Foreign-owned firms should notify the Contracting Officer of their intent to respond due to potential restrictions.

• The BAA is available on SAM.gov.

• Cost sharing is not required.

• This Call does not intend to use policies from Part 12, Acquisition of Commercial Items, but interested offerors can identify commercial item capability within 15 days of release.

Form / Attachment / Pricing Sheet

This document is a "Privacy Act Statement" for the Air Force Research Laboratory. It informs individuals about the collection, use, and disclosure of their personal information in relation to Federal Grants, Cooperative Agreements, Contracts, Other Transaction Agreements, and other research-related agreements awarded by the Department of the Air Force.

• Authority: Lists the legal statutes and executive orders governing the collection of information.
• Purpose: Explains why the information is collected (e.g., processing, investigating, and maintaining records for awards).
• Routine Uses: Details how the collected information may be used, including by contractors, grantees, and law enforcement.
• Effect of Not Providing Information: States that providing information is voluntary but failure to do so may result in rejection of applications, with potential civil or criminal remedies.
• Acknowledgment of Consent: Includes fields for signatures and printed names of the covered individual and the institution's authorized representative, along with the date, to acknowledge consent.
• Proposal Title: A field to enter the title of the proposal.

Bidders responding to opportunities involving Federal Grants, Cooperative Agreements, Contracts, or Other Transaction Agreements with the Air Force Research Laboratory may be required to complete and submit this form as part of their application or proposal. It outlines the privacy implications and consent requirements for individuals involved in the research or award process.

Solicitation / RFP / RFQ

This document outlines the requirements for a Security Risk Review process applied to federally funded research, designed to protect the Department of the Air Force's Science and Technology (S&T) by identifying potential vectors of undue foreign influence. The review process follows AFRL Instruction AFRLI 61-113 and Department of the Air Force Instruction DAFI 63-101/20-101.

• For Grant or Cooperative Agreement (CA) applications: Submit Standard Form 424 (Research and Related Senior and Key Person Profile - Expanded), Security Program Questionnaire, and a "Privacy Act Statement" consent form for each Covered Individual.

• For Contract or Other Transaction Agreement (OTA) proposals: Submit Research and Related Senior and Key Person Profile Worksheet, Security Program Questionnaire, and a "Privacy Act Statement" consent form for each Covered Individual.

• Applicants/Offerors must ensure all listed Senior/Key personnel are aware of disclosure requirements (42 U.S.C. § 6605) and potential penalties for false representations.

• Applicants/Offerors must establish internal processes to address foreign talent programs, conflicts of commitment/interest, and research integrity.

• Applicants/Offerors must exercise due diligence to identify Foreign Components or participation in Foreign Government Talent Recruitment Programs by Senior/Key Personnel and share this information with the Government upon request.

• Submission of the Research and Related Senior Key Person Profile and Security Program Questionnaire signifies agreement to comply with disclosure and due diligence requirements.

• If a security risk is identified that exceeds the acceptable threshold, the award will be declined, with rationale provided as Government OPSEC measures allow.

• Failure to report fully and completely may be considered a material statement under the False Claims Act.

• Annual re-submission of the Research and Related Senior and Key Person Profile is required.

• A new profile is required prior to continued performance whenever a new covered individual is added or identified.

• Prompt notification (within 5 business days) to the Contracting/Grants/Agreements Officer is required if Senior/Key Personnel are believed to be participants in a Foreign Government Talent Program or have Foreign Components with strategic competitors.

• This requirement must be flowed down to all sub-awardees/contractors with designated Senior/Key Research Personnel.

• Nationality or citizenship is not a factor in the security risk reviews.

• The review process generally examines five risk factors, with authority for expanded review.

• Appendices referenced include forms for Senior/Key Person Profile (Expanded), Security Program Questionnaire, Senior/Key Person Profile Worksheet, and Privacy Act Statement consent form.

Form / Attachment / Pricing Sheet

This document is the "Research and Related Senior and Key Person Profile Worksheet." It is a required form for bidders to complete and submit as part of their proposal.

• The worksheet requires detailed information for a Project Director / Principal Investigator and up to five Senior / Key Persons.
• Required fields for each person include: First Name, Last Name, Position/Title, Organization Name, and Email Address.
• Optional fields include: Middle Name, Suffix, Department, Division, Phone Number, and LinkedIn Profile.
• Bidders must also specify the "Project Role" (e.g., PD/PI) and can note "Other Project Role" if applicable.
• A footnote indicates that fields marked with an asterisk (*) are required items.

This form is crucial for bidders to accurately identify and provide qualifications for the key personnel who will be involved in performing the work under the contract. Failure to complete this form accurately and completely may impact proposal evaluation.

Form / Attachment / Pricing Sheet

This document is a Security Program Questionnaire designed to review the security programs and practices of institutions receiving research funding. It is intended to be completed by collaborators and reviewed by the S&T Protection Lead.

The questionnaire includes fields for:

• Date Submitted
• Applicant Name
• CAGE Code/SCL and level (if applicable)
• Completed by Name and Position/Title

It then poses 13 detailed questions covering:

• Physical security plans
• Information security processes
• Information storage locations
• Procedures for transmission/transportation, disposal/destruction, and reproduction of information
• Personnel safeguards for information access
• Plans for safeguarding Government Furnished Equipment/Information (GFE/GFI)
• Cybersecurity and network protection procedures
• Operations security processes
• Insider threat mitigation
• Procedures for handling information compromise
• Willingness to provide AFRL S&T Protection training

An area for additional comments is also provided.

Bidders may be required to complete this questionnaire as part of the application or proposal process to demonstrate their institution's security capabilities and compliance. Understanding these requirements is crucial for preparing a compliant and competitive response, particularly for opportunities involving sensitive research or data.