DASH 3 GBC RFP.pdf

Reference ID: FA238425SRHW3

Notice Type: Special Notice

Synopsis: Request for Proposal (RFP) for Transformational Model – Battle Management Generate Battle Courses of Actions (GBC) Decision Advantage Sprint for Human-Machine- Teaming (DASH)

FEDERAL AGENCY NAME: Department of Air Force, Air Force Material Command, Air Force Research Laboratory – AFRL/711th Human Performance Wing/Human Effectiveness Directorate, 2510 Fifth Street, Bldg. 840, Wright-Patterson AFB, OH 45433

1.0 GENERAL INFORMATION

1.1 THIS NOTICE IS A REQUEST FOR PROPOSAL (RFP) ONLY. This request for proposal does not commit the Government to contract for any supply or service whatsoever. Responders are advised that the U.S.

Government will not pay for any information or administrative costs incurred in response to this RFP. All other costs associated with responding to this RFP will be solely at the interested party’s expense. Not responding to this RFP does not preclude participation in any future request for information (RFI) or RFP, if any is issued. If a solicitation is released, it will be synopsized on the Beta SAM website. It is the responsibility of the potential offerors to monitor this site for additional information pertaining to this requirement. Respondents should indicate which portions of their response are proprietary and should mark accordingly. NOTE: This RFP is not associated with any previous or ongoing RFPs or Fair Opportunity Proposal Requests issued by the Department of the Air Force (DAF).

1.2 FEEDBACK. Submission is voluntary. Respondents are advised that AF/A57 and AFRL are under no obligation to provide feedback with respect to any information submitted under this RFP.

2.0 REQUEST FOR PROPOSAL (RFP)

2.1 BACKGROUND

The Combined Joint All-Domain Command and Control (CJADC2) Campaign Plan 2030 defines decision advantage as the ability to consistently make better, timelier decisions than the adversary. Current DAF command and control (C2) systems and processes are optimized for low intensity conflict and do not address decision advantage over the pacing challenge. Deriving effective C2 capability development toward decision advantage requires a clear understanding of what C2 decisions are. The DAF Advanced Battle Management System (ABMS) Cross Functional Team (CFT) provides a quantitative model for the Joint Warfighting Function of C2 as the Battle Command, Battle Plan, Battle Analysis, and Battle Management decision domains. Each of these decision domains are decomposed in the Transformational Model for Decision Advantage (TM) using model-based systems engineering which bring these C2 decisions to light in a detailed manner.

The TM describes military decisions being made within a human-machine team (HMT), including specific choices within these domains and the battlespace information needed to inform said choices.

Therefore, the TM provides foundational requirements for C2 decision-making that are universal

(agnostic to time epoch, process, geography, organization, doctrine, among others). Additional information on the TMs can be found at: SAM.gov

The Transformational Model – Battle Management (TM-BM) is comprised of 13 distinct and orthogonal subfunctions (Figure 1) deduced from the following operational environment (OE) assumptions/axioms:

• No entities exist in identical states simultaneously.

• Force distributions in the OE are not uniform.

• The OE evolves over time.

• Information is incomplete and uncertain.

• Missions are difficult and resources are constrained.

In OEs where these assumptions apply (which will be the case for the pacing challenge), the TM-BM subfunctions explain the comprehensive set of battlespace information elements and decisions an HMT must make to battle manage the battlespace. Consequently, TM-BM reveals measures of performance and give structure to a design of experiments (DOE) that best characterize a battle management HMT.

Figure 1: Transformational Model – Battle Management Subfunctions.

The resulting analysis delivers C2 decision advantage requirements to military capability developers and acquisition professionals through rigorous defensible analysis.

2.2 PROBLEM STATEMENT. Emerging C2 solutions focus on decision support (i.e., system interoperability, information exchange, and information presentations, i.e., battlespace awareness/display) and do not directly address decision advantage (i.e., software that machine-assists/automates battle management decision-making). To win against a peer adversary, the joint force must achieve decision advantage by equipping C2 HMTs with automation to sort through complex and high-volume battle management decisions with faster tempo and improved decision quality.

2.3 Decision Advantage Sprint for HMTs (DASH)

The DAF Advanced Battle Management System (ABMS) Cross Functional Team (CFT) (AF/A57RB) and Air Force Research Laboratory, 711 Human Performance Wing (711 HPW) are seeking proposals to support a Transformational Model – Battle Management Generate Battle Courses of Action (GBC) Decision Advantage Sprint for Human-machine-teaming (DASH) tentatively scheduled for 15 – 26 September 2025 at the Howard Hughes Operations (H2O) Center in Las Vegas, NV. An “Ask Me Anything” for this event is planned for 25 July 2025 at 1100 Eastern / 0800 Pacific. Participants will be limited based on resource and space constraints, and selected participants will be notified by 13 August 2025.

