N00019-27-RFI-PMA208ROCO (Updated 7-13).pdf

Request for Information (RFI)

N00019-27-RFI-PMA208ROCO

Title: Robust Communications (RoCo) for Sub-Sonic Targets

Issued By: Naval Air Systems Command (NAVAIR), on behalf of Program Management OƯice, Aerial Targets (PMA-208)

Date of Issuance: 11 June 2026

Response Due Date: 20 July 2026, 5:00 PM ET

1.0 GENERAL INFORMATION & DISCLAIMER

THIS REQUEST FOR INFORMATION (RFI) IS ISSUED SOLELY FOR INFORMATION AND

PLANNING PURPOSES AND DOES NOT CONSTITUTE A SOLICITATION. THE GOVERNMENT

MAY USE THE INFORMATION RECEIVED TO INFORM A POTENTIAL PROTOTYPE PROJECT

UNDER OTHER TRANSACTION AUTHORITY (OTA), PURSUANT TO 10 U.S.C. § 4022. THIS

ANNOUNCEMENT DOES NOT CONSTITUTE A COMMITMENT BY THE GOVERNMENT. ALL

INFORMATION SUBMITTED IN RESPONSE TO THIS RFI IS VOLUNTARY AND THE

GOVERNMENT WILL NOT COMPENSATE ANY RESPONDENT FOR ANY COST INCURRED IN

DEVELOPMENT OF INFORMATION PROVIDED TO THE GOVERNMENT. THIS IS NOT A

REQUEST FOR PROPOSAL; YET IS A MARKET RESEARCH TOOL TO DETERMINE POTENTIAL

FIRMS CAPABLE OF PROVIDING THE SUPPLIES DESCRIBED HEREIN PRIOR TO AN

ISSUANCE OF A REQUEST FOR PROPOSAL. THE GOVERNMENT IS NOT OBLIGATED TO PAY

FOR ANY INFORMATION RECEIVED FROM POTENTIAL SOURCES AS A RESULT OF THIS RFI.

THIS DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE CONSTRUED AS A

COMMITMENT BY THE GOVERNMENT OF ANY KIND. RESPONSES IN ANY FORM ARE NOT

OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT OR

NON-FAR BASED AGREEMENT (E.G. OTHER TRANSACTION) AS A RESULT OF THIS

ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES

TO THIS ANNOUNCEMENT. ANY INFORMATION SUBMITTED BY RESPONDENTS TO THIS

TECHNICAL DESCRIPTION IS STRICTLY VOLUNTARY. FAILURE TO SUBMIT A RESPONSE

WILL NOT PREVENT A COMPANY FROM PARTICIPATION IN ANY FUTURE COMPETITION

RELATED TO PMA208’S ROBUST COMMUNICATIONS FOR SUB-SONIC TARGETS.

INFORMATION PROVIDED SHOULD BE UNCLASSIFIED. ANY INFORMATION SUBMITTED

MAY BE REVIEWED AND USED ACROSS THE GOVERNMENT (INCLUDING WITH

CONTRACTOR SUPPORT PERSONNEL).

2.0 BACKGROUND & CAPABILITY REQUIREMENT

The Naval Air Systems Command (NAVAIR), on behalf of the PMA-208 Aerial Targets Program OƯice, is issuing this Request for Information (RFI) to seek industry's capability to provide a robust, high-bandwidth, and long-range communications solution for its Subsonic Aerial Targets (SSAT) fleet.

PMA-208 provides threat-representative aerial targets for test, evaluation, and training.

Current SSAT communication architectures are primarily based on Navy Command Data Link (NCDL) and other Line-of-Sight (LOS) radio systems. These systems have limitations that hinder the ability to simulate complex, long-range threats and collect comprehensive data.

For a detailed breakdown of the Government’s current technical assessment, capability gaps, system constraints, and performance objectives, respondents must thoroughly review Attachment 1: RoCo Technical Background and Capability Gaps.

Key identified gaps in the current system include:

Limited Range/Blue Water Capability: The current system has a nominal maximum range of approximately 200 nautical miles (nmi), which is insuƯicient for blue-water presentations.

InsuƯicient Data Rate: The current maximum bitrate restricts telemetry data, prevents the transmission of high-resolution video or payload data, and limits post-flight forensic analysis.

