HR001120S0057-Amendment-01.pdf

Broad Agency Announcement

Moving Target Recognition (MTR)

STRATEGIC TECHNOLOGY OFFICE

HR001120S0057

Amendment 01

September 11, 2020

Summary of Amendment 01 Changes:

The purpose of this amendment is to revise the classified submission language in Section IV.B.2.b. Security Information (page 19) and to extend the proposal due date by two calendar days as denoted in PART I: OVERVIEW INFORMATION (page 5) and Section IV.B.3.

Submission Information (page 23). Revised text is highlighted in yellow in the document.

TABLE OF CONTENTS

PART I: OVERVIEW INFORMATION

PART II: FULL TEXT OF ANNOUNCEMENT

I. Funding Opportunity Description

A. Program Overview B. Program Metrics

II. Award Information A. General Award Information B. Fundamental Research

III. Eligibility Information A. Eligible Applicants B. Organizational Conflicts of Interest C. Cost Sharing/Matching

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

V. Application Review Information A. Evaluation Criteria B. Review of Proposals

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

VII. Agency Contacts VIII. Other Information

IX. APPENDIX 1: PROPOSAL SLIDE SUMMARY

X. APPENDIX 2: SECURITY CLASSIFICATION GUIDE AND CLASSIFIED

ADDENDUM REQUEST FORM

XI. APPENDIX 3: VOLUME 1 COVER SHEET TEMPLATE

XII. APPENDIX 4: VOLUME 2 COVER SHEET, CHECKLIST AND SAMPLE

TEMPLATES

XIII. APPENDIX 5: SECURITY ADDENDUM SAMPLE TEMPLATE

XIV. APPENDIX 6: SECURITY TEST / DEMONSTRATION / EXPERIMENTATION

PLANNING

XV. APPENDIX 7: PROGRAM PROTECTION PLAN SAMPLE OUTLINE

PART I: OVERVIEW INFORMATION

Federal Agency Name – Defense Advanced Research Projects Agency (DARPA), Strategic Technology Office (STO) Funding Opportunity Title – Moving Target Recognition (MTR) Announcement Type – Initial announcement Funding Opportunity Number – HR001120S0057 Catalog of Federal Domestic Assistance Numbers (CFDA) – Not applicable Dates o Posting Date: July 15, 2020 o Deadline to Request Classified Addendum: July 29, 2020 by 4:00 p.m. (EDT) o Questions Due Date and Time: August 5, 2020 by 4:00 p.m. (EDT) o Deadline to Notify Security of Intent to Submit Classified Proposal: September 1, 2020 by 4:00 p.m. (EDT) o Proposal Due Date and Time: September 17, 2020 by 4:00 p.m. (EDT)

DARPA is soliciting innovative research proposals to develop novel collection techniques and processing algorithms for detection, geolocation, imaging, and automatic target recognition of moving ground targets with synthetic aperture radar sensors. Please request the BAA Classified Addendum for additional information. This program, Moving Target Recognition (MTR), is a vital part of the Mosaic Warfare end-state vision.

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 can be reached at:

HR001120S0057@darpa.mil

DARPA/STO

ATTN: HR001120S0057

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

PART II: FULL TEXT OF ANNOUNCEMENT

I. Funding Opportunity Description

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

The Defense Advanced Research Projects Agency (DARPA) is soliciting innovative proposals in the following technical areas: synthetic aperture radar (SAR); SAR processing and algorithms;

and ground moving target detection, geolocation, imaging, and automatic target recognition (ATR). The program, Moving Target Recognition (MTR), is a vital part of the Mosaic Warfare end-state vision. 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.

The BAA Classified Addendum contains additional details. See APPENDIX 2 of this BAA for instructions on how to request the Classified Addendum as well as the Security Classification Guide (SCG) for the MTR program.

A. Program Overview

Under the MTR program, performers will develop algorithms and collection techniques to enable SAR sensors to detect, geolocate, and image moving ground targets. Emphasis is on military vehicle targets, including slow moving vehicles whose SAR signatures are superimposed on clutter. If the goals of moving target detection, geolocation, and imaging are successfully achieved, the MTR program will proceed to develop ATR algorithms for the moving target images.

MTR will include airborne data collect experiments to test and evaluate the algorithms.

Performers will be responsible for the airborne radar sensors and flight services. The Government team will be responsible for designing experiments involving moving ground vehicles, instrumented to provide ground truth.

The MTR program will be executed in two phases:

Phase 1, solicited by this BAA, will focus on SAR moving target detection, geolocation, and imaging. Phase 1 consists of a 24-month Base Period and a 6-month Option Period. Proposers to this BAA must submit proposals for the Phase 1 Base Period and Option Period. It is anticipated that awards to multiple performer teams will be made for Phase 1.

Phase 2, not solicited by this BAA, will focus on ATR for the moving target images. Prior to the end of the Phase 1 Base Period, proposal instructions for Phase 2 will be issued to the Phase 1 performers.

See the BAA Classified Addendum for additional information.

B. Program Metrics

See the BAA Classified Addendum.

II. Award Information

A. 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.4., “Representations and Certifications”). The Government reserves the right to remove proposers from award consideration should the parties fail to reach agreement on award terms, conditions, and/or cost/price within a reasonable time, and the proposer fails to timely provide requested additional information. Proposals identified for negotiation may result in a Procurement Contract or Other Transaction, depending upon the nature of the work proposed, the required degree of interaction between parties, whether or not the research is classified as Fundamental Research, and other factors.

Proposers looking for innovative, commercial-like contractual arrangements are encouraged to consider requesting Other Transactions. To understand the flexibility and options associated with Other Transactions, consult 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 follow-on production contract or OT to the participant, or a recognized successor in interest to the OT.

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

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

B. Fundamental Research

It is DoD policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 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 efforts are fundamental research and why the proposed efforts should be considered fundamental research.

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

III. Eligibility Information

A. Eligible Applicants

All responsible United States Enterprises capable of satisfying the Government’s needs may submit a proposal that shall be considered by DARPA. United States Enterprises to include:

Industrial/commercial concerns including small businesses Accredited degree granting colleges and universities Non-profit and not-for-profit organizations

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

a) 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.

b) 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.

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

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

(2) When proposing to perform classified work, applicants will ensure all industrial, personnel, and information systems processing security requirements are in place at the appropriate level (e.g., Facility Clearance Level (FCL), Automated Information Security (AIS), Certification and Accreditation (C&A), and any Foreign Ownership Control and Influence (FOCI) issues are mitigated prior to contract award. Additional information on these subjects can be found at http://www.dcsa.mil.

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

http://www.dcsa.mil/

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.

C. Cost Sharing/Matching

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

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

IV. Application and Submission Information

A. Address to Request Application Package

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

1. Classified Addendum

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

It is the proposer’s responsibility to ensure that they fully familiarize themselves with the MTR Security Classification Guide prior to reading the Classified Addendum and preparing proposals for submission.

Requests for the Classified Addendum should include, at a minimum, the company name, Technical 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.

Requests for the Classified Addendum should be received by July 29, 2020 at 4:00 p.m. (EDT).

Proposers should allow at least five (5) business days for processing requests for the Classified http://www.darpa.mil/work-with-us/contract-management#OtherTransactions http://www.darpa.mil/

Addendum plus time for delivery. Requests will be handled on a first in, first out basis.

Incomplete or inaccurate forms will be returned to sender along with a notification of what needs to be corrected and the new request will be processed based on the date of when the revised request form is received.

B. Content and Form of Application Submission

All submissions 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.

1. Proposals Format

All proposals must be in the format shown below. 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. Proposals shall consist of two volumes:

1) Volume I, Technical and Management Proposal, and 2) Volume II, Cost Proposal.

Maximum page lengths for each section are shown in brackets {} below. The page limitation includes all figures, tables, and charts. Page size for all pages shall be 8-1/2 by 11 inches.

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 {No more than 2 pages}

(a) Cover Sheet to Include

(1) BAA number (HR001120S0057);

(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) Other team members (if applicable) and type of organization for each;

(5) Proposer’s reference number (if any);

(6) Proposal title;

(7) Technical point of contact to include: salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), email (if available);

(8) Administrative point of contact to include: salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), email (if available);

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

