ESSM Open-Source Modeling and Simulation Sources Sought.docx

DOCX document 554 KB Posted

Attached to
Evolved SEASPARROW Missile (ESSM) Open-Source Modeling and Simulation (M&S) Sources Sought
Solicitation number
N00024-25-R-5430
Issued by

About this file

This document is a Sources Sought Request for Information (RFI) from the Naval Sea Systems Command (NAVSEA) for the NATO SEASPARROW Project Office (NSPO). The agency is seeking open-source Modeling and Simulation (M&S) tools for the Evolved SEASPARROW Missile (ESSM) system, with specific requirements including integration with SysML v2 missile system models, missile system performance analysis, hardware/software change impact assessment, and the ability to run digital simulations of missile and kill chain performance.

Interested parties must submit a 10-page Capabilities Statement by July 14, 2025, to Megan Galloway and Allie Mullin via email. The response must detail the company's capabilities in developing M&S tools, including technical abilities, past performance, export regulation compliance, development timeline, and specific technical capabilities such as simulating missile kinematics, aerodynamics, seeker technologies, and target environments. The RFI is for market research purposes only, with no guaranteed procurement, and is open to large and small businesses across the 12-nation NATO SEASPARROW consortium, including Australia, Belgium, Canada, Denmark, Germany, Greece, Netherlands, Norway, Portugal, Spain, and Turkiye.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Evolved SEASPARROW Missile (ESSM) Open Source Modeling and Simulation (M&S) Sources Sought Department/Ind. Agency:

DEPT OF DEFENSE DEPT OF NAVY

PROGRAM EXECUTIVE OFFICER, INTEGRATED WARFARE SYSTEMS PROGRAM EXECUTIVE OFFICER, INTEGRATED WARFARE SYSTEMS, 12.0 Background/Program Details:

The NATO SEASPARROW Project Office (NSPO), PEO IWS 12.0, is seeking a suite of Open Source Modeling and Simulation tools that can integrate within the SysML v2 missile system model and provide: missile system performance analysis with limited to no use of custom application plug-ins (APIs), the ability to assess impact of missile hardware and software changes on performance, and the flexibility to run all digital low-to-high fidelity simulations of both end-to-end missile and full kill chain performance. The ability of these software tools to interface with full hardware-in-the-loop (HiL) and hybrid simulations is also of interest. This integrated M&S suite aims to enhance the efficiency, flexibility, and effectiveness of future ESSM development. Figure 1 is an example of what an open-source M&S suite would encompass for a missile system.

NSPO is a twelve nation international consortium with a mission to provide a platform for international cooperation and innovation to manage the development, production, integration, and sustainment of effective, reliable, and affordable weapon systems to protect consortium and partner nation forces from current and future threats. More information on the NATO SEASPARROW Surface Missile System Project can be found at this link; https://www.natoseasparrow.org/.

Figure 1: Distribution Statement A. approved for public release: distribution is unlimited. Example Operational View

1. SYNOPSIS

THIS SPECIAL NOTICE IS AN ADVANCED NOTICE FOR INFORMATION, MARKET RESEARCH, AND PLANNING PURPOSES ONLY. THIS IS NOT A REQUEST FOR PROPOSAL (RFP). THERE WILL NOT BE A SOLICITATION AVAILABLE AT THIS TIME. THIS ANNOUNCEMENT IS FOR THE PURPOSE OF MARKET RESEARCH ONLY AND MAY OR MAY NOT TRANSLATE INTO AN ACTUAL PROCUREMENT. THERE IS NO FUNDING ASSOCIATED WITH THIS ANNOUNCEMENT.

The Naval Sea Systems Command (NAVSEA), NATO Seasparrow Project Office is conducting market research to assess opportunities to develop and produce an Open-Source Modeling and Simulation tool that meets the restrictions and provides the capabilities listed below.

The Capabilities Statement should describe the company's demonstrated capabilities and experience with designing, integrating, testing and/or producing open-source modeling and simulation tools. Failure to provide a response does not preclude participation in any possible future RFP, if issued.

2. RESPONSE REQUIREMENTS

2.1 General. ALL RESPONSES MUST BE UNCLASSIFIED. Interested parties shaII submit, on company letterhead, one Capabilities Statement including the name, telephone number, mailing address, and email address of one point of contact. Please send the Capabilities Statement via email to the Contracting Officer, Megan Galloway, at Megan.e.galloway2.civ@us.navy.mil and Contract Specialist, Allie Mullin, at alexandra.j.mullin.civ@us.navy.mil with N00024-25-R-5430 Sources Sought in the subject field.

