DARPA-BAA-15-26_Amendment_1_SXCT.pdf

DARPA-BAA-15-26

Broad Agency Announcement

Squad X Core Technologies (SXCT) – Amendment 1

Tactical Technology Office (TTO)

February 24, 2015

Contents Part I: Overview Information Part II: Full Text of Announcement

I. Funding Opportunity Description A. Program Goals B. Program Plan C. Phase I (Concept Development) Technical Objectives D. Phase I (Concept Development) Reviews and Deliverables E. Phase II (Technology Maturation) Technical Objectives F. Phase II (Technology Maturation) Reviews and Deliverables

II. Award Information A. Awards B. Fundamental Research

III. Eligibility Information A. Eligible Applicants B. Procurement Integrity, Standards of Conduct, Ethical Considerations, and Organizational Conflicts of Interest C. Cost Sharing/Matching D. Other Eligibility Criteria

IV. Application and Submission Information A. Address to Request Application Package B. Content and Form of Application Submission

V. Application Review Information A. Evaluation Criteria B. Review and Selection Process

VI. Award Administration Information A. Selection Notices B. Administrative and National Policy Requirements C. Reporting D. Electronic Systems

VII. Agency Contacts VIII. Other Information

A. Intellectual Property Procurement Contract Proposers B. Non-Procurement Contract Proposers – Noncommercial and Commercial Items (Technical Data and Computer Software) C. All Proposers – Patents D. All Proposers – Intellectual Property Representations

Part I: Overview Information

• Federal Agency Name – Defense Advanced Research Projects Agency

(DARPA), Tactical Technology Office (TTO)

• Funding Opportunity Title – Squad X Core Technologies (SXCT)

• Announcement Type – Initial Announcement

• Funding Opportunity Number – DARPA-BAA-15-26

• Catalog of Federal Domestic Assistance Numbers (CFDA) – Not

Applicable

• Dates

• Posting Date February 24, 2015

• Addendum Request Due Date March 27, 2015 at 1400 EDT

• Security Class. Guide Request Due Date March 27, 2015 at 1400 EDT

• Proposers’ Day February 27, 2015

• Questions Due Date March 10, 2015 at 1400 EDT

• Proposals Due Date April 10, 2015 at 1300 EDT

• Concise description of the funding opportunity: The objective of the Squad X

Core Technologies program is to develop and deliver new technologies that give dismounted squads increased situational awareness and enable them to dominate their battlespace. This will be accomplished through research and development of novel technology solutions that advance the capabilities of the squad. Part of the program objectives can be found in this BAA’s classified addendum. Instructions for requesting the addendum can be found in Section IV.A of Part Two of this document.

• Total amount of money to be awarded: Up to $22.4M for Phase I (Base Period), and up to $33.6M in Phase II (Option)

• Anticipated individual awards – Multiple awards are anticipated for each Technical Area.

• Types of instruments that may be awarded -- Procurement contract or other transaction.

• Agency contact The BAA Coordinator for this effort can be reached at DARPA-BAA-15-26@darpa.mil or:

DARPA/TTO

ATTN: DARPA-BAA-15-26

675 North Randolph Street Arlington, VA 22203-2114 E-mail: DARPA-BAA-15-26@darpa.mil

• Other - The addendum to this BAA is available upon request as described in Section IV.A of Part Two of this announcement.

mailto:DARPA-BAA-15-26@darpa.mil

Part II: Full Text of Announcement

I. Funding Opportunity Description The Defense Advanced Research Projects Agency (DARPA) often selects its research efforts through the Broad Agency Announcement (BAA) process. This BAA is being issued, and any resultant selection will be made, using procedures under Federal Acquisition Regulation (FAR) 35.016. Any negotiations and/or awards will use procedures under FAR 15.4, Contract Pricing, as specified in the BAA. Proposals received as a result of this BAA shall be evaluated in accordance with evaluation criteria specified herein through a scientific review process.

DARPA BAAs are posted on the Federal Business Opportunities (FedBizOpps) website, http://www.fbo.gov/. The following information is for those wishing to respond to the BAA.

DARPA is soliciting innovative research proposals in the area of dismounted squad technologies. Proposed research should investigate innovative approaches that enable revolutionary advances in science, devices, or systems. Specifically excluded is research that primarily results in evolutionary improvements to the existing state of practice.

U.S. dismounted rifle squads lack 21st century combat power. Over 95% of casualties in Operations Enduring Freedom, Iraqi Freedom, and New Dawn occurred after operations transitioned from linear, conventional combat to the nonlinear, nonconventional stabilization phase. Rifle squads do not possess an inherent adaptability and flexibility to transition from offensive and defensive operations to stability operations and back again. The costs of this mismatch are high.

On their own terrain, our adversaries have significant advantages. They often have ubiquitous communications, can hide within the terrain or culture, and follow different rules of engagement. Adversaries can use materials and tools from their everyday society, keeping their logistics burden low. They can use emerging technologies to pose novel and diverse threats. The result is that our military squads have less situational awareness (SA) than their adversaries. Our squad sensing is limited by line of sight and narrow fields of view. Our squads also lack precision effects; their ability to finish engagements often relies on capabilities not carried organically by the dismounted squad.

