OpenADR Phase 2 Business and User Requirements r1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Phase: Created: Last Update: Print Date: By: Distrib&ti'n: 2.00 March 29, 2011 September 6, 2011 S !
Systems "pen#D$ %eam P&b(ic
OpenADR Business and User Requirements Document

(Phase 2)
)2.00, *+11+201,
1
- C'pyri.ht 2011, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed
24Acknowledgements 25 26The following individuals and their companies have contri uted and!or provided support to the 27wor" of the #pen$%& 'usiness and (ser &e)uirements *pecification+ 28
29'ruce 'artell, -tensi le *olutions 30.arl 'esaw, *outhern .alifornia /dison 31$l ert .hui, 0acific 1as 2 /lectric 321erald 1ra3, 1uiding 0rinciple .onsulting, 4nc 33/d 5och, $"uacom 346arco 1ra7iano, 8isi le /nerg3 359ohn :unnele3, 1ridata 361rish 1hati"ar, ;awrence 'er"ele3 :ational ;a orator3 37Tom 6ar"ham, <onewell 38$nne <endr3, <endr3 2 $ssociates 399onathan 'urrows, 0acific 1as 2 /lectric 409ohn 6ani, .omverge 416i"e .oop, Thin"*mart1rid 42%evon =alton,1ridata 431ale <orst, /lectric 0ower &esearch 4nstitute >/0&4? 446ar" &ussell 45$nno *cholten, .one@@ /nerg3 46Aarro"h $l u3eh, #$T4 47*a3a"a 4noue, /neleap 48*ila 5iliccote, ;awrence 'er"ele3 :ational ;a orator3 49%arren <ighfill, *outhern .alifornia /dison 509oshua 6c%onald, *outhern .alifornia /dison 51&olf 'ienert, #pen$%& $lliance 52.hristopher 5otting, 5ottage 4ndustries
53 54The #pen*1 #pen$%& Tas" Aorce wishes to than" all of the a oveBmentioned individuals and 55their companies for their support of this important endeavor, as it sets a "e3 foundation for the 56interopera le *mart 1rid of the futureC 58
)2.00, *+11+201,
2
59 60
Document History
Revision History
Revision Date Revision By 03/29/2011 Bruce Bartell 0*/17/2011 +erald +ray 0*/17/2011 Bruce Bartell */20/2011 +erald +ray */2*/2011 +erald +ray */25/2011 +erald +ray 0*/31/2011 Bruce Bartell 1/2/2011 1/3/2011 1/1/2011 1/20/2011 1/21/2011 Bruce Bartell Bruce Bartell Bruce Bartell Bruce Bartell Bruce Bartell Summary of Changes Initial draft shell! "ased on #$en%D& 'e(. %dded ,&- .se /ases in 0ection 1 %dded D&' .se /ase stu"s in 0ection 1 %dded u$dated se(uence dia2ra3s for ,&.1 .$dated use cases ,&- .2 and .3 4ith ver"ia2e, activity dia2ra3s, and re(uire3ents .$dated use case ,&- .* %dded so3e stuff to D+ ./16 still needs activity dia2ra3. %dded so3e detail to D+ section %dded %ctivity dia2ra3s to D+ section %dded 7erry8s .se /ase dia2ra3 to D+ ./7 %dded 9astD' $atterns. %dded .se /ase definitions for 9astD'. .$dated 0co$e and 'e(uire3ents to reflect 9astD' and 0ecurity. /onsolidatin2 ,&- use cases $er #$en0+ -ancouver feed"ac: %dded consolidated use case for D+ $er -ancouver feed"ac:. %dded fi2ure footers and inde; for fi2ures. /han2es line count to docu3ent Baselined <acce$ted all chan2es= Minor corrections, e.2. re3oved unnecessary ca$tions %dded so3e co. na3es to ac:no4led2e3ents, u$dated so3e ca$tions. Did acce$t chan2es. %dded ,&- "usiness re(uire3ents for authentication, dischar2e, and o$ti3al ener2y char2in2 %dded narrative and fi2ure to illustrate ,&co33unication assu3$tions /orrected ?eader Modified D+ %dvertise use case to $ut other Changes marked ) ) ) ) ) ) ) ) ) ) ) )
61Date of this revision: May 17, 2011 62

