12.07.2015 Views

2009 Scenario Reliability Assessment - NERC

2009 Scenario Reliability Assessment - NERC

2009 Scenario Reliability Assessment - NERC

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Scenario</strong> <strong>Reliability</strong> Self-<strong>Assessment</strong>sOther) and Conceptual Capacity. This is shown because the <strong>2009</strong> Long-Term <strong>Reliability</strong><strong>Assessment</strong> Reference Case had already shown some of this new renewable capacity beingcommercialized in the near-term (thus shown as Future Capacity (Planned & Other). Thoseequivalent amounts of capacity had to be taken out of the remaining Conceptual Capacity lineitem.One problem pertaining to wind capacity within the associated <strong>NERC</strong> spreadsheets is that whenit is categorized as Conceptual Capacity, only nameplate capacity is used. When that same windcapacity becomes near-term commercial, and is placed into the Future Capacity line item, thenthe specific Future, Planned Wind Expected On-Peak and the Future, Other Wind Derate On-Peak Capacity must be defined using the existing market rules and site-specific windinformation. Unfortunately, this information is not available for the majority of wind projectswithin the ISO-NE Queue, thus the reasoning for using nameplate wind capacity within both theReference and <strong>Scenario</strong> Case Conceptual Capacity line items.Although somewhat confusing, the <strong>Scenario</strong> Case’s new renewable capacity does match upbetween nameplate projections shown here (Table New England 2-1 through Table New England2-4) and the individual capacity components defined within the corresponding <strong>Scenario</strong> Casespreadsheet (as shown in Table New England 2-5 and Table New England 2-6).Page 72<strong>2009</strong> <strong>Scenario</strong> <strong>Reliability</strong> <strong>Assessment</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!