HR001117S0009.pdf

Broad Agency Announcement Secure Handhelds on Assured Resilient networks at the tactical Edge (SHARE)

STRATEGIC TECHNOLOGY OFFICE

HR001117S0009

23 January 2017

Secure Handhelds on Assured Resilient networks at the tactical Edge (SHARE)

TABLE OF CONTENTS

PART II: FULL TEXT OF ANNOUNCEMENT

1. FUNDING OPPORTUNITY DESCRIPTION

1.1 PROGRAM OVERVIEW

1.2 PROGRAM METRICS

2. AWARD INFORMATION

2.1 FUNDAMENTAL RESEARCH

3. ELIGIBILITY INFORMATION

3.1 ELIGIBLE APPLICANTS

3.2 ORGANIZATIONAL CONFLICTS OF INTEREST

3.3 COST SHARING/MATCHING

3.4 COLLABORATIVE EFFORTS

4. APPLICATION AND SUBMISSION INFORMATION

4.1 ADDRESS TO REQUEST APPLICATION PACKAGE

4.2 CONTENT AND FORM OF APPLICATION SUBMISSION

4.3 FORMATTING CHARACTERISTICS

4.4 SUBMISSION DATES AND TIMES

4.5 OTHER SUBMISSION REQUIREMENTS

5. APPLICATION REVIEW INFORMATION

5.1 EVALUATION CRITERIA

5.2 REVIEW AND SELECTION PROCESS

6. AWARD ADMINISTRATION INFORMATION

6.1 SELECTION NOTICES AND NOTIFICATIONS

6.2 ADMINISTRATIVE AND NATIONAL POLICY REQUIREMENTS

6.3 REPORTING

6.4 ELECTRONIC SYSTEMS

7. AGENCY CONTACTS

8. OTHER INFORMATION

8.1 INTELLECTUAL PROPERTY

9. APPENDIX 1: PROPOSAL SLIDE SUMMARY

10. APPENDIX 2: VOLUME 1 COVER SHEET TEMPLATE

11. APPENDIX 3: VOLUME 2 COVER SHEET, CHECKLIST AND SAMPLE

TEMPLATES

PART I: OVERVIEW INFORMATION

Federal Agency Name – Defense Advanced Research Projects Agency (DARPA), Strategic Technology Office

Funding Opportunity Title – Secure Handhelds on Assured Resilient networks at the tactical Edge (SHARE)

Announcement Type – Initial Announcement Funding Opportunity Number – HR001117S0009 Catalog of Federal Domestic Assistance Numbers (CFDA) - Not applicable Dates o Posting Date January 23, 2017 o Proposal Due Date March 15, 2017 o BAA Closing Date August 15, 2017 o Proposer Day Date January 31, 2017

Concise description of the funding opportunity - DARPA is soliciting innovative research proposals to develop security and networking architectures and software for sharing multilevel secure information across wireless networks for direct tactical cooperation between U.S. and coalition partners.

Anticipated total amount of money to be awarded – $30.5 million Anticipated individual awards - Multiple awards are anticipated.

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

Any cost sharing requirements – N/A Agency contact o Points of Contact The BAA Coordinator for this effort may be reached at:

HR001117S0009@darpa.mil

DARPA/STO

ATTN: HR001117S0009

675 North Randolph Street Arlington, VA 22203-2114 mailto:HR001117SXXXX@darpa.mil

PART II: FULL TEXT OF ANNOUNCEMENT

1. FUNDING OPPORTUNITY DESCRIPTION

This publication constitutes a Broad Agency Announcement (BAA) as contemplated in Federal Acquisition Regulation (FAR) 6.102(d)(2) and 35.016 and 2 CFR § 200.203. Any resultant award negotiations will follow all pertinent law and regulation, and any negotiations and/or awards for procurement contracts will use procedures under FAR 15.4, Contract Pricing, as specified in the BAA.

The Defense Advanced Research Projects Agency (DARPA) is soliciting innovative proposals in the following technical area: tactical secure multilevel information sharing networks. 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.

1.1 PROGRAM OVERVIEW

The Secure Handhelds on Assured Resilient networks at the tactical Edge (SHARE) program seeks to develop security and networking architectures and software for sharing multilevel secure information across wireless networks for direct tactical cooperation between U.S. and coalition partners. SHARE will deliver a demonstration of U.S. and coalition coordinated operations using secure tactical edge information sharing in an operationally-relevant exercise.

