N241-037 TITLE: Weapons Scheduling for Uncertain Weapon-Target Assignment
OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Advanced Computing and Software
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 an automated capability for the Ship Self-Defense System (SSDS) that maximizes weapon scheduling effectiveness where explicit weapon-target assignment solutions are not possible.
DESCRIPTION: Current US Naval platforms use a variety of onboard sensors, communications networks, data processing systems, weapons, and other components organized into a combat system to detect, track, and classify inbound targets, determine how to best employ weapons and countermeasures to defeat those targets, and then use those weapons and countermeasures to maximum effect. This involves explicit selection, scheduling, and assignment of self-defense weapons to inbound targets to achieve an optimal defensive solution, often across multiple layers of weapons in range (i.e., "depth of fire"). This process uses a variety of factors to make explicit weapon-target assignments (WTA) and schedule engagements against incoming targets, including but not limited to: assessments of target attributes, the number of detected targets, the number of defensive weapons in inventory, doctrine describing how and when particular weapons are used, and other factors. Furthermore, engagement schedules are "dynamic, changing as new sensor data are provided, additional targets are disclosed, and initially scheduled engagements are executed" [Ref 1]. This is a challenging and complex process.
Due to the ever-shifting landscape posed by our adversaries, future Naval combat systems must be resilient to scenarios in which generating engagement schedules with explicit WTA approaches are not tenable and no current solution is available. The Navy therefore seeks an automated capability that generates engagement schedules enabling incoming target raid annihilation in the face of uncertainty regarding the number of inbound targets, the physical location and position of targets, knowledge of expected inbound target behavior during terminal homing phases, inferred target identity, and other characteristics occurring during off-axis, massed and/or swarm attacks [Refs 2, 3]. Proposals using machine learning approaches will also be considered, but candidate solutions must be capable of generating schedules against completely novel, never-before-seen threats and raid conditions, and in scenarios for which training data for use in ML-focused solutions cannot be provided. Solutions must reside inside and support integration into the SSDS combat management system (CMS) (that is, algorithms should not be targeted for integration into weapons or sensors), but must use data (e.g., radar track and state data, sensor data, and others) that are common to other CMSs. Furthermore, the solution should consider the potential complexities introduced by distinctions between CMS-provided WTA, and WTA approaches decided by defensive interceptors themselves as they near their targets [Ref 4]. Finally, the solution must be compatible with current combat system operational characteristics and constituent components (that is, solutions cannot depend on integrating new weapons and/or sensors into the combat system) [Ref 1]. The solution used to demonstrate proposed methods and/or algorithms for scheduling under WTA uncertainty should be demonstrated under low- to medium-fidelity modeling and simulation approaches. Simulation and analysis results should be presented in the form of scenario descriptions, Red and Blue force asset laydown(s), and engagement timelines using synthetic yet realistic engagement events, parameters, and data. The inner workings of proposed algorithmic approaches must be explainable.
Three SSDS Top Level Requirements (TLRs) would be supported by this investigation. These TLRs will be provided by the government to the awardee. These requirements are:
• The SSDS CS shall determine, recommend and apply weapons tactics to include firing policy, salvo size, and salvo spacing [SSDS_CS_TLR-1571];
• The SSDS CS shall reevaluate and rebuild HK and SK schedules periodically, as well as when certain events occur that can change target and resource status [SSDS_CS_TLR-1674]; and
• The SSDS CS shall consider the effects of multiple targets in the weapon's field of view on weapon performance when building the engagement schedule [SSDS_CS_TLR-1684].
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. Reference: 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
PHASE I: Develop a concept for a capability to generate SSDS engagement schedules that enables incoming target raid annihilation without using explicit weapon-target assignment approaches. Demonstrate the feasibility of the concept to meet the conditions outlined in the Description section through modeling, simulation, and analysis. 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 an engagement scheduling system prototype capable of meeting realistic engagement and operational requirements based on the results of Phase I. Demonstrate at a Government- or company-provided facility that the prototype meets all parameters detailed in the Description. The technology will be assessed by Navy subject matter experts.
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. The technology will go through system integration and qualification testing for the prototype engagement scheduling approach developed in Phase II. This prototype will be delivered to support the Navy through a critical experiment conducted jointly by the awardee and combat system engineering agent (CSEA). This is expected to take place in a live environment with tactical SSDS CMS software. Integrate the prototype into the SSDS CMS.
Dual use applications to consider include commercial resource management, delivery, and scheduling challenges that are particularly vulnerable to uncertainty that is difficult to deterministically quantify and/or changes over time.
KEYWORDS: Operational characteristics; WTA uncertainty; weapon-target assignment; schedule optimization; stochastic optimization; weapons and countermeasures
** TOPIC NOTICE **
The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoD 24.1 SBIR BAA. Please see the official DoD Topic website at www.defensesbirsttr.mil/SBIR-STTR/Opportunities/#announcements for any updates.
The DoD issued its Navy 24.1 SBIR Topics pre-release on November 28, 2023 which opens to receive proposals on January 3, 2024, and now closes February 21, (12:00pm ET).
Direct Contact with Topic Authors: During the pre-release period (November 28, 2023 through January 2, 2024) 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 3, 2024 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.
SITIS Q&A System: After the pre-release period, until January 24, 2023, at 12:00 PM ET, proposers may submit written questions through SITIS (SBIR/STTR Interactive Topic Information System) at www.dodsbirsttr.mil/topics-app/ by logging in and following instructions. In SITIS, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing.
Topics Search Engine: 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.
|We could not locate some of the references. Is there any more information on the references for #2 (Kline, A.), #4 (Ahmadi, M.), #5 (Ono, M.) or #6 (Ingraham, M.)? Thanks.
|It appears there is an error with the number formatting for the references here for the posting of the topic on the DSIP Topic Q&A. The correct listing of references can be found in the official posting of the topic within the BAA. We apologize for any confusion. We will also list here: