HDTRA120S0001_BAA.pdf

DEFENSE THREAT REDUCTION AGENCY

BROAD AGENCY ANNOUNCEMENT

HDTRA1-20-S-0001

CHEMICAL / BIOLOGICAL

TECHNOLOGIES

February 3, 2020

Table of Contents

1.0 INTRODUCTION

2.0 BAA PARTICULARS

3.0 BAA ELIGIBILITY

4.0 PROPOSAL SUBMISSION INFORMATION

5.0 PROPOSAL EVALUATION INFORMATION

6.0 SELECTION DECISION INFORMATION

7.0 POST-SELECTION ACTIVITIES

8.0 BAA CONTACT INFORMATION

9.0 LIST OF ATTACHMENTS

1.0 Introduction

1.1 Overview

The Defense Threat Reduction Agency (DTRA) is issuing this Broad Agency Announcement (BAA) to seek participants for research and development projects in support of the Research & Development Directorate, Chemical / Biological Technologies (RD-CB) Department. This BAA constitutes a public notice for competitive opportunities as described in Federal Acquisition Regulation (FAR) Part 35.016 and FAR 6.102(d)(2).

1.2 BAA Purpose and Scope

The purpose of this BAA is to serve as a one-year (12-month) open continuous vehicle through which topics will be released as they become available during the BAA open period. This BAA will remain open for one year from the date of release. This BAA, and any future topics released, may be accessed via Contract Opportunities (https://beta.sam.gov/). Proposers are encouraged to monitor Contract Opportunities.

The scope of this BAA is limited to projects that meet Technology Readiness Level (TRL) definitions in the TRL range of 3-6 (see ATTACHMENT 1 for TRL definitions). Upon completion of the proposed development efforts, solutions should strive to meet a TRL in the range of 4-6.

Proposals that address technologies at TRL 4 or greater should also be aware of the Manufacturing Readiness Level (MRL) considerations.

1.3 Technical Domains

The DTRA RD-CB mission was established by the Department of Defense (DoD) to provide state-of-the-art defense capabilities to allow military forces of the United States to operate and to successfully complete their missions in chemical and biological warfare environments. The scope of mission efforts and the priorities assigned to specific projects are influenced by changes in military and civilian Chemical and Biological Defense (CBD) science and technology, advanced developments, operational requirements, military threat assessments, and national defense strategies. To keep pace with defense capability requirements, the CBD Program (CBDP), as part of its mission, routinely promulgates chemical and biological research. The comprehensive research program encompasses both intramural and extramural sources, and the role of each is vital to the fulfillment of the CBDP objectives.

https://beta.sam.gov/

DTRA is seeking optimum approaches to meet technology objectives within the areas listed below, with a goal to identify and select science and technology projects that can be transitioned to joint acquisition programs:

Detection – Chemical and Biological: The goal of the Detection area is to provide real-time capability to detect, identify, characterize, locate and warn against all known or validated CB warfare agents in addition to other chemical or biological threat materials (e.g., Toxic Industrial Chemicals).

Digital Battlespace Management: The Digital Battlespace Management area seeks to provide information superiority with respect to the Chemical, Biological, Radiological, and Nuclear (CBRN) environment. This is achieved by delivering cutting edge Integrated Early Warning, Information Management and Applied Analytic capabilities to the warfighter for rapid situational awareness, course of action (CoA) analysis and decision support.

Protection – Individual and Collective: The Protection capability area seeks to provide unencumbered full-dimensional protection to the warfighter for both personal protective gear (individual protection) and protection of large scale fixed or mobile environments (collective protection).

Hazard Mitigation: The goal of the Hazard Mitigation capability area is to develop technologies that can rapidly restore pre-contamination capabilities with a minimum of logistical impact.

Threat Agent Science: The Threat Agent Science capability area seeks to maintain and develop scientific knowledge of current, non-traditional, and emerging threats in addition to studying areas such as low level toxicity, agent fate, and improved simulant materials.

Medical Pretreatments: The goal of the Pretreatments capability area is to conduct research in order to develop lead candidate vaccines and chemical pretreatments and protectants that can be administered before exposure to provide both specific and broad-spectrum protection against validated chemical or biological agents.

Categories of threat agents addressed in this capability area include nerve agents, viruses, bacteria and toxins.

Medical Diagnostics: Medical Diagnostics involves the diagnosis of infection by or exposure to bacterial, viral, or toxin agents (biological diagnostics) or of exposure to nerve, vesicant, respiratory and blood agents (chemical diagnostics) with the goal to rapidly identify the causative agent in a remote environment prior to onset of symptoms.

Medical Therapeutics: The goal of the Therapeutics capability area is to develop lead candidate medical treatments and pharmaceuticals that, when administered after exposure to a chemical or biological agent, mitigate or curtail the effects of that exposure and sustain forces operating in a chemical biological warfare hazard area.

Medical Therapeutics are segregated into biological countermeasures and chemical countermeasures.

2.0 BAA Particulars

2.1 BAA Process Overview

This BAA will utilize either a one, or two-phase evaluation process for each submission. The two-phase process will consist of the submission and evaluation of Phase I and Phase II proposals.

While all interested parties may submit Phase I proposals, submission of Phase II proposals will be by invitation only. Please note that the two-phase process will apply to all topics released unless otherwise identified within a specific topic.

In the case of a two-phase process, the evaluation status of Phase I and Phase II proposals will be provided at two points. An email will be sent to each proposer after the completion of Phase I proposal evaluations. The email will either inform the proposer that their Phase I proposal is no longer under consideration, or it will provide instructions for the submission of a Phase II proposal. In a similar manner, proposers that submit a Phase II proposal will receive an email informing them that their proposal is either no longer under consideration or has been selected for award pending successful negotiations.

In the case of a one-phase process, the Government may engage in communications with proposers during the course of evaluations for the purpose of enhancing the Government’s understanding of a research proposal and facilitating the evaluation process. These communications may be considered in rating proposals. Upon completion of evaluation and the subsequent selection decision, proposers will receive an email informing them that either their proposal is no longer under consideration or has been selected for award pending successful negotiations. Proposers should note that while proposal selection is premised upon a streamlined submission and evaluation process, a fully-supported cost proposal, technical basis of estimate and supplemental information will be required subsequent to the selection decision and notification. Successful proposers will be provided with proposal instructions at the appropriate time.

2.2 Proposal Submission Deadline

Submission deadlines are detailed in the calls released for each topic or set of topics.

Proposals must be received by this date and time in order to be considered. Submission information is provided in Section 4.0 of this BAA.

2.3 Potential Award Instruments

A full range of flexible acquisition related statutory authority arrangements available to DTRA are possible results from this announcement, including but not limited to, contracts, Other Transaction Agreements (OTAs), and Interagency Agreements (IAs). The Government does not intend to award grants or cooperative agreements under this solicitation. Each of these procurement instruments offers different advantages, liabilities and responsibilities for proposers and the Government. Except for OTAs, the Government actions under this BAA shall adhere to the requirements of the Federal Acquisition Regulation (FAR) and Defense Federal Acquisition Regulation Supplement (DFARS).

While proposers may suggest a proposed instrument, the Government contracting officer has the sole discretion to determine the award instrument type and negotiate all instrument terms and conditions with proposers.

2.4 Contract Considerations

The Government intends to award Cost and Cost-Plus-Fixed-Fee (CPFF) contracts. In accordance with FAR 16.301-3(a)(3), Cost-Reimbursement contracts require that the proposer’s accounting system is adequate for determining costs applicable to the contract. Determinations of accounting system inadequacy, or lack of evidence to support a determination of accounting system adequacy, will preclude the proposer from receiving a cost-type contract. The Government will typically rely on the findings of a DCAA accounting system audit in making a determination of accounting system adequacy. The Government may consider award of fixed price contracts in appropriate circumstances.

In accordance with FAR 17.204(e), contract periods of performance shall be limited to a maximum of five years, inclusive of all options.

2.5 OTA Considerations

An OTA may only be awarded if it meets one of the following criteria:

There is at least one non-traditional defense contractor or non-profit research institution participating to a significant extent in the prototype project; or all significant participants in the transaction other than Federal Government are small businesses (including those participating in the Small Business Innovation Research (SBIR) or Small Business Technology Transfer (STTR) programs), or non-traditional defense contractors; or at least one-third of the total cost of the prototype project is to be paid out of funds provided by parties other than the Federal Government; or

The senior procurement executive for the agency determines in writing that exceptional circumstances justify the use of a transaction that provides for innovative business arrangements or structures that would not be feasible or appropriate under a contract, or would provide an opportunity to expand the defense supply base in a manner that would not be practical or feasible under a contract.

For purposes of determining whether or not a participant may be classified as a nontraditional defense contractor or small business and whether or not such participation is determined to be participating to a significant extent in the prototype project, the following definitions are applicable:

“Nontraditional defense contractor” means an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense for the procurement or transaction, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section.

“Small Business” means a small business concern as defined under Section 3 of the Small Business Act (15 U.S.C. § 632).

“Participating to a significant extent in the prototype project” includes, but is not limited to, the existence of one or more of the following considerations: whether the nontraditional defense contractor, small business or nonprofit research institution will supply a novel application or approach to an existing technology, product or process;

provide a material increase in the performance, efficiency, quality or versatility of a key technology, product or process; accomplish a significant amount of the prototype project;

cause a material reduction in the cost or schedule of the prototype project; or, provide for a material increase in performance of the prototype project.

In accordance with 10 U.S.C. § 2371b(f), the Government may award a follow-on production contract or OTA for any OTA awarded under this BAA if: (1) that participant in the OTA, or a recognized successor in interest to the OTA, successfully completed the entire prototype project provided for in the OTA, as modified; and (2) the OTA provides for the award of a follow-on production contract or OTA to the participant, or a recognized successor in interest to the OTA.

2.6 IA Considerations

In the event that a proposer is one of the three eligible federal sources listed below and the proposer’s project is tentatively selected for award and funding, DTRA will work with the appropriate sponsoring agency to issue an IA pursuant to the Economy Act (31 U.S.C. § 1531) or other appropriate authority.

DoD-sponsored Federally Funded Research and Development Center (FFRDC), as specified in DFARS 235.017-1

University Affiliated Research Center (UARC), provided that it is permitted by the UARC's DoD sponsor

Department of Energy (DOE) sponsored FFRDC or National Aeronautics and Space Administration (NASA) sponsored FFRDC, provided that authorization is obtained from the DOE or NASA sponsor

2.7 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 cannot identify whether the work to be awarded against each topic will be considered fundamental research and may award both fundamental and non-fundamental research.

For each topic, the Government shall have sole discretion to determine whether the proposed research shall be considered fundamental.

3.0 BAA Eligibility

3.1 Eligible Sources

Proposals submitted in response to this BAA will be considered from the following U.S. and Foreign Enterprises:

Industrial/commercial concerns including small businesses Accredited Degree granting colleges and universities Not-for-profit organizations Other Non-U.S. sources DoD-sponsored FFRDCs specified in DFARS 235.017-1 UARCs, provided that it is permitted by the UARC's DoD sponsor DOE-sponsored FFRDCs and NASA-sponsored FFRDCs, provided that authorization is obtained from the DOE sponsor or NASA sponsor

3.2 Non-Eligible Sources

The following entities may not participate as prime contractors, nor furnish Principal Investigators (PIs) in awards made under individual topics, but may act as subcontractors:

Federal laboratories other than those DoD, DOE and NASA sponsored FFRDCs specified above

U.S. Government agencies and organizations Academic institutions that are federal government organizations (e.g., Naval

Postgraduate School)

4.0 Proposal Submission Information

4.1 General Instruction Information

To assure timely and equitable evaluation of proposals, proposers must follow the instructions contained herein, unless otherwise provided within an individual topic. Proposers are required to meet all solicitation requirements, including terms and conditions, representations and certifications, technical requirements, and proposal content and format requirements. Failure to meet a requirement or to follow the specific proposal instructions provided may preclude consideration of the proposal and/or result in a proposal being ineligible for award.

Additionally, proposers must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. It is the proposer’s responsibility to ensure the completeness of the proposal. Evaluation of a proposal will be conducted only on the basis of the information contained within it and the Government will not assume that a proposer possesses any capabilities not specified.

Proposals shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposer shall assume that the Government has no prior knowledge of the proposer’s capabilities.

4.2 Registration for the DTRA Proposal Submission Website

All proposers are required to register at the DTRA proposal submission website prior to submission of proposals. Detailed registration and submission instructions are available at the website: http://www.dtrasubmission.net.

The registration must be submitted by a central Business Point of Contact (BPOC) rather than individual PI personnel. A BPOC is a person who is given the responsibility of coordinating all submissions from individual PIs at his or her work location and is the only individual who may access the DTRA proposal submission website. The intent is that all submissions from an organization be coordinated and submitted by a single, identified responsible party. Failure to register in accordance with instructions may render a proposer ineligible for participation in this BAA.

Proposers must be aware that it is their responsibility to ensure that e-mail notifications reach the designated BPOC and that e-mail notifications are not blocked due to the use of 'spam blocker' software or other means that the recipient's Internet Service Provider may have implemented as a means to block the receipt of certain e-mail messages.

Additionally, it is the responsibility of the BPOC to inform DTRA of any updates to e-mail addresses for both themselves as the registered BPOC and for the designated PI.

IMPORTANT: Registration at the DTRA proposal submission website is NOT the same as registering at the System for Award Management or beta.SAM.GOV websites. Failure to register http://www.dtrasubmission.net/ at the DTRA proposal submission website will prevent a proposer’s submission of documents required and thus render the proposer ineligible for participation in this BAA.

4.3 Registration for the System for Award Management (SAM)

Website DTRA requires that all proposers be registered in the SAM database at the time of proposal submission. Contractors must keep their registration current for the life of the contract.

Proposers may register with SAM online at https://www.sam.gov. Proposers will NOT be able to complete their SAM registration until SAM has confirmed the proposer’s Employer Identification Number (EIN) or Taxpayer Identification Number (TIN) with the Internal Revenue Service (IRS).

NOTE: It will take 24-48 hours for the IRS to validate the TIN. According to the IRS, if proposers do not currently have an EIN and need to apply for one over the phone or Internet, they will be given a tentative EIN, but the EIN may not become active for up to two (2) weeks. Questions regarding an EIN may be directed at 1-800-829-4933.

4.4 General Proposal Instructions

All proposals must be submitted electronically through the DTRA proposal submission website: http://www.dtrasubmission.net. Any proposal submitted by any means other than the DTRA proposal submission website will not be considered (e.g., hand-carried, postal service, commercial carrier, e-mail).

Proposers are responsible for ensuring submission of their proposals by the date and time specified in Section 2.2. Time management is wholly the responsibility of the proposer.

If a timely submission is not fully uploaded prior to the cutoff date/time, the proposal will not be considered. No exceptions will be made. The proposer must verify the submission of their proposal package by printing the electronic receipt (time and date stamped) that appears on the final screen following the compliant submission of a proposal to the DTRA proposal submission website.

Using the DTRA proposal submission website, all proposers must prepare proposal cover sheets for each proposal submitted (Phase I and Phase II, if applicable). All data point requirements must be completed in every cover sheet. Once the cover sheet is saved, the system will assign a unique proposal number for each submission. Cover sheets may be edited as often as necessary until the submission period closes. All submissions must be dated and unclassified.

https://www.sam.gov./ http://www.dtrasubmission.net/

If multiple proposals are being submitted by the same proposer in response to more than one topic, separate cover sheets must be generated for each proposal and the full proposal files must be uploaded with the associated cover sheet, since a unique document number will automatically be assigned to each submission by the electronic proposal tracking system. All documents submitted to the DTRA proposal submission website are considered works in progress and are not eligible for evaluation until the proposer submits the final proposal package for consideration. Once all proposal files have been uploaded and the proposer is ready to submit their application, select the green "Submit" button on the page. A confirmation message will appear on the page once the submission has gone through. Perform a virus check before uploading any proposal files. If a virus is detected, it may cause rejection of the file.

Proposers must submit proposals to the appropriate topic. Failure to do so will render the proposal ineligible for evaluation and award.

4.5 Late Submissions and Withdrawal of Proposals

Proposers are responsible for access to the DTRA proposal submission website and for submitting electronic proposals so as to be received at the Government site indicated in this BAA no later than the closing date and time stated in Section 2.2. Untimely proposals will not be considered.

When sending electronic files, the proposer will account for potential delays in file transfer from the originator’s computer server to the Government website/computer server. Proposers are encouraged to submit their proposals early to avoid potential file transfer delays due to high demand or problems encountered in the course of the submission. Proposers should also print, and maintain for their records, the electronic date/time stamped receipt that appears on the final screen following submission of a proposal on the DTRA proposal submission website. All submissions shall be fully uploaded before the cut off time/date in order to be considered.

Proposals may be withdrawn by written notice received at any time before award.

Withdrawals are effective upon receipt of notice via the e-mail address listed in Section 8.1.

4.6 Proposal File Requirements

Proposers shall submit the required components of each proposal volume as specified below.

Additional files will not be accepted. All proposal files must not be encrypted, and submission of files using older versions of the software below may not be accepted. It is recommended that all files be created using the most up to date versions of the software listed below.

4.6.1 Phase I Proposal

• Quad Chart – Microsoft (MS) PowerPoint

• White Paper – Portable Document Format (PDF) compatible with Adobe Acrobat

• Draft Statement of Work (SOW) – MS Word

4.6.2 Phase II Proposal

4.6.2.1 Technical Volume

• Technical Proposal – PDF compatible with Adobe Acrobat

• Basis of Estimate (BOE) - PDF compatible with Adobe Acrobat

• SOW – MS Word

4.6.2.2 Cost Volume

• Cost Narrative / Supporting Documentation – PDF compatible with Adobe Acrobat

• Cost Spreadsheet – MS Excel, or compatible format

4.6.2.3 Supplemental Information Volume

• Unless specified in Section 4.8.2.3, all documents within this volume shall be submitted as PDF compatible with Adobe Acrobat

4.7 Proposal Format Requirements

Proposals shall conform to the format requirements specified below.

4.7.1 Phase I Proposal

4.7.1.1 Quad Chart

• Paper Size: 8.5 x 11 inches, landscape orientation

• Page Limit: No more than one (1) page. Pages in excess of the page limitation will not be read or evaluated

• Classification: Unclassified

• Restrictive Markings: The Quad Chart must not contain information deemed trade secret, confidential or proprietary by the proposer

4.7.1.2 White Paper

• Paper Size: 8.5 x 11 inches

• Spacing: Single-spaced

• Margins: One-inch

• Page Limit: No more than six (6) pages. Pages in excess of the page limitation will not be read or evaluated

• Classification: Unclassified

• Restrictive Markings: Documents containing proprietary information shall contain the restrictive markings reflected in Section 4.7.3

4.7.1.3 Draft SOW

• Spacing: Single-spaced

• Margins: One-inch

• Page Limit: None

• Classification: Unclassified

• Restrictive Markings: The draft SOW must not contain information deemed trade secret, confidential or proprietary by the proposer; reference ATTACHMENT 2 for additional information

4.7.2 Phase II Proposal

4.7.2.1 Technical Volume

4.7.2.1.1 Technical Proposal

• Paper Size: 8.5 x 11 inches

• Spacing: Single-spaced

• Margins: One-inch

• Page Limit: No more than twenty-five (25) pages. Pages in excess of the page limitation will not be read or evaluated

• Classification: Unclassified

• Restrictive Markings: Documents containing proprietary information shall contain the restrictive markings reflected in Section 4.7.3

4.7.2.1.2 BOE

• Spacing: Single-spaced

• Margins: One-inch

• Page Limit: None

• Classification: Unclassified

4.7.2.1.3 SOW

• Spacing: Single-spaced

• Margins: One-inch

• Page Limit: None

• Classification: Unclassified

• Restrictive Markings: The SOW must not contain information deemed trade secret, confidential or proprietary by the proposer; reference ATTACHMENT 2 for additional information

4.7.2.2 Cost Volume

4.7.2.2.1 Cost Narrative / Supporting Documentation

• Paper Size: 8.5 x 11 inches

• Spacing: Single-spaced

• Margins: One-inch

• Page Limit: None

• Classification: Unclassified

4.7.2.2.2 Cost Spreadsheet

• Format shall be in accordance with ATTACHMENT 5

• All formulas shall be preserved

• Page Limit: None

• Classification: Unclassified

4.7.2.3 Supplemental Information Volume

• Spacing: Single-spaced

• Margins: One-inch

• Page Limit: None

• Classification: Unclassified

4.7.3 Restrictive Markings and Disclosure of Proprietary Information

Proposal content submitted in response to this BAA (with the exception of the SOW) may contain technical information and other data that the proposer does not want disclosed to the public or used by the Government for any purpose other than proposal evaluation. Public release of information in any submission will be subject to existing statutory and regulatory requirements. If proprietary information which constitutes a trade secret, proprietary commercial or financial information, confidential personal information, or data affecting national security is provided by a proposer, it will be treated in confidence, to the extent permitted by law, provided that the following legend appears and is completed on the front of the submission:

“For any purpose other than to evaluate the proposal, this data shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed in whole or in part, provided that, if an award is made to the proposer as a result of or in connection with the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the agreement. This restriction does not limit the right of the Government to use information contained in the data if it is obtained from another source without restriction. The data subject to this restriction is contained in page(s) of this proposal.”

Any other legend may be unacceptable to the Government and may constitute grounds for removing the proposal from further consideration without assuming any liability for inadvertent disclosure. The Government will limit dissemination of properly marked information to official channels.

In addition, the pages indicated as restricted must be marked with the following legend: “Use or disclosure of the proposal data on lines identified by an asterisk (*) are subject to the restriction on the front page of this proposal.” The Government assumes no liability for disclosure or use of unmarked data and may use or disclose such data for any purpose.

In the event that properly marked data contained in a proposal submitted in response to this BAA is requested pursuant to the Freedom of Information Act, 5 U.S.C. § 552, the proposer will be advised of such request and, prior to such release of information, will be requested to expeditiously submit to DTRA a detailed listing of all information in the proposal to which the proposer believes to be exempt from disclosure under the Act. Such action and cooperation on the part of the proposer will ensure that any information released by DTRA pursuant to the Act is properly identified.

By submission of a proposal, the proposer understands that proprietary information may be disclosed outside the Government for the sole purpose of technical evaluation. The contracts office will obtain a written agreement from the evaluator that proprietary information in the proposal will only be used for evaluation purposes and will not be further disclosed or utilized.

4.8 Proposal Content Requirements

Proposals shall conform to the content requirements specified below.

4.8.1 Phase I Proposal

4.8.1.1 Quad Chart

4.8.1.1.1 Heading

• Title of Project

• Topic Number

• Principal Investigator

• Organization

4.8.1.1.2 Upper Left Quadrant

• Objective – Provide a clear and concise description of the goal of the effort

• Description of Effort – Provide a brief description of the technology proposed for investigation and the methodologies to be used during the course of investigation

4.8.1.1.3 Lower Left Quadrant

• Benefits of Proposed Technology – Provide a brief description of the net advantages of the proposed technology over current practices and other competing technologies

• Challenges – Provide a bullet list of the technical or scientific challenges being addressed

• Maturity – Describe the maturity of proposed technology with respect to the TRL at project start and the anticipated TRL at project end. Reference ATTACHMENT 1 for TRL definitions

4.8.1.1.4 Upper Right Quadrant

• Picture or graphic illustrating proposed technology development

4.8.1.1.5 Lower Right Quadrant

• Period of Performance – Provide the project period of performance. If the project incorporates multiple periods of performance, separated by logical and meaningful milestones and go/no-go decision points, provide the duration of each period

• Major Goals/Milestones and Deliverables – Provide a bullet list of the major project goals, milestones and deliverables. If utilizing multiple project periods of performance, provide the goals, milestones and deliverables for each period and for the overall project

• Cost – Provide a Rough Order of Magnitude (ROM) cost estimate. If utilizing multiple project periods of performance, provide ROM estimates for each period and for the overall project

4.8.1.2 White Paper

The white paper shall include the following sections in the order given below:

(1) Proposers shall describe the following elements of the project technical approach:

• Project background, objectives and scope

• Overview of the tasks and methods planned to achieve each objective and the final deliverables and/or project end state

• Current Capabilities – Describe the proposer’s current capabilities in terms of key personnel, facilities, and equipment that will be dedicated to the execution of the technical approach

• Required Capabilities – Explain what capabilities will be required to successfully execute the technical approach, and describe how the proposer plans to fill any capability gaps in terms of expertise, facilities, and equipment (e.g. subcontractor teaming arrangements, consultants, equipment purchases, etc.)

• Evidence of Teaming Arrangements – For each of the capability gaps described in the “Required Capabilities” bullet, provide evidence of teaming arrangements or explain what steps have been taken to ensure a commitment to perform from the parties who will provide the necessary capabilities.

Supporting documentation, such as a signed Memorandum of Agreement (MOA) or Memorandum of Understanding (MOU) from potential team members, shall not be subject to the page limitation. Narratives explaining actions taken to secure commitments from potential team members shall be subject to the page limitation

• Any applicable technical and/or scientific challenges associated with the proposed project and how the proposer intends to address these challenges

(2) Proposers shall provide a narrative project overview describing:

• How the technology addresses the topic requirement

• How the technology can be implemented or utilized by DoD end-users and the impact of the technology on end-user mission capability

• The current TRL of the technology and the anticipated TRL at the end of the proposed project

(3) Proposers shall describe the estimated costs for the proposed technical approach.

Proposers shall provide a breakout of estimated costs by project milestone. If the proposed project includes multiple periods of performance, provide estimated costs by milestone for each project period

4.8.1.3 Draft SOW

The draft SOW shall be submitted in accordance with the sample template provided in

ATTACHMENT 2.

4.8.2 Phase II Proposal

4.8.2.1 Technical Volume

4.8.2.1.1 Technical Proposal

4.8.2.1.1.1 Abstract

Proposers shall provide a brief abstract

4.8.2.1.1.2 Scope

Proposers shall provide a detailed description of project scope, to include project objectives, background, programmatics and relevance.

A. Objective – Proposers shall state clearly and concisely the objective of the proposed project

B. Background – Proposers shall provide the necessary technical and scientific background, and preliminary data, to support the scientific and/or technical merit of the proposed project

C. Technical Approach – Proposers shall describe in detail the proposed technical approach

D. Relevance – Proposers shall describe the relevance of the proposed project in terms of DTRA mission, end-user needs and the state-of-the-art of the proposed technology

E. References – Proposers shall list any relevant documents used to develop the technical approach

4.8.2.1.1.3 Credentials

Proposers shall provide credentials and qualifications, limited to that which is directly relevant to the proposed work.

A. Summary of Organizational Credentials and Qualifications – Proposers shall describe their organizational qualifications and credentials to perform the proposed project

B. Summary of Qualifications for PI and Key Personnel – Proposers shall list summary qualifications for the proposed PI and other key personnel

4.8.2.1.1.4 Project Management

Proposers shall provide a project management plan, their capabilities to perform the proposed work, a Gantt chart, and a time-phased expenditure plan.

A. Project Management Plan – Proposers shall describe their organization’s project management plan for the proposed project. The proposer shall address each of the following:

1. Explain how the proposer will manage the project, ensuring that the required performance outcomes are achieved within the required schedule, at or below the contract cost ceiling

2. Provide the processes and techniques that demonstrate the proposer’s ability to act as a resource integrator with the capability to effectively manage all aspects of execution of the technical approach, to include:

a.) Identifying and addressing project technical risk;

b.) leveraging and managing resident expertise, teaming arrangements and/or other partnerships to provide the required capabilities to successfully execute the technical approach and accomplish the tasks identified in the SOW;

c.) effectively and efficiently managing and leading assigned tasks, including those assigned to external organizations; and d.) identifying key personnel to include a program/project manager responsible for providing cohesive technical and administrative leadership and direction to facilitate the successful completion of contract requirements

3. Explain the risks associated with achieving proposed project goals, objectives and milestones (what will be done), and risks associated with the technical approach (how it will be done). For all identified risks, proposers shall indicate how they plan to manage these risks (e.g.

avoidance, acceptance, mitigation, transfer) and provide a detailed narrative explaining the corresponding risk management actions that will be taken for each identified risk

B. Capabilities to Perform the Proposed Work – Proposers shall describe the roles and responsibilities that will be assigned to each proposed team member (e.g. proposer, subcontractor, consultant, CRO, etc.). The proposer shall also describe the capabilities each proposed team member possesses, to include expertise, facilities, and equipment, to successfully execute the proposed project, and substantiate these capabilities with examples of past performance/relevant experience executing similar work.

C. Gantt Chart – Proposers shall provide a Gantt chart that lists each individual SOW task and provides the duration of performance for each

D. Time-phased Expenditure Plan – Proposers shall provide a time-phased expenditure plan, provided in chart format, that provides estimated cost accruals by month, by project period. For example, if the proposed project includes three periods of performance, each lasting twelve months, the proposer’s chart will be broken out into three separate twelve-month periods

