Attachment 2 JADPACT DASH SOO.pdf

Transformational Model – Battle Management Decision Advantage Sprint for Human-machine teaming (DASH) events Statement of

Objectives (SOO)

1.0 Objective

Decision Advantage Sprint for Human-machine-teaming (DASH) events directly support command and control (C2) decision advantage capability development and are an opportunity to learn about and explore many different software approaches for building Battle Management machine teammates.

Furthermore, the events aim to ensure warfighter involvement in the development of AI/autonomy and further identify areas where autonomy would help a Joint All-Domain (JAD) Battle Manager. DASH events also foster connections with industry partners that are working on machine-aided Battle Management functions.

2.0 Scope

The DAF Advanced Battle Management System (ABMS) Cross Functional Team (CFT) (AF/A57RB) and Air Force Research Laboratory, 711 Human Performance Wing (711 HPW) will host a series of two-week DASH events occurring every 2-3 months at the Howard Hughes Operations (H2O) Center in Las Vegas, NV. Each DASH will focus on a specific decision function from the Transformational Model – Battle Management (Figure 1). Participants will be limited based on resource, time, and space constraints.

2.1 Transformation Model for Decision Advantage

Deriving effective C2 capability development toward decision advantage requires a clear understanding of what C2 decisions are. The Transformational Model for Decision Advantage (TM-DA) delivers a quantitative model for the Joint Warfighting Function of C2 as the Command, Plan, and Battle Management decision domains. Each of these decision domains are decomposed in the TM using model-based systems engineering and brings these C2 decisions to light in a very detailed manner. The TM describes military decisions being made within a human-machine team (HMT), including specific choices within decision functions, the battlespace information needed to inform said choices, and the decision function outputs. Therefore, the TM provides functional 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.

https://sam.gov/opp/a6f8e78859cd45d294a8df70906c90f5/view

Figure 1: Transformational Model – Battle Management Subfunctions.

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. The resulting analysis delivers C2 decision advantage requirements to military capability developers and acquisition professionals.

3.0 Technical Requirements

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.

3.1 Decision Advantage Sprint for HMTs (DASH)

During each DASH, participating software development teams will witness a battle management crew making battle management decisions in a simulated combat environment for the specified TM decision function. The participating software developers will then apply the TM’s functional description of C2 decision-making and their creativity in developing an application/microservice that helps the humans make faster and higher quality battle management decisions. Battle management warfighters will be teamed with coders to provide operational perspective and feedback. Software developers will also be asked to share insights from a technical implementation point of view. At the end of the DASH, each development team must demonstrate how their software affects overall human-machine team decision making during a culminating experiment. Software attributes will be measured based on HMT decision speed, correctness, completeness, and user experience. 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.

4.0 Other Requirements

4.1 OPSEC: The technical research areas under this contract shall be specified per task order.

At minimum, the contractor shall provide OPSEC protection for all sensitive/critical information and indicators involved in execution of this contract/Task Order, as defined by AFI 10-701 (Operations Security). 711 HPW Critical Information and Indicators are protected under the 711 HPW Operations Security Program and the 711 HPW Critical Information and Indicators List (CIIL). Contractor employees granted access to critical information and indicators will be provided initial OPSEC training by the 711 HPW OPSEC Coordinator upon in- processing and prior to being granted access to CIIL items related to the contract/Task Order. The contractor will also participate in 711 HPW's annual OPSEC training and education programs, which includes periodic updates and refresher training on CIIL items applicable to the contract/Task Order. The 711 HPW OPSEC coordinator will evaluate the OPSEC posture of AF contract activities and operations.

4.2 O&M Fiscal Considerations: To satisfy the Purpose Statute, proposed funding must be proper for the work to be performed (31 USC Sec. 1301 & DoD FMR, vol. 14, ch. 2, para.

020202.B.). The scope/purpose of the contract must be analyzed to ensure the use of O&M funds is proper and not an Anti-Deficiency Act violation. IAW the DoD Financial Management Regulation, RDT&E will finance research, development, test and evaluation efforts, including procurement of end items, weapons, equipment, components, materials and services required for development of equipment, material, or computer application software.

Transformational Model – Battle Management Decision Advantage Sprint for Human-machine teaming (DASH) events Statement of Objectives (SOO)