Tag Archives: Amazon

Unknown's avatar

Yay, Dominion is building solar! Just not for you.

by

solar installation public domainThis week’s news of an 18 megawatt solar facility to be installed at Naval Station Oceana in Newport News marks the latest in a string of announcements of new solar projects to be built in Virginia. The Commonwealth had only about 22 megawatts of solar installed as of the end of 2015, but by the end of this year, we should be comfortably into the triple digits. That’s still trivial compared to neighboring North Carolina, which added over 1,000 megawatts last year alone, but it’s grounds for celebration here in the “dark state.”

How is this happening? Customer demand, coupled with falling costs, finally wrought a change of attitude at Dominion Virginia Power. The state’s largest utility dragged its feet on solar for years until announcing, in early 2015, plans to spend $700 million on 400 megawatts of solar power in Virginia by 2020.

The welcome change comes with a caveat: while these new projects will supply solar to important and influential customers like Microsoft, Amazon, and even the state government itself, Dominion offers no programs to supply solar to ordinary Virginians. And indeed, even where ratepayers are footing the bill for projects, our regulators insist that the renewable energy certificates—the right to say it’s solar power—should be sold to someone else.

Dominion’s early adventures in solar were not altogether encouraging. In 2012 the General Assembly authorized the utility to “study” solar by building up to 30 megawatts of distributed (mostly rooftop) projects. The SCC approved $80 million for the “Solar Partnership Program” the following year, with the stipulation that Dominion should sell the renewable energy certificates to reduce the cost to ratepayers. A steep learning curve made for slow and expensive going, and while a number of schools, universities and commercial businesses signed up to host projects, they weren’t permitted to purchase the solar energy being produced right on their property.

In 2013, Dominion created a special tariff “Schedule RG” especially to allow commercial customers to buy renewable energy. Cumbersome, limited and expensive, it never attracted any takers. Dominion spokesman David Botkins suggested to reporters last May the problem was Dominion’s low rates. As in, who wants renewable energy when dirty power is so cheap?

That was one month before Amazon Web Services announced it had contracted for the output of an 80 megawatt solar farm to be built in Accomack County. The project sidestepped Dominion’s limitations by feeding power directly into the Delmarva Power grid in Maryland. Dominion promptly bought the project.

Schedule RG was clearly a failure, but just as clearly, there was money to be made on solar. Dominion just needed to figure out how.

The utility was already trying. In January of 2015 Dominion proposed to build a 20 megawatt solar farm near Remington, Virginia. The State Corporation Commission (SCC) originally rejected Dominion’s proposal, saying the company had not considered third-party alternatives that might be cheaper for ratepayers. (They were proved right when it turned out the Amazon project was slated to deliver power at a cost that was 25% less.)

Dominion didn’t give up on Remington, nor was it willing to turn the project over to a private developer. Instead, it got to work rejiggering the deal into what, this spring, became a public-private partnership. Governor McAuliffe arranged to have the state government, rather than ratepayers, buy the power output from Dominion, while Microsoft agreed to buy the renewable energy certificates (RECs) to meet its corporate commitment to buying renewable energy. (In every solar deal, watch what happens to the RECs.*)

Although I wondered at the time if the state might be taking a financial hit to make the deal work, more recent information suggests the opposite. According to Dominion’s website, “the construction and deployment of this solar asset will lower the cost of the energy purchased by the Commonwealth. The Commonwealth is projected to save $500,000 to $1M in energy costs over the lifetime of the project.”

This tells us two things: one, obviously, we should sell more solar to Microsoft. And two, either the website omits key details about the financing, or the cost of energy produced by solar panels is now pretty darn competitive.

The projects have started coming in more quickly in recent months. In February of this year, Dominion announced it would buy the output of a 20 megawatt solar farm in Chesapeake through a power purchase agreement (PPA) with a North Carolina developer. Other PPAs are said to be under consideration.

Then, on June 30, the SCC gave Dominion approval to move forward on building three new projects totaling 56 megawatts in Powhatan, Louisa, and Isle of Wight counties. The 800 local jobs associated with the projects sparked news stories across the state.

That brings us to this week’s announcement of the deal with the Commonwealth and the Department of the Navy at Oceana. According to Dominion’s press release, Dominion Virginia Power will own and operate the facility, and the Commonwealth will buy the electricity, with Dominion retiring the RECs on the Commonwealth’s behalf.

