DARPA-BAA-13-07_(Insight_Phase_2)_-_Amendment_1.pdf

Broad Agency Announcement Insight Phase 2

DARPA-BAA-13-07

January 4, 2013

Amendment 1

Defense Advanced Research Projects Agency 675 North Randolph Street Arlington, VA 22203-2114

DARPA-BAA-13-07 Insight Phase 2 2

Table of Contents Part I: Overview

Part II: Full Text of Announcement

I. FUNDING OPPORTUNITY DESCRIPTION

II. AWARD INFORMATION

III. ELIGIBILITY

A. Applicants

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

C. Cost Sharing/Matching

D. Other Eligibility Requirements

IV. APPLICATION

A. Announcement

B. Proposals

C. Proprietary and Classified Information

D. Submission Instructions

E. Funding Restrictions

V. EVALUATION

A. Evaluation Criteria

B. Review and Selection Process

VI. AWARD ADMINISTRATION

A. Selection Notices

B. Administrative and National Policy Requirements

C. Reporting

D. Electronic Systems

VII. AGENCY CONTACTS

VIII. OTHER INFORMATION

A. Frequently Asked Questions (FAQs)

B. Collaborative Efforts/Teaming

C. Proposers’ Day

D. Submission Checklist

DARPA-BAA-13-07 Insight Phase 2 3

Part I: Overview

• Federal Agency Name: Defense Advanced Research Projects Agency (DARPA), Information Innovation Office (I2O)

• Funding Opportunity Title: Insight Phase 2

• Announcement Type: Amendment

• Funding Opportunity Number: DARPA-BAA-13-07

• Catalog of Federal Domestic Assistance Numbers (CFDA): Not Applicable

• Dates:

o Posting Date: see announcement on the Federal Business Opportunities

(FBO) website at www.fbo.gov o Proposal Closing Date: January 24, 2013, 12:00 noon (ET) o Proposers’ Day: December 18, 2012

• Anticipated Individual Awards: DARPA anticipates a single award of approximately

$80M.

• Types of Instruments that May be Awarded: Procurement contract or other transaction authority (OTA) agreement. No grants or cooperative agreements will be awarded.

• Technical POC: Mr. Benjamin F. Cutler, Program Manager (PM), DARPA/I2O

• BAA Email: InsightPhase2BAA@darpa.mil

• BAA Mailing Address:

DARPA/I2O

ATTN: DARPA-BAA-13-07

• Insight Program Page: http://www.darpa.mil/Our_Work/I2O/Programs/Insight.aspx

• I2O Solicitation Website:

http://www.darpa.mil/Opportunities/Solicitations/I2O_Solicitations.aspx mailto:InsightPhase2BAA@darpa.mil http://www.darpa.mil/Our_Work/I2O/Programs/Insight.aspx http://www.darpa.mil/Opportunities/Solicitations/I2O_Solicitations.aspx

DARPA-BAA-13-07 Insight Phase 2 4

Part II: Full Text of Announcement

I. FUNDING OPPORTUNITY DESCRIPTION

DARPA is soliciting innovative research proposals for an analytical framework for global integrated intelligence, surveillance, and reconnaissance (ISR). Proposed research should investigate innovative approaches that enable revolutionary advances in science or systems.

Specifically excluded is research that primarily results in evolutionary improvements to the existing state of practice.

This Broad Agency Announcement (BAA) is issued, and any resultant selections shall be made, using procedures under Federal Acquisition Regulation (FAR) Part 35.016. Any negotiations and/or awards shall use procedures under FAR 15.4, Contract Pricing, as specified in this BAA.

Proposals received in response to this BAA shall be evaluated in accordance with the evaluation criteria specified herein through a scientific review process.

DARPA BAAs are posted on the Federal Business Opportunities website (http://www.fbo.gov/).

Introduction

Today's military intelligence analysts are faced with the monumental and escalating task of handling massive volumes of complex data from multiple sources. The data must be evaluated, correlated, and ultimately used to support a commander's time-critical decisions and actions.

To enhance analysts’ ability to more effectively and efficiently process information, the Insight program is developing an adaptable, integrated human-machine Exploitation and Resource Management (E&RM) System. Phase 1 of the program created the baseline system with an initial focus on counterinsurgency operations; Phase 2 will mature the Phase 1 capabilities and add additional ones to broaden the system’s applicability to expanded mission spaces (see detailed descriptions of Phase 1 functions/capabilities and Phase 2 objectives outlined below).

Through the development of semi- and fully automated technologies, the E&RM System will provide the following real-time capabilities in direct support of deployed forces:

• combination, analysis, and exploitation of information across multiple sources, including imaging sensors, non-imaging sensors, and other sources;

• efficient management of sensor tasking; and

• detection and identification of threats through the use of behavioral discovery and prediction algorithms.

The E&RM System is comprised of four main components:

• Integration, Processing, and Data Archive Environment (IPDAE) – provides a central repository for all E&RM System components; manages and monitors the mapping of http://www.fbo.gov/

DARPA-BAA-13-07 Insight Phase 2 5 dynamic algorithms on the execution environment; and captures the pedigree of all products to support the reasoning behind algorithmic exploitation results;

• Adaptive Multi-source Exploitation System (AMES) – enriches and exploits available multi-source data;

• Collection and Resource Management (CRM) – provides a common operating picture (COP) of ongoing collections, generates service requests, and plans and allocates sensor taskings; and

• Unified all-source ISR Human-Machine Interface (HMI) – enables analysts to visualize information from multiple perspectives in such a way that it is readily discoverable, accessible, meaningful, and useful.

For developmental purposes, the E&RM System is supported by:

• a Physical Test Bed (PTB) – exercises the E&RM System's capabilities with real-time sensors and activities in the context of realistic military scenarios set against the backdrop of an operationally relevant environment; and

• a Virtual Environment (VE) test bed – provides the ability to scale to real world complexity, time, and space (which is not feasible to demonstrate in the PTB).

Figure 1 illustrates the high-level Insight architecture and how it interfaces with test beds and various information inputs.

Figure 1: Insight Architecture

The E&RM System ingests data and information. Data inputs are uninterpreted content such as unstructured text from open-source intelligence (OSINT) or raw pixel-based imagery of an electro-optical (EO) sensor. In contrast, information inputs provide an interpretation of the underlying data, ideally in a form that is standards-compliant. For example, tracks of vehicles observed by a Wide Area Motion Imagery (WAMI) sensor, entity descriptions provided by a

DARPA-BAA-13-07 Insight Phase 2 6 signals intelligence (SIGINT) sensor or human intelligence (HUMINT) source, or the structured content of a database (e.g., Combined Information Data Network Exchange). The E&RM System is designed to work with information inputs, although in select cases it can also process data inputs.

The E&RM System ingests information inputs in the form of metadata (e.g., source identifiers, time, and location; activities, tracks, detections, and entity descriptions; confidence, probability, and uncertainty metrics) from a broad range of external sources (e.g., imaging sensors, non-imaging sensors, other sources such as databases, and external analysts’ products). As the information inputs are received and processed by the E&RM System, new metadata is derived and products created, yielding knowledge and understanding about the situation at hand. The process of discovery and building the body of evidence continues as new information requirements are issued (or tasked) to information sources directly controlled by the E&RM System and new information requests are issued to information sources that are not.

Regardless of whether an information source is directly controlled, the E&RM System is able to receive information inputs from any source that is discoverable by the E&RM System.

Internally, the E&RM System maintains the pedigree of all information inputs, derived metadata, and products. This enables a commander to understand the basis for any conclusions reached by the E&RM System, and provides the ability to reach back across the federated architecture to access data (e.g., imagery) associated with any information inputs.

Just as external information is discoverable by the E&RM System, products that are produced by and reside within the E&RM System are also made available for discovery by external systems and analysts across attached networks. This bidirectional discovery process is facilitated by the use of existing and emerging community sensor and information reporting standards.

The E&RM System will operate across three execution environments (unclassified, Secret, Top Secret (TS), including Sensitive Compartmented Information (SCI)),either operating stand-alone or connected via appropriate guards certified and accredited under either Department of Defense Instruction (DoDI) 8510.01 (for collateral Secret) or Intelligence Community Directive (ICD) 503 (for SCI) requirements. All information feeds, and products generated from those feeds, will remain, at a minimum, at their original classification levels governed by their respective Security Classification Guides (SCGs).

Figure 2 illustrates an example of the E&RM System in an operational context.

DARPA-BAA-13-07 Insight Phase 2 7

Figure 2: Operational Concept1

Phase 1 Background

Phase 1 of the program focused on using the E&RM System in scenarios involving irregular warfare, with emphasis on counterinsurgency operations (e.g., identify and defeat insurgent networks). It concentrated on prioritizing sensors, computing power, and analytical capability – all in direct support of tactical brigades and battalions, in accordance with command priorities, within a wide area security mission framework.

Phase 1 of the program demonstrated:

• live, real-time, end-to-end source-to-analyst exercise of the entire E&RM System;

• the ability to ingest information from ground battle command systems;

• the ability to ingest information from and dynamically interact with space, air, and ground-based sources;

• sequence-neutral (out-of-order) ingestion and processing of information;

• the ability to persistently store, index, search, and retrieve ingested multi-source information, and then reason over it and present it to an analyst;

1 BFT: Blue Force Tracker; DCGS: Distributed Common Ground System; CPoF: Command Post of the Future; EO/IR: Electro- Optical/Infra-Red; GMTI: Ground Moving Target Indicator; HSI: Hyperspectral Imagery; RADAR: Radio Detection And Ranging;

SIGINT: Signals Intelligence; WAMI: Wide Area Motion Imagery

DARPA-BAA-13-07 Insight Phase 2 8

• the ability to detect enemy networks;

• the ability to track multiple vehicles through suspected drop-off and pick-up vignettes using real-time and forensic rewind of high value target (HVT) tracks;

• the ability to provide timely and relevant information to the tactical edge; and

• virtual replay and sensor simulation capabilities as invaluable tools for system integration and test.

The scope of Phase 1 included six Technical Areas (TAs): TAs 1 – 4 comprised the E&RM System and TAs 5 – 6 comprised the Test Bed as described in the Introduction above. The primary functions/capabilities developed by each TA during Phase 1 of the program are summarized in Table 1.

TA Functions/Capabilities

IPDAE

• distributed integration and processing management framework;

• scalable, heterogeneous product index and repository;

• dynamically reconfigurable, high-performance computation and storage platform; and

• cross domain solution enabling seamless interaction between assets at various security classification levels (none exceeding collateral Secret).

AMES

• modular exploitation components that fuse and reason over shared information;

• dynamic graph that accumulates multi-source information and products generated by algorithms and analysts into a common framework;

• graph-based fusion that enables sequence-neutral processing that scales to the complexity of relevant operational challenges;

• element discovery and labeling that enriches the physical sensor picture with semantic labels and associations to information from other sources;

• modeling and detection that generates traffic pattern analyses; and

• reasoning tools that help the analyst make sense of large volumes of real-time and forensic information.

CRM

• dynamic tasking, cross-cueing, and handoff of external sensor systems;

• cognitive resources shifted towards information-driven analysis by performing mid-level resource management decisions; and

• coordinated resource management that accommodates heterogeneity in assets and tasking and increases transparency of resource usage by operator-algorithm negotiated interactions and automated correlations of plans to products.

HMI

• rapid customization and persistence of user- and mission-tailored workspaces that support complex, mixed-initiative analytical workflows;

• modular analytical display services that combine geospatial, network, temporal, video, and other task-specific interface components, enabling efficient visualization across diverse information sets and perspectives;

• efficient navigation tools that maximize cross-view coordination and minimize

DARPA-BAA-13-07 Insight Phase 2 9 cognitive cost of changing the information viewed, the display component used to view it, or the methods used for content presentation; and

• efficient overview, alerting, and navigation; coordinated information exploration tools; lightweight evidence management tools; interactions with automated reasoning support, and automated event detection and exploration.

PTB

• provides the venue for evaluation of exploitation systems under realistic operational conditions;

• collects field test-generated data and information that is subsequently used to derive parameters for the VE and validate VE simulation results;

• facilitates development and evaluation of CONOPs (concepts of operation), CONEMPs (concepts of employment), and TTPs (tactics, techniques, and procedures) necessary for successful transition;

• executes field tests that incorporate external sensor and non-sensor information sources; and

• enables system and component level performance assessments.

VE

• simulates friendly and enemy force actions in a large scale virtual world;

• generates high-fidelity sensor and non-sensor information outputs in real-time;

• simulates large numbers of truthed entities and sensor systems beyond the scope of practical field tests;

• enables “what-if” experiments with sensor configurations, enemy entity actions, and clutter backgrounds;

• enables evaluations of system performance with new exploitation algorithms or sensor systems; and

• generates ground truth and simulated information inputs for offline testing and evaluation.

Table 1: Phase 1 Technical Area Functions/Capabilities

Phase 2 Program Structure

Phase 2 shall be executed under a single technical area – Research, Development, Test, and Evaluation and System Integration (RDT&E/SI), which DARPA intends to award to a single prime contractor. The RDT&E/SI prime contractor shall be responsible for programmatic and engineering management of all subcontractors, and coordination with external organizations, programs, and partners. It is expected that the prime contractor will require a number of carefully selected subcontractors to adequately execute the tasks and achieve the Phase 2 objectives and overall high-level program goals outlined in Table 3. DARPA encourages proposals from agile teams, which include experts from industry-leading firms as well as special purpose contractors. Non-traditional Government service providers are encouraged to propose

– either on their own or in a teaming partnership with a firm with experience in Government contracting and the BAA process. A website has been established to facilitate teaming opportunities - see Section VIII.B for further information.

Proposers shall not directly contact:

DARPA-BAA-13-07 Insight Phase 2 10

• any of the Phase 1 performers other than to discuss potential teaming opportunities;

• the National Training Center (NTC) or other potential Phase 2 test bed venues or owning organizations; or

• existing or potential Insight program transition partners/stakeholders.

All inquiries must be directed to DARPA via the contact methods identified in Section VII.

Leadership Groups

The RDT&E/SI prime contractor and subcontractor(s) (henceforth referred to as the RDT&E/SI Team), shall execute work under the general oversight of a Government Team comprised of the DARPA PM, Contracting Officer, Contracting Officer's Representatives, and the Program Security Officer (PSO). The Government Team will be assisted by Scientific and Engineering Technical Assistants (SETAs), a Business Financial Manager, and various technical security representatives.

Three Leadership Groups will be established. Architectural coordination shall be implemented by an Architecture Leadership Group (ALG). The ALG shall provide leadership in development and application of the key architectural products for the E&RM System. Evaluation coordination shall be implemented by an Evaluation Leadership Group (ELG). The ELG shall assist in the development and implementation of effective and meaningful test and evaluation (T&E) efforts and shall provide guidance, technical support, and products necessary to enable valid assessments of system capabilities and limitations. Transition coordination shall be implemented by a Transition Leadership Group (TLG). The TLG shall engage early and continuously to coordinate transition opportunities and determine how best to represent the E&RM System's technical capabilities to potential transition partners. Additional detail on the areas of responsibility delegated to each leadership group is presented in Table 2:

Leadership Group Areas of Responsibility ALG Coordination of architectural aspects related to:

• interface definitions;

• functional architecture;

• information management; and

• technology standards.

ELG Coordination of evaluation aspects related to:

• operational employment of the E&RM System;

• functionality of the E&RM System; and

• functionality of the subsystem components.

TLG Coordination of transition aspects related to:

• transition of E&RM System builds/instantiations to specific transition partners;

• ensuring that relevant operational needs are addressed;

• identification and evaluation of potential obstacles to transition;

• facilitating outreach and demonstrations; and

DARPA-BAA-13-07 Insight Phase 2 11

• developing technology transition plans that describe the overall strategy for technology transition.

Table 2: Leadership Group Areas of Responsibility

The membership of each group shall be identified in the proposal and once established, shall include representation from the prime contractor and each of the appropriate subcontractors.

The DARPA PM shall appoint Government representation for each leadership group, once established, as well.

Phase 2 Program Scope

Objectives In order to achieve the overall high-level program goals, Phase 2 will:

• mature functions/capabilities developed during Phase 1, and broaden the E&RM System’s applicability to expanded mission spaces (new problem sets spanning operational environments and echelons of command);

• enable detection and identification of enemy networks by integrating information from all possible sources, including military intelligence repositories, human reporting, and space, air, sea, and ground-based sensors; and

• demonstrate the objectives listed in Table 3.

Phase 2 retains the scope of Phase 1 TAs 1 – 6 and adds scope for system integration, expansion of test beds, evaluation, transition activities, and the necessary associated security and Information Assurance (IA) tasks. Applicable Phase 1 program materials shall be made available to the RDT&E/SI Team upon contract award.

High-Level Program Goal Phase 2 Objectives

Replace existing stovepipes with an integrated ISR system.

• correlation of multi-source data and information across time and space to identify threat network relationships (consisting of entities, locations, devices, vehicles, events, activities, and other objects, structures, and attributes); and

• correlation of multi-source information from national, theater, and tactical systems.

Provide tools and automation to increase analyst productivity.

• automation of manual tasks to free analysts to develop bodies of evidence to confirm or deny hypotheses;

• georegistration of sensor inputs and intelligence products;

• enhancements over existing real-time forensic capabilities;

• tools to monitor more named areas of interest (NAIs) and

HVTs; and

• tools to enhance visualization and interaction with the E&RM

System.

Promote efficient collaboration between

• contribution to the intelligence layer of the commander’s COP by publishing the E&RM System's sensor COP and E&RM

DARPA-BAA-13-07 Insight Phase 2 12 analysts and increase the efficiency and effectiveness of individual analysts through a unified global ISR picture.

System-developed products;

• the capability to publish standards-based products across intelligence networks in support of other organizations; and

• automated search and retrieval capabilities across intelligence networks (subscribe) to discover available information sources for machine and human reasoning.

Provide an open, standards-based, multi-source, plug-and-play architecture to enable rapid integration of existing and nascent ISR technologies (i.e., sensor agnostic), and make it easy to add, remove, substitute, and modify hardware and software components.

• expanded capability to ingest and process inputs from space, air, ground, sea, and specialty sensors, including non-traditional ISR sources (e.g., fighter aircraft targeting pods);

• exploitation of crowd-sourcing, OSINT, and intelligence reporting to supported organizations;

• expanded capability to ingest and process non-sensor inputs, including data, information, and products produced by other systems or analysts; and

• the ability to receive and disseminate information and products from external systems operating at any classification level.

Provide mission flexibility and cross theater applicability.

• expanded mission space from counterinsurgency to full spectrum operations;

• applicability and adaptability to varied operational environments, including denied areas, various physical environments (terrain and weather), and human terrain;

• applicability to networks beyond insurgent networks, e.g., command and control, mobile missile, fires, air defense;

• capabilities in operationally relevant environments; and

• capabilities that scale.

Enable sequence-neutral processing (i.e., capable of ingesting and reasoning over data and information regardless of the order in which it is received).

• increased scale of time, space, and network complexity which can be represented and reasoned over;

• integration of new inputs and their attributes which must be reasoned over; and

• high fidelity results when incorporating very time-latent information (e.g., days, not minutes)

Provide the ability to dynamically task and cue sensor systems.

• dynamic sensor tasking, cross-cueing, and handoff capabilities in the face of an ISR-aware and -responsive adversary;

• increased efficiency of sensor resource usage; and

• opportunistic collection from sensors that are not directly controlled.

Disseminate products to the tactical edge in real-time.

• the ability to communicate information in support of time-sensitive operations; and

• product dissemination to disadvantaged users with small form factor devices.

DARPA-BAA-13-07 Insight Phase 2 13

Table 3: Phase 2 Objectives

System Integration

The RDT&E/SI Team shall:

• be responsible for developing and demonstrating a system-level capability, to include the interfaces between internal E&RM System components and external sources;

• maintain and build upon the foundational hardware and software architecture developed and implemented in Phase 1 to support continued RDT&E efforts to achieve the Phase 2 objectives; and

• mature the architecture to levels appropriate for transition.

As stated above, for Phase 2, the RDT&E/SI Team shall be responsible for continued and expanded development and transition activities, to be built upon the baseline E&RM System hardware and software developed during Phase 1 of the program. The Phase 1 baseline functionality/capability is outlined in Table 1. Details on the scope of expanded Phase 2 development and transition activities follow below.

Expansion of Test Beds

Phase 2 of the program shall continue field test operations at the existing Phase 1 Physical Test Bed location (NTC, Fort Irwin, CA).

The RDT&E/SI Team shall recommend and work with DARPA and other Government entities to explore opportunities to leverage or establish new venues or environments to exercise the E&RM System (e.g., live, virtual, or constructive simulation exercises, as well as other live missions and operating environments within or outside the continental U.S.). Potential venues for consideration include, but are not limited to:

• the National Simulation Center, Fort Leavenworth, KS;

• the Mission Command Training Program, Fort Leavenworth, KS;

• DCGS-A exercises at Fort Huachuca, AZ;

• U.S. Army Brigade Modernization Command Network Integration Exercises, Fort

Bliss, TX;

• ISR Sustainment Engineering Center, Robins AFB, GA;

• U.S. Air Force Warfare Center, Nellis AFB, NV;

• Naval Air Warfare Center Weapons Division, Point Mugu, CA;

• exercises orchestrated by the DDJ7 Joint and Coalition Warfighting Directorate of the Joint Staff; and

• live exercise venues in coordination with the Combatant Commands (COCOMs).

The RDT&E/SI Team shall assume that existing hardware and equipment that resides in the Phase 1 developmental Software Integration Laboratory (SIL) and in the Phase 1 experimental PTB will be provided as Government furnished equipment (GFE) under Phase 2. Proposals must

DARPA-BAA-13-07 Insight Phase 2 14 clearly state any assumptions concerning what sensors (and associated services such as ground stations, data links, etc.) will be provided by DARPA and what sensors will be provided by the RDT&E/SI Team for each of the Phase 2 field tests. All sensors in the latter category shall be proposed as separately-priced options and must be applicable and adaptable to the venues and scenarios of each field test.

DARPA will determine the initial planned mix of Government furnished property (GFP) sensors and RDT&E/SI Team provided sensors during initial contract negotiations. The RDT&E/SI Team is responsible for insuring that the sensor systems utilized within a venue provide products appropriate for utilization by the E&RM System. DARPA anticipates that additional GFP and RDT&E/SI provided sensors will be identified and incorporated into Phase 2 field tests via contract modifications. The RDT&E/SI prime contractor shall utilize agile, low overhead subcontracting processes to add sensor subcontractors, as directed by DARPA.

In addition, the RDT&E/SI Team shall:

• propose role players and associated equipment to support Phase 2 field tests;

• be responsible for coordination and connectivity with operational networks associated with Phase 2 field tests;

• be responsible for connectivity to additional external information sources;

• be responsible for maintaining the interior, exterior, and fenced perimeter area of the

Joint Insurgency Attack the Network Testbed (JIANT), Building 6223, of the existing test bed; and

• provide for the physical security of the JIANT, Building 6223 per the Program Security description below (see Additional Supporting Efforts).

Evaluation

The RDT&E/SI Team shall be responsible for the development, evaluation, verification, and validation of system-level and subsystem-level metrics, measures of performance (MOPs), and measures of effectiveness (MOEs), until the E&RM System has matured to a readiness level appropriate for formal independent validation and verification (IV&V). The RDT&E/SI Team shall work collaboratively with DARPA, other Government entities, transition partners, and stakeholders to adapt metrics and measures as necessary in order to support evaluation of the E&RM System capabilities measured against appropriate requirements.

Proposals must include an evaluation framework and key metrics and measures suitable for evaluation of the E&RM System by the program, that are also adaptable to serve the needs of the formal IV&V to be conducted to measure the E&RM System against the requirements of service and agency transition partners.

Additional Supporting Efforts

Program Security

DARPA-BAA-13-07 Insight Phase 2 15

For each contracted facility (to include test beds, laboratories, buildings, etc.) in which classified information will be handled, stored, or processed, the cognizant contractor shall appoint a U.S.

citizen employee, who is cleared as part of the Facility Clearance (FCL), to be the Facility Security Officer (FSO)/Contract Program Security Officer (CPSO). The FSO/CPSO will supervise and direct program security measures necessary for implementing applicable security requirements including, but not limited to:

• ensuring the physical and personnel security policies related to the protection of classified program information are adhered to (collateral or SCI depending on the work being performed.);

• ensuring guidelines set forth in the Insight SCG (DARPA-CG-696 Revision 1, November 21, 2011) are adhered to;

• supporting and overseeing the installation of the DARPA Secure Wide Area Network (DSWAN), where applicable; and

• coordinating with the DARPA PSO or Program Security Representative (PSR) and transition partners’ security personnel, as required.

Test bed-specific security requirements and FSO/CPSO roles and responsibilities: the E&RM System baseline is designed to be inserted into any operational environment. In order to support numerous potential operational environments and transition opportunities, the RDT&E/SI Team shall select and use only hardware and software which has already been approved for use on accredited, classified DoD/IC systems. Approved hardware and software lists include the following:

1. the DoD Unified Capabilities Product List, which can be found at https://aplits.disa.mil; and

2. the Approved Software Products List, which can be found on various classified networks.

In addition, in order to support the overall security posture of the test bed(s), the cognizant contractor will be required to provide dedicated onsite security personnel to support each test bed.

Information Assurance

IA has significant roles and responsibilities with respect to the E&RM System field tests and test beds, as well as the E&RM System deployments into various operational environments. The E&RM System's vulnerabilities to threats (as well as the threat of the E&RM System to external systems) influences:

• the design of the system and its protection features; and

• the security requirements and controls, which are likely to be unique to a particular mission or operational environment.

Certification and accreditation of the E&RM System is required before it can be approved to process classified information in any given test or operational environment, mission, and architecture.

https://aplits.disa.mil/

DARPA-BAA-13-07 Insight Phase 2 16

The RDT&E/SI Team will be responsible for the IA tasks associated with the development, certification, and accreditation of the E&RM System in any instance of T&E in a physical test bed or in any operational environment to which the E&RM System might be deployed.

Accreditation for collateral Secret shall be in accordance with DoDI 8510.01 requirements and ICD 503 for SCI. Regardless of network accreditation level, the RDT&E/SI Team will be responsible for providing dedicated and certified IA personnel to the program in accordance with DoD 8570.01-M. The IA personnel will be responsible for and capable of providing the following specific IA tasks in conjunction with the DARPA IA Managers (IAMs) and IA representatives from either a host test bed or a transition/stakeholder organization, agency, or entity and:

• determine the system security requirements and controls for accreditation;

• develop and maintain the Certification and Accreditation (C&A) body of evidence and prepare required documentation in accordance with DoD policies as required;

• develop tests to verify the evolving or modified system’s compliance with stated requirements;

• implement relevant IA policies in the design and test of the system in order to obtain

(and maintain) accreditation;

• ensure rigorous controls are in place to manage system changes and monitor and document system performance (configuration management);

• execute validation tests and assess risks (in the form of vulnerabilities, threats, and impact of failures) associated with the system, and propose and develop mitigation strategies and approaches;

• evaluate the system's protection features against stated criteria;

• assist in certifications to determine the ability of the system features to meet security requirements and controls, and assist in accreditation processes as required;

• conduct activities necessary for the continuing operation of the accredited system;

• develop and maintain:

o schedules; and o system descriptions, diagrams, and architectures;

• understand risk mitigation and acceptance;

• conduct periodic testing of the security posture of the Information System (IS);

• perform and oversee system audits; and

• perform incident investigations involving the IS.

DARPA Secret Wide Area Network (DSWAN)

DSWAN is a protected, classified communications architecture that provides Defense Security Service (DSS)-accredited Cleared Defense Contractors (CDCs) with a collateral Secret level secure IS solution to support DARPA programs. DSWAN provides collaboration capabilities between DARPA program management staff and distributed CDCs across the continental United States. DSWAN capabilities include email, file storage, data transfer, and web services.

DSWAN can be delivered as a Guest System or Interconnected System if connected to a DSS-accredited Local Area Network (LAN).

DARPA-BAA-13-07 Insight Phase 2 17

The RDT&E/SI Team will be required to use DSWAN for the Insight program. All DSWAN equipment shall be Government provided; however, it will be the responsibility of the contractor(s) with a DSWAN node(s) connected to the LAN(s) to:

• provide a firewall (which must be listed on the National Information Assurance Partnership/Common Criteria Evaluation and Validation Scheme Validated Products List);

• provide a DSS-accredited system; and

• provide an internet connection.

It will be the responsibility of all contractors receiving a DSWAN node, whether connected to a LAN or not, to:

• possess a current FCL from DSS;

• be approved for the storage and processing of collateral Secret information, and the storage of hardware and Communications Security (COMSEC) equipment per the CDC DSS Form 147 (Record of Controlled Area); and

• ensure that all personnel accessing DSWAN are U.S. citizens and have a minimum clearance level of Secret.

Associated security staff support requirements: the FSO/CPSO and the IS Security Manager (ISSM)/IS Security Officer (ISSO) will be responsible for the day-to-day security of the DSWAN equipment and the DSS-accredited "closed area." The FSO/CPSO and ISSM/ISSO will be responsible for:

• maintaining facility standard operating procedures and IS procedures to reflect connectivity to, and protection mechanisms for, DSWAN and associated COMSEC equipment in accordance with DARPA accreditation and cognizant DSS Field Office procedures; and

• providing the system's accreditation package/documentation to the DARPA DSWAN IAM, if connecting to the CDC LAN.

Secure Platform for Collaboration

Provide and host a secure (e.g., https) platform to support collaborative program management, development, integration and execution with a minimum of the following capabilities:

• document repository;

• source code repository;

• software release management;

• file release versioning;

• bug/issue trackers/tickets;

• discussion forums;

DARPA-BAA-13-07 Insight Phase 2 18

• email blasters;

• task management system;

• configurable role-based accesses;

• cross-service artifact linking (ability for one repository to point to content in another repository);

• support unclassified, For Official Use Only, and International Traffic in Arms Regulations content;

• wiki; and

• community calendar.

The contents of the secure platform for collaboration shall be archived and delivered to the Government at the end of each field test and again at the end of Phase 2 of the program.

Schedule and Milestones

Figure 3 depicts the notional Insight program schedule. Proposals must include detailed schedules that incorporate the milestones and deliverables outlined in Table 3 and Table 4.

Figure 3: Program Schedule

Month(s) After Contract Award

Milestone Description

<1 Kickoff Meeting

• review end of Phase 1 performance, capabilities, and limitations;

• review Phase 1 accomplishments and identification of requirements to achieve Phase 2 goals and objectives;

and

• present technical approach and planned schedule, including:

o any changes in approach or schedule from the

DARPA-BAA-13-07 Insight Phase 2 19 time of proposal to contract award;

o development plan;

o system-level technical approach including functional architecture and interfaces;

o system integration, verification and validation;

o test plan and evaluation development; and o programmatic processes for communication and collaboration among contractors and with the Government Team.

4, 10, 16, 22, 28

E&RM System Integration Event and Technical Test Readiness Design Review

• demonstrate an integrated system that exercises all system level interfaces for the purpose of validating those interfaces and demonstrating end-to-end system flow;

• review technical progress;

• demonstrate an integrated, test ready E&RM System capable of operating in real-time, open loop playback mode;

• demonstrate the ability to compute performance metrics resulting from all E&RM System and subsystem component processing;

• undergo unannounced “stress” tests that will probe for and identify weaknesses and limitations;

• demonstrate functionality, performance, and correctness of all elements;

• review status of functional architecture and interfaces;

and

• generate readiness report.

4, 10, 16, 22, 28

VE

Demonstration and Design Review

• present system architecture and design, to include technical progress and status of the functional architecture and interfaces; and

• simulate evaluation scenarios.

4, 10, 16, 22, 28

Physical Test Execution TRR and Design Review

• review the physical test bed design;

• review the Test Execution Plan;

• review the Evaluation Plan (identify metrics, critical operating issues, MOPs, MOEs, data elements, data collection methodology, dependencies, etc.); and

• generate a readiness report.

5, 11, 17, 23, 29 Field Tests (FTs)

4-8

• at the Phase 1 Physical Test Bed or other location TBD.

3, 6, 9, 12, 15, 18, 21, 24, 27, 30

Program Reviews

• review technical progress;

• present results of developmental work and post FT analyses;

• present plans for subsystem and system modifications

DARPA-BAA-13-07 Insight Phase 2 20 prior to next FT event; and

• review plans for FTs and simulation tests.

30 Phase 2 Final Review

• review E&RM System end-of Phase 2 performance, capabilities, and limitations;

• review VE end-of Phase 2 performance, capabilities, and limitation; and

• review Phase 2 accomplishments.

Table 4: Phase 2 Program Milestones

The location for the technical interchange meetings (TIMs) and the events above will be specified by the DARPA PM. In general, the location will be Arlington, Virginia, a contractor facility, or exercise location. In addition to the TIMs, regular teleconferences are encouraged to enhance communications with the Government Team and other contractors. Should important issues arise between program milestones, the Government Team will be available to support informal, interim TIMs.

Deliverables and Intellectual Property

In addition to the deliverables identified in Table 5, the RDT&E/SI Team will be responsible for all reporting as described in Sections VI.B., VI.C and VI.D.

Due Date Deliverable Example / Description

At the end of each FT and 30 months after contract

(MAC)

Contents of the platform used to support collaborative program management, development, integration and execution

For Phase 1, this was a combination of TeamForge Collabnet and the Virtual Distributed Laboratory.

3 MAC; at the end of each FT and 30

MAC

System Design Document / System Documentation

Describe the system in sufficient detail to permit an engineer to correctly implement the system without consulting the system designer.

Document source code, hardware description language specifications, system diagrams, part numbers and other data at a level sufficient to maintain and to produce copies of the system. Inclusive of hardware infrastructure design.

Includes Requirements Traceability Verification Metrics.

At the end of each Software / Software Includes: integration application program

DARPA-BAA-13-07 Insight Phase 2 21

FT and 30 MAC framework / Software applications / Software infrastructure / Source interfaces (APIs); operational releases of E&RM System software; Application Developer Kits, Interactive Analysis Packets; executables; licenses;

maintenance agreements; test bed prototypes/demonstration software, etc.

Include updates for each major release.

At the end of each FT and 30 MAC

Software Documentation

Document source code at a level sufficient to maintain and to produce copies of the software.

Includes: software infrastructure design, component definition packages, models, test plan inputs, test results, etc.

Include update for each major release.

3 MAC; at the end of each FT and 30

MAC

Algorithm Design Document

Describe the algorithmic detail of all components in sufficient detail to permit a software engineer to correctly code the algorithms without consulting the algorithm designer.

For each FT Field and User Manuals For each FT System Test Manuals and Guides

30 MAC Hardware suites

For each FT

FT Evaluation Plans and Evaluation; System Evaluation Plans and Evaluations

Includes: requirements, metrics, MOPs, MOEs, evaluation processes, data collection techniques, CONOPs identification, System Use Case descriptions, etc.

For each FT Test Bed(s) Documentation

Includes: design plans, equipment, data management system, experiment design documentation, test plans, test data, after action review materials, etc.

For each FT or transition instance

High Assurance Solution(s)

Includes: servers hosting software, design documents, internal test results, System Security Plans); Accreditation Test Procedures, Message Analysis and Generation Rules, any other documentation required for C&A activities.

Within one month after the end of Final Report Concisely summarize the effort conducted.

DARPA-BAA-13-07 Insight Phase 2 22

Phase 2 Table 5: Phase 2 Deliverables

All deliverables identified in Table 5 shall be provided in electronic form. Where meaningful, such materials will be provided in a form suitable for use with any computer-aided design (CAD) or other system or software used in the design and/or fabrication of the system or system components.

All deliverables under this effort, software and otherwise, are to be completely maintainable and modifiable with no reliance on any non-delivered computer programs, documentation, or other materials.

All computer software, technical data, and test data, harnesses, and methodologies developed must be delivered as source code and, where meaningful, as object (executable) code. For all computer software purchased or licensed for use as a component of the software or other deliverables, arrangements shall be made for licensing and maintenance agreements to be transferred to the Government at no additional cost upon the completion of the work under any contract awarded under this BAA.

A key goal of the Insight program is to establish an open, standards-based, multi-source, plug-and-play architecture that allows for interoperability and integration. This includes the ability to easily add, remove, substitute, and modify software and hardware components. This will facilitate rapid innovation by providing a base for future users or developers of Insight program technologies and deliverables. Therefore, it is desired that all noncommercial software (including source code), software documentation, hardware designs and documentation, and technical data generated by the program be provided as deliverables to the Government, with a minimum of Government Purpose Rights (GPR), as lesser rights may impermissibly impact the lifecycle costs of affected items, components, or processes.