Squad X Core Technologies (SXCT) is an advanced technology program to adapt, extend, and develop capabilities that enhance the dismounted rifle squad’s situational awareness and enable them to shape and dominate their battlespace. The goal is to build combat power from the rifle squad up, allowing forces to be adaptable and flexible across the range of military operations.

http://www.fbo.gov/

Technical capabilities to be developed within the program will address key capability gaps in the performance of dismounted rifle squads. The program will demonstrate efficacy of the resulting technologies through demonstrations, simulation, and experimentation.

DARPA will use a phased acquisition approach for the SXCT program under this BAA, which solicits proposals for Phase I (Base) and Phase II (Option) efforts as illustrated in Figure 1. Phase I (Concept Development) will research and demonstrate initial capabilities for each of four technical areas. The program expects to select multiple technologies from each technical area for maturation and initial proof of principle demonstration and/or simulation. Phase II (Technology Maturation) builds upon successful demonstrations in Phase I and conducts experiments to evaluate technologies as they mature. If the Government elects to continue the program into Phase II, it may exercise the option on the contract(s) of the selected performer(s) based on Phase I performance and the candidate technologies’ potential to meet the program goals and metrics. The Government retains the right to award all, some, one, none or portions of the proposed Phase II options to support promising further technology developments or support transition of a technology developed in Phase I. The SXCT capability development efforts will parallel Squad X study efforts. The focus of Squad X studies is to inform DARPA about potential squad-system development and integration efforts. At this time, DARPA does not expect data or results from Squad X studies to be incorporated into proposed SXCT efforts.

Figure 1. SXCT Program Plan Overview

A. Program Goals The Army and Marine Corps design rifle squads for linear, conventional operations. As a direct result, rifle squads lack the inherent adaptability and flexibility to successfully conduct a wide range of missions without significant non-organic support.

Stabilization operations challenge rifle squads when the rules of engagement restrict the use of non-organic, precision platforms designed for conventional operations. Future threats will employ asymmetric tactics, even in conventional conflicts.

The SXCT program will develop new, organic capabilities for the rifle squad by adapting and extending previous efforts or developing novel technical solutions. These new capabilities will enhance the situational awareness of the rifle squad and enable them to shape and dominate their battlespace. An overarching constraint of the SXCT program is to limit the amount of additional size, weight, and power requirements for dismounted infantrymen.

This BAA solicits proposals for Squad X Core Technologies Base and Option efforts only. In particular, this solicitation seeks new concepts and technologies that serve to enhance individual and/or group ability to perceive and comprehend the environment and events within it. It also seeks enabling technologies that allow the squad to project influence at longer range and individuals to direct accurate and precise effects despite degraded/obscured lines of sight. The program will exercise selected technology components in live experiments.

The SXCT program comprises four Technical Areas:

1. Precision Engagement – enable the rifle squad to precisely engage threats out to 1,000 meters while maintaining compatibility with infantry weapon systems and human factors limitations.

2. Non-Kinetic Engagement – enable the rifle squad to disrupt enemy command and control, communications, and use of unmanned assets to ranges greater than 300 meters while maneuvering at a squad-relevant operational pace.

3. Squad Sensing – enable the rifle squad to detect line of sight and non-line of sight threats out to 1000 meters while maneuvering at a squad-relevant operational pace.

4. Squad Autonomy – enable the rifle squad to improve their individual and collective localization accuracy to less than 6 meters in GPS-denied environments through collaboration with unmanned systems maneuvering reliably in squad formations.

Proposers should not submit proposals that combine multiple Technical Areas into a single effort; proposers may submit separate technical and cost proposals for each proposed technical area. DARPA will consider proposals that address multiple technical areas as non-responsive and will not evaluate them. The purpose of this approach is to streamline the contracting process and not to restrict ideas or prevent entities from offering multiple technology solutions. Proposers should strive to provide a clear understanding of the cost, risk, and organizational expertise to be used within each proposed effort.

A.1 Technical Area 1: Precision Engagement In order to control the squad battlespace, dismounted infantry squads require the ability to organically engage adversaries outside their line of sight. While infantry formations can effectively employ precision Non-Line-of-Sight (NLOS) effects, none of these capabilities currently exist in the rifle squad; the infantry company has the ability to apply precise, NLOS fires with increased precision at higher echelons.

The goal of Technical Area 1 is to develop technologies that enable the rifle squad to precisely engage known NLOS threats in their battlespace. This new capability will create a cost-effective increase in firepower using existing platforms, giving the squad an organic ability to precisely engage threats outside the warfighter’s line of sight and the potential to reduce the requirement for a rifle squad to engage the same target in order to mass effects.

DARPA seeks a guided weapon capability that is compatible with current squad equipment, such as the M203/M320 grenade launchers or the Picatinny Rail system.