4.8.2.1.2 BOE

A. For each proposed SOW task, proposers shall address the following:

1. SOW Task

2. Technical Approach – The proposed technical approach to execute the individual SOW task

3. Milestones, Metrics, Objectives and Deliverables – The milestones, metrics, objectives, and deliverables associated with the individual SOW task

4. BOE – The proposed resources to execute the technical approach, covering all cost elements in accordance with the below information and format requirements. No cost information shall be provided with the BOE. Address each of the following requirements:

a) Direct Labor

i. Direct Labor Breakout – Provide a chart that lists each individual labor category assigned to this task and the number of hours allocated to each listed labor category

ii. Direct Labor Justification – Proposers shall explain in detail, how the estimate was developed (e.g. bottom-up analysis, analogy), the rationale supporting the chosen estimating technique, and why each proposed labor category, and the hours allocated to each labor category, is reasonable and necessary to execute the technical approach. Proposers shall also explain any assumptions that were relied upon, and risks that were considered, in the development of the estimate

b) Subcontracts

i. Subcontractor Breakout – Provide a chart that lists each individual subcontractor assigned to this task

ii. Subcontractor Justification – Proposers shall explain, in detail, why each proposed subcontractor is appropriate and necessary to execute the technical approach

c) Consultants

i. Consultant Breakout – Provide a chart that lists each individual consultant assigned to this task and the number of hours allocated to each consultant

ii. Consultant Justification – Proposers shall explain, in detail, why each proposed consultant, and associated level of effort/hours, is appropriate and necessary to execute the technical approach. Proposers shall also explain any assumptions that were relied upon, and risks that were considered, in the development of the estimate

d) Materials/Supplies

i. Material/Supply Breakout – Provide a chart that lists each individual material and supply item assigned to this task and the quantity for each

ii. Material/Supply Justification – Proposers shall explain, in detail, how the estimate was developed (e.g. bottom-up analysis, analogy), the rationale supporting the chosen estimating technique, and why each proposed material and supply item is appropriate and necessary to execute the technical approach. Proposers shall also explain any assumptions that were relied upon, and risks that were considered, in the development of the estimate

e) Equipment

i. Equipment Breakout – Provide a chart that lists each individual equipment item assigned to this task and the quantity for each

ii. Equipment Justificiation – Proposers shall explain, in detail, how the estimate was developed (e.g. bottom-up analysis, analogy), the rationale supporting the chosen estimating technique, and why each proposed equipment item is appropriate and necessary to execute the technical approach.

Proposers shall also explain any assumptions that were relied upon, and risks that were considered, in the development of the estimate

f) Travel

i. Travel Breakout – Provide a chart that lists each individual travel event, and for each individual travel event, list the following: a) reason for travel, b) destination, c) number of travelers, d) applicable labor categories, and e) duration of travel

ii. Travel Justification – Proposers shall explain, in detail, why each proposed travel event and the proposed travelers (by labor category) are appropriate and necessary to execute the technical approach. Proposers shall also explain any assumptions that were relied upon, and risks that were

g) Other Direct Costs (ODCs)

i. ODC Breakout – Provide a chart that lists each individual ODC item assigned to this task and the quantity for each

ii. ODC Justification – Proposers shall explain, in detail, how the estimate was developed (e.g. bottom-up analysis, analogy), the rationale supporting the chosen estimating technique, and why each proposed ODC item is appropriate and necessary to execute the technical approach. Proposers shall also explain any assumptions that were relied upon, and risks that were

The BOE must clearly and accurately reflect the proposed SOW. Proposers must complete the above for each proposed project period of performance (e.g. Base Period, Option Period 1, etc.). Each proposed subcontractor must also provide a BOE addressing the above requirements.

4.8.2.1.3 SOW

The SOW shall be submitted in accordance with the sample template provided in ATTACHMENT 2.

4.8.2.2 Cost Volume

All proposals may be subject to the requirements of the Truth in Negotiations Act (TINA). A proposal tentatively selected for award exceeding the threshold listed in FAR 15.403-4(a)(1) may be required to submit a certificate of current cost and pricing data in the format described in FAR 15.406-2 upon conclusion of successful negotiations.

