FA8217_CRC_RRSVS_TCRR_RFI_2026_final .pdf

CUI

CUI

USAF AFLCMC/PAE C3BM

Command, Control, Communications and

Battle Management Program Office

Request for Information Pursuant to FAR Part 15.201(e)

30 January 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: Christine Israel, christine.israel@us.af.mil mailto:christine.israel@us.af.mil

CUI

DESCRIPTION

The Air Force Life Cycle Management Center, Portfolio Acquisition Executive Command, Control, Communications and Battle Management Program Office (AFLCMC/PAE C3BM) is conducting this Request for Information (RFI) to solicit information about current or future voice/data communications suite within Tactical C2.

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 a RFP in the future. This RFI is issued to better understand current Radio Frequency (RF) voice and data communications and related capabilities. 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. AFLCMC/C3BM 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 because 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 in the heading QUESTIONS.

BACKGROUND

The USAF is conducting market research to assess industry’s ability to support a Remote Radio

Secure Voice System (RRSVS) capability extension for the Control and Reporting Center (CRC) to align with the existing Tactical Operations Center – Light (TOC-L) Major Release 2 (MR 2) system architecture. The Government has an existing TOC-L System MR 2 design developed under the current rapid prototyping effort with Booz Allen Hamilton. The TOC-L MR 2 design already satisfies most of the RRSVS functional and interface requirements and the Government is assessing options to extend and iterate on this design to fully support CRC’s Remote Radio requirements with minimal non-recurring engineering (NRE). The Government seeks a RRSVS system for the CRC with as much TOC-L commonality and Advanced Battle Management

System (ABMS) integration technologies as possible for technical interoperability, cost, training, and product support efficiencies. The goal of the TOC-L extension to the current RRSVS is to

CUI

enhance the technical capabilities of the RRSVS by adding TOC-L integration to the RRSVS, thus providing a TOC Remote Radio (TCRR).

The Government seeks to develop a TCRR system that has all the capabilities of the radio subsystems of TOC-L MR2. The TCRR is expected to provide the TOC-L hardware and integration to the Remote Radio interface. When completed TCRR should provide a remote suite of TOC mission-capable radios to be used via a remote interface with TOC-L MR 2. The TCRR should support mobilizing its equipment to forward battle management areas to support secure voice and data communications during battle management activities when connected to a TOC-L

Enabled CRC. The CRC concept of the future involves multiple systems working together to provide battle managers with local and remote Line-of-Sight (LOS) radio secure voice and data capabilities. TOC-L and TCRR are both described in this RFI as the TOC-L interfaces will be used to remotely control the TCRR and both systems are expected to use the same radios, control and switching equipment and communications interfaces.

SCOPE

This document captures the need for an overarching CRC RRSVS Tech Refresh/Extension capability that aligns as much as possible with the TOC-L MR 2 architecture summarized below.

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

TOC-L MR 2 Architecture:

Specifically, CRC PMO requests information on capability of integrators to build a TCRR that allows tactical C2 operators to have access to external mobile radios, integrated under a single user interface at the CRC, that works seamlessly across a long-haul interface. Furthermore, this system should be scalable and highly configurable to the needs of an individual CRC operator.

The TCRR system should allow TOC-L Enabled CRC operators, that are co-located or disaggregated, to configure, control, and use remoted radios for battle management voice control of aircraft and surface assets and provide data from co-located sensors, joint forces, and other assets that can be integrated into the radio’s RF interfaces and networks. To that end, the TCRR should include all the TOC-L MR 2 F Radio Module, T Transport Module, and as much of the O

Operations Module as needed to support the REDCOM switching gear, two REDCOM

Communications Interface Panels, and the REDCOM Sigma software.

At AFLCMC/Cloud-Based Command and Control (CBC2), the TOC-L, and CRC Branches of the Deployable Systems have determined that the TCRR must:

• Integrate with any CRC sensor

• Work with the same transit case system as TOC-L

• Use the same self-encrypting L3Harris radios as TOC-L for HF/VHF/UHF (L3Harris

PRC-160 and PRC-167 models) o Provide NSA Type 1 encryption for both voice and data

