Missile Defense Agency (MDA), Ground Sensors, Modeling and Simulation Request for Information

Missile Defense Agency (MDA) Ground Sensors (SN) Modeling and Simulation (M&S) Requirements Request for Information Agency: Other Defense Agency Office: Missile Defense Agency Location: MDA-SNA Reference-Number: MDA22SNRFI03 NAICS: 541330 DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Approved for Public Release 22-MDA-11280 (6 Oct 22) 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). 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 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. 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. Market Research is the process of collecting and analyzing information about capabilities within the market to satisfy agency needs (FAR 2.101) Future requirements may include: Modeling and Simulation (M&S) requirements to include development, enhancement, modification, and sustainment of tactically-aligned digital end-to-end radar models and Hardware-in-the-Loop (HWIL) radar drivers to accurately simulate and/or stimulate MDS tactical radars, including existing and new radar capabilities as they are developed. The digital models and HWIL radar drivers must be delivered with required capability that can be validated and accredited for use. The digital models and HWIL drivers support radar development and assessment, as well as capability development of C2BMC and GMD. Due to the increasing pace of evolving threats and missile defense capability development, there are increased stakeholder needs for early radar representations and drivers that are aligned to tactical radar software releases. This has led to new M&S requirements to develop the digital radar models and HWIL radar drivers as part of the agile radar development cycle to closely coordinate with radar development efforts. This Request for Information (RFI) is issued solely for information and planning purposes - it does not constitute a Request for Proposal (RFP) or a 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. The information provided may be used in developing an Acquisition Strategy, Statements of Work, Statements of Objectives, or Performance Work Statements. 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. It is the responsibility of the potential respondents to monitor this site for additional information pertaining to this requirement. 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., use an attachment or exhibit). Respondents are responsible for adequately marking proprietary information contained in their response. Do not send any classified information. 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. M&S Requirements Description: MDA ground sensors (SBX, AN/TPY-2, LRDR, UEWR, and CD). (Anticipated NAICS / PSCs: 541330 / AC13 and 5840) 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 drivers for MDA ground sensors. Digital radar models and HWIL drivers should accurately simulate and/or stimulate MDA tactical radars, 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. 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 on the same timeline as radar software releases, to include radar software engineering releases and formal releases. Therefore, a new M&S requirement is that 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). 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, a new M&S requirement is that 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. 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), CI/CAT, Opportunistic Test Special Studies Live and HWIL events for data collection to support radar fielding decisions Instructions for Submissions: No later than 28 October 2022, respondents are invited to prepare and submit the following (Classified information is not requested in responses): Executive Summary (not to exceed 5 pages or slides), that includes: 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 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 and mitigation strategies to support the requirements identified in the Executive Summary. Note: 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 on the timeline required Mitigation of any learning curve impacts 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. The brief should include: A schedule estimate highlighting initial capability delivery/availability. If applicable, a description of any experience with MDA Mission Assurance Provisions (MAP) and Parts, Materials and Processes (PMP) compliance. 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-SNK Building 5222, Martin Rd Attn: VBIII, Redstone Arsenal, AL, 35898 Point of Contact(s): Khaliah Burns, Procuring Contracting Officer, Ground Sensors Contracts Email: khaliah.burns@mda.mil Approved for Public Release 22-MDA-11280 (6 Oct 22)