N251-046 TITLE: Joint Track Manager Data Synchronization
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 innovative software algorithm that seamlessly interacts with the Joint Track Manager (JTM) to provide a consistent and reliable transmission and reception of tactical data link (TDL) messages for real time comparison of track databases.
DESCRIPTION: The Command and Decision (CND) element of the AEGIS Weapon System (AWS) consists of multiple track management applications working in conjunction to create and maintain source and system level track data for use by the overall AEGIS Combat System (ACS). These applications include, but are not limited to, Product Line Architecture (PLA) System Track Manager/Track Server (STM/TS), System Track Processor (STP), Link Interface Function (LIF), AN/SPY-1(6) Processing Functions (SPF/SPF6), and Cooperative Engagement Function (CEF). Combat system baseline configuration dictates which source managers are contained within a specific version of the AWS. While the STM implements a TS to store all Source and System level track data, each of the other source managers utilize local, internal track stores, maintained in parallel to the TS, while receiving and processing Source and System level track data. At times, these internal track stores can become out of synch with the TS, leading to the potential for a degraded state of track management functionality, and overall situational awareness. The Navy seeks an innovative software application that performs real-time monitoring of all link message types for interoperability to interface with CND and make corrections as necessary to keep them all in synch with the TS. This capability would ensure that the most accurate and up to date track data is available to the weapon system. This leads to increased situational awareness and decision-making abilities for the warfighter. This provides the Navy with a reduction in manning and maintenance costs. Currently there are no commercial solutions available to provide the synchronization needed.
This solution shall run in the background and not constrain the flow of track data between source and system level track management applications. The application will compare, at a minimum, track numbers, track identification/classification, and Identification Friend or Foe (IFF) modes and codes, with an objective to compare and synchronize all track attributes from incoming and outgoing link messages. The solution will benefit the Navy in improving product quality to ensure all track management subsystems are in synch and provide for the highest level of situational awareness in the Command and Control (C2) Track Management domain. The speed and accuracy of the solution must exceed existing ACS performance by 10% or better.
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 JTM data synchronization that meets the objectives stated in the Description. Demonstrate the feasibility of the concept in meeting the Navy’s need by any combination of analysis, modelling, and simulation. The Phase I Option, if exercised, will include the initial design specifications and capabilities description to build a prototype in Phase II.
PHASE II: Develop and deliver a prototype JTM data synchronization software application based on the results of Phase I. Demonstrate performance of the prototype in an existing Government-approved modeling and simulation environment. The demonstration will be conducted in a Government-provided facility. Analyze the accuracy of the software through assessment of the logic in mathematical algorithms developed to accurately represent a passive reporting capability approach to integrate into the Aegis Test Bed (ATB) environment. Deliver prototype software to the Navy along with complete test data, installation and operation instructions, and any auxiliary software and special hardware necessary to operate the prototype.
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 for government use. The prototype will be incorporated into the AEGIS baseline testing modernization process. This will consist of integration into a baseline definition, incorporation of the baselines existing and new threat capabilities, validation testing, and combat system certification.
STM/TS algorithms could provide assistance to air traffic controllers in monitoring potential collisions by increasing the accuracy and throughput of data.
REFERENCES:
1. Silberschatz, Avi; Korth, Hank and Sudarshan, S. "Database System Concepts: Seventh Edition." New York: McGraw-Hill Education, March 2019. https://www.bing.com/ck/a?!&&p=608a16eebb4be72aJmltdHM9MTcxMTkyOTYwMCZpZ3VpZD0zMTQyYzdiNS0xOGUxLTY3ZjAtMjBhMC1kM2UxMTk0YjY2YjYmaW5zaWQ9NTIyMA&ptn=3&ver=2&hsh=3&fclid=3142c7b5-18e1-67f0-20a0-d3e1194b66b6&psq=https%3a%2f%2fDatabase+System+Concepts+-+7th+edition+(db-book.com)&u=a1aHR0cHM6Ly93d3cuZGItYm9vay5jb20v&ntb=1
2. DPC CaP1 Tactical Datalink Capability Team. "Tactical Data Exchange - Link 16." STANAG 5516 Ed 4, 29 September 2008. https://www.bing.com/ck/a?!&&p=1a7296d1bca7e171JmltdHM9MTcxMTkyOTYwMCZpZ3VpZD0zMTQyYzdiNS0xOGUxLTY3ZjAtMjBhMC1kM2UxMTk0YjY2YjYmaW5zaWQ9NTE5OQ&ptn=3&ver=2&hsh=3&fclid=3142c7b5-18e1-67f0-20a0-d3e1194b66b6&psq=Link+16%3a+https%3a%2f%2fnisp.nw3.dk%2fstandard%2fnato-stanag5516ed4.html&u=a1aHR0cHM6Ly9uaXNwLm53My5kay9zdGFuZGFyZC9uYXRvLXN0YW5hZzU1MTZlZDQuaHRtbA&ntb=1
3. Campos, Luna "Data Synchronization: What It Is and How to Sync Data for Beginners." December 05, 2022. HTTPS://BLOG.HUBSPOT.COM/WEBSITE/DATA-SYNCHRONIZATION
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: Product Line Architecture (PLA); System Track Manager/Track Server (STM/TS); System Track Processor (STP); Link Interface Function (LIF); SPY Processing Function (SPF); Cooperative Engagement Function (CEF).
TPOC 1: Gerald Lawrence
(202) 781-0567
Email: [email protected]
TPOC 2: Richard Waters
(540) 653-641
Email: [email protected]
** 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.
|