HR001119S0070.pdf

Broad Agency Announcement Pecan

BIOLOGICAL TECHNOLOGIES OFFICE

HR001119S0070

July 3, 2019

HR001119S0070, Pecan

TABLE OF CONTENTS

PART I: OVERVIEW INFORMATION

PART II: FULL TEXT OF ANNOUNCEMENT

1. Funding Opportunity Description

1.1. Program Overview

1.2. Technical Approach

1.3. Program Structure

1.4. Program Metrics

1.5. Permits and Compliance

1.6. General Requirements

1.7. Additional Information

2. Award Information

2.1. General Award Information

2.2. Fundamental Research

3. Eligibility Information

3.1. Eligible Applicants

3.2. Organizational Conflicts of Interest

3.3. Cost Sharing/Matching

4. Application and Submission Information

4.1. Address to Request Application Package

4.2. Content and Form of Application Submission

4.3. Funding Restrictions

4.4. Other Submission Requirements

5. Application Review Information

5.1. Evaluation Criteria

5.2. Review of Proposals

6. Award Administration Information

6.1. Selection Notices

6.2. Administrative and National Policy Requirements

6.3. Reporting

6.4. Electronic Systems

7. Agency Contacts

8. Other Information

8.1. Teaming Information

8.2. Proposers Day

9. APPENDIX 1 – Volume II Checklist

10. APPENDIX 2 – Classified Addendum Request Form

LIST OF ATTACHMENTS

Attachment 1 – Full Proposal Summary Slide Template

Attachment 2 – Statement of Work (SOW) Template

Attachment 3 – Budget Template

PART I: OVERVIEW INFORMATION

Federal Agency Name – Defense Advanced Research Projects Agency (DARPA), Biological Technologies Office

Funding Opportunity Title – Pecan Announcement Type – Initial announcement Funding Opportunity Number – HR001119S0070 Catalog of Federal Domestic Assistance Numbers (CFDA) – 12.910 Research and

Technology Development Dates o Posting Date: July 3, 2019 o Proposal Abstract Due Date: August 20, 2019 o Proposal Due Date: October 1, 2019 o Deadline to Request Copies of the Classified Addendum: September 6, 2019 o Proposers Day: See classified addendum

Concise description of the funding opportunity: DARPA seeks expertise in synthetic biology and biochemistry of synthetic biology and biochemistry.

Anticipated individual awards – Multiple awards are anticipated.

Types of instruments that may be awarded – Procurement contract or Other

Transaction.

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

Pecan@darpa.mil

DARPA/BTO

ATTN: HR001119S0070

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

PART II: FULL TEXT OF ANNOUNCEMENT

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

DARPA seeks expertise in synthetic biology and biochemistry of synthetic biology and biochemistry.

1.1. PROGRAM OVERVIEW

See classified addendum.

1.2. TECHNICAL APPROACH

See classified addendum.

1.3. PROGRAM STRUCTURE

See classified addendum.

1.4. PROGRAM METRICS

See classified addendum.

1.5. PERMITS AND COMPLIANCE

See classified addendum.

1.6. GENERAL REQUIREMENTS

See classified addendum.

1.7. ADDITIONAL INFORMATION

Proposing Teams It is expected that proposals will involve multidisciplinary teams that include expertise from multiple complementary disciplines.

Specific content, communications, networking, and team formation are the sole responsibility of the proposer teams. Proposer teams must submit a single, integrated proposal led by a single Program Integrator/Manager or prime contractor that addresses all program phases, as applicable.

DARPA will hold a Proposers Day to facilitate the formation of proposer teams with the expertise necessary to meet the goals of the program and enable sharing of information among interested proposers. See the Classified Addendum for more information.

Data Sharing DARPA anticipates that a large amount of data will be generated under this program by each performer and that the approaches and validation will be strengthened by compiling and integrating information across all performers. The Pecan program will require that performer data and analysis be shared with DARPA, the Independent Verification & Validation (IV&V) partner, and U.S. Government stakeholders. DARPA encourages sharing of pre-existing data, including those generated through funding from other sources, with the aforementioned entities although this is not a requirement of the program.

2. Award Information

2.1. GENERAL AWARD INFORMATION

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

The Government reserves the right to select for negotiation all, some, one, or none of the proposals received in response to this solicitation and to make awards without discussions with proposers. The Government also reserves the right to conduct discussions if it is later determined to be necessary. If warranted, portions of resulting awards may be segregated into pre-priced options. Additionally, DARPA reserves the right to accept proposals in their entirety or to select only portions of proposals for award. In the event that DARPA desires to award only portions of a proposal, negotiations may be opened with that proposer. The Government reserves the right to fund proposals in phases with options for continued work, as applicable.

The Government reserves the right to request any additional, necessary documentation once it makes the award instrument determination. Such additional information may include but is not limited to Representations and Certifications (see Section VI.B.2., “Representations and Certifications”).

The Government reserves the right to remove proposers from award consideration should the parties fail to reach agreement on award terms, conditions, and/or cost/price within a reasonable time, and the proposer fails to timely provide requested additional information. Proposals identified for negotiation may result in a procurement contractor Other Transaction, depending upon the nature of the work proposed, the required degree of interaction between parties, whether or not the research is classified as Fundamental Research, and other factors.

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

In accordance with 10 U.S.C. § 2371b(f), the Government may award a follow-on production contract or Other Transaction (OT) for any OT awarded under this BAA if: (1) that participant in the OT, or a recognized successor in interest to the OT, successfully completed the entire prototype project provided for in the OT, as modified; and (2) the OT provides for the award of a http://www.darpa.mil/work-with-us/contract-management#OtherTransactions http://www.darpa.mil/work-with-us/contract-management#OtherTransactions follow-on production contract or OT to the participant, or a recognized successor in interest to the OT.

In all cases, the Government contracting officer shall have sole discretion to select award instrument type, regardless of instrument type proposed, and to negotiate all instrument terms and conditions with selectees. DARPA will apply publication or other restrictions, as necessary, if it determines that the research resulting from the proposed effort will present a high likelihood of disclosing performance characteristics of military systems or manufacturing technologies that are unique and critical to defense. Any award resulting from such a determination will include a requirement for DARPA permission before publishing any information or results on the program. For more information on publication restrictions, see the section below on Fundamental Research.

2.2. FUNDAMENTAL RESEARCH

It is DoD policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 defines fundamental research as follows:

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

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

Proposers should indicate in their proposal whether they believe the scope of the research included in their proposal is fundamental or not. While proposers should clearly explain the intended results of their research, the Government shall have sole discretion to determine whether the proposed research shall be considered fundamental and to select the award instrument type. Appropriate language will be included in resultant awards for non-fundamental research to prescribe publication requirements and other restrictions, as appropriate. This language can be found at http://www.darpa.mil/work-with-us/additional-baa.

For certain research projects, it may be possible that although the research to be performed by a potential awardee is non-fundamental research, its proposed subawardee’s effort may be fundamental research. It is also possible that the research performed by a potential awardee is fundamental research while its proposed subawardee’s effort may be non-fundamental research.

In all cases, it is the potential awardee’s responsibility to explain in its proposal which proposed http://www.darpa.mil/work-with-us/additional-baa efforts are fundamental research and why the proposed efforts should be considered fundamental 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.

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

FFRDCs FFRDCs are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions. (1) FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector. (2) FFRDCs must provide a letter, on official letterhead from their sponsoring organization, that (a) cites the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and (b) certifies the FFRDC’s compliance with the associated FFRDC sponsor agreement’s terms and conditions. These conditions are a requirement for FFRDCs proposing to be awardees or subawardees.

Government Entities Government Entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations. Government Entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority and contractual authority, if relevant, establishing their ability to propose to Government solicitations and compete with industry. This information is required for Government Entities proposing to be awardees or subawardees.

Authority and Eligibility At the present time, DARPA does not consider 15 U.S.C. § 3710a to be sufficient legal authority to show eligibility. While 10 U.S.C.§ 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility. DARPA will consider FFRDC and Government Entity eligibility submissions on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer.

3.1.2. Applicants Considering Classified Submissions

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 http://www.dss.mil.

http://www.dss.mil/

3.2. ORGANIZATIONAL CONFLICTS OF INTEREST

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

FAR 9.505-4.

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

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

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

The name of the DARPA office receiving the support;

The prime contract number;

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

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

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

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

3.3. COST SHARING/MATCHING

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

4. Application and Submission Information

4.1. ADDRESS TO REQUEST APPLICATION PACKAGE

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

4.1.1. Program Security

This program will be executed in the SECRET security environment in accordance with the Pecan DARPA Program Security Classification Guide. The proposer is responsible for providing adequate cleared personnel, IT infrastructure, and facilities to execute the program IAW the

NISPOM.

The Government will provide a program protection plan at contract award. The contractor shall provide a program protection implementation plan, security manufacturing plan, transportation plans, and security test plans. The program protection implementation is required 60 days after contract award. The security manufacturing plan is required 60 days after contract award.

Transportation plans are due to DARPA 60 days prior to planned shipments of classified material. Security test plans shall be delivered 60 days prior to test events.

4.1.2. Classified Addendum

A formal request for the HR001119S0070 Classified Addendum and the Security Classification Guide may be submitted by filling out the Classified Addendum Request Form (found in Appendix 2 to this BAA) and emailing the Request Form to Pecan@darpa.mil with the subject line titled “Request HR001119S0070 Classified Addendum and Security Classification Guide.”

Requests for the Classified Addendum should include, at a minimum, the company name, technical point of contact (POC) name and phone number, Facility Security Officer (FSO) name and phone number, CAGE code, statement of facility clearance and safeguarding capability, and a valid U.S. Postal Service address for receiving classified material at the Secret level. DARPA will verify the facility clearance and the clearance of the recipient before e-mailing (via secure system) and/or mailing the classified material.

Proposers should allow at least five (5) business days for processing requests for the classified addendums plus time for delivery. Requests for this information will not be accepted after September 6, 2019.

https://www.fbo.gov/

DARPA intends to use the FedEx shipping service in an effort to expedite receipt of the addendum. Please note that any requesting organizations that are unable to accept this form of delivery may experience delays.

4.2. CONTENT AND FORM OF APPLICATION SUBMISSION

All submissions, including abstracts and proposals, must be written in English with type not smaller than 12-point font. Smaller font may be used for figures, tables, and charts. Copies of all documents submitted must be clearly labeled with the DARPA BAA number, proposer organization, and proposal title/proposal short title.

4.2.1. Proposal Abstract Format

Proposers are strongly encouraged to submit an abstract in advance of a proposal to minimize effort and reduce the potential expense of preparing an out of scope proposal. The abstract is a concise version of the proposal comprising a maximum of six (6) pages including all figures, tables, and charts. All submissions must be written in English with type no smaller than 12-point font. Smaller font may be used for figures, tables, and charts. All pages shall be formatted for printing on 8-1/2 by 11 inch paper. Margins must be 1-inch on all sides. Copies of all documents submitted must be clearly labeled with the DARPA BAA number, proposer organization, and proposal abstract title.

Abstracts must include the following components:

A. Cover Sheet (does not count towards page limit): Include the administrative and technical points of contact (name, address, phone, fax, email, lead organization). Also include the BAA number, title of the proposed project, primary subcontractors, estimated cost, duration of the project, and the label “ABSTRACT.”

B. Goals and Impact: Clearly describe what is being proposed and what difference it will make (qualitatively and quantitatively), including brief answers to the following questions:

1. What is the proposed work attempting to accomplish or do?

2. How is it done today and what are the limitations of the current practice?

3. What is innovative in your approach and how does it compare to the current state-of-the-art (SOA)?

4. What are the key technical challenges in your approach and how do you plan to overcome these?

5. Who cares? If you are successful, what difference will it make?

6. How much will it cost and how long will it take?

C. Technical Plan: Outline and address all technical challenges inherent in the approach and possible solutions for overcoming potential problems. This section should provide a plan for accomplishment of the milestones.

D. Capabilities: Provide a brief summary of expertise of the team, including subcontractors and key personnel. A principal investigator for the project must be identified. No more than two resumes should be included as part of the abstract, and one resume must be from the PI. Resumes do not count as part of the page limit.

Include a description of the team’s organization including roles and responsibilities.

Describe the organizational experience in this area, existing intellectual property required to complete the project, and any specialized facilities to be used as part of the project. List Government-furnished materials or data assumed to be available. If desired, include a brief bibliography with links to relevant papers or reports.

E. Cost and Schedule: Cost and schedule for the proposed research, including an estimate of (a) total cost, (b) cost for each task in each phase of the effort by prime and major subcontractors, and (c) any cost share (if applicable).

4.2.2. Proposal Format

