RFI for AESA Radar (Rev G)_Sensors_OCT 2024.pdf

REQUEST FOR INFORMATION

Active Electronically Scanned Array Radar Program Executive Office Aviation, In-Flight Demonstration

1.0 General

Pertaining to this notice THIS IS A REQUEST FOR INFORMATION ONLY to support a potential in-flight demonstration of the Active Electronically Scanned Array (AESA) Radar to be conducted on Redstone Arsenal, Al. It is the intent of the government to investigate AESA Radar technologies capable of fulfilling the requirements of multiple rotary and fixed wing platforms.

Desired capabilities include Fire Control, Pilotage, Pilot aid in Degraded Visual Environments (DVE), Pole/Tower and Cable Detection, Airborne Hazards, Terrain Following (TF), Terrain Avoidance (TA), and Shoreline mapping using Augmented Reality (AR) techniques. If respondents can only provide a subset of capabilities, they are still encouraged to respond.

The U.S. Government, Project Manager for Apache Attack Helicopter within the Program Executive Office for Aviation is conducting market research to determine potential sources capable of meeting technical requirements for an AESA Radar for the Army’s Attack (AH-64 Apache), Utility (UH-60 Black Hawk), Cargo (CH-47 Chinook) helicopters, Fixed Wing and Future Long Range Assault Aircraft. Interested respondents are encouraged to provide substantiated evidence of their relevant capabilities, successes, and readiness for in-flight demonstration. Section 1.0 – “Surrogate Platform Interface Requirements” gives an overview of integration requirements to mount and connect the demonstration article to a standard Apache weapons pylon. Additional information can be obtained from the AH-64E V6 TM 1-1520-263-10 Operators Manual, AH-64E V6 System Subsystem Design Descriptions (SSDD), MIL-STD-8591, and MIL-STD-810. United States Government (USG) will assist in the publishing of the required Airworthiness Release (AWR) and submission of the DD-1494 for this demonstration event.

The submission of this information is solely for informational, market research, and in-flight demonstration planning purposes. This submission is NOT a request for competitive proposals, quotations, or an invitation to reimburse responders for associated costs to respond or for any information provided. This notice does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This notice does not commit the USG to contract for any supply or service whatsoever. No reimbursement will be made for any costs associated with providing information in response to this notice or any follow up information requests. All costs associated with responding to this notice will be solely at the responding party's expense. At the discretion of the USG, some respondents may be selected to participate in an in-flight demonstration of their system; no reimbursement will be made for incurred vendor costs associated with the demonstration. Respondents not yet able to integrate onto a surrogate aircraft are encouraged to respond and highlight technical maturity limitations and other feasible demonstration capabilities.

If a respondent is not selected or ready for an in-flight demonstration but would like to sponsor its own system demonstration, the USG will consider attending the respondent-hosted event. At the discretion of the USG, a post-demonstration report may be generated regarding the respondent-hosted event with all the considerations described in section 2.5.

USG Demonstration Contributions - The USG is funding a variety of aspects of the demonstration and offering industry the opportunity to demonstrate their AESA Radar system and collect data against relevant targets on a fielded AH-64E platform. The USG will provide comprehensive support, including preparation and planning, system integration assistance, and mission planning.

The event will feature USG funded test assets such as, aircraft (AH-64E) and fuel, targets, test range, test pilots, and flight test engineers. Vendors will have access to an implemented instrumentation package including an up-down control link, and navigation data. The event will be divided into two sections, in which the vendors will benefit from performance time against generalized scenarios and a customized vendor showcase demonstration section. Additionally, the USG will supply raw demonstration data, including flight cards, aircraft and target TSPI, and a detailed post-demonstration assessment report. This demonstration is intended to provide USG with information regarding available state-of-the-art AESA technology while providing industry the opportunity to showcase their system capabilities, and to collect data against a diverse target set on a fielded weapons aerial platform.

Not responding to this notice does not preclude participation in any future RFP, if issued.

