60 likes | 81 Views
Emerging Technologies Working Group Discussion: AXRs. Contents Ready or Not, Here They Come ALRs, the Camel’s Nose The Whys and Why Nots Questions for Today. September 24, 2014. I. Ready or Not, Here They Come.
E N D
Emerging Technologies Working GroupDiscussion: AXRs Contents Ready or Not, Here They Come ALRs, the Camel’s Nose The Whys and Why Nots Questions for Today September 24, 2014
I. Ready or Not, Here They Come • We have reasonable expectation that increasing numbers of (r)esources will be installed on distribution feeders. These may be: • PACE financed Co-Gen • 3rd Party Ownership PV • Storage Resources, 4CP Driven • Storage Resources, Resiliency Driven • Hybrid Systems • Building Energy Management Systems
II. ALRs, The Camel’s Nose • If we can have this: • “A Load Resource that is an aggregation of individual metered sites, each of which has less than ten MW of Demand response capability and all of which are located within a single Load Zone.” • Can we have an aggregation of individual metered sites that represent other (r)esource-types, which in aggregation could be (R)esources? • ALRs implemented by NPRR555, NPRR640 and OBD (“Requirements for Aggregate Load Resource Participation in the ERCOT Markets”): • Concerns About: ALR Telemetry Validation
III. The Whys and Why Nots • Why? • If the resources may be in play regardless, it benefits ERCOT operations to get forward guidance of expected deployments by Resources that maintain their COP. • Owners of resources may have a reasonable expectation to have access to the market. • Resources located closer to Loads – within pockets of congestion. • Why not? • Modeling aggregated resources is… problematic. • Reverse flow concerns. • Performance, telemetry concerns. • Market gaming, settlement concerns. • Cost to implement vs value to market concerns.
IV. Questions for Today • Are other markets including distributed resources in the market? (GTM) • Are companies and technologies available that want and can participate in a distributed resource market? (GTM) • Are there efforts underway to address standards for DG interconnection? (NREL) • What are the technical considerations that must be addressed for integrating distributed resources? (EPRI) • What are the technical capabilities of equipment? (ABB) • What else may be driving DG resources to the market? (SERE) • What did we learn from the implementation of ALRs? (Paul)
APPENDICES • ALRs, NPRR 555: • 3.7.1.2(3) Resource Parameters submitted by a Resource Entity must also include, for each of its ALRs, mapping between the ALR and the individually metered Loads, by ESI ID or, in the case of a Non-Opt-In Entity (NOIE), equivalent unique meter identifier, comprising the ALR. • 3.10.7.2(2) Each Resource Entity shall provide ERCOT and TSPs with information describing each of its Aggregate Load Resources (ALRs) as specified in Section 3.7.1.2, Load Resource Parameters, and any additional information and telemetry as required by ERCOT, in accordance with the timelines set forth in Section 3.10.1, Time Line for Network Operations Model Changes. ERCOT shall coordinate the modeling of ALRs with their representatives to ensure consistency between TSP models and ERCOT models. • OBD: “Requirements for Aggregate Load Resource Participation in the ERCOT Markets” • ALRS, NPRR 640: • 3.6.1(4) A QSE representing a Load Resource and submitting a bid to buy for participation in SCED, as described in Section 6.4.3.1, Real-Time Market (RTM) Energy Bids, must represent the Load Serving Entity (LSE) serving the Load of the Load Resource. If the Load Resource is an Aggregate Load Resource (ALR), the QSE must represent the LSE serving the Load of all sites within the ALR. • OBD, “Requirements for Aggregate Load Resource Participation in the ERCOT Markets”: