LEXI_BAA Attachment 5_Vol1_Technical and Management.docx

Source Selection Information – See FAR 2.101 and 3.104 HR001120S0056 Lexi Program BAA

Volume 1: Technical and Management Volume Template

Use of this template is required.

This document should be submitted in .pdf, .odx, .doc, or .docx formats. The slides must be in .ppt or .pptx format and should be attached as a separate file to this document.

All pages must be written in Enlgish and 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 full proposals includes all figures, tables, and charts. Margins must be 1-inch on all sides. Copies of all documents submitted must be clearly labeled with the BAA number, proposer organization, and proposal title/proposal short title. 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. Copies of not more than three (3) relevant papers may be included with the submission. The bibliography and attached papers are not included in the page counts given below. The submission of other supporting materials along with the proposals is strongly discouraged and will not be considered for review. The maximum page count for Volume 1 is 40 pages. The official transmittal letter is not included in the page count.

Proposals with fewer than the maximum number of pages will not be penalized.

Official transmittal letter

Proposal Summary Slide

Resumes

References/Bibliography (Optional)

Technical Papers (no more than 3)

Section I

[PRIME ORGANIZATION LOGO]

HR001120S0056 Lexi Volume 1: Technical and Management Volume

Proposal Title

Proposer Organization

Technical Area(s)

Proposer Reference Number, if any

Address:

Telephone:

Email:

Address:

Telephone:

Email:

Place(s) of Performance

Period(s) of Performance

Months

Organization:

Organization Type:

Year 2: $ Year 3: $ Year 4: $ Total: $

Data Universal Numbering System (DUNS) number[endnoteRef:2] [2: The DUNS number is used as the contractor identification code for all Government procurement-related activities. Go to http://fedgov.dnb.com/webform/index.jsp to request a DUNS number (may take at least 1 business day). ]

Taxpayer identification number (TIN)[endnoteRef:3] [3: See https://www.irs.gov/individuals/international-taxpayers/taxpayer-identification-numbers-tin for information on requesting a TIN. Note, requests may take from 1 business day to 1 month depending on the method (online, fax, mail).]

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

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

Name:

Address:

Telephone:

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

Name:

Address:

Telephone:

Date Proposal was Prepared

Proposal Validity Period (minimum 120 days)

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

Executive Summary Slides (attachment 3) [Use the Full Proposal Summary Slide template provided as Attachment 3 to the BAA and the classified addendum for instructions. Include the PowerPoint slides as a separate attachment to this document.]

Section II A. Goals and Impact [Clearly describe what the 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.] B. Technical Plan [See classified addendum.] C. Management Plan [Provide a brief summary of expertise of the team, including subcontractors and key personnel. It is expected that proposals will involve multidisciplinary teams that include expertise from multiple complementary disciplines, for example, biology, biotechnology, chemistry, ecology, materials science, molecular biology, and plant physiology. A Principal Investigator (PI) for the project must be identified, along with a description of the team organization including the breakdown by Technical Area. All teams are strongly encouraged to identify a Project Manager/Integrator to serve as the primary point of contact to communicate with the DARPA Program Manager, IV&V partner, and Contracting Officer’s Representative, coordinate the effort across co-performer, vendor, and subcontractor teams, organize regular performer meetings or discussions, facilitate data sharing, and ensure timely completion of milestones and deliverables. Provide a clear description of the team’s organization including an organization chart that includes, as applicable: the programmatic relationship of team members; the unique capabilities of team members; the task responsibilities of team members, the teaming strategy among the team members; and key personnel with the amount of effort to be expended by each person during each year. Team member descriptions should address the Technical Plan, describe the time and percent effort divisions for members participating across multiple TAs, and delineate individuals to avoid duplication of efforts. Describe any formal teaming agreements that are required to execute this program.] D. Capabilities [Describe organizational experience in relevant subject area(s), existing intellectual property, and any Government-furnished materials or information. Describe any specialized facilities to be used as part of the project, the extent of access to these facilities, and any biological containment, biosafety, and certification requirements. Discuss any work in closely related research areas and previous accomplishments.] E. Statement of Work [The SOW should provide a detailed task breakdown, citing specific tasks for each Technical Area, and their connection to the milestones and program metrics. Each phase of the program should be separately defined, and all tasks/subtasks should be identified by Technical Area. The SOW must not include proprietary information. It is encouraged, though not required, to use the SOW template provided as Attachment 4. SOW is not included in the Volume 1 page count.

For each defined task and subtask, provide:

· A detailed description of the approach to be taken that includes metrics, methods, and an assessment plan.

· Identification of the primary organization responsible for task execution (prime contractor, subcontractor(s), consultant(s), by name).

· Measurable milestone(s), deliverable(s), demonstration(s), or other event/activity signifying 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 all tasks and subtasks within the SOW proposed to be completed at a lower classification level as prescribed by the SCG

· For all tasks and subtasks proposed to be unclassified, proposers will distinguish between work proposed to be Fundamental Research versus work proposed to be CUI. Proposers will provide a short explanation for why each subtask should be categorized as Fundamental Research or CUI. Proposals should be clear and concise to enable the Government to accurately assess program risk.

F. Schedule and Milestones [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.] Section III G. 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 H. Bibliography (Optional) [Provide a brief (no more than 5 pages) bibliography with links to relevant papers, references, reports, etc.]

HR001120S0056 Volume 1 5