DARPA-BAA-12-61_ADAPTable_Sensor_Systems_Phase_2.pdf

Broad Agency Announcement

ADAPTable Sensor Systems Phase 2

STRATEGIC TECHNOLOGY OFFICE

DARPA-BAA-12-61

September 28, 2012

DARPA-BAA-12-61 ADAPT Phase 2

TABLE OF CONTENTS

Part One: Overview Information

Part Two: Full Text of Announcement

1. FUNDING OPPORTUNITY DESCRIPTION

1.1. PROGRAM OVERVIEW

PROPOSAL TOPIC AREAS

Topic 1: Reference Designs Topic 2: Reusable Core Software Topic 3: Core and Ancillary Hardware Additional Information

2. AWARD INFORMATION

3. ELIGIBILITY INFORMATION

3.1 ELIGIBLE APPLICANTS

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

3.2 COST SHARING/MATCHING

3.3 OTHER ELIGIBILITY REQUIREMENTS

3.3.1 Collaborative Efforts

4. APPLICATION AND SUBMISSION INFORMATION

4.1 ADDRESS TO REQUEST APPLICATION PACKAGE

4.2 SECURITY AND PROPRIETARY ISSUES

4.3 CONTENT AND FORM OF APPLICATION SUBMISSION

4.3.1 Abstract and Proposal Information

4.3.2 Restrictive Markings on Proposals

4.4 FORMATTING CHARACTERISTICS

4.4.1 Proposal Abstract Format

4.4.2 Proposal Format

4.5 SUBMISSION DATES AND TIMES

4.5.1 Abstract and Proposal Submission Deadline

4.6 INTERGOVERNMENTAL REVIEW

Not Applicable

4.7 FUNDING RESTRICTIONS

4.8 OTHER SUBMISSION REQUIREMENTS

5. APPLICATION REVIEW INFORMATION

5.1 EVALUATION CRITERIA

5.1.1 Overall Scientific and Technical Merit

5.1.2 Potential Contribution and Relevance to the DARPA Mission

5.1.3 Realism of Proposed Schedule

5.1.4 Proposer’s Capabilities and/or Related Experience

5.1.5 Plans and Capability to Accomplish Technology Transition

5.1.6 Cost Realism

5.2 REVIEW AND SELECTION PROCESS

6. AWARD ADMINISTRATION INFORMATION

6.1 SELECTION NOTICES

6.2 ADMINISTRATIVE AND NATIONAL POLICY REQUIREMENTS

6.2.1 MEETING AND TRAVEL REQUIREMENTS

6.2.2 HUMAN USE

6.2.3 ANIMAL USE

6.2.4 PUBLICATION APPROVAL

6.2.5 EXPORT CONTROL

6.2.6 SUBCONTRACTING

6.2.7 ELECTRONIC AND INFORMATION TECHNOLOGY

6.2.8 EMPLOYMENT ELIGIBILITY VERIFICATION

6.2.9 System for Award Management Registration and Universal Identifier Requirements

6.2.10 Reporting Executive Compensation and First-Tier Subcontract Awards

6.2.11 Updates of Information Regarding Responsibility

6.2.12 Representation by Corporations Regarding Unpaid Delinquent Tax Liability or a Felony Conviction Under Any Federal Law

6.2.13 Cost Accounting Standards Notice and Certification (Deviation 2012-00003 (JAN 2012)

6.2.14 Controlled Unclassified Information on Non-DoD Information Systems

6.2.15 Providing Accelerated Payment to Small Business Subcontractors (DEVIATION) . 37

6.3 REPORTING

6.4 ELECTRONIC SYSTEMS

6.4.1 Representations and Certifications

6.4.2 Wide Area Work Flow (WAWF)

6.4.3 i-EDISON

6.5 AGENCY CONTACTS

7. OTHER INFORMATION

7.1 INTELLECTUAL PROPERTY

7.1.1 Procurement Contract Proposers

7.1.2 NonProcurement Contract Proposers

8. APPENDIX 1: PROPOSAL SLIDE SUMMARY

9. APPENDIX 2: Volume 1 cover sheet template

10. APPENDIX 3: Volume 2 cover sheet, CHECKLIST AND SAMPLE templateS

11. APPENDIX 4: Darpa-BAA-12-61 FOUO ADDENDUM REQUEST FORM

12. APPENDIX 5: Darpa-BAA-12-61 U.S. Permanent Resident and Foreign National Visit Request FORM

13. APPENDIX 6: Darpa-BAA-12-61 Verification of U.S. Citizenship FORM

Part One: Overview Information

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

Funding Opportunity Title – ADAPTable Sensor Systems Phase 2 Announcement Type – Initial announcement Funding Opportunity Number – Broad Agency Announcement (BAA)-12-61 Catalog of Federal Domestic Assistance Numbers (CFDA) – Not applicable.

Dates o Posting Date: September 28, 2012 o Proposer’s Day: October 4, 2012 o Proposal Abstract Due Date: October 26, 2012 o Proposal Due Date: November 30, 2012 o BAA Closing Date: March 27, 2013

Anticipated individual awards - Multiple awards are anticipated.

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

Award fee.

Agency contact o Points of Contact The BAA Coordinator for this effort may be reached at electronic mail:

DARPA-BAA-12-61@darpa.mil

DARPA/STO

Attn: DARPA-BAA-12-61 675 N. Randolph Street Arlington, VA 22203-2114

Part Two: Full Text of Announcement

1. FUNDING OPPORTUNITY DESCRIPTION

The Defense Advanced Research Projects Agency often selects its research efforts through the Broad Agency Announcement (BAA) process. The BAA will appear first on the FedBizOpps website, http://www.fbo.gov/. The following information is for those wishing to respond to the

BAA.

DARPA is soliciting innovative research proposals to accelerate development time of sensor systems through the use of commercial processes that have not been typically used in military sensor system development. The intent to explore the use of commercial processes is not intended to restrict bidding to commercial firms nor is it intended to restrict the use of revolutionary approaches. We seek a new approach to developing sensor systems. 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 ADAPTable Sensor Systems Phase 2 (ADAPT Phase 2) program seeks to accelerate the development time of sensor systems through the use of commercial processes. The goal of the program is to allow sophisticated sensor systems to be developed in one year or less. Today, military sensor system development programs focus on developing systems designed to meet a specific system need and “stovepipe” systems are designed from scratch.

In contrast, commercial consumer electronics has experienced a revolution in development process in the past decade. Technology developers invest in “reference designs”1 that both demonstrate the technology performance and serve as a basis for consumer electronic products.

System integrators incorporate these reference designs (or at least significant elements of the reference design) into their products. The existence of the reference design allows system integrators to develop products rapidly and refresh technology frequently. This methodology is enabled by the existence of a reference design.

The ADAPT program has developed core hardware and software technology to be used in sensor systems. This technology leverages technology developed for the commercial Smartphone market and comprises the following:

Processing power, Storage memory Commercial Communications (low power, high rate and long range) Navigation (GPS) Orientation (compass, accelerometer, gyro) Flexible interface to mission specific sensors and communication systems Open source operating system (Android)

1 (From Wikipedia) Reference design refers to a technical blueprint of a system that is intended for others to copy.

It contains the essential elements of the system; however, third parties may enhance or modify the design as required. Reference Design Packages enable a fast track to market thereby cutting costs and reducing risk in the customer's integration project. Reference designs enable customers to shorten their time to market. In this modern competitive world shortening the design cycle and speeding up the time to market is the major challenge faced by Original equipment manufacturers (OEMs). The main purpose of reference design is to support companies in development of next generation products using latest technologies.

Sensor management, detection and processing utilities Distributed database and communications protocols External interface and display utilities

This ADAPT Phase 2 BAA seeks to create and support reference designs that would make use of this core technology. The overall goal of the ADAPT phase 2 program is to accelerate system development time – the reference designs developed by this program will support this goal by allowing system integrators to develop and deliver new sensor missions in less than 12 months.

PROPOSAL TOPIC AREAS

Under this BAA, DARPA is seeking proposals for reference designs as well as additional core hardware, and additional reusable core software to support these designs. Proposals to design, develop, configure, integrate, test or supply reference designs, core hardware, or reusable core software in support of the ADAPT Phase 2 mission are requested. A proposal may only address a single topic; proposers may submit multiple proposals.

Topic 1: Reference Designs

The reference designs sought by this BAA are generic, laboratory grade systems that allow a broad range of system integrators to quickly develop, test and refine distributed sensor systems.

Several design attributes are sought:

Reference designs should support multiple military sensor missions; they should not be developed for a specific mission. They might be demonstrated for a specific mission but are not reference designs unless the technology can be used in other areas. For example, proposing a robotic system that is used to clear a culvert pipe is not interesting; proposing a robotic system that could be used to quickly develop a culvert clearing system is interesting. Proposers should detail how their proposed reference design supports development of several relevant military missions.

Reference designs should be open to allow design elements to be copied, modified and expanded by third parties. Proprietary or encumbered aspects of a design will slow development and adoption of the technology and is not responsive to this BAA. For example, if robotics technology is proposed but the collision avoidance technology is delivered as restricted or licensed object code, the reference design could not be tailored to different kinds of environments, limiting its usefulness. Proposers should clearly describe any restrictions on the use of the proposed technology; any such restrictions must be supported by a compelling need.

Reference designs should be inexpensive. The objective is to make the technology ubiquitous and accessible. Robust, field grade equipment is not needed – reference designs are to be copied into mission specific, field grade systems. “Hardening” of the technology is itself a mission specific requirement and not part of the reference design.

Examples of things not needed by the reference design include armor, shock tolerance for airdrop, and tolerance of extreme temperature or altitudes. Proposers should clearly separate non-recurring expenses and unit build costs. Unit build costs should be given for quantities of 100, 1000, and 10,000 units.

Reference designs are meant to communicate technical capability. By themselves, reference designs are to be used by third parties for evaluation of capability, development of tactics and development of application software. Tools to support these operations may be needed. These could include programming tools, display tools or data collection tools.

Proposers should clearly describe the support tools and environment that will be delivered to facilitate third party experimentation with the reference design.

Reference designs should make use of the ADAPT core technology (hardware and software).

The Government will furnish this technology to successful bidders. Detailed design information for the current ADAPT core hardware and software will be provided upon formal request and certification of ability to receive and handle information marked “For Official Use Only (FOUO).” This information is being provided for reference only and is not required to submit a proposal. Information needed to request core hardware and software design information is provided in Appendix 4.

Proposals should indicate the quantity of hardware needed. ADAPT core technology provides significant capabilities; proposers should maximize their use of this core technology and minimize the incorporation of duplicative functions in their reference designs. For example, if an Unmanned Aerial Vehicle (UAV) reference design were proposed, the flight control should be performed in the core along with sensor operation and third party applications. The existing core algorithms should support sensing and detection where applicable. Communication between nodes and to external users should use the core protocols where applicable. Proposers should detail their proposed use of the ADAPT core hardware and software. Reference design power consumption should be appropriate for the types of systems that would be developed using the reference design.

The ADAPT program currently has one reference design in development – a reference design for unattended ground sensors. This reference design demonstrates how the ADAPT core technology can be used in sophisticated, distributed (500 nodes), stationary sensor systems. This design provides examples for external sensor interface, intra-node communications (using internal or off-board radios), in network detection and tracking and external “Man-in-the-Loop” system operation. This BAA seeks additional reference designs to expand the scope of ADAPT applications. In particular, the proposed reference designs should support mobility and coordinated, cooperative operation between mobile and stationary sensors. The specific reference designs are left to the proposer but DARPA seeks to expand applicability beyond just Unmanned Ground Sensor (UGS) systems. Proposers are advised to review the evaluation criteria against the merits of their proposed solution.

DARPA is interested in design services to assist developers utilize commercial processes in the development of Reference Designs. Such design services may improve the cost, production, availability, flexibility or development time for the Reference Designs.

Topic 2: Reusable Core Software

This topic seeks to expand the capabilities of the existing ADAPT core software. It does not seek to replace the existing software modules and functions. Solutions that create new capabilities and opportunities by building upon and extending the existing library are preferred.

The ADAPT core hardware includes a substantial general purpose processor, a graphics coprocessor, an FPGA, a variety of radios (cell, Wi-Fi, Bluetooth), and a variety of sensor and GPIO interfaces. The proposed software may utilize any or all of these devices. Proposers are advised that power consumption is a significant consideration, so while these devices may all be used; a plan to control their power consumption should be an integral part of any software design.

Proposed software is encouraged to utilize existing ADAPT core software where appropriate. In particular, intranetwork communication (if required) can be supported by the existing distributed database and low power mac protocol. The solution may opportunistically utilize external infrastructure (cell systems, Wi-Fi access points, and so on) but should not be dependent on their presence.

The ADAPT core software architecture is a symmetric, data centric design. Software operating on the nodes produces data of varying types (for example, node location and orientation, sensor detections, audio, video, and other identifying data) that they deposit in a distributed database.

This distributed database then shares data with neighboring nodes according to subscriptions entered by other software for data of interest. The extent of data movement is controlled by the subscriptions—data may move over an area larger than just the neighboring nodes through purely local means by interlocking subscriptions. Higher-level software analyzes the data and produces composited objects (for example, target tracks or target identification). Users may connect to any node and enter their own queries for data. In general, the system only reports high level objects to users to satisfy their stated requirements. While the core software supports TCP/IP for remote access by users, it does not utilize TCP/IP or routing for communication between nodes.

The core software does not specify the data model—it may be different on different systems. The proposed solution should be flexible to accommodate different data models. For example, the data records could describe detections, targets, and other events that have been detected by the network. Most data records will have a dependence on geographic location and will include a location as one of the data fields. Portions of this database are on each node. The data is typically stored on several nodes in the geographic vicinity of where it was produced.

Proposers should describe their proposed solution in sufficient detail to allow evaluation. In particular:

Proposers should describe the proposed problem and its relevancy to the ADAPT mission (accelerating system development).

Proposers should show how their solution would support different scenarios.

Proposers should describe the various options and configuration parameters that are available and the effect of these parameters on the operation of the system.

Proposers should describe any data or messages that must be exchanged to accomplish the solution and any computations that must be performed.

Proposers should (at a minimum) include an analysis of the energy cost of the solution.

Simulation or measured results are encouraged.

The following topics are examples of potential candidates for Phase 2 solutions. These topics do not limit the range of possible software solutions proposed under this BAA—any innovative software that supports the accelerated development of sensor systems composed of a large number of cooperating nodes may be proposed. DARPA is especially interested in novel ideas that may not have been previously considered.

1. DARPA is seeking a software solution to use the cellular modem on the core hardware for peer-to-peer communication between nodes. The core hardware is theoretically capable of peer-to-peer operation using Time Division Duplex (TDD), but no effort has been expended to date to realize this type of operation. The proposed solution should include methods to discover peers and to make decisions about using the peer-to-peer links. The solution should operate autonomously without user intervention. The existing ADAPT peer-to-peer network protocols operate over a low power ground radio, but not over the cell modem. This protocol may be able to supply hints to aid rapid acquisition of cellular links.

2. DARPA is seeking a software solution to opportunistically use existing non-ADAPT network infrastructure. Deployment may occur in an area with existing network infrastructure and it may be advantageous to use that existing network infrastructure— cell, Wi-Fi, or Bluetooth. This infrastructure may be known in advance of deployment or it may be discovered only after deployment. It may be owned and operated by the deploying force, the enemy force, or neutral third parties. Use of existing network infrastructure should enhance the operation of the sensor network. Network infrastructure should not be required for operation. The proposed solution should include methods to discover existing network architecture, to make decisions about using the network infrastructure, and to switch operation from the standard peer-to-peer operation to the infrastructure enabled operation. The solution must maintain network operation in the event of infrastructure failure. The solution should operate autonomously without user intervention. Standard protocol stacks are available for all three transceivers. Normally these protocol stacks and the transceivers are off to conserve energy. Any plan to use these transceivers must include a method to enable them when needed.

3. DARPA is seeking software solutions to efficiently share data among a number of cooperating nodes. Depending upon the relative cost of the network links, the amount of data, the persistence of the data, delivery latency, and other factors, it may be advantageous to handle the acquisition of existing data records in ways other than the existing persistent query data flow. For example, a single shot query that acquires data from the network once and does not persistently alter data flow patterns may be more efficient in some cases. Alternatively, a network query that performs aggregation as it acquires the data may be more efficient for some queries. It may be advantageous to enter the query on a node near where the data originated or even on multiple geographically dispersed nodes and handle the consolidation of results with a new technique. Proposals should describe the proposed data sharing techniques, when these techniques would be useful, and the proposed integration with the existing database software.

The proposed software may include, but is not limited to, the following:

(1) driver software for the hardware components,

(2) hardware abstraction layers to allow easy substitution of hardware components,

(3) manufacturing calibration and test software,

(4) embedded operating systems,

(5) support services useful for multiple sensor missions,

(6) mission development tool kits,

(7) sensor applications that would benefit multiple system implementations (e.g., target tracking applications and decision support applications),

(8) device maintenance and reprogramming support tools, and simulation and modeling software,

(9) software and firmware integration frameworks and support,

(10) external test equipment to stimulate the system and test the core hardware and software,

(11) built-in experiment and test equipment and tools to support system evaluation.

Topic 3: Core and Ancillary Hardware

This topic seeks to extend and enhance the state of the art in the context of the existing ADAPT core hardware. The ADAPT core module should remain positioned at the current state of the art for commercial smart phones. Solutions that create new capabilities and opportunities by building upon and extending the existing system are preferred. Substitution of components may be desirable, but the tradeoffs between new capability and breakage of existing software services inherent in any such substitution must be revealed and analyzed.

Core hardware should be designed and manufactured using commercial ODM processes where possible.

The ADAPT core hardware includes a substantial general purpose processor, a graphics coprocessor, an FPGA, a variety of radios (cell, Wi-Fi, Bluetooth), and a variety of sensor and GPIO interfaces. An ancillary module containing additional sensor interfaces and a lower frequency (300-1000MHz) radio, the “ground radio” is under development to provide additional capability. The proposed software may use any or all of these devices. Proposers are advised that power consumption is a significant consideration, so while these devices may all be used; control signals should be available to allow the core software to control their power consumption.

Proposers should describe their proposed solution in sufficient detail to allow evaluation. In particular:

Proposers should describe the proposed problem and its relevancy to the ADAPT mission (accelerating system development time).

Proposers should show how their solution would support different scenarios.

Proposers should describe the various options and configuration parameters that are available and the effect of these parameters on the operation of the system.

Proposers should (at a minimum) include an analysis of the energy cost of the solution.

Simulation or measured results are encouraged.

The following topics have been identified by DARPA as potential candidates for Phase 2 solutions. These topics do not limit the range of possible hardware solutions proposed under this BAA—any innovative hardware that supports the accelerated development of sensor systems composed of a large number of cooperating nodes may be proposed. DARPA is especially interested in novel ideas that may not have been previously considered.

1. DARPA is interested in future revisions of the core hardware that maintain the core hardware module at the commercial state of the art. A program to provide updated modules is of interest. As the state of the art improves, DARPA expects hardware improvements to translate into higher performance on a variety of metrics. Of special concern are: size, weight, power consumption, and cost. Proposals should detail the expected hardware improvements and describe how these improvements translate into improvements in these performance parameters.

2. Module power consumption can be improved by utilizing lower power components or by increasing the controls available to software to manage the power consumption of the components. Both solutions should be considered. Software based power control is expected to operate on the order of microseconds or milliseconds as opposed to seconds or minutes.

3. As the ADAPT core uses commercial components, commercial Intellectual Property (IP) restrictions present barriers to the development of sophisticated software algorithms to utilize and control the components. DARPA is interested in the exposure of hardware programming interfaces for the selected components to the ADAPT software development community. Constructive plans for providing this protected IP should be described. Plans that guarantee the availability of hardware programming interfaces are preferred. Programming support for specialized or IP-restricted hardware components may also be of interest.

4. It may be desirable to include additional components on the core hardware module to increase the number of systems in which it can be utilized with little to no additional work. Additional components should be useful for a number of different missions, not just for a single mission. Of particular interest is a lower frequency radio as used in the ground radio and sensor inputs configured for different classes of external sensors.

Proposers may also suggest other components that might be of interest.

Proposers may also propose the development of ancillary hardware modules that interface to the core module to provide additional capability. These ancillary modules should provide a general-purpose function that may be used in support of a number of missions, or in studies and experiments to determine applicability to a number of missions.

DARPA is also interested in design services to assist developers utilize commercial processes in the development of the core hardware. Such design services may improve the cost, production, availability, flexibility or development time for the core hardware.

Additional Information

Demonstrations of Reference Designs are planned for Spring 2014 and Summer 2014. All performers are required to support these combined system experiments that are intended to test the core hardware, core software, and reference designs in a realistic data driven scenario.

Proposers must list any data items—for example, hardware designs, software or documentation—that will be delivered with restricted data rights. For any such data item, the proposed licensing terms and conditions, including proposed costs, must be supplied. Costs should be broken down into development support costs and per unit costs as applicable to the proposed licensing terms. Per unit costs must be supplied based on quantities of 100, 1000 and 10,000 or more licenses if per unit licenses are expected.

2. AWARD INFORMATION

Multiple awards are possible. 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.

Awards under this BAA will be made to proposers on the basis of the evaluation criteria listed below (see section labeled “Application Review Information”, Sec. 5.), and program balance to provide overall value to the Government. 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, and other factors. The Government reserves the right to request any additional, necessary documentation once it makes the award instrument determination. Such additional information may include but is not limited to Representations and Certifications. The Government reserves the right to remove proposers from award consideration should the parties fail to reach agreement on award terms, conditions and cost/price within a reasonable time or the proposer fails to timely provide requested additional information.

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,' i.e., 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. 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 nature of the research included in their proposal is fundamental or restricted, with the understanding that in all cases, the DARPA contracting officer shall have sole discretion to select award instrument type and to negotiate all instrument provisions with selectees. See Section 6.2.4 for further information on fundamental, non-fundamental and restricted research.

3. ELIGIBILITY INFORMATION

3.1 ELIGIBLE APPLICANTS

All responsible sources capable of satisfying the Government's needs may submit a proposal that shall be considered by DARPA. Historically Black Colleges and Universities (HBCUs), Small Businesses, Small Disadvantaged Businesses and Minority Institutions (MIs) are encouraged to submit proposals and join others in submitting proposals; however, no portion of this announcement will be set aside for these organizations’ participation due to the impracticality of reserving discrete or severable areas of this research for exclusive competition among these entities.

Federally Funded Research and Development Centers (FFRDCs) and Government entities (Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they address the following conditions. FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector AND must also provide a letter on letterhead from their sponsoring organization citing the specific authority establishing their 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 to be prime or subcontractors. Government entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority (as well as, where relevant, contractual authority) establishing their ability to propose to Government solicitations. At the present time, DARPA does not consider 15 U.S.C. 3710a to be sufficient legal authority to show eligibility.

While 10 U.S.C. 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility. DARPA will consider eligibility submissions on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the Proposer.

Foreign participants and/or individuals may participate to the extent that such participants comply with any necessary Non-Disclosure Agreements, Security Regulations, Export Control Laws, and other governing statutes applicable under the circumstances. See Section 4.2 “Security and Proprietary Issues” regarding the proposers capabilities to perform research and development at the classification level they propose.

Applicants considering classified submissions (or requiring access to classified information during the life-cycle of the program) shall ensure all industrial, personnel, and information system processing security requirements are in place and at the appropriate level (e.g., Facility Clearance (FCL), Personnel Security Clearance (PCL), Certification and Accreditation (C&A)) and any Foreign Ownership Control and Influence (FOCI) issues are mitigated prior to such submission or access. Additional information on these subjects can be found at: www.dss.mil.

3.1.1 Procurement Integrity, Standards of Conduct, Ethical Considerations, and Organizational Conflicts of Interest Current federal employees are prohibited from participating in particular matters involving conflicting financial, employment, and representational interests (18 USC 203, 205, and 208).

The DARPA Program Manager for this BAA is Mr. Mark Rich. Once the proposals have been received, and prior to the start of proposal evaluations, the Government will assess potential conflicts of interest and will promptly notify the Proposer if any appear to exist. (Please note, the Government assessment does NOT affect, offset, or mitigate the Proposer’s own duty to give full notice and planned mitigation for all potential organizational conflicts, as discussed below.)

Without prior approval or a waiver from the DARPA Director, in accordance with FAR 9.503, a Contractor cannot simultaneously provide scientific, engineering, technical assistance (SETA) or similar support and also be a technical performer. Therefore, all Proposers as well as proposed subcontractors and consultants must affirm whether they (their organizations and individual team members) are providing SETA or similar support to any DARPA technical office(s) through an active contract or subcontract. All affirmations must state which office(s) the Proposer, subcontractor, consultant, or individual supports and identify the prime contract number(s).

Affirmations shall be furnished at the time of proposal submission. All facts relevant to the existence or potential existence of organizational conflicts of interest (FAR 9.5) must be disclosed. The disclosure must include a description of the action the Proposer has taken or proposes to take to avoid, neutralize, or mitigate such conflict. If in the sole opinion of the Government after full consideration of the circumstances, a proposal fails to fully disclose potential conflicts of interest and/or any identified conflict situation cannot be effectively mitigated, the proposal will be rejected without technical evaluation and withdrawn from further consideration for award.

If a prospective Proposer believes that any conflict of interest exists or may exist (whether organizational or otherwise) or has questions on what constitutes a conflict of interest, the Proposer should promptly raise the issue with DARPA by sending his/her contact information and a summary of the potential conflict to the BAA mailbox before time and effort are expended in preparing a proposal and mitigation plan.

3.2 COST SHARING/MATCHING

Cost sharing is not required for this particular program; however, cost sharing will be carefully considered where there is an applicable statutory condition relating to the selected funding instrument (e.g., for any Other Transactions under the authority of 10 U.S.C. § 2371). Cost sharing is encouraged where there is a reasonable probability of a potential commercial application related to the proposed research and development effort.

3.3 OTHER ELIGIBILITY REQUIREMENTS

3.3.1 Collaborative Efforts

Collaborative efforts/teaming are encouraged.

4. APPLICATION AND SUBMISSION INFORMATION

4.1 ADDRESS TO REQUEST APPLICATION PACKAGE

This solicitation contains all information required to submit a proposal. No additional forms, kits, or other materials are needed. This notice, with the FOUO addendum - Supplemental Design Information, constitutes the total BAA. No additional information is available, nor will a formal Request for Proposal (RFP) or additional solicitation regarding this announcement be issued. Requests for same will be disregarded.

4.2 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.

The Government anticipates proposals submitted under this BAA will be unclassified. However, if a proposal is submitted as “Classified National Security Information” as defined by Executive Order 13526, then the information must be marked and protected as though classified at the appropriate classification level and then submitted to DARPA for a final classification determination.

Security classification guidance via a DD Form 254, “DoD Contract Security Classification Specification,” will not be provided at this time, since DARPA is soliciting ideas only. After reviewing the incoming proposals, if a determination is made that the award instrument may result in access to classified information; a DD Form 254 will be issued and attached as part of the award.

A formal request for the FOUO addendum may be submitted by filling out the FOUO Addendum Request Form (found in APPENDIX 4 to this BAA), the Verification of U.S.

Citizenship Form (found in APPENDIX 6 to this BAA), and/or the U.S. Permanent Resident and Foreign National Visit Request Form (found in APPENDIX 5 to this BAA) and emailing all appropriate forms to DARPA-BAA-12-61@darpa.mil with subject line titled “Request DARPA- BAA-12-61 FOUO Addendum.”

Proposers are encouraged to submit this request no later than 10 October 2012 to allow for adequate time for delivery of the material. The DARPA-BAA-12-61 FOUO Addendum Request Form is the only method of request that will be accepted. All requestors will receive a confirmation email with a delivery tracking number. Prior to receipt of any FOUO information, the request must be validated by the Program Security POC before any FOUO documentation on the BAA is sent to the performer.

Classified submissions shall be appropriately and conspicuously marked with the proposed classification level and declassification date. Submissions requiring DARPA to make a final classification determination shall be marked as follows:

CLASSIFICATION DETERMINATION PENDING. Protect as though classified (insert the recommended classification level: (e.g., Top Secret, Secret or Confidential)

Classified submissions shall be in accordance with the following guidance:

Confidential and Secret Collateral Information: Use classification and marking guidance provided by previously issued security classification guides, the DoD Information Security Manual (DoDM 5200.01, Volumes 1 - 4), and the National Industrial Security Program Operating Manual (DoD 5220.22-M) when marking and transmitting information previously classified by another Original Classification Authority. Classified information at the Confidential and Secret level may be submitted via ONE of the two following methods:

1. Hand-carried by an appropriately cleared and authorized courier to the DARPA CDR. Prior to traveling, the courier shall contact the DARPA CDR at 703-526-4052 to coordinate arrival and delivery.

OR

2. Mailed via appropriate U.S. Postal Service methods (e.g., (USPS)

Registered Mail or USPS Express Mail). All classified information will be enclosed in opaque inner and outer covers and double wrapped. The inner envelope shall be sealed and plainly marked with the assigned classification and addresses of both sender and addressee.

The inner envelope shall be addressed to:

Defense Advanced Research Projects Agency ATTN: Strategic Technology Office (STO) Reference: DARPA-BAA-12-61 675 North Randolph Street

The outer envelope shall be sealed with no identification as to the classification of its contents and addressed to:

Defense Advanced Research Projects Agency Security & Intelligence Directorate, Attn: CDR 675 North Randolph Street

All Top Secret materials: Top Secret information should be hand carried by an appropriately cleared and authorized courier to the DARPA CDR. Prior to traveling, the courier shall contact the DARPA CDR at 703-526-4052 to coordinate arrival and delivery.

Special Access Program (SAP) Information: SAP information must be transmitted via approved methods. Prior to transmitting SAP information, contact the DARPA SAPCO at 703-526-4052 for instructions.

Sensitive Compartmented Information (SCI): SCI must be transmitted via approved methods. Prior to transmitting SCI, contact the DARPA Special Security Office (SSO) at 703- 526-4052 for instructions.

Proprietary Data: All proposals containing proprietary data should have the cover page and each page containing proprietary data clearly marked as containing proprietary data. It is the Proposer’s responsibility to clearly define to the Government what is considered proprietary data.

Proposers must have existing and in-place prior to execution of an award, approved capabilities (personnel and facilities) to perform research and development at the classification level they propose. It is the policy of DARPA to treat all proposals as competitive information, and to disclose their contents only for the purpose of evaluation. Proposals will not be returned. The original of each proposal 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 unsuccessful notification.

4.3 CONTENT AND FORM OF APPLICATION SUBMISSION

4.3.1 Abstract and Proposal Information

Proposers are strongly encouraged to submit a proposal abstract in advance of a proposal. This procedure is intended to minimize unnecessary effort in proposal preparation and review. The time and date for submission of proposal abstracts is specified in Section 4.5.1 below. DARPA will acknowledge receipt of the submission and assign a control number that should be used in all further correspondence regarding the proposal abstract.

DARPA will respond to abstracts with a statement as to whether DARPA is interested in the idea. DARPA will attempt to reply to abstracts via letter within thirty (30) calendar days of receipt. Should a proposer be discouraged from submitting a full proposal, the letter must contain feedback for the proposer regarding the rationale for the decision not to recommend a full proposal be submitted. Abstracts will be reviewed in the order they are received. Early submissions of abstracts and full proposals are strongly encouraged because selections may be made at any time during the period of solicitation. Regardless of DARPA’s response to an abstract, proposers may submit a full proposal. DARPA will review all full proposals submitted using the published evaluation criteria and without regard to any comments resulting from the review of an abstract.

Proposers are required to submit proposals by the time and date specified in the BAA in order to be considered during the initial round of selections. DARPA may evaluate proposals received after this date for a period up to one year from date of posting on FedBizOpps. Ability to review late submissions remains contingent on availability of funds.

The typical proposal should express a consolidated effort in support of one or more related technical concepts or ideas. Disjointed efforts should not be included into a single proposal.

Restrictive notices notwithstanding, proposals may be handled, for administrative purposes only, by a support contractor. This support contractor is prohibited from competition in DARPA technical research and is bound by appropriate nondisclosure requirements. Proposals and/or proposed abstracts may not be submitted by fax or e-mail; any so sent will be disregarded.

Proposals not meeting the format described in the BAA may not be reviewed.

STO’s BAA Submission Portal:

Proposals and abstracts sent in response to DARPA-BAA-12-61 may be submitted via STO’s BAA Website (https://stobaa.sainc.com). Visit the website to register for an account (via the “Register your Organization” link along the left side of the homepage), view submission instructions, and upload/finalize abstracts and full proposals. All submissions must be compressed and encrypted as described below.

All proposals submitted electronically by means of an Electronic Business Application Tool or proposal submission website must be encrypted using WinZip or PKZip with 256-bit AES encryption. Please submit full proposals as two separate documents, Volume I (Technical and Management Proposal) and Volume II (Cost Proposal), uploaded as one single encrypted .zip file. Proposals not zipped/encrypted will be rejected by DARPA. An encryption password form must be completed and e-mailed to DARPA-BAA-12-61@darpa.mil at the time of submission.

See https://stobaa.sainc.com for the encryption password form (via the “Password Form” link along the left side of the homepage).

Note the word “PASSWORD” must appear in the subject line of the above e-mail and there are minimum security requirements for establishing the encryption password. Failure to provide the encryption password may result in the proposal not being evaluated. For further information and instructions on how to zip and encrypt proposal files, see https://stobaa.sainc.com.

Proposers using the STO BAA Website may encounter heavy traffic on the submission deadline date; it is highly advised that submission process be started as early as possible.

All administrative correspondence and questions on this solicitation, including requests for information on how to submit a proposal to this BAA, should be directed to one of the administrative addresses below; e-mail is preferred.

BAA Administrator E-mail: DARPA-BAA-12-61@darpa.mil

DARPA/STO

http://www.darpa.mil/sto/solicitations/solicit.htm

All administrative correspondence and questions on this solicitation, including requests for information on how to submit a proposal abstract or proposal to this BAA, should be directed to one of the administrative addresses below; e-mail is preferred.

DARPA/STO

ATTN: DARPA-BAA-12-61

675 North Randolph Street Arlington, VA 22203-2114 Email: DARPA-BAA-12-61@darpa.mil Office Website: http://www.darpa.mil/sto

DARPA intends to use electronic mail for correspondence regarding DARPA-BAA-12-61.

Proposals and proposal abstracts may not be submitted by fax or e-mail; any so sent will be disregarded. DARPA encourages use of the Internet for retrieving the BAA and any other related information that may subsequently be provided.

4.3.2 Restrictive Markings on Proposals

All proposals should clearly indicate limitations on the disclosure of their contents. Proposers who include in their proposals data that they do not want disclosed to the public for any purpose, or used by the Government except for evaluation purposes, shall-

(1) Mark the title page with the following legend:

This proposal includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed-in whole or in part-for any purpose other than to evaluate this proposal. If, however, a contract is awarded to this proposer as a result of, or in connection with, the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract. This restriction does not limit the Government's right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]; and

(2) Mark each sheet of data it wishes to restrict with the following legend:

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.

Markings like "Company Confidential" or other phrases that may be confused with national security classifications shall be avoided. See Section 6.0, for additional information.

4.4 FORMATTING CHARACTERISTICS

4.4.1 Proposal Abstract Format

Proposal abstracts are encouraged in advance of proposals in order to provide potential proposers with a rapid response to minimize unnecessary effort. Proposal abstracts should follow the same general format as described for Volume I under PROPOSAL FORMAT (see below), but include ONLY Sections I and II. The cover sheet should be clearly marked “PROPOSAL ABSTRACT” and the total length should not exceed 10 pages, excluding cover page and official transmittal letter. All pages shall be printed on 8-1/2 by 11 inch paper with type not smaller than 12 point.

Smaller font may be used for figures, tables and charts, but will be ignored if not legible. The page limitation for proposal abstracts includes all figures, tables, and charts. No formal transmittal letter is required. All proposal abstracts must be written in English.

4.4.1.1. {1} Cover sheet to include:

1. BAA number DARPA-BAA-12-61

2. Technical area (see Sec 1.1)

3. Lead Organization Submitting proposal

4. Type of business, selected among the following categories: "LARGE BUSINESS,"

"SMALL DISADVANTAGED BUSINESS," "OTHER SMALL BUSINESS,"

"HBCU," "MI," "OTHER EDUCATIONAL,” or "OTHER NONPROFIT"

5. Contractor’s reference number (if any)

6. Other team members (if…