SAM #N00019-25-RFPREQ-WPM201-0360

RFI for Network Enabled Weapons Trainer (NEWT) for Naval Air Systems Command

The Naval Air Systems Command (NAVAIR), part of the Department of the Navy, is seeking industry input for the development and manufacture of a Network Enabled Weapons Trainer (NEWT) for Navy aircraft. - Government Buyer: - Department of the Navy - Naval Air Systems Command (NAVAIR) - OEMs and Vendors: - No specific OEMs or vendors are named; open to industry sources - Products/Services Requested: - Network Enabled Weapons Trainer (NEWT) - Must emulate all Air launched DOW Network Enabled Weapons (NEW) used by Navy aircraft - Airworthy and suitable for Aircraft Carrier operations - Captive carriage trainer, agnostic to weapon type - Compatible with fixed wing platforms employing Network-Enabled Weapons - Unique or Notable Requirements: - Exportable to FVEY (Five Eyes) partners - Minimum power-on times - Compatibility with existing support and test equipment - Software modularity and compliance with AT/Cyber standards - Carrier environment design, including integrated antennas - Software-defined radio covering 0-6 GHz - Internal processing power with future growth capacity - Reusable trainer with rapid post-flight data extraction - Minimized impact on platform code - Respondents are asked to submit white papers detailing their approach or existing capability, including company information and relevant experience. - No specific products, part numbers, or quantities are specified; this is a sources sought for potential solutions.

Description

DISCLAIMER:

This is a request for information (RFI)/sources sought for white papers only. There is no solicitation at this time.

The Naval Air Systems Command (NAVAIR) is conducting market research to identify potential industry sources and commercial-off-the-shelf (COTS) capabilities.

The PMX-201 Precision Strike Weapons, Effects Deployment Office (FXDO), Network Enabled Weapons Trainer (NEWT) Program requests interested parties submit a white paper detailing their proposed approach or existing capability to develop, manufacture, and maintain an airworthy, aircraft carrier suitable store[JN1] [CM2] that will emulate all air-launched DOW Network Enabled Weapons (NEW).

SUBMISSION INSTRUCTIONS:

Format: White papers must be submitted in PDF/Microsoft Word format. Page Limit: Responses shall not exceed 8 pages, excluding the cover page. Font: Times New Roman or Arial, 11-point font or larger. Deadline: All submissions must be received no later than (NLT) 09 November 2026, 5 pm Eastern Standard Time. Delivery: Submit via email to breanne.n.jilcott.civ@us.navy.mil with the subject line: Response to N00019-25-RFPREQ-WPM201-0360 – Company Name

The Government acknowledges that white papers may contain proprietary or trade secret information. All proprietary information contained in the response must be clearly marked.

The Government will safeguard properly marked proprietary information from unauthorized disclosure in accordance with applicable laws and regulations.

Please do not submit classified information or pricing information in response to this RFI.

Please provide the following information:

Company Name and Address Cage Code and UEI Number Company business size by NAICS code Small Business Type(s), if applicable Point of Contact for questions and/or clarifications (Name, Title, Phone, Email) Telephone Number and email address Web Page URL (if applicable) Teaming Partners (if applicable) Information regarding the viability to receive and process classified information with appropriate contact information Provide any recommendations and/or concerns. Location(s) of work to be performed.

Capabilities Statement:

Provide a detailed description of your company's experience, capabilities, and planned approach to develop and manufacture the following:

Provide an agnostic Captive Carriage Network Enabled Weapons Trainer (NEWT) to emulate all Network Enabled Weapons (NEWs) employed by aircraft in the DoN inventory. This trainer will have the following:

Supportable Platforms The NEWT shall be captive carried from DoN fixed wing platforms that employ Network-Enabled Weapons. The NEWT shall meet exportability requirements to FVEY.

Reliability The NEWT shall have a minimum power on time of 4 hrs with a 30 min cool off period for Strike Fighter training, during which the NEWT can be cold soaked at altitude. Maritime Patrol and Reconnaissance Force (MPRF) is 12-hour power-on operations. [JN5] [CM6] This includes power on deck (BIT, Mission Planning download, crypto verification) and power while airborne. BLOS communications are needed pre-employment, employment and post simulated launch of long-range NEWs.

