Missile Defense System Test Planning, Execution, and Analysis, Modeling and Simulation, and AN/TPY-2 Radar Contractor Logistics Support Request for Information

Missile Defense Agency (MDA) Ground Sensors (SN) Programs Request for Information Solicitation Number: To Be Determined Agency: Other Defense Agencies Office: Missile Defense Agency Location: MDA-SNA Reference-Number: MDA21SNRFI01 DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Approved for Public Release 21-MDA-10848 (4 Jun 21) Description : The Missile Defense Agency Ground Sensors Directorate (MDA/SN) is conducting market research to determine industry interest and capability to support future requirements for the Missile Defense System (MDS). The mission of MDA/SN is to develop, test, acquire, deploy, and sustain MDS radars. MDA/SN radars include X-Band (Army Navy/Transportable Radar Surveillance and Control Model 2 (AN/TPY-2), Sea-Based X-Band Radar (SBX), S-Band (Long Range Discrimination Radar (LRDR), UHF (Upgraded Early Warning Radar (UEWR)), and L-Band (COBRA DANE (CD)). Each requirement below should be addressed with a separate submission response. Future requirements may include: (1) MDS Test Planning, Provisioning, Execution, Analysis, and Infrastructure. Efforts associated with the first requirement may include test provisioning, operation, and non-Commercial Off-the-Shelf (COTS) sustainment for the Hardware-in-Loop (HWIL) representations for each sensor along with laboratory facilities that will be required to execute System Pre-Mission Testing (SPMT) for flight tests, MDS flight and ground testing, and element level testing. This also includes tech refresh (including cyber security), maintenance, and operation of two shelters that support AN/TPY-2 participation in MDS flight test, the Mission Operations Center (MOC) and the Mission Support Center (MSC). (2) Modeling and Simulation (M&S) support for AN/TPY-2, SBX, LRDR, UEWR, and CD. Efforts for the second requirement may include development and sustainment of digital and HWIL radar models to accurately simulate and/or stimulate MDS tactical radars. This also includes tech refresh of system hardware as needed to satisfy cybersecurity and performance requirements. (3) AN/TPY-2 Radar Contractor Logistics Support (CLS). Efforts for the third requirement may include Operations and Sustainment (O&S) support for a family of AN/TPY-2 radars. This also includes integration and management support for the deployment, site facilities planning, operation and sustainment of radar systems, facilities, and support equipment. This Request for Information (RFI) is issued solely for information and planning purposes – it does not constitute a Request for Proposal (RFP), a promise to issue an RFP in the future, or that any future RFP would include all of the three requirements associated with this RFI. This RFI does not commit the Government to establish a contract for any supply or service whatsoever. Further, MDA is not seeking proposals 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 upon responding to this RFI. MDA will not provide feedback for any submission. Marking: 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., paragraph markings, image markings, or use an attachment or exhibit). Respondents are responsible for adequately marking proprietary information contained in their response. The Freedom of Information Act (FOIA) and its amendments have resulted in an increasing number of requests for copies of industry documents submitted to federal agencies. If a respondent’s submissions contain information that he/she believes should be withheld from such requestors under FOIA on the grounds that they contain “trade secrets and commercial or financial information” [5 USC§552(b)(4)], the respondent should mark its submissions in the following manner: The following notice should be placed on the title page: “Some parts of this document, as identified on individual pages, are considered by the respondent to be privileged or confidential trade secrets or commercial or financial information not subject to mandatory disclosure under the Freedom of Information Act. Material considered privileged or confidential on such grounds is contained on page(s) [enter page number(s)].” Each individual item considered privileged or confidential under FOIA should be marked with the following notice: “The data or information is considered by the submitter to be confidential or privileged, and is not subject to mandatory disclosure under the Freedom of Information Act.” Response Review: The MDA intends to use third party, non-Government (i.e., 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 support personnel and the MDA and are on file with the MDA. A submission of a response under this RFI constitutes a grant of authority by the respondent to the MDA to allow access to Federal personnel and these third party individuals to any content of the submission that may constitute material within the ambit of the Trade Secrets Act, 18 U.S.C. 1905. Background: The Missile Defense Agency Ground Sensors Directorate (MDA/SN), located at Redstone Arsenal, Alabama, is responsible for the development, testing, and sustainment of sensors that provide the acquisition and tracking of missiles that may be launched against the United States, deployed forces, friendly nations, and allies. The primary objective of the Ground Sensors Directorate is to provide a pervasive sensor network for the MDS that ensures each sensor integrates into the layered defense system, with the ultimate goal of providing target information that can be used by any weapon in the system. Radar testing ensures effective development and maturation of the MDS and encompasses detection, tracking, and threat discrimination/classification during the early, midcourse, and terminal phases of flight. Radar testing also consists of ground testing within a Hardware in the Loop (HWIL) lab in CONUS or a distributed ground test at the radar site, which may be CONUS or OCONUS. Flight tests are executed between multiple sites, and may require radars to be relocated to obtain the required test configuration. Test execution may require personnel and equipment deployment to the radar site. Models and Simulations are required to support development, testing, and sustainment of sensors and other MDS elements, as well as MDS-level performance assessments and Warfighter events. Contractor Logistics Support (CLS) is required to support the family of Missile Defense System AN/TPY-2 radars and associated equipment. The support includes but is not limited to integration and management support for the deployments, site facilities planning, and operation and sustainment of radar systems, facilities, and equipment. Radar Test Major Requirement Area Description: 1. MDS Test Planning, Execution, and Analysis (Anticipated NAICS / PSCs: 541330 / AC25 and 5840) Sensors test planning, provisioning, and execution is the responsibility of the MDA Ground Sensors Test Division (MDA/SNT) and Sensors test analysis is the responsibility of the MDA Ground Sensors Systems Engineering (MDA/SNE), both are located at Redstone Arsenal, Alabama. Test events are defined in the MDS Integrated Master Test Plan (IMTP). MDA plans, executes, and analyzes test events in the manner outlined in the MDA Flight and Ground Test Concept of Operations (CONOPS). Typically, Test Support includes a consistent level of support for MDS ground testing in concert with the Continuous Integration/Continuous Agile Testing (CI/CAT) to include SPMTs, one to two flight tests per year, and pairwise element level testing with other MDS Elements as required. MDA executes the IMTP-defined ground test events at HWIL facilities or at distributed radar sites. The HWIL equipment utilized in testing currently consists of multiple test strings, all located at the Advanced Research Center (ARC) in Huntsville, Alabama. HWIL strings (with the exception of CD) are Unix- or Linux-based processors, storage, and display equipment loaded with mission software (as applicable) which represents the functionality and performance of Prime Mission Equipment (PME). HWIL CD strings are Digital Equipment Corporation (DEC) Virtual Address eXtension (VAX) processors, storage, and display equipment loaded with CD mission software, which represents the functionality and performance of CD PME. X-Band (AN/TPY-2 and SBX) Radar Test Planning, Execution, and Analysis Flight Test planning, execution, and analysis of MDS test requirements in accordance with the MDA IMTP: Pre-test planning and analysis (includes SPMTs) Electromagnetic Interference (EMI) Analysis Test Execution Post-test analysis and reporting Test Provisioning Test Infrastructure maintenance (MOC/MSC) (AN/TPY-2) Ground Test planning, execution, and analysis of MDS test requirements in accordance with the MDA IMTP and the CI/CAT CONOPS: Pre-test planning and analysis Take Objective Simulation Framework (OSF) scenario binary file(s) and create a test case for the signal injection system for AN/TPY-2 Take OSF scenario binary file(s) and create a test case for the signal injection system for SBX Test Execution Post-test analysis and reporting Operation and Sustainment (Non-COTS only) of HWIL Strings Radar element level testing and pairwise/integration testing Command, Control, Battle Management & Communication (C2BMC), Ground-based Midcourse Defense (GMD), and Terminal High Altitude Area Defense (THAAD). S-Band (LRDR) Radar Test Planning, Execution, and Analysis Flight Test planning, execution, and analysis of MDS test requirements in accordance with the MDA IMTP: Pre-test planning and analysis (includes SPMTs) Electromagnetic Interference (EMI) Analysis Test Execution Post-test analysis and reporting Ground Test planning, execution, and analysis of MDS test requirements in accordance with the MDA IMTP and CI/CAT CONOPS: Pre-test planning and analysis Take OSF scenario binary file(s) and create a test case for the signal injection system for LRDR Test Execution Post-test analysis and reporting Operation and Sustainment (Non-COTS only) of HWIL Strings Radar element level testing and pairwise/integration testing with C2BMC, GMD, and OSF. UHF and L-Band (UEWR and CD) Radar Test Planning, Execution, and Analysis Flight Test planning, execution, and analysis of MDS test requirements in accordance with the MDA IMTP: Pre-test planning and analysis (includes SPMTs, if required) Test Execution Post-test analysis and reporting Ground Test planning, execution, and analysis of MDS test requirements in accordance with the MDA IMTP: Pre-test planning and analysis Take OSF scenario binary file(s) and create a test case playback for CD Take OSF scenario binary file(s) and create a test case for the signal injection system for UEWR Test Execution Post-test analysis and reporting Operation and Sustainment (Non-COTS only) of HWIL Strings Radar element level testing and pairwise/integration testing with GMD and OSF. M&S Major Requirement Area Description: 2. Modeling and Simulation (Anticipated NAICS / PSCs: 541330 / AC25 and 5840) Full life-cycle systems engineering, development, maintenance, test, verification and validation of real-time and non-real-time digital models and HWIL radar drivers for MDA ground sensors (SBX, AN/TPY-2, LRDR, UEWR, and CD). Developed models should accurately simulate and/or stimulate MDA tactical radar, while maintaining the fidelity of complex radar scenes presented to the model and simulation. Complex radar scenes typically include multiple objects and scatterers, and their propagation through weather and other environmental effects, not limited to effects such as rain and intercept debris. Models and simulations should implement tactical messages and interfaces that integrate into interoperable frameworks such as the OSF. Development, maintenance, and test of COTS hardware used by digital models and HWIL radar drivers to ensure models meet performance requirements needed to satisfy intended use cases. Development and maintenance of sensor model training materials. Conduct as needed, hands-on training to end-users and stakeholders. Development and maintenance of current applicable cybersecurity documentation for each sensor 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 sensor model. Provide RMF continuous monitoring. 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) Tactical Evaluation Tactical Performance Verification Test and Operational Mission Plan Analysis & Development Pairwise Testing Pre-Mission Testing Flight Test SPMT Flight Test Element Pre-Mission Analysis Post-Flight Reconstruction 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), CI/CAT, Opportunistic Test Special Studies Live and HWIL events for data collection for radar fielding decisions AN/TPY-2 Radar Contractor Logistics Support (CLS) Major Requirement Area Description: 3. CLS (Anticipated NAICS / PSCs: 334511 / L058) The Missile Defense Agency (MDA) has a requirement for Operations and Sustainment (O&S) support for the family of Ballistic Missile Defense System (BMDS) AN/TPY-2 Radars and the associated equipment. The Contractor shall provide integration and management support for the deployment, site facilities planning, operation and sustainment of radar systems, facilities, and support equipment. The Contractor shall provide overall management to all or a part of the Contractor Logistics Support (CLS) Program to meet the Government’s operational, sustainment, development, and test objectives. This effort shall consist of: AN/TPY-2 Radar Operations and Maintenance support requirement at multiple sites Provide sustainment team members capable of diagnosing and maintain radar hardware and software Provide Warfighter Training at CONUS and OCONUS sites. Training will require preparation of material and instruction to soldiers and contractors at each location as needed. Provide Software and Hardware Maintenance as primary maintainer for all levels of maintenance. AN/TPY-2 Radar Logistics Support Permanently deployed site support team at OCONUS locations Deployable site support team at CONUS Locations Line Replaceable Unit (LRU) Repair and Return 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 THAAD radars) AN/TPY-2 Sustaining and 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 Instructions for Submissions: No later than the 60 calendar days from the release date of this RFI, respondents are invited to prepare and submit responses (Classified information is not requested in responses). Respondents can submit a response for any of the three requirements areas (1-Test, 2-M&S, or 3-CLS). Each response should cover only one requirement area and include the following: Executive Summary (not to exceed 5 pages or slides) that includes: The major requirement area to which the response applies. Indication if the respondent possesses a facility clearance and to what level. Descriptive Data: Company Name Point of Contact Address Telephone and Fax Numbers E-mail Address DUNS Number CAGE Code and/or Tax ID Number Business Size Standard and applicable North American Industry Classification System (NAICS) codes Specifically what if any Government furnished technical data, computer software, computer software documentation, programmatic or operational information is necessary to perform the requirement. List and describe this data (does not count toward page limit for Executive Summary). Any small business contractor responding to this RFI should include past experience in managing subcontractors on similar requirements and, if applicable, include subcontractor or teaming partners’ experience applicable to requirements specified in this RFI. Small businesses planning teaming arrangements to meet the support requirements listed above should 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 should 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. White paper (not to exceed 10 pages) that discusses respondent’s capabilities, associated risks (to include any submissions that specifies the need for Government furnished technical data, computer software, computer software documentation, programmatic, operational information, etc. that would be necessary to execute the requirement), and mitigation strategies to support the requirement area identified in the Executive Summary. Each white paper should clearly identify which requirement area is being discussed. Note: As appropriate for the requirement area, risk mitigation strategies should address but are not limited to: Development of tactically aligned MDS sensor (SBX, AN/TPY-2, LRDR, UEWR, and CD) models. Execution of test and analysis for both flight and ground test by X-Band, S-Band, and UHF/L-Band Radars. Mitigation of any learning curve impacts (trained personnel, maintenance, and situational awareness, etc.). Lack of knowledge of radar software development in the analysis of radar test performance and modeling and simulation development and how this risk will be mitigated. Execution of overall management to all or a part of the Contractor Logistics Support (CLS) Program to meet the Government’s operational, sustainment, development, and test objectives. A capability brief discussing (not to exceed 15 slides) the respondent’s capabilities to perform the requirement area identified in the Executive Summary and relevant experience. Each brief should clearly identify which requirement area is being discussed. The brief should include: A capability statement explaining why the respondent believes it is a responsible source. A schedule estimate highlighting initial capability delivery/availability. If your response addresses a subset of the requirement area identified in the Executive Summary versus the entire requirement, address how any seams/gaps would be mitigated. If applicable, a description of any experience with MDA Mission Assurance Provisions (MAP) and Parts, Materials and Processes (PMP) compliance. If applicable, identification of any software Capability Maturity Model Integration (CMMI) designations. If responding as a team, describe the team’s probable membership, organization, and approach. Contracting Office Address: Missile Defense Agency, MDA-DACX Redstone Arsenal, AL, 35898, UNITED STATES Point of Contact(s): Khaliah Burns, Procuring Contracting Officer, Ground Sensors Email: [email protected] Approved for Public Release 21-MDA-10848 (4 Jun 21)