Several technology challenges limit tactical edge, small unit information sharing between coalition and U.S. forces. Current approaches to coalition information sharing depend on large data centers that are not feasible at the tactical edge, need separate equipment (e.g., laptops) for each secure information enclave or trusted group, and are impeded by legacy solutions that require secure network technology that uses end-to-end connections. These heavyweight solutions to U.S. military security requirements result in long deployment timelines measured in months to years, as well as limited information sharing with coalition partners who cannot support U.S. system security requirements. Various after action reports from coalition operations and exercises demonstrate gaps in existing information sharing capabilities that impede coordinated tactical operations.

SHARE will provide the rapidly deployable and secure information sharing technology needed to conduct coordinated operations with coalitions and other partners. Key SHARE program goals are:

Moving trusted security management functions from large, complex data centers to distributed, tactical commercial handheld devices.

Creating a resilient architecture for secure tactical networks.

Rapid, dynamic configuration of sharing rules and user authorities throughout the network.

SHARE is a 36-month program based around three technology focus areas that pursue each of these goals. SHARE uses a three phase development strategy in which Phase 1 concentrates on technology development efforts, Phase 2 on prototype development, and Phase 3 on integration activities. Phase 1 is the base effort, while Phases 2 and 3 are to be proposed as fully-priced option efforts. This BAA solicits responses from proposers that address all three phases of the program. Within the three phases of the program, there are three technology focus areas, and each proposal submitted for consideration under this BAA shall address all focus areas. Based on the successful completion of the milestones for each phase, DARPA will exercise the proposed option periods of performance for the performer(s) that best satisfy SHARE objectives.

Detailed program milestones for each phase and focus area are provided below.

Background

Secure Handhelds on Assured Resilient networks at the tactical Edge (SHARE) will develop innovative approaches, including new networking technology and software-based security on commercial devices in order to facilitate the information flow that is the basis for effective operational coordination between U.S. and coalition forces. Three critical challenges will be addressed by the SHARE program:

1. The information sharing envisioned in this effort will be with and between U.S. and/or coalition partners and thus requires the capacity to cross between security and/or trust groups.

The current architecture is built around specialized military radios at the tactical level and/or reach back to large, centralized data centers in rear areas (outside of the combat zone) for managing data security labeling and access privileges between trusted groups1. Use of commercial handheld devices, which allows sharing information locally at the tactical level, helps overcome the logistical and cost problems with current approaches that require deploying and communicating with large, specialized systems. SHARE will distribute security management functions to trusted tactical devices on the edge of the network.

2. Information sharing also requires secure tactical networking capabilities. Current approaches are based around IP VPN (Virtual Private Network) technologies, which exhibit poor resilience in tactical wireless networking environments characterized by high packet error rates, because the VPN end-to-end connections need to be reestablished after every packet loss. New approaches, such as Named Data Networking (NDN), most recently developed within the NSF Future Internet Architectures (FIA) initiative, promise to provide both enhanced resilience and security by combining store-and-forward capabilities with secure individual packets.

3. The deployment of coalition networks, where each network is built for a particular set of partners with customized, manually configured sharing rules, has traditionally taken months to years. These timelines can be shortened by automating the configuration and verification of sharing rules and user authorities throughout the network.

SHARE seeks novel technologies and system approaches to create the following:

Multilevel secure software on handheld devices to distribute trusted security management from data centers to the tactical edge, Resilient secure networks for the tactical edge, leveraging research from academic and industry testbeds, and

1 For example, the U.S. Battlefield Information Collection and Exploitation System (US BICES).

Automated configuration and management of information sharing to enable rapidly deployable systems.

The integration of these technologies on handheld devices will create a revolutionary tactical capability for U.S. and coalition forces.

Technical Focus Areas

DARPA seeks innovative proposals that address all of the following three technical focus areas:

Focus Area 1: Distributed Tactical Security Management

A tactical environment security architecture must address two challenges,

(a) how to distribute, synchronize, apply, and manage application security rules and user privileges in tactical networks and devices, and

(b) how to secure handheld mobile devices with sufficient trust to host distributed security functionality.

To address the first challenge, SHARE seeks to develop technologies and policy tools, integrated onto handheld devices, to share information between trusted groups. Performer systems must be able to process content at multiple security levels, and manage user identities and application access/authorization privileges. Management of data security levels by both manual and automated methods (e.g., preconfigured applications, preconfigured rules, or using techniques such as machine learning) is desired. The approach should be suitable for use by warfighters in a tactical environment. Because this is a distributed architecture, the systems and rulesets must be capable of being securely configured remotely from across the network while also being secure in the event the device is lost, or a user tries to gain unauthorized access.

