Enabling The Standard for

Automated Demand Response

OpenADR 2.0 Overview

Fremont, September 3, 2014

Understanding OpenADR

Open Automated Demand

Response (OpenADR) provides a

non-proprietary, open

standardized DR interface that

allows electricity providers to

communicate DR signals directly

to existing customers using a

common language and existing

communications such as the

Internet.

2

Source: LBNL

OpenADR Progression

3

2002 to 2006 2007 2008 2009 2010 2011 2012 2013 2014

Research initiated by LBNL/ CEC

Pilots and field trials Developments, tests (Utilities)

OpenADR 1.0 Commercialization (PG&E, SCE, and SDG&E)

Official OpenADR specification (v1.0) by LBNL/CEC*

1. OpenADR Standards Development - OASIS (EI TC), UCA, IEC

2. NIST Smart Grid, PAP 09

1. DR 2.0 Pilots and field trials - Wholesale markets, ancillary services - Dynamic pricing, renewable, EVs - International demonstrations

2. All end-uses and sectors

1. Foster Adoption 2. Test/Certify (v2.0)

* OpenADR v1.0: http://openadr.lbl.gov/ ** OASIS EI 1.0 standards: http://www.oasis-open.org/committees/download.php/45425/energyinterop-v1.0-cs01.zip *** Publication: http://drrc.lbl.gov/sites/drrc.lbl.gov/files/LBNL-5273E.pdf

Standards Interoperability Lifecycle Process: An iterative development process for a standard to be deployed In markets.*** 1. Research and development 2. Pilots and field trials 3. Interoperability standards development 4. Deployment and market facilitation

EI 1.0 standards - OpenADR profiles**

1. OpenADR 2.0 specifications - International standards (IEC) - OpenADR 2.0 products/deployments.

2. USGBC national pilots 3. Codes (CA T24)

OpenADR Mission

The mission of the OpenADR Alliance is to foster

global development, adoption, and

compliance of Open Automated Demand

Response (OpenADR) standards through

collaboration, education, testing, and

certification.

OpenADR Alliance Overview

100+ member organization

comprised of key industry

stakeholders

Fosters global development,

adoption, and compliance

of OpenADR standards

through collaboration,

education, testing, and

certification.

Leverages Smart Grid-related

standards efforts from SGIP,

OASIS, UCAIug and NAESB

Enables stakeholders to

participate in automated DR,

dynamic pricing, and

electricity grid reliability

Member Growth

0 20 40 60 80 100 120

Sponsor

Contributor

Adopter

Individual

Total Members

OpenADR Members by Country

Canada, 5 France , 3

Hong Kong, 1

Japan, 12

Korea , 8

Netherlands, 2

Norway, 1

Taiwan, 3

USA, 79

OpenADR 2.0

Terminology

Server entity is a Virtual Top Node (VTN)

Client entity is a Virtual End Node (VEN)

Systems can be VTNs, VENs, or combinations

thereof

VTN

VTN/VEN

VEN VEN

VEN

Information Interoperability

Client Logic

OpenADR Service Provider

Secure Internet

A

C

D

C

E

ESI = Energy Services Interface

A = OpenADR

B = Proprietary

C = Residential Load Control (SEP, EchoNET, OpenADR, etc.)

D/E = Commercial/Industrial Load Control (LonWorks, BACnet, etc.)

A and/or B

Third-Party Cloud

Service

Provider

PCT

OpenADR

Enabled

Devices

EV

Charger

E

S

I

HAN

BMS

EMCS

Energy Usage Data

Analytics, Visualization

RTU

9

A

OpenADR 2.0 Profiles

Energy Interoperation 1.0

B Profile

EiEvent

EiOpt

EiReport

EiRegistrerParty

A Profile

Simple EiEvent

• “A” profile is targeted at

limited resource devices

and simple DR applications

• “B” profile is targeted at

robust devices and

sophisticated DR

applications

Excerpted from QualityLogic’s OpenADR Training Workshop © QualityLogic

Profile Architecture

11

Transport Protocols 1. Simple HTTP: Using standard http

command. Ideal for pull clients, possible for push but firewall issues need to be taken into account

2. XMPP: Used in messengers and many other social communication tools. Excels for push applications and fast DR. Pull also possible

Simple HTTP or XMPP for VEN, both mandatory for VTN

Profile Architecture

12

Security 1. Standard Security: TLS with server

and client side certificates

2. High Security: Standard Security + XML signatures to increase non-repudiation

Standard Security mandatory, High Security optional

OpenADR Alliance has their own root certificates

Services

Web Service like logical request-response

services

Event Service – Send and Acknowledge DR Events

Opt Service – Define temporary availability schedules

Report Service – Request and deliver reports

RegisterParty Service – VEN Registration, device

information exchange

XML Payloads – Root element defines service

operation

