TECHNOLOGY AREA(S): Weapons

ACQUISITION PROGRAM: Program Executive Office Integrated Warfare System (PEO IWS) 1.0 � AEGIS Combat System

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 section 5.4.c.(8) of 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 debris-modeling software for Anti-Ship Cruise Missile (ASCM) defense that models debris patterns of interceptor detonation and target destruction to enhance AEGIS combat system (ACS) effectiveness.

DESCRIPTION: ACS engagement utilizes the predicted intercept point (PIP) of the interceptor to the target to recommend weapons engagement sequencing.� The detonation of the initial target or the self-detonation of an interceptor can cause a debris field that could affect re-engagements or subsequent engagements. Several models currently in use address functionally different interceptors that do not represent the type of interceptor used in ASCM defense.� For example, the debris modeling used for Ballistic Missile Defense models exo-atmospheric environments and threats.� The interceptor warhead type and engagement environments (endo-atmospheric vs. exo-atmospheric) result in substantially different modeling characteristics for debris modeling.� The Navy needs a debris model that enables combat system and weapon engineers to accurately assess debris impacts on combat system design and operational effectiveness.� Additionally, in the test and certification environment, this model is needed to validate the effect of the debris field on the ACS and potentially reduce the number of interceptors and subsequent costs required to validate system performance.

The Navy seeks debris modeling software application for ASCM defense that accurately models Surface to Air missile engagement debris, including warhead, missile body, and target body fragments.� The physics-based mathematical debris model should have the capability to model various threat types including generic threat classes for ASCM, small aircraft, helicopters, Unmanned Arial Vehicles (UAV), and large aircraft.� Additionally, the debris model should have the capability to define and model various intercept characteristics based on threat type within a collective debris cloud.� These characteristics include size, velocity, density, and radar cross section in multiple bands.� The debris model should dynamically model the resulting intercept debris based on physical interaction with the environment.� This software application will need to integrate with the Combat System Test Bed (CSTB) environment to facilitate more cost-effective testing and certification of Surface to Air missiles and combat systems by reducing the number of interceptors required to validate system performance.� The software application will be required to run on LINUX-based hardware and seamlessly interface with all ACS elements to include sensors and radars, track managers, and weapons control systems. AEGIS Baseline 9 and 10 combat system configurations will be the primary focus for integration activities.

The Phase II effort will likely require secure access, and NAVSEA will process the DD254 to support the contractor for personnel and facility certification for secure access.� The Phase I effort will not require access to classified information.� If need be, data of the same level of complexity as secured data will be provided to support Phase I work.

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 DOD 5220.22-M, National Industrial Security Program Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Security Service (DSS). The selected contractor and/or subcontractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances, in order to perform on advanced phases of this contract as set forth by DSS 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 IAW DoD 5220.22-M during the advance phases of this contract.

PHASE I: Develop a concept for debris modeling software application for ASCM defense that accurately models Surface to Air Missile intercept debris, including warhead, missile body, and target body fragments.� The concept will support the test capabilities identified in the Description section of this document. Feasibility will be established by evaluation of the proposed debris model to incorporate physics-based mathematical models representative of the environment, proximity-based interceptors, and threat models to differentiate between debris and targets.� The Phase I Option, if awarded, will include the initial design specifications and capabilities description to build a prototype in Phase II. Develop a Phase II plan.

PHASE II: Based upon the results of Phase I and the Phase II Statement of Work (SOW), design, develop, and deliver a prototype of the debris modeling software application.� The prototype will demonstrate the capability to model debris from engagements within the CSTB, which represents the combat system test environment.� The debris software application must be able to execute in the operational environment of the combat system as described in the Description.� The software will be evaluated against Government-provided debris field data and Phase I validation approaches. The demonstration will take place at a Government- or company-provided facility.� The company will provide software design descriptions (SDDs) and test plans and procedures to demonstrate the product meets the attributes described in the Description section of this document. Prepare a Phase III development plan to transition the technology for Navy use and potential commercial use.

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 PEO IWS 1.0 in system integration of the prototype from Phase II.� AEGIS Baseline 9 and 10 combat system configurations will be the primary focus for integration activities.� The debris model will be fully functional in the AEGIS baseline testing modernization process and integrated into a baselines definition, incorporated into the baselines existing and new threat capabilities, validation testing, and combat system certification.

This technology is uniquely targeted at improvements to a Navy system.� Commercial use is not pertinent to this technology.� The algorithms produced for the software may have use in the shipping industry where navigating littoral waters could be improved by creating debris possibilities.

REFERENCES:

1. �Naval Weapons.� Jane�s 360, March 2017. http://www.janes.com/defence/weapons/naval-weapons

2. �Air-Launched Weapons.� Jane�s 360, March 2017. http://www.janes.com/defence/weapons/air-launched-weapons

KEYWORDS: Debris Modeling Software; Predicted Intercept Point; Anti-Ship Cruise Missile (ASCM); Self-detonation of an Interceptor; Surface to Air Missile Engagement Debris; Collective Debris Cloud