To address the second challenge, SHARE seeks to develop a secure multilevel operating system and distributed application security framework for mobile handheld devices, e.g. Android tablets and smart phones, suitable for use in a tactical environment. Performer operating systems must be able to isolate and protect content at multiple security levels, as well as securely integrate with networking protocol software that supports multilevel capabilities. Performers should provide an application security framework that allows applications to run at the distinct security levels. It is further anticipated that the performer will need to implement mandatory and discretionary access and authentication controls to provide security checks and record actions in auditable logs.

Performers should also address data-at-rest risks associated with devices supporting multilevel secure architectures.

Because the SHARE program will create revolutionary new approaches for information sharing at multiple security levels, proposers should plan to support interaction with relevant agencies.

New concepts for information sharing processes and rules for tactical environments to prevent leakage (e.g., limiting access outside the tactical environment) are desired.

Performers should be able to demonstrate the ability to exchange the required multilevel secure information across an entire network as well as label information at the appropriate security levels without any errors (leakage). Further, the performer’s multilevel security approach should support four or more simultaneous security enclaves per device, and will be analyzed and validated by the SHARE Government Team (test and evaluation team).

It is envisioned that proposers will offer a variety of solutions with regard to the mobile handheld device hardware and software. For example, viable approaches include building upon operating systems such as Security Enhanced Linux (SELinux) or Security Enhanced Android (SE Android) and the capabilities provided by the National Security Agency’s (NSA) Suite B and Commercial Solutions for Classified (CSfC), or alternatively, building upon handhelds with single or multiple virtual machines (VM) performing the various tasks required to meet SHARE program objectives. As detailed in various DoD handheld programs, preferred mobile devices should include characteristics such as the ability to present information in an easily understandable, simple, and intuitive graphical user interface (GUI), enable single-digit minute engagements, and allow easy access to I/O and button placement. It is envisioned that mobile devices will be handled with and without gloves allowing for easy manipulation of on screen data.

Focus Area 2: Resilient Secure Networks

A resilient and secure network for the tactical environment must address two challenges,

(a) the lack of resilience in secure tactical networks built around IP VPN technology, and

(b) adapting technical applications currently designed for these unreliable network architectures.

To address the first challenge, SHARE is seeking to develop new networking technologies that inherently support the ability to exchange information at multiple security levels and provide resilient secure store and forward capabilities rather than brittle end-to-end connections. An example is Named Data Networking (NDN), which was developed through the NSF Future Internet Architectures (FIA) program. Performers should build upon these foundations, and enhance the protocols and implementations as needed for U.S. and coalition tactical use.

To address the second challenge, SHARE is seeking to adapt existing applications that have been designed for current networking technologies to new technologies such as NDN. The application software effort should focus on the interface between the network protocols and the application itself, and build upon existing applications (e.g. Android Tactical Assault Kit (ATAK)) that implement critical tactical capabilities such as Command and Control (C2), tactical operations support, and imagery distribution.

The performer’s networking software must include both the software that resides in the handheld devices and the software needed to manage and route the data in the network.

The network security approach should be stable and resilient, even if the physical network is not.

Performers should be able to demonstrate reliable communication under conditions of 10% packet error rate or worse, and deliver 50% or better goodput with 5% packet error rates. The security of the networking solution will be evaluated by the SHARE Government Team and should provide assurances equivalent to the National Institute of Standards and Technology (NIST) SP 800-77 standard for IP VPNs.

Focus Area 3: Secure Configuration Automation

An automated and secure configuration system must address two challenges,

(a) the complex task of managing users, groups, rules, and authorities across multiple security enclaves, and

(b) rapid configuration of the SHARE system of systems for new coalitions.

To accomplish this, performers should integrate the software technologies from Focus Areas 1 and 2, along with the additional algorithms and software needed to configure and manage distributed security at the tactical edge. This automation software will provide the capability to automate and streamline the management of information sharing rules and user authorities throughout the network.

The final system will create the ability to support multiple trusted groups per network and the ability to deploy a network with new partners within 48 hours. This effort will culminate in a final demonstration of SHARE in an operationally representative coalition exercise.

Recognizing the challenges associated with accrediting systems for operational use, proposers should identify the areas where they believe their solution will be compliant with DoD policy requirements (e.g. Security Technical Implementation Guides (STIG) and Information Assurance Software Requirements Documents (IASRD)). Noting this, however, SHARE values innovation in the aforementioned focus areas, so it is understood that the proposed solution may not be fully compliant with policy requirements. Proposals should identify areas of non-compliance and discuss how the risks associated with non-compliance can be addressed either during or after DARPA program execution.

