ABMS CBC2 BC3 RFI 08 Jan 26.pdf

CUI

CUI

AFLCMC/PAE C3BM/C3B

Advanced Battle Management System (ABMS)

Request for Information (RFI)

07 Jan 2026 Version 1.0

Controlled by: AFLCMC/PEO C3BM Controlled by: PEO C3BM CUI Categories: CTI DISTRIBUTION STATEMENT C. Distribution authorized to U.S. Government agencies and their contractors. Other requests for this document shall be referred to AFLCMC/PEO C3BM.

POCs: Cahi Hardy, cahi.hardy@us.af.mil

CUI

DESCRIPTION

The Air Force Life Cycle Management Center, Portfolio Acquisition Executive Command, Control, Communication, & Battle Management, Advanced Battle Management System Division (AFLCMC/PAE C3BM/C3B) is conducting market research to identify potential sources that possess the technical data, expertise, capabilities, and experience to meet qualification requirements to provide Battlespace Command and Control Center (BC3) software capabilities to the Cloud Based Command and Control (CBC2) program.

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. It is important to note that this RFI is not a

Request for Proposal (RFP). This RFI is issued solely for information and planning purposes. It does not constitute an RFP or a promise to issue an RFP in the future. The information provided in this RFI is subject to change and is not binding upon the U.S.

Government. This RFI does not commit the U.S. Government to contract for any supply or service. Further, AFLCMC/PAE C3BM/C3B is not seeking proposals at this time and will not accept unsolicited proposals. Responders are advised the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the responder's expense. Not responding to this RFI does not preclude participation in any future RFP, if issued. The U.S.

Government has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur costs for which reimbursement would be required or sought. This notice shall not be construed as a commitment by the Government to issue a solicitation or ultimately award a contract, nor does it restrict the Government to a particular acquisition approach. Any information provided to the Government as a result of this RFI is voluntary. The information, data, comments, or reactions obtained may be used as research for future solicitation.

Respondents will not necessarily be notified of the results of the review from this RFI. All submissions will be used for review in the context of this RFI or related potential future solicitations and will be held and used for these purposes only. Submissions will not be returned to the respondent.

Nongovernmental A&AS support may be utilized in the review process of RFI submissions.

These nongovernmental support staff are covered directly by Nondisclosure Agreements (NDAs) with the US Government as a condition of employment. Any respondent to the RFI with concerns should notify one of the POCs listed above.

BACKGROUND

The USAF seeks to develop a cross-cutting portfolio of complementary, linked projects and programs for Advanced Battle Management System (ABMS). The goal of ABMS is to realize the vision of Joint All Domain Command and Control (JADC2), and to enhance warfighting capabilities by enabling any sensor to inform any shooter in any domain.

The Government seeks to develop a “Team of Teams” of ABMS software providers to include government software programs, government laboratories, academia, and defense & commercial industry that can onboard and grow software applications into an ABMS microservices

CUI

architecture. The Government requires software development teams to integrate, maintain, and evolve code, services, and applications that interface with other components by coordinating and synchronizing with a Software Integrator (separate from this contract) to deliver advanced capability for the warfighter.

Future conflicts will not be limited to air, space, surface, sub-surface or cyber domains in isolation.

Rather, they will require that individual military activities be integrated such that activities in one domain enhance the effectiveness of those in other domains and compensate for vulnerabilities.

This is the vision for JADC2. ABMS is a top modernization priority for the USAF and is the U.S. Space Force and U.S. Air Force’s primary contribution to enable JADC2. The USAF’s ABMS program will enable decision superiority by delivering relevant information and capabilities to warfighters and operators at all echelons. ABMS will integrate current and future sensors; develop applications that leverage machine learning (ML) and artificial intelligence (AI), sophisticated algorithms and multi-layered protections to make sense of massive amounts of trusted data; link space capabilities with weapon systems and personnel across domains; and design pods, platforms, pathways, procedures, and policies that connect and integrate the warfighter better and faster than in any other time in our history.

The Chairman of the Joint Chiefs of Staff issued Joint Requirements Oversight Council Memorandum (JROCM) 075-19 which established the foundational requirements for JADC2, which, in turn, has formed the foundation for ABMS. JROCM 075-19 established that JADC2 must:

• Enable secure, resilient C3, battlespace awareness, integrated fires

• Encompass any sensor, any shooter

• Seamlessly connect forces from the Strategic level to the Tactical level of warfare

