From pv magazine USA
Duke Energy’s two North Carolina utilities – Duke Energy Carolinas (DEC) and Duke Energy Progress (DEP) – have completed a request for proposals (RFP), via the state’s Competitive Procurement of Renewable Energy (CPRE) program (pdf), that has approved bids of 551 MW of solar power. DEC approved 465 MW while DEP approved 86 MW.
The fourteen winning projects, ranging from 7 MW to the 80 MW maximum size, submitted bids that averaged 3.794¢/kWh and 3.83¢/kWh (below image) for the electricity in 20 year power purchase agreements (PPA). Two of the projects had energy storage.
One project has withdrawn from the RFP after being approved, but was removed from these values. If that project had been included, the DEC region would have had 515 MWac.
The CPRE program has a goal of soliciting 2.6 GW of solar power in the 45 months following January 18, 2018, when the program was instituted.
Eighteen developers submitted 78 proposals (below image) in total between the two utility areas, with ten of the eighteen developers submitting more than one proposal. The total capacity submitted was 2,732.72 MW in total – more than four times the solicited volume.
Four proposals submitted included energy storage, with three of them connecting to the distribution system and one to the transmission system.
The report noted that PPA proposals fees ranged from $500 to $10,000, and that Interconnection Application and Proposal fees totaled $922,710.
The CPRE program requires that new projects be priced below administratively-established avoided costs. The RFP provided avoided cost rates for three pricing periods (below image): summer, non-summer, and off peak, to which all proposals must have bid at or below.
The program scored the projects on a variety of items (below image), with the price of the electricity being 60% of the overall scoring.
One developer noted that Duke Energy themselves submitted, and won, an 80 MW project – but that their proposal was submitted outside of the rule process that all other developers had to consider when submitting. The final RFP notes, “The RFP expressly waived the proposal security requirement for utility self-developed proposals.”
The specific rules were noted in the original RFP requirements (pdf) were that all participants were required to submit proposal security along with tier projects, something that would add up to seven months of time to project development.
Since many of these RFPs are put forward with projects due within a few months, it is not possible to get a project ready for a deal like this within the alloted time. With this, only developers that already have projects pretty far along the time line will have a real chance.
The developer further provided further insights to pv magazine USA:
Duke could have bid a site on which limited site control and interconnection request was only established one week prior to the Tranche 1 bid deadline, and on which it had made zero progress in zoning and permitting as of the performance security posting deadline – because Duke knew it would have 6-7 months longer than other bidders to further develop, de-risk, and diligence the site to determine whether or not it was actually financeable.
This content is protected by copyright and may not be reused. If you want to cooperate with us and would like to reuse some of our content, please contact: email@example.com.
By submitting this form you agree to pv magazine using your data for the purposes of publishing your comment.
Your personal data will only be disclosed or otherwise transmitted to third parties for the purposes of spam filtering or if this is necessary for technical maintenance of the website. Any other transfer to third parties will not take place unless this is justified on the basis of applicable data protection regulations or if pv magazine is legally obliged to do so.
You may revoke this consent at any time with effect for the future, in which case your personal data will be deleted immediately. Otherwise, your data will be deleted if pv magazine has processed your request or the purpose of data storage is fulfilled.
Further information on data privacy can be found in our Data Protection Policy.