Atch 3 - MASH SOO.pdf

MASH CLOSED CALL (SOO)

1.0 OBJECTIVE

The Joint All Domain Persistent Adaptive Collaborative Technologies Project is Human-Machine Teaming (HMT) concepts that leverage AI/Automation capabilities to support Battle Mangers. C2 Decision Advantage Events provide support for ABMS Transformational Model Battle Management and an opportunity to learn about and explore many different AI/automation approaches for Battle Management. Furthermore, the events and R&D aim to ensure warfighter involvement in the development of AI/autonomy and further identify areas where autonomy would support Battle Managers.

The goal is to include industry to ensure work being done to develop and adapt the latest, cutting-edge AI/automation approaches can be leveraged and adapted to the needs of Battle Managers. This will be accomplished by seeking unique and innovative solutions to accomplish the defined technical requirements.

2.0 SCOPE

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 Command, Plan, 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.

2.1 Transformation Model

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.

Figure 1: Transformational Model – Battle Management Subfunctions.

In OEs where these assumptions apply (which will be the case for the pacing challenge), the TM-https://sam.gov/opp/a6f8e78859cd45d294a8df70906c90f5/view

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 through rigorous defensible analysis.

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 Multi-Decision Advantage Sprint for Human-Machine Teaming (MASH) Events

The ABMS CFT (AF/A57RB) and Air Force Research Laboratory, 711 Human Performance Wing (711 HPW) will host a series of events. These events will conduct Research and Development surrounding the Transformational Model – Battle Management (Figure 1), with the function(s) varying for each event. The event is seeking the following: 1) understanding of the Transformational Model 2) alignment with the Transformational Model 3) maturity of software services that completes a single decision function (PAE, MEF, GBC)

During these events the contractor shall accomplish the following: Traveling to attend the event in Las Vegas, participating software development teams will witness a battle management crew making battle management decisions in a simulated combat environment for the three specified decision functions. The participating software developers will then apply the Transformational Model (the functional description of the decision functions) and their creativity in applying the application microservice developed at previous DASH event(s) (PAE, MEF, GBC) 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. As part of the event, each team will have the opportunity to demonstrate how their software affects overall human-machine team decision making during culminating battle management scenarios. During these scenarios, each team will have opportunities to run their software addressing one or more of the three specified decision functions. The software solutions for all three decision functions, across one or more teams, will be ran simultaneously connecting via a government owned API to demonstrate how the various software solutions integrate and affect the overall human-machine team decision making. The contractor shall not be required to connect directly to other contractors’ services/software. The contractors shall connect to the government owned software and adhere to the messaging standard and API provided by the government stakeholders. Evaluation 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.

Offerors must describe the current maturity level of their proposed tool. Is it a conceptual model, a lab prototype, or a market-ready product? Evidence of prior application or testing is highly encouraged.

Crucially, offerors must describe their plan and technical approach for achieving a live, functional demonstration during the MASH event. Proposals must explicitly detail how their tool is designed to:

1. Function as a Containerized Service: Operate within a containerized environment provided by the government.

2. Integrate via a Well-Defined API: Expose a stable API that can be called by the Government-owned Digital Assist Orchestrator. A preliminary API definition in the proposal is highly encouraged.

3. Process Dynamic Data: Ingest real-time, streaming data from the government's simulation environment.

The primary goal is to demonstrate the offeror's readiness to integrate and function in a live, government-hosted ecosystem, not to deliver a final, static codebase for government acceptance at the conclusion of the event.

3.2 EXPECTED OUTCOMES

The government is not procuring a final software deliverable through this MASH event.

Instead, participation will be evaluated based on the offeror's ability to successfully demonstrate the following key outcomes within the two-week event window:

1. Successful Live Integration: The offeror's tool successfully integrates with and is called by the Government Digital Assist Orchestrator during live scenario runs. This is the primary measure of success.

2. Demonstrated Functional Relevance: The AI tool demonstrably processes dynamic scenario data and provides outputs that are relevant to the targeted Decision Function (e.g., PAE, MEF, GBC).

3. Contribution to Human-Machine Team Performance: The demonstrated outputs of the tool contribute to the overarching goal of enabling the human operator to make better, faster decisions. The tool should help the user make sense of a complex environment rather than simply presenting more raw data.

At the conclusion of the MASH, government assessors will record the performance and integration success of each vendor's tool. This record of demonstrated capability will serve as the primary output of the event. No transfer of intellectual property or final code delivery is required under this agreement.

3.3 REPORTING

At the conclusion of each event, the Contractor shall compile findings within and deliver a presentation that includes a summary of the work that was conducted, any relevant metrics, and lessons learned, via a Test Scientific and Technical reports (CDRL A001)

4.0 DELIVERABLES

4.1 In addition to the reporting and data deliverables identified in the previous section 3.2 the Contractor shall deliver the following:

4.2 Software deliverables & schedule

During the event the contractor will be required to adhere to the government owned messaging standard and API for integration with Government Software System. All messaging outputs will be recorded and available for future Government use.

5.0 OTHER REQUIREMENTS

5.1 SECURITY AND OPSEC

5.1.1 General Operations Security (OPSEC) procedures, policies and awareness are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. The Critical Information and Indicator List (CIIL) and the 711th HPW OPSEC Plan will be provided upon request by AFRL/711HPW Information Protection Office. While working on the government installation, OPSEC guidance and OPSEC training will be provided by AFRL/711HPW Information Protection Office. This training will ensure contractors are familiar with 711th HPW’s CIIL and OPSEC Plan as it pertains to their contract. The contractor shall apply OPSEC in their management of their current program IAW AFI 10-701 Operations Security.

5.1.2 All contractor personnel require a minimum of a Tier 1 background check (T1)/SF85 for any position that requires access to the internet, use of automated information systems to cover standalone computers or unescorted entry into restricted or controlled areas prior to reporting for duty in support of any requirement. The investigation is not for a security clearance; it is for a position of trust. This is a mandatory requirement set forth in DoDM 5200.02_AFMAN 16-1405, Air Force Personnel Security Program. All documentation required for security certification shall be the responsibility of the contractor.

5.1.3 All documents, including papers, abstracts and posters shall be cleared by AF prior to public release.

5.1.4 Highest Security Classification [Unclassified]

5.2 SAFETY REQUIREMENTS

5.2.1 The Contractor shall comply with all applicable federal, state, and local safety, occupational health and environmental regulations.

6.0 AFRL POLICY ON EMPLOYMENT OF NON-US CITIZEN CONTRACTORS

6.1 Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S.

Government Information Technology networks in connection with the work on this contract must be U.S. citizens. Possession of a permanent resident card (“Green Card”) does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

7.0 FEDERAL HOLIDAYS

7.1 The prices / costs in Section B of the contract include holiday observance; accordingly, the Government shall not be billed for such holidays, except when services are required by the Government and are actually performed on a holiday. The following days are contract holidays: New Year’s Day, Birthday of Martin Luther King, Jr., Washington’s

Birthday, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, and Christmas Day.

MASH CLOSED CALL (SOO)