The SHARE program must endeavor to ensure releasability to multiple coalition partners.

Therefore, the ability to mitigate the risks and impact of International Trade and Arms Regulations (ITAR) is critical. Proposers should describe how they will meet program objectives while maintaining hardware and software functionality, e.g., by adhering to preferred open system modular development processes that are in compliance with or do not invoke ITAR restrictions.

A long term goal of the SHARE program is the ability to sustain, adapt, and integrate new capabilities through the inclusion of third party development of both hardware and software.

Therefore, proposers should describe how their hardware and software approach might live beyond the DARPA funded effort.

SHARE will attempt to identify transition partners early in the program; therefore, advocates for existing or emerging DoD tactical handheld device programs of record and other identified stakeholders will be invited to participate in all Phases of program development from program kickoff to final demonstration in order to better understand the technology and operational application.

Program Structure

An overview of the SHARE program structure is depicted in Figure 1. The detailed relationship between the focus areas and Phases is outlined in the sections below.

Figure 1 SHARE Program Structure

1.1.1 Phase 1

Objective Deliverable Distributed multilevel secure management on mobile handhelds

CDR-level design that validates the technology and application security approach, and demonstrations of relevant technologies at TRL 4

New resilient networking architecture for the tactical edge

Networking lab experiment under tactical edge conditions demonstrating technologies at TRL 4

Software to automate management of information sharing and users

PDR-level design of overall system architecture, and demonstrations of relevant technologies at TRL 3

Table 1 – Phase 1 Objectives

Phase 1 is the 12-month base effort and will concentrate on developing technology in each of the focus areas as listed in Table 1. In the area of distributed tactical security management, handheld device software will be developed and portions demonstrated at TRL (Technology Readiness

Level) 4, and the approach will be validated at a critical design review (CDR). In the area of new resilient networking architectures, software will be developed and demonstrated at TRL 4, and lab experiments will be performed under tactical network conditions. In the area of security configuration automation, a system architecture will be designed and portions demonstrated at TRL 3, and a preliminary design review (PDR) will be successfully completed. It is anticipated that two performers will be selected for Phase 1.

In maturing these enabling technologies, the performer is expected to determine how these might evolve into the desired tactical system architecture. Phase 1 will define the security environment, and study and propose steps towards system accreditation. As is the case in all Phases of the program, it is important to engage potential stakeholders regarding policies, user needs, and concepts of operations.

The Phase 1 events and milestones are listed in Table 2. At the end of Phase 1, at a minimum, performer(s) are expected to demonstrate the ability of their individual technical elements to achieve the program objectives as identified in Table 1 and the metrics in Table 11.

Phase 1 performers will implement their technologies in an Engineering Development Model (EDM) configured for network testing to be performed towards the end of Phase 1. The EDM will include the network protocol and application software being developed in Focus Area 2.

The tests will be performed in a laboratory environment and will be assessed by the SHARE Government Team. Phase 1 performers will also deliver a CDR-level design for Focus Area 1 that validates the chosen handheld hardware platform and application security approach, and a PDR-level design for Focus Area 3 for the configuration automation approach and the overall system architecture. Phase 1 performers should demonstrate all Phase 1 objectives listed in Table 1. The deliverables schedule is listed in Table 3.

Proposers are expected to provide the software development plan they will use during the life of the program, which should include details such as management tools, software development models, and timelines (e.g., for spirals or sprints).

Proposers are expected to provide the necessary detail to validate the intended Phase 1 testing environment. The proposer should comment on the testing environment’s ability to support interaction with potential stakeholders, e.g., for demonstration and training purposes. It is envisioned that this will facilitate user feedback regarding the ability of the performer’s hardware and software to support tactical edge information sharing. In addition, this environment might help support the data requirements necessary to inform overall system accreditation.

Event Venue Month After Contract Award

Program Kickoff Arlington, VA 1 Quarterly Program Review (QPR) 1 Performer facility 3 QPR 2 Performer facility 6 QPR 3 Performer facility 9 EDM Demonstrations in Lab Performer facility 11

Table 2 – Phase 1 Events and Milestones

At the conclusion of Phase 1, the Government may elect to exercise the option for select performer(s) to transition to Phase 2 based on the metrics listed in Table 12.

Deliverable Format Months After Contract Award

