RFI MCS-U.pdf

REQUEST FOR INFORMATION

Tactical Air Control Party Modernization (TACP-M)

Mobile Communications System (MCS)-Universal

1.0 Introduction

This Request for Information (RFI) is for the Air Force Special Warfare (AFSPECWAR)

MCS-Universal (MCS-U) program, which will provide a vehicle agnostic communications/ command and control (C2) system for Tactical Air Control Party (TACP) operators while on the move (OTM) and at the halt (ATH).

THIS IS A REQUEST FOR INFORMATION ONLY. This RFI is issued solely for information and planning purposes – it does not constitute a Request for Proposals (RFP) or a promise to issue an RFP in the future. This RFI does not commit the Government to contract for any supply or service whatsoever. Further, the Air Force is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that 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 interested party’s expense. Not responding to this RFI does not preclude participation in a future RFP, if any is issued. No acquisition approach or contract strategy has been determined.

2.0 Background

MCS-U is an evolution of mobile communications and command and control system capabilities in AFSPECWAR vehicles. Previous MCS capabilities were designed and customized for specific vehicles.

MCS-U capabilities provide AFSPECWAR teams: platform agnostic mobile communications; maneuverable and survivable tactical C2 node; and the ability to network

AFSPECWAR teams across the battlefield to aggregate at the decisive point on behalf of the

Commander, Air Force Forces. The capabilities leverage Advanced Battle Management

System contributions in support of Joint All Domain Command and Control as an integrated capability within the Department of the Air Force Battle Network. MCS-U resides within the

TACP Weapon System and provides interoperability with AFSPECWAR teams across any

Major Command.

MCS-U provides TACPs with critical voice, data, and video communications to perform the

AFSPECWAR missions, with vehicles connected through a mesh network. MCS-U provides an integrated communications/C2 capability, including multiband and high frequency radios, a video data link, computing devices, user interface equipment, networking equipment, navigation equipment, and software.

3.0 Anticipated Requirements

If a contract is awarded, the MCS-U program is planned to provide solutions that are interchangeable/common between AFSPECWAR vehicles as much as possible. A System

Requirements Document (SRD) or similar detailed written requirements will be part of an

MCS-U RFP, if issued. Anticipated capability requirements are shown in the attached

Requirements Document. Specific program requirements (prototyping, production, fielding, etc.

are to be determined.

4.0 Tentative, Unapproved Schedule

Draft SRD: FY27

Draft RFP: FY27

Limitations: This program is pending formal acquisition approval, as well as funding approval, which may impact the schedule above. The contracting approach has not been determined and may change based on industry responses to this RFI and other market research efforts.

5.0 Requested Information

The TACP-M Program Office is requesting industry input/guidance on the MCS-U program, including information on production ready technologies and components that would meet

MCS-U requirements and any further development work anticipated. Component specifications, component reuse feedback, certifications, accessories, supply chain issues/lead times, and integration/production schedules are requested to be provided by each interested company. Alternate solutions are encouraged. Note: If requested capabilities are not expected until a specific future date, please suggest a recommended roadmap to those capability requirements. In addition, rough order magnitude cost information (non-recurring and recurring) is requested.

The following are specific areas of interest to the Government:

a. Alternative approaches for “weather tight” equipment enclosures/packaging (or to weatherproof existing kits) that allow equipment to be operational while mounted on vehicles such as Joint Light Tactical Vehicles, Infantry Squad Vehicles, MRZRs, marine vehicles, commercial trucks and SUVs, Special Operations Craft–Riverine (SOC-R), Amphibious Combat Vehicle (ACV) Family of Vehicles (FOV), including personnel carrier (ACV-P) and command and control (ACV-C) variants, etc., and allow for rapid installation/de-installation of the equipment.

b. Alternative approaches for mounting/bracketing systems that minimize vehicle-specific mounting/bracketry and provide for shock/vibration protection while OTM in vehicles, during transition to ATH operations, and during equipment transport.

c. Options for mobile adhoc (mesh) network connectivity.

d. Alternative approaches for Radio over IP (ROIP)/intercom capability inside vehicles and between vehicles.

e. Alternative approaches for antenna mounting on various vehicles with potentially non-standard mounting provisions.

f. Potential approaches and solutions for antenna auto tracking, allowing effective use of directional antennas and compatible with Single Input, Single Output (SISO) and

Multiple Input, Multiple Output (MIMO) networks.

g. Alternatives for integrating multiple types of uninterruptible power supplies in case of prime power (vehicle or shore power) failure.

The TACP-M Program Office is also requesting information on company capabilities

(including digital engineering and management capabilities), as well as feedback, questions, and any other information for the MCS-U program.

The MCS-U Requirements Document is available upon request. A non-disclosure agreement

(NDA) will be required to be signed to obtain the Requirements Document, which will be sent via DoD SAFE upon successful execution of the NDA.

6.0 Responses

Interested parties are requested to respond to this RFI with a Microsoft Word compatible white paper of their own format.

White papers are due no later than 11 December 2026, 3:00pm ET. Responses are limited to

10 pages and are to be submitted via e-mail only to Mr. Ryan Gresse, Contract Specialist, at ryan.gresse@us.af.mil and to Mr. Edwin Hernandez Mendez, Contracting Officer, at edwin.hernandez_mendez.2@us.af.mil. Each email transmittal cannot exceed 10MB. All

Controlled Unclassified Information (CUI) must be submitted via DoD SAFE. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the

Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned.

Government support contractors may be involved in the review of responses. All Government support contractors have signed NDAs, which are on file with the cognizant Government contracting office. The primary companies that will be providing technical and management support are Odyssey Systems Consulting Group, Ltd., and its subcontractors under the

Engineering, Professional, and Administrative Support Services contract.

Section 1 of the white paper shall provide administrative information, and shall include the following as a minimum:

(a) Company name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and name, e-mail, and phone of designated point of contact.

(b) The facility security clearance of the company.

7.0 Industry Discussions

TACP-M Program Office representatives may or may not choose to meet with potential offerors. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, including any risks. An industry day may be conducted to allow additional Government and industry input.

8.0 Questions

Questions regarding this announcement shall be submitted in writing by e-mail to Mr. Ryan

Gresse, Contract Specialist, at ryan.gresse@us.af.mil and to Mr. Edwin Hernandez Mendez, Contracting Officer, at edwin.hernandez_mendez.2@us.af.mil. Verbal questions will NOT be accepted. Questions and answers that are pertinent to all potential offerors will be provided via email from the contracting officer. Accordingly, questions shall NOT contain proprietary or mailto:edwin.hernandez_mendez.2@us.af.mil mailto:edwin.hernandez_mendez.2@us.af.mil classified information. The Government does not guarantee that questions received after 11

December 2026 at 3:00pm ET will be answered.

9.0 Summary

THIS IS A REQUEST FOR INFORMATION ONLY to identify sources and equipment that can support the MCS-U program. The information provided in the RFI is subject to change and is not binding on the Government. The Air Force 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 cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.

ATTACHMENT (available upon request):

MCS-U Requirements Document (CUI)

EDWIN O. HERNANDEZ MENDEZ, NH-03, DAF

Contracting Officer, AFLCMC/WISN