DON26BZ03-NV064 TITLE: Terminal Defense Weapon System Coordinator

OUSW (R&E) CRITICAL TECHNOLOGY AREA(S): Applied Artificial Intelligence (AAI)

COMPONENT TECHNOLOGY PRIORITY AREA(S): Advanced Computing and Software; Integrated Network Systems-of-Systems; Trusted AI and Autonomy

PROJECTED CMMC LEVEL REQUIREMENT: Level 2 (Self)

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 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.

PHASE I: Develop a concept for a TDSWC concept using MBSE. Demonstrate feasibility in meeting the weapon system coordinator requirements using modelling, simulation, and analysis. The Phase I Option, if exercised, will include the initial design specifications and a capabilities description to build a prototype in Phase II.

PHASE II: Develop a TDSWC prototype based on results of the Phase I. Demonstrate the prototype meets the Description parameters by integrating the executable software into a Navy-provided simulation testbed that complies with the combat system and terminal defense systems interface requirements. Verify the prototype meets the defined requirements and architectures. Deliver the prototype to the Navy.

It is probable that the work under this effort will be classified under Phase II.

PHASE III DUAL USE APPLICATIONS: Support the Navy in transitioning the prototype TDSWC model and executable to a Navy appointed warfare center for future development and maintenance. Provide oversight during the transition of the TDSWC. Assist the Navy in product field testing, implementing upgrades, and porting the executable to different computing platforms.

Successful use of MBSE to document requirements, architecture and executable is desirable for products that can be used on a variety of computing platforms. The design and behavior of the product remains the same while the implementation of the product changes based on the computing platform’s characteristics (physical configuration, manufacturer, instruct set architecture, etc.). As such, this technology is useful for all computing architectures in corporations.

REFERENCES:

1. Mitchell, Steven W. "Model-based System Development for Managing the Evolution of a Common Submarine Combat System." A FCEA-GMU C4I Center Symposium on Critical Issues in C4I, 18-19 May 2010. STEVEMITCHELL_CI_C4I_2010V6. https://www.omg.org/sysml/Model_Based_Approach_to_Manage_Evolution-SteveMitchell_CI_C4I_2010v6.pdf
2. Lockheed Martin Company. "Lockheed Martin MDA Success Story: F16 Modular Mission Computer Application Software." Based on a presentation by Lauren E. Clark, Chief Engineer F-16 Modular Mission Computer Software; Terry Ruthruff, Staff Specialist Software Engineering Core; and Bary D. Hogan, Methodology Lead F-16 Modular Mission Computer Software.

https://www.omg.org/mda/mda_files/LockheedMartin.pdf

3. 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: Ship Combat System; Model Based System Engineering; MBSE; Code Generator; Terminal Defense System; TDSWC; AI Heuristics; Weapon System Coordinating

TPOC 1: Peter Johnson
(703) 872-3740
[email protected]

TPOC 2: Ted Edwards
(703) 872-3575
[email protected]