Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF DECEMBER 13, 2008 FBO #2574
SOLICITATION NOTICE

A -- BAA 09-03 Machine Reading

Notice Date
12/11/2008
 
Notice Type
Modification/Amendment
 
NAICS
541712 — Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology)
 
Contracting Office
Other Defense Agencies, Defense Advanced Research Projects Agency, Contracts Management Office, 3701 North Fairfax Drive, Arlington, Virginia, 22203-1714
 
ZIP Code
22203-1714
 
Solicitation Number
DARPA-BAA-09-03
 
Response Due
1/16/2009 12:00:00 PM
 
Archive Date
11/13/2009
 
Point of Contact
IPTO BAA Coordinator, Phone: XXXXXXXXXX
 
E-Mail Address
see_admin_address@announcement.mil
 
Small Business Set-Aside
N/A
 
Description
<!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--> <!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--> <!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> Description: The purpose of this modification is to make the following changes under Section IV.B.2. Proposal Preparation and Format. 1. Paragraph 1.8 is replaced in its entirety as follows: 1.8 Technical Approach {15 pages} Provide a detailed description of the technical approach for the complete program. When addressing aspects of the technical approach that evolve over the course of the program, Phase 1 must be addressed separately from the rest of the phases. There are no restrictions on page allocations between subsections. This section will elaborate on many of the topics identified in the proposal roadmap and will serve as the primary expression of the offerors’ scientific and technical ideas. A one paragraph executive-style summary must be provided for each proposal subsection. The following subsections must be included within this section of the proposal but it is not limited to these items: Problem Description. Provide a concise description of the problem areas addressed specific to your approach. Research goals. Identify specific research goals. Goals should address the technical challenges of the effort. Expected impact. Describe the expected impact of your research Approach to be taken in the program. Justify ability to pass Go/No-Go evaluation criteria requirements for specified metrics for each phase. Possibilities might include: <!--[if !supportLists]--> · <!--[endif]-->A summary to enumerate, prioritize, and quantify key risks <!--[if !supportLists]--> · <!--[endif]-->Approaches to mitigate these risks <!--[if !supportLists]--> · <!--[endif]-->Checkpoint milestones to assess progress <!--[if !supportLists]--> · <!--[endif]-->Other monitoring or programmatic solutions 2. Paragraph 1.14 Personnel, Qualifications and Commitments. The page limit is amended to add, {No More than Three Pages for Offeror’s Prior Experience}. 3. Paragraph 1.14 Personnel, Qualifications and Commitments. The following sentence is added, “Discuss offeror’s prior experience, accomplishments, and work in this or closely related research areas.” 4. Paragraph 1.15 is replaced in its entirety as follows: 1.15 Cost Summaries {no page limit}. This section shall contain two tables, each of which should assume a May 31, 2009 start date for costing purposes. The first table must summarize the proposed costs, but break them down by project task and phase, i.e., show the costs of each project task for each phase, with the task labels on the y-axis and the program phases on the x-axis. It may be appropriate to create a subtotal under some closely related tasks. Table entries should contain the dollar figure and a percentage that specifies the percentage of that phase’s total costs that are allocated to said task. The second table should show the costs broken down by prime/subcontractor and by phase, i.e., the labels of the prime/subcontractors should be on the y-axis and the five phases on the x-axis. Table entries should contain the dollar figure and a percentage that specifies the percentage of that phase’s total costs allocated to said prime or subcontractor. Offerors should format their proposals for Phase 1, with subsequent phases (e.g., Phase 2, 3, 4, 5) priced as options. 5. Paragraph 2.2 Detailed Cost Breakdown. The first sentence of paragraph one is amended to add, “Assume a May 31, 2009 start date.”
 
Web Link
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=f980c8c096fcdc6d117ae6cc340dc7c1&tab=core&_cview=1)
 
Record
SN01717422-W 20081213/081211215920-f980c8c096fcdc6d117ae6cc340dc7c1 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.