Low Signal Resiliency: The existing architecture is susceptible to signal loss due to airframe masking and single points of failure.

Restricted Datalink Connectivity: The current datalink format is not compatible with operational platforms (e.g., Link-16), precluding direct data exchange and collaborative control.

The purpose of this RFI is to conduct market research in order to gain understanding of current technologies and potential solutions that can address critical capability gaps in the existing Command and Control (C2) system. The Government is seeking feedback regarding industry's technical capabilities, innovative approaches, experience in integrating complex systems, potential costs and schedule to deliver solutions.

NAVAIR is considering awarding one or more Other Transaction Agreements (OTA), pursuant to 10 U.S.C. 4022 “Authority of the Department of Defense to carry out certain prototype projects,” for Robust Communications (RoCo) for Sub-Sonic Targets.

The Government reserves the right to pursue production of a successful prototype(s).

3.0 REQUIRED CAPABILITIES

The scope of the RoCo project is the C2 transmitter/receiver layer. The desired solution must interface with the existing System for Naval Targets Control (SNTC) (see Figure 1:

Current System) and be integrated with, at a minimum, the BQM-177 and BQM-34 target aircraft. For technical background and capability gap analysis see Attachment 1. For further definitions of key components see Attachment 2 RoCo Definitions.

Figure 1: Current System

Note 1: All distances listed above were modeled assuming a minimum 12 dB link margin and a minimum response rate of 97.5%.

Note 2: Participants include targets, relays, and shipboard transponders.

Note 3: Due to local frequency management at each operating site, most sites are only allowed to radiate on 8-10 frequencies.

Operational Distances o Ground Radio Frequency Unit (GRFU) to Target Transponder direct: 200 nmi 1 o GRFU to Relay: 200 nmi 1 o Relay to Target Transponder 130 nmi 1 o Max number of aerial targets: 6 o Max number of participants: 13 2 o Number of channels: 24 3 o Bitrate: 230.4 kbps Data Recording

The Ground Control Station (GCS) records all messages transmitted and all messages received in the mission data file. Likewise, the airborne relay and transponder each have an SD card installed which records all received messages and all transmitted messages. Therefore, if a target is recovered, the GCS mission data file can be compared to the transponder SD card.

Respondents should provide solutions that address the capability gaps outlined above and within Attachment 1, with a do no harm mindset, to maintain the operational capability of the system. The Government is interested in solutions that meet the following thresholds/objectives while also fitting within the technical constraints:

Element Threshold Objective Constraints Range 200 nmi Global Operations from CONUS N/A

Data Rate 1.0 Mbps 30 Mbps

Transponder- FCS update rate at least 10 Hz

Transponder downlink update rate at least 10 Hz

Peak signal latency less than 1.0 sec

Datalink Connectivity One-way push TSPI as J-Series messages

Two-way interaction with Link-16 network

System does not raise the security classification of the SNTC network

Table 1: Thresholds and Objectives

All airborne hardware must adhere to the Size, Weight, and Power (SWaP) constraints of the aerial target platforms, see Table 2, though trade-space is available to optimize these parameters.

SwaP Metrics Size: 3.5”H x 6.5”W x 7”D Weight: 7.8 lbs Power: 28 VDC, not to exceed 2 A Range: 200 nmi (nominal)

Table 2: SWaP Metrics

4.0 INFORMATION REQUESTED FROM INDUSTRY

Interested parties may submit a Capability Statement identifying their interest and capability to respond to the requirement or submit proposals. A determination by the Government not to compete this proposed contract action based upon responses to this notice is solely within the discretion of the Government. Capability Statements received will be considered for the purpose of determining whether to conduct a competitive procurement. Capability Statements submitted should be pertinent and specific in the technical/management/business area under consideration. Interested parties are requested to provide a capabilities statement (no more than 20 pages) addressing the following:

4.1 Technical Approach:

Describe your proposed technical solution to address the four key capability gaps (Range, Data Rate, Resiliency, Connectivity). Refer to Attachment 1 and technical attributes described above.

Detail your solution's architecture and how it would integrate with the existing SNTC network and target aircraft.

Describe any potential impacts on frequency management, cybersecurity, and range safety policies.

Explain the maturity and Technological Readiness Level (TRL) of your solution.