Solutions can include, but are not limited to, a micro-missile or advanced 40mm grenade that can precisely engage NLOS targets. Successful solutions will be able to leverage the networked squad, which can be assumed to include accurately localized squad members (manned and unmanned) and a squad-shared awareness enabled by data fusion from multiple sources.

Proposed solutions should require either continuous closed-loop guidance of a projectile to target or initial closed-loop guidance followed by accurate terminal engagement. The desired engagement ranges for Squad X extend beyond capabilities of grenades, which are presently only effective up to 400m. Proposers may describe efforts to track and engage moving targets out to 1,000m. Proposers may also describe efforts to develop novel, launchable sensors (e.g., small unmanned aerial vehicles) for reconnaissance, surveillance, and target acquisition. Proposed solutions must limit recoil energy to the rifleman to a safe level, since squad systems are expected to be shoulder-fired using existing equipment.

Program success metrics for Technical Area 1 are:

o Accuracy 2m CEP o Mass ≤ 1.0 kg o Recoil Energy ≤ 70 joules

Specifically not desired are: developments in explosive payloads; evolutionary upgrades to existing rounds; solutions requiring excessive impulse forces on the Soldier;

open-loop ballistic guidance; or developments that do not interface with existing squad equipment, i.e., the M203/M320 or Picatinny Rail.

A.2 Technical Area 2: Non-Kinetic Engagement Technical Area 2 will explore integrating non-kinetic offensive capabilities into the dismounted rifle squad in order to increase their operational flexibility. Concepts may explore the capability to disrupt threat command, control, and communications, as well as counters for threat use of unmanned systems.

Program success metrics for Technical Area 2 are:

o Squad Movement Speed ≥ 2 m/s o Soldier SWaP – Mass < 900 g o Soldier SWaP – Volume < 500 cm3

The full objectives and scope of Technical Area 2 can be found in this BAA’s classified addendum.

A.3 Technical Area 3: Squad Sensing Today’s squad has limited situational awareness due to limited line of sight and narrow fields of view. Current sensing technology does not lend itself well to squad operations due to high size, weight, power, cost, and false alarm rate.

Technical Area 3 will extend the squad’s situational awareness by developing novel means to identify threats in the squad’s operational environment. The goal is to detect where Soldiers cannot – beyond the limitations of their own senses. Of special interest are techniques that take advantage of the distributed nature of the squad (e.g., acoustic sensor arrays) or multiple sensing modalities (e.g., handheld radar, human heartbeat, and infrared). This technical area will emphasize detecting and localizing potential human threats.

Technical Area 3 solicits two types of technology solutions, Sensing and Exploitation.

Sensing (3A)

DARPA seeks sensor systems with sufficiently low weight and power that they can be carried by the Soldier or autonomous platforms and can take advantage of the distributed nature of the squad to sense beyond the Soldier’s normal range. Proposed efforts may investigate sensor arrays to network the squad’s sensing and novel human detection capabilities to enhance the squad’s ability to detect threats. Proposed efforts may also investigate directed sensors to eliminate the existing sensing gap that results from current rules of engagement, while developing technologies that minimize low false alarm rates over realistic operational conditions. Proposers are encouraged to pursue a technical approach that minimizes the size, weight, and power (SWaP) of sensing on both human and machine members of the squad.

Exploitation (3B) DARPA seeks efficient, accurate exploitation of data collected by sensors on autonomous platforms to classify threats beyond the line of sight. Identifying moving people from an unstable platform, such as a Soldier or UAV, is not a solved problem under real-world conditions. Further, performance of current solutions degrades at extended ranges and under natural illumination. DARPA desires novel exploitation techniques that can classify threats in collected sensor data, especially human threats.

The focus will be on methods that can perform within squad-level sensing and computing limitations.

Technical Area 3 is primarily a software development effort. Some sensor integration may be required to create novel hardware configurations or packaging, but the program does not expect significant new sensor type development. Proposers may address Solutions 3A, 3B, or both in their proposals for Technical Area 3.

Program success metrics for Technical Area 3 are:

o Accuracy 0.9 o Squad Movement Speed ≥ 2 m/s o Soldier SWaP – Mass < 350 g o Soldier SWaP – Volume < 200 cm3

Specifically not desired are: evolutionary algorithm or sensor developments;

significant hardware or software interface development; or global, multi-scale common world model development.

A.4 Technical Area 4: Squad Autonomy Technical Area 4 will develop collaborative manned-unmanned teaming to improve friendly situational awareness. The focus is on squad-level localization through the combination of multiple localization techniques per agent, coupled with multi-agent localization between heterogeneous human and machine agents. It will also focus on squad-relevant robotic behaviors in operational missions, enabling squad robotic team members to maneuver as a member of the squad formation.

Technical Area 4 solicits technologies in two areas: Localization and Robotic Behaviors. Proposed solutions should operate in complex military environments, such as cluttered urban and rolling open terrain, at a squad-relevant military tempo (constant movement speed of 2 m/s, burst movement speed of 4 m/s).