All full proposals must be in the format given below. Proposals shall consist of two volumes: 1) Volume I, Technical and Management Proposal, and 2) Volume II, Cost Proposal. All pages must be written in Enlgihs and 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. The page limitation for full proposals includes all figures, tables, and charts. Margins must be 1-inch on all sides. Copies of all documents submitted must be clearly labeled with the DARPA BAA number, proposer organization, and proposal title/proposal short title. Volume I, Technical and Management Proposal, may include an attached bibliography of relevant technical papers or research notes (published and unpublished) which document the technical ideas and approach upon which the proposal is based. Copies of not more than three (3) relevant papers may be included with the submission. The bibliography and attached papers are not included in the page counts given below. The submission of other supporting materials along with the proposals is strongly discouraged and will not be considered for review. The maximum page count for Volume 1 is 30 pages. The official transmittal letter is not included in the page count. Volume I should include the following components:

NOTE: Non-conforming submissions that do not follow the instructions herein may be rejected without further review.

a. Volume I, Technical and Management Proposal

Section I. Administrative

A. Cover Sheet (LABELED “PROPOSAL: VOLUME I”):

1. BAA number (HR001119S0070);

2. Lead organization submitting proposal (prime contractor);

3. Type of organization, selected from among the following categories: “LARGE

BUSINESS,” “SMALL DISADVANTAGED BUSINESS,” “OTHER SMALL

BUSINESS,” “HBCU,” “MI,” “OTHER EDUCATIONAL,” OR “OTHER

NONPROFIT”;

4. Proposer’s reference number (if any);

5. Other team members (if applicable) and type of business for each;

6. Proposal title (MUST BE UNCLASSIFIED);

7. Technical point of contact (Program Manager or Principal Investigator) to include:

salutation, last name, first name, street address, city, state, zip code, telephone, fax, e-mail;

8. Administrative point of contact (Contracting Officer or Grant Officer) to include:

salutation, last name, first name, street address, city, state, zip code, telephone, fax, e-mail;

9. Award instrument requested: cost-plus-fixed-free (CPFF), cost-contract—no fee, firm-fixed-price, Other Transaction, or other type (specify);

10. Place(s) and period(s) of performance;

11. Proposal validity period;

12. Total funds requested from DARPA, and the amount of cost share (if any); AND

13. Date proposal was submitted.

Information on award instruments is available at http://www.darpa.mil/work-with-us/contract-management.

B. Official Transmittal Letter

C. Executive Summary Slides: Provide a one-slide summary in PowerPoint that effectively and succinctly conveys the main objective, key innovations, expected impact, and other unique aspects of the proposed project. The slide template is provided as Attachment 1 to the BAA posted at http://www.fbo.gov. Use of this template is required.

Section II. Detailed Proposal Information

A. Executive Summary: Provide a synopsis of the proposed project, including answers to the following questions:

What is the proposed work attempting to accomplish or do?

How is it done today, and what are the limitations?

What is innovative in your approach?

What are the key technical challenges in your approach and how do you plan to overcome these?

Who or what will be affected and what will be the impact if the work is successful?

How much will it cost, and how long will it take?

http://www.darpa.mil/work-with-us/contract-management http://www.darpa.mil/work-with-us/contract-management http://www.fbo.gov/

B. Goals and Impact: Clearly describe what the team is trying to achieve and the difference it will make (qualitatively and quantitatively) if successful. Describe the innovative aspects of the project in the context of existing capabilities and approaches, clearly delineating the uniqueness and benefits of this project in the context of the state of the art, alternative approaches, and other projects from the past and present. Describe how the proposed project is revolutionary and how it significantly rises above the current state of the art. Describe the deliverables associated with the proposed project and any plans to commercialize the technology, transition it to a customer, or further the work.

C. Technical Plan: Outline and address technical challenges inherent in the approach and possible solutions for overcoming potential problems. This section should provide appropriate measurable milestones (quantitative if possible) at intermediate stages of the program to demonstrate progress, and a plan for achieving the milestones (see Classified Addendum this BAA). The technical plan should demonstrate a deep understanding of the technical challenges and present a credible (even if risky) plan to achieve the program goal. Discuss mitigation of technical risk.

D. Management Plan: Provide a summary of expertise of the team, including any subcontractors, and key personnel who will be doing the work. Resumes count against the proposal page count. Identify a principal investigator for the project. Provide a clear description of the team’s organization including an organization chart that includes, as applicable: the programmatic relationship of team members; the unique capabilities of team members; the task responsibilities of team members, the teaming strategy among the team members; and key personnel with the amount of effort to be expended by each person during each year. Provide a detailed plan for coordination including explicit guidelines for interaction among collaborators/subcontractors of the proposed effort.

