F-15EX Missile Warning System

The Department of the Air Force, Air Force Materiel Command (AFMC), Air Force Life Cycle Management Center (AFLCMC), Fighters & Advanced Aircraft Directorate (AFLCMC/WA), F?15 System Program Office (AFLCMC/WAQ), Wright-Patterson Air Force Base (WPAFB) is seeking sources for the procurement of an operationally qualified threat missile launch and approach warning system for rapid integration into the United States Air Force (USAF) F-15EX Eagle II fighter aircraft. INTRODUCTION: This is a SOURCES SOUGHT ANNOUNCEMENT to acquire a missile warning system (MWS) to be integrated into the F-15EX fleet. The system must alert the F-15EX aircrew to missile threats without unreasonably distracting the aircrew with false alarms. The MWS must use the six pre-existing sensor locations, data cables, power cables, and cooling. The MWS must be easily, safely, rapidly, and organically installable and removable in the field by USAF military aircraft maintenance personnel. In accordance with Revolutionary Federal Acquisition Regulation Overhaul (RFO) Part 10, Market Research, AFLCMC/WAQ is seeking information for potential sources for an integrated MWS solution for the F-15EX. This publication is intended to elicit responses from sources with knowledge, skills, data, equipment, access to appropriate facilities, and the capacity to meet the Air Force s requirements. The dollar value and period of performance (PoP) for the contract will be commensurate with the requirement. This contract effort is subject to RFO 52.232-18, Availability of Funds. 1.1 SOURCES SOUGHT INFORMATION 1.2 DISCLAIMER: THIS?SOURCES SOUGHT?IS FOR INFORMATIONAL PURPOSES ONLY.? THIS IS NOT A REQUEST FOR PROPOSAL (RFP), REQUEST FOR QUOTE (RFQ) OR AN INVITATION FOR BID (IFB).?IN ACCORDANCE WITH?RFO 15.101(c),?THIS NOTICE?DOES NOT CONSTITUTE SOLICITATION AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT. RESPONSES IN ANY FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT 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. THE GOVERNMENT MAY USE THE INFORMATION OBTAINED FROM RESPONSES TO THIS NOTICE IN DETERMINING ITS ACQUISITION APPROACH.? THE ISSUANCE OF THIS NOTICE DOES NOT RESTRICT THE GOVERNMENT ACQUISTION APPROACH.? 1.3 REQUIRED CAPABILITIES Interested firms should submit information as to the capabilities, capacity, and experience to provide an MWS as set forth below: The MWS must alert the F-15EX aircrew to the presence of missiles that may threaten the aircraft without unreasonably distracting the aircrew with false alarms. The MWS must use the six (6) pre-existing F-15EX sensor locations, data cables, power cables, and cooling. It must be easily, safely, rapidly, and organically installable and removable in the field by USAF military aircraft maintenance personnel without requiring any change to aircraft configuration beyond installation of MWS line replaceable units (LRUs) in the six (6) pre-existing locations in the aircraft dedicated for missile warning. To avoid compromise of classified information, this notice does not ask for threat missile launch and approach detection performance for various use cases nor for an MWS concept of operations. AFLCMC/WAQ may contact you to ask for detection performance information if your response to this Sources Sought notice indicates your MWS is integrable in an F-15EX aircraft. Questions: What is the name of the MWS you describe in your response to this Sources Sought notice? Please include titles, abbreviations, and nomenclature as available. Please only identify and describe a single MWS in your response. On what Department of War (DoW) aircraft model(s) is your MWS approved for operational use today? Approval for operational use requires both 1) determination of airworthiness of the aircraft with your MWS integrated and 2) sustainment of the aircraft s cybersecurity Authorization to Operate. Who are the best references (name, position, organization, commercial telephone number, and US Government email address) for DoW acquirers responsible for procuring your MWS for operational use on DoW aircraft named in question 2? Is your MWS in active production today? How many months from contract award could your MWS be delivered? Does your MWS consist only of sensor LRUs or does your MWS consist of sensor LRUs connected to a central processing LRU? If MWS sensors are connected to a central processor, how are they connected? What are the dimensions of each LRU in your MWS? You are alternately welcome to include in your response figures from engineering drawings that identify dimensions, rather than listing dimensions. How much does each LRU in your MWS weigh? How are your MWS s LRUs physically fastened to an aircraft? What are your MWS s electrical power requirements? Through what cable connection(s) is your MWS powered by the aircraft? What are your MWS s cooling requirements? Through what interface(s) is your MWS cooled by the aircraft? Can your MWS be connected to an aircraft s MIL-STD-1553 avionics bus? What are the terms by which your firm will share the MIL-STD-1553 avionics bus interface specification for your MWS with The Boeing Company so data can be exchanged between your MWS and the F-15EX s onboard mission computer? Does your MWS require the aircrew or maintenance personnel to provide information to your MWS during aircraft preflight or midflight for it to correctly detect missiles that may threaten the aircraft? If so, how is this information provided to your MWS? Does the installation on, operation of, or removal of your MWS from an aircraft expose personnel to a known health or safety hazard? Are there any known limitations on your MWS s use in the F-15EX aircraft s operational environment as verified in accordance with MIL-STD-810H? Does a field-executable procedure exist today for verifying the correct operation of your MWS during aircraft preflight or periodic inspection? If so, please briefly summarize the procedure. Does installation or removal of your MWS require any specific tools that are not commercially available? If yes, please identify the tools and tool vendors. Are there any known limitations on your MWS storage environment when MWS LRUs are not installed on an aircraft? What are your plans (if any) for adapting your MWS to meet the architecture and interface requirements of the Agile Mission Suite Government Reference Architecture (https://open-arsenal.gitlab.io/platforms/)? 1.4 NORTH?AMERICAN INDUSTRY?CLASSIFICATION SYSTEM?CODE?(NAICS):? The anticipated NAICS Code is?334511; the corresponding Small Business size?standard in?1350 employes. If the NAICS Code or Small Business size standard appears to be?incorrect,?please suggest an alternative NAICS Code and Small Business size?for consideration.? 1.5? SUBMISSION DETAILS:?? Vendors interested in responding to this announcement should submit an UNCLASSIFIED technical capabilities statement paper via DoD SAFE NO LATER THAN 12 NOVEMBER 2026, 1600, Eastern Time. To request a DoD SAFE link be sent to your email address to upload your technical capabilities statement paper, please email both Contracting Officer Stephannie Siembab at stephannie.siembab@us.af.mil and Morgan Grudich at morgan.grudich@us.af.mil. NO PHONE CALLS WILL BE ACCEPTED. CLASSIFIED information will NOT be accepted. The Government will not reimburse the contractor for any costs associated with preparing or submitting a response to this notice. Responses shall be limited to six (6), 8.5 x 11-inch pages with no smaller than 12-point font. 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. It is the submitter s sole responsibility to verify the e-file was received and can be viewed. All information received that is marked Proprietary will be handled accordingly.?Please be advised that all submissions become Government property and will not be returned. All Government and contractor personnel reviewing sources sought responses will have signed non- disclosure agreement and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described in 41 USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not property identified.? 1.6 RESPONSES SHALL INCLUDE: Name of Company, Address, and Point of Contact (Name, Title, Phone, Email) Contractor and Government Entity (CAGE) code Unique Entity ID (UEI) DUNS Number Capabilities statement paper (no more than six (6), 8.5 x 11-inch pages with no smaller than 12-point font) demonstrating ability to perform in accordance with paragraph 1.3 above Firms responding to this…