Localization (4A) Army and Marine infantry squads currently have a limited capability to dynamically and accurately localize squad member position, which greatly hinders the squad’s effectiveness. The U.S. Army fielded Nett Warrior-equipped squads, which can register and communicate GPS position location information (PLI) to other similarly-equipped nodes on the network. Nett Warrior does not provide PLI in a GPS-denied environment. Only three squad members (out of nine) carry end-user devices and squad radios. The remainder of the dismounted squad members must maintain line of sight contact for tasking, ranging, and tactical maneuvers.

Present-day position, navigation and timing (PNT) and inertial navigation systems (INS) primarily focus on single node, single/multi-mode localization techniques.

Technology is slowly evolving to improve sensor navigational accuracy and reduce size, weight and power, but does not address the use of multiple nodes to reduce localization or robust operation in GPS-denied environments such as buildings, subterranean, or in urban canyons. A significant challenge is bounding error growth over time in austere environments.

DARPA seeks novel techniques to improve localization accuracy using multiple localization techniques per Soldier and multi-agent localization across all members of the squad (including autonomous platforms). The goal is to address the challenges of a distributed squad battlespace:

• Accuracy in GPS-denied environments;

• Accuracy over time and distance with inexpensive (or common Soldier) sensors;

• Multi-node localization (among humans and unmanned systems);

• Collaborative error reduction – teamwork, anchor, reset;

• Multiple sensor mode localization;

• Lack of a “motion model” for humans; and

• Accuracy over range of Warfighter motions: running, climbing, crawling.

Proposed technologies must function in a GPS-denied environment. Localization techniques may assume the use of a priori, two- and three-dimensional data to improve performance and accuracy. Proposers may assume that bandwidth between nodes is not a constraint.

Robotic Behaviors (4B) Current autonomous systems are unable to work with a squad at full operational tempo or without requiring a head-down operator. DARPA seeks technologies that enable heterogeneous (ground and air) unmanned vehicles to perform squad-level tasks at distances up to 300m between nodes with zero interventions. DARPA does not consider standard tasking commands as interventions.

Robotic team members should be able to execute preparative and reactive actions with equivalent autonomy to junior squad members. They must be capable of taking minimal mission-based input and performing maneuver, coverage, and tactics relevant to their squad role (and payloads) without requiring head-down control by an operator.

Examples of operations include: Squad Movement Techniques, Squad React to Contact, Squad Break Contact, and Squad React to Ambush. Proposers may assume that each squad member (human and robotic) will receive an updated pose estimate of all individual squad members and may use a priori, two- and three-dimensional data.

Proposers may describe their own robotic team configuration, which must be organic to the squad. The following is a notional robotic team, which does not encompass the entire range of configurations that could be proposed:

• One Unmanned Air Vehicle (UAV) with 2.5 kg of payload that operates at ~30- 60m above the squad and ~30-60m ahead of the squad. The UAV will track the squad and take cues from squad maneuver (optimal) and direct squad tasking.

• One Unmanned Ground Vehicle (UGV) serving as a RSTA/SA1 point robot 30 m ahead of the squad on the ground capable of operating as a breaching/engineering/ sensor asset. The ground vehicle will have a 25 kg payload capacity for sensors and systems.

1 Reconnaissance, Surveillance, and Target Acquisition / Situation Awareness

• One UGV for operating in squad formation as a support robot. The payload is 50kg for either supplies, specialized communications gear, or for offensive/defensive payload systems for the squad.

The SXCT program does not intend to invest in platform development. Proposers should describe the (surrogate) platforms to be used and the advantages of that platform for the intended development. The following are point-of-departure platform examples.

Emphasis should be placed on suitability for experimentation, cost, and SWaP (not in order of priority):

• Commercial, medium scale quadrotors (2.5 kg to 5 kg, 30 min to 60 min flight time, 300 m altitude) with modifications for payloads, sensing, controls, perception, and communications. The platform should be able to be carried by one Soldier and should be powered by batteries.

• Commercial UGVs (wheeled, tracked, or other) with modifications for payloads, sensing, controls, perception, and communications. The platform should not exceed 700 kg (without payload) and have at least a 0.2 m ground clearance.

Ground and air platforms should be able to support operational squad speeds up to

4 m/s and have sufficient mobility to traverse slightly cluttered urban and rolling open terrain. Performers will purchase their own platforms and specify appropriate perception and computing payloads. Proposers should describe interfaces to be used by squad members for controlling robotic team members.

DARPA is interested in perception systems that use minimal (or zero) active sensing, or active systems with minimal signatures (e.g., spread-spectrum LIDAR).

Proposers are encouraged to pursue a technical approach that minimizes sensing system SWaP on both human and machine members of the squad. Perception system development should be embedded within an approach that develops robotic behaviors, not solely an effort to develop new perception systems.

Ideally, proposed efforts will address all elements of Technical Area 4 as described above. Teams may propose efforts to only develop human, collaborative localization technology. Teams may propose efforts to develop human-machine collaborative localization without autonomous behaviors or efforts to develop autonomous behaviors without addressing human-machine collaborative localization.