Include risk management approaches. Describe any formal teaming agreements that are required to execute this program.

E. Capabilities: Describe organizational experience in relevant subject area(s), existing intellectual property, and any Government-furnished materials or information. Discuss any work in closely related research areas and previous accomplishments.

F. Statement of Work (SOW): The SOW should provide a detailed task breakdown, citing specific tasks for each Technical Area, and their connection to the milestones and program metrics. Each phase (Phase I (Base), Phase II (Option), and Phase III (Option)) of the program should be separately defined, and all tasks/subtasks should be identified by Technical Area. The SOW must not include proprietary information. It is encouraged, though not required, to use the SOW template provided as Attachment 2. SOW is not included in the Volume 1 page count.

For each task/subtask, provide:

A detailed description of the approach to be taken that includes metrics, methods, and an assessment plan.

Identification of the primary organization responsible for task execution (prime contractor, subcontractor(s), consultant(s), by name).

Measurable milestone(s), deliverable(s), demonstration(s), or other event/activity signifying task completion.

A definition of all deliverables (e.g., data, reports, software) to be provided to the

Government in support of the proposed tasks/subtasks.

G. Schedule and Milestones: Provide a detailed schedule showing tasks (task name, duration, work breakdown structure element as applicable, performing organization), milestones, and the interrelationships among tasks. The task structure must be consistent with that in the SOW. Measurable milestones should be clearly articulated and defined in time relative to the start of the project.

H. Technology Transfer Plan: Proposers should provide a detailed plan, with milestones, showing how safety, and transition aspects of the technology will be addressed. The plan should include descriptions of how potential DoD users will be engaged as well as paths for commercialization of the technology.

b. Volume II, Cost Management Proposal (MUST BE UNCLASSIFIED)

Cover Sheet (LABELED “PROPOSAL: VOLUME II”) with Appendix I:

1. BAA number (HR001119S0070);

2. Lead Organization Submitting proposal;

3. Type of organization, selected among the following categories: “LARGE BUSINESS”, “SMALL DISADVANTAGED BUSINESS”, “OTHER SMALL BUSINESS”, “HBCU”, “MI”, “OTHER EDUCATIONAL”, OR “OTHER NONPROFIT”;

4. Proposer’s reference number (if any);

5. Other team members (if applicable) and type of business for each;

6. Proposal title (MUST BE UNCLASSIFIED);

7. Technical point of contact (Program Manager or Principal Investigator) to include:

salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), electronic mail (if available);

8. Administrative point of contact (Contracting Officer or Grant Officer) to include:

salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), and electronic mail (if available);

9. Award instrument requested: cost-plus-fixed-free (CPFF), cost-contract—no fee, cost sharing contract – no fee, or other type of procurement contract (specify), or Other Transaction;

10. Place(s) and period(s) of performance;

11. Total proposed cost separated by basic award (12 months) and options (12 and 18 months, respectively);

12. Name, address, and telephone number of the proposer’s cognizant Defense Contract

Management Agency (DCMA) administration office (if known);

13. Name, address, and telephone number of the proposer’s cognizant Defense Contract

Audit Agency (DCAA) audit office (if known);

14. Date proposal was prepared;

