AN/TPY-2 Radar Program Request for Information

Missile Defense Agency (MDA) AN/TPY-2 Radar Program Request for Information NAICS: 334511 PSC: AC25 Agency: Other Defense Agencies Office: Missile Defense Agency Location: MDA-SNA Solicitation Number: N/A Reference-Number: 24-MDA-11952 Notice ID: MDA25SNRFI02 DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Approved for Public Release: 5-Nov 2024 I. DESCRIPTION A. AN/TPY-2 Description: The Missile Defense Agency's Ground Sensors Directorate (MDA/SN) is conducting market research to determine industry interest and capability to support future requirements for its Army Navy/Transportable Radar Surveillance and Control Model-2 (AN/TPY-2). The requirements include hardware and software development development (to include radar modeling and simulation); production of components, spares, fleet refurbishment, and capability upgrades; and operations and sustainment of AN/TPY-2 radars. Responses to this Request for Information (RFI) may address all or part of these requirements. The Government invites industry to provide feedback on contracting strategy for the requirements to include combination of requirements, contract type, and areas that would be accomplished well through small business set aside versus full and open competition. This 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 of the requirements. Further, MDA is not seeking proposal 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. II. AN/TPY-2 RADAR MAJOR REQUIREMENT AREA DESCRIPTIONS A. Development 1. Software Maintenance Current software primarily developed in Ada language 2. Software upgrades Open Architecture to accommodate integration of 3rd part algorithms Modular design New Capability Development Acquisition Tracking Discrimination Debris mitigation Electronic Protection Post-intercept Assessment Fault tolerance Active bias monitoring and reporting Radar Integrated Satellite Monitoring and Calibration Space Situational Awareness/Space Domain Awareness Target Object Map Raid handling Long Range High Sensitivity Low and High Elevation Full Azimuth Coverage 3. Hardware upgrades Digital Receiver/Exciter (DREX) Wideband Digital Signal Processing Arbitrary Waveform Generator Digital Array architecture upgrades to the AN/TPY-2 Antenna Equipment Unit Additional distributed, passive or active phased array panels to support mission objectives against advanced threats. Performance information is desired for these potential upgrades. 4. Architecture to optimize performance on an x86-based supercomputer and the implementation of a DREX Performance improvements, including, but not limited to, analysis and implementation of parallel processing, multicore computing, Field Programmable Gated Arrays, and advanced real-time processing capabilities Re-architecture including, but not limited to, analysis and implementation of secure server configurations eliminating, mitigating, and limiting cyber vulnerabilities 5. System Engineering Support software, software databases, and hardware upgrades including new functionality and evolving threats. Systems engineering includes configuration management, requirements development and analysis, software capabilities performance assessment, qualification, formal test, and requirements verification. Systems engineering support is also required to: Support radar system integration and test with the Terminal High Altitude Area Defense (THAAD) weapon system at the prime contractor's System Integration Laboratory (SIL) for development and flight test activities Support radar system integration and test with Command, Control, Battle Management & Communication (C2BMC) weapon system at the prime contractor's SIL for development and flight test activities. Support United States Government (USG) and Foreign Military Sales (FMS) development and support efforts. Support software and hardware engineering technical reviews via incremental development such as agile methodologies. Adhere to guidance and develop program documentation including but not limited to management plans, quality, safety, security, reliability, risk, program protection, cybersecurity, integration, interoperability, capability roadmaps, Concept of Operations (CONOPS), trade studies, cost, schedule and performance, working groups, contract execution, development oversight, and reporting. Develop and maintain Operation Mission Plans/Profiles (OMPs) across several geographical locations. Flight and Ground Test Planning, Execution, and Analysis. Software Engineering Releases (ER), Formal Releases (FR), and Maintenance Releases (MR) to support material release of capabilities for Technical Capability Declaration (TCD) and Operational Capability Baseline (OCB) concurrence. Support radar software Independent Verification and Validation (IV&V) at the Government's Software Engineering Directorate (SED). 6. Engineering support Facilitate maintenance efforts which may include but are not limited to: Trade studies Hardware obsolescence studies Hardware redesign Technology insertion Refurbishment efforts. 7. Modeling and Simulation Systems engineering, development, maintenance, test, verification and validation of real-time and non-real-time digital end-to-end radar models and real-time HWIL radar driver for AN/TPY-2. Digital radar models and HWIL driver should accurately simulate and/or stimulate tactical AN/TPY-2, while maintaining the fidelity of complex radar scenes presented to the model and simulation. Complex radar scenes typically include simple and advanced threats comprised of multiple objects and scatterers, and the effects as they propagate through an air picture. The air picture captures weather, environmental, and other effects. Examples include but are not limited to precipitation, sky noise, tropospheric effects, and intercept debris. Complex radar scenes may also incorporate electronic attack. Model development, verification, validation, and accreditation must support tactical development, test and fielding in accordance with the MDA Phased Implementation Plan and Integrated Master Test Plan. HWIL radar drivers, aligned to tactical radar capabilities, are required for development and testing of the radar software, and are required early in the radar software development timeline due to increasingly complex radar capabilities. Therefore, HWIL radar drivers must be developed as part of the agile radar development cycle to more closely coordinate with radar development efforts, and must be integrated with the HWIL radar representation as part of the development cycle. Due to increasing stakeholder needs for digital radar models early in the radar software development cycle, digital radar models, with capabilities aligned to tactical radar software releases, are required along the same timeline as radar software releases, to include radar software engineering releases and formal releases. Therefore, digital end-to-end radar models should utilize Wrapped Tactical Code (WTC) methodology, as applicable, using radar software source code with appropriate interfaces to operate in both real-time and non-real-time as either standalone models or as part of integrated system simulations such as End-to-End Digital Integrated System Simulation (EDISS). Models and simulations should implement tactical messages and interfaces that integrate into interoperable frameworks such as the OSF for Ground Test Integrated System Simulation (GTISS) and EDISS. Integration of digital radar models and HWIL radar drivers with simulation frameworks such as the OSF for GTISS and EDISS. Maintenance and test of COTS hardware used by digital radar models and HWIL radar drivers to ensure models meet cybersecurity and performance requirements needed to satisfy intended use cases. Development and maintenance of current applicable cybersecurity documentation for each radar model in order to support Risk Management Framework (RMF) authorization. Implement applicable cybersecurity requirements and solutions into System Development Life Cycle (SDLC). Development of RMF package and support cybersecurity and Software Assurance (SwA) requirements and activities for each radar model. Provide RMF continuous monitoring. Development and maintenance of radar model training materials. Conduct as needed, hands-on training to end-users and stakeholders. Support for use of models and simulations in events, including but not limited to the following: Performance Assessment Warfighter Exercises and Training Element Development and Verification Tactical Software Verification Testing Ground Test (GT) Integrated Ground Test (GTI) Distributed Ground Test (GTD) Continuous Digital Assessment (CDA) Tactical Evaluation Tactical Performance Verification Test and Operational Mission Plan Analysis & Development Pairwise Testing Flight Test Pre-Mission Testing Flight Test SPMT Flight Test Element Pre-Mission Analysis Post-Flight Reconstruction (PFR) and Satellite-pass Reconstruction System Post-Flight Reconstruction (SPFR) for Validation & Anchoring Element Post-Flight Reconstruction (EPFR) for Validation & Anchoring Continuous Development and Integration (CDI) and Opportunistic Test System Federated Verification Event (SFVE) Special Studies Live and HWIL events for data collection to support radar fielding decisions B. Production 1. Production Components Hardware production, integration, test, and delivery of components and end items to mitigate obsolescence, increase end item quantities, and provision spares. Components and end items include, but are not limited to: Spares for radar components (including Gallium Nitride (GaN) Transmit Receive Integrated Microwave Modules (TRIMMs)) Digital Receiver/Exciter (DREX) Upgrade Kits Advanced Signal Processing Server/Network Kits with interconnection kits AN/TPY-2 Cooling Equipment Unit (CEU) upgrade kits Baseline upgrade: heat exchangers, motor controllers, and associated hardware AN/TPY-2 Antenna Equipment Units (AEU) Baseline upgrade: control panel, variable frequency drives, and associated hardware AC/DC Converters 2. Engineering Support Maintenance and sustainment efforts which include, but are not limited to: Trade studies Hardware obsolescence studies Hardware redesign Technology insertion Refurbishment efforts 3. Systems Engineering Redesign for out-of-production mitigation, fabrication, integration, test (design verification, qualification, and acceptance) evaluation, documentation, and delivery of Radar hardware. Systems engineering includes cost, schedule, technical, performance, and reliability risk management processes to mitigate program and schedule risk. 4. Program Support Configuration management Quality assurance Operations and program security requirements Missile Defense Agency Assurance Provisions (MAP) and Parts, Materials, and Processes Mission Assurance Plan (PMAP); and safety Manufacturing qualification processes 5. Integrated Logistics Component, part, and end item marking and tracking Component and end item integration, calibration, and acceptance testing Sparing strategy development, spare production, and spare delivery Management and tracking of Government Furnished Equipment/Material 6. Program Management Integrated approach to monitoring and reporting cost, schedule, and fiscal status Technical reviews/technical interchange meetings Integrated product team organization, inclusive of government participation 7. Test Functions Activities necessary to confirm component and end item performance in accordance with requirements. Tests may be conducted at government owned ranges and test facilities, in addition to contractor owned facilities. Tasks are conducted in accordance with Department of Defense and other government regulatory guidance. C. Operations and Sustainment 1. Radar Operation and Maintenance Support (at multiple sites) Diagnose hardware and software failures Provide Software and Hardware Maintenance as primary maintainer for all levels of maintenance 2. Radar Logistics Support Establishment and maintenance of permanently deployed site support team at OCONUS locations Establishment and maintenance of deployable site support team at CONUS locations Line Replaceable Unit (LRU) Repair and Return Provide Subject Matter Expertise (SME) to Depot when required for MEI refurbishments Inventory Control and Management Spares Management Logistics Operations Training Development and Delivery for soldiers and contractor personnel World-wide deployment, transportation coordination, set-up, and tear-down of the AN/TPY-2 Radar fleet (both forward-based and Terminal High Altitude Area Defense (THAAD) radars) 3. Sustaining Engineering Support for all AN/TPY-2 radars to facilitate maintenance efforts, which may include but are not limited to trade studies and analysis, hardware obsolescence studies, hardware redesign, technology insertion, and refurbishment efforts. Engineering Analysis and Studies Sustainment of legacy software Builds Failure Review and Corrective Action System (FRACAS) Mission Assurance/Quality support Obsolescence Management Obsolescence forecasting Obsolescence mitigation recommendations Obsolescence redesigns as required Fleet retrofits as required III. INSTRUCTIONS FOR SUBMISSION A. Deadline Respondents to this RFI are invited to prepare and submit responses, no later than 60 calendar days from the release date of this RFI. The Government does not intend to extend this due date. B. Required Documents 1. Executive Summary Executive Summary (not to exceed 5 pages or slides, excluding 1.d. below) that includes: a. A summary matrix indicating interest in competing for one or more requirement area listed above. b. Indication if the respondent possesses a facility clearance and to what level. c. Descriptive Data: i. Company Name ii. Specify if US or foreign owned iii. Point of Contact (POC) iv. POC Address v. POC Telephone and Fax Numbers vi. POC e-mail Address vii. DUNS Number viii. CAGE Code and/or Tax ID Number ix. Business Size Standard and applicable NAICS codes x. Socio-economic Category, if applicable (e.g. woman-owned small business, HUBZone small business; etc.) d. Indicate whether Government Furnished technical data would be required in order to facilitate the execution of the capabilities identified in response to this RFI. List and describe this data (does not count toward page limit for Executive Summary) e. Indicate whether the respondent is currently performing as a MDA TEAMS or TEAMS-NEXT prime or subcontractor (include contract name (s) and number (s)). f. Recommend break out of for requirement areas and areas that could be set-aside for small business g. Provide existing Multiple Award Schedule (MAS) or other Government-wide requirement to be evaluated as a possible acquisition strategy h. Provide feedback regarding consolidation or break-out of requirements, contract type, and areas that would be accomplished well through small business set aside versus full and open competition. 2. White Paper For each major requirement area identified above in which the respondent expresses capability/interest, submit a White paper (not to exceed 10 pages) that discusses capabilities, recommended alternatives, associated non-recurring engineering costs, and associated risks and mitigation strategies. Note: Risk mitigation strategies should address: i. Development or improvement of X-Band radar capabilities and hardware including experience, manufacturing processes, integration approaches, and testing. ii. Production of AN/TPY-2 Radar system components. Mitigation of any production learning curve impacts (trained personnel, maintenance, and situational awareness, etc.). iii. Failure examination and root cause analysis of failed weapon system components. iv. Development of tactically-aligned AN/TPY-2 models on the timeline required v. Mitigation of any M&S learning curve impacts 3. Capability Brief For each major requirement area identified above in which the respondent expresses capability/interest, submit a capability brief discussing (not to exceed 30 slides) the respondent's capabilities to perform the requirement area(s) identified above and relevant experience. The brief should include: i. A schedule estimate highlighting initial capability delivery/availability. ii. If your response addresses a subset of a requirement area identified in the Executive Summary versus the entire requirement, address how any seams/gaps would be mitigated. iii. Description of any experience with MDA Mission Assurance Provisions (MAP) and Parts, Materials and Processes (PMP) compliance. iv. Description of any experience with configuration management processes and tools during development and production. v. Identification of any software Capability Maturity Model Integration (CMMI) designations 4. Data Requirements Provide a detailed list 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 Request for Information. 5. Small Business Considerations Because one objective of this RFI is to determine the capability of small business to meet the requirements contained herein, and to inform the acquisition strategy with regard to setting aside any future acquisition for small businesses, small businesses are encouraged to respond to this request for information for those areas of the listed requirement in which they have an interest. MDA request the following information: The prime small business contractor responding to this RFI must include their past experience in managing subcontractors on similar requirements, and if applicable, include subcontractor or teaming partners past experience applicable to requirements specified in this RFI. Responsible small businesses planning teaming arrangements to meet the support requirements listed above are expected to articulate the portions of work that the prime small business intends to perform as well as articulate the portions that subcontractors or teaming partners (if applicable) will perform. Responses must include business size and business socio-economic category of all subcontractors or teaming partners identified to perform work associated with the NAICS for this RFI. C. Additional information 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. D. Point of Contact for Submissions Questions regarding this announcement shall be submitted in writing by e-mail to the Contracting Officer. Submit all questions no later than 30 calendar days from the release date of this RFI. Although the Government will attempt to answer all questions submitted, the Government is under no obligation to answer any questions submitted after 30 calendar days from the release date of this RFI. Verbal questions will NOT be accepted. All non-proprietary questions and answers will be distributed via e-mail to all respondents. Validated proprietary questions and answers will be addressed with individual companies and will not be distributed via e-mail. Based on the responses from Industry, Industry Days and One-on-ones may be scheduled in the future. Contracting Office Address: Missile Defense Agency, MDA/SNK Building 5224, Martin Rd, Attn: VBIII Redstone Arsenal, AL, 35898, UNITED STATES Primary Point of Contact: John Michael, Procuring Contracting Officer, Ground Sensors Contracts Email: john.michael@mda.mil Secondary Point of Contact: Kimberly Black, Procuring Contracting Officer, Ground Sensors Contracts Email: kimberly.black@mda.mil