• Use the same external L3Harris 50-watt RF amplifiers connected to the PRC-167 radios

• Provide an interface to work with the CRC provided long-haul connections

(COMSATCOM, MILSATCOM, 4G/5G, or commercial internet) o TCRR I/O to the long-haul is to be bulk encrypted via a KG-175 encryptor

• Work with portable power sources or connect to power sources provided at remote sites

• Provide the same voice/data switching systems as the REDCOM systems in TOC-L

• Provide the same user interfaces as provided by the REDCOM Sigma software in

TOC-L

• Be configurable to the number of radios in the TCRR

CUI

• Be able to set up/teardown within the allotted timeframes set forth in the TCRR SRD

• Meet all requirements set forth in the TCRR SRD o See Bidder’s Library to find TCRR SRD

RESPONSES

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

1. Technical Approach and Design Reuse

a. Describe your approach to delivering a Remote Radio capability for the CRC that integrates with an existing TOC-L system architecture

b. Identify whether your approach would:

i. Reuse existing design

ii. Require modification of an existing design

iii. Require development of new architecture

c. Identify specific technical artifacts you would require to begin work

2. Data Rights and Government-Furnished Information (GFI)

a. Identify the minimum technical data and documentation required from the

Government to avoid redevelopment of system architecture and interfaces

b. Describe how limitations in available Government data rights would affect cost, schedule, and technical risk

3. Non-Recurring Engineering (NRE)

a. Provide a rough order of magnitude (ROM) estimate of NRE required to:

i. Understand the existing TOC-L MR 2 design

ii. Develop or modify system architecture to integrate remote radio modernization functionality

4. Schedule Realism

a. Provide an estimated timeline from award to delivery of an operational prototype, including:

i. Onboarding and familiarization

ii. Architecture development

iii. Integration and testing

iv. Fielding of initial systems

b. Identify schedule drivers that could not be reduced without increased risk

5. Integration and Sustainment

a. Describe your approach to:

i. System integration and interoperability with TOC-L MR 2 and

ABMS technologies

ii. Help desk and Contractor Logistics Support

iii. Cybersecurity accreditation (e.g., Identity, Authentication, Authorization, Traceability (IATT) and Authority to Operate (ATO))

CUI

6. Cost Efficiency and Lifecycle Considerations

a. Describe cost efficiencies, if any, that can be achieved by:

i. Leveraging existing TOC-L design

ii. Using common integration and sustainment approach

b. Identify any cost drivers

7. Relevant Experience

a. Describe prior experience delivering remote radio or similar C2 capabilities

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 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, Wendy Farley at wendy.farley@us.af.mil and Contract Specialist, Carlos Michel at carlos.michel@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) mailto:wendy.farley@us.af.mil mailto:carlos.michel@us.af.mil

CUI

POC (Name, Email, Phone)

Facility/Safeguarding Clearance Levels

Security POC (Name, Email, Phone)

Technical POC (Name, Email, Phone)

Secure Fax or SIPR Email if Available

Section 2 – RFI Technical Response

The response shall address the information requested in the heading RESPONSES 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) Mountain Standard Time

(MST), 2 March 2026. Please notify the Contracting Officer, Wendy Farley at wendy.farley@us.af.mil and Contract Specialist, Carlos Michel at carlos.michel@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 the

Contracting Officer, Wendy Farley at wendy.farley@us.af.mil and Contract Specialist, Carlos

Michel at carlos.michel@us.af.mil, 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 the Contracting Officer, Wendy Farley at wendy.farley@us.af.mil and

Contract Specialist, Carlos Michel at carlos.michel@us.af.mil, respectively, for unclassified questions.

The Government does not guarantee responses to questions received after 2 March 2026 @ 1200

MST will be answered in time for the submittal deadline.

mailto:wendy.farley@us.af.mil mailto:carlos.michel@us.af.mil mailto:wendy.farley@us.af.mil mailto:carlos.michel@us.af.mil mailto:wendy.farley@us.af.mil mailto:carlos.michel@us.af.mil