15. Data universal numbering system (DUNS) number (http://www.dnb.com/get-a-duns-number.html);

16. Taxpayer ID number (https://www.irs.gov/Individuals/International-

Taxpayers/Taxpayer-Identification-Numbers-TIN);

17. Commercial and Government Entity (CAGE) code

(https://cage.dla.mil/Home/UsageAgree); and

18. Proposal validity period.

NOTE: Non-conforming submissions that do not address both Technical Areas and/or follow the instructions herein may be rejected without further review.

The Government encourages proposers to complete an editable MS excel budget template that covers many of the items discussed below. This template document is provided as Attachment 3 to this BAA. If proposers choose to use Attachment 3, submit the MS Excel template in addition to Volume I and II of their proposal. The template is not a Volume II alternative. Volume II must include all other items discussed below that are not covered by the editable MS excel budget template. Proposers are welcome to utilize an alternative format, provided the information requested below is clearly and effectively communicated.

(1) Please submit any breakdown of expenses in an editable, MS EXCEL cost file.

(2) Total program, per phase (Phase I (Base); Phase II (Option); and Phase III (Option)), and per task cost broken down by major cost items to include:

i. Direct Labor – Including individual labor categories with associated labor hours and direct labor rates. If selected for award, be prepared to submit supporting documentation to justify labor rates. (i.e., screenshots of HR databases, comparison to NIH or other web-based salary database);

For Equipment and Materials, include a sanitized list.

ii. Materials and Supplies – itemized list which includes description of material, quantity, unit price, and total price. If a material factor is used based on historical purchases, provide data to justify the rate.

http://www.dnb.com/get-a-duns-number.html http://www.dnb.com/get-a-duns-number.html https://www.irs.gov/Individuals/International-Taxpayers/Taxpayer-Identification-Numbers-TIN https://www.irs.gov/Individuals/International-Taxpayers/Taxpayer-Identification-Numbers-TIN https://cage.dla.mil/Home/UsageAgree

iii. Equipment – itemized list which includes description of equipment, unit price, quantity, and total price. Any equipment item with a unit price over $5,000 must include a vendor quote.

iv. Animal Use Costs – itemized list of all materials, animal purchases, and per diem costs, associated with proposed animal use; include documentation supporting daily rates.

v. Travel – provide an itemized list of travel costs to include purpose of trips, departure and arrival destinations, projected airfare, rental car and per General Services Administration approved diem, number of travelers, number of days); provide screenshots from travel website for proposed airfare and rental car, as applicable;

provide screenshot or web link for conference registration fee and note if the fee includes hotel cost. Conference attendance must be justified, explain how it is in the best interest of the project. Plan for two (2) DARPA program review meetings per year.

vi. Other Direct Costs (e.g., computer support, clean room fees) – Should be itemized with costs or estimated costs. Backup documentation and/or a supporting cost breakdown is required to support proposed costs with a unit price over $5,000. An explanation of any estimating factors, including their derivation and application, must be provided. Please include a brief description of the proposers’ procurement method to be used.

vii. Consultants – provide executed Consultant Agreement that describes work scope, rate and hours.

viii. Indirect Costs – including, as applicable, fringe benefits, overhead, General and Administrative (G&A) expense, and cost of money (see University vs. Company specific requirements below.

ix. Indirect costs specific to a University performer: (1) Fringe Benefit Rate (provide current Department of Health and Human Services (DHHS) or Office of Naval Research (ONR) negotiated rate package; if calculated by other than a rate, provide University documentation identifying fringe costs by position or HR documentation if unique to each person); (2) F&A Indirect Overhead Rate (provide current DHHS or ONR negotiated rate package); (3) Tuition Remission (provide current University documentation justifying per student amount); and (4) Health Insurance/Fee (provide current University documentation justifying per student amount, if priced separately from fringe benefits with calculations included in the EXCEL cost file).

x. Indirect costs specific to a Company performer: (1) Fee/Profit (provide rationale for proposed fee/profit percentage using criteria found in DFARS 215.404-70); and

(2) Fringe Benefit/Labor OH/Material OH/G&A Rates (provide current Forwarding Pricing Rate Proposal (FPRP) or DCMA/DCAA Forward Pricing Rate Recommendation or Agreement (FPRR or FPRA). If these documents are not available, provide company historical data, preferably two years, minimum of one, to include both pool and expense costs used to generate the rates).

(3) A summary of total program costs by phase I, II, and III and task;

(4) An itemization of Subcontracts. All subcontractor cost proposal documentation must be prepared at the same level of detail as that required of the prime. Subcontractor proposals should include Interdivisional Work Transfer Agreements (IWTA) or evidence of similar arrangements (an IWTA is an agreement between multiple divisions of the same organization). The prime proposer is responsible for compiling and providing all subcontractor proposals for the Procuring Contracting Officer (PCO). The proposal must show how subcontractor costs are applied to each phase and task. If consultants are to be used, proposer must provide consultant agreement or other document that verifies the proposed loaded daily/hourly rate.

(5) An itemization of any information technology (IT) purchase (including a letter stating why the proposer cannot provide the requested resources from its own funding), as defined in FAR Part 2.101;

(6) A summary of project funding requirements by month for all the phases of the project.

(7) A summary of tasks that have animal or human use funding.

(8) The source, nature, and amount of any industry cost-sharing. Where the effort consists of multiple portions which could reasonably be partitioned for purposes of funding, these should be identified as options with separate cost estimates for each;

(9) Identification of pricing assumptions of which may require incorporation into the resulting award instrument (e.g., use of Government Furnished Property/Facilities/Information, access to Government Subject Matter Expert(s), etc.);

(10) Any Forward Pricing Rate Agreement, DHHS rate agreement, other such approved rate information, or such documentation that may assist in expediting negotiations (if available); and

(11) Proposers with a Government acceptable accounting system who are proposing a cost-type contract must submit the DCAA document approving the cost accounting system.

Per FAR 15.403-4, certified cost or pricing data shall be required if the proposer is seeking a procurement contract award per the referenced threshold, unless the proposer requests and is granted an exception from the requirement to submit cost or pricing data. Certified cost or pricing data” are not required if the proposer proposes an award instrument other than a procurement contract (e.g., an other transaction.)

Subawardee Proposals The awardee is responsible for compiling and providing all subawardee proposals for the Procuring Contracting Officer (PCO)/Grants Officer (GO)/Agreements Officer (AO), as applicable. Subawardee proposals should include Interdivisional Work Transfer Agreements (ITWA) or similar arrangements. Where the effort consists of multiple portions which could reasonable be partitioned for purposes of funding, these should be identified as options with separate cost estimates for each.

All proprietary subawardee proposal documentation, prepared at the same level of detail as that required of the awardee’s proposal and which cannot be uploaded with the proposed awardee’s proposal, shall be provided to the Government either by the awardee or by the subawardee organization when the proposal is submitted. Subawardee proposals submitted to the Government by the proposed subawardee should be submitted via e-mail to the address in Section I.

Other Transaction Requests All proposers requesting an OT must include a detailed list of milestones for each phase of the program (I, II, and III). Each milestone must include the following:

milestone description, completion criteria, due date, and payment/funding schedule (to include, if cost share is proposed, awardee and

Government share amounts).

It is noted that, at a minimum, milestones should relate directly to accomplishment of program technical metrics as defined in the BAA and/or the proposer’s proposal. Agreement type, expenditure or fixed-price based, will be subject to negotiation by the Agreements Officer. Do not include proprietary data.

4.2.3. Additional Proposal Information

Proprietary Markings Proposers are responsible for clearly identifying proprietary information. Submissions containing proprietary information must have the cover page and each page containing such information clearly marked with a label such as “Proprietary” or “Company Proprietary.” NOTE:

“Confidential” is a classification marking used to control the dissemination of U.S. Government National Security Information as dictated in Executive Order 13526 and should not be used to identify proprietary business information.

Security Information DARPA anticipates that submissions received under this BAA will be classified. Submission information can be found below and in Section 4.2.4.

The classified proposal shall use the outline and section numbering as directed by this document and the classified addendum. DARPA will provide specific security classification guidance via a Security Classification Guide (SCG) and/or DARPA DD Form 254, “DoD Contract Security Classification Specification”.

a) Classified Proposal Markings Classified submissions shall be transmitted and marked in accordance with the following guidance. If a submission contains Classified National Security Information or the suspicion of such, as defined by Executive Order 13526, the information must 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 SECRET” NOTE: Classified submissions must indicate the classification level of not only the submitted materials, but also the classification level of the anticipated award.

b) Classified Submission Requirements and Procedures Proposers submitting classified information must have, or be able to obtain prior to contract award, cognizant security agency approved facilities, information systems, and appropriately cleared/eligible personnel to perform at the classification level proposed. All proposer personnel performing Information Assurance (IA)/Cybersecurity related duties on classified Information Systems shall meet the requirements set forth in DoD Manual 8570.01-M (Information Assurance Workforce Improvement Program). Additional information on the subjects discussed in this section may be found at http://www.dss.mil.

Proposers choosing to submit classified information from other collateral classified sources (i.e., sources other than DARPA) must ensure (1) they have permission from an authorized individual at the cognizant Government agency (e.g., Contracting Officer, Program Manager); (2) the proposal is marked in accordance with the source Security Classification Guide (SCG) from which the material is derived; and (3) the source SCG is submitted along with the proposal.

When submitting a hard copy of the classified proposal according to the instructions outlined below, proposers should submit six (6) hard copies of the classified proposal and two (2) CD- ROMs containing the classified proposal broken into separate files containing:

(1) the proposal abstract with required attachments in searchable Adobe PDF,

(2) full proposal Volume I in searchable Adobe PDF,

(3) full proposal Volume II in searchable Adobe PDF, and

(4) the unclassified budget spreadsheet in Microsoft Excel.

Classified Information Use transmission, classification, handling, and marking guidance provided by the solicitation SCG, the DoD Information Security Manual (DoDM 5200.01, Volumes 1 - 4), and the National Industrial Security Program Operating Manual, including the Supplement Revision 1 (DoD 5220.22-M and DoD 5200.22-M Sup. 1), when submitting Confidential, Secret, and/or Top Secret classified information.

Secret classified information may be submitted via ONE of the two following methods to the mailing address listed in the contact information in Part I of this BAA:

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