2.2 Page Format. Responses shall be submitted in Microsoft Word or Adobe Acrobat Portable Document Format (PDF) format and reference: N00024-25-R-5430 Sources Sought. Page size must be 8.5 x 11 inches. The top, bottom, and side margins must be at least 1 inch. Pages must be numbered sequentially. The text must be no less than 12 points and use Times New Roman font.

2.3 Page Limitations. The Capabilities Statement shall not exceed 10 single-sided pages. Each page must be counted except for the following:

· Cover Page

· Company Information

· Company Size and Status

2.4 Organization & Content. Responses shall be organized into the following sections with the following information:

A. Introduction - Provide a brief company introduction and relevant details of the company/organization, including any potential teaming approach. Additionally, interested parties shall identify if their company has the capability to be a prime contractor or if it is only interested in subcontracting opportunities. Ensure responses include the following information:

a. Company name

b. Company primary and alternate points of contact (title, email and phone)

c. Company address

d. DUNS Number / SAM ID

e. CAGE code

f. Business size

g. Status B. Capabilities - Succinctly address the contractor's ability to manage the types and magnitude of tasking, technical ability to perform the task, and the capacity to conduct the requirements of the task.

C. Experience - This section should include specific demonstrated capabilities, knowledge, and experience for each capability. Identify any demonstrated expertise and experience that can be directly applied to the development and evaluation of military combat system capabilities. Identify any past experience working with the Navy Marine Corps Intranet (NMCI) system. Detail the applicable Modeling and Simulation (M&S) Verification, Validation, and Accreditation (VV&A) history as well as any VV&A efforts currently underway. Please provide examples of relevant and recent (within three years before the date of this RFI posting) past performance of all topics in this section. Please include contracts and Government sponsor points of contact where the experience described was completed.