Responses to this notice are not offers and cannot be accepted by the USG to form a binding contract. The submission will require a detailed system description and expected performance against defined demonstration parameters and objectives to be performed by the demonstration article as detailed in section 2.4 when integrated on the Surrogate Platform, i.e. Fire Control Targeting, Pilotage, Pilot aid in DVE, Pole/Tower and Cable Detection, Airborne Hazards and TF & TA, and Shoreline mapping using AR techniques. The system description will include the Hardware Technology Readiness Level (HW TRL), Software TRL (SW TRL), readiness for flight and Manufacturing Readiness Levels (MRL). If the system is not ready for flight, each shortcoming must be listed, explained (to include a detailed schedule required to achieve flight readiness), and must be provided in the submission. It is the responsibility of the interested parties to monitor the System for Award Management (SAM) (https://sam.gov) site for additional information. Respondents are encouraged to provide unclassified submissions. However, if necessary, information at the secret level can also be provided (see section 6.3).

2.0 AESA Radar Description

Details provided in ENCLOSURE 1, Technical Objectives.

3.0 Product History and Capabilities

Details provided in ENCLOSURE 1, Technical Objectives.

4.0 Corporate Capabilities and Limitations

Details provided in ENCLOSURE 1, Technical Objectives.

5.0 Demonstration Strategy

At the discretion of the USG, some respondents may be selected to participate in an in-flight demonstration of their system; no reimbursement will be made for any costs associated with post RFI submittal activities. This section provides an outline of the preparation, conducting, and reporting of the demonstration event.

5.1 Notional Schedule

This schedule provides an overview of the RFI and demonstration timeline including RFI submission, vendor selection, preparation/integration, demonstration and report. This schedule is at the discretion of the USG and is subject to change.

5.2 USG Visit to Vendor Site

As part of the overall product evaluation process the USG may entertain site visits post-RFI submission to conduct the following:

• Further discuss RFI response, and familiarize USG with proposed demonstration article

• Witness an AESA Radar demonstration (if possible)

• Survey the vendors facility, design, test, & production capability

With the RFI submission, provide a schedule showing when USG can conduct a site visit to vendor facility.

5.3 Preparation/Integration

Prior to the demonstration there will be up to three planning meetings for each of the selected respondents. The planning meetings will take place in the “Integration” time detailed in line 8 of the schedule in section 5.1. The order and timing of the below meetings may be changed at the discretion of the USG.

• The first planning meeting will be up to a two-day site visit to the Redstone Test Center (RTC)

Apache hangar. It will include aircraft familiarization and interface/connection discussions with the RTC instrumentation group and experimental flight test team.

• The second planning meeting will be up to a five-day site visit to the RTC Apache hangar.

This will be an opportunity for each vendor to install the demonstration article on an Apache to check fit and function and conduct initial troubleshooting with the RTC instrumentation group and experimental flight test team.

• The third planning meeting will be up to two-day site visit to the selected vendor’s location.

The purpose of this site visit is to provide system specific hands-on training to the U.S. Army Experimental Test Pilots and Flight Test Engineers that will execute the demonstration. At a minimum, the vendor will be expected to provide training and training materials for the system control/display, discussion of modes/sub-modes, and overview of capabilities and limitations.

5.4 Demonstration Event

Each selected vendor will be allotted a three-week period to demonstrate the capabilities of their AESA system at Redstone Arsenal, Al. The demonstrations are anticipated to occur in alignment with schedule in section 5.1.

• The three-week period will include inventory, installation, ground check, instrumentation check, Electromagnetic compatibility (EMC) check, wedge check, range checkouts. These measures must be completed prior to system demonstration activities. Should the vendor be unable to meet these requirements in the allotted timeline, no demonstration flight time can be guaranteed.

• Upon completion of the required airworthiness testing, up to three pre-demonstration flights in the local flying area may be allotted to each vendor, dependent on time, weather, and maintenance. Pre-demonstration flights will support in-flight check-out, system orientation/alignment, adaptation of system to conform to targets and flight profiles.

• The three-week period will conclude with a demonstration day. The demonstration day will consist of at least one flight in which the demonstration article will be exercised against RTC developed reference scenarios. A second demonstration flight may be possible allowing vendors to further showcase key features of the demonstration article. RTC test pilots will operate the demonstration unit during the pre-demonstration flights and on the demonstration day. Vendors will be able to control/exercise the demonstration unit via the Radio Frequency (RF) up-down link as required under the direction of RTC.

• The RTC developed scenario will include attack profiles for ground, air, and littoral targeting, a Nap-of-the-Earth (NOE) route for Terrain Mapping (TM), TF, and TA, a DVE landing profile to preview pilot aided symbology, and an overwater route for Shoreline/Synthetic Aperture Radar (SAR) mapping. During demonstration the Radar will be required to detect, record and display targets at various ranges. i.e. Corner cubes, Dismounts, Ground Targets Stationary and Moving (motorcycle, truck, and tank), Littoral Targets (Stationary and Moving), Airborne Targets In-flight and at Hover (Apache, M530, T6, UAS’s), Telephone poles/towers and wires, Shoreline/SAR mapping, TF & TA, Weather.

o The inability of the demonstration article to perform all modes and functions may not disqualify vendor participation. The intent of the demonstration is to showcase current technology, not to dictate performance requirements. The flight profiles (height above target, aspect, slant-ranges) will be adapted to the demonstration article’s capabilities.

5.5 Post-Demonstration Report

It is the intent of the USG to develop a post-demonstration report for each vendor who participates in the demonstration event. Vendors will provide RAW and processed Radar data to PM Apache Sensors to substantiate the report detailing the demonstrated capabilities. The USG encourages vendors to engage in the post-demonstration data analysis and provide clarification to the USG to ensure accurate interpretation of the data. A draft copy of the report will be provided to each vendor for their comments prior to finalization. Each vendor has the rights to its recorded data and select aircraft data from the demonstration flights (states, rates, TSPI). Vendors are not prohibited from sharing this data as marketing material, and product development. Final reports will processed in accordance with Distribution D and the USG will not share the final report with industry.

6.0 RFI Protocol

6.1 Industry Discussions

The Government reserves the right to hold one-on-one meetings or an industry day as a result of responses received from this RFI as part of its market research. PM AAH office representatives may or may not choose to meet with potential respondents. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, especially any development and certification risks. To facilitate information exchange Apache Sensors will entertain a vendor’s request for an NDA.

6.2 Questions

All questions relating to this RFI shall be submitted in writing only via email to Army Contracting Command point of contact, Jarrod Weeks, Contracting Officer, at jarrod.r.weeks.civ@army.mil.

The subject line on the email submissions for questions or requests for clarifications should read:

“RFI: Apache AESA/FCR, Questions/Clarifications”. Absolutely no telephone calls will be accepted in response to this RFI. Questions or requests for clarification shall NOT contain proprietary or classified information. To facilitate a timely response, all questions or requests for clarification are due no later than fifteen (15) days after the RFI Published Date at 4:00 pm Central Time. Responses to the questions received will be answered and posted no later than thirty (30) days after the RFI Published Date at 4:00pm Central Time. USG responses will be available for all interested parties to see via an amendment to the RFI on the SAM website. The Government reserves the right to not address questions or requests for clarification should it not be pertinent to the RFI.

6.3 Responses

• Responses are due no later than sixty (60) days of RFI Published Date at 4:00 pm Central

Time. Responses shall be submitted electronically via the DoD Secure Access File Exchange (SAFE) website (https://safe.apps.mil). To be able to utilize the DoD SAFE website, request a Drop-off code via e-mail to Army Contracting Command point of contact, Jarrod Weeks, Contracting Officer, at jarrod.r.weeks.civ@army.mil. After receiving the Drop-off code, use the following distribution email address as prompted by the site:

jarrod.r.weeks.civ@army.mil.civ@army.mil. The subject line for the SAFE submission should read: RFI: “Apache AESA Radar- YOUR COMPANY NAME”. No hard copy or fax responses will be accepted. If a late submittal is received, acceptance of such will be at the discretion of USG. Telephone inquiries will not be accepted or acknowledged.

• Responders are requested to submit clear and concise written notification of their interest, qualifications, and technical concepts to meet the requirements of this RFI. All submitted responses shall follow the outline below and be provided in Microsoft (MS) Word compatible format or Adobe PDF. Responses shall be capable of being printed on 8.5x11 inch paper with one inch margin (top, bottom, left, and right) and no smaller than 12-point, Arial font. Line spacing shall be set no less than single space. Any drawings shall be capable of being printed on 11x17 inch paper and no smaller than 10-point font. Responses shall be no more than thirty

(30) total pages with limitations per section as follows: Twenty-page limit for section 3, eight-page limit for section 4, and a two-page limit for section 5. This limit excludes the cover page and table of contents. All figures and drawings are included in the page limits. All responses shall contain a Cover Page identifying:

o RFI Title o Company or organization name, mailing address (City/State/Zip), and Unique Entity

Identifier.

o Company web page URL, if any o Point of Contact (name, title, phone number, and e-mail address) o Distribution D statement

• Responses will be reviewed by Government representatives as approved by the PM AAH office and other governing agencies. All information provided will be adequately protected in accordance with the provided markings.

• Proprietary information should be clearly marked.

• It is suggested that no classified documents should be included in the responses. However, if necessary, the USG may entertain accommodating classified deliveries on a case-by-case basis. Coordination of classified deliveries shall be conducted via email with the Army Contracting Command point of contact, Jarrod Weeks, Contracting Officer, at jarrod.r.weeks.civ@army.mil

6.4 Post Submission Guidelines

Please, be advised all information submitted in response to the RFI becomes the property of the USG and will not be returned. The Government is under no obligation to provide feedback to respondents with respect to any information submitted under this RFI. There is no guarantee that any submission in response to this RFI will result in a Government program or selection for demonstration. The Government may or may not use any responses to this RFI as a basis for a subsequent project. The information submitted in response to this RFI may be used to help the Government further define its demonstration and or procurement requirements. If the Government develops a program that addresses any submitted or similar topic, the resulting procurement will address technology and business specific requirements as defined by the Government to achieve the required objectives. Any projects developed from the RFI responses may be the subject of a subsequent acquisition; any such subsequent acquisition will be publicized accordingly.

Responders to this RFI will have no competitive advantage in receiving any awards related to the submitted topic area. Responders who do not submit a white paper to this RFI will not be prohibited from submitting a proposal if an RFP is published at some point in the future.