During the DASH, participating software development teams will witness a battle management crew making GBC battle management decisions in a simulated combat environment. The participating software developers will then apply the Transformational Model (the functional description of C2 decision-making) and their creativity in developing an application/microservice that helps the humans https://sam.gov/opp/a6f8e78859cd45d294a8df70906c90f5/view make faster and higher quality battle management decisions. Battle management warfighters will team with coders to provide operational perspective and feedback. Some warfighters may originate from allied nations. At the end of the DASH, each development team will have the opportunity to demonstrate how their software affects overall human-machine team decision making during a culminating experiment. Experiment results and the list of participants will be shared with government stakeholders. Invited participants will retain their intellectual property (IP), including any changes made over the course of the week. Government stakeholders reserve the right to analyze all collected sprint data (including software performance and technical integration insights) to derive, refine and mature functional and technical C2 software requirements.

2.4 TECHNICAL CHALLENGE

While perhaps streamlining and expediting battlespace information transport and display, current and emerging C2 systems still foist battle management decision-making on the humans. One of these decision functions is Generate Battle Courses of Action (GBC). GBC considers which units, agencies, formations, platforms, or weapon systems—individually or as pre-arranged force packages—potentially can and may achieve a particular effect, and rank-orders those potential matches.

GBC takes a matched effect-effector set output from a “Match Effectors” decision (i.e., the principal effect, deliverable(s), & effector(s)), determines what other effect(s) support the principal effect, and builds a web of events representing the actions necessary for the principal effector(s) to achieve the principal effect, and for all participants to arrive in some post-execution disposition.

The GBC DASH aims to answer the following core questions:

• How many decision opportunities are recognized/missed?

• How fast can the HMT make its decision?

• How accurate or error free are the HMT’s decisions?

• How confident is the human operator in the HMT’s solution?

• What are some technical software attributes/requirements that must be considered along with the functional requirements?

Since GBC is expected to generate more courses of actions than manual data collection and analysis processes can derive insights, a hypergraph may be the best presentation of COAs and associated paths.

Software attributes will be assessed based on HMT decision speed, correctness, completeness, and user experience. Experiment details will be distributed along with this RFP.

3.0 REQUEST FOR INFORMATION (RFP) ABSTRACTS

3.1 CONTENT AND FORMAT

NO CLASSIFIED INFORMATION SHOULD BE INCLUDED IN THE RFP RESPONSE.

Section A: A cover page (not to exceed a single page) identifying the company or organization, CAGE Number, street address, and the names, emails, company web page URL, and telephone numbers of the point of contact. In the case of partnerships, please provide the appropriate information for the lead POC. Include the names, emails, and phone numbers of up to five personnel who would be available, if invited by the Government, to attend a MEF DASH event from 21 July – 1 Aug 2025 at the Howard Hughes Operations (H2O) Center in Las Vegas NV. A formal sprint announcement will NOT be posted to SAM.gov, invitations will be sent directly to those organizations that are invited to attend.

State whether your company is a Small Business such as 8(a), Small Disadvantaged Business, Women-own Business, HUBZone Small Business, Veteran-owned Business, or Service-Disabled Veteran Owned Business. Also include a statement as to whether your company is domestically or foreign owned. If foreign, indicate the country of ownership.

Also provide a short summary statement of the company’s or party’s experience/capabilities and a short summary of the organization’s experience in the areas described above. This section is not included in the page count.

Section B: Technical Summary. The Government is assessing the current state-of-the-art and potential near-term solutions. The RFP should reflect an understanding of the MEF decision function, describe the potential product solution, and address coverage of the requirements stated in this RFP (“technical challenge”) by the potential solution. As part of “understanding of the MEF decision function”, include an unclassified military use case (short vignette) that demonstrates the company’s/party’s understanding the MEF decision function, i.e., what in the scenario constitutes a chain of events leading from knowledge about an entity of interest to knowledge about a battle effect with a time window.

The abstract shall not exceed 5 pages including figures. All abstracts may be single spaced with a font no smaller than 11 pt font. All responses to this announcement must be addressed to POCs, as discussed in Section 6.0 of this announcement. Responses should be submitted in Microsoft Office Word or PDF format.

Section C: Cost Summary. As part of its cost proposal, the offeror shall submit the information outlined below, together with supporting breakdowns. All direct costs (travel) should be provided by contractor fiscal year (CFY).

a) Travel: Travel costs must be justified with supporting data and related to the needs of the project. Identify the method of travel, number of travelers, airfare, per diem, lodging, etc

b) CLIN Structure:

CLIN 0001 Travel Firm Fixed Price* CLIN 0002 Data Not Separately Priced

*Not-to Exceed (NTE) Value of $10,000/awardee.