Program success metrics for Technical Area 4 are:

o Absolute position ≤ 6 m o Interventions 0 o Soldier SWaP – Mass < 350 g o Soldier SWaP – Volume < 200 cm3

Specifically not desired are: unmanned platform development; evolutionary autonomy system development; developmental sensors; individual person or platform localization; machine-only collaborative localization and mapping; or fully active sensor systems using traditional/fixed wavelengths (e.g., LIDAR at typical 850-905 nm ranges).

B. Program Plan DARPA will execute the SXCT program in two phases:

• Phase I - Concept Definition - a 12-month effort to research and demonstrate initial capabilities for each of the four technical areas. The program expects to select two to four efforts from each technical area, with an estimated total of eight to twelve efforts for maturation and initial proof of principle demonstration.

• Phase II – Technology Maturation – an 18-month effort that builds upon successful demonstrations of capability performance. If the Government elects to continue the program into Phase II, it may exercise the option on the contract(s) of the selected performer(s) based on Phase I performance and the candidate technologies’ potential to meet the program goals and metrics. The program expects to select approximately four to six performers for continuation into Phase

II.

The SXCT program schedule is shown in Figure 2.

Figure 2. SXCT Program Schedule

C. Phase I (Concept Development) Technical Objectives The objectives of Phase I are to design, implement, and demonstrate novel squad capabilities in each of the technical areas. Successful proposers will demonstrate technologies that help meet the program goals and make progress towards the program success metrics listed in Table 1. A key consideration is that any developed capability shall have sufficiently low SWaP that it can be effectively integrated into the dismounted infantry squad.

Table 1. SXCT Program Success Metrics

Topic Area Criteria Metrics/Goals Precision Engagement Accuracy

Mass Recoil Energy

2m CEP ≤ 1.0 kg ≤ 70 joules

Non-Kinetic Engagement Squad Movement Speed Soldier SWaP - Mass Soldier SWaP - Volume

≥ 2 m/s < 900 g < 500 cm3

Squad Sensing Accuracy Squad Movement Speed Soldier SWaP - Mass Soldier SWaP - Volume

0.9 ≥ 2 m/s < 350 g < 200 cm3

Squad Autonomy Absolute position Interventions Soldier SWaP - Mass Soldier SWaP - Volume

≤ 6 m < 350 g < 200 cm3

The SXCT program will add metrics during the course of the program based on the mix of proposed technologies and the outcome of modeling, simulation, and baseline experimentation efforts.

C.1 System Development and Demonstration Plan (SDDP) The performer shall refine and add details to the SDDP provided in the proposal, which is described further in Section IV under “Section II. Technical Details” on page 31 of this document. The SDDP defines the team’s overall approach to mitigating risk and maturing their technology. The SDDP should define the risk reduction, technology development and maturation, and demonstration activities necessary to achieve the SXCT program objectives. The SDDP will provide an integrated basis for all development and demonstration activities and describe the progression of demonstrations over both phases that will achieve the program goals.

C.2 Concept Demonstration In Phase I, performers will substantiate technology performance through a concept demonstration. The Phase I demonstrations will show the soundness of the technical approach, express a thorough understanding of the proposed capability, and help DARPA predict success in Phase II. At a minimum, Phase I performers will demonstrate the final proposed capability in a modeling and simulation environment.

DARPA prefers that Phase I teams perform a live demonstration. Where necessary, the proposer may augment testing with appropriate systems-level modeling and simulation by using simulation to exercise subsystem components or attributes that are not easily tested, preferably in a hardware-in-the-loop approach. Concept demonstrations will be held at a performer-designated location.

DARPA expects Phase I demonstrations to clearly illustrate performance against the program success metrics. Demonstrations should include, at a minimum (not in order of priority):

1. Precision Engagement: Hardware-in-the-loop simulation with estimation of procurement cost, degree of interoperability with current rifle squad weapon systems, and human factor impacts.

2. Non-Kinetic Engagement: Tactical demonstration in open terrain with an estimation of size, weight, and power requirements to achieve program success metrics at the end of Phase II.

3. Squad Sensing: Live demonstration of capability with a representative fire team in open terrain and an estimation of size, weight, and power requirements at completion of Phase II.

4. Squad Autonomy: Live demonstration of capability with a representative fire team in open terrain and an estimation of size, weight, and power requirements at completion of Phase II.

D. Phase I (Concept Development) Reviews and Deliverables To successfully achieve the SXCT objectives, DARPA has defined a minimum list of reviews and deliverables that must be included in proposals. Table 2 outlines the expected Phase I reviews and deliverables. The table uses a relative schedule of Months After Award (MAA); performers should estimate contract award to be in Q4FY15 for planning purposes. Proposers should populate their program schedule with these minimum deliverables and supplement this list with additional deliverables/material to be presented at each review, in accordance with their unique program schedule and development approach.

Table 2. SXCT Phase I Concept Development Reviews and Deliverables

Event Due Date Deliverables Location

Kickoff Meeting 0 MAA Review briefings DARPA Vicinity

Concept Preliminary Design Review 4 MAA Review briefings

Updated SDDP Performer Location

Concept Critical Design Review 7 MAA Review briefings

Updated SDDP Performer Location

Concept Demonstration 11 MAA Concept Demonstrations

Demonstration Report Performer Location

Monthly R&D Status Reports: Technical & Financial

1, 2, 3, … MAA

Monthly R&D Status Reports:

Technical & Financial N/A

Final Report 12 MAA Final Report N/A

D.1. Phase I Kick-off Meeting A kick-off meeting will be held at or near the DARPA facility. The objective of this meeting will be to discuss the performer’s approach to the program and provide feedback to guide the performer in executing their Phase I effort. DARPA and the performer will also establish the program review schedule as well a schedule of interim informal interactions, including routine management and technical teleconferences.

D.2. Concept Preliminary Design Review The objective of this review is to assess the performer’s program approach and progress, and allow DARPA an opportunity to provide guidance. The performer shall present a detailed design and an initial plan for the concept demonstration. This discussion should assess the performer’s progress towards achieving the program success metrics. The performer shall also update the SDDP and provide a revised risk assessment of their proposed concept, including high risk enabling technologies and major risk reduction activities that they believe are required to meet the program goals.

D.3. Concept Critical Design Review The objective of this review is to assess the performer’s program approach and progress, and allow DARPA an opportunity to provide guidance. The performer shall provide details of the implementation and a detailed plan for the concept demonstration.

This discussion shall also update the SDDP and predict system performance against the program success metrics.

D.4. Concept Demonstration At the end of Phase I, each performer will substantiate the efficacy of their approach through a concept demonstration, which will follow the proposer’s updated SDDP. Demonstrations will clearly show the soundness of the technical approach, express a thorough understanding of the proposed capability, and indicate the likelihood of success in Phase II by comparison with the program success metrics listed in Table 1.

Performers shall deliver a test report analyzing system performance against overall program metrics and illustrating progress against program goals.

D.5. Monthly R&D Status Reports & Final Report The performer will submit monthly technical, financial, and schedule status reports that highlight overall team work and progress. The performer will be required to submit a Final Report upon contract completion. Performers shall deliver reports via e-mail to DARPA directly in addition to any award distribution or online submission requirements.

E. Phase II (Technology Maturation) Technical Objectives Phase II (Option) is an 18-month effort that builds upon successful demonstrations of capability performance. If the Government elects to continue the program into Phase II, it may exercise the option on the contract(s) of the selected performer(s) based on Phase I performance and the candidate technologies’ potential to meet the SXCT program goals and metrics at the end of Phase II. The program expects to select approximately four to six performers for continuation into Phase II.

E.1 System Development and Demonstration Plan (SDDP) The performer shall refine and add details to the SDDP based on performance in

Phase I and guidance from the Government. The SDDP will describe the team’s approach to mitigating risk and maturing their technology through Phase II. The SDDP should define the risk reduction, technology development and maturation, and demonstration activities necessary to meet the SXCT program success metrics.

E.2 Evaluation Experiments The goal of Phase II is to mature the Phase I capabilities, put them into a form that can be evaluated in a field experiment, and demonstrate performance against the program metrics listed in Table 1. During Phase II, DARPA will assess technology performance through a set of Evaluation Experiments that focus on rifle squad operations in a complex urban environment. The Phase II experiments will be run by DARPA at a location to be defined later. These events will evaluate each technical area with respect to the program success metrics and demonstrate continuous progress throughout the Phase. A key consideration is that any developed capability shall have sufficiently low SWaP that it can be effectively integrated into the dismounted infantry squad.

By technical area, the Phase II experiments will assess:

• Precision Engagement: Guided flight demonstration of capability with production representative components.

• Non-Kinetic Engagement: Final demonstration of capability will be a tactical demonstration in an urban environment with surrogate systems, with computer processing located on the surrogate systems.

• Squad Sensing: Final demonstration of capability will be with a rifle squad in urban terrain with all hardware and processing located within the squad formation.

• Squad Autonomy: Final demonstration of capability will be with a rifle squad in urban terrain with all hardware and processing located within the squad formation.

F. Phase II (Technology Maturation) Reviews and Deliverables To successfully achieve the SXCT objectives, DARPA has defined a minimum list of reviews and deliverables that must be included in proposals. Table 3 outlines the expected Phase II reviews and deliverables. The table uses a relative schedule of Months After Award; for planning purposes, performers may estimate option execution to be in Q4FY16. Proposers should populate their program schedule with these minimum deliverables and supplement this list with additional deliverables/material to be presented at each review, in accordance with their unique program schedule and development approach.

Table 3. SXCT Phase II Technology Maturation Reviews and Deliverables

Event Due Date Deliverables Location

Kickoff Meeting 0 MAA Review briefings Updated SDDP

DARPA

Vicinity

Progress Reviews 3, 9, and

15 MAA

Review briefings Updated SDDP

Performer Location

Evaluation Experiments

6, 12, and

17 MAA

Attendance at experiment Experiment Test Report

Government-defined Site

Monthly R&D Status Reports: Technical & Financial

1, 2, 3, … MAA

Monthly R&D Status Reports:

Technical & Financial N/A

Final Report 12 MAA Final Report N/A

F.1. Phase II Kick-off Meeting A kickoff meeting will be held at or near the DARPA facility. The objective of this meeting is to discuss the program plan and approach, and provide feedback to guide the performer in executing their Phase II effort. The performer shall present their plans for maturing the technology and outline an Experiment Plan that describes how best DARPA can evaluate the proposed capability.

F.2. Progress Reviews During Phase II, three progress reviews will be held to assess the performer’s approach to technology maturation. The objectives of these reviews are to assess the performer’s program approach and progress, and allow DARPA an opportunity to provide guidance. During each of these reviews, the performer will present updates to the Phase II SDDP. It shall contain a detailed evaluation plan for the SXCT Evaluation Experiments, to include test objectives, test metrics, test schedules, test resources, safety plans, and test reporting. The SDDP shall also describe the approach to mitigating risk and meeting the program success metrics.

F.3. Evaluation Experiments The performer will participate in three Evaluation Experiments that demonstrate efficacy of their developed capability. The experiments will be run by DARPA at a DARPA-specified site. For planning purposes, performers may assume the experiments will occur at Fort Benning, GA. Each experiment will evaluate the technology against the program success metrics, using live rifle squad operations in a complex, urban environment. The performer shall provide a test report assessing system performance against the SXCT program success metrics.

F.4. Monthly R&D Status Reports & Final Report

The performer will submit monthly technical, financial, and schedule status reports that highlight overall team work and progress. The performer will be required to submit a Final Report upon contract completion. Report shall be delivered via e-mail to DARPA directly in addition to any award distribution or online submission requirements.

II. Award Information

A. Awards Multiple awards are anticipated for each technical area. The amount of resources made available under this BAA will depend on the quality of the proposals received and the availability of funds. DARPA plans to invest up to $22.4M for Phase I (Base Period) concept development efforts. The current Phase II (Option) budget available for award is approximately $33.6M. If DARPA elects to continue the program into Phase II, DARPA may exercise multiple Phase II contract options to conduct technology maturation.

DARPA retains the right to award all, some, one, or none of the proposed Phase II options and may elect to fund only portions of a Phase II option based on transition opportunities, proposals received, and funding available.

The Government reserves the right to select for negotiation all, some, one, or none of the proposals received in response to this solicitation, and to make awards without discussions with proposers. The Government also reserves the right to conduct discussions if it is later determined to be necessary. If warranted, portions of resulting awards may be segregated into pre-priced options. Additionally, DARPA reserves the right to accept proposals in their entirety or to select only portions of proposals for award.

In the event that DARPA desires to award only portions of a proposal, negotiations may be opened with that proposer. The Government reserves the right to fund proposals in phases with options for continued work at the end of one or more of the phases.

Awards under this BAA will be made to proposers on the basis of the evaluation criteria listed below (see section labeled “Application Review Information”, Sec. V.), and program balance to provide overall value to the Government. The Government reserves the right to request any additional, necessary documentation once it makes the award instrument determination. Such additional information may include but is not limited to Representations and Certifications. The Government reserves the right to remove proposers from award consideration should the parties fail to reach agreement on award terms, conditions and cost/price within a reasonable time or the proposer fails to provide requested additional information in a timely manner. Proposals identified for negotiation may result in a procurement contract or other transaction, depending upon the nature of the work proposed, the required degree of interaction between parties, whether or not the research is classified as Fundamental Research, and other factors.

In all cases, the Government contracting officer shall have sole discretion to select award instrument type and to negotiate all instrument terms and conditions with selectees. Proposers are advised that if they propose grants or cooperative agreements, the Contracting Officer may select other award instruments, as he/she deems appropriate.

DARPA will apply publication or other restrictions, as necessary, if it determines that the research resulting from the proposed effort will present a high likelihood of disclosing performance characteristics of military systems or manufacturing technologies that are unique and critical to defense. Any award resulting from such a determination will include a requirement for DARPA permission before publishing any information or results on the program. For more information on publication restrictions, see the section below on Fundamental Research.

Some aspects of the SXCT program are classified. Instructions for requesting the classified addendum can be found in Section IV.A of this BAA.

B. Fundamental Research

It is DoD policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 established the national policy for controlling the flow of scientific, technical, and engineering information produced in federally funded fundamental research at colleges, universities, and laboratories. The Directive defines fundamental research as follows:

'''Fundamental research' means basic and applied research in science and engineering, the results of which ordinarily are published and shared broadly within the scientific community, as distinguished from proprietary research and from industrial development, design, production, and product utilization, the results of which ordinarily are restricted for proprietary or national security reasons."

As of the date of publication of this BAA, the Government expects that some program goals as described herein either cannot be met by proposers intending to perform fundamental research or the proposed research is anticipated to present a high likelihood of disclosing performance characteristics of military systems or manufacturing technologies that are unique and critical to defense. Therefore, the Government anticipates restrictions on the resultant research that will require the contractor to seek DARPA permission before publishing any information or results relative to the program.

Proposers should indicate in their proposal whether they believe the scope of the research included in their proposal is fundamental or not. While proposers should clearly explain the intended results of their research, the Government shall have sole discretion to select award instrument type and to negotiate all instrument terms and conditions with selectees. Appropriate clauses will be included in resultant awards for non-fundamental research to prescribe publication requirements and other restrictions, as appropriate.

For certain research projects, it may be possible that although the research being performed by the prime contractor is restricted research, a subcontractor may be conducting contracted fundamental research. In those cases, it is the prime contractor’s responsibility to explain in their proposal why its subcontractor’s effort is contracted fundamental research.

The following statement or similar provision will be incorporated into any resultant non-fundamental research procurement contract or other transaction:

There shall be no dissemination or publication, except within and between the contractor and any subcontractors, of information developed under this contract or contained in the reports to be furnished pursuant to this contract without prior written approval of DARPA’s Public Release Center (DARPA/PRC). All technical reports will be given proper review by appropriate authority to determine which Distribution Statement is to be applied prior to the initial distribution of these reports by the contractor. With regard to subcontractor proposals for Contracted Fundamental Research, papers resulting from unclassified contracted fundamental research are exempt from prepublication controls and this review requirement, pursuant to DoD Instruction 5230.27 dated October 6, 1987.

When submitting material for written approval for open publication, the contractor/awardee must submit a request for public release to the PRC and include the following information: (1) Document Information: document title, document author, short plain-language description of technology discussed in the material (approx. 30 words), number of pages (or minutes of video) and document type (e.g., briefing, report, abstract, article, or paper); (2) Event Information: event type (conference, principal investigator meeting, article or paper), event date, desired date for DARPA's approval; (3) DARPA Sponsor: DARPA Program Manager, DARPA office, and contract number; and

(4) Contractor/Awardee's Information: POC name, e-mail and phone. Allow four weeks for processing; due dates under four weeks require a justification. Unusual electronic file formats may require additional processing time. Requests may be sent either by-mail to prc@darpa.mil or via 675 North Randolph Street, Arlington VA 22203-2114, telephone (571) 218-4235. Refer to the following for link for information about DARPA’s public release process:

http://www.darpa.mil/NewsEvents/Public_Release_Center/Public_Release_Cente r.aspx .

III. Eligibility Information

All responsible sources capable of satisfying the Government's needs may submit a proposal that shall be considered by DARPA.

A. Eligible Applicants

1. Federally Funded Research and Development Centers (FFRDCs) and Government entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions: (1) mailto:prc@darpa.mil http://www.darpa.mil/NewsEvents/Public_Release_Center/Public_Release_Center.aspx http://www.darpa.mil/NewsEvents/Public_Release_Center/Public_Release_Center.aspx

FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector. (2) FFRDCs must provide a letter on official letterhead from their sponsoring organization citing the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and their compliance with the associated FFRDC sponsor agreement and terms and conditions. This information is required for FFRDCs proposing to be prime contractors or subcontractors. Government entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority and contractual authority, if relevant, establishing their ability to propose to Government solicitations. At the present time, DARPA does not consider 15 U.S.C. § 3710a to be sufficient legal authority to show eligibility. While 10 U.S.C.§ 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility. DARPA will consider FFRDC eligibility submissions on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer.

All proposers are expected to address transition (see ”Relevance to DARPA Mission” in section IV.B); transition is part of the evaluation criteria in section V.A. However, given their special status, FFRDCs should describe how and when a proposed technology/system will transition to which Non-FFRDC organization(s).

2. Non-U.S. organizations and/or individuals may participate to the extent that such participants comply with any necessary nondisclosure agreements, security regulations, export control laws, and other governing statutes applicable under the circumstances.

B. Procurement Integrity, Standards of Conduct, Ethical Considerations, and Organizational Conflicts of Interest

Current federal employees are prohibited from participating in particular matters involving conflicting financial, employment, and representational interests (18 U.S.C. §§ 203, 205, and 208). Once the proposals have been received, and prior to the start of proposal evaluations, the Government will assess potential conflicts of interest and will promptly notify the proposer if any appear to exist. The Government assessment does

NOT affect, offset, or mitigate the proposer’s responsibility to give full notice and planned mitigation for all potential organizational conflicts, as discussed below.

Without prior approval or a waiver from the DARPA Director, in accordance with FAR 9.503, a contractor cannot simultaneously provide scientific, engineering, technical assistance (SETA) or similar support and also be a technical performer. As part of the proposal submission, all members of the proposed team (prime proposers, proposed subcontractors, and consultants) must affirm whether they (their organizations and individual team members) are providing SETA or similar support to any DARPA technical office(s) through an…