(10) Date proposal was submitted.

(b) Official transmittal letter

Section II: Summary Slides {No more than 3 slides} A three-slide summary of the proposal that quickly and succinctly indicates the concept overview, key innovations, expected impact, and other unique aspects of the proposal. The format for the summary slides is included as APPENDIX 1 to this BAA.

Section III: Technical Proposal {No more than 30 pages} This section provides the detailed discussion of the proposed work necessary to enable an in-depth review of the specific technical issues. Specific attention must be given to addressing both risk and payoff of the proposed work that make it desirable to DARPA.

A. Technical approach and innovative claims for the proposed research. This section is the centerpiece of the proposal and should succinctly describe the uniqueness and benefits of the proposed approach relative to the current state-of-art alternate approaches.

B. Technical rationale in support of innovative claims. Proposals should clearly explain the technical approach(es) that will be employed to meet or exceed each program metric and provide ample justification as to why the approach(es) is/are feasible.

C. Risk assessment and mitigation plan.

D. Technical development approach and plan. This should include a clear and logical progression proposed to achieve the innovations claimed and retire risks.

E. Description of the results, products, transferable technology, and expected technology transfer path. This should also address mitigation of life-cycle and sustainment risks associated with transitioning intellectual property for U.S. military applications, if applicable. See also Section IV.B.2.h of this BAA, “Intellectual Property.”

F. Discussion of proposer’s previous accomplishments and work in closely related research areas. Clearly identify results, technology, or concepts from other research that will be utilized in the proposed effort.

Section IV: Management Proposal {No more than 16 pages} This section provides the detailed discussion of the proposed work necessary to enable an in-depth review of the specific managerial issues.

A. Program schedule and measurable milestones for the proposed research, including estimates of cost for each task in each year of the effort delineated by the proposed awardee and major subawardees. NOTE: Measurable milestones should capture key development points in tasks and should be clearly articulated and defined in time relative to start of effort. These milestones should enable and support a decision for the next part of the effort. Additional interim non-critical management milestones are also highly encouraged at regular intervals. If the proposed effort consists of multiple portions that could reasonably be partitioned for purposes of funding, these should be identified as Options with separate cost estimates for each. The milestones must not include proprietary information.

B. Deliverables associated with the proposed research and the plans and capability to accomplish technology transition. Include in this section all proprietary claims to the results, prototypes, intellectual property, or systems supporting and/or necessary for the use of the research, results, and/or prototype. If there are no proprietary claims, this should be stated. For forms to be completed regarding intellectual property, see Section IV.B.2.h of this BAA. There is no page limit for the listed forms.

C. Clearly defined organization chart for the program team, to include (as applicable): (1) the programmatic relationship of team member; (2) the unique capabilities of team members; (3) the task of responsibilities of team members; (4) the teaming strategy among the team members; and (5) the key personnel along with the amount of effort to be expended by each person during each year.

D. Description of Security Management architecture and/or approach for the proposed effort. Detail unique additional security requirements regarding OPSEC, program protection planning, test planning, transportation plans, work being performed at different classification levels, and/or utilizing test equipment not approved at appropriate classification level.

E. Description of the facilities that would be used for the proposed effort. This section should address how safeguarding of materials will be handled at each facility to include classified materials when applicable.

F. Any agreements, including formal teaming agreements, Government Furnished Equipment (GFE), Government Furnished Information (GFI) and/or Government Furnished Facilities (GFF) that are required to execute this program. For any requested GFE/GFI/GFF item, the proposer shall provide an item description, supporting justification, owner/source, estimated cost (lease, refurbishment or transportation expense), and an item need date.

Section V: Statement of Work (SOW) {No page limit} Clearly delineate the Base Period and Option Period, and for each define the technical tasks/subtasks to be performed, their durations, and dependencies among them. For each task/subtask, provide:

General description of the objective (for each defined task/activity);

Detailed description of the approach to be taken to accomplish each defined task/activity;

Identification of the primary organization responsible for task execution (prime, sub, team member, by name, etc.);

Completion criteria for each task/activity - a product, event, or milestone that defines its completion;

Define all deliverables (reporting, data, reports, software, etc.) to be provided to the

Government in support of the proposed research tasks/activities; and Clearly identify any tasks/subtasks (to be performed by either an awardee or subawardee) that will be accomplished on-campus at a university, if applicable.

Do not include any proprietary information in the SOW.

Section VI: Security Plan {No page limit} Due to the protected nature of this program and the degree of security required to protect Critical Program Information (CPI), the proposer will describe their security approach to protect the technical objectives and articulate internal security practices for protecting contracting activities.

The format for the Program Protection Strategy is included as APPENDIX 5 to this BAA and does not count against the page limit.

Section VII: Additional Information {No more than 12 pages} A brief bibliography of relevant technical papers and research notes (published and unpublished) that document the technical ideas upon which the proposal is based. These papers or research notes will not be formally reviewed against the evaluation criteria, but should allow technical understanding of the claims made. Copies of not more than three (3) relevant papers can be included in the submission.

b) Volume II, Cost Proposal {No page limit}

The Cost Proposal must be unclassified.

All proposers, including FFRDCs, must submit the following:

(1) Cover sheet to include:

(1) BAA number (HR001120S0057);

(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) Other team members (if applicable) and type of organization for each;

(5) Proposer’s reference number (if any);

(6) Proposal title;

(7) Technical point of contact to include: salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), email (if available);

(8) Administrative point of contact to include: salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), and email (if available);

(9) Award instrument requested: cost-plus-fixed-fee (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 and option(s) (if any);

(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) DUNS number;

(16) TIN number;

(17) CAGE Code;

(18) Subawardee Information; and

(19) Proposal validity period.

(2) Additional Cost Proposal Information

(a) Supporting Cost and Pricing Data

The proposer should include supporting cost and pricing information in sufficient detail to substantiate the summary cost estimates and should include a description of the method used to estimate costs and supporting documentation.

(b) Cost Breakdown Information and Format

Detailed cost breakdown to include:

Total program costs broken down by major cost items (direct labor, including labor categories; subcontracts; materials; other direct costs; overhead charges, etc.) and further broken down by task and phase;

Major program tasks by fiscal year;

An itemization of major subcontracts and equipment purchases;

Documentation supporting the reasonableness of the proposed equipment costs

(vendor quotes, past purchase orders/purchase history, detailed engineering estimates, etc.) shall be provided;

An itemization of any information technology (IT) purchase, as defined by FAR

2.101 – Documentation supporting the reasonableness of the proposed equipment costs (vendor quotes, past purchase orders/purchase history, detailed engineering estimates, etc.) shall be provided, including a letter stating why the proposer cannot provide the requested resources from its own funding for prime and all sub-awardees;

Summary of projected funding requirements by month;

Source, nature, and amount of any industry cost-sharing; and Identification of pricing assumptions which may require incorporation into the resulting award instrument (e.g., use of Government Furnished Property/Facilities/Information, access to Government Subject Matter experts, etc.).

The cost proposal must include a cost detail spreadsheet from the prime proposer and each proposed subcontractor using the attached template, in an editable format with calculation formulas intact. Please follow the instructions on the template, ensuring that the Base and Option 1 tabs are utilized for the costs of the two respective periods.

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. Certified cost or pricing data are not required if the proposer proposes an award instrument other than a Procurement Contract (e.g., Other Transaction).

(c) Subawardee Proposals

The awardee is responsible for compiling and providing all subawardee proposals for the Procuring Contracting Officer (PCO)/Agreement 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 awardee should be submitted in a sealed envelope that the proposed awardee will not be allowed to view. The subawardee must provide the same number of copies to the PCO/AO as is required of the awardee. See Section IV.B.3.a. of this BAA for proposal submission information.

(d) Other Transaction Requests

All proposers requesting an OT must include a detailed list of milestones. 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.

2. Additional Proposal Information

a) 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.”

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.

b) Security Information

(1) Program Security Information

(a) Program Security

Proposers should include with their proposal any proposed solution(s) to program security requirements unique to this program. Common program security requirements include but are not limited to: operational security (OPSEC) contracting/sub-contracting plans; foreign participation or materials utilization plans; program protection plans (which may entail the following) manufacturing and integration plans; range utilization and support plans (air, sea, land, space, and cyber); data dissemination plans; asset transportation plans; classified test activity plans; disaster recovery plans; classified material / asset disposition plans and public affairs / communications plans.