Section D: Security Summary. As part of its proposal, the offeror shall review and complete the security requirements outlined in Attachments 3-6. Not providing the security requirement documentation will result in an incomplete proposal and will not be considered for award.

3.2 ADDITIONAL INFORMATION. The submitted documentation and content thereof become the property of the U.S. Government and will not be returned. It does not commit the Government to reply to information received.

3.3 PROPRIETARY INFORMATION. This notice is part of Government market research. Information received from this request will be considered as sensitive and will be protected as such. Any company or industry proprietary information contained in responses should be clearly marked by paragraph, so that publicly releasable and proprietary information are clearly distinguished. Any proprietary information received in response to this request will be properly protected from unauthorized disclosure. The Government will not use proprietary information submitted from any one source to establish the capability and requirements for any future acquisition, so as to inadvertently restrict competition.

4.0 SPECIAL CONSIDERATIONS. Government representatives may or may not choose to meet with vendors responding to this RFP. Such discussions would only be intended to get further clarification of potential capability to meet the requirements.

The Government will review abstracts and provide email notification no later than 8 August 2025 of those selected for participation in a 15 – 26 September 2025 DASH event at the H2O Center in Las Vegas NV to be held at the unclassified level. If selected and invited by the Government, no more than 8 individuals from each company may participate in the sprint week. Invitees must RSVP no later than 5 September 2025 with employee name, email, phone number, and clearance information to POC identified in Section 6.

5.0 SCHEDULE.

25 July 2025: “Ask Me Anything” on Microsoft Teams (1100 – 1300 Eastern Time) Join the meeting now Meeting ID: 993 145 070 027 Passcode: ts2oz9tC Call in option: +1 410-874-6750 Phone conference ID: 250 638 632#

8 August 2025: Industry abstracts due to Government by 1500 Eastern.

https://dod.teams.microsoft.us/l/meetup-join/19%3adod%3ameeting_6b3d9c041ed04558a40758959e4cee9f%40thread.v2/0?context=%7b%22Tid%22%3a%228331b18d-2d87-48ef-a35f-ac8818ebf9b4%22%2c%22Oid%22%3a%22fe0950f3-e833-4790-a20e-4df60228c554%22%7d

13 August 2025: Government invites selected participants.

27 August 2025: GBC Deep Dive Briefing

5 September 2025: Traveler Details Due

15-26 September: GBC DASH, H2O Center, Las Vegas NV.

• 15 September: Academics and initial battle management scenario run

• 16 – 19 September: Software development

• 19/22 September: Optional mid-course checkpoint with battle management scenario run

• 23-24 September: Software development

• 24-25 September: Final scenario run with software Subject Matter Experts

• 26 September: Travel day

6.0 POINT OF CONTACTS:

6.1 Non-Government Advisors. Non-Government advisors may be used in the evaluation of responses and have signed non-disclosure agreements (NDAs) with the Government. Additional NDAs will not be required. Instead, a response to this RFP will be considered an implicit acknowledgement and acceptance of the fact that non-Government advisors will be assisting the Government in this process.

The Government understands that information provided in response to this RFP is presented in confidence and may contain trade secret, commercial or financial information, and it agrees to protect such information from unauthorized disclosure to the maximum extent permitted or required by –

a) 18 USC 1905 (Trade Secrets Act);

b) 18 USC 1831 et seq. (Economic Espionage Act);

c) 5 USC 552(b) (4) (Freedom of Information Act);

d) Executive Order 12600 (Pre-disclosure Notification Procedures for Confidential Commercial

Information); and

e) Any other statute, regulation, or requirement applicable to Government employees

6.2 Agency Contacts: RFP responses should be submitted electronically, via email (or a DoD SAFE link can be provided) to Technical & Contracting POC’s listed below:

Primary Technical POC:

Lt Col Timothy Wintch

ABMS CFT (AF/A57RB)

timothy.wintch@us.af.mil

Alternate POC:

Maj Corey Ellsworth

ABMS CFT (AF/A57RB)

corey.ellsworth.1@us.af.mil

Alternate POC:

Dr. Elizabeth Frost

711 HPW/RHTWC

mailto:timothy.wintch@us.af.mil mailto:corey.ellsworth.1@us.af.mil elizabeth.frost.7@us.af.mil

Contracting Officer POC:

Breeana Dixon AFRL/RAKHC breeana.dixon@us.af.mil

ATTACHMENTS

1. CDRLs- Scientific and Technical Report

2. Statement of Objective

3. Security Risk Review – AFRLI 61-113

4. Security Program Questionnaire

5. Privacy Act Statement

6. Research and Related Senior and Key Person Profile Worksheet mailto:elizabeth.frost.7@us.af.mil mailto:breeana.dixon@us.af.mil