N251-051 TITLE: Aegis System Track Manager/Track Server

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 software capability that ensures mismatches between internal track management components of the AEGIS Weapon System are identified and corrected in a real-time environment.

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). Track management is the process of utilizing all available sources of track data and supporting information, including on and off-board sensors and external communications systems, to create and maintain an accurate and consistent track picture, providing reliable Command and Control (C2) capabilities to the war fighter. Track management includes the processes of managing track numbers across disjointed track databases, maintaining track attributes such as, but not limited to, kinematic state, identification, classification, and Identification Friend or Foe (IFF) modes and codes, as well as providing for track data availability throughout the combat system. 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), SPY Processing Function (SPF), and Cooperative Engagement Function (CEF). Combat system baseline configuration dictates which source managers are contained within a specific version of the AWS. While System Track Manager (STM) implements a Track Server (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 a TS, while receiving and processing Source and System level track data. At times, these internal track stores can become out of synchronization with a 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 will perform real-time monitoring of all track databases within CND elements and automatically make corrections as necessary to keep them all in synchronization with the TS. This capability is not currently found anywhere else commercially and will provide for reduced hands-on maintenance of the systems, improved decision making with less researching of items, and provide smoother operation of the system.

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 IFF modes and codes, with an objective to compare and synchronize all track attributes. 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 an Aegis STM/TS software application 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. Analyze the accuracy of the software results 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. 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 a prototype Aegis STM/TS software application based on the results of Phase I. Demonstrate performance of the application in an existing Government-approved modeling and simulation environment in a Government-provided facility. Deliver the 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 STM/TS software application 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. Ramakrishnan, Raghu; Gehrke, Johannes; Derstadt, Jeff; Seliko, Scott and Zhu, Lin. "Database Management Systems Soluntion Manual Third Edition." University of Wisconsin–Madison. https://pages.cs.wisc.edu/~dbbook/openAccess/thirdEdition/solutions/ans3ed-oddonly.pdf

2. "System Track Manager/Track Server (STM/TS)." https://apps.dtic.mil/sti/pdfs/ADA557871.pdf

3. "Aegis Combat System." https://www.lockheedmartin.com/en-us/products/aegis-combat-system.html

4. "Track Management." https://www.lockheedmartin.com/en-us/products/seacommander.html

5. "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: Track identification/classification; Track Management domain; System Track Manager (STM); Track Server (TS); Product Line Architecture (PLA); synchronize all track attributes

TPOC 1: Richard Waters
(540) 653-6411
Email: [email protected]

TPOC 2: Gerald Lawrence
(202) 781-056
Email: [email protected]

---