Initial Software Development Plan Document Due at Kickoff Initial System Architecture Design Document 5 Initial Software Design Document Document 5 Initial Network Design Document Document 5 Phase 1 Demonstration and Assessment of EDM

Slide presentation, demonstration

Phase 1 Final Report Document 12 Incrementally Functional Software Builds

Commented source code check-in, executables delivered

Source code due 1 week prior to QPRs and EDM

Demonstration

Table 3 – Phase 1 Deliverable Schedule

1.1.2 Phase 2

Objective Deliverable Integrated multilevel handheld software and new networking architecture

Field experiment on handhelds demonstrating technology at TRL 5

System architecture compatible with handheld and network approach

CDR-level design of system architecture and demonstration of technology at TRL 4

Table 4 – Phase 2 Objectives

Phase 2 is a 12-month option that will concentrate on developing prototypes that integrate the software from the distributed tactical security management and secure resilient networking architectures focus areas, as listed in Table 4. During Phase 2, performers will build on their Phase 1 progress to develop end-to-end prototype systems and applications. These prototypes will be evaluated through field experimentation on handheld devices, reaching TRL 5. Phase 2 experimentation will demonstrate the secure information sharing capability necessary to plan and execute operations in all phases of a tactical operation. The software being developed in the security configuration automation focus area will be refined and matured to TRL 4. Continued engagement with the user community throughout Phase 2 will identify transition partners and aid in enabling and assessing the desired operational impact.

Deliverables from Phase 2 are listed in Table 6. It is anticipated that during Phase 2, the performer(s) will integrate their efforts from Focus Areas 1 and 2 into a SHARE end-to-end prototype. This prototype will be assessed by the SHARE Government Team towards the end of Phase 2. Additionally, Phase 2 performer(s) will undergo a successful CDR including presentation of the design of their overall system architecture. Phase 2 events and technology milestones are listed in Table 5.

In addition to the ability to meet the Phase 2 objectives in Table 4, desirable capabilities include the following:

Integrated networking and multilevel secure technology on the selected hardware and operating system, including application software to be identified during the program Ability to support ad-hoc coalitions with changing membership through the rapid creation and deployment of a multilevel, tactical edge information sharing network Ability of the system to push and pull data from information and intelligence sources

(commercial and government) to be identified during the program Extent to which the system complies with existing cross-domain solutions (e.g., those used by US BICES) and can operate in multiple trusted groups Extent to which the system complies with existing DoD security requirements Extent to which the system user authentication and authorization scheme possesses the flexibility to comply with various U.S. and coalition requirements Ability to support inclusion of multiple and new applications

Event Venue Months After Option Award

Phase 2 Kickoff Arlington, VA 1 QPR 1 Performer facility 3 QPR 2 Performer facility 6 QPR 3 and Laboratory Prototype End-to-End Experimentation

Performer facility 9

Tactically Relevant Demonstration of Prototype

Government range, e.g., Fort A.P. Hill

Table 5 – Phase 2 Events and Milestones

Using the data gathered throughout Phase 2, including the SHARE Government Team’s assessment of the Phase 2 demonstration based on the metrics listed in Table 12, it is anticipated that one performer will transition to Phase 3.

Deliverable Format Months After Option Award Final System Architecture Design Document 3 Final Software Design Document Document 3 Final Network Design Document Document 3 Initial System Management Document

Document 3

QPR Presentation Slide presentation 3, 6, 9 Phase 2 Demonstration and Assessment

Slide presentation, demonstration

Phase 2 Final Report Document 12 Incrementally Functional Software Builds

Commented source code check-in, executables delivered

Source code due 1 week prior to QPRs and Demonstration of

Prototype Table 6 – Phase 2 Deliverable Schedule

1.1.3 Phase 3

Objective Deliverable Fully integrated handheld, network, and management system

Field experimentation and demonstration of integrated system at TRL 6

Table 7 – Phase 3 Objectives

Phase 3 is a 12-month option that will concentrate on overall system integration, experimentation, and demonstrations with coalition partners to meet the objectives as described in Table 7. The handheld platform and networking prototype developed in Phase 2 will be refined and integrated with the security configuration automation software to create a system at TRL 6 that includes security management with rapid deployment capabilities that meets the metrics listed in Table 13. The final Phase 3 demonstration will be an operationally-relevant exercise that showcases the ability to support U.S. and coalition coordinated operations through secure tactical edge information sharing.

Event Venue Months After Option Award

