F-EW RFI Final.docx

Marine Air Defense Integrated System (MADIS) and Light-MADIS (L-MADIS) Electronic Warfare (EW) system

NOTE: THIS IS NOT A SOLICITATION FOR PROPOSALS. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is for planning and informational purposes only and shall NOT be considered as a Request for Proposal (RFP) or as an obligation on the part of the Government to acquire any products or services. The Government will NOT be responsible for any costs incurred in responding to this RFI or furnishing the requested information. No entitlement to payment of direct or indirect costs or charges by the Government will arise because of a contractor's submission of responses to this RFI or the Government's use of such information. The Government reserves the right to reject, in whole or in part, any contractor's input resulting from this RFI. No contract will be awarded from this announcement. Pursuant to Federal Acquisition Regulations (FAR) 15.101(c), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.

1.0 Introduction:

The United States Marine Corps (USMC), Program Manager Ground Based Air Defense (PM GBAD) has a requirement to integrate an Electronic Warfare (EW) system onto the Marine Air Defense Integrated System (MADIS) Family of Systems (FoS) to meet Counter Unmanned Aircraft Systems (CUAS) non-kinetic defeat requirements. This RFI is focused on existing commercially available EW systems that are Technology Readiness Level (TRL) 8/9.

2.0 Purpose:

The purpose of this RFI is to solicit potential solutions from industry on advanced electronic warfare systems to be integrated on MADIS and L-MADIS vehicles. The desired solution will serve as the non-kinetic defeat capability for the MADIS FoS in support of the USMC air defense community. Vendors are requested to submit responses stating their capabilities that meet the requirements listed. Mature capabilities that exhibit the potential to meet these requirements MAY, at the Government’s discretion, be invited to a live demonstration in February 2027 at Yuma Proving Ground, Yuma, AZ for a demonstration This information will help identify potential solutions for the future EW system.

The requirement may include the following: training, integration, testing, production, and maintenance support. This RFI constitutes market research in accordance with FAR part 10 and is not a RFP. The USMC is issuing this RFI, in support of PM GBAD, to determine what vendors have the capability to meet the requirements listed in this document.

3.0 Program Background:

The MADIS is a FoS consisting of specific, integrated capabilities required to carry out active air defense against UAS and Fixed Wing (FW)/Rotary Wing (RW) threats. The mission set requires an integrated and in-depth air defense umbrella based upon the rapid kill chain sequence of “detect”, “track”, “identify”, and “defeat”. This doctrinal task sequence provides the foundation for the concept of operation enabling the MADIS FoS to use organic and/or non-organic data to acquire, engage, and negate, or destroy aerial threats. The MADIS FoS achieves success by employing a dispersed, integrated, and composite defense comprised of layers of Short-Range Air Defense (SHORAD) systems to defend designated stationary military assets and offensive formations while considering standoff, lethality, range, and effectiveness.

The MADIS FoS utilizes various kinetic and non-kinetic techniques and technologies to perform the defeat function required. The EW system is a critical portion of this capability allowing Marines to perform non-kinetic sensing and attack through Radio Frequency/Global Navigation Satellite System (RF/GNSS) jamming and spoofing.

3.1 Requirements:

To best support the MADIS FoS requirements, PM GBAD has a requirement to integrate and deliver an EW system with the capability to defeat threats under all weather conditions to include on the move and at the halt.

EW system: A TRL 8/9 EW solution capable of defeating Group 1-3 UAS, including FW and RW, day and night. The future EW system is not limited to RF and may be comprised of any EW solution. The contractor shall describe its EW solution with regard to the following:

3.1.1 Design Considerations

1. Provide the total system weight, with a breakdown by major components.

2. Specify the average and peak electrical power consumption during operation. If the system supports simultaneous functions (e.g., sensing and electronic attack), detail the power requirements for all operational modes.

3. Provide the physical dimensions of the complete system and its major subsystems.

4. Provide the system's cooling requirements, including any necessary external equipment.

5. Describe all antenna requirements, including size, weight, and optimal placement considerations for integration onto MADIS Family of Systems (FoS) vehicles.

6. Describe the system's use of open standards and design features that facilitate straightforward vehicle integration and mounting.

7. Describe the system's hardware and software adaptability to accommodate Marine Corps-specific modifications.

8. Describe the user interface, focusing on intuitive operation, and the system's capability to disseminate data across a tactical network.

3.1.2 Interoperability Considerations

