DARPA-BAA-16-38_Attachment_3_Proposal_Template_Technical_ _Management_Volume.docx

DARPA-BAA-16-38 ACCESS BAA

Attachment 3: Technical and Management Volume Template The Technical and Management Volume must include all components described herein.

All pages shall be formatted for printing on 8-1/2 by 11 inch paper with 1-inch margins and font size not smaller than 11 point. Font sizes of 8 or 10 point may be used for figures, tables, and charts. Submissions must be written in English. The Technical and Management Volume must be in .pdf, .odx, .doc, .docx, .ppt, .pptx, .xls, or .xlsx formats. The PowerPoint slides described herein should be attached as a separate file (all slides combined into a single slide deck) to this document.

Proposers are encouraged to submit concise, but descriptive, Technical and Management Volumes. Specific examples of problems, approaches, or goals are preferred to qualitative generalities. The Government will not consider pages in excess of the page count limitation, as described herein. Proposals with fewer than the maximum number of pages will not be penalized. Technical and management information not explicitly called for in the BAA or this document may only 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. Information incorporated into the Cost Volume which is not related to cost will not be considered.

Proposals not meeting the format prescribed herein may not be reviewed.

Volume 1 shall not exceed a maximum of 32 pages.

<PRIME ORGANIZATION LOGO>

DARPA-BAA-16-38

Volume 1: Technical and Management Volume

Proposal Title

Proposer Organization

Proposer Reference Number, if any

Address:

Telephone:

Email:

Address:

Telephone:

Email:

Place(s) of Performance

Period(s) of Performance

Organization:

Organization Type:

Date Proposal was Prepared

Proposal Validity Period (minimum 120 days)

Table of Contents

Source Selection Information – See FAR 2.101 and 3.104

DARPA-BAA-16-38 6

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

Proposal Summary Slides [Include the PowerPoint slides as a separate attachment to this document. Do not replicate the template using your own letterhead or formatting, nor submit it as a .pdf document or un-editable image file. Flattened graphics within the document are not acceptable.]

a. Executive Summary Slide [Using the slide template provided as Slide 1 of Attachment 1 to the BAA, provide a summary in PowerPoint that effectively and succinctly conveys the main objective, key innovations, expected impact, and other unique aspects of the proposed project.]

b. Concept Slide [Using the slide template provided as Slide 2 of Attachment 1 to the BAA, provide graphics, plots, conceptual diagrams and/or process flows to highlight the concept and technical approach.]

c. Cost Summary by Category Slide [Using the template provided as Slide 3 in Attachment 1 to the BAA, provide total effort cost by Government fiscal year broken down by major cost items.]

d. Cost Summary by Task Slide [Using the template provided as Slide 4 in Attachment 1 to the BAA, provide a summary of total effort costs by task.]

Milestone and Deliverable Summary Table [Using the template provided as Attachment 2 to the BAA, list the project milestones, deliverables and expected completion dates for the 15-month period of performance. Completion dates should be given in terms of months (or weeks) after award. If an award is made, this table will be updated to reflect calendar dates based on the actual award start date. Include the Word document as a separate attachment to this document. Do not replicate or mimic this template using your own letterhead or formatting, nor submit it as a .pdf document or uneditable image file.]

Goals and Impact [Describe what the proposed team is trying to achieve and the difference it will make (qualitatively and quantitatively) if successful. Describe the innovative aspects of the project in the context of existing capabilities and approaches, clearly delineating the uniqueness and benefits of this project in the context of the state of the art, alternative approaches, and other projects from the past and present. Describe how the proposed project is revolutionary and how it significantly rises above the current state of the art.

Describe the deliverables associated with the proposed project and any plans to commercialize the technology, transition it to a customer, or further the work. Discuss the mitigation of any issues related to sustainment of the technology over its entire lifecycle, assuming the technology transition plan is successful.]

Technical Plan [Outline and address technical challenges inherent in the approach and possible solutions for overcoming potential problems. 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. Discuss how the proposed approach compares to alternative approaches, and the comparative advantages, disadvantages, and risks inherent in each.

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

Team Management Plan [Provide a summary of expertise of the proposed team, including any subcontractors/consultants and key personnel who will be executing the work. Identify a principal investigator (PI) for the project. Provide a clear description of the team’s organization including an organization chart that includes, as applicable, the relationship of team members; unique capabilities of team members; task responsibilities 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.

Provide a detailed plan for coordination including explicit guidelines for interaction among collaborators/subcontractors of the proposed project. Include risk management approaches. Describe any formal teaming agreements that are required to execute this project.]

Personnel, Qualifications, and Commitments [List key personnel (no more than one page per person), showing a concise summary of their qualifications, discussion of previous accomplishments, and work in this or closely related research areas. Indicate the level of effort in terms of hours to be expended by each person during each contract year and other (current and proposed) major sources of support for them and/or commitments of their efforts.

DARPA expects all key personnel associated with a proposal to make substantial time commitment to the proposed activity and the proposal will be evaluated accordingly. 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.]

Capabilities [Describe organizational experience in relevant subject area(s), existing intellectual property, or specialized facilities. Discuss any work in closely related research areas and previous accomplishments. Identify other 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.]

Statement of Work (SOW) – 15 Month Period of Performance [Provide a detailed task breakdown, citing specific tasks and their connection to the interim milestones and metrics, as applicable. Do not include proprietary information. For each defined task/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 be performed on campus at a university.

· Identification (by name) of the primary organization (prime contractor, subcontractor(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.]

10. Top-Level Statement of Work (SOW) – 30 Month Period of Performance [Provide a top-level task breakdown, citing notional tasks and their connection to any notional milestones and metrics, as applicable. Do not include proprietary information. It is understood that any detail provided in this section is speculative.]

11. 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.]

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

13. Bibliography (optional) [If desired, include a brief bibliography with links to relevant papers, reports, or resumes. This section is optional, and the linked materials will not be evaluated as part of the proposal review.]