1 / 10

“OpenADR” “Boot Camp” Overview

“OpenADR” “Boot Camp” Overview. Albert Chiu, Chair, OpenADR TF. Ed Koch, Co-Chair, OpenADR TF. OpenADR History. 2002 - Research begun at LBNL Demand Response Research Center (DRRC) into automated DR 2003 – 2006 Numerous pilots and field trials

bina
Télécharger la présentation

“OpenADR” “Boot Camp” Overview

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”“Boot Camp” Overview Albert Chiu, Chair, OpenADR TF Ed Koch, Co-Chair, OpenADR TF

  2. 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 • 2010 – UCAIug focus on OpenADR SRS and SD

  3. 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

  4. OpenADR TF Tasks to Date • Worked with NAESB on retail DR Requirements for PAP 09. Phase 1 effort currently being voted out of NAESB Executive Committee. • Began work on SRS for DR in Jan within the OpenADR Taskforce • Approaching requirements from Utility enterprise perspective • Using OpenADR as basis and utilizing CIM where applicable • Harmonizing with SEP and Wholesale (NAESB) requirements • Trying to maintain consistency with OASIS EI TC • Utilizing requirements from a number of different efforts – NAESB, EIS alliance, SEP 2.0, EMIX, WS-Calendar • Doing preliminary mappings and comparisons between requirements from different efforts – OpenADR, NAESB (wholesale and retail), SEP • Currently working with other OpenSG groups on DR related issues – Conformance, Security, OpenHAN, OpenADE

  5. OpenADR TF Upcoming Goals and Milestones • Complete SRS by end summer 2010 • UCAIug not an SDO - will feed requirements to NAESB and OASIS EI TC and contribute to their work • Continue to actively engage other organizations • Work with NAESB on phase II data requirements for PAP 09 • Joint meetings with OASIS EI TC • Actively collaborate with IRC (wholesale) • Continue to receive information from SEP 2.0 effort

  6. SRS Scope

  7. Interaction Model

  8. DR Event Model Used for Data Requirements

  9. Example Data Requirements Table

More Related