Phase 3 Kickoff Arlington, VA 1 QPR 1 Performer facility 3 QPR 2 Performer facility 6 QPR 3 and Final Configuration End-to-End Experimentation

Performer facility 9

Final Configuration Demonstration in Coalition Exercise

U.S. or coalition partner military range

Table 8 – Phase 3 Events and Milestones

The Phase 3 deliverables are listed in Table 9. The final Phase 3 demonstration will be an experiment conducted in an operationally representative coalition exercise or limited user evaluation that showcases the ability of the SHARE technology to support U.S. and coalition coordinated operations. An example of the final demonstration objective is shown in Figure 2.

This illustrates an integrated system, running over several types of networks (e.g. LTE, Wi-Fi, U.S. military networks), with the ability to provide the secure information sharing required to plan and execute exercise-specific coalition operations. Demonstration in a real world coalition exercise will also highlight the ability to quickly establish the networking infrastructure necessary to securely share time sensitive battlespace awareness information. Performers will be expected to provide at least 50 handheld devices for this demonstration, plus any supporting commercial network and server equipment. The Government will provide tactical radios as needed. While it is useful for proposers to identify potential exercises and the rationale for their selection, it is anticipated that the Government support team will work closely with performers to finalize event identification and coordinate the inclusion of SHARE technologies into the event.

For budgeting purposes, performers should assume that the final demonstration will be held in conjunction with an EUCOM or PACOM exercise, and will last for approximately two weeks – one week for setup and one week for the exercise. Note that performers may require security clearances at the SECRET level to participate in these exercises.

Performers should plan to deliver SHARE software releases that are structured and packaged with sufficient documentation to enable a device vendor, network designer, or application writer to develop their specific technologies without participation or technical support by the initial SHARE design team. Proposals that use Government or open source code and/or Government repositories such as DI2E (Defense Intelligence Information Enterprise) will be preferred.

The Government encourages proposals that, to the greatest extent possible, are free of IP and data rights restrictions as this will allow for an easier transition at the conclusion of the program.

Performers should provide a good faith representation that they either own or possess appropriate licensing rights to all other intellectual property that they expect to use for the SHARE program.

Additionally, proposers shall provide a short summary for each item asserted with less than unlimited rights that describes the nature of the restriction and the intended use of the intellectual property in the conduct of the proposed research.

Figure 2 – Demonstration Objective: Resilient exchange of sensitive multilevel secure information using handheld devices

Deliverable Format Months After Option Award System Integration Plan Document 3 Test Plan Document 3 Final System Management Document

Document 3

QPR Presentation Slide presentation 3, 6, 9 Final Demonstration and Assessment

Slide presentation, demonstration, raw data

Program Final Report Document 12 Incrementally Functional Software Builds

Commented source code check-in, executables delivered

Source code due 1 week prior to QPRs and 1 month prior to Final

Demonstration Table 9 – Phase 3 Deliverable Schedule

1.1.4 Schedule

The SHARE program is planned as a three phase, 36 month effort with the phases evenly divided over the life of the program as seen in Figure 3. This single unclassified BAA solicits proposals discussing required analysis, methods, technical justification, and the statement of work necessary to create innovative solutions that satisfy overall program objectives. The program will consist of a base effort of 12 months for Phase 1 and two 12-month Options for Phases 2 and

3. As mentioned in Section 1, DARPA will exercise the proposed option period of performance for each respective performer(s) that best satisfies SHARE objectives.

Figure 3 – SHARE Schedule

1.1.5 Government Furnished Equipment, Information, and Resources

The following equipment and resources will be provided/funded by the Government for use during the final assessment and demonstration of Phase 3.

Government off-the-shelf (GOTS) application software to be specified during the program DoD security requirements and U.S. and coalition user authentication and authorization requirements as needed during the program Tactical radios for use during the final assessment and demonstration, quantity 3 total Military facility for final demonstration in coalition exercise - Government will arrange and provide funding for access and facilities

Table 10 – Government Furnished Equipment, Information, and Resources

If any additional Government Furnished Equipment or resources are requested by the performer, these should explicitly be described in the proposal along with a rough order of magnitude of expected costs.

1.2 PROGRAM METRICS

In order for the Government to evaluate the effectiveness of a proposed solution in achieving the stated program objectives, proposers should note that the Government hereby promulgates the following program metrics that may serve as the basis for determining whether satisfactory progress is being made to warrant continued funding of the program. Although the following program metrics are specified, proposers should note that the government has identified these goals with the intention of bounding the scope of effort, while affording the maximum flexibility, creativity, and innovation in proposing solutions to the stated challenges.