DARPA-BAA-13-07 Insight Phase 2 23

II. AWARD INFORMATION

A single award is anticipated. The level of funding for any award made under this BAA will depend on the quality of the proposals received and the availability of funds. Awards will be made to proposers whose proposals are determined to be the most advantageous and provide the best value to the Government, all factors considered, including the potential contributions of the proposed work, overall funding strategy, and availability of funding for the effort. See Section V.B. for further information.

Proposals selected for award negotiation may result in a procurement contract or OTA depending upon the nature of the work proposed, the required degree of interaction between parties, and other factors. In all cases, the Government contracting officer shall have sole discretion to select award instrument type and to negotiate all instrument provisions with selectees.

As of the date of publication of this BAA, DARPA expects that program goals for this BAA cannot be met by proposers intending to perform 'fundamental research,' as defined by National Security Decision Directive 189.2 Therefore, DARPA anticipates restrictions on the resultant research. Notwithstanding this statement of expectation, DARPA recognizes that proposed research solutions could be of either a fundamental or restricted nature. Proposers should indicate in their proposal whether they believe the scope of the research included in their proposal is fundamental or restricted. See Section VI.B.5 for further information on fundamental, non-fundamental, and restricted research.

The Government reserves the right to:

• Select for negotiation all, some, one, or none of the proposals received in response to this solicitation.

