Air Force Special Warfare Seeks One Mobile Comms Kit for Every Vehicle

Air Force Special Warfare wants a single mobile communications and command-and-control system that fits any vehicle, and it wants industry's ideas by Dec. 11. The request for information, published Thursday on sam.gov, feeds the Mobile Communication System-Universal program, or MCS-U. The vision: a mobile C2 node that passes "critical voice, data, and video communications" between Tactical Air Control Party operators, whether driving or parked.

The motivation is refreshingly plain. "MCS-U is an evolution of mobile communications and command and control system capabilities in AFSPECWAR vehicles," the RFI states. "Previous MCS capabilities were designed and customized for specific vehicles." bespoke builds, one per platform, are expensive habits. The new system would need to mix and match between Air Force Special Warfare vehicles "as much as possible," the document adds.

MCS-U would also plug into the Advanced Battle Management System, which builds the DAF Battle Network — the Air Force's contribution to the Pentagon's Joint All-Domain Command and Control effort. TACP operators, for context, call in airstrikes from the front lines while typically embedded with Army soldiers and Marines, according to an Air Force webpage.

What does the RFI actually ask for?

The TACP-Modernization program office wants feedback on available capabilities and components for MCS-U. That includes weatherproof kits that keep systems running while integrated with a remarkably varied fleet:

• Joint Light Tactical Vehicles
• Infantry Squad Vehicles
• MRZRs
• Special Operations Craft-Riverine (SOC-R)
• Amphibious Combat Vehicle (ACV) Family of Vehicles
• Marine Vehicles
• Commercial trucks and SUVs

When a riverine craft and a showroom SUV share one requirement, the word "universal" is doing honest work. The RFI also asks for input on mounting systems to vehicles agnostically, mesh network connectivity options, antenna auto-tracking approaches and power supply integration alternatives.

What happens next — and what might not?

A draft system requirements document and a draft request for proposals are tentatively slated to publish in fiscal 2027. The RFI, however, is candid about the program's fragility. "This program is pending formal acquisition approval, as well as funding approval, which may impact the schedule above," the document states.

The Air Force has not settled on a contracting strategy, and the RFI says that approach will likely take shape based on industry replies. Requirements themselves have yet to be fleshed out and will appear in a request for proposals, "if issued," according to the notice. That two-letter hedge carries the weight of the whole document.

What does this change for vendors?

For defense comms suppliers, the opening is real but conditional. Dec. 11 is the deadline to shape a program that has no approved funding, no confirmed acquisition path and no final requirements. That is either a risk or a first-mover advantage, depending on your tolerance for Pentagon scheduling.

The technical brief is nonetheless clear: build one C2 node, weatherproof it, mount it on anything from a commercial SUV to a riverine boat, keep voice, data and video flowing on the move, and connect it to the ABMS backbone. Industry answers due in under a month; everything else due sometime after fiscal 2027, if the money arrives.