HR001119S0045.pdf

Broad Agency Announcement

The Military Tactical Means (MTM)

STRATEGIC TECHNOLOGY OFFICE

HR001119S0045

September 17, 2019

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

PART I: OVERVIEW INFORMATION

Federal Agency Name – Defense Advanced Research Projects Agency (DARPA), Strategic Technology Office (STO) Funding Opportunity Title – Military Tactical Means (MTM) Announcement Type – Initial announcement Funding Opportunity Number – HR001119S0045 Catalog of Federal Domestic Assistance Numbers (CFDA) – Not applicable Dates Posting Date: September 17, 2019 Request for Classified Addendum: Requests may be made immediately after BAA posting and must be made prior to September 27, 2019 Proposers Day: October 7, 2019 Questions Due Date and Time: October 10, 2019, 4:00 p.m. (EDT) Proposal Due Date and Time: November 7, 2019, 4:00 p.m. (EST)

DARPA is soliciting innovative research proposals to design advanced sensing and automated processing of remotely sensed data for the purposes of detection, classification and geolocation of adversary military equipment on the battlefield. This program, called Military Tactical Means (MTM), 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.

Any cost sharing requirements: None Agency contact:

o The BAA Coordinator for this effort can be reached by electronic mail:

HR001119S0045@darpa.mil DARPA/Strategic Technology Office

ATTN: HR001119S0045

675 North Randolph Street Arlington, VA 22203-2114 703-526-6630 tel:+17035266630

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 areas of multi-mode electro-optics (EO), sensors, and exploitation techniques capable of performing wide-area searches to detect high-value targets in order to task engagement systems to close effects-chains. 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.

A. Program Overview The Military Tactical Means (MTM) program will develop sensors and exploitation techniques capable of performing wide-area searches to detect high-value targets in order to task engagement systems to close effects-chains.

MTM will consist of two 24-month phases. Phase 1, solicited by this BAA, consists of two Technical Areas (TAs) to be completed in parallel in 24-months. Phase 2, not included in this solicitation, consists of one TA. Proposers should submit proposals for Phase 1, broken into a 14-month base period and a 10-month option. The base period culminates with a Critical Design Review (CDR), the results of which will inform how the Government will make option exercise determinations. The 10-month option includes revisions to technology resulting from the CDR in anticipation of Phase 2.

Proposers are required to bid to both TAs for Phase 1. Proposers shall include a Rough Order of Magnitude (ROM) cost estimate for Phase 2 as well as a list of assumptions used to inform the basis for the cost estimate. This submission will be used for planning purposes only and will not be evaluated. Prior to the end of Phase 1, detailed proposal instructions for Phase 2 will be issued to the Phase 1 performers for which the Government had exercised the option period.

See MTM Classified Addendum for additional information.

B. PROGRAM METRICS

See MTM Classified Addendum for additional information.

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 6.2.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, grant, cooperative agreement 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.

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.

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

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.

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 http://www.darpa.mil/work-with-us/additional-baa 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.dss.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 http://www.dss.mil/

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.

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, and any references to external websites herein constitute the total solicitation. If proposers cannot access the referenced material posted in the announcement found at http://www.darpa.mil, contact the administrative contact listed herein.

2. Classified Addendum A formal request for the HR001119S0045 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 to this BAA) and emailing the Request Form to HR001119S0045@darpa.mil with subject line titled “Request HR001119S0045 Security Classification Guide and Classified Addendum.”

It is the proposer’s responsibility to ensure that they fully familiarize themselves with the MTM Security Classification Guide prior to reading the Classified Addendum and preparing full 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 http://www.darpa.mil/work-with-us/contract-management#OtherTransactions http://www.darpa.mil/work-with-us/contract-management#OtherTransactions http://www.darpa.mil/ mailto:HR001119S0045@darpa.mil clearance and the clearance of the recipient before e-mailing (via secure system) and/or mailing the classified material.

Requests for the Classified Addendums must be received by September 27, 2019 at 4:00 p.m.

(EDT). Proposers should allow at least five (5) business days for processing requests for the Classified Addendums 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 fonts may be used for figures, tables, and charts. Copies of all submitted documents submitted must be clearly labeled with the DARPA BAA number, proposer organization, and proposal title/proposal short title.

