Multi-sensor and Acoustic Contact Localization through Artificial Intelligence/Machine Learning

Navy SBIR 25.1- Topic N251-047
Naval Sea Systems Command (NAVSEA)
Pre-release 12/4/24   Opens to accept proposals 1/8/25   Closes 2/5/25 12:00pm ET    [ View Q&A ]

N251-047 TITLE: Multi-sensor and Acoustic Contact Localization through Artificial Intelligence/Machine Learning

OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Trusted AI and Autonomy

The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with the Announcement. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.

OBJECTIVE: Develop a technology that can localize maritime entities from passive sensor contact information using artificial intelligence or machine learning (AI/ML) algorithms.

DESCRIPTION: Modern submarines are fitted with numerous arrays with the intent of minimizing blind spots. However, the parameters associated with these disparate arrays makes it difficult to create a unified picture, particularly where entities are detected by multiple sensor arrays. Submarines and other undersea warfare systems use passive sensor information to develop track information (bearing, range, course and speed vs. time) of maritime entities. It does so by leveraging multiple separate algorithms and observations of changes in the dynamics of acoustic sensor data such as signal arrival angle at the sensor array, Doppler shift, and data from spatially separated arrays. Often the submarine will maneuver to drive changes in how the entity appears to the sensor to enable Target Motion Analysis (TMA). The sensor data feeds various algorithms that suggest the proper 4-state solution (bearing, range, course, and speed) for entity location and velocity. The quality of the solution depends on the completeness and accuracy of the data fed into the algorithms and how the submarine maneuvers.

Several of the acoustic arrays that submarines rely on are towed, with estimated shape and position used when computing entity positions.

The operator typically cycles between multiple separate solution development and evaluation tools to arrive at candidate contact track solutions. This process becomes increasingly inaccurate as the incoming information becomes more complex, as might occur with noisy, sparse, or weak contact signals or when a large number of contacts must be managed. Advances in solution accuracy have been achieved through refining the operator machine interface to support efficient operator workflow based on the current paradigm of cycling through multiple algorithm-generated displays to assess validity of multiple hypothetical track solutions.

The Navy seeks to shift to an integrated technology for simultaneously evaluating all available information for localizing maritime entities. A solution for obtaining this shift is not commercially available.

AI/ML algorithms for U.S. Navy Undersea Warfare sensors have been used to assist in detection and classification of signals within the current cyclic process. This SBIR topic seeks to migrate to AI/ML technology where detection information such as operator-promoted contact followers are used to achieve rapid and accurate localization of individual maritime entities in support of a holistic tactical contact picture. The tool developed will need to demonstrate an ability to develop contact track solutions using all promoted sensor data and associated environmental propagation information as measured by estimated 4-state solution (bearing, range, course, and speed) when compared to the true track.

In addition to producing rapid estimates of contact position and speed, the desired AI/ML technology should also be able to provide refined array shape and position estimates in real time, rather than relying on predicted shape and position using high-level parameters such as platform speed and tow cable scope.

The technology architecture must be extensible to multiple arrays and array types as well as contact follower data from multiple vehicles. It must use data that is diverse and representative of real world acoustic data. The data should be representative of both hull mounted and line array configurations. It is desirable for the technology to provide a confidence value in addition to track solution estimates. The solution will provide novel visualization tools or processes that suggest track solutions, the quality of constituent data sources, and instances where operator-specified information (e.g., propagation paths) do not make sense in light of the larger sets of data considered by the AI/ML technology.

Work produced in Phase II may become classified. Note: The prospective contractor(s) must be U.S. owned and operated with no foreign influence as defined by 32 U.S.C. § 2004.20 et seq., National Industrial Security Program Executive Agent and Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Counterintelligence and Security Agency (DCSA) formerly Defense Security Service (DSS). The selected contractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances. This will allow contractor personnel to perform on advanced phases of this project as set forth by DCSA and NAVSEA in order to gain access to classified information pertaining to the national defense of the United States and its allies; this will be an inherent requirement. The selected company will be required to safeguard classified material during the advanced phases of this contract IAW the National Industrial Security Program Operating Manual (NISPOM), which can be found at Title 32, Part 2004.20 of the Code of Federal Regulations.

PHASE I: Develop a concept for an AI/ML TMA tool that meets the parameters of the Description and demonstrates the feasibility of the concept using unclassified data obtained or created by the awardee and that is clearly extensible to the acoustic data use case. Show feasibility through analysis, modelling, simulation, and testing. The Phase I Option, if exercised, will include the initial design specifications and capabilities description to build a prototype solution in Phase II.

PHASE II: Develop and deliver a prototype AI/ML TMA tool with architecture and methodology for incorporating the capability into submarine sonar contact management. Demonstrate that the prototype meets the required range of desired performance attributes given in the Description. System performance will be demonstrated through installation and prototype testing on a testbed with the lead system integrator provided by the government.

It is probable that the work under this effort will be classified under Phase II (see Description section for details).

PHASE III DUAL USE APPLICATIONS: Support the Navy in transitioning the technology to Navy use in Anti-Submarine Warfare (ASW). Demonstrate and report on performance during laboratory testing. The prototype will be integrated into ASW combat systems for which IWS 5.0 develops updates, which include the AN/SQQ-89, AN/BQQ-10, and AN/BYG-1 systems.

