TAPSoS DMR RFI - 16 May 2025.pdf

Request for Information (RFI)

Airspace Mission Planning Division (C3M)

Theater Air Planning System of Systems (TAP SoS)

Dynamic Mission Replanning (DMR)

THIS NOTICE IS NOT A REQUEST FOR PROPOSAL. This notice is for information and planning purposes only. In accordance with Part 10 of the Federal Acquisition Regulation (FAR), the Government is conducting market research to determine the availability and adequacy of potential business sources in developing the software identified below that meet the Government's requirements. This request for information (RFI) does not constitute a solicitation for bids or proposals and is not to be construed as a commitment by the Government. The information contained herein is subject to change and in no way binds the Government to solicit for or award a competitive contract. Proprietary information and trade secrets shall NOT be submitted in response to this RFI. The Government will not review any submittals with proprietary information or trade secrets.

The Government is not obligated to and will not reimburse respondents for any costs associated with preparing or submitting a response to this notice and submittals will not be returned to the sender.

This RFI is from the Airspace Mission Planning Division (C3M) of the Department of the Air Force (DAF) Command, Control, Communications, and Battle Management (C3BM) Program Executive Office (PEO), located at 16 Eglin Street, Hanscom AFB, MA 01731. DAF PEO/C3BM is seeking unclassified information from interested Contractors.

Any response submitted to this RFI constitutes consent for that submission to be reviewed by Government personnel, Federally Funded Research and Development Center (FFRDC) employees, employees and Advisory & Assistance Services (A&AS) Contractor employees supporting DAF PEO/C3BM employed by Leidos, Inc., Odyssey Systems Consulting Group, LLC, SAVI LLC., Modern Technology Solutions Inc., ASI, ITSC Secure Solutions unless the respondent clearly objects, in writing, to the release of this information to FFRDC employees and A&AS Contractor employees supporting DAF PEO/C3BM in a cover letter accompanying your response.

Overview:

C3M is seeking responses from Industry for a problem set identified as Theater Air Planning System of Systems Dynamic Mission Replanning (TAP SoS DMR). The DAF is currently seeking evidence of relevant experience to assess industry capabilities.

Background:

Modern battlespace in every theater is becoming increasingly complex requiring joint and coalition forces to operate seamlessly across multiple domains – air, land, space, sea, and cyber. Theater Air Planning (TAP) plays a pivotal role in synchronizing air operations with broader military strategies and doctrine to achieve mission success. The planning, execution, and dynamic adaptation of air operations demands the integration of multiple interconnected systems, platforms, technologies, data sources, and processes that, together, form the Theater Air Planning System of Systems (TAP SoS). Current operations manage any changes occurring in the execution of air operations using human to human interactions, which greatly impacts timely execution of a replan and introduces risk for errors in the replan process. Dynamic Mission Replanning (DMR) is proposed to solve this problem. The DAF is seeking solutions to automate and identify Courses of Action (CoAs) for the replan process in order to expedite theater operations. The TAP SoS DMR objective is to address infrastructure changes to the architecture and systems, resulting from change(s) in the plan during execution, to increase the overall speed and effectiveness of

TAP.

References:

TAP SoS DMR Inventory R2

TAP SoS DMR OV-1 and OV-2

(these are documents Controlled Unclassified Information (CUI); see paragraph below for instructions to receive CUI information: “Receiving Controlled Unclassified Information”).

NOTE: These references are provided as additional information and not direction for solution creation. Any questions or concerns regarding the reference shall be identified in a cover letter accompanying your response to the Points of Contact (PoCs) identified below.

Capability Description Summary:

DMR is a capability intended to enable warfighters to rapidly replan complex Air Battle Plans and packages during execution in response to evolving battlespace conditions and changes while in conflict with a pacing threat. TAP SoS DMR occurs in the period between publishing the Air Tasking Order (ATO) and handing over authorities to the battle manager or package commander (Reference Attachment 3, OV-1, see paragraph below for instructions to receive CUI information “Receiving Controlled Unclassified Information (CUI)”).

