Terminal Defense Weapon System Coordinator

Objective: Develop a Terminal Defense System Weapon System Coordinator (TDSWC) for terminal defense system weapon system engagements. Description: PEO IWS 11 is responsible for providing terminal defense weapon systems for ship self-defense against Anti-Ship Missile (ASM), Helicopter, Aircraft, Unmanned Aerial Systems (UAS), and Surface Threats. The program’s portfolio includes Rolling Airframe Missile (RAM), Close-in Weapon System (CIWS), Counter-Unmanned Aircraft Systems (CUAS), Directed Energy, and Guns. Ship combat systems direct and manage terminal defense weapon system engagements so terminal defense weapon system upgrades require an update to the ship combat system. In addition, ship combat system weapon direction and management require complex algorithms in the ship combat system plus a detailed understanding of weapon systems’ performance. Ship combat system weapon system updates are part of the combat system’s major releases. This takes years of development, followed by years of fielding. The Navy seeks a capability that decouples weapon system upgrades from ship combat system updates and allows terminal defense systems to develop and field updates within two months. Currently no existing commercial technology can meet this need. The solution will move the ship combat system terminal defense weapon system responsibilities for managing upgrades and weapon system coordinating engagements from the combat system to the weapon system coordinator in real-time without latency. Development of the weapon system coordinator solution must use model-based system engineering (MBSE) for documenting requirements, developing the architecture, and testing the behavior. The coordinator shall use Artificial Intelligence (AI) for engagement coordination by implementing AI heuristics and machine learning. The MBSE model shall include a code generator that will translate the model to an executable program that can be run on a RED HAT LINUX platform. The coordinator will include a combat system interface for managing combat system commands as well as cyber secure interfaces to each terminal defense weapon system. 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 NASEA 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. Keywords: Ship Combat System; Model Based System Engineering; MBSE; Code Generator; Terminal Defense System; TDSWC; AI Heuristics; Weapon System Coordinating CMMC Level: Level 2 (Self)