The technology can be extended to any passive sensor, including non-acoustic sensors. This technology can be used in a wide range of complex systems of systems where AI/ML is used to characterize operator proficiency and just-in-time performance assistance is crucial to mission performance. The technology would be of greatest use in complex safety-critical systems where mistakes carry disproportionate risk of mission failure.

REFERENCES:

1. Shahbazian, Reze et al. "Machine Learning Assist IoT Localization: A Review of Current Challenges and Future Trends." Sensors 2023, 23(7), 3551. https://www.mdpi.com/1424-8220/23/7/3551

2. "AN/BQQ-10 Acoustic Rapid Commercial Off-the-Shelf Insertion (A-RCI) Sonar." FY16 Navy Programs. https://www.dote.osd.mil/Portals/97/pub/reports/FY2016/navy/2016arci.pdf?ver=2019-08-22-105302-370

3. "AN/SQQ-89(V) Undersea Warfare / Anti-Submarine Warfare Combat System." Navy Fact File, last updated 20 Sep 2021. https://www.navy.mil/Resources/Fact-Files/Display-FactFiles/Article/2166784/ansqq-89v-undersea-warfare-anti-submarine-warfare-combat-system/

4. "National Industrial Security Program Executive Agent and Operating Manual (NISP), 32 U.S.C. § 2004.20 et seq. (1993)." https://www.ecfr.gov/current/title-32/subtitle-B/chapter-XX/part-2004

KEYWORDS: Artificial intelligence or machine learning (AI/ML); acoustic sensor data; undersea warfare systems; data that is diverse and representative; Target Motion Analysis (TMA); Holistic Tactical Contact Picture


** TOPIC NOTICE **

The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoD 25.1 SBIR BAA. Please see the official DoD Topic website at www.dodsbirsttr.mil/submissions/solicitation-documents/active-solicitations for any updates.

The DoD issued its Navy 25.1 SBIR Topics pre-release on December 4, 2024 which opens to receive proposals on January 8, 2025, and closes February 5, 2025 (12:00pm ET).

Direct Contact with Topic Authors: During the pre-release period (December 4, 2024, through January 7, 2025) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. Once DoD begins accepting proposals on January 8, 2025 no further direct contact between proposers and topic authors is allowed unless the Topic Author is responding to a question submitted during the Pre-release period.

DoD On-line Q&A System: After the pre-release period, until January 22, at 12:00 PM ET, proposers may submit written questions through the DoD On-line Topic Q&A at https://www.dodsbirsttr.mil/submissions/login/ by logging in and following instructions. In the Topic Q&A system, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing.

DoD Topics Search Tool: Visit the DoD Topic Search Tool at www.dodsbirsttr.mil/topics-app/ to find topics by keyword across all DoD Components participating in this BAA.

Help: If you have general questions about the DoD SBIR program, please contact the DoD SBIR Help Desk via email at [email protected]

Topic Q & A

1/5/25  Q.
  1. What specific types and formats of sensor data are expected to be used for developing and testing the AI/ML tool? Will government-provided datasets include both hull-mounted and towed array configurations?
  2. Should the tool integrate directly with specific submarine sonar systems like AN/SQQ-89 or AN/BQQ-10? Are there existing interfaces or standards the tool must adhere to?
  3. What level of real-time processing is expected for contact localization and array shape estimation? Should the tool prioritize speed, accuracy, or a balance of both?
  4. What is the desired level of detail for the confidence values provided by the AI/ML system? Should these include visualizations or explanations for operators?
  5. Are there specific requirements for the visualization tools? For instance, should they highlight data quality issues, inconsistencies, or provide decision-making recommendations?
  6. To what extent should the architecture be designed to accommodate future sensors or data types beyond acoustic arrays, such as non-acoustic or multi-vehicle systems?
  7. Are there particular commercial or non-military applications (e.g., environmental monitoring, maritime logistics) that should influence the tool’s design or features?
   A.
  1. The Phase I will be unclassified. The government expects the company to propose data that will support powerful demonstration of the technology feasibility during the Phase I base. The topic already contains information regarding the nature of sensors that could be tapped, which include hull mounted arrays, towed arrays, and off board sources, such as proximate unmanned vehicles. As the topic mentions, the framework should be extensible to multi-platform contact localization.
  2. If successful, the prototype developed under this topic will be integrated into a Navy sonar system. However, it is not necessary for specific interfaces and standards to be a concern of the Phase I research.
  3. As it will not be possible to determine the correct balance prior to Phase II, the government suggests companies develop technologies that can be successful across a relatively wide range of speed/accuracy tradeoffs.
  4. The GUI associated with the technology will be refined during Phase II in cooperation with the Navy’s ASW Operator/Machine Interface Working Group. Operators will need to generate confidence in the tool, so it is recommended that the initial planned prototype recommend association of contacts across arrays, with the option to soft-fuse contacts for a subsequent integration (with the term “soft-fuse” intended to imply that the fusion could take place unless interrupted by an operator).
  5. For Phase I, the government looks to the company to provide suggestions for association visualization. Upon selection for Phase II, when there is no longer a competitive selection environment, the government will provide more granular guidance regarding desired information for the Phase II prototype.
  6. It is desired that the framework/architecture be extensible to foreseeable sensors and platform configurations, as described in the topic.
  7. The government is delighted to understand the company’s vision for how the technology they plan to develop can be used for purposes that will improve US Government or US commercial capabilities beyond the Navy’s intended transition. As the government does not know the full range of innovations that companies will propose, it is not possible to specify which non-military functionalities or enhancements would be possible.


[ Return ]