Current DMR capabilities require operators to monitor data from a huge variety of different sources and manually assess that data for changes and events that require a replan. When a replan is required, operators must manually generate and select CoAs, piecing together the downstream impacts of any changes they may make. This process is manageable for a small number of simple changes, but each additional change can create multiple downstream impacts, each of which can create multiple additional impacts, increasing change impacts exponentially. The purpose of the TAP SoS DMR capability is to automate the ingestion and monitoring of the battlespace, aid the operator in assessing whether changes require replanning, and automatically provide the operator with CoAs that are optimized within the given constraints of the Air Battle Plan actively being executed. This capability is intended to exist within and augment the larger system-of-systems that includes the Kessel Run All Domain Operations Suite (KRADOS), C2Core, and Widow to meet DAF PEO C3BM Enterprise objectives.

Figure 1: System Boundary, Major Functions, Inputs, and Outputs

Figure 1 shows the three main functions that the DMR solution will need to support, with a yellow dashed line for the system boundary, inputs on the left in blue/brown, and downstream consumers in green. In more detail, the main functions that the DMR solution will need to support are:

1. Monitor: Ingest and monitor a wide variety of data sources and display that information to a Command and Control (C2) professional in a manner that enables them to understand the battlespace. Some potential input data types are described in Figure 1.

2. Assess and Decide to Replan: Assist C2 professionals by quickly detecting and assessing changes in the battlespace to determine whether a replan is necessary.

3. Rebuild the Plan: Generate CoAs and/or help C2 professionals generate CoAs that continue to achieve the Commander’s intent while minimizing disruption to the rest of the ATO. Ideally, the solution will generate CoAs automatically and rapidly, giving the operator the ability to quickly choose the CoA that best meets their needs.

Finally, once a CoA is selected, the solution will need to be able to exchange the replanned Air Battle Plan with the larger TAP SoS ecosystem.

Attachment 3, OV-2, shows the operational performers involved in the DMR space. Central to the diagram is the Combat Operations Division (COD), who is responsible for the actual monitoring and replanning efforts. The COD monitors the battlespace for important changes and when a replan is necessary, interacts with many other cells and divisions within the Air Operations Center (AOC) to execute the replanning effort. The diagram does not contain an exhaustive list of groups that the COD interacts with but shows several of the most critical. After the replan has been accomplished, the COD distributes the change to other echelons and other groups within the Operational echelon for execution.

Development of the DMR solution is expected to follow modern software development best practices: iterative development and delivery of capability informed by regular feedback from operators. The security level protection requirement of this capability is anticipated to be, at a minimum, IL6 (Impact Level 6). IL6 accreditation of the capability will be required for any eventual solution(s).

The Contractor is expected to be proficient in both agile development and software development methodology. The Contractor is expected to perform requirements analysis, software design, code development, operational DMR environment, system integration, and DMR Contractor test events (i.e. Formal Release Events (FREs)), with both a Minimum Viable Product (MVP) and Minimum Viable Capability Release (MVCR). The Contractor is expected to support follow-on Government-conducted Development Testing (DT), Operational Testing (OT), and Formal Qualification Testing (FQT) to ensure DMR effectiveness and suitability for fielding. NOTE: all Contractor employees must be U.S.

citizens.

Anticipated activities (subject to change): The Government may issue a solicitation for an initial design, followed by a prototype/development effort, and subsequent production.

At this time, to promote transparency and facilitate dialogue with industry, the Government intends to host an industry day at Hanscom Air Force Base, MA in the upcoming months.

The industry ‘day’ is currently planned for 16-17 June 2025. Contractors interested in attending the industry day should email the Government points of contact (POCs) provided below. In the email indicating interest in attending the industry day, Contractors shall also indicate if they would be interested in an individual/1-on-1 session with the Government, to occur at the industry day. Interested parties are encouraged to return to this SAM.gov posting for further information/announcements. Additional information regarding industry day may also be provided via email directly to the Contractors who have indicated an interest in attendance.

Partnering with Industry and Securing Data Rights:

The Government intends to partner with industry on the development of this new capability; sharing in the development/prototype efforts, as well as the full development of the DMR solution. Both parties will participate in the development of the software, and assessment of the potential use of DoD Software Factories and other organic development environments, in order to share in the capability development, and will result in the Government securing Government Purpose Rights.

