HDTRA1-17-S-0002_Addendum_2_Rev_2.pdf

October 2017 Revision to

ADDENDUM # 2

to the

DEFENSE THREAT REDUCTION AGENCY

BROAD AGENCY ANNOUNCEMENT

HDTRA1-17-S-0002

SCIENCE AND TECHNOLOGY

NEW INITIATIVES

Original Release: July 2017

Countering small Unmanned Aircraft Systems

(C-sUAS)

Addendum #2 to HDTRA1-17-S-0002 Page 2

1 FUNDING DESCRIPTION

This revision to this addendum updates the notification date in Section 5.1. All changes are prefaced by the word “updated” in all caps and bold text. No other changes were made.

1.1 This addendum serves to supplement the Defense Threat Reduction Agency’s (DTRA)

Science and Technology New Initiatives Broad Agency Announcement (BAA), HDTRA1-17-S-

0002. This research opportunity expands on the Research & Development Technology Area

(TA) 2: Counter WMD. As detailed in the BAA, TA2 Counter WMD states: “Develop, demonstrate, and transition innovative technologies and capabilities to actively counter the full spectrum of CBRNE threats.”

1.2 The Joint Improvised-threat Defeat Organization (JIDO), a component of DTRA, is seeking solutions for Countering small Unmanned Aircraft Systems (C-sUAS). JIDO is interested in solutions addressing aspects of the detect, track, identify, and defeat (DTID) engagement sequence portions of the C-sUAS kill chain, as well as complementary C-sUAS solutions as outlined in this addendum.

2 BACKGROUND

2.1 For this addendum, the following terms are defined:

2.1.1 C-sUAS: Countering small Unmanned Aircraft Systems

2.1.2 Detect: Initial discovery and alerting of a non-friendly sUAS in the vicinity

2.1.3 DID: Detect, Identify, and Defeat

2.1.4 DTID: Detect, Track, Identify, and Defeat

2.1.5 Track: Ability to dynamically monitor and report on sUAS position (2-D or 3-D geolocation)

2.1.6 Identify: Ability to determine make and model of sUAS that was detected

2.1.7 Defeat: Ability to disrupt, mitigate or destroy a sUAS or its mission functionality

2.1.8 Soft Kill: Ability to disrupt or mitigate by non-physical, non-destructive means

2.1.9 Hard Kill: Ability to physically disable or destroy sUAS (e.g. kinetic, directed energy, net capture, etc.)

2.1.10 Clutter: Non-sUAS signal sources which can cause a signal obscuration or false alerts from a C-sUAS sensor system if not discriminated against (relevant sources of clutter will vary depending on technique and environmental factors; e.g. RF sources, RADAR returns, acoustic sources, etc.)

2.1.11 Passive Threat: A non-friendly sUAS which does not have dedicated RF signal emissions (such as the Command and Control (C2) link, telemetry link, video link, etc.)

Addendum #2 to HDTRA1-17-S-0002 Page 3

2.1.12 White-List: Ability to discriminate between cooperatively registered (method of registration can vary) blue/white sUAS and unregistered red sUAS in vicinity

2.1.13 Red: Indicates an enemy piece of equipment (as in ‘red sUAS’)

2.1.14 Blue: Indicates a friendly piece of equipment (as in ‘blue sUAS’)

2.1.15 SWaP: Size, Weight and Power

2.1.16 Multiple-sUAS (or drone) Attack: An attack by multiple, independently flown and coordinated red sUAS

3 OBJECTIVE / PROBLEM STATEMENT

3.1 Most known single C-sUAS technology modalities are incapable of adequately performing each element of the DTID engagement sequence as identified above. As such, JIDO is seeking approaches which systematically integrate various technology modalities in order to appropriately address requirements.

3.2 JIDO’s specific interest areas in C-sUAS appear below. In general, longer range capabilities are preferable.

3.3 JIDO is not seeking to fund development of wholly new methodologies or technologies from the ground up. Rather, this initiative seeks to spur innovative use or integration of existing technologies/methodologies/techniques to satisfy the requirements listed below. This initiative also seeks to assist nearly completed developmental methods in reaching a point where they can be applied to the requirements below, and be compatible with operations in both unclassified and classified domains. As such, JIDO is interested in technologies with a minimum Technology

Readiness Level (TRL) of 4. Proposals which can achieve a field-able prototype status in under two years of development effort will be more strongly considered than longer efforts.

3.4 General Requirements:

Simple to use (Soldier-operable with minimal training)

Hardened to withstand environmental testing detailed in MIL-STD-810G for operation in inclement weather and extreme temperatures

Systems should save all relevant data and make that data available for later exploitation

Built on open software architecture and modular hardware framework for integration with other GOTS and/or COTS systems

A post prototyping production plan should be highlighted in proposals

4 JIDO C-sUAS AREAS OF INTEREST

Offerors should note that across all of the areas of interest detailed below that low cost solutions are strongly encouraged. Shorter schedules for achieving field-able prototype will be considered favorable (i.e. 3 months > 6 months > 9 months > 12 months…). The duration of Addendum #2 efforts will be no more than 18 months.

Addendum #2 to HDTRA1-17-S-0002 Page 4

All of the distances given below are with respect to either the soldier (dismounted operations), vehicle (mounted operations) or outer boundaries of site (fixed-site operations).

Area of Interest 1—Integrated Prototype System Utilizing a Hard Kill (DTID): An integrated

C-sUAS system covering the DTID engagement sequence (via a hard kill solution) portions of the C-sUAS kill chain. The DTID minimum effective distance is 2 km. Low SWaP and high versatility systems (able to be used in dismount, mobile, fixed-site operations, etc.) are preferred.