Excerpted from QualityLogic’s OpenADR Training Workshop © QualityLogic

Certification & Testing

Alliance created

Profile Specification

PICS documents

Test plan and testing

Certification documents

Certification test tool

Test tool built by QualityLogic

Third party testing performed by Intertek

Members can obtain test tool for pretesting and do final certification testing at the test lab

2.0a/b Certified Products (examples)

Virtual Top Nodes (VTNs)

DROMS (Demand

Response Optimization

and Management System)

Demand Response

Automation Server (DRAS)

Energy Interop Server &

System (EISS)

SaVE (Smart and Valid

Energy) server

Virtual End Nodes (VENs)

ControlScope

Mercury DRMS

Site Server

Enlighted Demand

Response

EISSBox

Smart Community

Platform

Swarm Energy

Management

ISY99i Z Series

Vertex

http://www.openadr.org/certified-products

Now 58 certified systems!

OpenADR in the IEC

The OpenADR Alliance has been active in

several IEC working groups

IEC PC118 recently published the OpenADR

2.0b Profile Specification as IEC/PAS 62746-

10-1

IEC PC118 and TC57 WG 21 are working on

adapting OpenADR into the CIM framework

IEC TC65 WG17 (Industrial Automation) is

leaning on OpenADR 2.0 functionality

OpenADR in the IEC

OpenADR in Korea

Korea is ready to form Korean OpenADR Alliance Affiliate

(OpenADR Korea)

Organized by Korean Smart Grid Association

Korean companies can join locally

Membership fees are split between Affiliate and OADR

Alliance

Affiliate will have local activities and own board of

directors

Technical and Marketing activities to be discussed

Certification testing will become available locally

Japanese Market

Proposal to form OpenADR Japan on the table

Several demo projects on the way organized by TEPCO, METI, Waseda University

Title 24 and OpenADR

Title 24 of the California Code of Regulations, known as

the California Building Standards Code

Demand Response Signal is a signal sent by the local utility, Independent System Operator (ISO), or

designated curtailment service provider or aggregator,

to a customer, indicating a price or a request to modify

electricity consumption, for a limited time period.

Demand responsive controls and equipment must be

capable of receiving and automatically responding to

at least one standards based messaging protocol which

enables demand response after receiving a demand

response signal.

Impacts all new constructed and retrofitted non-

residential buildings over 10,000 sq.ft.

Applies to energy management systems, HVAC systems,

lighting control and smart thermostats

All three California Investor Owned Utilities (IOUs) are

using OpenADR for their autoDR programs

Key Milestones

Q4 - 2013

First OpenADR 2.0b certified products

Japan test events

Discussions with Korea Smart Grid Association

Over 4000 downloads of OpenADR specs

Q1/2/3 – 2014

Begin work on Demand Response Program Implementation

Guidelines

Passed 58 Certified Products

Successful trial in Japan

Korean Chapter in discussions

IEC PAS published by PC 118 – ICE PAS 62746-10-1

EPRI Open Source Software stack released

Multiple new projects in Europe and US

2014/15 OpenADR Work Items

VTN (Utility,

Aggregator, DR

Operator)

(ISO or Utility)

VEN

(C&I, SMB,

Residental)

Currently OpenADR 2.0 defines the

communications interface

• No specific DR Program Definitions &

Restrictions

• Very flexible

• Many Implementers (VTN & VEN) seek

more Guidance and Harmonization

Implementation Working Group started work

to expand the domain of the protocol

• Define common DR program goals and

objectives

• Reduce the complexity by defining

common OpenADR-based DR programs

• Create a decision tree for implementers

to select the relevant program to support

• Create testable DR program templates

OpenADR DR Parameters

Grid Reliability & Safety (Primary Objective)

Frequency and Voltage Stability

Resource Adequacy

Peak Capacity

Ramping

Contingency

Peak Shaving

Load Following

Frequency Regulation

Reserves

Asset Protection

Transactive (Incentivize)

System Load Requests

Indirect Automation

Control Physical Devices

Different Customer segments (C&I, …)

Example of

Decision Tree

Secondary Objectives

Load Profile Objectives

Interaction Pattern

OpenADR DR Parameters

Additional Primary & Secondary Objectives

Procurement of Energy

Spot Market Prices

Price Arbitrage

Asset Management

Damage Prevention

Maintenance Reduction

Lifetime Extension

Capacity Management

Economic Benefits

Emergency Management

Environmental

Negawatt

Clean Energy

Current Work Items

Collect existing and planned DR Program

information

Review existing DR Program description

Filter program parameters to establish common

criteria

Define OpenADR 2.0 DR Profiles (not a new

Profile specification)

Vendor Guide document

Rolf Bienert

Technical Director

rolf@openadr.org

+1 925 336 0239

www.openadr.org

Thank You!

Q&A