Please see Table 3 below for TRL definitions.

Level Definition TRL 9 Actual system proven through successful mission operation.

TRL 8 Actual system completed and qualified through test and demonstration.

TRL 7 System prototype demonstration in an operational environment.

TRL 6 System/subsystem model or prototype demonstration in a relevant environment.

TRL 5 Component and/or breadboard validation in a relevant environment.

TRL 4 Component and/or breadboard validation in a laboratory environment.

TRL 3 Analytical and experimental critical function and/or characteristic proof of concept.

TRL 2 Technology concept and/or application formulated.

TRL 1 Basic principles observed and reported.

Table 3: Technology Readiness Level (TRL) Definitions Table

4.2 Cost and Schedule:

Provide a rough order of magnitude (ROM) cost estimate for the development, integration, and procurement of your provided solution. Please break down costs for non-recurring engineering and per-unit hardware, if possible.

Provide an estimated schedule for the development, testing, and fielding of the solution, from contract award to initial operational capability. Include key milestones.

4.3 OEM Collaboration:

The RoCo solution will require integration with aerial target systems provided by Original Equipment Manufacturers (OEMs). Respondents must describe their plan or ability to establish a working arrangement with the incumbent OEMs for the BQM- 177 (Kratos), BQM-34 (Northrop Grumman), and SNTC (Micro Systems, Inc.).

4.4 Corporate Experience:

Provide a brief overview of your company's experience in developing and integrating similar C2 or datalink systems for unmanned or airborne platforms.

5.0 DISCLAIMER

Any information received in response to this request will be properly protected and handled accordingly; In order to complete its review, NAVAIR must be able to share information within the Government and with contractor support staƯ (CSS).

6.0 RESPONSE SUBMISSION

6.1 All responses shall be submitted via email in Microsoft Word or Adobe PDF format to the points of contact below no later than 5:00 PM ET on 20 July 2026. Interested parties are advised against submitting Capability Statements that merely mimic information in this RFI, provides brochure-like information, or provides general information. Responses to this

RFI are not to exceed 20 pages in length on 8.5X11 inch paper with one-inch margins and font no smaller than 10 points Times New Roman.

Primary: Joseph Perriello, Contract Specialist, joseph.c.perriello.civ@us.navy.mil

Secondary: Raymond Cannon, Procuring Contracting OƯicer / Agreements OƯicer, raymond.c.cannon2.civ@us.navy.mil

Secondary: Torie Benefield, Contract Specialist, torie.d.benefield.civ@us.navy.mil

6.2 Questions regarding this RFI shall be submitted via email to the primary point and secondary point of contact. The Government is not obligated to respond to questions submitted by industry as part of this RFI. The Government is not accepting phone calls or meetings regarding this RFI prior to deadline for submissions. However, after receipt of RFI submission, the Government may elect to arrange a meeting/phone call with vendors to conduct further market research and seek clarifications on its response.

Classified material SHALL NOT be submitted. All submissions shall include this RFI Reference Number, company name, company address, CAGE code, Unique Entity Identifier (UEI) number, and a point of contact information (including name, position, phone number, and email address) who is able to discuss the Capability Statement submitted.

All information submitted will be adequately safeguarded from unauthorized disclosure.

As previously noted, RFI responses will be reviewed by contractor support personnel. The Government will not accept responses marked with Distribution F per DoDI 5230.24.

Responses that fail to comply with the above instructions or present ideas not pertinent to subject, may not be reviewed. All information received in response to this Notice that is marked proprietary will be handled accordingly. Information submitted in response to this RFI is submitted at no cost to the Government and will not be returned. The Government is under no obligation to provide responses or comments to information received from interested parties.

The Government is considering utilizing the Naval Air Systems Consortium to potentially award one or more OTAs pursuant to 10 U.S.C. 4022 “Authority of the Department of Defense to carry out certain prototype projects”. This eƯort will be briefed by the Government at the NASC Membership Meeting on 25 June 2026. This forum is limited to the members of the NASC. For more information about membership as well as the Robust Communications briefing, please visit nascsolutions.org.

Note: If an interested person is a foreign concern or if a U.S. interested person has a team member or partner who is a foreign entity, both identification of this partnership to the

Government and adherence to all International TraƯic and Arms Regulations (ITAR) are required.