Area of Interest 2—Integrated Mobile System (DID) with Ground Station Geolocation: An integrated, mobile C-sUAS system covering the DID portions of the C-sUAS kill chain. The

DID minimum effective distance is 2 km. The system will be small enough to operate on a light tactical vehicle (such as the M-RZR) and be operable “on-the-move”. In addition to any other functions, this system will be able to geolocate the red ground station.

Area of Interest 3—Integrated Dismount (soldier-worn or backpack-able) System (DID): An integrated, soldier-worn or backpack-able C-sUAS system covering the DID portions of the C-sUAS kill chain for use on dismounted operations. The DID minimum effective distance is 2

km. System will be no more than 12 lbs. overall weight (including power source) and must have the ability to detect sUAS while “on-the-move”. User interfaces that can be integrated with

Android OS are strongly encouraged. System will be fully operable for a minimum of eight hours on battery power. Integration with standard military battery pack required. System use-case versatility (e.g. dismounted operations, mobile operations, etc.) is encouraged.

Area of Interest 4—Integrated RADAR and Optical Defeat Solution: An integrated C-sUAS system combining a RADAR (detect and track) with an automated optical defeat system. The optical defeat (such as a LASER dazzler, etc.) will effectively deny the enemy the ability to view video (live-feed or recorded) for no less than 180 seconds. This may be accomplished by damage, interference or other means.

Area of Interest 5—Small Standalone Optical Defeat Solution: A small, standalone C-sUAS optical defeat system that will effectively deny the enemy the ability to view video (live-feed or recorded) for no less than 180 seconds. This may be accomplished by damage, interference or other means. This solution will be small enough and light enough to be soldier-packable or mounted on standard issue weaponry.

Area of Interest 6—Automated Hunter-Killer Drone Defeat Solution: System utilizing a blue sUAS (Group 1 or 2) to defeat a red sUAS (e.g. kinetic, net, electronic, etc.). After initialization, the system will be able to accept a 3-D geolocation cue (constantly updating, such as from a

RADAR) and proceed to defeat the red sUAS in a fully automated fashion.

Area of Interest 7—Minimal Collateral Damage Munition or other Defeat Effector for Hunter-

Killer Drone: A munition or other defeat effector (e.g. net, EMP, etc.) which is lightweight enough to be delivered by a small (Groups 1 and 2) hunter-killer UAS. The effector will be designed to minimize collateral damage.

Addendum #2 to HDTRA1-17-S-0002 Page 5

Area of Interest 8—Counter Multi-UAS Defeat Solutions: C-sUAS solutions for defeating multiple drone attacks. System will be capable of defeating a group of sUAS simultaneously or in a short period of time (<6 seconds per individual defeat). Defeat minimum effective distance is 2 km.

Area of Interest 9—Passive Threat Detection System: System capable of detecting a passive sUAS threat (red sUAS with no dedicated RF signal transmissions). Minimum detection distance is 2 km. Examples include, but are not limited to, acoustic, optical and RADAR systems. Systems which are passive (non-emitting) themselves are encouraged, though not required.

Area of Interest 10—Forensic Exploitation of Airborne sUAS: Solution capable of interrogating and extracting information from embedded chips on red sUAS platforms while they are in flight. Minimum effective distance is 2 km.

Area of Interest 11—Complementary Solutions to Improve RADAR Clutter Discrimination:

Hardware or software solutions to aid in improving clutter discrimination of sUAS and other small RCS (RADAR cross-section) objects. Solutions capable of integration with existing military RADAR systems are preferable.

Area of Interest 12—Dismounted Defeat Solutions: Small form factor defeat solution for dismounted operations. Defeat minimum distance is 2 km. Soft-kill solutions should be no more than 5 lbs. overall weight (including power source) and hard-kill solutions no more than 10 lbs.

overall weight.

5 MAJOR MILESTONES

5.1 The schedule for Addendum #2—Countering small Unmanned Aircraft Systems (C-sUAS) submission information is detailed in the following table:

Date Event

3 July 2017 DTRA BAA Addendum 2 announced in FedBizOpps website

5 July 2017 Begin registration at the DTRA proposal submission website

26 July 2017 Pre-coordination white paper and quad deadline (pre-coordination will occur on a rolling basis; early submission is encouraged)

11 August 2017 Pre-coordination activities end

8 September 2017 Formal proposal receipt deadline

Addendum #2 to HDTRA1-17-S-0002 Page 6

UPDATED:

On or about 31 January 2018

Notifications of proposal review to Offerors by e-mail

Awards expected to begin approx. 150 days following initiation of negotiations 1, 2

Notes:

* DTRA may engage in technical discussions with offerors; however, not all offerors will be contacted. Discussion occurrence does not indicate DTRA’s level of interest.

1. Actual award dates will vary based on receipt of funding, complexity, statutory requirements, proposal quality, pricing considerations, DCAA audits of proposed rates, type of instrument, number of awards, and other considerations. All dates are subject to change.

2. Awards will be made subject to the availability of funds. All Offerors will be invited to begin negotiations upon notification of intent to award.

6 SUBMISSION INSTRUCTIONS

6.1 While submissions may span one of more of the areas of interest detailed herein, Offerors should submit pre-coordination communications and formal proposals to the primary area of interest. Secondary areas of interest may be referenced as well.

6.2 All pre-coordination and formal proposal submissions should be made in accordance with the guidance provided in HDTRA1-17-S-0002, Science and Technology New Initiatives BAA.