SG-Systems

6
Knoxville, TN October 20, 2009 SG-Systems SG-Systems OpenADR Task Force Breakout Session Report Outs

description

SG-Systems. OpenADR Task Force Breakout Session Report Outs. Suggest DR Use Case Matrix. Use Case Development Accomplishment. DR Use Case Discussion Topics. 4.4 Broadcast “Pricing” (Retail) for DR Purpose – The term pricing will change to more generic Reference Architecture - PowerPoint PPT Presentation

Transcript of SG-Systems

Page 1: SG-Systems

Knoxville, TN October 20, 2009

SG-SystemsSG-Systems

OpenADR Task Force

Breakout Session Report Outs

Page 2: SG-Systems

Knoxville, TN October 20, 2009

Suggest DR Use Case Matrix

uc Use Case Matrix

3.0 Administrate DR Resource

3.1 Administrate Bulk Power DR Resource

3.2 Administrate Distribution DR

Resource

1.0 Administrate DR Program

3.1.1 Registor DR Resource

3.1.4 Administrate DR Asset (Direct)

3.1.2 Declare DR Resource Status

4.0 Execute DR Ev ent

3.1.3 Remov e DR Resource

1.1 Create DR Program

1.2 Udpate DR Program

1.3 Remov e DR Program

2.0 Administrate Customer Entity for DR

4.1.1 Adv anced Notification for DR

(Bulk Power)

4.1.2 Update a DR Ev ent (Bulk Power)

4.1.3 Cancel a DR Ev ent (Bulk Power)

4.1.4 DR Resource Confirmation (Bulk

Power)

4.2.1 Adv anced Notifiation for DR

(Distribution)

4.3 Broadcast Pricing (Wholesale)

for DR Purpose

4.2.2 Update a DR Ev ent (Distribution)

4.2.3 Cancel a DR Ev ent (Distribution)

4.2.4 DR Resource Confirmation (Distribution)

4.4 Broadcast Pricing (Retail) for DR Purpose

4.5 Dispatch DR Instructions (Bulk

Power)

4.7 DR Direct Load Control (Distribution)

4.5.1 Monitor DR Ev ent (Bulk)

Administrate DER for DR Purpose

4.9 Operational Coordination between Transmission and

Distribution and DR Resources

4.7.1 Monitor DR Ev ent (Distribution)

5.0 Post DR Ev ent Management

4.8 DR Resource Ev ent Execution

5.1 Post DR Ev ent M&V (Wholesale)

5.2 Post DR Ev ent M&V (Retail -

Regulated)

5.3 Post DR Ev ent &V (Retail - Deregulated)

5.4 DR Ev ent Financial Settlement

4.1 Notify DR Ev ent (Bulk Power)

4.2 Notify DR Ev ent (Distribution)

DR Signals Use Cases Diagram - (NAESB Smart Grid Task Force)

The purpose of this diagram is to show all relevant use cases under the scope of NIST PAP09 (Standard DR Signals) and shall cover DR programs at both the wholesale and retial market level. The focus of the use cases are interactions between the Smart Grid Domains defined by the NIST Smart Grid Interoperability Standards Roadmap.

Verison 0.1Date: October 14, 2009

3.1.5 DR Bidding

4.6 Dispatch DR Instructions (Distribution)

«include»

«include»«include»

«include»

«include» «include»

«invokes»

«include»«include»

«include»«include»

«invokes»

«precedes»

«include»

«include»

«include»

«include»

«include»

«include»«include»«include»

«precedes»«precedes»

«extend»

«include»«include»«include»

«include»«include»«include»

«include»«extend» «extend»

«include»

«precedes»

«invokes»

«include»«include»«include» «include»«include»«include»

«include»

«precedes»«precedes»

«include»

«include»

Page 3: SG-Systems

Knoxville, TN October 20, 2009

Use Case Development Accomplishment

Use Case # Use case description Note

4.2 Notify DR Event SD and Interaction - Completed

4.2.1 Advanced Notification for DR SD and Interaction - Completed

4.2.2 Update a DR Event SD and Interaction - Completed

4.2.3 Cancel a DR Event SD and Interaction - Completed

4.2.4 DR Resource Confirmation SD and Interaction - Completed

4.7 Direct Load Control SD and Interaction - Completed

4.7.1 Monitor DR Event SD and Interaction - Completed

Page 4: SG-Systems

Knoxville, TN October 20, 2009

DR Use Case Discussion Topics

• 4.4 Broadcast “Pricing” (Retail) for DR Purpose – The term pricing will change to more generic

• Reference Architecture• DR acknowledgement and confirmation• Advanced Notification for DR• Adding testing use case• DR Resource Confirmation (DR Resource,

Asset, PHEV)• Direct Load Control – randomization, monitor

protocol

Page 5: SG-Systems

Knoxville, TN October 20, 2009

Next steps and next encounter date/time

• Next steps– Refine use cases developed– Provide draft use cases to sub-group leader (Joe) by Friday,

October 21st

– Refine combined retail and wholesale use cases in the next two weeks

– Finalized use case and framework document by first week of November

– Continue to work with NAESB, NIST and OASIS on SRS and Service Definition

• Next encounter date/time– Every Thursday joint conference call with NAESB (12-2:00

central time)– NAESB SGTF sub-group F2F meeting in New England

Page 6: SG-Systems

Knoxville, TN October 20, 2009

If you have comments and/or wish to join and contribute to the OpenADR Task Force effort,

please contact

Albert Chiu or Ed Koch

at [email protected] or [email protected]