OR

Mailed via U.S. Postal Service (USPS) Registered Mail, USPS Express Mail, or Federal Express (FedEx). 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 http://www.dss.mil/ envelope shall be addressed to Defense Advanced Research Projects Agency, ATTN:

DARPA/BTO Dr. Christian Sund, with a reference to the BAA number.

Each copy must be clearly labeled with BAA number HR001119S0070, proposer organization, technical point of contact, and unclassified proposal title (unclassified short title recommended).

Senders should mail to the mailing address listed in the contact information herein.

Subcontractor proposals not submitted by the Prime should include the Prime organization name, proposal title (same as the Prime), and the Subcontractor contact information on the inner envelope.

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.

Disclosure of Information and Compliance with Safeguarding Covered Defense Information Controls The following provisions and clause apply to all solicitations and contracts; however, the definition of “controlled technical information” clearly exempts work considered fundamental research and therefore, even though included in the contract, will not apply if the work is fundamental research.

DFARS 252.204-7000, “Disclosure of Information” DFARS 252.204-7008, “Compliance with Safeguarding Covered Defense Information Controls” DFARS 252.204-7012, “Safeguarding Covered Defense Information and Cyber Incident Reporting”

The full text of the above solicitation provision and contract clauses can be found at http://www.darpa.mil/work-with-us/additional-baa#NPRPAC.

Compliance with the above requirements includes the mandate for proposers to implement the security requirements specified by National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations” (see https://doi.org/10.6028/NIST.SP.800-171r1) that are in effect at the time the BAA is issued.

For awards where the work is considered fundamental research, the contractor will not have to implement the aforementioned requirements and safeguards. However, should the nature of the work change during performance of the award, work not considered fundamental research will be subject to these requirements.

Human Subjects Research (HSR)/Animal Use Proposers that anticipate involving human subjects or animals in the proposed research must comply with the approval procedures detailed at http://www.darpa.mil/work-with-us/additional-baa, to include providing the information specified therein as required for proposal submission.

http://www.darpa.mil/work-with-us/additional-baa#NPRPAC https://doi.org/10.6028/NIST.SP.800-171r1

Approved Cost Accounting System Documentation Proposers that do not have a Cost Accounting Standards (CAS) compliant accounting system considered adequate for determining accurate costs that are negotiating a cost- type procurement contract must complete an SF 1408. For more information on CAS compliance, see http://www.dcaa.mil/cas.html. To facilitate this process, proposers should complete the SF 1408 found at http://www.gsa.gov/portal/forms/download/115778 and submit the completed form with the proposal. To complete the form, check the boxes on the second page, then provide a narrative explanation of your accounting system to supplement the checklist on page one. For more information, see (https://www.dcaa.mil/Content/Documents/Preaward_Survey_of_Prospective_Contractor_Accou nting_System_Checklist.pdf).

Small Business Subcontracting Plan Pursuant to Section 8(d) of the Small Business Act (15 U.S.C. § 637(d)) and FAR 19.702(a)(1), each proposer who submits a contract proposal and includes subcontractors might be required to submit a subcontracting plan with their proposal. The plan format is outlined in FAR 19.704.

Section 508 of the Rehabilitation Act (29 U.S.C. § 749d)/FAR 39.2 All electronic and information technology acquired or created through this BAA must satisfy the accessibility requirements of Section 508 of the Rehabilitation Act (29 U.S.C. § 749d)/FAR 39.2.

Intellectual Property All proposers must provide a good-faith representation that the proposer either owns or possesses the appropriate licensing rights to all intellectual property that will be utilized under the proposed effort.

For Procurement Contracts

Proposers responding to this BAA requesting procurement contracts…