1 / 8

OpenADR Taskforce

OpenADR Taskforce. Chair – Albert Chiu Co-chair – Ed Koch Technical Editors – Bruce Bartell, Gerald Gray. OpenADR and NIST Smart Grid Roadmap. What is Demand Response & OpenADR. Demand Response is defined by FERC as:

andren
Download Presentation

OpenADR Taskforce

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OpenADR Taskforce Chair – Albert Chiu Co-chair – Ed Koch Technical Editors – Bruce Bartell, Gerald Gray

  2. OpenADR and NIST Smart Grid Roadmap

  3. What is Demand Response & OpenADR • Demand Response is defined by FERC as: • “…action taken to reduce electricity demand in response to price, monetary incentives, or utility directives so as to maintain reliable electric service or avoid high electricity prices.” • Shift demand from peak to off-peak times • DR Programs are designed to enable customers to shift or reduce demand • OpenADR - Open Automated Demand Response • Originated as Specification: • Open Automated Demand Response Communications Specification (Version 1.0). California Energy Commission, PIER Program. CEC‐500‐2009‐063, 2009.

  4. Importance to the Utility Industry • Importance of Demand Response • Since electrical systems are generally sized to support peak demand “demand response can reduce the need for new electric supply, reduces the need for new transmission and distribution systems, and helps reduce overall electricity prices.” • Importance of OpenADR • OpenADR will provide benefits “by both increasing the number of facilities that participate in demand response, and reducing the cost to conduct frequent and persistent participation in demand response.” • “improve the feasibility of achieving the state’s policy goals of moving toward dynamic pricing, such as critical peak or real time pricing, for all customers.”

  5. Summary of DR Event Message Types • OpenADR • Objectives Based • Demand Reduction or Generation based objectives expressed as absolute, relative kW or enumerators (moderate, high) • Price • Supports relative pricing, relative to tariff (i.e. CPP and TOU) • Market price (Wholesale plus uplift)

  6. OpenADR History • 2002 - Research begun at LBNL Demand Response Research Center (DRRC) into automated DR • 2003 – 2006 Numerous pilots and field trials • 2007 - Present – Commercialization and use of OpenADR in PG&E, SCE, and SDG&E DR programs to automate DR programs with primarily Commercial and Industrial customers. Number of DR programs utilizing OpenADR continues to expand. • Q1/2007 – Standardization effort for OpenADR begins at DRRC with Industry Consortium drafting specification • Q1/2009 – First official draft of OpenADR specification is published by California Energy Commission. Work is donated to UCAIug and OASIS • 2009 – OpenADR taskforce formed within UCAIug • 2009 – Energy Interoperation Technical Committee formed within OASIS • 2009 – NIST develops SmartGrid Roadmap in which OpenADR is identified as one of the original 16 low hanging fruit. • Q3/2009 – NIST forms Priority Action Plan (PAP) 09 for standardizing DR signals. OpenADR taskforce works closely with NAESB to develop requirements for PAP 09 • Q4/2010 – UCAIug OpenADR Task Force contributes OpenADR 1.0 System Requirements Specification and Service Definitions to OASIS Energy Interoperation TC • 2010 – OpenADR Alliance (focus on testing and certification) was formed

  7. UCAIug OpenADR Taskforce Goals OpenADR focuses on DR from an application point of view and specifically on the interactions between the Utility and Facility whereas other groups within UCAIug are more focused on platforms or systems that may support DR applications within their specific domains Work closely with horizontal OpenSG groups. Some overlap with OpenHAN (facility side) and AMI Ent (Utility head end side). Develop requirements and harmonize with CIM efforts Will work with existing standards such as 61850, CIM, and Multispeak which may have DR components Will work with emerging standards organizations such as OASIS, Zigbee/Homeplug (SEP), and NAESB

  8. Status and Next Steps • Task Force completed 1.0 SRS and SD in 2010 • 2011 OpenADR TF focus (Phase 2) • PEV • Fast DR • DER • Security • Expect to complete Phase 2 Business and User Requirements in July 2011

More Related