Proposals should cite the quantitative and qualitative success criteria that the proposed effort will achieve by the time of each Phase’s program metric measurement. Overall program metrics, broken out by focus area, are given in Tables 11, 12, and 13. Proposers should be able to meet or exceed all relevant metrics at the end of each Phase. Failure to meet the metrics may result in program termination or down-scoping.

Tests and demonstrations towards the end of each Phase are intended to (a) assess system performance, (b) determine which performers and their technologies from each technical focus area successfully achieved program objectives and technical milestones, and (c) engage with a variety of key stakeholders to obtain feedback that can influence program direction, system functionality/attributes, operational applicability, and compliance with DoD/NSA standards (to the extent possible given the technical readiness level of the technology).

Focus Area Metric Cross trust group sharing Ability by untrained users to share across security levels with no leakage using application software

Distributed Tactical Security

Management Device security Four simultaneous security enclaves per device Table 11 – SHARE Focus Area 1 Metrics

Focus Area Metric Resilience Reliable communication with > 10% PER

> 50% goodput with 5% PERResilient Secure Networks Security Packet-level security

(equivalent to NIST SP 800-77 for IPsec VPNs) Table 12 –SHARE Focus Area 2 Metrics

Focus Area Metric Number of trusted groups supported

4 per local networkSecurity Configuration Automation Time to deploy new partner < 48 hours

Table 13 –SHARE Focus Area 3 Metrics

1.2.1 Government Team

At the end of each Phase, the SHARE program Government Team will help assess the performance of the performer’s solution. The SHARE Government Team will comprise technical representatives from multiple Government agencies with a vested interest in the transition of the SHARE program. Each assessment will independently validate the performer’s data and benchmark solution performance. The SHARE Government Team will also conduct user trials to independently assess the usability of applications.

The intent of the SHARE Government Team is to stay abreast of program development status and conduct a fully independent validation and verification of performer solutions. Therefore, continuous collaboration between performer integrated product teams (IPT) and the SHARE Government Team throughout the development process is of importance and should be reflected in the proposal. Verification includes repeating the performer’s training and testing method to verify that the Government is able to reproduce the performer’s results on the data sets used by the performer. Validation will be conducted by repeating the training and testing sequences using a sequestered data set that has not been provided to the performer. Government validation on independent but statistically similar data sets will ensure that the resulting performance estimates are accurate.

2. AWARD INFORMATION

Multiple awards are anticipated. The amount of resources made available under this BAA will depend on the quality of the proposals received and the availability of funds.

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, as applicable. 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 (see Section 6.2.8, “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/or cost/price within a reasonable time, and the proposer fails to timely provide requested additional information. 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.

Proposers looking for innovative, commercial-like contractual arrangements are encouraged to consider requesting Other Transactions. To understand the flexibility and options associated with Other Transactions, consult www.darpa.mil/work-with-us/contract-management#OtherTransactions.

In all cases, the Government contracting officer shall have sole discretion to select award instrument type, regardless of instrument type proposed, and to negotiate all instrument terms and conditions with selectees. 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.

2.1 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 defines fundamental research as follows:

http://www.darpa.mil/work-with-us/contract-management#OtherTransactions http://www.darpa.mil/work-with-us/contract-management#OtherTransactions

‘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 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 awardee2 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. This clause can be found at www.darpa.mil/work-with-us/additional-baa.

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

3. ELIGIBILITY INFORMATION

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

3.1 ELIGIBLE APPLICANTS

3.1.1 Federally Funded Research and Development Centers (FFRDCs) and Government Entities

FFRDCs FFRDCs are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions: (1) FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector. (2)

2 As used throughout this BAA, awardee refers to anyone who might receive a prime award from the Government, including recipients of procurement contracts, grants, cooperative agreements, Other Transactions, or any type of award. Subawardee refers to anyone who might receive a subaward from a prime awardee.

http://www.darpa.mil/work-with-us/additional-baa

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’s terms and conditions. This information is required for FFRDCs proposing to be awardees or subawardees.

Government Entities Government Entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations. 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.

Authority and Eligibility 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 and Government entity eligibility submissions on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer.

(1) Non-U.S. Organizations 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.

(2) Applicants Considering Classified Submissions For classified proposals, applicants will ensure all industrial, personnel, and information systems processing security requirements are in place and at the appropriate level (e.g., Facility Clearance Level (FCL), Automated Information Security (AIS), Certification and Accreditation (C&A), and any Foreign Ownership Control and Influence (FOCI) issues are mitigated prior to submission. Additional information on these subjects can be found at www.dss.mil.

3.2 ORGANIZATIONAL CONFLICTS OF INTEREST

FAR 9.5 Requirements In accordance with FAR 9.5, proposers are required to identify and disclose all facts relevant to potential OCIs involving the proposer’s organization and any proposed team member (subawardee, consultant). Under this Section, the proposer is responsible for providing this disclosure with each proposal submitted to the BAA. The disclosure must include the proposer’s, and as applicable, proposed team member’s OCI mitigation plan. The OCI mitigation plan must include a description of the actions the proposer has taken, or intends to take, to prevent the existence of conflicting roles that might bias the proposer’s judgment and to prevent the proposer from having unfair competitive advantage. The OCI mitigation plan will specifically discuss the disclosed OCI in the context of each of the OCI limitations outlined in FAR 9.505-1 through FAR 9.505-4.

Agency Supplemental OCI Policy In addition, DARPA has a supplemental OCI policy that prohibits contractors/performers from concurrently providing Scientific Engineering Technical Assistance (SETA), Advisory and Assistance Services (A&AS) or similar support services and being a technical performer.

Therefore, as part of the FAR 9.5 disclosure requirement above, a proposer must affirm whether the proposer or any proposed team member (subawardee, consultant) is providing SETA, A&AS, or similar support to any DARPA office(s) under: (a) a current award or subaward; or (b) a past award or subaward that ended within one calendar year prior to the proposal’s submission date.

If SETA, A&AS, or similar support is being or was provided to any DARPA office(s), the proposal must include:

The name of the DARPA office receiving the support;

The prime contract number;

Identification of proposed team member (subawardee, consultant) providing the support; and An OCI mitigation plan in accordance with FAR 9.5.

Government Procedures In accordance with FAR 9.503, 9.504 and 9.506, the Government will evaluate OCI mitigation plans to avoid, neutralize or mitigate potential OCI issues before award and to determine whether it is in the Government’s interest to grant a waiver. The Government will only evaluate OCI mitigation plans for proposals that are determined selectable under the BAA evaluation criteria and funding availability.

The Government may require proposers to provide additional information to assist the Government in evaluating the proposer’s OCI mitigation plan.

If the Government determines that a proposer failed to fully disclose an OCI; or failed to provide the affirmation of DARPA support as described above; or failed to reasonably provide additional information requested by the Government to assist in evaluating the proposer’s OCI mitigation plan, the Government may reject the proposal and withdraw it from consideration for award.

3.3 COST SHARING/MATCHING

Cost sharing is not required; however, it will be carefully considered where there is an applicable statutory condition relating to the selected funding instrument. Cost sharing is encouraged where there is a reasonable probability of a potential commercial application related to the proposed research and development effort.

For more information on potential cost sharing requirements for Other Transactions for Prototype, see http://www.darpa.mil/work-with-us/contract-management#OtherTransactions.

3.4 COLLABORATIVE EFFORTS

Collaborative efforts/teaming are encouraged.

4. APPLICATION AND SUBMISSION INFORMATION

4.1 ADDRESS TO REQUEST APPLICATION PACKAGE

This announcement, any attachments, and any references to external websites herein constitute the total solicitation. If proposers cannot access the referenced material posted in the announcement found at www.darpa.mil, contact the administrative contact listed herein.

4.2 CONTENT AND FORM OF APPLICATION SUBMISSION

4.2.1 Security and Proprietary Issues

NOTE: If proposals are classified, the proposals must indicate the classification level of not only the proposal itself, but also the anticipated award document classification level.

DARPA policy is to treat all submissions as source selection information (see FAR 2.101 and 3.104), and to disclose their contents only for the purpose of evaluation. Restrictive notices notwithstanding, during the evaluation process, submissions may be handled by support contractors for administrative purposes and/or to assist with technical evaluation. All DARPA support contractors performing this role are expressly prohibited from performing DARPA-sponsored technical research and are bound by appropriate nondisclosure agreements.

Submissions will not be returned. The original of each submission received will be retained at DARPA and all other non-required copies destroyed. A certification of destruction may be requested, provided the formal request is received at this office within 5 days after notification that a proposal was not selected.

a. Proprietary Information Proposers are responsible for clearly identifying proprietary information. Submissions containing proprietary information must have the cover page and each page containing such information clearly marked with a label such as “Proprietary”. NOTE: “Confidential” is a classification marking used to control the dissemination of U.S.