Addendum C Word Template for proposal.docx

Addendum C - Technical Volume Template Instructions This template has been formatted to fit the requirements of the HelioCon RFP and is meant to serve as a guide to writing your proposal:

The Technical Volume to the Full Application may not be more than 15 pages, including the cover page, project overview, Technical description, innovation and impact, Project work Plan, and Project Team and Resources (including all citations, charts, graphs, maps, photos, or other graphics). All the information is presented in the table below. The Offeror should consider the weighting of each of the evaluation criteria (see Section 10 of the HelioCon RFP) when preparing the Technical Volume.

DELETE ALL INSTRUCTIONS/NOTES IN RED ITALIC FONT

Heliostat Technology Advancement

REQUEST FOR PROPOSALS (RFP) RFP RFX-2024-10000

Technical Volume

Project Title:

Topic Area:

Lead Organization Name and Address:

Team Members:

(list partners participating in the project) <name, Institution, email>

Key Participants:

(list any other collaborating individuals or institutions) <name, Institution, email>

sensitive. Hence, they should not be shared outside of the HelioCon review team.

conceptual design • components • integration • mass production • heliostat field

Technical Volume (Technical Merit 50%, Organization and Execution 30%, Team Capability and Resources 20%)

Project Summary: (Suggested 1 page)

This section should describe the proposed project and its potential to contribute to the RFP goals. Offerors should clearly define the proposed technology/concept, the current state of that technology/concept, the target markets for the technology being developed, and how the proposed technology relates to existing or competing technologies. Offerors should include data or references to support cost and performance claims.

· Background: The Offeror should discuss the background of their organization, including the history, successes, and current research and development status (i.e., the technical baseline) relevant to the technical topic area being addressed.

· Project Goal: The Offeror should explicitly identify the targeted improvements to the baseline technology and the critical success factors in achieving that goal.

Technical Description, Innovation, Impact: (Suggested 5 pages)

· Relevance and Outcomes: The Offeror should provide a detailed description of the technology, including the scientific and other principles and objectives that will be pursued during the project. This section should describe the relevance of the proposed project to the goals and objectives of the RFP, including the potential to meet specific DOE technical targets or other relevant performance targets. The Offeror should clearly specify the expected outcomes of the project, including how results will be made publicly accessible.

· Feasibility: The Offeror should demonstrate the technical feasibility of the proposed technology and capability of achieving the anticipated performance targets, including a description of previous work done and prior results.

· Innovation and Impacts: The Offeror should describe the current state of the art in the applicable field, the specific innovation of the proposed technology, the advantages of proposed technology over current and emerging technologies, and the overall impact on advancing the state of the art/technical baseline if the project is successful. Offerors should clarify how the proposed effort is differentiated from other funded research. Offerors should clearly define the target markets for the technology being developed, and how the proposed technology relates to existing or competing technologies. Offerors should include data or references to support cost and performance claims.

Project Work Plan: (Suggested 5 pages)

· Project Objectives: The Offeror should provide a clear and concise (high-level) statement of the goals and objectives of the project as well as the expected outcomes.

conceptual design • components • integration • mass production • heliostat field

· Technical Scope Summary: The Offeror should provide a summary description of the overall work scope and approach to achieve the objective(s). The overall work scope is to be divided by performance periods that are separated by discrete, approximately annual decision points. The Offeror should describe the specific expected result of each performance period.

· Work Plan: The Workplan should describe the work to be accomplished and how the Offeror will achieve the milestones, will accomplish the final project goal(s), and will produce all deliverables. A milestone is an action or event marking a significant change or state in development. The Workplan is to be structured with a hierarchy of performance period (approximately annual), task and subtasks, which is typical of a standard WBS for any project. The Workplan shall contain a concise description of the specific activities to be conducted over the life of the project. Task descriptions should consist of: A distinct title, description of the activities, Potential risks or barriers and approaches for overcoming them, and Key personnel or resources.

· Milestone Summary: The Offeror should provide a summary of appropriate milestones throughout the project to demonstrate success. A milestone may be either a progress measure (which can be activity based) or a SMART technical milestone. SMART milestones should be Specific, Measurable, Achievable, Relevant, and Timely, and must demonstrate a technical achievement.

· Go/No-Go Decision Points: The Offeror should provide a summary of project-wide Go/No- Go decision points at appropriate points in the Workplan.

· End of Project Goal: The Offeror should provide a summary of the end of project goal(s). At a minimum, each project must have one SMART end of project goal.

Tasks and Deliverables Table

This section should specifically delineate what work each Offeror will perform with delivery dates. The price should reflect the scope of work requested in this RFP.

Team Composition, Coordination, and Capabilities: (Suggested 3 pages)

Teaming Overview: Strong team composition, available resources and capabilities, and effective leadership and coordination are vital components of a successful proposal. Please address the Project Leader and Key Personnel qualifications, including past experience and subject matter expertise. This section should clearly address the relevant evaluation criteria (see Section 10), highlighting the following:

· How this team is uniquely suited to achieve the project objectives

· Description of Offeror team member capabilities including the performance levels of any relevant materials, cells, modules, and equipment that will be available at the start of the project.

conceptual design • components • integration • mass production • heliostat field

· How the Offeror firm will make decisions (i.e., which research areas are most important to pursue, whether any new capabilities are needed, etc.)

· Identification of any non-federal resources that are expected to be leveraged by the consortium in pursuit of its goals (See Non-Federal Resources and Industry Effort below).

If applicable, list lab support requested from X lab. List the capabilities within each lab that this proposal seeks to utilize. Provide a brief rationale of the benefit to the project of the use of these capabilities conceptual design • components • integration • mass production • heliostat field

U.S. Department of Energy HelioCon Heliostat Consortium for Concentrating Solar-Thermal Power conceptual design • components • integration • mass production • heliostat field image1.jpeg image2.jpeg image3.jpeg image4.jpeg