• Provide a coherent architecture that empowers forces at the edge using computing, processing, data storage, search, machine learning and artificial intelligence

• Enable operations over multi-trust/zero-trust networks

• Enable a multi-spectrum mesh infrastructure

• Tolerate disconnected intermittent, low-bandwidth environments

• Provide a means to condition and index both new and legacy data

• Identify mechanisms for coalition partner participation

To meet the JROCM directive, ABMS is pursuing a digital transformation effort that leverages digital engineering, open architecture, and open standards. To perform an enterprise-level digital transformation, ABMS seeks to leverage the advantages of cloud computing, Platform-as-a-Service (PaaS), Infrastructure as-a-Service (IaaS), application containerization, microservices architecture, and Continuous Integration/Continuous Delivery (CI/CD) pipelines. ABMS software will leverage digital infrastructure to deliver resilient Command and Control (C2), battlespace awareness, and integrated fires capabilities to joint and coalition forces in disconnected, intermittent, and low-bandwidth environments. ABMS software will be designed to maximize the use of available storage and compute/processing power from CONUS/OCONUS cloud to the tactical edge and use artificial intelligence and machine learning capabilities to enable optimal decision making for C2 operators.

Software capabilities will be planned, acquired, developed, tested, and integrated in an iterative and incremental manner via a CI/CD application ecosystem to assess operational value and make subsequent portfolio decisions.

CUI

Scope This document captures the need for an overarching ABMS Cloud Based Command and Control (CBC2) a multi-user interface solution, addressing the near term/fight tonight critical capabilities.

That supports rapid integration, can scale to support the larger ABMS Enterprise, and operate at multiple classification and releasability levels in both a cloud and edge environment. The capability will initially support the Homeland Air Defense Sectors (ADS), Tactical Operations Center –Light (TOC-L) enabled Control Reporting Center (CRC) and Air Base Air Defense System (ABADS).

CBC2 has identified Battlespace Command and Control Center (BC3) software as the near-term Battle Management Command and Control (BMC2) user interface solution for CBC2 until other user interface solutions can scale/mature. BC3 is comprised of commercial software Multi-Source Correlator Tracker (MSCT), MSCT Display and separately funded BC3 extensions. For clarity, these existing BC3 extensions provide capabilities such as enhanced data fusion algorithms, mission-specific symbology sets, and interfaces for legacy data links.

Responses can be at the Secret//Collateral level of classification.

The ABMS CBC2 Software Integrator will facilitate the standup of a CI/CD pipeline that allows for the management of multiple software portfolios and integration of the capabilities developed both internally and externally to ABMS. The Contractor will leverage this ABMS CBC2 CI/CD pipeline.

The Software Integrator team will be focused on practice and process consistency across multiple capability providers for engineering, User Interface/ User Experience (UI/UX), and product management to produce program outcomes. The Contractor will work closely with the Software Integrator and all other capability providers (CPs) to ensure the alignment of technical, program, security, Agile process, and architectural goals and to ensure consistency of interfaces and standards. They will collaborate with this larger government-Contractor team and operate under the management of a Software Integrator who will drive architectural decisions and ensure seamless integration of disparate development activities. The Contractor will also work with the Software Integrator and all other CPs to ensure the BC3 capability can integrate with ABMS CBC2 microservices/services, the new services can be supported at a system-level, and there is training for all levels of users.

The contractor will also leverage the Government-provided cloud environment for conducting all software development activities. The Software Integrator will provide the Infrastructure as Code (IaC) and Configuration as Code (CaC) for deploying onto various Kubernetes distributions via the ABMS CBC2 CI/CD pipeline. This will include environments with different levels of connectivity, as well as classified and unclassified environments. The Government envisions the Software Integrator maintaining an integrated digital environment (IDE) that individual Capability Providers will integrate into for their development activities.

CUI

RESPONSES

Interested parties may respond to this RFI in their own format, however, the response must not exceed 5 pages, Times New Roman, 12 pt font, and must provide, at a minimum, the following information:

CBC2 is seeking to procure MSCT software licenses with BC3 extensions and software development activities.

BC3 licenses (along with any developed capabilities) will be provided as GFE to CBC2’s selected contractor(s) responsible for the assembly and delivery of CBC2 hardware.

CBC2 intends to contract separately for the deployment, installation, operations, maintenance, and management of the hardware solution components.

The BC3 software provider (“contractor”) shall provide system development & integration support. The contractor will be responsible for participating in integration efforts, product roadmap workshops, agile meetings, test, cybersecurity, technical interchange meetings associated with CBC2-directed product enhancements, improvements, and development efforts.

