Inactive

04/11/2022 - The Government updated the response date from 04/20/2022 to 05/11/2022. This notice is a Request for Information (RFI) as defined in FAR 15.201(e). The Naval Sea Systems Command (NAVSEA) ... 04/11/2022 - The Government updated the response date from 04/20/2022 to 05/11/2022. This notice is a Request for Information (RFI) as defined in FAR 15.201(e). The Naval Sea Systems Command (NAVSEA) is conducting market research for the Navigation Systems Engineering Agent (NSEA) requirement. The US Navy leverages a variety of navigation solutions that allow vessels to navigate safely with and without GPS. The individual systems operate as disparate nodes on a dispersed network behind various enclaves. The US Navy is looking to modernize the approach to navigation, moving disparate systems within one enclave and virtualizing them over time. Below are some of the relevant systems: WSN-12 (Inertial Navigator) CDU (Control Display Unit) ACNS (Automated Celestial Navigation System) ECDIS (Electronic Charting Display and Information System) NCDS (Navigation Critical Distribution System) ANCHOR – Will serve as the cybersecurity layer for the enclave – to be developed DHYSL (Digital Hybrid Speed Log) AIAS (Aircraft Inertial Alignment System) The phased approach includes continued production of these and other navigation systems, while engineering a service based solution. This is being termed “Navigation as a Service” (NaaS). NaaS includes several elements listed below: Infrastructure as a Service (IaaS) - The resources required to provide the information to the customers Platform as a Service (PaaS) - The environment in which the capability and resources reside Software as a Service (SaaS) - The ability to de-couple applications from specific HW so that updates come without having to modify HW NaaS incorporates all of these into a single architecture that is integrated to exchange information within a flexible infrastructure that does not require major hardware changes To implement NaaS, the Navy plans to take a phased approach: Build to Print – This involves the continued production of Navigation assets. This is essentially the as-is state. Initial State – The initial systems that will live on common hardware include WSN-12, ANCHOR, ACNS, ECDIS. Relevant navigation sensor interfaces will be integrated into the initial NaaS solution. There will be interfaces to interact with other ship systems. Final State – All navigation equipment to include legacy systems are virtualized and live within the navigation enclave as part of NaaS. Interfaces to external ship systems and navigation sensors are part of the baseline. The US Navy will complete installation of NaaS assets. The US Navy will look for third-party support for lifecycle sustainment efforts such as configuration management, software sustainment, and logistics. US Navy and commercial enterprises leverage a variety of navigation solutions that allow vessels to safely navigate with and without GPS. The US Navy is looking to modernize legacy systems over time. This RFI seeks information on prospective technologies that could be leveraged or developed as enablers for a NaaS solution. This RFI is interested in options that will allow the Navy to transition from the current state of disparate navigation solutions to a unified suite of solutions that all live within a secured enclave. Lastly, this RFI seeks to understand how interested parties would integrate the NaaS with navigation sensors and other ship equipment. Particular emphasis should be placed on affordability and technical readiness of a shipboard application for build to print beginning in FY 2023 and NaaS implementation in FY 2026-2027. NAVSEA invites all interested parties, including small business concerns, to submit written information sufficient to demonstrate the respondent's ability to fulfill the requirements. For those interested parties that have technologies which may not achieve a Technology Readiness Level (TRL) of 8-9 by FY 2025, please provide information on current research and development efforts that may address some or all requirements of this RFI beyond FY 2025. The Navy is conducting market research to identify qualified and responsible sources that may be interested in the requirements described in this notice. This RFI is issued for informational and planning purposes only and does not constitute a solicitation or a Request for Quote (RFQ). This RFI is not to be construed as a commitment by the Government to issue a solicitation or award a contract. Responses should include one (virus scanned) copy sent via email to the points of contact listed in this notice, and must be received no later than May 11, 2022. Please ensure that the subject line of any emails containing responses or questions related to this notice includes the name of your firm and "Navigation Systems Engineering Agent" (without quotation marks). Include a cover page with the response that lists the following information: Solicitation number for this notice (N00024-22-R-5210) Company Name Mailing address and physical address (if different) DUNS number CAGE code Business size status (based on NAICS code 334511) Type of small business (if applicable) Name, position, email address, and phone number of point(s) of contact All information received bearing proprietary markings will be handled in accordance with applicable statutes and regulations and be limited in distribution to cognizant government agencies and to the program Technical Direction Agent. Responses to this notice will not be returned. 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 contacts listed in this notice. Interested parties submitting proposed solutions shall include the following in the RFI submission: How virtualization of Navigation technology will be achieved Anticipated development timeline How the solution will be phased over time Additional technologies that can be leveraged to support a robust Navigation solution Sensors supported (e.g. radars, EO/IR, AIS, etc.) Interfaces supported Projected cost drivers or potential major cost drivers Projected schedule drivers or potential major schedule drivers Identify relevant technology risk areas and any ongoing technology maturation initiatives currently under way. Request information concerning your ability at conducting and supporting the full-range of current Model Based Systems Engineering – Digital Engineering (MBSE-DE) features to consider in a CTR-GOVT partnership with a vision for balancing benefits of DE collaboration against additional costs and learning curve up-front and long-term. The ability to build Navigation systems based on government provided TDPs and other design specific documentation. NOTE: Please limit RFI responses to 15 pages or less, excluding the cover page, with 1-inch margins, and 10-point Times New Roman font or larger. This notice is not a request for proposals. Per FAR 15.201(e), responses to this notice do not constitute offers and cannot be accepted by the Government to form a binding contract. This notice is issued solely for information and planning purposes and does not constitute a solicitation or obligation on the part of the Government. The Government makes no representations that a solicitation for the requirements described in this notice will be issued. Respondents are wholly responsible for any costs or expenses associated with submitting a response. No reimbursement will be made for any costs associated with providing information in response to this notice or any further requests for information relating to a response. Respondents will not be notified of the results of this notice. The information obtained from submitted responses may be used by the Government in the development of a procurement strategy. Information submitted in response to this notice will become the property of the United States Government. Respondents should properly mark any materials submitted with the appropriate restrictive markings. Information that is proprietary or competition-sensitive may be protected from disclosure under the public records statutes only if properly labeled as such.