Revision Number 0.0 0.0 0.2 0.2* 0.3 0.31 .031 .031 .031 .031 .1 .1
.2 .2
7/22/2011 +erald +ray 5/1/2011 Bruce Bartell
) )
.3 .31 .31 .> .>*
5/3/2011 +erald +ray 5/*/2011 +erald +ray 5/5/2011 Bruce Bartell 5/9/2011 Bruce Bartell 5/11/2011 +erald +ray
) ) ) ) )
.* .* 1.0
5/23/2011 +erald +ray 5/23/2011 Bruce Bartell 9/1/2011 Bruce Bartell
) ) )
)2.00, *+11+201,
3
3ar:et interactions out of sco$e. Did acce$t chan2es and deleted co33ents.
)2.00, *+11+201,
4
UC#0&. "penS S !Systems

5
"pen#D$ B&siness and User $e1&irements D'c&ment
63
64
Table of Contents
REVISION HISTORY..................................................................................................................................... 3 1.1 INTRODUCTION TO AUTOMATED DEMAND RESPONSE.............................................................................1 1.2 PURPOSE OF DOCUMENT...................................................................................................................... 1 1.3 TERMS AND DEFINITIONS...................................................................................................................... 2 1.4 REFERENCES....................................................................................................................................... 3 2.1 BACKGROUND...................................................................................................................................... 4 2.2 OPPORTUNITY...................................................................................................................................... 4 2.3 OBJECTIVES ........................................................................................................................................ 5 2.4 RISKS.................................................................................................................................................. 5 2.5 SPECIFIC BUSINESS REQUIREMENTS..................................................................................................... 5 3.1 PROJECT VISION STATEMENT............................................................................................................... 7 3.2 MAJOR FEATURES................................................................................................................................ 7 3.3 ASSUMPTIONS AND DEPENDENCIES....................................................................................................... 8 4.1 SCOPE OF INITIA RE EASE.................................................................................................................. 8 4.2 SCOPE OF OPENADR PHASE 2 ........................................................................................................... 8 4.3 IMITATIONS AND E!C USIONS.............................................................................................................. " 5.1 STAKEHO PROFI
ES...................................................................................................................... "
65DOCUMENT HISTORY............................................................................................................................... 3 66 68 69 70 71 73 74 75 76 77 79 80 81 83 84 85 87 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 671.0 INTRODUCTION................................................................................................................................... 1
722.0 OPENADR BUSINESS RATIONALE.................................................................................................... 4
783.0 OPENADR VISION................................................................................................................................ 7
824.0 OPENADR SCOPE............................................................................................................................... 8
865.0 OPENADR CONTEXT........................................................................................................................... 9

DER
886.0 OPENADR USE CASES..................................................................................................................... 10
#.1 OPENADR USE CASES FOR PEV................................................................................................... 13 #.1.1 PEV $ CONSO IDATED ENRO MENT USE CASE..............................................................................15 #.2 OPENADR USE CASES FOR DISTRIBUTED GENERATION..................................................................18 #.2.1 DG $ OCA GENERATION............................................................................................................... 1" #.2.2 DG $ CHARGE STORAGE................................................................................................................. 2% #.2.3 DG $ DISCHARGE ENERGY STORED DURING PEAK DEMANDS.............................................................21 #.2.4 DG $ CURTAI STORAGE CHARGING................................................................................................ 22 #.2.5 DG $ COMPENSATE FOR VARIAB E DER......................................................................................... 23 #.2.# DG $ ADVERTISE DER CAPABI ITIES............................................................................................... 24 #.2.7 DG $ IS ANDING............................................................................................................................. 2# #.2.8 DG $ PROVIDE REGU ATION SERVICES............................................................................................. 27 #.3 OPENADR USE CASES FOR FASTDR............................................................................................. 2" #.3.1 FASTDR $ ASYNCHRONOUS DISPATCH............................................................................................2" #.3.2 FASTDR $ ASYNCHRONOUS DISPATCH &ITH COMMUNICATIONS HIERARCHY......................................3% #.3.3 FASTDR $ ASYNCHRONOUS DISPATCH &ITH OAD AGGREGATION....................................................31 #.3.4 FASTDR $ PO ED DISPATCH $ T&O PARTY....................................................................................32 #.3.4 FASTDR $ PO ED DISPATCH &ITH COMMUNICATIONS HIERARCHY 'PU (........................................33 #.3.5 FASTDR $ PO ED DISPATCH &ITH OAD AGGREGATION 'PU AT END POINT ON Y(.......................34 #.3.# FASTDR $ PO ED DISPATCH &ITH OAD AGGREGATION 'PU AT EACH EVE (..............................3# #.3.7 FASTDR $ TE EMETRY.................................................................................................................... 37 #.3.8FASTDR $ TE EMETRY &ITH COMMUNICATIONS HIERARCHY..............................................................38
/1.00, 29 "ct'ber 2009

6

7

OAD
110 111
#.3." FASTDR $ TE
EMETRY &ITH
AGGREGATION............................................................................3"
112 113
ist of !i"ures
114 I!URE 1 " DR USE CASES OVERVIE#............................................................................................... 11 115 I!URE 2 ADMINISTRATE DR RESOURCE........................................................................................... 12 116 I!URE 3 $ EXECUTE DR EVENT........................................................................................................... 13 117 I!URE 4 % SAE PEV USE CASES& RELATIONSHIPS& AND DEPENDENCIES. SOURCE% SAE 118'2836( VEHICLE USE CASE TAS) ORCE.........................................................................................14 119 I!URE 5 % HI!H LEVEL CONCEPTUAL MODEL O PEV TO ESI TO UTILITY * THIRD PARTY 120COMMUNICATION.................................................................................................................................... 15 121 I!URE 6 % CUSTOMER ENROLLS A PEV IN A DEMAND RESPONSE RELATED PRO!RAMM 122EITHER THROU!H A UTILITY OR ESCO...............................................................................................16 123 I!URE 7 " UC 1$4 D! CONSOLIDATED PROCESS.............................................................................18 124 I!URE 8 " D!1 LOCAL !ENERATION.................................................................................................20 125 I!URE 9 " D!2 CHAR!E STORA!E.................................................................................................... 21 126 I!URE 10 " D!3 DISCHAR!E STORA!E............................................................................................22 127 I!URE 11 " D!4 CURTAIL STORA!E CHAR!IN!.............................................................................23 128 I!URE 12 " D!5 COMPENSATE OR VARIABLE DER......................................................................24 129 I!URE 13 " D!6 ADVERTISE DER CAPABILITIES.............................................................................26 130 I!URE 14 " D!7 ISLANDIN!................................................................................................................ 27 131 I!URE 15 " D!8 PROVIDE RE!ULATION SERVICES........................................................................28 132 I!URE 16 " AST DR INTERACTIONS................................................................................................. 29 133 I!URE 17 " AST DR ASYNCHRONOUS DISPATCH +T#O PARTY,.................................................30 134 I!URE 18 " AST DR ASYNCHRONOUS DISPATCH +#ITH COMMUNICATIONS HIERARCHY,.....31 135 I!URE 19 " AST DR ASYNCHRONOUS DISPATCH +#ITH LOAD A!!RE!ATION,......................32 136 I!URE 20 " AST DR POLLED DISPATCH +T#O PARTY,.................................................................33 137 I!URE 21 " AST DR POLLED DISPATCH +#ITH COMMUNICATIONS HIERARCHY,.....................34 138 I!URE 22 " AST DR POLLED DISPATCH +#ITH LOAD A!!RE!ATION,......................................35 139 I!URE 23 " AST DR POLLED DISPATCH +#ITH LOAD A!!RE!ATION PULL AT EACH LEVEL, 140................................................................................................................................................................... 37 141 I!URE 24 " AST DR TELEMETRY...................................................................................................... 38 142 I!URE 25 " AST DR TELEMETRY ..................................................................................................... 39 143 I!URE 26 " AST DR TELEMETRY +#ITH LOAD A!!RE!ATION,...................................................40
144
/1.00, 29 "ct'ber 2009

8
ii

9
145#$% &'TRODUCT&O' 146#$# &ntroduction to Automated Demand Response 147The #pen *mart 1rid #pen $utomated %emand &esponse >#pen$%&?1 is an industr3Bled 148initiative under the #pen *mart 1rid >#pen*1? su committee within the (.$ 4nternational 149(sers 1roup >(.$4ug?C The #pen$%& Tas" Aorce defines s3stems re)uirements, policies and 150principles, est practices, and services, re)uired for usiness and data re)uirements for 151standardi7ing control and pricing signals for %emand &esponse >%&? and %istri uted /nerg3 152&esources >%/&? as part of the *mart 1rid implementation2C 153#pen$%& facilitates automated demand response for load shedding or shifting through demand 154response signals containing d3namic pricing or event o DectivesC %emand &esponse /vents are 155in response to emergenc3 or relia ilit3 conditions that affect the gridC 156#$2 Purpose of Document 157 158The 0urpose of this %ocument is to define the usiness and user re)uirements for #pen 159$utomated %emand &esponse >hereafter #pen$%&? for 0hase 2C 160The content of this document uilds on the wor" of E#pen $%& Aunctional &e)uirements and 161(se .ase %ocument 8ersion 1C0F and E#pen$%& 1C0 *3stem &e)uirements *pecificationF 162>E#pen$%& *&*F?C The e@isting #pen$%& *&* contains the definitions of roles, actors, and 163data architecture that is uilt upon in this documentC The *ervice %efinitions that support the data 164architecture defined in the *&* are defined in E#pen$%& 1C0 *ervice %efinition G .ommonFC 165The functional areas addressed in #pen$%& 0hase 2 are ased on priorities agreed upon 3 the 166#pen$%& Tas" Aorce su se)uent to the ratification of the #pen$%& 1C0 *3stem &e)uirements 167*pecification and the associated #pen$%& 1C0 *ervice %efinitionsC 168Aurther definition of these functional areas and the resulting re)uirements is defined in *ection 2C
101 The #pen$%& Tas" Aorce of the #pen *mart 1rid (sers 1roup ac"nowledges the wor" coordinated 3 the 11%emand &esponse &esearch .enter and funded 3 the .alifornia /nerg3 .ommission >/nerg3 .ommission?, 0u lic 124nterest /nerg3 &esearch >04/&? 0rogram in development of the Open Automated Demand Response 13Communications Specification, also "nown as #pen$%& or #pen $utoB%&C Aor the purposes of this document the 14specification will e cited using the full titleC The term #pen$%& *&* or *&* refers to the OpenSG OpenADR 15System Requirements SpecificationC 162 Requirements Specifications for Wholesale Standard DR Signals - for NIS !A!"#$ Requirements Specifications 17for Retail Standard DR Signals - for NIS !A!"#
/1.00, 29 "ct'ber 2009
18

19
169#$( Terms and Definitions 170 171This su section provides the definition of select terms used in this documentC 172
Term #&th'ri2in. 3ntity #&th'ri2ed $e1&est %'8en Definition %he entity 4e... PUC, Uti(ity, b'ndin. a.ent, etc.5 6h' appr'/es a *rd Party t' &ti(i2e the "pen#D3 inter7ace. # &ni1&e identi7ier 46ith'&t Pers'na( 0n7'rmati'n5 shared bet6een the Uti(ity and *rd Party, de7ined based 'n the a&thenticati'n standard bein. &sed. System by 6hich third parties can recei/e C'ns&mer Uti(ity Data 7r'm &ti(ities. "7ten priced separate(y 7r'm p'6er .enerati'n and pr'c&red as an anci((ary ser/ice, these re.&(ati'n ser/ices are &sed t' c'ntin&'&s(y 7ine t&ne the ba(ance bet6een .enerati'n and demand. # c'ns&mer 6h' recei/es ser/ice 7r'm the Uti(ity. May inc(&de c'ns&mer e(ectrica( &sa.e data, c'ns&mer ener.y mana.ement data, meter e/ents, :#; in7'rmati'n enera((y, the c'((ecti'n '7 c&rrent and hist'rica( c'ns&mer e(ectrica( &sa.e data. <r'm the S#3 P3) &se cases, this acr'nym is &sed t' describe a si.na( that may be sent t' a de/ice as part '7 a demand resp'nse pr'.ram. 0n7'rmati'n that pertains t' a speci7ic indi/id&a( and can be &sed t' identi7y that indi/id&a(, s&ch as C&st'mer name, address, 2ip c'de, &ti(ity acc'&nt n&mber, 'r 'ther in7'rmati'n 6hich identi7ies the indi/id&a( c&st'mer in the &ti(ity bac8 '77ice system # standard inter'perab(e inter7ace, as de7ined by "penS S System ='r8in. r'&p, the b&siness and &ser re1&irements '7 6hich are c'ntained in this d'c&ment. L'.ica( p'int 'n the net6'r8 6here the '6nership '7 the ser/ice chan.es hands !! typica((y 6here a meter may be insta((ed. # party 6h' has been a&th'ri2ed by an a&th'ri2in. a.ent 4e... &ti(ity, PUC, b'ndin. a.ent, etc.5 t' recei/e c&st'mer in7'rmati'n thr'&.h the "pen#D3 inter7ace at the re1&est '7 the c&st'mer. %he e(ectric ser/ice pr'/ider, 6hich, at a minim&m, is resp'nsib(e 7'r readin. the e(ectric meter, pr'/idin. :#; access t' the meter, and de(i/erin. ener.y t' the c'ns&mer. %his may be an inte.rated e(ectric &ti(ity 'r a %ransmissi'n and Distrib&ti'n &ti(ity.
- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed 2
#&t'mated Data 39chan.e 4#D35 #&t'matic enerati'n C'ntr'( 4# C5
C&st'mer C'ns&mer Uti(ity Data C'ns&mpti'n Data Direct De/ice C'ntr'( 4DDC5 a8a Direct L'ad C'ntr'( 4DLC5 Pers'na( 0n7'rmati'n
"pen#D3
Ser/ice De(i/ery P'int 4SDP5
*rd Party
Uti(ity
/1.00, 29 "ct'ber 2009

20

21
"pen#D$ B&siness and User $e1&irements D'c&ment Definition May act as an a(ternati/e t' the &ti(ity in estab(ishin. a re(ati'nship 6ith the c&st'mer. #(s' 8n'6n as an 3SC", a C'mpetiti/e 4'r a(ternati/e5 s&pp(ier '7 c'mm'dity ser/ice Used by the &ti(ity 'r #3S 7'r estab(ishin. a c'mm&nicati'n sessi'n
Term #(ternati/e 3ner.y S&pp(ier 4#3S5 'r 3SC" 3ner.y Ser/ice C'mm&nicati'ns 0nter7ace 43CS05 3(ectric /ehic(e 43)5 ! 3nd Use Meas&rement De/ice 43UMD5 3(ectric )ehic(e S&pp(y 31&ipment 43)S35
%he de/ice that meas&res and c'mm&nicates ener.y &sa.e in7'rmati'n pay('ad t' 3ner.y Ser/ices C'mm&nicati'n 0nter7ace 43SC05. P3) c'nnects t' the .rid &sin. an 3(ectric )ehic(e S&pp(y 31&ipment 43)S35. 3(ectric )ehic(e S&pp(y 31&ipment 43)S35 is the physica( e(ectrica( c'rd and c'nnect'rs that are speci7ied by app(icab(e S#3 standards 4e..., S#3 229*, >1??2, >2@*6 A >2@,?.5 that pr'/ide trans7er '7 e(ectrica( ener.y 7r'm ener.y p'rta( t' P3). %his can be 120) 'r 2,0) #C dependin. &p'n c'nnecti'n. %6' type '7 c'nnecti'n inc(&de 15 3)S3 c'rdset and 25 Premise M'&nted /ersi'n. %he Premise 3)S3 6'&(d n't inc(&de the char.er 7'r #C 4Le/e( 25 ener.y trans7er described in >1??2. %his 6'&(d e9pect the char.er t' be inc(&ded 6ith the /ehic(e. 07 the 3)S3 inc(&ded a char.er, DC 4Le/e( *5 ener.y trans7er is e9pected and the /ehic(e 6'&(d n't inc(&de the char.er since it 6as 6ithin the 3)S3. %his 3)S3 that inc(&des the char.er may a(s' be capab(e '7 #C ener.y trans7er at b'th 120) 4Le/e( 15 and 2,0) 4Le/e( 25 (e/e(s as described in >1??2.
173 174#$) References 175*C 'radner, 5e3 words for use in &A.s to 4ndicate &e)uirement ;evels, 176http+!!wwwCietfCorg!rfc!rfc2119Ct@t, 4/TA &A. 2119, 6arch 1997C4nformative &eferences 177 178 179 180 181 182 183 184 *outhern .alifornia /dison *mart.onnect 0rogram (se .ase+ 01 G (tilit3 0rovides *ervices to 0lugB4n /lectric 8ehicle >0/8? .ustomer *outhern .alifornia /dison *mart.onnect (se .ase+ 02 G .ustomer .onnects 0lugB4n /lectric 8ehicle >0/8? to 0remises /nerg3 0ortal *outhern .alifornia /dison *mart.onnect (se .ase+ 03 B .ustomer /nrolls in a 0/8 %emandB*ide 6anagement 0rogram *$/ 8ehicle (se .ase Tas" Aorce 92836!1H /nerg3 4ndependence and *ecurit3 $ct of 2007
/1.00, 29 "ct'ber 2009

22

23
1852$% OP*'ADR BU+&'*++ RAT&O'A * 186 187This section descri es the usiness rationale ehind #pen$%& G that is, the fundamental 188 usiness Dustification for defining the s3stemC 189 1902$# Bac,"round 191 1924n response to local and federal initiatives toward improving grid relia ilit3 and promoting 193consumer involvement in alancing suppl3 and demand of energ3 resources, the #pen *mart 1941rid >#pen*1? su committee within the (.$ 4nternational (sers 1roup has organi7ed a 195num er of wor"ing groups and tas" forces to develop re)uirements and specifications for *mart 1961rid needsC *u se)uentl3, a tas" force >#pen$%&? has een formed within #pen*1 to gather 197re)uirements and use cases for $%& from all interested sta"eholders, including utilities, 3rd 198parties, consumers, regulators, and othersC 199(nder the /nerg3 4ndependence and *ecurit3 $ct >/4*$? of 2007, the :ational 4nstitute of 200*tandards and Technolog3 >:4*T? was given the Eprimar3 responsi ilit3 to coordinate 201development of a framewor" that includes protocols and model standards for information 202management to achieve interopera ilit3 of smart grid devices and s3stemsIF J/4*$ Title -444, 203*ection 1305KC :4*T has engaged a road range of sta"eholders in the development of a *mart 2041rid 4nteropera ilit3 *tandards &oadmap and the formation of the *mart1rid 4nteropera ilit3 2050anel >*140?C The outcome of two wor"shops hosted 3 :4*T was a list of critical standards 206and standards development activities needed for the *mart 1ridC 4n an $ugust 10, 2009 report, 207:4*T proposed a set of fourteen 0riorit3 $ction 0lans >0$0s? >and still growing? for developing 208standards necessar3 to uild an interopera le *mart 1ridC 0$009+ *tandard %& and %/& 209*ignals3 is one of these 0$0sC 210The (.$ #pen*mart1rid organi7ation, in conDunction with The :orth $merican /nerg3 211*tandards 'oard >:$/*'?, developed the document EAramewor" for 4ntegrated %emand 212&esponse >%&? and %istri uted /nerg3 &esources >%/&? 6odelsFC This wor" was the 213foundation for the :$/*' E&e)uirements *pecification for &etail *tandard %& *ignals G for 214:4*T 0$009FC This document served as the &e)uirements %ocument for the E#pen$%& 1C0 215*3stem &e)uirements *pecificationF which was ratified 3 the #pen*1 /@ecutive .ommittee in 216#cto er 2010C 217This document will uild on the wor"s cited a ove and descri es onl3 the new functionalit3 to e 218addressed in #pen$%& 2C0C 2192$2 Opportunit220 221%efine an open standard interopera le interface that addresses $utomated %emand &esponseC
243 %etails of the 0$009 # Dectives and Tas" 0lan can e found at+ 0$009%&%/&
/1.00, 29 "ct'ber 2009
25

26
222The initial scope of #pen$%& 1C0 as defined in the *3stem &e)uirements specification 1C0 223e@cluded some functional areas that were targeted as part of the Aramewor" and :$/*' 224&e)uirements in order to allow the aseline wor" to e completed without attempting to "eep 225aligned with onBgoing efforts within other 0$0s or *140 =or"ing 1roupsC 226There is now the opportunit3 to address some of the roader or crossBcutting issues not addressed 227in #pen$%& 1C0C 228 2292$( Ob.ecti/es 2301oal+ Ainish 0hase 2 'usiness and (ser &e)uirements 2C0 and the *3stem &e)uirements 231*pecification >*&*? 2C0 document 3 $ugust 2011CC 232 2332$) Ris,s 234 #ther standards odies or users groups with conflicting wor" or agendasC
2352$0 +pecific Business Requirements 236 237The usiness re)uirements provide a frame of reference, or domain, in which to define a specific 238s3stemC 4n some senses, the usiness re)uirements serve as constraints on a proDectLs vision and 239scopeC $s such, the3 are generall3 defined independentl3 and in advance of the vision and 240scopeC 241There ma3 e a need >due to regulator3 or other considerations? for alternate authori7ation 242approaches >in conDunction with federal and state law?M however, specific conformance with the 243re)uirements outlined in this document is encouragedC 244The "e3 words 6(*T, 6(*T :#T, &/N(4&/%, *<$;;, *<$;; :#T, *<#(;%, *<#(;% 245:#T, &/.#66/:%/%, 6$O, and #0T4#:$; in this document are to e interpreted as 246descri ed in J&A.2119KC 247The following ta le lists specific usiness re)uirements for #pen$%& 2C0C 248
0D
"#D$ B$3)!1 "#D$ B$3)!2 "#D$ B$3)!*
B&siness $e1&irement
%he &ti(ity M#B '77er the C&st'mer a P3) tari77 that pr'/ides a ('6 rate 7'r '77!pea8 char.in. and a hi.her rate 7'r 'n!pea8 char.in.. 4S#3 >2@*6+1 C5 %he &ti(ity MUS% pr'/ide ser/ices t' s&pp'rt ener.y s&pp(ied t' c&st'mer P3) 4$e7erence S#3 >2@*6+1 C5 %he &ti(ity MUS% imp(ement an enr'((ment system 7'r C&st'mers 6ith a P3) inc(&din. re.istrati'n and c'mmissi'nin.. 4$e7erence S#3 >2@*6+1 C5
/1.00, 29 "ct'ber 2009

27

28
"#D$ B$3)!,
%he &ti(ityEs 3ner.y Ser/ices C'mm&nicati'n 0nter7ace 43SC05 S:#LL a(('6 7'r the estab(ishment '7 a c'mm&nicati'ns sessi'n 4c'mm&nicati'ns bindin.5, at a premise ('cati'n each time a P3) p(&.s in 7'r char.in.. 4$e7erence S#3 >2@*6+1 C5 0n7'rmati'n re(ated t' &ti(ity P3) pr'.rams, ener.y &sa.e, and P3) char.in. stat&s+in7'rmati'n S:"ULD be made a/ai(ab(e t' the C&st'mer 7'r /ie6in. /ia a 6ebsite 'r 'ther c&st'mer pr'/ided disp(ay e1&ipment 4$e7erence S#3 >2@*6+1 C5 07 a/ai(ab(e, the C&st'mer M#B se(ect .reen ener.y as a char.in. 'pti'n 7'r P3) /ehic(es 4$e7erence S#3 >2@*6+1 C5. %he C&st'mer M#B se(ect the pri'rity '7 the ener.y char.in. re1&est 6hich indicates the &r.ency '7 the char.in. need. 4$e7erence: S#3 >2@*6+1 C5 %he C&st'mer M#B se(ect t' 'ptimi2e the char.in. '7 the P3) 4$e7erence: S#3 >2@*6+1 C5 %he &ti(ity 4'r 3SC"5 MUS% a&thenticate P3) enr'((ment re1&ests 4$e7erence: S#3 >2@*6+1 C5 %he C&st'mer M#B e(ect a pr'.ram that a(('6s their P3) t' dischar.e 'nt' the .rid Distrib&ted enerati'n may participate 'r "pt!'&t '7 a D$ 3/ent based 'n ec'n'mic c'nsiderati'ns re.ardin. the c'st '7 ener.y d&rin. the e/ent. Price in7'rmati'n d&rin. the e/ent sha(( be s&77icient t' s&pp'rt the ec'n'mic c'nsiderati'ns. Distrib&ted enerati'n sha(( ha/e the abi(ity t' c'mm&nicate and "pt!'&t 7'r a speci7ic D$ 3/ent. Distrib&ted enerati'n sha(( ha/e the abi(ity t' enr'(( 4re.ister5 res'&rces in D$ Pr'.rams. Distrib&ted enerati'n res'&rces sh'&(d ha/e the abi(ity t' c'ns&me D$ 3/ent si.na(s 7'r re.&(ati'n ser/ices. <astD$ sha(( s&pp'rt dispatch 7re1&encies 7r'm , sec'nds t' many min&tes. <astD$ sha(( s&pp'rt te(emetry rates as 7ast as , sec'nds.
"#D$ B$3)!D
"#D$ B$3)!6 "#D$ B$3)!? "#D$ B$3)!@ "#D$ B$3)!9 "#D$ B$3)! 10 "#D$ B$D ! 11 "#D$ B$D ! 12 "#D$ B$D ! 1* "#D$ B$D ! 1, "#D$ B$<D! 1D "#D$ B$<D! 16 "#D$
/1.00, 29 "ct'ber 2009
29
<astD$ sha(( s&pp'rt D$ $es'&rces dispatched in the 1000Fs.


30
B$<D! 1? "#D$ B$<D! 1@ "#D$ B$<D! 19 "#D$ B$<D! 20 "#D$ B$<D! 21 #dd Demand $esp'nse c'mm&nicati'ns m&st be sec&re and s&pp'rt the n'rma( set '7 7eat&res inc(&din. inte.rity, c'n7identia(ity, a/ai(abi(ity, and a&thenticity. ;'n!rep&diati'n may a(s' be re1&ired. Demand $esp'nse Dispatches are typica((y &sa.e (e/e(s and may represent either a speci7ic &sa.e set p'int 4i.e. (i8e a .enerat'r5 'r may be an '77set 7r'm base(ine. Dispatches may ha/e speci7ic start and st'p times 'r they may be 'pen ended meanin. it is a c'mmand that is 7'(('6ed &nti( the res'&rce is t'(d 'ther6ise. #(( c'mm&nicati'ns m&st be re(iab(e.,
249 250 251($% OP*'ADR 1&+&O' 252 253This section on #pen$%& 8ision attempts to define the full potential of #pen$%& interface, 254rather than Dust those elements that will e part of the initial releaseC 255($# Pro.ect 1ision +tatement 256 257The vision of the #pen$%& effort is that a consistent set of usiness re)uirements can e used to 258foster the development of standard interfaces to facilitate %emand &esponseC This wor" will e 259provided to sta"eholders to develop standards and est practices that will foster innovationC 260($2 2a.or !eatures 261 262This section attempts to delineate all features that are >and specificall3 are not? part of the 263 roader #pen$%& vision for 0hase 2C 264 !eature
S&pp'rt 7'r P(&.!in )ehic(es 4P3)5 c'mm&nicati'n in the c'nte9t '7 Uti(ity Pr'.rams
&n
G
Out
314 &elia le messaging is the assurance that the correct messages have een delivered across a networ" e@actl3 once, 32and in the correct orderC The use of =*B&elia le6essaging protocol is not re)uired to meet this re)uirementC
/1.00, 29 "ct'ber 2009
33

34
S&pp'rt 7'r <astD$ c'mm&nicati'n as de7ined in this d'c&ment. S&pp'rt 7'r Distrib&ted enerati'n c'mm&nicati'n 7'r &se cases de7ined as in sc'pe in this d'c&ment. S&pp'rt 7'r Distrib&ted enerati'n c'mm&nicati'n by Uti(ity C&st'mers S&pp'rt 7'r Distrib&ted enerati'n c'mm&nicati'n by n'n!&ti(ity C&st'mers 'r Distrib&ted enerati'n s&pp(ied '&tside '7 the c&st'merEs re.istered ('cati'n 4s&ch as P3) 'r 'ther r'amin. s'&rces5.
G 3
265 266($( Assumptions and Dependencies 267 268The following assumptions were made in development of these re)uirementsC 269 270 271 272 273 274 275)$% OP*'ADR +COP* 276 277This section on #pen$%& 2C0 *cope attempts to constrain the definition of the 2C0 version of 278#pen$%&C 279 280)$# +cope of &nitial Release 281 282#pen$%& 1C0 scope is limited to the items as defined in the *cope section of the E#pen*1 283#pen$%& 1C0 *3stem &e)uirements *pecificationFC 284 285)$2 +cope of OpenADR Phase 2 286 287The 2C0 8ersion of #pen$%& consists of addressing the following areas for %emand &esponse+ 288 289 1C 0lugBin /lectric 8ehicle >0/8? 2C Aast %emand &esponses >Aast%&?
/1.00, 29 "ct'ber 2009
35
(se .ases for 0/8 are defined on other cited documents, and are assumed to e representative and completeC (se .ases for Aast%& are ased on wor" done in conDunction with .$4*# and othersC The assumption is that variations in regional mar"et structures do not affect the asic re)uirementsC

36
290 291
3C %istri uted 1eneration >%1?5 4C *ecurit3
292*ecurit3 (se .ases and &e)uirements are addressed in the E#pen$%& *ecurit3 0rofileF which is 293 eing developed Dointl3 with the *1 *ecurit3 >(til*ec? TeamC 294 295)$( 296 297The following ta le lists specific features associated within the areas in scope for 2C0 and listed 298as in or out of scopeC These are features more specific than defined for 6aDor Aeatures which 299arise during the (se .ase $nal3sisC 300C !eature
0s(andin. '7 Distrib&ted enerati'n
imitations and *4clusions
&n
Out
3 G
The conte@t of advertise %/& .apa ilities within #pen$%& is limited to the capa ilities availa le as part of a %emand &esponse 0rogramC #ther capa ilities are advertised into other mar"ets in which the consumer wishes to participateC The definitions of these other mar"ets is not in scope for #pen$%&C
301 3020$% OP*'ADR CO'T*3T 3030$# +ta,eholder Profiles 304 305 +ta,eholder
C'ns&mer
+ta,eholder 5oal
#b(e t' ma8e in7'rmed decisi'ns ab'&t their e(ectric c'ns&mpti'n by ha/in. time(y access t' c&rrent and hist'ric c'ns&mpti'n in7'rmati'nH c'ns&mpti'n is Im're transparentJ
375 %istri uted 1eneration was originall3 descri ed as %istri uted /nerg3 &esources >%/&?C
/1.00, 29 "ct'ber 2009
38

39
#b(e t' .rant *rd Parties access t' their C'ns&mpti'n Data in 'rder t' recei/e *rd Party /a(&e!added pr'd&cts and ser/ices. Uti(ities Pr'/ide better + m're appr'priate ser/ices t' c'ns&mers Pr'/ide the standard machine t' machine inter7ace t' enab(e additi'na( cate.'ries '7 ser/ices, as appr'priate 4inc(&din. e... Demand #..re.ati'n5 IS'cia(J bene7it 0ncreased c&st'mer satis7acti'n. #ccess t' c&st'mer C'ns&mpti'n Data is a basic enab(er '7 *rd Party pr'd&cts and ser/ices *rd Parties Pr'/ide Smart rid enab(ed pr'd&cts and ser/ices t' ener.y c'ns&mers 0ncreases (i8e(ih''d '7 &ti(ity pr'/idin. *rd Party access t' c'ns&mer data. Simp(i7ies the &ti(ity inter7ace , /ers&s a n'n! standard inter7ace 'n a per!&ti(ity basis PUC Satis7ies PUC .'a( '7 ma9imi2in. c'ns&mer /a(&e L'6ers &ti(ity '/era(( c'sts L'6ers '/era(( c'st '7 data access imp(ementati'ns
306 307 3086$% OP*'ADR U+* CA+*+ 309 310The following diagram shows an overview of the use cases involved in this recommendationC
311
/1.00, 29 "ct'ber 2009

40
10

41
uc DR Use Cases Ov erv iew Diagram (sim !e"
.$% ,dministrate DR &rogram
(from !.0 Administrate DR Program) @$recedesA
-$% ,dministrate Customer for DR
@$recedesA
+$% ,dministrate DR Resource
(from 2.0 Administrate
ustomer for DR)
(from 3.0 Administrate DR Resource)
@$recedesA
)$% '*ecute DR 'v ent
@$recedesA
#$% &ost DR 'v ent (anagement
(from 4.0 Execute DR Event)
(from 5.0 Post DR Event Management)
312
313
/igure . 0 DR Use Cases Overview
314Aigure 1 is the high level overview of #pen$%&C The scope is currentl3 limited to the activities 315defined for 3C0 $dministrate %& &esource >e@clusive of 3C2 %& 'idding? and 4C0 /@ecute %& 316/ventC The Aigures 1B3 are provided for conte@t of the #pen$%& (se .ases defined elow, and 317are full3 defined in the :$/*' 0$009 &etail &e)uirementsC
/1.00, 29 "ct'ber 2009

42
11

43
uc +$% ,dministrate DR Resource
+$% ,dministrate DR Resource Serv ice &rov ider (from Actors)
+$- ,dministrate Distribution DR Resource
@includeA
@includeA
@includeA
+$-$. U date DR Resource
+$-$- Register DR Resource
+$-$+ Remov e DR Resource
@includeA
@e;tendA
@e;tendA
@e;tendA
+$+ DR Bidding
+$-$) ,dministrate DR ,sset (Direct" +$-$)$- U date DR ,sset @includeA @includeA +$)$-$+ Remov e DR ,sset
@includeA +$+$. Retai! DR Bid to Su !y (Offers" +$+$- DR Bid to Buy +$-$)$. Register DR ,sset +$-$# ,dministrate D'R for DR &ur ose
318
319
/igure - ,dministrate DR Resource
/1.00, 29 "ct'ber 2009

44
12

45
uc '*ecute DR 'v ent
)$6 O erationa! Coordinations
@includeA
)$5 DR 'v ent '*ecution
@invo:esA
@invo:esA
)$1 Dis atch DR 2nstructions (Retai!"
)$3 DR Direct 4oad Contro! (Retai!"
)$% '*ecute DR 'v ent Serv ice &rov ider (from Actors) Resource (from Actors)
)$) Broadcast DR (essage (&rice &!us 2nformation"
)$- Notify DR 'v ent (Retai!"
320
321
/igure + 7 '*ecute DR 'vent
3226$# OP*'ADR U+* CA+*+ for P*1 323'efore e@ploring the 0/8 use cases that are pertinent for the #pen$%& 2C0 discussion it is 324important to understand the following use cases in the overall conte@t of the use cases as the3 325were developed 3 *$/C The focus of this e@ploration will e the utilit3 related use cases >(1 G 326(5?, ut there are other related use cases that will inform the discussion as shown in the 327following figureC
/1.00, 29 "ct'ber 2009

46
1*

47
328
329/igure ) 8 S,' &'9 use cases: re!ationshi s: and de endencies$ Source8 S,' ;-5+1< 9ehic!e Use 330Case =ask /orce
331 The *$/ 92836 standard descri es several use cases that can inform the discussion on the use of 3320/8s in a demand response conte@tC There are two classes of communicationM 1? that associated 333with enrolling the 0/8 in a specific utilit3 program 2? the messages associated with the 334respective program once the 0/8 is enrolledC 335Aor the purposes of demand response T#( is out of scopeC =hile T#( covers location, amount 336of usage, and price associated with a particular load, T#( rates do not change ver3 often and are 337usuall3 associated with a tariff set 3 the local Durisdictional authorit3C The other programs noted 338in the *$/ standard are within scope as the3 include various schemes where 3 some signal is 339sent 3 a utilit3, aggregator, /*.#, or other entit3 that causes the load to changeC 340$dditionall3, in terms of enrollment there is a generic enrollment case and each of the ( use 341cases cover one of the utilit3 programsC <owever, the onl3 difference etween the uses cases is 342the program to e enrolled in and an alternative scenario where the enrollment ma3 e handled 343 3 an /*.#C #ther than those two distinctions the use cases are the sameC Therefore for the 344purposes of the #pen$%& assessment the enrollment use cases have een consolidated elowC 345#ne other point of interest in terms of 0/8 and %& related communications is the *$/ 346assumption that the 0/8 connects to the /*4 in a 0(;; method, that is, once the 0/8 connects 347it polls the /*4 for an3 %& related event informationC This must also assume that an3 %& related
/1.00, 29 "ct'ber 2009
48
1,

49
348information must e sent to the /*4 3 the utilit3 or other third part3C T3pciall3 sending 349information to an /*4 emplo3s a 0(*< model, ut a 0(;; model could also e usedC This high 350level communication concept is illustrated elowC
351
352/igure # 8 High !eve! conce tua! mode! of &'9 to 'S2 to Uti!ity > =hird &arty communication
353 3546$#$# P*1 7 Consolidated *nrollment Use Case 356Context+ This use case presumes that the utilit3 ma3 have various programs associated with 0/8 357ownership that ma3 create an incentive for the 0/8 owner to parta"e in the respective programsC 358#f interest for demand response are the realBtime pricing, direct load control, critical pea"B 359pricing, and optDmi7ed energ3 charging programs noted in 92836!1HC 360Primary Actor+ .onsumer 361Stakeholders and Interests+ (tilit3, 3rd 0art3 >/*.#? 362Preconditions+ 363 364 1C .ustomer has a 0/8 and wishes to enroll in T#( programM 2C (tilit3 or /*.# offers 0/8 0rograms to its customersC
355
365Trigger(s)+ 366The .ustomer ac)uires a 0/8 and contacts the (tilit3 to enroll in a 0/8Brelated programC 367The customer ma3 e prompted 3 the dealer, 86, retail store, utilit3 and more for specific 368programsC 369 370Post-Condition 371The (tilit3 or /*.# has successfull3 enrolled the .ustomer 0/8 in the 0rogram desired 3 the 372.ustomerC 373Activity !iagram+
/1.00, 29 "ct'ber 2009

50
1D

51
act Conso!idated &'9 ,ctiv ity Diagram /usto3er
%ctivityInitial
Becomes aw are of Uti!ity &'9 rograms
2nitiate enro!!ment
Com !ete &'9 enro!!ment
Determine e?ui ment use
'?ui ment insta!!ed
Set v ehic!e arameters
Determine w hen and w here to use the &rogram
%ctivity9inal
#"Bect)ode1 .tility / &0/# #"Bect)ode2 &rocess enro!!ment re?uest C&0/#D &ass re?uest to C!earinghouse Send &'9 rogram info to customer C.tilityD #"Bect)ode3
,uthenticate customer
Confirm 'nro!!ment
Com !ete Back7Office &rocessing C.tilityD
Schedu!e meter insta!!
2nsta!! meter
Sw itch to new serv ice
2ssue fina! bi!!
/learin2house Determines commodity rov ider
,&-
#"Bect)ode> ,cce t arameters
374
375/igure 1 8 Customer enro!!s a &'9 in a demand res onse re!ated rogramm either through a Uti!ity 376or 'SCO
378"ain S#ccess Scenario+ 379This consolidated series of steps has een s3nthesi7ed from *$/ 92836!1H general use case /, 380and utilit3 enrollment use case (1 G (5C
*tep 1 2 $ctor .ustomer .ustomer %escription 4nformed of programLs costs! enefits 4nitiates enrollment >enrolls? in a specific program with (tilit3 or /*.# %etermines who provides the commodit3 0resents .ustomer with 0/8 program information and selections :otes 0rograms ma3 e+ T#(, &T0, .00, %;., #ptimi7ed /nerg3 Arom use case / generic enrollment and each alternative scenario Arom use case / generic enrollment $uthentication should occur efore determining eligi ilit3 so onl3 valid enrollments are processed .om ined two
16
377
3 4
.learinghouse /*.# ! (tilit3
5 6
.ustomer /*.# ! (tilit3
.ompletes enrollment and returns it to the (tilit3 or /*.# >we , mail, other? $uthenticates the customer, customer account, premise information, and collects 0/8 information >eCgC 0/84%?
7
/1.00, 29 "ct'ber 2009
52
/*.# ! (tilit3
.onfirms enrollment is complete,

53
"pen#D$ B&siness and User $e1&irements D'c&ment determine .ustomer eligi ilit3 and advises an3 ne@t steps &e)uest meter installation from the (tilit3 %ased on program enrollment (tilit3 schedules meter installation, issues cutBover order, and notifies customer of meter installation >inB service? date (tilit3 installs meter and completes ac"Boffice administrative action (tilit3 switches service to T#(, .00, #ptimal /nerg3 .harging, &T0, or %;. and issues final ill for old service .ustomer determines whether to use .ordset, /8*/, or 0remise unitM purchases from vehicles dealership, retail store, utilit3 or /*.# as availa le .ustomer selfBinstalls or contracts installation of .ordset, /8*/, 0remise unit $dditional control devices could e installed, dependent on program .ustomer selects 0/8 program and sets parameters vehicle ! /8*/ ! <$: to accept program o Dectives .ustomer determines when!wh3 to use the program previous steps
8 9
/*.# (tilit3
Arom use case (1, (2, (3, (4 Arom use case (1, (2, (3, (4 Arom use case (1, (2, (3, (4
10 11
(tilit3 (tilit3
12
.ustomer
13 14 15 16
.ustomer .ustomer .ustomer .ustomer
Arom use case / generic enrollment
381 382$xtensions+ :one 383 384"inimal %#arantees+ 385The .ustomerLs enrollment data has not een e@posed to parties that are not re)uired to complete 386an enrollmentC 387S#ccess %#arantees+ 388The .ustomerLs enrollment re)uest has een authenticated 389The .ustomerLs 0/8 is enrolled in the desired 0rogramC 390 391&re'#ency o( )cc#rrence+ 6inimum fre)uenc3 will e oneC <owever, it is assumed that there 392ma3 e a duration associated for the enrollment at the conclusion of which the .ustomer ma3 393have the option to e@tend the program that the3 are enrolled in, or enroll in a different 0/8B 394related programC 395
/1.00, 29 "ct'ber 2009

54
1?

55
3966$2 OP*'ADR U+* CA+*+ for Distributed 5eneration 397%istri uted generation, also called distri uted energ3, generates electricit3 from man3 small deB 398centrali7ed energ3 sourcesC 399$s the concept of %emand &esponse is e@panded to include generation as an e)uivalent to 400negative load, %istri uted 1eneration offers additional options in response to %& # Dective or 4010rice *ignalsC $dditionall3 %istri uted 1eneration is capa le of fulfilling other ancillar3 services 402which are identified in the use casesC 403The %istri uted 1eneration &esource is assumed to e in an e@isting state of generate, charge or 404discharge, with var3ing rates of u3, use, and sale of power, and capa le of moving to another 405state in response to %& related signalsC 406The model for the %istri uted 1eneration (se .ases assumes a constantl3 recurring evaluation 407of the relative costs and capa ilities for each of the optionsC There is no se)uence of states and 408onl3 charge!discharge can not happen concurrentl3C The /nerg3 6anagement *3stem might 409decide on a mi@ of generate, u3, charge!discharge, load reduction an an3 given moment ased 410on capa ilities, constraints, and est economic choice availa le to the facilit3C 411(se .ases 1 through 4 represent the four different outcomes of the decision process when 412impacted 3 the conditions of a %emand &esponse /ventC The activit3 diagram elow represents 413the consolidation of those use cases as a series of choices in a single diagramC 414Activity !iagram
act D@ Conso!idated &rocess (U.7U)" D' /ontroll in2 &ntity / -E)
Send Demand Res onse Signa! (&rice or ObA ectiv e" (from D"! #oca$ "eneration)
Receiv e O t Out
Receiv e 'v ent /eedback 'aring)
(from D"! #oca$ "eneration) (from D"4 % urtai $ &torage
9aci lity / D' 'esource Buy &ow er O t Out of 'v ent &rov ide /eeback if during 'v ent 'aring)
(from D"! #oca$ "eneration) Determine Re!ativ e &rice &oints for 'conomic Decisions Determine 'conomic O timiBation from &rice &oint and Ca abi!ities @enerate &ow er (for Sa!e: Use: or Storage" /hoice Based on &;ternal /ost vs. Internal /ost and %vai la"l e 0tora2e Charge
(from D"4 % urtai$ &torage (from D"! #oca$ "enerati on)
Reciev e Demand Res onse Signa!
Shed ,dA ust Storage Rate
(from D"! #oca$ "enerati on) (from D"4 % urtai$ &torage 'ari ng)
Discharge
Se!! &ow er
Consume 4oca!!y
415
416
/igure 3 0 UC .7) D@ Conso!idated &rocess
/1.00, 29 "ct'ber 2009

56
1@

57
4176$2$# D5 7 ocal 5eneration 419Context+ $ facilit3 that has its own local energ3 resources uses the mar"et to ma"e up for 420shortfalls to meet local re)uirementsC The customer has agreed to shed load ased on the terms of 421a %emand &esponse 0rogram, ut when the re)uest comes in the facilit3 cannot participateM for 422e@ample, ecause the load is in process or otherwise criticalC The 0rogram penalt3 ma3 ma"e it 423worthwhile to ramp generationC .onsiderations are the cost of energ3 during critical event plus 424the penalt3 ma3 ma"e it more economical to ramp up generation capacit3C 425Primary Actors+ .onsumer, Aacilit3 ! Aacilit3 6anagement *3stem, (tilit3 or %& $ggregator 426>%& .ontrolling /ntit3 or 8irtual Top :ode? 427Stakeholders and Interests+ .ustomer, (tilit3, possi le 3rd 0art3 %& $ggregator 428Preconditions+ 429 430 431 432Trigger(s)+ 433%& /vent *ignal is received or re)uested 3 the facilit3C 434"ain S#ccess Scenario 435 1C Aacilit3 receives %& /vent *ignal >o Dective or price?C 436 2C &amp generation in response to %& signal to support critical loadsC 437 3C 0rice responsive generators ramp up when grid cost e@ceeds operational costC 438Post-Condition 4390rovide local generation to reduce demand on the gridC 440 441Activity !iagram+ 1C Aacilit3 has its own energ3 resources and uses the mar"et to ma"e up shortfallC 2C .ustomer has enrolled facilit3 as a &esource for a %& 0rogram
418
/1.00, 29 "ct'ber 2009

58
19

59
act D@. 4oca! @eneration D' /ontrollin2 &ntity / -E)
0tart
Send Demand Res onse Signa! (&rice or ObA ectiv e"
Receiv e O t Out &nd
9acility / 'esource
Buy &ow er Reciev e Demand Res onse Signa! .se Focal ,o4er or BuyG
#"Bective 0i2nalG
O t Out of 'v ent
@enerate &ow er for 4oca! Consum tion
&nd
442
443
/igure 5 0 D@. 4oca! @eneration
4446$2$2 D5 7 Char"e +tora"e 446Context+ .onsumer has onsite storage that can a sor e@cess energ3 or charge during offBpea" ! 447lowBcost periodsC The stored energ3 can later e discharged to support %&C 448Primary Actor+ .onsumer, Aacilit3 ! Aacilit3 6anagement *3stem 449Stakeholders and Interests+ .ustomer, (tilit3, possi le 3rd 0art3 %& $ggregator 450Preconditions+ 4511C #nsite storage is not alread3 charged 4522C $ price point has een determined and set when it is economical to charge the storage 453device 4543C 4554C #ff pea" rates >:ighttime? energ3 rates can e ver3 low ! negative .onsumer receives incentives to charge during over suppl3
445
456Trigger(s)+ 4570rice point falls elow the set point to egin the charge c3cleCC 458"ain S#ccess Scenario 459 460 1C /nerg3 is economicall3 stored such that a discharge results in a net cost saving to the consumer
/1.00, 29 "ct'ber 2009

60

61
461Post-Condition 462.onsume e@cess suppl3 3 storing energ3 offBpea" 463Activity !iagram+

act D@- 7 Charge Storage D' /ontrollin2 &ntity / -E)
Send &rice or ObA ectiv e Signa!
9acility / 'esource Charge Storage Determine Charge7 not Charge &rice &oint Reciev e &rice or ObA ectiv e Signa! &cono3ic Decision
&nd of 9lo4
Discharge Storage
464
465
/igure 6 0 D@- Charge Storage
4666$2$( D5 7 Dischar"e ener"- stored durin" pea, demands 468Context+ .onsumer has onsite storage that is full3 or partiall3 charged and can e discharged to 469support critical loads, or rought to ear to in addition to, or in lieu of, load reductions during a 470%& eventC *tored energ3 could e thermal or other forms that produce electricit3 upon discharge 471or otherwise offset the use of electricit3 >eCgC ice storage to offset <8$. load?C $de)uate 472amounts of storage can e used to relia l3 power critical loads for well defined durations during 473%& events or grid outagesC 474Primary Actor+ .onsumer, Aacilit3 ! Aacilit3 6anagement *3stem 475Stakeholders and Interests+ .ustomer, (tilit3, possi le 3rd 0art3 %& $ggregator 476Preconditions+ 4771C *torage resource is full3 or partiall3 charged 4782C $ %& price signal, %& severit3 level, or demand limit threshold is used to determine the 479point at which the storage resource will dischargeC
/1.00, 29 "ct'ber 2009
62
467
21

63
480Trigger(s)+ 4810rice point, %& signal severit3 level, or demand limit threshold is reached that triggers the 482storage resource to dischargeC 483"ain S#ccess Scenario 484 485 486 1C %& load offset targets are achievedC 2C %emand limit thresholds are respectedC 3C Aacilit3 re)uirements for power relia ilit3 to critical loads are metC
487Post-Condition 488/nerg3 is supplied to the grid or load is offsetC 489Activity !iagram+

act D@+ 7 Discharge Storage D' /ontrollin2 &ntity / -E)
Send &rice or ObA ectiv e Signa! (from D"2 % 'arge &torage)
9acility / 'esource Charge Storage &nd of (from D"2 % 'arge &torage) 9lo4 (from D"2 % 'arge &torage) 4oad Reduction Discharge Storage (from D"2 % 'arge &torage) Internal &cono3ic Decision Se!! to @rid
Determine Charge7 not Charge &rice &oint
Reciev e &rice or ObA ectiv e Signa!
&cono3ic Decision
(from D"2 % 'arge &torage) (from D"2 % 'arge &torage)
490
491
/igure .% 0 D@+ Discharge Storage
4926$2$) D5 7 Curtail +tora"e Char"in" 494Context+ .onsumer has energ3 storage resources whose charge c3cle can e curtailed during a 495%& eventC 496Primary Actor+ .onsumer, Aacilit3 ! Aacilit3 6anagement *3stem 497Stakeholders and Interests+ .ustomer, (tilit3, possi le 3rd 0art3 %& $ggregator 498Preconditions+ 499 500 501 1C *torage resource is in the process of chargingC 2C $ %& price point, %& severit3 level, or demand limit threshold is used to determine when to suspend charging c3cleC
/1.00, 29 "ct'ber 2009
64
493
22

65
502Trigger(s)+ 503$ %& price point, %& severit3 level, or demand limit threshold is reached that triggers the charge 504c3cle to e suspendedCC 505"ain S#ccess Scenario 506 507 1C ;oad from the storage charging is shifted to when the price lowers, %& event ends, or demand thresholds can e respectedC
508Post-Condition 509.urtailment of storage for re)uested intervalC 510Activity !iagram+

act D@) 7 Curtai! Storage Charging D' /ontrollin2 &ntity / -E)
Receiv e 'v ent /eedback
9acility / 'esource
Determine Charge7 not Charge &rice &oint
&cono3ic Decision
,dA ust Storage Rate
&rov ide /eeback if during 'v ent
511
512
/igure .. 0 D@) Curtai! Storage Charging
5136$2$0 D5 7 Compensate for 1ariable D*R 515Context+ 8aria le generation sources such as wind and solar can e compensated for 3 516shedding or ramping loadC The load response must e EfastFC *udden drops or ramps in the 517varia le generation are generall3 forecasta le in the short term >eCgC sunrise!sunset, approaching 518clouds, wind gusts!lulls?C 519Primary Actor+ .onsumer, Aacilit3 ! Aacilit3 6anagement *3stem 520Stakeholders and Interests+ .ustomer, (tilit3, possi le 3rd 0art3 %& $ggregator 521Preconditions+
514
/1.00, 29 "ct'ber 2009

66
2*

67
522 523 524 525
1C .onsumer has onsite varia le generation resourceC 2C ;oads are availa le to shed in response to a drop in production 3C ;oads or storage are availa le to ramp in response to an increase in production
526Trigger(s)+ 527*udden drop or rise in varia le generationC 528"ain S#ccess Scenario 529 530 1C ;oads are shed to compensate for a drop in generation 2C /@cess energ3 is supplied to the grid, additional loads, or onsite storageC
531Post-Condition 532;oads are operating as normalC 533Activity !iagram+

act D@# 7 Com ensate for 9ari!ab!e D'R D' /ontrollin2 &ntity / -E )
Receiv e 'v ent /eedback (from D"4 % urtai$ &torage 'aring)
9acility / 'esource 4oad Shed Determine Charge7 not Charge &rice &oint &rov ide /eeback if during 'v ent (from D"4 % urtai$ &torage 'aring)
&cono3ic Decision
Charge Storage
(from D"2 % 'arge &torage) Discharge Storage (from D"2 % 'arge &torage) (from D"2 % 'arge &torage)
534
535
/igure .- 0 D@# Com ensate for 9ariab!e D'R
5366$2$6 D5 7 Ad/ertise D*R Capabilities 538Context+ .onsumer has onsite resources that can e offered to the utilit3 to support grid 539operations and relia ilit3C 'ase generation forecast is folded into the overall demand forecast 540while additional capacit3 or services are offered at mar"et ratesC The conte@t of advertise %/& 541.apa ilities within #pen$%& is limited to the capa ilities availa le as part of a %emand
537
/1.00, 29 "ct'ber 2009

68
2,

69
542&esponse 0rogramC #ther capa ilities are advertised into other mar"ets in which the consumer 543wishes to participateC The definitions of these other mar"ets is not in scope for #pen$%&C 544The capa ilities include+ 545 546 547 548 549 550 551 552 553 554 555 556 557 558Primary Actor+ .onsumer, Aacilit3 ! Aacilit3 6anagement *3stem 559Stakeholders and Interests+ .ustomer, (tilit3, possi le 3rd 0art3 %& $ggregator 560Preconditions+ 561 562 563 564 565 566 567 568 569 570 571 572Trigger(s)+ 573(tilit3 calls upon resource to e dispatchedCC 1C %istri uted &esource has some preBdefined "nowledge of its capa ilities and constraintsC 2C 1eneration resources are characteri7ed according to+ aC T3pe of resource G =atts, 8$&*, <7, 8olts, other C 0rice of resource cC /mission characteristics dC $vaila ilit3 eC %uration fC &esponse time gC &amp time 3C (tilit3 is made aware of resources /@pected "= ! "=< o .ontingenc3 &eserve $ncillar3 *ervices o 8$& *upport >8oltage .ontrol? o 8oltage rideBthrough >sta3 connected, disconnect, provide 8oltage .ontrol *ervice? o Are)uenc3 regulation $ssociated costs /missions characteristics $vaila ilit3, %uration o &esponse Time o &amp Time
/1.00, 29 "ct'ber 2009

70
2D

71
574"ain S#ccess Scenario 575 1C 1rid relia ilit3 is maintained 3 operation of resource 576Post-Condition 577.onsumer is credited for performing re)uested service ! dispatching of resource 578Activity !iagram+
act D@1 7 ,dv ertise D'R Ca abi!ities D' /ontrollin2 &ntity / -E)
Registered Resource
'esource
Register Resource
579
580
/igure .+ 0 D@1 ,dvertise D'R Ca abi!ities
5816$2$8 D5 7 &slandin" 583Context+ .onsumer has ade)uate onsite generation!storage resources to operate critical loads 584independent from the gridC %uring times of grid insta ilit3 or %& events, the consumer can 585isolate the premise from the grid completel3 while maintaining operationsC 586Primary Actor+ .onsumer, Aacilit3 ! Aacilit3 6anagement *3stem 587Stakeholders and Interests+ .ustomer, (tilit3, possi le 3rd 0art3 %& $ggregator 588Preconditions+ 589 590 1C .onsumer has a microBgrid capa le of supporting operations while the grid is down or under stressC
/1.00, 29 "ct'ber 2009
72
582
26

73
591 592Trigger(s)+ 5931rid )ualit3 falls out of spec or a severe %& event is issuedCC 594"ain S#ccess Scenario 595 596 1C .onsumer maintains operation of critical loads during event or outage 2C .onsumer facilit3 is reconnected to the grid when the event or outage has completedC
597Post-Condition 598.onsumer facilit3 is reconnected to the grid and normal operations ensueC 599*se Case !iagram+
uc D@3 7 2s!anding
Disconnect from @rid @rid ,sset (Resource" @$recedesA Shed non7critica! !oads
@$recedesA
Ram !oca! generation
Islandin2 is nor3ally considered to "e $art of Distri"ution %uto3ation <D%=. Hhile it 3ay 3a:e use of Distri"uted +eneration assets, 4hen an outa2e event occurs the islandin2 ca$a"ility 3ay "e out of sco$e for consideration as $art of De3and 'es$onse si2nalin2 fro3 the .tility or other Ehird ,arty.
600
601
/igure .) 0 D@3 2s!anding
6026$2$9 D5 7 Pro/ide re"ulation ser/ices 604Context+ .onsumer has generation devices capa le of providing regulation services such as 605reactive power, voltage, and fre)uenc3 regulationC These services ma3 e dispatcha le or 606operated autonomousl3 3 preprogramming of responses to prescri ed conditionsC 607
/1.00, 29 "ct'ber 2009
74
603
2?

75
608Primary Actor+ .onsumer, Aacilit3 ! Aacilit3 6anagement *3stem 609Stakeholders and Interests+ .ustomer, (tilit3, possi le 3rd 0art3 %& $ggregator 610Preconditions+ 611 612 613 614 615Trigger(s)+ 616&egulation service is called upon 3 the utilit3 and dispatched 3 the consumerC #r grid 617conditions invo"e preBprogrammed autonomous responseC 618"ain S#ccess Scenario 619 1C 1rid relia ilit3 and )ualit3 are maintainedC 620Post-Condition 621.onsumer is compensated for dispatch or operation of regulation servicesC 622Activity !iagram+
act D@5 7 &rov ide regu!ation serv ices D' /ontrollin2 &ntity / -E)
1C .onsumer resources have een advertised to the utilit3 for dispatch 2C .onsumer resources have een preprogrammed to operate autonomousl3 according to the utilit3 re)uirementsC
Send Demand Res onse Signa! (&rice or ObA ectiv e" (from D"! #oca$ "eneration) 'esource
Receiv e 'v ent /eedback (from D"4 % urtai$ &torage 'aring)
Reciev e Demand Res onse Signa!
&rov ide Regu!ation Serv ice
&rov ide /eeback if during 'v ent (from D"4 % urtai$ &torage 'aring)
(from D"! #oca$ "eneration)
623
624
/1.00, 29 "ct'ber 2009
76
/igure .# 0 D@5 rovide Regu!ation Services

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed 2@

77
6256$( OP*'ADR U+* CA+*+ for !astDR 626Aast %emand &esponse >Aast%&? is characteri7ed 3 support of fast dispatch fre)uencies ranging 627from 4 seconds to several minutesC #ne of the intended uses is to support some t3pes of ancillar3 628services that re)uire a response in the 4 second to 10 minute rangeC These services ma3 include+ 629 &egulating &eserve 630 ;oad Aollowing or Aast /nerg3 6ar"ets 631 *pinning &eserve 632 :onB*pinning &eserve 633 &eplacement or *upplemental &eserve 634The Aast%& (se .ases are in three areas+ $s3nchronous %ispatch, 0olled %ispatch and 635Telemetr3C
uc /ast DR 2nteractions 9ast D' Interactions
,synchronous Dis atch
&o!!ed Dis atch
DR Contro!!ing 'ntity DR Resource
=e!emetry
636 638
637
/igure .1 0 /ast DR 2nteractions
6396$($# !astDR 7 As-nchronous Dispatch 641Context+ %ispatch of %& *ignals is supported in oth a EpushF and EpullF >aC"CaC .all ac"? 642interaction patternC %& &esources of $s3nchronous %ispatch must e capa le of consuming a 643%ispatch that is sent without a preceding re)uest for dispatchC 644Primary Actors+ %& .ontrolling /ntit3, %& &esource 645Stakeholders and Interests+ (tilit3, .ustomers, and 3rd 0art3 service providers
/1.00, 29 "ct'ber 2009
78
640
29

79
646Preconditions+ 647 648 649 650Trigger(s)+ 651%& /vent has een announced 3 a 6ar"et #perator or (tilit3C 652"ain S#ccess Scenario 653 654 655 657 658Se'#ence !iagram+
sd ,synchronous Dis atch (=w o &arty"
1C The %& .ontrolling /ntit3 and parties representing the %& &esource have enrolled in the same %& 0rogramC
1C %& %ispatch is sent to %& &esourceC 2C &eceipt $c"nowledgement >if re)uested? is sent from &esource to originating %& .ontrolling /ntit3C
656Post-Condition
D' /ontrollin2 &ntity
D' 'esource
Dis$atch<set$oint, dis$atch level, =
%c:no4led2e3ent<=
659
660
/igure .3 0 /ast DR ,synchronous Dis atch (=wo &arty"
6616$($2 !astDR 7 As-nchronous Dispatch :ith Communications ;ierarch663Context+ The $s3nchronous %ispatch can occur through la3ers of service providers such as %& 664$ggregators or .ommunications 4ntermediariesC The latenc3 re)uirements are measured from 665the time of initial dispatch to the point where the re)uested action is performedC 666Primary Actors+ %& .ontrolling /ntit3, %& &esource, %& *ervice 0rovider >4ntermediar3? 667Stakeholders and Interests+ (tilit3, .ustomers, and 3rd 0art3 service providers
/1.00, 29 "ct'ber 2009
80
662
*0

81
668Preconditions+ 669 670 671 672Trigger(s)+ 673%& /vent has een announced 3 a 6ar"et #perator or (tilit3C 674"ain S#ccess Scenario 675 676 677 678 680 681Se'#ence !iagram+
sd ,synchronous Dis atch (w > Comms Heirarchy" D' /ontrollin2 &ntity 4/ %22re2ated /o33unications
1C The %& .ontrolling /ntit3, 4ntermediaries and parties representing the %& &esource have enrolled in the same %& 0rogram
1C %& %ispatch is sent to 4ntermediar3>ies?C 2C %& %ispatch is forwarded to another intermediar3 or the %& &esourceC 3C The %& &esource that actuall3 supplies the service is a le to respond within the re)uired response timeC
679Post-Condition
@act...
/o33unications Inter3ediary
D' 'esource
Dis$atch<= %c:no4led2e<= Dis$atch<= %c:no4led2e<=
682
683
/igure .5 0 /ast DR ,synchronous Dis atch (with Communications Hierarchy"
6846$($( !astDR 7 As-nchronous Dispatch :ith oad A""re"ation 686Context+ The $s3nchronous %ispatch can occur through la3ers of service providers such as %& 687$ggregators or .ommunications 4ntermediariesC The latenc3 re)uirements are measured from 688the time of initial dispatch to the point where the re)uested action is performedC
/1.00, 29 "ct'ber 2009
82
685
*1

83
689Primary Actors+ %& .ontrolling /ntit3, %& &esource, %& *ervice 0rovider >$ggregator? 690Stakeholders and Interests+ (tilit3, .ustomers, and 3rd 0art3 service providersC 691Preconditions+ 692 693 694 695Trigger(s)+ 696%& /vent has een announced 3 a 6ar"et #perator or (tilit3C 697"ain S#ccess Scenario 698 699 700 701 702 704 705Se'#ence !iagram+
sd ,synchronous Dis atch (w > 4oad ,ggregation" %22re2ated D' 'esouce
1C The %& .ontrolling /ntit3, %& $ggregators and parties representing the %& &esource have enrolled in the same %& 0rogramC
1C %& %ispatch is sent to $ggregator>s?C 2C %& %ispatch is forwarded >with deBaggregated re)uirements applied? to another aggregator or the %& &esourceC 3C The %& &esource that actuall3 supplies the service is a le to respond within the re)uired response time
703Post-Condition
D' 'esource <%22re2ator=
D' 'esource
Dis$atch<= %c:no4led2e3ent<= Dis$atch<= %c:no4led2e3ent<=
706
707
/igure .6 0 /ast DR ,synchronous Dis atch (with 4oad ,ggregation"
7086$($) !astDR 7 Polled Dispatch 7 T:o Part709
/1.00, 29 "ct'ber 2009

84
*2

85
710Context+ %ispatch of %& *ignals is supported in oth a EpushF and EpullF >aC"CaC .all ac"? 711interaction patternC %& &esources of a 0olled %ispatch will re)uest the latest %ispatch from the 712%& .ontrolling /ntit3C 713Primary Actors+ %& .ontrolling /ntit3, %& &esource 714Stakeholders and Interests+ (tilit3, .ustomers, and 3rd 0art3 service providers 715Preconditions+ 716 717 718 719Trigger(s)+ 720%& /vent has een announced 3 a 6ar"et #perator or (tilit3CC 721"ain S#ccess Scenario 722 723 725 726Se'#ence !iagram+
sd &o!!ed Dis atch (=w o &arty"
1C The %& .ontrolling /ntit3 and parties representing the %& &esource have enrolled in the same %& 0rogramC
1C %& &esource re)uests latest %& %ispatch from %& .ontrolling /ntit3C 2C %& %ispatch is sent to %& &esourceC
724Post-Condition
D' /ontrollin2 &ntity Dis$atch 'e(uest<= Dis$atch 'es$onse<=
D' 'esource
727
728
/igure -% 0 /ast DR &o!!ed Dis atch (=wo &arty"
7296$($) !astDR 7 Polled Dispatch :ith Communications ;ierarch- (Pull) 731Context+ The 0olled %ispatch can occur through la3ers of service providers such as %& 732$ggregators or .ommunications 4ntermediariesC The latenc3 re)uirements are measured from 733the time of initial dispatch to the point where the re)uested action is performedC :ote that the 734EpullF scenario is onl3 applica le to the interaction with the &esource associated with the final 735end point in this caseC 736Primary Actor+ %& .ontrolling /ntit3, %& &esource, %& *ervice 0rovider >4ntermediar3? 737Stakeholders and Interests+ (tilit3, .ustomers, and 3rd 0art3 service providers
/1.00, 29 "ct'ber 2009
86
730
**

87
738Preconditions+ 739 740 741 742Trigger(s)+ 743%& /vent has een announced 3 a 6ar"et #perator or (tilit3C 744"ain S#ccess Scenario 745 746 747 748 749 751 752Se'#ence !iagram+
sd &o!!ed Dis atch (w > Comms Hierarchy" D' /ontrollin2 &ntity 4/ %22re2ated /o33unications
1C The %& .ontrolling /ntit3, 4ntermediaries and parties representing the %& &esource have enrolled in the same %& 0rogramC
1C %& %ispatch is sent to 4ntermediar3 2C %& &esource re)uests the latest %ispatchC 3C %& %ispatch is forwarded to the %& &esourceC 4C The %& &esource that actuall3 supplies the service is a le to respond within the re)uired response time
750Post-Condition
@act...
D' 'esource
Dis$atch<= %c:no4led2e<= Dis$atch 'e(uest<= Dis$atch 'es$onse<=
753
754
/igure -. 0 /ast DR &o!!ed Dis atch (with Communications Hierarchy"
7556$($0 !astDR 7 Polled Dispatch :ith oad A""re"ation (Pull at *nd Point Onl-) 757Context+ The 0olled %ispatch can occur through la3ers of service providers such as %& 758$ggregators or .ommunications 4ntermediariesC The latenc3 re)uirements are measured from 759the time of initial dispatch to the point where the re)uested action is performedC :ote that the
/1.00, 29 "ct'ber 2009
88
756
*,

89
760EpullF scenario is onl3 applica le to the interaction with the &esource associated with the final 761end point in this caseC 762Primary Actor+ %& .ontrolling /ntit3, %& &esource, %& *ervice 0rovider >$ggregator? 763Stakeholders and Interests+ (tilit3, .ustomers, and 3rd 0art3 service providers 764Preconditions+ 765 766 767 768Trigger(s)+ 769%& /vent has een announced 3 a 6ar"et #perator or (tilit3C 770"ain S#ccess Scenario 771 772 773 774 775 777 778Se'#ence !iagram+
sd &o!!ed Dis atch (w > 4oad ,ggregation case ." %22re2ated D' 'esouce
1C The %& .ontrolling /ntit3, $ggregators and parties representing the %& &esource have enrolled in the same %& 0rogramC
1C %& %ispatch is sent to $ggregator 2C %& &esource re)uests the latest %ispatchC 3C %& %ispatch is sent to the %& &esourceC 4C The %& &esource that actuall3 supplies the service is a le to respond within the re)uired response time
776Post-Condition
D' 'esource
Dis$atch<= %c:no4led2e3ent<= Dis$atch 'e(uest<= Dis$atch 'es$onse<=
779
780
/igure -- 0 /ast DR &o!!ed Dis atch (with 4oad ,ggregation"
/1.00, 29 "ct'ber 2009

90
*D

91
7816$($6 !astDR 7 Polled Dispatch :ith oad A""re"ation (Pull at *ach e/el) 782Context+ The 0olled %ispatch can occur through la3ers of service providers such as %& 783$ggregators or .ommunications 4ntermediariesC The latenc3 re)uirements are measured from 784the time of initial dispatch to the point where the re)uested action is performedC :ote that the 785EpullF scenario is onl3 applica le to the interaction with oth $ggregators and the &esource 786associated with the final end point in this caseC 787Primary Actor+ %& .ontrolling /ntit3, %& &esource, %& *ervice 0rovider >$ggregator? 788Stakeholders and Interests+ (tilit3, .ustomers, and 3rd 0art3 service providers 789Preconditions+ 790 791 792 793Trigger(s)+ 794%& /vent has een announced 3 a 6ar"et #perator or (tilit3C 795"ain S#ccess Scenario 796 797 798 799 800 802 803Se'#ence !iagram+ 5C %& %ispatch is sent to $ggregator 6C %& &esource re)uests the latest %ispatchC 7C %& %ispatch is sent to the %& &esourceC 8C The %& &esource that actuall3 supplies the service is a le to respond within the re)uired response time 1C The %& .ontrolling /ntit3, $ggregators and parties representing the %& &esource have enrolled in the same %& 0rogramC
801Post-Condition
/1.00, 29 "ct'ber 2009

92
*6

93
sd &o!!ed Dis atch (w > 4oad ,ggregation case -"
%22re2ated D' 'esouce
D' /ontrollin2 &ntity Dis$atch 'e(uest<= Dis$atch 'es$onse<=
D' 'esource
Dis$atch 'e(uest<= Dis$atch 'es$onse<=
804
805
/igure -+ 0 /ast DR &o!!ed Dis atch (with 4oad ,ggregation &u!! at 'ach 4eve!"
8066$($8 !astDR 7 Telemetr807Context+ Aast%& Telemetr3 (se .ases represent the upstream telemetr3 from the %& &esource 808and is used 3 the %& .ontrolling entit3 to verif3 and monitor the response %& &esource to the 809dispatch in real timeC 4n the simplest case, Telemetr3 is provided from the %& &esource to the 810%& .ontrolling /ntit3C 811Primary Actors+ %& .ontrolling /ntit3, %& &esourceC 812Stakeholders and Interests+ (tilit3, .ustomer 813Preconditions+ 814 815 816 817Trigger(s)+ 818%& &esource receives %& /vent message with Telemetr3 re)uirementsC 819"ain S#ccess Scenario 820 821 822 824 1C %& &esource sends a Telemetr3 6essage to the %& .ontrolling /ntit3 within an agreed upon intervalC 2C %& .ontrolling /ntit3 sends ac"nowledgment to %& &esourceC 1C %& .ontrolling /ntit3 and %& &esource are enrolled in the same %& 0rogramC 2C %& .ontrolling /ntit3 has successfull3 sent the %& &esource a %& /vent 6essageC
823Post-Condition
/1.00, 29 "ct'ber 2009

94
*?

95
825Se'#ence !iagram+
sd =e!emetry
D' /ontrollin2 &ntity Eele3etry<= %c:no4led2e3ent<=
D' 'esource
826
827
/igure -) 0 /ast DR =e!emetry
8286$($9 !astDR 7 Telemetr- :ith Communications ;ierarch829Context+ Aast%& Telemetr3 (se .ases represent the upstream telemetr3 from the %& &esource 830and is used 3 the %& .ontrolling entit3 to verif3 and monitor the response %& &esource to the 831dispatch in real timeC Telemetr3 with a .ommunications <ierarch3 is the case where the %& 832/vent message was sent via an 4ntermediar3 as defined in (se .ase EAast%& G $s3nchronous 833%ispatch with .ommunications <ierarch3F >either E0ushF or E0ullF?C 834Primary Actors+ %& .ontrolling /ntit3, %& &esource, 4ntermediar3 835Stakeholders and Interests+ .onsumers, (tilit3, %& *ervice 0roviders 836Preconditions+ 837 838 839 840 841Trigger(s)+ 842%& &esource has received a %& /vent 6essage via an 4ntermediar3C 843"ain S#ccess Scenario 844 845 846 847 848 1C %& &esource sends Telemetr3 6essage to .ommunications 4ntermediar3C 2C .ommunications 4ntermediar3 sends $c"nowledgment 6essage to %& &esourceC 3C .ommunications 4ntermediar3 sends Telemetr3 6essage to %& .ontrolling /ntit3C 4C %& .ontrolling /ntit3 sends $c"nowledgement 6essage to .ommunications 4ntermediar3C 1C %& .ontrolling /ntit3 and %& &esource are enrolled in the same %& 0rogramC 2C %& .ontrolling /ntit3 has successfull3 sent the %& &esource a %& /vent 6essage via an 4ntermediar3C
849Post-Condition 850Se'#ence !iagram+
/1.00, 29 "ct'ber 2009

96
*@

97
sd =e!emetry (w > Comms Heirarchy"
@act... "pen#D$ B&siness and User $e1&irements D'c&ment
D' /ontrollin2 &ntity 4/ %22re2ated /o33unications
D' /ontrollin2 &ntity Eele3etry<= %c:no4led2e<=
D' 'esource
Eele3etry<= %c:no4led2e<=
851
852
/igure -# 0 /ast DR =e!emetry
8536$($< !astDR 7 Telemetr- :ith oad A""re"ation 854Context+ Aast%& Telemetr3 (se .ases represent the upstream telemetr3 from the %& &esource 855and is used 3 the %& .ontrolling entit3 to verif3 and monitor the response %& &esource to the 856dispatch in real timeC Telemetr3 with a .ommunications <ierarch3 is the case where the %& 857/vent message was sent via an 4ntermediar3 as defined in (se .ase EAast%& G $s3nchronous 858%ispatch with ;oad $ggregationF >either E0ushF or E0ullF?C 859Primary Actors+ %& .ontrolling /ntit3, %& &esource, %& $ggregator 860Stakeholders and Interests+ .onsumers, (tilit3, %& *ervice 0roviders 861Preconditions+ 862 863 864 865 866 867Trigger(s)+ 868%& &esource has received a %& /vent 6essage via a %& $ggregatorC 869"ain S#ccess Scenario 870 871 1C %& &esource sends Telemetr3 6essage to %& $ggregatorC 2C %& $ggregator sends $c"nowledgment 6essage to %& &esourceC 1C %& .ontrolling /ntit3, %& $ggregator and %& &esource are enrolled in the same %& 0rogramC 2C %& .ontrolling /ntit3 has successfull3 sent the %& &esource a %& /vent 6essage via the %& $ggregatorC
/1.00, 29 "ct'ber 2009

98
*9

99
872 873 874 876
3C %& $ggregator sends Telemetr3 6essage to %& .ontrolling /ntit3C 4C %& .ontrolling /ntit3 sends $c"nowledgement 6essage to .ommunications 4ntermediar3C
875Post-Condition 877Se'#ence !iagram+

sd =e!emtry (w > 4oad ,ggregation" %22re2ated D' 'esouce
D' /ontrollin2 &ntity Eele3etry<= %c:no4led2e3ent<=
D' 'esource
Eele3etry<= %c:no4led2e3ent<=
878
879
/igure -1 0 /ast DR =e!emetry (with 4oad ,ggregation"
/1.00, 29 "ct'ber 2009

100
,0

OpenADR Phase 2 Business and User Requirements r1.0

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenADR Phase 2 Business and User Requirements r1.0

Uploaded by

Copyright:

Available Formats

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Phase: Created: Last Update: Print Date: By: Distrib&ti'n: 2.00 March 29, 2011 September 6, 2011 S !

Systems "pen#D$ %eam P&b(ic

OpenADR Business and User Requirements Document

- C'pyri.ht 2011, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

- C'pyri.ht 2011, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

61Date of this revision: May 17, 2011 62

7/22/2011 +erald +ray 5/1/2011 Bruce Bartell

.3 .31 .31 .> .>*

5/23/2011 +erald +ray 5/23/2011 Bruce Bartell 9/1/2011 Bruce Bartell

- C'pyri.ht 2011, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

- C'pyri.ht 2011, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

722.0 OPENADR BUSINESS RATIONALE.................................................................................................... 4

783.0 OPENADR VISION................................................................................................................................ 7

824.0 OPENADR SCOPE............................................................................................................................... 8

865.0 OPENADR CONTEXT........................................................................................................................... 9

886.0 OPENADR USE CASES..................................................................................................................... 10

/1.00, 29 "ct'ber 2009

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

/1.00, 29 "ct'ber 2009

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

#&t'mated Data 39chan.e 4#D35 #&t'matic enerati'n C'ntr'( 4# C5

Ser/ice De(i/ery P'int 4SDP5

/1.00, 29 "ct'ber 2009

UC#0&. "penS S !Systems

/1.00, 29 "ct'ber 2009

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

/1.00, 29 "ct'ber 2009

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

<astD$ sha(( s&pp'rt D$ $es'&rces dispatched in the 1000Fs.

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

3C %istri uted 1eneration >%1?5 4C *ecurit3

imitations and *4clusions

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

/1.00, 29 "ct'ber 2009

- C'pyri.ht 2009, UC#(&. "penS S !Systems, #(( $i.hts $eser/ed

UC#0&. "penS S !Systems

"pen#D$ B&siness and User $e1&irements D'c&ment

.$% ,dministrate DR &rogram