Data & Software Rights: The Government anticipates that any new software code, modifications, or enhancements developed under this effort will be delivered with, at a minimum, Government Purpose Rights (GPR). Respondents should briefly describe their standard licensing models and their ability to accommodate GPR requirements for derivative or newly developed capabilities.

Additionally, the contractor shall be available as subject matter expert(s) with regard to operational questions and the maintenance of the software, including software verification.

The contractor shall support CBC2’s Helpdesk, to diagnose and troubleshoot software difficulties encountered by the users.

The contractor may be required to travel to equipment at the specified locations, or the equipment may be delivered to the contractor. The contractor shall perform maintenance, repair or supply action required affecting a repair to the fielded software.

Interested firms who believe they are capable of providing the above mentioned software and services are invited to indicate their interest by providing a response as outlined below.

The information you share may be classified up to (S//Collateral) as well as proprietary, as applicable. The government will handle and publish the information accordingly within the

CUI

appropriate classification channels while protecting proprietary information (material marked as proprietary will not be shared with any other contractors). The incorporation of any vendor information into the Government Roadmap does not imply the DoD will automatically endorse, integrate, or assess your Technology or Product.

Note: RFI submissions are encouraged for the broadest dissemination of information. The intent of the RFI is for partnering DoD Services and potentially (as allowed by proprietary and classification markings) other industry partners to leverage this information. Please consider the implication when using proprietary markings.

For the information provided, specify what has been accomplished under Government funded

Contract Research and Development and what has been accomplished under Independent

Research and Development (IRAD), or other relevant past performance/execution of related activities.

NOTE: Care must be taken to ensure the proper classification of the responses. Classification of the responses can be U, CUI, or S Collateral; although for this specific RFI, it is expected that responses will be CUI. For reference, utilize the applicable Security Classification Guide (SCG) as required.

Section 1 – Company Information

The response shall provide administrative information, including the following as a minimum per the table below. Respondents are further requested to indicate their status as a Foreign-owned/Foreign-controlled firm and any contemplated use of foreign national employees for this effort. This information should be provided via email to the Contracting Officer, Cahi Hardy at cahi.hardy@us.af.mil and Contract Specialist, Katharine DeConzo at katharine.deconzo@us.af.mil respectively, for all submissions.

Category Response

Company Name and Mailing Address

(Include Outer and Inner envelope address if sending Secret Collateral)

Company CAGE Code and Unique Entity Identifier (UEI)

Overnight Delivery Address

(If different from mailing address)

POC (Name, Email, Phone)

Facility/Safeguarding Clearance Levels

Security POC (Name, Email, Phone)

CUI

Technical POC (Name, Email, Phone)

Secure Fax or SIPR Email if Available

Section 2 – RFI Technical Response

Section 2 of the response shall address the information requested in Section 3.1 of this RFI.

Proprietary information, if any, MUST BE CLEARLY MARKED. Please be advised that all submissions will be reviewed by government personnel only for this RFI and potential future solicitations and will not be returned. Respondents are advised that employees of commercial firms, Federally Funded Research and Development Center, and University Affiliated Research Centers under contract with the Government may be used to administratively process submissions and provide technical reviews requiring access to other contractors’ proprietary information.

These contractors have executed nondisclosure agreements prohibiting their contractor employees from disclosing any information submitted by other respondents/contractors or using such information for any purpose other than that for which it was furnished.

RESPONSE SUBMISSION INFORMATION

Responses for this RFI are due no later than noon (12pm) Eastern Standard Time (EST), on

Monday 09 February 2026. Please notify the Contracting Officer, Cahi Hardy at cahi.hardy@us.af.mil and Contract Specialist, Katharine DeConzo at katharine.deconzo@us.af.mil respectively, for all submissions.

Requirements for Submission:

All response submissions shall be submitted via email appropriately as to whether they address any proprietary, CUI, or classified information. Questions shall be submitted via email to Contracting Officer, and Contract Specialists, respectively. (For unclassified questions).

QUESTIONS

All questions regarding this announcement shall be submitted via email appropriately as to whether they address any proprietary, CUI, or classified information. Questions shall be submitted via email to Contracting Officer, Cahi Hardy at cahi.hardy@us.af.mil and Contract Specialist, Katharine DeConzo at katharine.deconzo@us.af.mil respectively. (For unclassified questions).

The Government does not guarantee responses to questions received after will be answered in time for the submittal deadline.