Due to the nature of the capability requirements, although not required, the Government strongly encourages developing teaming arrangements to capitalize on industry partner strengths and existing capabilities, for a full DMR solution.

North American Industry Classification System (NAICS) Code:

The anticipated North American Industry Classification System Code (NAICS) for this requirement is 541715. Industry is encouraged to comment on the use of this NAICS Code for this acquisition.

Receiving Controlled Unclassified Information (CUI):

Some of the referenced attachments/figures are Controlled Unclassified Information (CUI).

Due to the controlled nature, these documents are available to respondents upon request.

Interested parties are required to fill out the attached Non-Disclosure Agreement (NDA) to the POCs, identified below. Once approved by the Contracting Officer, CUI documents will be shared via DoD Safe Access File Exchange (SAFE) (http://safe.apps.mil).

NOTE: A current National Institute of Standards and Technology Special Publications (NIST SP) 800-171 Department of Defense (DoD) Assessment with a minimum score of at least 110 is required for Contractors to receive any CUI.

For the NIST SP 800-171 DoD Assessment to be considered current, a compliant basic assessment must have been approved within three (3) years of the date this RFI is posted.

Responses:

Responses to this RFI are due: 30 June 2025, by 5:00PM ET. Responses shall be limited to no more than 20 pages total, in Microsoft Word utilizing Times New Roman, 10 pt font, double spaced, including any image(s), table(s), and/or graph(s). No imbedded files are permitted.

Questions regarding the RFI may be submitted, in writing, via email to the Contracting Officers, Ms. Brenna Gonsalves at brenna.gonsalves@us.af.mil, and Mr. Matthew MacEachern, at matthew.maceachern@us.af.mil as well as Contract Specialists, Mr. Cody Sheehan, cody.sheehan@us.af.mil, and Mr. Christopher Nugent, at christopher.nugent.6@us.af.mil.

RFI Questions will be accepted within ten (10) days of RFI release and may be addressed via email or at an industry day to all RFI respondents in a consolidated response from the Government.

Responses shall be submitted via e-mail to the Contracting Officers, Brenna Gonsalves, at brenna.gonsalves@us.af.mil, and Matthew MacEachern, at matthew.maceachern@us.af.mil as well as Contract Specialists, Cody Sheehan, cody.sheehan@us.af.mil, and Christopher Nugent, at christopher.nugent.6@us.af.mil.

mailto:brenna.gonsalves@us.af.mil mailto:cody.sheehan@us.af.mil mailto:brenna.gonsalves@us.af.mil mailto:cody.sheehan@us.af.mil

All CUI responses must be submitted via DoD Safe (https://safe.apps.mil/) to Brenna Gonsalves at brenna.gonsalves@us.af.mil, Cody Sheehan, at cody.sheehan@us.af.mil, and Christopher Nugent, at christopher.nugent.6@us.af.mil.

DO NOT provide classified information, proprietary information, and/or trade secrets in response to this RFI.

The CUI document(s) in the referenced section and redacted information for this effort is available upon request. Due to the controlled nature, interested parties are required to fill out the attached NDA/CUI form to gain access. Once approved by the Contracting Officer, the documents and unredacted RFI will be distributed via DoD Safe.

Please be advised that all submissions become Government property and will not be returned. A cover page to the response shall provide administrative information (not included in the page count), and shall include the following, at a minimum:

a. Name, mailing address, cage code, DUNS, phone number, fax number, and e-mail of designated POC(s).

b. Recommended North American Industry Classification System (NAICS) code(s).

Include Business size under the recommended NAICS (large business, small business, small, disadvantaged business, 8(a)-certified small, disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business).

c. Any commercial solution opening(s) that you are party to applicable to this effort.

d. Any recommended contract vehicle(s) with scope relevant to this RFI. Including

Government Wide Acquisition Contracts (GWACs), Small Business Innovation Research (SBIR) contracts or other strategic sourcing vehicles that you are party to.

Provide answers to the following questions, numbering the responses as they are identified:

1. Describe your company’s experience within Theater Air Planning.

2. Describe your company’s experience with any Dynamic Mission Replanning effort.

Include any Mission Engineering efforts you have performed in the DMR space or related operational areas. Include relevant information on any commercial programs, Government/contractor developed solutions, contractual efforts/vehicles, platforms supported, key delivered systems, etc.

3. Describe your company’s relevant experience with automating processes and/or systems utilizing Artificial Intelligence (AI) and/or Machine Learning (ML). Include experience with technical solutions related to algorithm work to generate automated CoA generation.

4. Describe your company’s experience creating visualization applications/decision making tools.

5. Describe your company’s experience using a Cloud Infrastructure.

mailto:brenna.gonsalves@us.af.mil mailto:cody.sheehan@us.af.mil

6. Describe your company’s experience with data integration/fusion.

7. Describe your company’s experience with iterative software (SW) deliveries requiring continuous integration into a system. Include how your company addressed updating SW across an enterprise due to those iterations.

8. Describe your company’s experience in developing prototype demonstrations of a solution that would support the Government in a fielded environment. Include any relevant experience in the development and fielding of significantly complex software systems that resulted from the integration of multiple software applications on layered architecture (e.g., operating system and infrastructure).

9. Describe your company’s experience with capability maturation. Include relevant information on the assessments performed, documentation produced, metrics used, timelines, etc.

10. Describe your company’s experience with interfacing to pre-existing dynamic targeting tools.

11. Describe your company’s experience integrating and deploying a Cross Domain Solution among Joint Services including interoperability across multiple security levels.

12. Describe your company’s experience collaborating across multiple external geographically separated stakeholders.

13. Does your company have an integrated digital environment, enabling digital transfers between your company and the Government?

14. Identify your company’s Facility Clearance level(s), including maintenance and storage.

a. Does your company have the ability to work at the Top Secret/Sensitive Compartmentalized Information (TS/SCI) level?

b. Does your company have any approved Special Access Program Facilities (SAPFs)?

c. Does your company have or have the ability to obtain clearances up to Top Secret?

15. Does your company have any commercial capabilities that could be leveraged to address the DMR problem set?

Attachments

1. DMR Inventory R2 (CUI document)

2. C3M Non-Disclosure Agreement

3. OV-1 and OV-2 (CUI document)

Acronyms

A&AS Advisory and Assistance Services ACO Airspace Control Order A/C Aircraft AI Artificial Intelligence AO Area of Operations or Action Officer AOD Air Operations Directive ATO Air Tasking Order ATO AA, AB, AC, PROD Represent days in an ATO cycle BDA Battle Damage Assessment C2Core Command and Control Core C3BM Command, Control Communication Battle Management C3M Airspace Mission Planning Division CC Combatant Commander CFACC Combined Forces Air Component Command CoA Course of Action COCOM Combatant Command COP Common Operational Picture CUI Controlled Unclassified Information DAF Department of the Air Force DFQT Development Formal Qualification Test DoD Department of Defense DMR Dynamic Mission Replanning

DT Development Test

FFRDC Federally Funded Research and Development Center

FRE Formal Release Events GWACS Government Wide Contracts IL (6) Impact Level (6) ISR Intelligence, Surveillance, and Reconnaissance JFACC Joint Forces Air Component Commander JFC Joint Forces Command JIO Joint Integrated Order JIPTL Joint Integrated Prioritized Target List

JTL Joint Task List JTO Joint Tasking Order JAOP Joint Air Operations Plan KRADOS Kessel Run All Domain Operations Suite LOE Level of Effort MAAP Master Air Attack Plan MISREP Mission Report ML Machine Learning MPC Mission Planning Cell MVCR Minimum Viable Capability Release MVP Minimum Viable Product NAICS North American Industry Classification System NDA Non-Disclosure Agreement NIST SP National Institute of Standards and Technology Special

Publications NSL No Strike List PEO Program Executive Office POC Point of Contact OT Operational Test OV-1 Operation View 1 OV-2 Operational View 2 TAP SoS Theater Air Planning System of Systems RFI Request for Information ROE Rules of Engagement RSTA Annex Reconnaissance, Surveillance, and Target acquisition SAFE (DoD) Safe Access File Exchange SAP Special Access Program SBIR Small Business Innovation Research SEIC System Engineering Integration Contract SITREP Situation Report SPINS Special Instructions SW Software TACREP Tactical Report TS/SCI Top Secret/Sensitive Compartmented Information Wx Weather

Background: