New Radar TBGR RFI 9.4.25.pdf

Missile Defense Agency (MDA) Theater Based Ground

Radar Request for Information

NAICS: 334511

PSC: AC25

Agency: Other Defense Agencies

Office: Missile Defense Agency

Location: MDA-TBS

Description: The Missile Defense Agency’s Mobile Land-Based Sensors Program Office

(MDA/TBS) is conducting market research to determine industry interest and capability to meet requirements for a new radar in support of the Next Generation Missile Defense.

This Request for Information (RFI) is issued solely for information and planning purposes – it does not constitute a Request for Proposal (RFP) or promise to issue an RFP in the future. This

RFI does not commit the government to establish a contract for any supply or service whatsoever. Further, MDA is not seeking nor will it accept proposals. All costs associated with responding to this RFI will be solely at the respondent’s expense. Participation in future Agency transactions and procurement opportunities is not contingent on responding to this RFI. MDA will not provide feedback for any submission.

Introduction:

The new radar is envisioned to acquire, track, and discriminate missile threats to the U.S.

homeland. It is intended to be mobile, not a static fixed-site radar. The singular term ‘radar’ is used by convention in this document; however, that does not preclude multiple phased array panels combined into a system level solution.

Schedule:

Production of the first radar unit must complete no later than 31 December 2028 and two additional units complete no later than 31 December 2029. Demonstration of the required radar system capability described below is to be accomplished through Modeling and Simulation by

HWIL testing. Demonstration of the required radar sensitivity metrics below is to be accomplished through tracking of government designated calibration satellites and aircraft.

Notional Threat Vignettes:

• Ballistic Missile Defense:

o Objective Sensitivity: -10 dBsm target at 2233 km range. (15 dB SNR with single pulse or CPI dwell time no greater than 10 milliseconds) o Each ballistic missile defense target will consist of a complex containing one or multiple re-entry vehicles, spent boosters, decoys, jammers, and debris.

o Quantity of ballistic missile defense targets: 24 o The term ‘ballistic’ is here for legacy nomenclature purposes and does not imply that the threat’s trajectory is purely ballistic motion, i.e. it may maneuver at any point in the trajectory.

• Hypersonic Missile Defense:

o Objective: -20 dBsm target at 375 km range. (15 dB SNR with single pulse or

CPI dwell time no greater than 2.5 milliseconds) o Each hypersonic missile defense target will consist of a complex containing one glide body, decoys, and jammers.

o Quantity of hypersonic missile defense targets: 10 o The hypersonic glide body is expected to be maneuvering at the upper end of the atmosphere during most of its visible timeline, although it may begin its trajectory as a ballistic missile threat type.

• Cruise Missile Defense:

o Objective: -20 dBsm target at 200 km range. (15 dB SNR with single pulse or

CPI dwell time no greater than 1.0 milliseconds) o Each cruise missile defense target will consist of a complex containing one aerodynamic cruise missile body, decoys, and jammers.

o Quantity of cruise missile defense targets: 24 o The cruise missile is expected to be flying at low altitudes, and the intent is to acquire the threat soon after it breaks radar horizon limited by curvature of the earth.

Required Radar Capabilities:

• Acquisition:

o The radar system should be able to acquire a combined total threat raid of the quantity specified of all three missile types (i.e. ballistic missiles, hypersonic missiles, and cruise missiles simultaneously) at the ranges specified in the threat vignettes described above. The capability to perform low elevation acquisition will be very important for hypersonic and cruise missile threats. It is expected that potential offerors will describe their design approach to deliver this capability.

o Overall Field-Of-View (FOV):

▪ Ballistic Missile Defense: ±65° azimuth from boresight; 1° – 90° elevation

▪ Hypersonic Missile Defense: 360° azimuth coverage; 0° – 90° elevation

▪ Cruise Missile Defense: 360° azimuth coverage; 0° – 90° elevation

• Tracking:

o Track Quantity:

▪ The radar system should be able to track a combined total threat raid of the quantity specified of all three missile types (i.e. ballistic missiles, hypersonic missiles, and cruise missiles simultaneously) at the ranges specified in the threat vignettes described above.

o Track Initiation:

▪ Track shall be established on hypersonic and cruise missile targets within

1° of horizon break. Track firmness shall be adequate to maintain track identity (track number) continuity.

o Track Accuracy:

▪ The track accuracy for ballistic missile threats should be no worse than

1km overall position error and 10m/s velocity error after 60 seconds of track time. Overall position / velocity error includes all error sources, including radar registration errors and scan biases.

o Track Purity:

▪ The radar system should be able to maintain correct individual track numbers on each object in the threat complex despite endo or exo-atmospheric maneuvers for the threat vignettes described above.

• Discrimination:

o The radar system should be able to discern which objects carry the warhead from decoys, debris, and other inert objects in a period of time no greater than 180 seconds of track time.

• Interceptor Support:

o The radar system should be able to provide in-flight guidance updates to an interceptor as well as other status and informational messages.

o The interceptors require X-band communications and the system may require a designated uplinker if this functionality is not provided by the main array.

• Communication:

o The radar system should be capable of interfacing both with the MDA C2BMC and Army IBCS battle management systems.

• Transportability:

o The radar system should be transportable, and upon reaching the intended radar site, be able to be physically emplaced and operational in a time period of no greater than 24 hours. The radar system should be able to be calibrated to meet mission requirements in a time period of no greater than 48 hours.

• Architecture:

o A modular build-block antenna architecture which lends itself to cost-effective construction of subscale arrays is preferred

• Physical Footprint:

o The radar system should occupy a footprint no greater than 100 m x 100 m.

• Personnel Utilization:

o The radar system should require not greater than 2 onsite personnel. Personnel should be in the maintainer / caretaker role and will not be radar operators. Radar operation will be managed from a remote location. Radar operation tasks include, but are not limited to:

o Remote loading of radar system software, operating system, cybersecurity patches, mission profiles, and associated updates.

o Continuous radar calibration in parallel with live operations: calibration processes should not require specialized subject matter expertise to execute.

o Automatic generation of quick-look reports/briefings for post-event analysis.

o Logistics support approaches should minimize on-site “fly-away” personnel requirements and leverage methods such as vendor maintenance agreements and digital reachback.

• Frequency:

o The radar system’s frequency will not be specified, however potential designs should avoid frequency bands currently or planned to be in commercial use within

CONUS or included in upcoming FCC spectrum selloff plans.

• Power/Cooling:

o The radar system’s prime power should be provided by one or several standard

MEP-810D units providing 4160 Volt, 3 phase, 0.8 PF, and 4-wire distribution.

• Electromagnetic Interference (EMI) Protection:

o The radar system should be High Altitude Electromagnetic Pulse (HEMP) hardened.

• Electromagnetic Protection (EP):

o The radar system should provide mitigations against jamming.

• Reliability:

o The radar system should be capable of 24/7 operations for a period of 90 days.

The design should avoid single points of failure and be easily sustainable in the field.

• Other Items:

o It is also important to note that form factor, cooling, maintenance, and weather protection are important, but solutions are not specified in this document, as intended, to allow for design flexibility.

• Note: This RFI is not a requirements document, the requirements listed here are not intended to be complete but rather give a flavor for the key government considerations for potential designs.

Instructions for Submissions:

Respondents to this RFI are invited to prepare and submit responses, no later than 45 days after release. The Government has granted an extension to 12-Sept-2025 to allow for CUI submissions. No further extensions will be granted. Responses should be UNCLASSIFIED and/or CUI and include the following:

1. Responses shall be submitted in Microsoft (MS) Word compatible format or electronic

Portable Document Format (.pdf) only with searchable capability (no scanned documents), capable of being printed on 8.5x11 inch paper with one inch margin (top, bottom, left, and right), single-line spaced, Times New Roman font, and no smaller than

12-point font. Any drawings shall be capable of being printed on 11x17 inch paper and no smaller than 10-point font. All figures and drawings are included in the page limits.

All responses shall contain a cover page identifying:

i. RFI Title

ii. Company or organization name, mailing address (City/State/Zip), and

Unique Entity Identifier

iii. Company web page URL, if applicable

iv. Point of Contact (name, title, phone number, and e-mail address)

2. For each major requirement area identified above in which the respondent expresses capability/interest, submit:

a. White paper (not to exceed 30 pages) that discusses capabilities, recommended alternatives, associated non-recurring engineering costs, and associated risks and mitigation strategies. Note: Risk mitigation strategies should address:

i. Production of hardware to meet delivery timelines.

ii. Radar software strategy to meet mission requirements.

iii. The technical risks inherent in manufacturing processes.

iv. The technical cost drivers for development and life cycle cost, and opportunities to reduce the Total Ownership Costs.

v. Description of contractor’s experience with development, implementation, and management of a product support strategy while applying life cycle management principles.

vi. Provide Rough Order of Magnitude cost for the proposed concept, to include estimated breakout of development, and engineering services.

3. Data Requirements: Provide a detailed list (page limit is as required) and description of documentation requirements for a technical library to support your development of a future competitive proposal, organized by requirements area identified above, should

MDA compete any or all of these requirements. No Government information will be supplied in conjunction with this Sources Sought.

Proprietary information is neither sought nor desired by MDA. If such information is submitted, it must clearly be marked "proprietary" on every sheet containing such information, and the proprietary information must be segregated to the maximum extent practicable from other portions of the response (e.g., use an attachment or exhibit). Respondents are responsible for adequately marking propriety information contained in their response. The Government intends to use third party, non-Government (contractor) support personnel as subject matter experts in the review of responses received, including the review of any marked or unmarked proprietary information provided. Appropriate non-disclosure agreements have been executed between the third party, non-Government (contractor) support personnel and the Government and are on file with the Government. A submission of a response to this RFI constitutes the respondent’s acknowledgement and agreement that the information provided in the response, including any marked or unmarked proprietary or source selection information, may be disclosed to these third party, non-Government (contractor) support personnel.

Questions regarding this announcement shall be submitted in writing by e-mail to the

Contracting Officer. Submit all questions no later than 15 days after release. Although the

Government will attempt to answer all questions submitted, the Government is under no obligation to answer any questions submitted after the 15 days. Telephone or verbal inquiries will NOT be accepted or acknowledged, and no feedback or evaluations will be provided to companies regarding submissions. The overall deadline has been extended to 12-Sept-2025.

Any CUI level submission will be accepted, however, you must request a DoD SAFE link no later than 9-Sept-2025 and must be submitted by the extended date of 12-Sept-2025. Request should be made to Logan Phifer at logan.phifer@mda.mil. All unclassified correspondence related to this matter, should be e-mailed to mda.new-radar-rfi@mail.mil and copied to the

Contracting Officer as follows:

mailto:logan.phifer@mda.mil mailto:mda.new-radar-rfi@mail.mil

Contracting Office Address:

Missile Defense Agency, MDA/DACB

Building 5224, Martin Rd, Attn: VBIII

Redstone Arsenal, AL, 35898, UNITED STATES

Point of Contact:

Contracting Officer

Erica Barbee, Procuring Contracting Officer, Mobile Land-Based Sensors AN/TPY-2

Email: Erica.M.Barbee.civ@mda.mil mailto:Erica.M.Barbee.civ@mda.mil