Deputy Secretary of Commerce Hayes Framme confirmed to me this deal is the first step toward satisfying Governor McAuliffe’s commitment to having the state government get 8% of its power from solar by the time he leaves office, an amount equal to roughly 110 megawatts. That should mean there will be more announcements to come.

The Navy’s role here is especially interesting. Although some news outlets reported the Navy would buy the electricity, this appears to be a misreading of the Navy’s press release. Naval Station Oceana will instead receive “in-kind consideration in the form of electrical infrastructure upgrades” for hosting the project on its land. But the press release dwells mainly on the benefit to the regional grid that serves the naval station:

“Renewable energy projects, like the one at NAS Oceana and others throughout the Mid-Atlantic Region, are win-win-win collaborations. They’re good for the utility companies, good for our installations and good for the communities surrounding our installations,” said Rear Adm. Jack Scorby, Jr., commander, Navy Region Mid-Atlantic. “These projects increase the energy security, energy diversity and energy resiliency of our bases. Energy security, or having assured access to reliable supplies of energy and the ability to protect and deliver sufficient energy to meet mission-essential requirements, is critical to our installations’ roles to support the Fleet.”

The reference to “energy security, energy diversity and energy resiliency” is key here. The Navy will benefit from having a large renewable generation source onsite, one that can be protected from attack and that is not susceptible to fuel supply disruptions.

Come to think of it, “energy security, energy diversity and energy resiliency” are three of the prime reasons we need more solar projects all across the state, and why the benefits shouldn’t be limited to large, influential customers. So yay, Dominion, for getting rolling on all these solar projects! Now please stop blocking the way for the rest of us.

*RECs were invented as a way to identify units of electricity generated by wind, solar and other sources, since the electrons themselves can’t be dyed green. But RECs don’t have to just follow electrons around; they can also be bought and sold separately from the underlying electricity. When the RECs associated with a solar project are sold separately (in the case of the Remington solar project, to Microsoft), the electricity loses its green quality, and the buyer (in this case, the Commonwealth) can’t claim to be buying solar energy. For a fuller explanation of RECs, see this earlier post on the subject.

Unknown's avatar

Dominion makes a play for utility-scale solar, but Amazon steals the show

by

As_solar_firmengebaude.Christoffer.ReimerThis winter Dominion Virginia Power promised Governor Terry McAuliffe it would build 400-500 megawatts (MW) of utility-scale solar power in Virginia by 2020, part of the deal it cut to gain the governor’s support for a bill shielding it from rate reviews through the end of the decade. The company also took a welcome first step by announcing a proposed 20-MW solar farm near Remington, Virginia.

The applause had hardly died down, though, when Amazon Web Services announced it would be building a solar project in Accomack County, Virginia, that will be four times the size of Dominion’s, at a per-megawatt cost that’s 25% less.

Why such a big difference in cost? The way Dominion chose to structure the Remington project, building and owning it directly, makes it cost more than it would if a third party developed the project, as will be he case for the Accomack project. That means Dominion is leaving money on the table—ratepayers’ money.

There is nothing wrong with the Remington project otherwise. The site seems to be good, local leaders are happy, and solar as a technology has now reached the point where it makes sense both economically and as a complement to Dominion’s other generation. But by insisting on building the project itself, and incurring unnecessary costs, Dominion risks having the State Corporation Commission (SCC) reject what would otherwise be a great first step into solar.

And that’s a crying shame, because solar really is a great deal for consumers these days. Utilities now regularly sign contracts to buy solar for between 4.5 and 7.5 cents per kilowatt-hour. Compare that to the 9.3 cents/kWh cost of electricity produced by Dominion’s newest coal plant in Virginia City, and it’s no wonder that solar is the fastest growing energy source in the country.

Utilities get those rates by buying solar energy from solar developers, not by playing developer themselves. From the ratepayer’s point of view, developers have three advantages over utilities: they are experts at what they’re doing, they work on slimmer profit margins, and they get better tax treatment. Dominion loses all three advantages if it builds the Remington solar farm itself.

Dominion has already demonstrated its lack of solar knowhow. In a May 7, 2015 filing with the SCC (case PUE-2011-0017), it admitted its “Solar Partnership Program,” which puts solar on commercial rooftops, is a year behind schedule and will total less than 20 MW of the 30 MW legislators wanted. Previously the company had told stakeholders it would likely hit its $80 million budget limit with only 13-14 MW installed.

As for profit margins, Dominion gets a guaranteed 10% return on its investments. This explains its desire to build solar itself, but it’s hard to justify charging ratepayers a 10% premium when there are cheaper alternatives courtesy of the free market. Unlike Dominion, solar developers have to compete against each other, so they accept much slimmer profit margins.