1. Describe the system's interoperability with existing Marine Corps and Joint Force Command and Control (C2) and fire control architectures. Identify any Department of War C2 systems with which the system is currently integrated.

2. Identify all industry (e.g., SAE, IEEE) and military standards the system uses for interfacing with external systems.

3. Describe the system’s ability to deconflict its output with co-located systems, detailing features such as frequency notching, smart filtering, or autonomous deconfliction.

3.1.3 Performance Considerations

1. Detail any operational limitations in azimuth and elevation.

2. Describe the system's use of cognitive EW and machine learning to autonomously detect, track, identify and defeat threats, thereby reducing operator workload.

3. Describe the system's performance against moving targets while the host vehicle is both static and on the move.

4. Provide the system’s integration history on mobile platforms.

5. Detail the available EW techniques (e.g., RF/GNSS jamming, denial, spoofing).

6. Specify the number of threats the system can simultaneously track and/or defeat. Describe the system's ability to maintain tracking threats while engaging.

7. Describe the capability to download post-mission data for intelligence analysis and threat library refinement.

8. Detail any additional functions the system can perform concurrent with its primary EW mission.

9. Describe the system's ability to network with other similar EW systems for coordinated operations.

10. Describe the system's ability to keep pace with evolving threats via integrating new SW, hardware and additional computing power availability.

11. Describe the system's ability to operate in a contested/limited communications environment.

3.1.4 Procurement Considerations

1. Provide an estimated per-system procurement cost.

2. State the current quantity of systems available on hand.

3. Detail the system’s lead time and production capacity (units per month).

4. Identify any alternative or interim solutions that could accelerate the delivery of this capability.

3.1.5 Environmental / Safety Considerations

1. Describe measures taken to protect the system from solar radiation damage.

2. Describe the system's ability to operate effectively in all weather conditions, including day/night operations, rain, snow, high humidity, and blowing sand/dust.

3. Identify which Laboratory Test Methods in MIL-STD-810H (with change notice 1) the component meets, or meets the requirements and associated limits as applicable in an earlier MIL-STD-810 version.

4. Identify whether the component meets MIL-STD-461G or meets the EMI requirements and associated limits, as applicable in an earlier MIL-STD-461 version.

5. Specify if the system meets MIL-STD-464C for electromagnetic environmental effects (E3), including any completed testing for Hazards of Electromagnetic Radiation to Personnel, Fuels, and Ordnance (HERP, HERF, HERO).

6. For all EMI/EMC testing, provide the Name, Date, Report Number, and Testing Agency.

7. List any other MIL-STD certifications the system has achieved.

3.1.6 Logistics Considerations

1. Provide established Reliability, Availability, and Maintainability (RAM) data and recommend preventative maintenance schedules.

2. Describe design features that simplify maintenance procedures.

3. Detail the system’s diagnostic and prognostic capabilities, including Built-In-Test (BIT).

4. List any special tools or equipment required for on-site maintenance.

5. Specify the required manpower, including operator and maintainer quantity and skillsets.

6. Describe the available training packages and technical publications.

7. List any parts that have assigned or require a National Stock Number (NSN).

8. Describe the availability of spare parts kits for high-wear or high-failure rate items.

9. Identify any batteries internal to the system.

10. Detail all warranty periods, broken down by component or part.

11. Identify any components containing materials listed on the NAS411-1 Hazardous Materials Target List (HMTL).

12. Provide a draft or existing Sustainment Support Plan.

3.1.7 Sustainment Considerations

1. Provide the estimated lifecycle timeline for the EW system and its major subcomponents, including any plans to discontinue production or support.

2. Provide all available Diminishing Manufacturing Sources and Material Shortages (DMSMS) data for the system and its components.

4.0 Requested Information:

Respondents who are interested are requested to provide the information that identifies their capability to provide the support described herein. The Government MAY invite interested vendors, at the Government’s discretion, to demonstrate their capability in February 2027 at Yuma Proving Ground, Yuma, AZ for a demonstration against live targets. Any interested vendors invited to participate in the demonstration shall provide system information to support spectrum clearance authorization. The Government will request this information via email to the Point of Contact (POC) listed in the interested vendors RFI submission.

5.0 Responses:

Vendors possessing the requisite skills, resources, and capabilities necessary to perform the stated requirements are invited to respond to this RFI via an electronic technical submission of not more than 20 pages as well as an executive summary not more than 10 pages in length when printed on 8 ½ x 11 in paper using 12-point font and single spaced. All responses must include the following information:

