Design Forward-2

Design Forward-2 publically releasable high level overview slides are available here DF2QuadCharts.pptx (1157k).


Design Forward-2 System Integration Request for Proposals


 

ALL PROPOSALS ARE DUE ON OR BEFORE

July 24, 2014 3:00 PM PDT

(Amendment 1, Issued 7/10/2014)


Interested Offerors are advised to monitor this Web site for potential Design Forward-2 RFP amendments and other Design Forward RFP information updates. LBNL may notify interested Offerors (who have previously contacted LBNL and expressed an interest in the Design Forward RFP) of updated Design Forward RFP information via e-mail; however, LBNL is under no obligation to do so. It is the responsibility of all interested Offerors to monitor this Web site for current Design Forward RFP information.

Interested Offerors must submit all communication (questions, comments, etc.) about the Design Forward RFPs by email to design-forward-rfp@lbl.gov.

The Design Forward-2 RFP, Design Forward-2 System Integration is issued effective June 6, 2014. The RFP letter and applicable attachments are provided as Microsoft Word and Adobe Portable Document Format.

The following list of documents and forms apply to the RFP:

1. DesignForward2 System Integration RFP
2. Statement of Work, June 6, 2014
3. Sample Subcontract
4. General Provisions - Fixed Price Non Commercial
5. DesignForward2 Rep-Cert Form
6. Small Business Subcontracting Plan Model
7. EEO Preaward Compliance Certification

The entire DesignForward RFP package, as issued on June 6, 2014 is contained in a ZIP file.



FREQUENTLY ASKED QUESTIONS


Q1 - We are considering use of third party IP in our proposal. We will have costs involved in licensing the patent rights if we proceed in this direction. We expect to negotiate a one time fixed fee price, not an ongoing royalty as mentioned in the RFP.  How is this best handled in our proposal?  Can we include such costs as part of our expenses? Will the government require rights to such IP?

A1 - Royalties and other costs for use of patents are allowable when necessary for the performance of the sponsored project.  They are unallowable when the Federal Government has a license or the right to free use of the patent or copyright.  We would need information in your proposal about the patent fees so we can make a determination on its total cost and allowability.  When we evaluate proposals, the payment of royalties and/or patent fees will be considered, keeping in mind that Design Forward is a multi Laboratory effort and the fees could become excessive if there is not a DOE-wide right to use the IP.


Q2 - Is the DesignForward-2 open to be public - so I can pass the URL to some (potential) collaborators ?

A2 - The RFP is a publicly available document so you can redistribute the URL.


Q3 - It appears that the RFP is for companies only.  LBL is issuing the RFP representing 7 DOE labs: Argonne, Oak Ridge, PNNL, Livermore, Sandia, LBNL and Los Alamos. Can any of the 7 labs be a proposal partner"

A3 - We are not able to send any Design Forward money to DOE labs.  There would be the appearance of a a conflict of interest if the Labs or their personnel participate in the RFP, since the Labs helped write the RFP. 


Q4- Offerors are expected to leverage the DOE Co-Design Centers to ensure solutions are aligned with DOE needs.  Can you elaborate on how an offeror should assure proper resource is available for such collaboration?  I am thinking about resource/budget dedicated  for joint supervision of Ph.D students and postdoc level researchers between us, universities and DOE co-design center team members.

A4 - Currently, the Design Forward and Fast Forward teams have successfully established collaborations and dialogues with Co-Design Centers, but the Co-Design centers interact with the Design Forward and Fast Forward awardees using their own funding (they do not receive any funding from the Design Forward or Fast Forward awardees).


Q5 - Can a university be the lead organization for a DF-2 proposal ?

A5 - That wasn't our intent but it's not prohibited by the RFP.  Please remember that the RFP requires a specific and complete exascale system design in your response (see SOW A1-2).


Q6 - I read that DOE EPScoR State program at the following site: http://science.energy.gov/bes/epscor/about/
How should we take this into consideration when respond to  the DF-2?

A6 - There is no connection between the DOE EPScoR program and DesignForward-2.


Q7 - Is it a requirement to have a compute solution as a part of a response? 

A7 - Yes. We are looking for development of an integrated system design, including the rationale for the architecture and execution model


Q8 - Can foreign owned entities respond to the designforward-2 RFP? If so, what are the rules regarding intellectual property (IP)? Can a foreign owned entity partner with a non-foreign owned entity for the designforward-2 RFP?  If the non-foreign owned entity is prime on the contract, what are the rules and regulations regarding IP for the foreign owned entity?

A8 - Yes, a foreign owned entity can respond to DesignForward-2.  48 CFR 952.227-13 is the default patent rights clause for subcontracts to foreign companies.  The text of the clause can be found here:

 http://www.gpo.gov/fdsys/pkg/CFR-2006-title48-vol5/pdf/CFR-2006-title48-vol5-sec952-227-13.pdf

The Class Advance Waiver will not apply. The default is US Government ownership of the invention. Note that the foreign company, in accordance with DEAR 952.227-84 Notice of Right to Request Patent Waiver, may request title to their inventions created under the subcontract and DOE will process the request.  Requests for title will require the foreign subcontractor to complete a petition for title and would be handled on case-by-case basis.


Q9 - Can we propose designs that improve our near-term product plans?

A9 - This RFP requires the development of a conceptual design for an exascale system that will be delivered in 2022-2023. We are not interested in simply funding a company's next product design.


Q10 - Please grant a 1 week extension to the proposal receipt date.

A10 - Amendment 1 was issued to extend the proposal due date to July 24, 2014.  The Amendment is attached below.


Q11 - To clarify, is it required that we include both a hardware and software design in the proposal? For example, can we assume a hardware design, providing a high-level, generic description in our proposal, and focus the proposed R&D efforts on addressing Exascale system software?

A11 - An exascale system design must include a hardware design.  Our intent was that software would be discussed in the context of a specific hardware architecture and execution model that is part of an integrated solution in the proposal. We are not seeking software designs in the absence of a hardware design.

ĉ
Lynn Rippe,
Jun 5, 2014, 3:17 PM
Ċ
Lynn Rippe,
Jun 5, 2014, 3:17 PM
ĉ
Lynn Rippe,
Jun 5, 2014, 3:17 PM
Ċ
Lynn Rippe,
Jun 5, 2014, 3:17 PM
Ċ
Lynn Rippe,
Jun 5, 2014, 3:18 PM
ĉ
Lynn Rippe,
Jun 5, 2014, 3:18 PM
Ċ
Lynn Rippe,
Jun 5, 2014, 3:19 PM
ĉ
Lynn Rippe,
Jun 5, 2014, 3:19 PM
Ċ
Lynn Rippe,
Jun 5, 2014, 3:19 PM
ĉ
Lynn Rippe,
Jun 5, 2014, 3:19 PM
Ċ
Lynn Rippe,
Jun 5, 2014, 3:19 PM
Ċ
Lynn Rippe,
Jul 10, 2014, 7:03 PM
ć
Sue Kelly,
Sep 28, 2015, 2:14 PM
ċ
DF2_RFP.zip
(2239k)
Lynn Rippe,
Jun 5, 2014, 3:20 PM
Comments