And then there are the tax implications. A third-party developer can claim the federal 30% tax credit immediately, and can take accelerated depreciation on the cost of the facility over five years. A utility has to take both the tax credit and the depreciation over the expected life of the facility, 20 years or more.

These three factors—knowhow, free-market cost competition, and tax implications—add up to huge savings for consumers when a project is put out to bid by third-party developers.

Just how big the savings could be is clear from a comparison of Dominion’s solar farm with Amazon’s project, to be built by a third-party developer. Dominion says Remington will cost $47 million for 20 MW, or $2.35 million/MW. Amazon’s project is reported to cost $150 million for 80 MW, or $1.875 million/MW. That is a difference of about 25%.

Obviously, then, the better way to finance Remington is for Dominion to put the project out for competitive bid among solar developers. Dominion won’t make as much money for its shareholders, but it will save money for ratepayers. And really, as a member of the American Legislative Exchange Council (ALEC), Dominion ought to jump at the chance to live up to ALEC’s “free markets” mantra.

More to the point, keeping costs down this way will make it possible for the project to get SCC approval, opening the way to many more like it. With hundreds of megawatts still to go, Dominion needs to show it can do solar right.

In fact, Dominion should put out a request for proposals for the full 400 MW it says it plans to build. This could include revisiting its refusal to buy power from another proposed solar farm that went nowhere. That solar facility in Clarke County, proposed by OCI Solar Power six months ago, would have added another 20 MW to the grid. With only a year and a half to go before the 30% federal tax credit drops to 10%, Virginia ratepayers have a right to expect many more solar farms, and soon.

Frustration over Dominion’s slow pace is widespread among solar advocates. Cale Jaffe, Director of the Southern Environmental Law Center’s Virginia office, noted, “Last General Assembly session, Dominion committed to building 400 megawatts of utility-scale solar projects in Virginia by 2020.  The General Assembly then passed, at Dominion’s urging, legislation declaring up to 500 megawatts of new solar projects to be in the public interest. But, unfortunately, Dominion appears to be getting out of the blocks very slowly when it comes to solar power.  I’m concerned that the company is not currently on pace to live up to its pledge.” SELC has intervened in the Remington case on behalf of environmental groups Appalachian Voices and Chesapeake Climate Action Network.

Of course, we also need solar from all sources, not just our utilities. Homeowners, small businesses, nonprofits, and big industrial customers—all should be encouraged to build solar as a matter of the public interest. Solar diversifies our energy base, creates local jobs, strengthens the electricity grid, and will help Virginia meet the EPA’s Clean Power Plan.

Even 500 MW of solar pales compared to the 4,300 MW of new natural gas plants Dominion expects to have built by 2020. When you adjust for capacity factors, in 2020 solar will make up less than five percent of Dominion’s power generation from new projects, and barely a blip on the radar screen of total generation.

While sad, this is hardly news. Virginia famously lags behind neighboring states in developing solar resources. Maryland had 242 MW of solar installed at the end of 2014 and expects to meet its goal of 1,250 MW by the end of 2015. North Carolina has over 1,000 MW and counting. The same source puts Virginia at a grand total of 14 MW.

(In fairness I think our total has to be a little better than that, but when your state’s total looks like some other state’s rounding error, who really stops to crunch the numbers?)

Getting serious about solar means opening our market to competition. Attracting more projects like Amazon’s will require the General Assembly to pass legislation removing all barriers to third-party power purchase agreements. Amazon’s solar farm has the advantage of being located on the Maryland border. It will feed into power lines owned by Delmarva Power, and then into the PJM transmission grid serving the multistate region that includes Virginia. It will not serve Amazon’s data centers in Virginia directly, but will simply offset their power demand. If Amazon or anyone else wanted to put in a similar solar farm elsewhere in Virginia, they would run into restrictions on third-party power purchase agreements and the absurd terms and conditions imposed by our utilities even on large corporate customers.

Tearing down the barriers that prevent the private market from building solar is critical to closing this gap. Dominion made a half-hearted effort to serve big customers, in the form of its cumbersome “RG tariff.” The fact that no one has used it, and Amazon has done an end-run around it, proves how worthless it is. Virginia should put an end to utility red tape, open the market to competition, and let the sunshine in.

The State Corporation Commission will hear arguments on the Remington proposal starting at 10 a.m. on July 16, 2015 at its offices in Richmond. The case is PUE-2015-00006.