(1) Name and address of applicant/company (Corporate/Principal Office).

(2) Name, telephone number, fax number, and e-mail address of point of Contact.

(3) General Service Administration (GSA) contract number (if applicable).

(4) CAGE Code and DUNS Number.

(5) Business Size (under NAICS 334511, Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing).

(7) Recommendations to improve the Marine Corps’ approach to this requirement.

(8) State whether the Company has a Secret Facility Clearance and Secret Safeguarding.

(9) State the potential small business subcontracting opportunities in regards to type of work for this requirement provided for by small businesses, the type of small business (small business (SB), veteran owned small business (VOSB), service-disabled veteran-owned small business (SDVOSB), historically underutilized business zone (HUBZone) small business, small disadvantaged business (SDB), and women owned small business (WOSB) concerns) involved, the significance of the effort to the requirement and the percentage of total potential effort being able to be provided to those types of small businesses.

(10) Identify whether your product is a commercial item in accordance with the definitions in FAR 2.101. In addition, your response must address DFARS PGI 212.102(a).

(11) Data Right Assertions: The government anticipates that the source for the development of all the technical data, training material and software deliverables, including all components of same, would be government funding under a contract effort, with the result that the government will receive unlimited rights in all such deliverables. If this assumption is incorrect, please identify every deliverable or every component of every deliverable, that will come with a restriction; for this request for information, please follow the procedure and format for Assertions of Restrictions in DFARS 252.227-7017, which the government will consider to be a notional Assertion. Indicate in this notional Assertion any uncertain entries, and the basis of that uncertainty, that might change in a formal Assertion if a contract were awarded to the respondent. For any training material that is pre-existing and would come from your company, or from a third party, or from the government, identify that material and confirm that it can be delivered with a copyright release that will allow the government to make all copies or derivative work that it might find necessary. For any software deliverable or deliverable component, identify any portions of software come from existing commercial software or from open-source software, and list the respective software license(s) that pertains.

Please be advised that any proprietary information must be marked as such on a page-by-page and paragraph by paragraph basis. The Government will not assume that any of the information provided by a respondent is proprietary unless it is conspicuously marked on this basis. Moreover, the Government does not assume any duty to contact a respondent and inquire whether any unmarked information submitted in response to this RFI is proprietary.

The Government is only seeking sources/information for market research to determine the availability of commercial capabilities in the described areas. Acknowledgement of receipt will not be made. Availability of any formal solicitation will be announced separately. Submittals will not be returned to the sender. Respondents will not be notified of the results of the evaluation. It is the contractor’s responsibility to check SAM.gov (https://sam.gov/) to get additional data.

This RFI does NOT constitute an RFP nor a promise to issue an RFP in the future. This RFI does not commit the United States Government (USG) to contract for any supply or service. Further, the USG is not seeking proposals at this time and will not accept unsolicited proposals. Contractors are advised the USG will not pay for any information or administrative costs incurred in response to this RFI.

The information provided in the RFI is subject to change and is not binding on the USG. The USG has not made a commitment to procure any of the items discussed and the release of this RFI should not be construed as a commitment or as authorization to incur cost for which reimbursement would be required or sought.

Responses shall be submitted via e-mail to justin.hempe@usmc.mil and stasia.baker@usmc.mil no later than 1400 Eastern Time on 3 August 2026. Telephone replies will not be accepted. Responses can be submitted via DoD Secure Access File Exchange (SAFE). The interested vendor shall submit a DoD SAFE link request to justin.hempe@usmc.mil and stasia.baker@usmc.mil no later than 1200 Eastern Time on 30 July 2026.

6.0 Questions

Questions or comments regarding this notice may be addressed to justin.hempe@usmc.mil and stasia.baker@usmc.mil by email only. No questions will be accepted after 16 July 2026 at 1400 Eastern Time. The Government intends to respond to as many questions as practicable and will respond to questions via an amendment to this RFI posted to SAM.gov so that all interested parties will benefit from the same information. All interested offeror(s) are encouraged to register on the SAM.gov website to receive email notifications when information related to this acquisition is updated, or documents related to this acquisition are issued and available for download. The Government requests that all interested parties ensure that they are listed on the "Interested Vendors List" on SAM.gov. As a rule, the Government will not send notifications directly to interested offeror(s), and it is recommended that the interested offeror(s) periodically check this website for updates.