DARPA-BAA-16-22_Attachment_1_Proposal_Template_-_Technical_ _Management_Volume.docx
DOCX document 32 KB Posted
- Attached to
- Improv Federal contract opportunity
- Solicitation number
- DARPA-BAA-16-22
About this file
DARPA-BAA-16-22 Attachment 1 Proposal Template - Technical Management Volume
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| DARPA-BAA-16-22_Attachment_5_Proposal_Template_-_Statement_of_Work-_Amendment_1.pdf | ||
| DARPA-BAA-16-22_Amendment_1.pdf | ||
| DARPA-BAA-16-22_Attachment_3_Proposal_Template_-_Cost_Summary_Spreadsheet.xlsx | XLSX spreadsheet | |
| DARPA-BAA-16-22.pdf | ||
| DARPA-BAA-16-22_Attachment_2_Proposal_Template_-_Cost_Volume.docx | DOCX document | |
| DARPA-BAA-16-22_Attachment_5_Proposal_Template_-_Statement_of_Work.docx | DOCX document | |
| DARPA-BAA-16-22_Attachment_6_Proposal_Template_-_Purchase_Order.pdf | ||
| DARPA-BAA-16-22_Attachment_4_Proposal_Template_-_Administrative_ _National_Policy_Requirements.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DARPA-BAA-16-22 Improv BAA Attachment 1 Technical and Management Volume Template
The Technical and Management Volume must address three independent and sequential project phases: Feasibility Study (Phase 1); Prototype Construction (Phase 2); and Prototype Evaluation (Phase 3).
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.
The Technical and Management Volume must be in .pdf, .odx, .doc, or .docx formats. Submissions must be written in English.
Sections 2-4 of the Technical and Management Volume shall not exceed a maximum of 7 pages. Page limit does not include the Cover Sheet, Table of Contents, Section 1 (Official Transmittal Letter), or Section 5 (Novelty of Proposed Work).
If applicable, add classification markings as described in Section 4.5.3 of the Improv BAA, DARPA-BAA-16-22.
Source Selection Information – See FAR 2.101 and 3.104
DARPA-BAA-16-22 3
<PRIME ORGANIZATION LOGO>
DARPA-BAA-16-22
Technical and Management Volume
Proposal Title
Proposer Organization
| Type of Organization |
| Choose one: Large Business, Small Disadvantaged Business, Other Small Business, HBCU, MI, Other Educational, or Other Nonprofit |
Proposer Reference Number, if any
| Technical Point of Contact (POC) |
| Name: |
Address:
Telephone:
Email:
| Administrative POC |
| Name: |
Address:
Telephone:
Email:
| Security POC |
| Name: |
Address:
Telephone:
Email:
| Identifying number of associated abstract |
| DARPA-16-22-Improv-PA-___ |
Place(s) of Performance
Period(s) of Performance
| Other Team Members (subcontractors and consultants), if any |
| Technical POC Name: |
Organization:
Organization Type:
| Total Proposed Cost |
| Phase 1: $ |
Phase 2: $ Phase 3: $ Total: $
Date Proposal was prepared
Proposal Validity Period (minimum 270 days)
Table of Contents
| 1. | Official Transmittal Letter | 3 |
| 2. | Improv Program Participation | 3 |
| 3. | Goals and Impact | 3 |
| 4. | Technical Plan | 3 |
| 5. | Capabilities/Management Plan | 3 |
| 6. | Novelty of Proposed Work | 3 |
DARPA-BAA-16-22 4
Official Transmittal Letter [Attach the official transmittal letter from the prime proposer organization.]
Improv Program Participation [Complete the following statement.] The proposer acknowledges that participation in the Improv program, whether as a proposer or a performer, does not authorize any violation of local, state, or Federal law: No Yes
Goals and Impact [Describe the purpose of the prototype system or product. Identify the military capability that would be threatened if the new system or product were to be fully realized. If possible, express the nature of the threat quantitatively in scientific or technological terms.]
Technical Plan [Outline and address technical challenges inherent in the approach and proposed 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. Quantitatively describe how the proposed threat effectiveness is expected to vary as a function of prototype operating parameters or characteristics, including environmental effects. Discuss why the overall concept is nonobvious.
Explain why completion of the Feasibility Study phase is critical to understanding this technology.
Explain why completion of the Prototype Construction phase is critical to understanding this technology.
Explain why completion of the Prototype Evaluation phase is critical to understanding this technology.
Provide a detailed list of the major hardware and software components to be acquired (including source, model #, etc.) and a discussion of the major integration tasks and processes.]
Capabilities/Management Plan [Provide a summary of the team’s expertise, including subcontractors and key personnel. Identify a principal investigator for the project, and include a top-level description of the team’s organization including roles and responsibilities.
Provide a clear, detailed description of the team’s organization, including an organization chart that describes, as applicable, the relationship among team members; unique capabilities of team members; task responsibilities of team members; teaming strategy among the team members; and key personnel including the amount of effort to be expended by each person during the project.]
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
File details come from the government source that posted it. Updated .