3. Proposals Format All proposals must be in the format given below. Nonconforming proposals may be rejected without review. Proposals shall consist of two volumes. All pages shall be printed on 8-1/2 by 11-inch paper with type not smaller than 12-point. Smaller font may be used for figures, tables, and charts. The page limitation for proposals includes all figures, tables, and charts. 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. 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 may be included with the submission.

The submission of other supporting materials, along with the proposals, is strongly discouraged and will not be considered for review. Maximum page lengths for each section are shown in brackets {} below. All proposals must be written in English.

a) Volume I, Technical and Management Proposal Section I: Administrative {No more than 2 pages}

A. Cover Sheet to Include

1. BAA number (HR001119S0045)

2. Technical area;

3. Lead Organization Submitting proposal;

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

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

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

NONPROFIT”;

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

6. Other team members (if applicable) and type of organization for each;

7. Proposal title;

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

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

10. Date proposal was submitted;

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

B. Official transmittal letter Section II: Summary Slides {No more than 3 slides} A three-slide summary of the proposal, in PowerPoint, 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 and does not count against the page limit.

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 (See classified addendum for additional information).

A. 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-the-art and alternative approaches.

B. Technical rationale in support of innovative claims and overall feasibility of the proposed concept.

C. Risks 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 4.2.3.10 “Intellectual Property.”

F. General discussion of other research in this area and other areas that may be applicable.

Clearly identify results, technology, or concepts from other research that will be utilized in the proposed effort.

G. Classified Addendum Response.

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 delineated by the prime and major subcontractors. Note: Measurable milestones should capture key development points in tasks and should be clearly articulated and defined relative to months after contract award. 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 milestones for each. Additionally, 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.

The milestones must not include proprietary information.

B. Deliverables associated with the proposed research and the plans and capability to accomplish technology transition and commercialization. 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 not proprietary claims, this should be stated.

C. A clearly defined organization chart for the program team which includes, 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. Discussion of proposer’s previous accomplishments and work in closely related research areas.

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

G. Approximate task costs for each major task in each phase of the effort delineated by the proposed awardee and major subawardees, total cost, and any company cost share.

H. To manage cost, Proposers describe an earned value management system (EVMS) which will be appropriate for an R&D program, such as MTM.

Section V: Statement of Work (SOW) {10} Clearly define the technical tasks/subtasks to be performed, their durations, and dependencies among them. Clearly delineate the tasks associated with the base period which culminate with the CDR and the 10-month option period. In the event tasking requires specific, classified descriptions, classified information will be provided in a classified appendix (see Section 4.2).

Phase option SOWs should standalone and be at the same level of detail as the Phase 1 SOW.

Note: An unclassified version of the SOW should be provided with the unclassified cost proposal.

For each task/subtask, provide:

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

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

A detailed description of the tasks associated with the base period, which culminate with the CDR, and the option period;

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

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

A detailed description of the management approach for integrating concepts, results, and findings from members across the team, including anticipated coordination meetings and shared access to data and equipment.

Define all deliverables (reporting, data, reports, software, etc.) to be provided to the Government in support of the proposed research tasks/activities.

Identification of any dependencies between major tasks, by task number, within a Phase.

Approximate cost of each major task.

Do not include any proprietary information in the SOW.

Section VI: Additional Information {No more than 12 pages} A brief bibliography of relevant technical papers and research notes (published and unpublished) which 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 no more than three (3) relevant papers can be included in the submission.

b) Volume II, Cost Proposal {No Page Limit}

Rough Order of Magnitude (ROM) Cost Estimate Proposers shall include a ROM cost estimate for Phase 2 as well as a list of assumptions used to inform the basis for the cost estimate. This submission will be used for planning purposes only and will not be evaluated. Cost volumes submitted should be unclassified.

Use of the MS Excel™ spreadsheet is highly encouraged. A template for this will not be provided.

Please include as ‘Attachment 1” to the Proposal.

All proposers, including FFRDCs, and Subawardees must submit the following:

Cover sheet to include:

(1) BAA number (HR001119S0045)

(2) Technical area;

(3) Lead Organization Submitting proposal;

(4) Type of organization, selected among the following categories: “LARGE

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

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

NONPROFIT”;

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

(6) Other team members (if applicable) and type of organization for each;

(7) Proposal title;

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

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

(10) 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;

(11) Place(s) and period(s) of performance;

(12) Total proposed cost separated by basic award and option(s) (if any);

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

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

(14) Name, address, and telephone number of the proposer’s cognizant Defense Contract Audit Agency (DCAA) audit office (if known);

(15) Date proposal was prepared;

(16) DUNS number;

(17) TIN number;

(18) CAGE Code;

(19) Subawardee Information;

(20) Proposal validity period.

The Government requires that tables included in the cost proposal also be provided in an editable (e.g., MS Excel™) format with calculation formulas intact to allow traceability of the cost proposal numbers across the prime and subawardees (Note: Subawardees are also required to submit fully-disclosed cost information with the same level of detail as required by the prime.

This cost information shall be submitted in an editable (e.g., MS Excel™) format with calculation formulas intact.) This includes the calculations and adjustments that are utilized to generate the Summary Costs from the source labor hours, labor costs, material costs, etc. input data. The Government prefers receiving cost data as MS Excel™ files; however, this is not a requirement. If the PDF submission differs from the Excel submission, the PDF will take precedence. Each copy must be clearly labeled with the DARPA BAA number, proposer organization, and proposal title (short title recommended).

The Government also strongly encourages that the proposer provide a detailed cost-breakdown to include:

(1) total program cost, delineated by base period and option period, broken down by major cost items to include:

i. Direct labor, including individual labor categories, or persons, with associated labor hours and numbered direct labor rates

ii. If consultants are to used, proposer must provide consultant agreement or other document which verifies the proposed loaded daily/hourly rate

iii. Indirect costs including Fringe Benefits, Overhead, General and Administrative

Expense, Cost of Money, etc. (Must show base amount and rate)

iv. Travel – Number of trips, number of days per trip, departure and arrival destinations, number of people, etc.

v. Other Direct Costs – Should be itemized with costs or estimated costs. Backup documentation will be submitted to support proposed costs. 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.

(2) major program tasks by fiscal year

(3) an itemization of major subcontracts and equipment purchases, to include: a cost proposal as detailed as the Proposer’s cost proposal

(4) an itemization of any information technology (IT) purchase, as defined in FAR Part 2.101

(5) a summary of projected funding requirements by month

(6) 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

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

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. Tables included in the cost proposal in editable (e.g. MS Excel) format with calculation formulas intact. NOTE: If PDF submissions differ from the Excel submission, the PDF will take precedence.

The proposer shall identify required Government-furnished facilities, data, manpower, additional facility improvements over existing facility capabilities, and equipment to support the proposer’s development and demonstration approach. This list should include rationale, itemized Rough Order of Magnitude (ROM) costs and dates needed. The costs of Government furnished equipment, facilities and information (GFE/GFF/GFI) count against the full budget the Government has available for the program. GFE/GFF/GFI may include facilities and support equipment for subsystem and system testing, data collection assets, acoustic transmitters and receivers, support hardware, range facilities, and data collection assets.

Per FAR 15.403-4, certified cost or pricing data shall be required 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., other transaction).

Subawardee Proposals The awardee is responsible for compiling and providing all subawardee proposals for the Procuring Contracting Officer (PCO). Subawardee proposals should include Interdivisional Work Transfer Agreements (ITWA) or similar arrangements. 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. NOTE: for IT and equipment purchases, include a letter stating why the proposer cannot provide the requested resources from its own funding.

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 hard copies and/or electronic proposals as is required of the awardee.

Other Transaction Requests All proposers requesting an Other Transaction for Prototypes (OT) agreement 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, contractor 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, fixed price or expenditure based, will be subject to negotiation by the Agreements Officer. Do not include proprietary data.

NOTE: PROPOSERS ARE CAUTIONED THAT PROPOSALS MAY BE REJECTED IF

SUBMITTAL INSTRUCTIONS ARE NOT FOLLOWED.

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

d) Security Information IV.B.1.d.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.

IV.B.1.d.2 Classified Submissions

(a) Classified Proposal Markings At this time, DARPA anticipates that full proposals submitted in response to this BAA may generate or involve access to classified information. Classified submissions shall be transmitted and marked in accordance with the following guidance.

A formal request for the HR001119S0045, Security Classification Guide, may be submitted by filling out the Security Classification Guide Request Form (found in APPENDIX 2 to this BAA) and emailing the Request Form to HR001119S0045@darpa.mil with subject line titled "Request HR001119S0045 Security Classification Guide." Security classification guidance via a Security Classification Guide and a DD Form 254, "DoD Contract Security Classification Specification," will be provided.

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, 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 should 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 a proposal includes a classified portion, and when able, according to security guidelines, we ask that proposers send an e-mail no later than October 22, 2019 to HR001119S0045@darpa.mil as notification that there is a classified portion to the proposal. When submitting a hard copy of the classified portion according to the instructions outlined below, proposers should submit three (3) hard copies of the classified portion of their proposal and two (2) CD-ROMs containing the classified portion of the proposal as a single, searchable Adobe PDF file.

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. At least 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 Classified Document Registry at 703-526-4052 to coordinate arrival and delivery. The courier shall also contact the DARPA Program Security Representative (PSR), Linda Barnes, at 571-218-4655, Linda.Barnes.ctr@darpa.mil

OR

Mailed via U.S. Postal Service (USPS) Registered Mail or USPS Express Mail. All classified information will be enclosed in opaque inner and outer covers and double-http://www.dss.mil/ mailto:Linda.Barnes.ctr@darpa.mil 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 advance notification required as outlined in Part I of this BAA, proposers shall contact the DARPA PSR, Linda Barnes, at 571-218-4655, Linda.Barnes.ctr@darpa.mil

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

Strategic Technology Office – Linda Barnes, with a reference to the BAA number

(HR001119S0045).

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: DARPA Classified Document Registry.

Top Secret Information Top Secret information must be hand-carried by an appropriately cleared and authorized courier to the DARPA Classified Document Registry. Prior to traveling, the courier shall contact the DARPA Classified Document Registry at 703-526-4052 to coordinate arrival and delivery. The courier shall also contact the DARPA PSR, Linda Barnes, at 571-218-4655, Linda.Barnes.ctr@darpa.mil.

Sensitive Compartmented Information (SCI) Proposers choosing to submit SCI information from SCI sources must ensure (1) they have permission from an authorized individual at the cognizant Government agency (e.g., Contracting Officer, Program Manager); (2) the proposal 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, Linda Barnes, at 571-218-4655, Linda.Barnes.ctr@darpa.mil.

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 which will be provided by the Technical Office PSO or their staff.

Proposers choosing to submit SAP information from an agency other than DARPA are 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. For clarification regarding this process, contact the DARPA Technical Office PSO via the BAA mailbox or by contacting the DARPA PSR, Linda Barnes, at 571-218-4655, Linda.Barnes.ctr@darpa.mil.

Additional SAP security requirements regarding facility accreditations, information security, personnel security, physical security, operations security, test security, classified transportation plans, and program protection planning may be specified in the DD Form 254.

NOTE: All proposals containing Special Access Program (SAP) information must be processed on a SAP information technology (SAP IT) system that has received an Approval-to-Operate mailto:Linda.Barnes.ctr@darpa.mil

(ATO) from the DARPA Technology Office PSO, or other applicable DARPA SAP IT Authorizing Official. The SAP IT system ATO will be based upon the Risk Management Framework (RMF) process outlined in the Joint Special Access Program Implementation Guide (JSIG), current version, (or successor document). (Note: A SAP IT system is any SAP IT system that requires an ATO. It can range from a single laptop/tablet up to a local and wide area networks.)

The Department of Defense mandates the use of a component’s SAP enterprise system unless a compelling reason exists to use a non-enterprise system. The DARPA Chief Information Officer (CIO) must approve any performer proposal to acquire, build, and operate a non-enterprise SAP IT system during the awarded period of performance. Use of the DARPA SAP enterprise system, SAVANNAH, does not require CIO approval.

SAP IT disposition procedures must be approved by the DARPA Senior Authorizing Official, or SAPCO, IAW the OSD SAPCO Memorandum, “Disposition of DoD Special Access Program Information Technology Devices”, July 27, 2017.

(c) Both Classified and Unclassified Submissions

For a proposal that includes both classified and unclassified information, the proposal may be separated into an unclassified portion and a classified portion. The proposal should include as much information as possible in the unclassified portion and use the classified portion ONLY for classified information. The unclassified portion can be submitted through the DARPA BAA Website, per the instructions in Section IV.4.b., below. The classified portion must be provided separately, according to the instructions outlined in the ‘Classified Submission Requirements and Procedures’ section above.

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

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

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.

f) Human Subjects Research (HSR)/Animal Use Proposers that anticipate involving human subjects or animals in the proposed research…