(2) Classified Submissions

(a) Classified Proposal Markings

At this time, DARPA anticipates that proposals submitted in response to this BAA may generate or involve access to classified information.

Submitting a proposal without requesting the Security Classification Guide may lead to a security incident.

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____________________________(insert the recommended classification level, e.g., Top Secret, Secret, or Confidential)”

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 cognizant security agency approved facilities, information systems, and appropriately cleared/eligible personnel at the classification level of the proposal. 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.dcsa.mil.

http://www.dcsa.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 a proposal includes a classified portion, and when able according to security guidelines, we ask that proposers send an email no later than September 1, 2020, to HR001120S0057@darpa.mil and Kyle.Smith.ctr@darpa.mil as notification that there is a classified portion to the proposal.

Confidential, Secret, and Top Secret Information Use transmission, classification, handling, and marking guidance provided by previously issued SCGs, 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.

Confidential and Secret Confidential and 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). At least five (5) business days prior to traveling, and in accordance with the advance notification required as outlined in Part I of this BAA, the courier shall contact the DARPA CDR at 703-526-4052 to coordinate arrival and delivery. The courier shall also contact the DARPA Program Security Representative (PSR), Mr. Kyle C. Smith, at 571-218-4802, Kyle.Smith.ctr@darpa.mil.

OR

Mailed via U.S. Postal Service (USPS) Registered Mail or USPS Express Mail or shipped via commercial carrier approved by DARPA Security. To ship via commercial carrier, proposers must obtain preapproval by contacting the DARPA PSR. 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. Senders should mail to the mailing address listed in the contact information herein. Prior to mailing, and in accordance with the advanced notification required as outlined in Part I of this BAA, proposers shall contact the DARPA PSR, Mr. Kyle C. Smith, at 571-218-4802, Kyle.Smith.ctr@darpa.mil.

The inner envelope shall be addressed to Defense Advanced Research Projects Agency, ATTN:

Strategic Technology Office and Dr. Adam Bryant, with a reference to the BAA number

(HR001120S0057).

mailto:HR001120S0057@darpa.mil mailto:Kyle.Smith.ctr@darpa.mil mailto:Kyle.Smith.ctr@darpa.mil

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.

Top Secret Information Top Secret information must 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 and the DARPA PSR, Mr. Kyle C. Smith, at 571-218-4802, Kyle.Smith.ctr@darpa.mil, to coordinate arrival and delivery. Pre-coordination must be completed at least five (5) business day prior to traveling.

Sensitive Compartmented Information (SCI) SCI must be marked, managed, and transmitted in accordance with DoDM 5105.21 Volumes 1 -

3. Questions regarding the transmission of SCI may be sent to the DARPA Technical Office Program Security Officer (PSO) via the BAA mailbox or by contacting the DARPA PSR, Mr.

Kyle C. Smith, at 571-218-4802, Kyle.Smith.ctr@darpa.mil. Pre-coordination with the DARPA PSR must be provided no later than September 1, 2020, when submitting classified information at the SCI level.

Successful proposers may be sponsored by DARPA for access to SCI. Sponsorship must be aligned to an existing DD Form 254 where SCI has been authorized. Questions regarding SCI sponsorship should be directed to the DARPA Personnel Security Office at 703-526-4543.

Special Access Program (SAP) Information SAP information must be marked in accordance with DoDM 5205.07 Volume 4, and transmitted by specifically approved methods that will be provided by STO PSO or their staff.

Proposers choosing to submit SAP information required to provide the DARPA Technical Office PSO written permission from the source material’s cognizant Special Access Program Control Officer (SAPCO) or designated representative via approved channels by September 1, 2020. For clarification regarding this process, contact the DARPA STO PSO, Mr. Jason Potter, at 703-526- 2687 or Jason.Potter@darpa.mil, or the DARPA PSR, Mr. Kyle C. Smith, at 571-218-4802, Kyle.Smith.ctr@darpa.mil.

c) 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” mailto:Kyle.Smith.ctr@darpa.mil mailto:Kyle.Smith.ctr@darpa.mil mailto:Jason.Potter@darpa.mil

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.

d) 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.

e) Approved Cost Accounting System Documentation

Proposers that do not have a Cost Accounting Standards (CAS) complaint 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. 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.

f) 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.

g) 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.

h) 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.

http://www.darpa.mil/work-with-us/additional-baa#NPRPAC https://doi.org/10.6028/NIST.SP.800-171r1 http://www.darpa.mil/work-with-us/additional-baa http://www.darpa.mil/work-with-us/additional-baa http://www.dcaa.mil/ http://www.gsa.gov/portal/forms/download/115778

(1) For Procurement Contracts

Proposers responding to this BAA requesting Procurement Contracts will need to complete the certifications at DFARS 252.227-7017. See http://www.darpa.mil/work-with-us/additional-baa for further information. If no restrictions are intended, the proposer should state “NONE.” The table below captures the requested information:

Technical Data Computer

Software To be Furnished With

Restrictions

Summary of Intended Use in the Conduct of the Research

Basis for Assertion

Asserted Rights Category

Name of Person Asserting

Restrictions

(LIST) (NARRATIVE) (LIST) (LIST) (LIST)

(2) For All Non-Procurement Contracts

Proposers responding to this BAA requesting an Other Transaction for Prototypes shall follow the applicable rules and regulations governing these various award instruments, but, in all cases, should appropriately identify any potential restrictions on the Government’s use of any Intellectual Property contemplated under the award instrument in question. This includes both Noncommercial Items and Commercial Items. Proposers are encouraged use a format similar to that described in Paragraph (1) above. If no restrictions are intended, then the proposer should state “NONE.”

i) System for Award Management (SAM) and Universal Identifier Requirements

All proposers must be registered in SAM unless exempt per FAR 4.1102. FAR 52.204-7, “System for Award Management” and FAR 52.204-13, “System for Award Management Maintenance” are incorporated into this BAA. See http://www.darpa.mil/work-with-us/additional-baa for further information.

International entities can register in SAM by following the instructions in this link:

https://www.fsd.gov/fsd-gov/answer.do?sysparm_kbid=dbf8053adb119344d71272131f961946&sysparm_search=KB001 3221.

3. Submission Information

DARPA will acknowledge receipt of all submissions and assign an identifying control number that should be used in all further correspondence regarding the submission. DARPA intends to use email correspondence regarding HR001120S0057. Submissions may not be submitted by fax or email; any so sent will be disregarded.

Submissions will not be returned. An electronic copy of each submission received will be retained at DARPA and all other non-required copies destroyed. A certification of destruction http://www.darpa.mil/work-with-us/additional-baa http://www.darpa.mil/work-with-us/additional-baa http://www.darpa.mil/work-with-us/additional-baa https://www.fsd.gov/fsd-gov/answer.do?sysparm_kbid=dbf8053adb119344d71272131f961946&sysparm_search=KB0013221 https://www.fsd.gov/fsd-gov/answer.do?sysparm_kbid=dbf8053adb119344d71272131f961946&sysparm_search=KB0013221 https://www.fsd.gov/fsd-gov/answer.do?sysparm_kbid=dbf8053adb119344d71272131f961946&sysparm_search=KB0013221 may be requested, provided the formal request is received by DARPA within five (5) days after notification that a proposal was not selected.

The proposal must be received at DARPA/STO, 675 North Randolph Street, Arlington, VA 22203-2114 (Attn.: HR001120S0057) on or before, September 17, 2020, by 4:00 p.m. (EDT), in order to be considered during the initial round of selections; however, proposals received after this deadline may be received and evaluated up to six months (180 days) from date of posting on www.beta.SAM.gov (formerly FedBizOpps). Proposals submitted after the due date specified in the BAA or due date otherwise specified by DARPA may be selected. Proposers are warned that the likelihood of available funding is greatly reduced for proposals submitted after the initial closing date deadline.

a) Proposal Submission

Classified submissions should NOT be submitted through DARPA’s BAA Website (https://baa.darpa.mil), though proposers will likely still need to visit https://baa.darpa.mil to register…