Attachment_C_COOP_Proposal_Instructions_and_Volume_I_Technical_and_Management_Template.docx

HR001124S0016: Continuous-correctness On Opaque Processors (COOP) Program Attachment C - Volume I: Technical and Management Proposal Volume Template

Use of this template is mandatory for all proposal submissions to this BAA. Proposers must include Attachments B, C, D, and E to constitute a full proposal submission. Proposals not meeting the format prescribed herein may not be reviewed.

This document must include all components described herein and must be submitted in PDF or Microsoft Word formats. All submissions must be written in English, and all pages shall be formatted for printing on 8-1/2 by 11-inch paper with 1-inch margins and font size no smaller than 12-point. Font sizes of 8 or 10-point may be used for figures, tables, and charts.

Proposers are encouraged to submit concise but descriptive proposals. Specific examples of problems, approaches, or goals are preferred to qualitative generalities. The Government will not consider pages in excess of the page count limitations, as described herein. Proposals with fewer than the maximum number of pages will not be penalized. Additional information not explicitly called for in the Technical and Management Volume must not be submitted with the proposal but may be included as links in the bibliography. Such materials will be considered for the reviewers’ convenience only and not evaluated as part of the proposal.

Technical and Management Volumes shall not exceed a maximum of 15 pages.

Official transmittal letter

Table of Contents

Appendix I: Formal Threat Model (Optional)

Appendix II: References/Bibliography (Optional)

Appendix III: Statement of Work

Appendix IV: Administrative

Resumes (Optional)

Technical Papers (Optional)

Proposals must be submitted per the instructions outlined herein and received by DARPA no later than the due date and time listed in the Overview Information section. Proposals received after this time and date may not be reviewed. Please visit Proposer Instructions and General Terms and Conditions for instructions on how to submit your proposal through the Broad Agency Announcement Tool (BAAT).

COVER SHEET

[PRIME ORGANIZATION LOGO]

Proposal Title

Proposer Organization

SAM.gov Unique Entity ID (UEI)[endnoteRef:2] [2: The SAM-generated UEI becomes the official identifier for doing business with the U.S. Government. This replaces DUNS.]

Commercial and Government Entity (CAGE) code[endnoteRef:3] [3: A CAGE Code identifies companies doing or wishing to do business with the Federal Government. ]

Proposer Reference Number, if any

Address:

Telephone:

Email:

Address:

Telephone:

Email:

Organization:

Organization Type:

Place(s) of Performance (including sub-awardees)

Period(s) of Performance

Total Proposed Cost (by Government Fiscal Year)

Base

Option 1

Option 2

Option 3

Total

Total Proposed Cost (by Calendar Year)

Base

Option 1

Option 2

Option 3

Total

Administration Office POC at Defense Contract Management Agency (DCMA)[endnoteRef:4] or Office of Naval Research (ONR)[endnoteRef:5], if known [4: https://pubapp.dcma.mil/CASD/CasdSearch.do.] [5: http://www.onr.navy.mil/Contracts-Grants/Regional-Contacts.aspx.]

Name:

Address:

Telephone:

Audit Office POC at Defense Contract Audit Agency (DCAA)[endnoteRef:6], if known [6: http://www.dcaa.mil/Home/Locator?title=Locator]

Name:

Address:

Telephone:

Date Proposal was submitted

Proposal Validity Period (minimum 120 days)

[Proposers may modify the header and footer to insert the company name, the page number and source selection information must remain in footer]

Table of Contents

Official Transmittal Letter [Attach the official transmittal letter from the prime proposer organization.]

HR001124S0016 Attachment C - Volume I: Technical and Management Proposal Volume Template Source Selection Information – See FAR 2.101 and FAR 3.104

Executive Summary [Summarize the technical approach, anticipated performance, and expected outcomes of the proposed effort. The executive summary should be concise and to the point. Tables, graphs, and diagrams can be used as supplemental material along with narrative to convey the information.] Innovative Claims Table [The table describing the innovative claims of the proposer technical approach. This table should include a title of the innovative claim, a short description of the innovative claim, a comparison to the state of the art, and (if applicable) who will be performing the innovative claim Informal Threat Model and Assumptions [All proposals are required to submit a one page (maximum) informal model that counts towards the page limit. Lengthier informal and formal models can be submitted as an optional appendix that does not count towards the page limit. Succinctly describe what the adversarial threat model being considered is and what assumptions must be held in order for the threat model to be realistic. Threat models will be grounded in quantifiable physics and physical phenomenon rather than qualitative concepts such as nation state actors.] Technical Approach [Outline and address technical challenges inherent in the approach and possible solutions for overcoming potential problems. This section should include a detailed technical approach, technical rationale, and constructive plan for accomplishing the technical goals in support of the innovative claims and deliverable creation. A constructive plan is a technical approach that builds upon itself and is tied together with the innovative claims, statement of work, and the technical rationale. The constructive plan should elaborate on the innovative claims table and provide detailed technical rationale as to why the technical approach will meet the program metrics. The technical rationale provides backing to the technical approach or innovative claim and enables the government to verify the claim or approach. The technical approach should also include a description of how formal models and claims will be internally and externally verified beyond the planned IV&V team. Demonstrate a deep understanding of the technical challenges and present a credible (even if risky) plan to achieve the project’s goal. Discuss mitigation of technical risk. The risk mitigation description should also include the risk of the proposed solution introducing new vulnerabilities and attack surfaces. Provide appropriate measurable milestones (quantitative if possible) at intermediate stages of the project to demonstrate progress and a plan for achieving the milestones. List Government-furnished materials or data assumed to be available.] Management Plan [Provide a summary of the proposed team, including any sub-awardees/consultants and key personnel who will be executing the work (please use table below). Identify a principal investigator (PI) for the project. Provide a clear description of the team’s organization, including an organization chart that illustrates, as applicable, the relationship of team members, unique capabilities of team members, teaming strategy among the team members, and key personnel with the amount of effort to be expended by each person during the project. It is DARPA’s intention to put key personnel conditions into the awards, so proposers should not propose personnel that are not anticipated to execute the work or with small time commitments. Provide a detailed plan for coordination, including explicit guidelines for interaction among collaborators/sub-awardees of the proposed project. Include risk management approaches. Describe any formal teaming agreements that are required to execute this project.] Prime

Sub-awardees/Consultants

Requirements for teams that include Government Entities and/or Federally Funded Research and Development Centers (FFRDCs) Are any of the team member organizations (prime or sub-awardee) a Government entity or FFRDC? No Yes [If yes, provide the information outlined below.]

a. Proof of Eligibility to Propose [Provide documentation citing the specific authority that establishes the applicable team member’s eligibility to propose to Government solicitations; include: (1) statutory authority; (2) contractual authority; (3) supporting regulatory guidance; and (4) evidence of agency approval for applicable team member participation. For FFRDCs, this documentation must be in the form of a letter on official letterhead from their sponsoring organization and must also include a statement of compliance with the terms and conditions of the associated FFRDC sponsor agreement, as applicable.]

b. Statement of Unique Capability [Provide a statement that demonstrates the work to be performed by the Government entity or FFRDC team member is not otherwise available from the private sector.]

Organizational Conflict of Interest Affirmations and Disclosure [In accordance with the requirements of the BAA, provide the following information.]

a. Are any of the proposed individual team members or their respective organizations (whether prime or sub-awardee or consultant) currently providing SETA, A&AS or similar support to DARPA? No Yes

b. Did any of the proposed individual team members or their respective organizations (whether prime or sub-awardee or consultant) provide SETA, A&AS or similar support to DARPA within one calendar year of this proposal submission? No Yes

[If you answered “Yes” to 8.a OR 8.b, provide the following information for each applicable team member:

· The name of the DARPA office receiving the support;

· The prime contract number;

· Identification of proposed team member (sub-awardee, consultant) providing the support; and

· An OCI mitigation plan in accordance with FAR 9.5.]

c. Are there any other potential Organizational Conflicts of Interest involving any of the proposed individual team members or their respective organizations (whether prime or sub-awardee or consultant)? No Yes [If yes, provide the following information for each applicable team member:

· Identification of applicable team member; and

· An OCI mitigation plan in accordance with FAR 9.5.]

Capabilities [Describe the organizational experience in the relevant subject area(s), existing intellectual property, or specialized facilities. Discuss any work in closely related research areas and previous accomplishments. Identify other Government solicitation(s) to which this concept has been proposed. If applicable, state whether funding or a positive funding decision has already been received and from which agency.] Novelty of Proposed Work [Has the proposed work been submitted to any other Government solicitation?

No Yes [If yes, provide the following information]

· Solicitation number ________________________

· Agency _________________________

· Proposed work has already received funding or a positive funding decision.

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

Appendix I: Formal Threat Model [Appendix for formal threat model (no more than 5 pages)]

I-1 Appendix II: Bibliography (Optional) [A brief (no more than 5 pages) bibliography may be provided with links to relevant papers, references, reports, etc.]

II-1

Appendix III: Statement of Work (SOW) [Provide a detailed task breakdown by Contractor Fiscal Year, citing specific tasks and their connection to the interim milestones and metrics, as applicable. Ensure all Phases/options are delineated. Do not include proprietary information.

For each defined task and subtask, provide:

· A general description of the objective.

· A detailed description of the approach to be taken to accomplish each defined task/subtask.

· Identification of any tasks/subtasks that will involve human subjects or animals.

· Identification of any tasks/subtasks that will be performed on campus at a university.

· Identification (by name) of the primary organization (prime contractor, sub-awardee (s), consultant(s)) responsible for task/subtask execution.

· A measurable milestone (e.g., a deliverable, demonstration, or other event/activity that marks task completion).

· A definition of all deliverables (e.g., data, reports, software) to be provided to the Government in support of the proposed tasks/subtasks.

· Identification of the proposed classification for each task/subtask.

· For all tasks and subtasks proposed to be unclassified, identify if the task/subtask is proposed as fundamental research or controlled unclassified information (CUI).

· Provide a short explanation for why each task/subtask should be categorized as fundamental research or CUI.]

III-1

Appendix IV: Administrative

1. Representations and Certifications

· For proposers requesting procurement contracts, please download, complete, and submit within this volume “Procurement Contracts Reps and Certs 2024 Fillable Template” available at the following link: Procurement Contracts

· For proposers requesting Other Transactions, please download, complete, and submit within this volume “2-SAMPLE OT certifications” available at the following link:

2. Intellectual Property (IP) Please provide the following information, as applicable. Note: the Government will assume unlimited rights to all IP not explicitly identified as restricted in the proposal.

a. Technical Data and Computer Software Are you asserting any IP restrictions on any technical data or non-commercial computer software that will be delivered to the Government? No Yes

[If yes, list all proprietary claims to results, prototypes, deliverables or systems supporting and/or necessary for the use of the proposed research, results, prototypes and/or deliverables. Provide a short summary for each item asserted with less than unlimited rights that describes the nature of the restriction and the intended use of the intellectual property in the conduct of the proposed research. Use the following format for these lists.]

NONCOMMERCIAL

Asserted Rights Category

Name of Person Asserting Restrictions

Are you proposing any commercial software that will be delivered to the Government? No Yes [If yes, please provide licensing terms.]

COMMERCIAL

Asserted Rights Category

Name of Person Asserting Restrictions

b. Patents Does the proposed effort involve using patented inventions that are owned by or assigned to the proposing organization or individual? No Yes [If yes, provide documentation proving ownership or possession of appropriate licensing rights to all patented inventions to be used for the proposed project. If a patent application has been filed for an invention, but it includes proprietary information and is not publicly available, provide documentation that includes: the patent number, inventor name(s), assignee names (if any), filing date, filing date of any related provisional application, and summary of the patent title, with either: (1) a representation of invention ownership; or (2) proof of possession of appropriate licensing rights in the invention (i.e., an agreement from the owner of the patent granting license to the proposer).]

IV-1