Supportability The NEWT shall be capable of off-aircraft BIT/ reprogramming using existing CMBRE or other follow-on systems. The NEWT shall be compatible with existing support equipment and test equipment (GSE). Ground Crew shall be able to change the NEWT to the weapon it is emulating without downloading the NEWT from the aircraft.[JN7] [CM8] The NEWT shall focus on software modularity instead of hardware interchangeability. The NEWT shall not require liquids or gases that need to be refilled.

Program Protection The NEWT shall minimize or eliminate weapons CPI content. The NEWT shall meet current AT / Cyber standards for new hardware (if not already flight proven hardware).

Environmental/Structural The NEWT shall be designed for the carrier environment. The NEWT shall be designed for a Vmax of 1.2 IMN The NEWT shall be reusable with a maximum down time of 45 minutes between flights. The NEWT life shall maximize the number of catapults and arrestments. Once the NEWT has reached its service life, maintenance actions to return to flying status are limited to the Organizational (O) and Intermediate (I) level maintenance.[JN9] [CM10]

Connectivity The NEWT shall utilize all NEW waveforms The NEWT shall be capable of operating between 0-6 GHz including, but not limited to WF L, WF X, WF S, WF Y, and Link-16. The NEWT radio shall be software defined to allow for future waveform growth

Hardware The NEWT shall minimize testing requirements to be cleared on the aircraft platform. The NEWT shall be inert with no energetic components The NEWT shall have a clear view of the sky for its own antennas to enter required networks; the NEWT shall not depend on the aircraft platform to communicate with external architecture. The NEWT’s antennas shall be integrated into its Outer Mold Line (OML) and not require deployment of any doors or other mechanisms. The NEWT shall use primary power from the launch platform power source.

System Performance The NEWT shall be integrated with the Navy's broader network-centric warfare systems, enabling coordinated operations and enhanced situational awareness. The NEWT shall notify the platform of the receipt and acceptance of Inflight Target Updates (IFTUs).[JN11] [CM12] The NEWT shall exercise the network and weapon mission planning processes to include Cryptographic Key Material handling. The NEWT shall not utilize the onboard processing capacity of the host platform. The NEWT shall be capable of all required processing capabilities with 50% growth available. All processing power will be handled internally to the NEWT. This does not include any processing power the platform will need for cockpit display of IFTU[JN13] [CM14] reception and fly-out. The NEWT shall use the aircraft/weapon interface for the weapon it is emulating (UAI, common flex, 1760, etc) The NEWT shall utilize current Fleet released mission planning system (JMPS/CMPC) as the respective NEW weapon that NEWT is emulating. An emphasis should be placed on minimizing unique planning that deviates from actual weapon mission planning. The NEWT shall be designed for net entry while on the ground, and airborne if NEWT is secured for takeoff. The NEWT shall ingest live, virtual, and constructive tracks from both the continuous learning environment and real-world networks. The NEWT shall emulate the respective dynamic LAR of the weapon that NEWT is emulating. The NEWT shall be designed with future proofing in mind. Future upgrades could involve but not limited to: Open Architecture. Inject new waveforms. Computing power, firmware memory and processor reserve of 50% or greater for future growth. The NEWT shall record data for post flight debrief/analysis including but not limited to: Supply power to the data recorder upon NEWT startup. Enable rapid post flight data extraction via removable storage or electronic extraction to ensure seamless integration with JMPS / CMPC processing workflows. Maintain open physical and logical access to the memory interface (removable / electronic) during host aircraft operations with NEWT loaded. Record BLOS IFTUs received and processed Record release conditions at simulated launch. The NEWT shall minimize platform MC code impact.

This RFI is issued solely for information and planning purposes—it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request does not commit the U.S. Government to contract for any supply or service whatsoever. Further, the Government 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 any future RFP, if any is issued.

Responses to this Request for White Paper are not quotes on which PMX-201 Precision Strike Weapons can issue any contract. This Request for White Paper is issued for information and planning purposes only and does not in itself constitute a proposal. The Government does not intend to award a contract based only on responses to Request for White Paper.

All information received in response to this Request for White Paper marked

View original listing