• Make awards without discussions with proposers.

• Conduct discussions with proposers if it is later determined to be necessary.

• Segregate portions of resulting awards into pre-priced options.

• Accept proposals in their entirety or to select only portions of proposals for award.

• Fund proposals in increments with options for continued work at the end of one or more phases.

• Request additional documentation once the award instrument has been determined;

such information may include, but is not limited to, representations and certifications.

• Remove proposers from award consideration should the parties fail to reach agreement on award terms within a reasonable time or the proposer fails to provide requested additional information in a timely manner.

2 “Fundamental research means basic and applied research performed [on campus] 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.”

DARPA-BAA-13-07 Insight Phase 2 24

III. ELIGIBILITY

A. Applicants

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

1. Historically Black Colleges and Universities (HBCUs), Small Businesses, Small Disadvantaged Businesses and Minority Institutions (MIs)

HBCUs, small businesses, small disadvantaged businesses, and MIs are encouraged to submit proposals and team with others to submit proposals; however, no portion of this announcement will be set aside for these organizations due to the impracticality of reserving discrete or severable areas of this research for exclusive competition among these entities.

2. Federally Funded Research and Development Centers (FFRDCs) and Government Entities

FFRDCs and Government entities (e.g., Government/national laboratories and military educational institutions) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless the following conditions are met.

− FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector and must provide a letter on official letterhead from the sponsoring organization citing the specific authority establishing eligibility to propose to Government solicitations and compete with industry, and compliance with the associated FFRDC sponsor agreement and terms and conditions. This information is required for FFRDCs proposing as either prime contractors or subcontractors.

− Government entities must clearly demonstrate that the proposed work is not otherwise available from the private sector and provide documentation citing the specific statutory authority (and contractual authority, if relevant) establishing their eligibility 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 eligibility submissions on a case-by-case basis; however, the…