The responsibility for providing adequate supporting data and attachments lies solely with the proposer. The cost proposal must include cost estimates sufficiently detailed for meaningful evaluation. Further, the proposer must also bear the burden of proof in establishing reasonableness of proposed costs; therefore, it is in the proposer’s best interest to submit a fully supportable and well-prepared cost proposal. The basis and rationale for all proposed costs should be provided in the cost narrative so that Government personnel can place reliance on the information as current, complete, and accurate.

4.8.2.2.1 Cost Narrative / Supporting Documentation

All proposers shall provide documentation, and analysis as required, to support the proposed costs contained within ATTACHMENT 5. Specific information requirements for this section are also included within ATTACHMENT 5

4.8.2.2.2 Cost Spreadsheet

The proposer shall prepare the Cost Spreadsheet utilizing ATTACHMENT 5.

Proposers shall follow all instructions, including those referenced as ‘Notes’ contained within the Cost Spreadsheet

4.8.2.3 Supplemental Information Volume

Proposers must complete the Supplemental Volume Cover Sheet provided as ATTACHMENT 4. Any required supplemental volume items not addressed by the information sheet must be uploaded to the supplemental volume section of the proposal submission website. Additional details about each specific item are located in the below sections. If any particular item is not relevant to the proposed effort, include a reference to the requested information and state that the particular information is not applicable in order to confirm a negative response.

4.8.2.3.1 Representations and Certifications

Proposers must complete the annual representation and certifications electronically via SAM. In addition, the proposer is also required to execute the following representations and certifications that are not in SAM by completing and submitting ATTACHMENT 6.

• FAR 52.204-24 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment

• FAR 52.204-26 Covered Telecommunications Equipment or Services-

Representation

• FAR 52.209-7 Information Regarding Responsibility Matters

• FAR 52.209-13 Violation of Arms Control Treaties or Agreements-

Certification

• DFARS 252.203-7005 Representation Relating to Compensation of Former

DoD Officials

• DFARS 252.204-7008 Compliance with Safeguarding Covered Defense

Information Controls

• DFARS 252.204-7016 Covered Defense Telecommunications Equipment or

Services-Representation

• DFARS 252.204-7017 Prohibition on the Acquisition of Covered Defense

Telecommunications Equipment or Services-Representation

Additionally, the proposer is required to verify that the electronic representations and certifications are current, accurate and complete and applicable to this BAA in accordance with FAR 4.1201.

4.8.2.3.2 Intellectual Property

A. Patents – Proposers must list any known patents, patent applications, or inventions which the proposer may be required to license in order to perform the work described in the proposer’s proposal, or which the Government may be required to license to make or use the deliverables of the contract, should the proposer’s proposal be selected for award. For any patent or patent application listed above, the proposer must provide the patent number or patent application publication number, a summary of the patent or invention title, and indicate whether the proposer is the patent or invention owner. If a patent or invention is in-licensed by the proposer, identify the licensor.

If any listed patent, patent application or invention is owned or licensed by the proposer, the proposer must provide a statement, in writing, if it either owns or possesses the appropriate licensing rights to the patent, patent application or invention to perform the work described in the proposal and/or to grant the Government a license to make or use of the deliverables for this program. If any listed patent, patent application or invention is not owned or licensed by the proposer, then the proposer must explain how it will obtain a license, how the Government may obtain a license and/or whether the proposer plans to obtain these rights on behalf of the Government.

Be advised that no patent, patent application or invention disclosure will be accepted if identified in the Data Rights Assertion List described in subsection

4.8.2.3.2 (B) below. Existing inventions, patents and patent applications should be discussed in the above list. Government rights in any technology that might be invented or reduced to practice under the contract are addressed in the patent rights clause to be included in the contract.

B. Data Rights – Proposals submitted in response to this BAA shall identify, to the extent known at the time an offer is submitted to the Government, the technical data or computer software that the proposer, its subcontractors or suppliers, or potential subcontractors or suppliers, assert should be furnished to the Government with restrictions on use, release, or disclosure, in accordance with DFARS 252.227-7017, Identification and Assertion of Use, Release or Disclosure Restrictions, and DFARS 252.227-7028, Technical Data or Computer Software Previously Delivered to the Government. The proposer's assertions, including the assertions of its subcontractors or suppliers or potential subcontractors or suppliers, shall be submitted as an attachment to its offer, utilizing ATTACHMENT 3, dated and signed by an official authorized to contractually obligate the proposer. If the proposer will deliver all technical data and computer software to the Government without restrictions, enter “NONE” in this table under the heading “Technical Data or Computer Software to be Furnished with Restrictions.”

Proposers responding to this BAA requesting an OTA shall specifically identify any asserted restrictions on the Government’s use of intellectual property contemplated under those award instruments. For this purpose, proposers must propose specific Intellectual Property terms and conditions and a data deliverable list. Proposers are encouraged to model their data rights assertions list to the template provided in DFARS 252.227-7017.

4.8.2.3.3 Subcontracting Plan

Any proposer, other than small businesses, submitting a proposal for an award with a value more than the amount listed in FAR 19.702(a)(1) and that has subcontracting possibilities, must submit a subcontracting plan in accordance with FAR 19.7. Pursuant to Section 8(d) of the Small Business Act (15 U.S.C. § 637(d)), it is the policy of the Government to enable small business and small disadvantaged business concerns to be considered fairly as subcontractors to contractors performing work or rendering services as prime contractors or subcontractors under Government contracts, and to assure that prime contractors and subcontractors carry out this policy.

A subcontracting plan identifies the proposer's approach to awarding subcontracts to small business, small disadvantaged business, women-owned small business, service-disabled veteran owned small business, and Historically Underutilized Business Zone (HUB Zone) small business concerns, on this effort.