D. State whether you can comply with export restrictions that may apply to your chosen technical data and/or technologies (in particular, International Traffic in Arms Regulations (ITAR) and Export Administration Regulations (EAR), and how you will comply with any U.S. domestic sourcing restrictions such as the Buy American Act and the DFARS clause 232.225.7007 Prohibition on Acquisition of Certain Items from Communist Chinese Military Companies. If a non-U.S. source, state how you will contend with export to all of the 11 consortium nations, including; Australia, Belgium, Canada, Denmark, Germany, Greece, Netherlands, Norway, Portugal, Spain, and Türkiye.

E. State whether you will be the actual producer of this item, or if you intend to subcontract all or a portion of the requirement. If you are not the actual producer, indicate what development operations you intend to subcontract.

F. A description of the Rough Order of Magnitude (cost) for designing and building a model that meets the system capabilities, including expected lifecycle costs.

a. Projected or potential major cost drivers and mitigations to control costs in design and development.

G. Provide a notional anticipated development timeline to achieve a missile model.

H. Established facility clearance up to SECRET and current COMSEC accounts.

a. Demonstrate that the company has adequate program personnel with United States SECRET security clearances.

I. Provide details on Open-Source Modeling and Simulation tools to include but not limited to:

a. Ability to simulate missile kinematics, aerodynamics, and structural mechanics.

b. Ability to simulate missile software logic.

c. Ability to simulate radio frequency and infrared missile seekers.

d. Ability to simulate target detection and warhead lethality.

e. Ability to simulate radio frequency target environment.

f. Ability to simulate infrared target environment.

g. Ability to interface with SysML v2 system models with limited to no use of custom APIs.

h. Ability to assess impact of missile hardware and software changes on performance.

i. Ability to interface with full hardware-in-the-loop (HiL) and hybrid simulations.

j. Ability to interface with other M&S tools

k. Relative fidelity of tools in their respective areas of the simulations for both end-to-end missile and full kill chain performance.

2.5 Data Right Assertions: The government anticipates that the source for the development of all the technical data, training material and software deliverables, including all components of same, would-be Government funded under a contract effort, with the result that the Government will receive unlimited rights in all such deliverables. If to be delivered with less than unlimited rights, please identify every deliverable or every component of every deliverable, that will be delivered with a restriction on the Government’s rights; for this request for information, please follow the procedure and format for Assertions of Restrictions in DFARS 252.227-7017, which the government will consider to be a notional Assertion. Indicate in this notional Assertion any uncertain entries, and the basis of that uncertainty, that might change in a formal Assertion if a contract were awarded to the respondent. For any software deliverable or deliverable component, identify any portions of software that come from existing commercial software or from open-source software.

2.6 Classification. INTERESTED PARTIES MUST ENSURE RESPONSES ARE APPROPRIATELY UNCLASSIFIED.

2.7 Business Size. Large business concerns and all small business concerns are highly encouraged to respond

2.8 Deadline. Interested parties shall submit one electronic response via email by 17:00 (11 weeks after posting) Washington, DC local time, Eastern Time (ET) on 14 JUL 2025 to the Contracting Officer, Megan Galloway, at Megan.e.galloway2.civ@us.navy.mil and Contract Specialist, Allie Mullin, at alexandra.j.mullin.civ@us.navy.mil.

3. DISCLAIMER

THIS REQUEST FOR INFORMATION (RFI), AS DEFINED IN FAR 15.201(e), IS SOLELY FOR INFORMATIONAL AND PLANNING PURPOSES ONLY AND SHALL NOT BE CONSTRUED AS A REQUEST FOR PROPOSAL, REQUEST FOR QUOTE (or any type of solicitation), OR AS AN OBLIGATION OR COMMITMENT ON THE PART OF THE GOVERNMENT TO CONTRACT FOR ANY SUPPLY OR SERVICE, or as a promise to issue a solicitation in the future. THERE WILL NOT BE A SOLICITATION, SPECIFICATIONS, OR DRAWINGS AVAILABLE. THIS ANNOUNCEMENT MAY OR MAY NOT TRANSLATE INTO AN ACTUAL PROCUREMENT(S) IN FUTURE YEARS. THERE IS NO FUNDING ASSOCIATED WITH THIS ANNOUNCEMENT. IN ACCORDANCE WITH FAR 15.201(e) RESPONSES TO THIS NOTICE ARE NOT OFFERS AND CANNOT BE ACCEPTED BY THE GOVERNMENT TO FORM A BINDING CONTRACT. THE GOVERNMENT IS NOT AT THIS TIME SEEKING PROPOSALS AND WILL NOT ACCEPT UNSOLICITED PROPOSALS. RESPONDENTS ARE ADVISED THAT THE GOVERNMENT WILL NOT PAY FOR ANY INFORMATION OR ADMINISTRATIVE COSTS INCURRED IN RESPONSE TO THIS RFI; ALL COSTS ASSOCIATED WITH RESPONSDING TO THIS RFI WILL BE SOLELY AT THE RESPONDENTS EXPENSE.

Failure to respond to this RFI itself does not preclude participation in response to any future solicitation, if any is issued. If a solicitation is issued, it will be synopsized on the System for Award Management website at SAM.gov. The information provided in this RFI is subject to change and is not binding on the Government. It is the responsibility of potential respondents to monitor these sites for additional information pertaining to this requirement. The information requested by this RFI will be used within the U.S. Navy/Department of the Navy to facilitate decision making and may be used in the development of the acquisition strategy and any future solicitations. Any information provided by industry to the Government as a result of this RFI is voluntary. Other requests for information contained in this RFI shall be referred to NAVSEA 02 – Contracting Officer, Megan Galloway (Megan.e.galloway2.civ@us.navy.mil) and Contract Specialist, Allie Mullin (Alexandra.J.Mullin.Civ@US.Navy.mil).

Proprietary information, if any, must be clearly marked. To aid the Government in its review and evaluation, please segregate proprietary information and label it as such page-by-page and paragraph- by-paragraph for appropriate handling by the Government. Respondents are solely responsible for properly marking and clearly identifying any proprietary information or trade secrets contained within their response. All information received that includes proprietary markings will be handled in accordance with applicable statutes and regulations. An acknowledgement of receipt will be provided for all responses received. If you do not receive an acknowledgement within two working days, please notify the points of contact listed in this notice. Please be advised that all submissions become Government property and will not be returned. Respondents that include their submissions data that they do not want disclosed to the public for any purpose, or to be used by the Government except for RFI response consideration purposes, shall include in their submissions:

1) Mark the title page with the following legend: This response includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed – in whole or in part – for any purpose other than to consider this response. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]; and

2) Mark each sheet of data it wishes to restrict with the following legend: Use or disclosure of data contained in on this sheet is subject to the restriction on the title page of this submission.

All submitted materials will be designated for Government Use Only, which includes the U.S. Government and other governments that are affiliated with the NATO SEASPARROW PROJECT OFFICE; specifically: Australia, Belgium, Canada, Denmark, Germany, Greece, Netherlands, Norway, Portugal, Spain, and Türkiye. Any information submitted which is to be provided and reviewed by Government personnel only (including but not limited to U.S. Government personnel only), shall be clearly marked as such.

The Government shall not be liable for any consequential damages for proprietary information not properly identified. Proprietary information will be safeguarded in accordance with the applicable law.

image1.png

File details come from the government source that posted it. Updated .