Table of Contents

Model Detail	4
Model 	4
NAESB Demand Response Use Cases for NIST Smart Grid 	4
<anonymous>	5
Actors 	6
Commercial Customer	6
Curtailment Service Provider	6
DMS	7
DR Aggregator	9
DR Asset	10
DR Asset/Resource Owner	11
DR Controlling Entity	12
DR Resource	15
DRMS	17
Demand Response Program	18
Distributed Energy Resource	19
Distribution Company	19
Distribution Operator	19
Electricity Consumer	20
Energy Service Provider	21
Industrial Customer	22
Load Serving Entity	22
Merchant Operator	23
Metering Agent	23
Regulator	24
Residential Customer	24
System and Market Operator	24
DR Use Cases 	25
1.0 Administrate DR Program 	26
1.0 Administrate DR Program	27
1.1 Create DR Program	28
1.2 Udpate DR Program	30
1.3 Remove DR Program	30
2.0 Administrate Customer for DR 	31
2.0 Administrate Customer for DR	32
2.1 Register / Enroll Customer for DR Program	33
2.2 Update Customer Identity	35
2.3 Remove Customer from DR Program	35
3.0 Administrate DR Resource 	36
3.0 Administrate DR Resource	37
3.1 Administrate Bulk Power DR Resource	38
3.2 Administrate Distribution DR Resource	38
3.2.1 Declare DR Resource	40
3.2.2 Register DR Resource	41
3.2.3 Remove DR Resource	43
3.2.4 Administrate DR Asset (Direct)	44
3.2.6 DR Bidding	44
3.2.5 Administrate DER for DR Purpose	45
4.0 Execute DR Event 	46
4.0 Execute DR Event	46
4.1 Notify DR Event (Bulk Power)	48
4.1.1 Advanced Notification for DR (Bulk Power)	49
4.1.2 Update a DR Event (Bulk Power) 	49
4.1.3 Cancel a DR Event (Bulk Power)	50
4.1.4 DR Resource Confirmation (Bulk Power)	50
4.2 Notify DR Event (Distribution)	51
4.2.1 Advanced Notification for DR (Distribution)	52
4.2.2 Update a DR Event (Distribution)	54
4.2.3 Cancel a DR Event (Distribution)	55
4.2.4 DR Resource Confirmation (Distribution)	56
4.3 Broadcast Pricing (Wholesale) for DR Purpose	58
4.4 Broadcast Pricing (Retail) for DR Purpose	58
4.5 Dispatch DR Instructions (Bulk Power)	60
4.5.1 Monitor DR Event (Bulk) 	61
4.6 Dispatch DR Instructions (Distribution)	61
4.7 DR Direct Load Control (Distribution)	63
4.7.1 Monitor DR Event (DR Resource)	64
4.7.2 Monitor DR Event (DR Asset)	66
4.8 DR Event Execution	67
4.8.1 DR Execution - Dynamic Price-Based	68
4.8.2 DR Execution - Notification Based	69
4.8.2 DR Exedcution - Direct Load Control	70
Distribution Operator	71
Load Forecast	71
Load Forecast	72
4.9 Operational Coordination between Transmission and Distribution and DR Resources	73
Adjust Schedule	74
Apply Retail Uplift Charges	75
Assess Congestion Uplift Charges	75
Check againts circuit operating limits	76
Check for Distribution Circuit Contraints	77
Identify Impacted Circuits	78
Load Forecast by Circuit	79
Locational Wholesale Prices	80
Specify Load Profile	80
Wholesale Locational Prices	81
5.0 Post DR Event Management 	81
5.0 Post DR Event Management	82
5.1 Post DR Event M&V / Settlement (Open Wholesale, No Open Retail)	83
<anonymous>	84
<anonymous>	85
<anonymous>	85
<anonymous>	86
<anonymous>	87
5.2 Post DR Event M&V / Settlement (No Open Wholesale, No Open Retail)	87
<anonymous>	88
<anonymous>	88
<anonymous>	89
5.3 Post DR Event M&V / Settlement (Open or Not Open Wholesale, Open Retail)	89
<anonymous>	91
<anonymous>	92
<anonymous>	93
<anonymous>	94
<anonymous>	94

Model Documentation
Model Detail
This document provides a complete overview of all element details. For simpler and more focused reports, simply copy this initial template and turn off the sections not required. 

Model 
Type:		Package 
Status:		Proposed. Version . Phase 1.0.
Package:	
Detail:		Created on 10/27/2009. Last modified on 10/27/2009
GUID:		{D9BDCAE3-2D06-438b-B1D1-CBFAF77D76F0}

NAESB Demand Response Use Cases for NIST Smart Grid 
Type:		Package 
Status:		Proposed. Version . Phase 1.0.
Package:	Model
Detail:		Created on 9/10/2009. Last modified on 9/10/2009
GUID:		{AA419E10-2506-472d-9397-5F001C9471A3}
This package contains the set of Use Cases for Demand Response scenarios which may be implmented within a NIST standard Smart Grid 

NAESB-NIST-SMART-GRID-DR-USE-CASES - (Use Case diagram) 
Created By:	rbrooks on 11/19/2005
Last Modified:	10/26/2009
Version:		1.0. Locked: False
GUID:		{CC9376ED-195E-4db9-B037-804D2DA11B45}

Figure: 1

<anonymous>
Type:		Note    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	NAESB Demand Response Use Cases for NIST Smart Grid     Keywords:   
Detail:		Created on 1/5/2006.  Last modified on 1/5/2006.
GUID:		{35E123DD-5827-4e0a-92AE-A39B6106D265}

Actors are the users of the system being modeled. Each Actor will have a well-defined role, and in the context of that role have useful interactions with the system.

A person may perform the role of more than one Actor, although they will only assume one role during one use case interaction.

An Actor role may be performed by a non-human system, such as another computer program.

Connections
Connector	Source	Target	Notes	
NoteLink   
 
	Public  
Actors
 	Public  
<anonymous>

 

Actors 
Type:		Package 
Status:		Proposed. Version 1.0. Phase 1.0.
Package:	NAESB Demand Response Use Cases for NIST Smart Grid
Detail:		Created on 11/19/2005. Last modified on 11/19/2005
GUID:		{E4B9A5DB-DB49-4408-91B2-9D1132FEC14D}

Actors - (Use Case diagram) 
Created By:	rbrooks on 11/19/2005
Last Modified:	10/27/2009
Version:		1.0. Locked: False
GUID:		{4E93A8E4-D0E6-49f0-A838-D69538F9613C}

Figure: 2

Commercial Customer
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{D3F02B4B-FCFD-469f-A357-F31DF8B7C383}

 

Curtailment Service Provider
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{ECBDDA25-7463-4ea0-9047-E17F97594568}

 

DMS
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{5B920E17-E0F6-4e58-9F53-2DD7F651215A}

 

Connections
Connector	Source	Target	Notes	
Sequence  Load Forecast by Circuit 
Source -> Destination 
	Public  
Load Forecast
 	Public  
DMS

Sequence  Load Profile Forecast by Circuit 
Source -> Destination 
	Public  
Load Forecast by Circuit
 	Public  
DMS

Sequence  DR Control schedule by Circuit 
Source -> Destination 
	Public  
DRMS
 	Public  
DMS

Sequence  DR Schedule by Circuit 
Source -> Destination 
	Public  
DRMS
 	Public  
DMS

Sequence  Check Againts Circuit Limits 
Source -> Destination 
	Public  
DMS
 	Public  
DMS

Sequence  Check Schedule Against Circuit Limits 
Source -> Destination 
	Public  
DMS
 	Public  
DMS

Sequence  Monitoring and Alarms 
Source -> Destination 
	Public  
DMS
 	Public  
Distribution Operator

Sequence  Load Forecast by Circuit 
Source -> Destination 
	Public  
Load Forecast
 	Public  
DMS

Sequence  Monitor - Alarams 
Source -> Destination 
	Public  
DMS
 	Public  
Distribution Operator

Sequence  No Violations, Control Schedule Approved 
Source -> Destination 
	Public  
DMS
 	Public  
DRMS

Sequence  No Violations, Schedule Approved 
Source -> Destination 
	Public  
DMS
 	Public  
DRMS

Sequence  Check Against Circuit Operating Limits 
Source -> Destination 
	Public  
DMS
 	Public  
DMS

Sequence  Monitor and Alarms 
Source -> Destination 
	Public  
DMS
 	Public  
Distribution Operator

Sequence  Manual Interventions 
Source -> Destination 
	Public  
Distribution Operator
 	Public  
DMS

Sequence  Manual Interventions 
Source -> Destination 
	Public  
Distribution Operator
 	Public  
DMS

Sequence  Limit Violations, Suggested  Schedule Adjustments 
Source -> Destination 
	Public  
DMS
 	Public  
DRMS

Sequence  Limit Violations - Suggested Adjustments 
Source -> Destination 
	Public  
DMS
 	Public  
Energy Service Provider

Sequence  Limit Violations, Suggested Schedule Adjustments 
Source -> Destination 
	Public  
DMS
 	Public  
DRMS

 

DR Aggregator
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 9/10/2009.  Last modified on 9/10/2009.
GUID:		{17E688E7-A7CD-4040-A848-2C0F539A984D}

An entity that has acquired curtailment rights from electricity consumers and manages the aggregate amount of capacity that is curtailable as an eligible energy or capacity resource to participate in Demand Response programs. 

Connections
Connector	Source	Target	Notes	
UseCaseLink   
Source -> Destination 
	Public  
DR Aggregator
 	Public  
3.2 Administrate Distribution DR Resource

Association   
Unspecified 
	Public  
DR Aggregator
 	Public  
2.0 Administrate Customer for DR

Association   
Unspecified 
	Public  
DR Aggregator
 	Public  
1.0 Administrate DR Program

Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
Load Serving Entity
 	Public  
DR Aggregator

Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
DR Aggregator
 	Public  
DR Resource

 

DR Asset
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 9/10/2009.  Last modified on 9/10/2009.
GUID:		{8EA0EA8D-089E-4fe1-8620-2CDB010A2D31}

An energy resource that is capable of shedding load in response to Demand Response Events, Electricity Price Signals or other system events (e.g. under frequency detection).

Examples of Demand Response Assets are: Smart Appliances, entire buildings that are under the control of an Energy Management System, Electric Vehicles.

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
DR Asset

Association   
Unspecified 
	Public  
4.6 Dispatch DR Instructions (Distribution)
 	Public  
DR Asset

Association   
Unspecified 
	Public  
4.7 DR Direct Load Control (Distribution)
 	Public  
DR Asset

Sequence  asset load control command 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset

Sequence  DR Asset State 
Source -> Destination 
	Public  
DR Asset
 	Public  
DR Controlling Entity

Sequence  acknowledgement 
Source -> Destination 
	Public  
DR Asset
 	Public  
DR Controlling Entity

 

DR Asset/Resource Owner
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{1E69EEF6-8EFD-4aff-ABB1-D8350075C100}

The entity that is reponsible for the DR Resource or Asset.

Connections
Connector	Source	Target	Notes	
UseCaseLink   
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
3.2 Administrate Distribution DR Resource

Association   
Unspecified 
	Public  
4.6 Dispatch DR Instructions (Distribution)
 	Public  
DR Asset/Resource Owner

Association   
Unspecified 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
DR Asset/Resource Owner

Sequence  Remove DR Resource Message 
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
DR Controlling Entity

Sequence  DR Resource Declaration 
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
DR Controlling Entity

Sequence  DR Resource Registration Message 
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
DR Controlling Entity
 	Information required to register a DR Resource
 	
Sequence  Request for Bids 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  Acknowledgement 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  Acknowledgement 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  Acknowledgement 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  DR Resource Bid 
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
DR Controlling Entity

Sequence  bid accept/reject 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

 

DR Controlling Entity
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{08267450-3751-4c13-8934-761703455EE2}

This is a generalized actor class and represents all the different entities that may need to manage and interact with retail DR resources. It includes the followinng actors:
•	Distribution Company
•	Load Serving Entity
•	DR Aggregator

Connections
Connector	Source	Target	Notes	
UseCaseLink   
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
3.2 Administrate Distribution DR Resource

Sequence  DR Resource Confirmation 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity

Sequence  Remove DR Resource Message 
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
DR Controlling Entity

Sequence  DR Resource Declaration 
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
DR Controlling Entity

Sequence  DR Resource Registration Message 
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
DR Controlling Entity
 	Information required to register a DR Resource
 	
Sequence  asset load control command 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset

Sequence  DR Resource Usage 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity

Sequence  DR Asset State 
Source -> Destination 
	Public  
DR Asset
 	Public  
DR Controlling Entity

Sequence  DR Event Notification 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Resource

Sequence  DR dispatch instructions 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Resource

Sequence  Update DR Event 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Resource

Sequence  Cancel DR event 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Resource

Sequence  Request for Bids 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  DR Resource Confirmation 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity
 	See the DR Resource Confirmation use case
 	
Sequence  Acknowledgement 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  Acknowledgement 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  Acknowledgement 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  acknowledgement 
Source -> Destination 
	Public  
DR Asset
 	Public  
DR Controlling Entity

Sequence  acknowledgement 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity

Sequence  Message Receipt Acknowledgement 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity

Sequence  DR Resource Bid 
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
DR Controlling Entity

Sequence  DR Resource Confirmation 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity
 	See DR Resource Confirmation use case
 	
Sequence  bid accept/reject 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Asset/Resource Owner

Sequence  DR Resource Confirmation 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity
 	See the DR Resource Confirmation use case

DR Resource
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 9/10/2009.  Last modified on 9/11/2009.
GUID:		{22717FF2-D1A2-4d73-BCAE-7C5F4E375E91}

Is similar to a DR Asset in that it is capable of shedding load in response to a triggering event. Unlike a DR Asset, which is autonomous, a DR Resource may consist of multiple DR Assets that have been aggregated to form a larger capacity or energy resource.

An apartment building with multiple electricity consumers, each one having one or more DR Assets may be considered one large DR Resource by aggregating the total load shedding capacity of all the DR Assets in the Apartment Building and representing the sum total of this capacity as one DR Resource.

A DR Resource may also consist of different types of Assets (e.g. A wind Turbine and an electric motor that work in combination to meet DR program obligations).

Connections
Connector	Source	Target	Notes	
Sequence  DR Resource Confirmation 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity

Sequence  DR Resource Usage 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity

Sequence  DR Event Notification 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Resource

Sequence  DR dispatch instructions 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Resource

Sequence  Update DR Event 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Resource

Sequence  Cancel DR event 
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
DR Resource

Sequence  DR Resource Confirmation 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity
 	See the DR Resource Confirmation use case
 	
Sequence  acknowledgement 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity

Sequence  Message Receipt Acknowledgement 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity

Sequence  DR Resource Confirmation 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity
 	See DR Resource Confirmation use case
 	
Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
DR Aggregator
 	Public  
DR Resource

Sequence  DR Resource Confirmation 
Source -> Destination 
	Public  
DR Resource
 	Public  
DR Controlling Entity
 	See the DR Resource Confirmation use case
 	
Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
Load Serving Entity
 	Public  
DR Resource

Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
System and Market Operator
 	Public  
DR Resource

 

DRMS
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{8AC5521A-88F5-4b41-A374-83D79237F712}

 

Connections
Connector	Source	Target	Notes	
Sequence  DR Control schedule by Circuit 
Source -> Destination 
	Public  
DRMS
 	Public  
DMS

Sequence  DR Schedule by Circuit 
Source -> Destination 
	Public  
DRMS
 	Public  
DMS

Sequence  No Violations, Control Schedule Approved 
Source -> Destination 
	Public  
DMS
 	Public  
DRMS

Sequence  No Violations, Schedule Approved 
Source -> Destination 
	Public  
DMS
 	Public  
DRMS

Sequence  Limit Violations, Suggested  Schedule Adjustments 
Source -> Destination 
	Public  
DMS
 	Public  
DRMS

Sequence  Limit Violations, Suggested Schedule Adjustments 
Source -> Destination 
	Public  
DMS
 	Public  
DRMS

 

Demand Response Program
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 9/10/2009.  Last modified on 9/10/2009.
GUID:		{70336B03-2959-4f99-93B3-8AEA2D449AA6}

A defined set of procedures and rules that enable  Electricity Consumers to temporarily change electricity consumption of a DR Asset or DR Resource in response to market or reliability conditions.  For purposes of these standards, Demand Response does not include energy efficiency or permanent Load reduction.

Distributed Energy Resource
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 9/10/2009.  Last modified on 10/27/2009.
GUID:		{4A076E43-FEAD-4d38-9042-674E90191B05}

Distributed energy resources are small, modular, energy generation and storage technologies that provide electric capacity or energy where it is needed*

A DER may be implemented by an Electricity Consumer to generate electricity for its own use during DR Events in order to meet load shedding obligations it may have within a Demand Response Program.

*Definition of DER provided by the Department of Energy, http://www1.eere.energy.gov/femp/pdfs/31570.pdf

Distribution Company
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/7/2009.  Last modified on 10/7/2009.
GUID:		{0D1E0FA4-BC03-494e-BEDA-B85A7504B78E}

A Company that delivers electricity to end use customers and can accept energy delivery from end use customers that have some form of generation (DER).

Connections
Connector	Source	Target	Notes	
UseCaseLink   
Source -> Destination 
	Public  
Distribution Company
 	Public  
3.2 Administrate Distribution DR Resource

 

Distribution Operator
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{A5E5FE92-7375-448c-866A-95ACAA73CB06}

 

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
Distribution Operator
 	Public  
Check againts circuit operating limits

Sequence  Monitoring and Alarms 
Source -> Destination 
	Public  
DMS
 	Public  
Distribution Operator

Sequence  Monitor - Alarams 
Source -> Destination 
	Public  
DMS
 	Public  
Distribution Operator

Sequence  Monitor and Alarms 
Source -> Destination 
	Public  
DMS
 	Public  
Distribution Operator

Sequence  Manual Interventions 
Source -> Destination 
	Public  
Distribution Operator
 	Public  
DMS

Sequence  Manual Interventions 
Source -> Destination 
	Public  
Distribution Operator
 	Public  
DMS

 

Electricity Consumer
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 9/10/2009.  Last modified on 9/10/2009.
GUID:		{A5D0E301-DAC4-47db-936B-C87191250B6E}

Any entity that consumes electricity.

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
Electricity Consumer
 	Public  
Specify Load Profile

Association   
Unspecified 
	Public  
Electricity Consumer
 	Public  
2.0 Administrate Customer for DR

 

Energy Service Provider
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/27/2009.
GUID:		{0A3D7B68-156F-4602-888B-E6B9CFC7A215}

 

Connections
Connector	Source	Target	Notes	
Dependency   
Source -> Destination 
	Public  
Specify Load Profile
 	Public  
Energy Service Provider

Dependency   
Source -> Destination 
	Public  
Energy Service Provider
 	Public  
Apply Retail Uplift Charges

Dependency   
Source -> Destination 
	Public  
Energy Service Provider
 	Public  
Load Forecast by Circuit

Association   
Unspecified 
	Public  
Locational Wholesale Prices
 	Public  
Energy Service Provider

Sequence  Locational Prices  
Source -> Destination 
	Public  
System and Market Operator
 	Public  
Energy Service Provider

Sequence  Apply Price Uplifts 
Source -> Destination 
	Public  
Energy Service Provider
 	Public  
Energy Service Provider

Sequence  Aggregate and update forecast 
Source -> Destination 
	Public  
Energy Service Provider
 	Public  
Load Forecast

Sequence  Limit Violations - Suggested Adjustments 
Source -> Destination 
	Public  
DMS
 	Public  
Energy Service Provider

Sequence  Determine Congestion Price Uplift by Circuit 
Source -> Destination 
	Public  
Energy Service Provider
 	Public  
Energy Service Provider

 

Industrial Customer
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{B2DFE962-CF5D-4a1c-872D-D44869A8CBCD}

 

Load Serving Entity
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 9/10/2009.  Last modified on 10/27/2009.
GUID:		{D80D044E-C605-4a2d-A723-C9B4C66B2D48}

The entity that is responsible for serving the Electricity Customers Electricity needs. An LSE may also perform the role of DR Aggregator.

Connections
Connector	Source	Target	Notes	
UseCaseLink   
Source -> Destination 
	Public  
Load Serving Entity
 	Public  
3.2 Administrate Distribution DR Resource

Association   
Unspecified 
	Public  
Load Serving Entity
 	Public  
2.0 Administrate Customer for DR

Association   
Unspecified 
	Public  
Load Serving Entity
 	Public  
1.0 Administrate DR Program

Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
System and Market Operator
 	Public  
Load Serving Entity

Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
Load Serving Entity
 	Public  
DR Aggregator

Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
Load Serving Entity
 	Public  
DR Resource

 

Merchant Operator
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{01316339-DCE0-4a6b-914A-6DE25BECAC64}

 

Metering Agent
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{D1461F61-F4F3-4f89-8573-EC78BAE907F5}

 

Regulator
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{EAF6ADCD-01EC-4583-9A8F-213605A636B4}

 

Residential Customer
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 10/27/2009.  Last modified on 10/27/2009.
GUID:		{4FCC2D55-4D0A-4172-A6EC-407C6B84C5FC}

 

System and Market Operator
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	Actors     Keywords:   
Detail:		Created on 11/19/2005.  Last modified on 10/7/2009.
GUID:		{DAF868DE-391C-4891-88D0-E4B10647C91E}

The Market Operator manages the bulk electricity market and produces prices for various products. 

A System Operator is a Balancing Authority, Transmission Operator, or Reliability Coordinator whose responsibility is to monitor and control an electric system in real time (based on NERC definition).  The System Operator is responsible for initiating Demand Response Events (e.g. Advance Notifications, Deployment, and Release/Recall instructions).

ISO New England and PJM Interconnection are examples of Market and System Operators that perform this function

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
System and Market Operator
 	Public  
2.0 Administrate Customer for DR

Association   
Unspecified 
	Public  
System and Market Operator
 	Public  
1.0 Administrate DR Program

Sequence  Locational Prices  
Source -> Destination 
	Public  
System and Market Operator
 	Public  
Energy Service Provider

Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
System and Market Operator
 	Public  
Load Serving Entity

Sequence  Broadcast DR Message 
Source -> Destination 
	Public  
System and Market Operator
 	Public  
DR Resource

 

DR Use Cases 
Type:		Package 
Status:		Proposed. Version 1.0. Phase 1.0.
Package:	NAESB Demand Response Use Cases for NIST Smart Grid
Detail:		Created on 10/26/2009. Last modified on 10/26/2009
GUID:		{2FE2D525-608E-466f-B71C-EF8131179F57}

DR Use Case Overview Diagram - (Use Case diagram) 
Created By:	jzhou on 10/9/2009
Last Modified:	10/26/2009
Version:		1.0. Locked: False
GUID:		{F3C64595-72B9-4e0d-898A-CC62E898614A}

Figure: 3

1.0 Administrate DR Program 
Type:		Package 
Status:		Proposed. Version 1.0. Phase 1.0.
Package:	DR Use Cases
Detail:		Created on 10/26/2009. Last modified on 10/26/2009
GUID:		{585FDBCD-7287-4225-A508-8AA24496C1CC}

1.0 Administrate DR Program - (Use Case diagram) 
Created By:	jzhou on 10/26/2009
Last Modified:	10/27/2009
Version:		1.0. Locked: False
GUID:		{2ACCE0F3-EEA4-42c3-8F09-1936801C2DBC}

Figure: 4

1.0 Administrate DR Program
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	1.0 Administrate DR Program     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{7797A9BD-E22E-4b9b-B29F-4866332F1C01}

This a high level use case, and see its sub use cases for details. 

Connections
Connector	Source	Target	Notes	
Dependency   
Source -> Destination 
	Public  
1.0 Administrate DR Program
 	Public  
2.0 Administrate Customer for DR

Include   
Source -> Destination 
	Public  
1.0 Administrate DR Program
 	Public  
1.1 Create DR Program

Association   
Unspecified 
	Public  
Load Serving Entity
 	Public  
1.0 Administrate DR Program

Association   
Unspecified 
	Public  
System and Market Operator
 	Public  
1.0 Administrate DR Program

Include   
Source -> Destination 
	Public  
1.0 Administrate DR Program
 	Public  
1.2 Udpate DR Program

Include   
Source -> Destination 
	Public  
1.0 Administrate DR Program
 	Public  
1.3 Remove DR Program

Association   
Unspecified 
	Public  
DR Aggregator
 	Public  
1.0 Administrate DR Program

 

1.1 Create DR Program
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	1.0 Administrate DR Program     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{0EB22636-AEAA-4489-A40E-9B39C55A45B9}

A DR program is created to meet one of two, or both, situations.  A DR program is created to meet a reliability need; i.e. projected insufficient energy supply, and/or for economic purposes; i.e. when market prices are peaking.

A properly designed DR program will have a clearly stated goal or objective, System Operator or Program Administrator, activation and operational protocols, and responsibilities and obligations.  The items that should be considered should include, but not limited to:
·    The type and size of Customer to be targeted
·    The type of program to be implemented; e.g. Direct Load Control, Firm Service Level, Guaranteed Load Drop, etc.
·    The type of metering to be used/required
·    Any regulatory requirements
·    Method of communication
·    Activation protocol
·    Marketing and Sales activities
·    Customer Education activities
·    Duration
·    Delivery Period
·    LSE Compensation
·    Data Exchange Protocols
·    Customer Authorization
·    Third Party Participation
·    Registration / Enrollment Process
·    Approval Process
·    Baseline Calculations
·    Settlement Process
·    Payment Process
·    M&V Methodology
·    Contractual Agreements
·    Dispute Resolution Process
·    Phase-in or Roll-out Plan

Once the DR program is developed, it should be tested which may be accomplished through a pilot program. The results of the test/pilot should then be compared against the goal/objective of the program and any needed modifications made.  Upon satisfactory results, the DR program should be filed with and approved by the Applicable Regulatory Authority, if any.  Depending on which Entity is creating the DR program, it must also be submitted and approved by the System Operator.  Finally, the DR program must be implemented.

Upon activation of a DR program, an observable demand reduction should occur.

Responsibilities (internal requirements)	
Ÿ	Customer Size - Functional (Proposed, Medium difficulty)
	
Ÿ	Customer Type - Functional (Proposed, Medium difficulty)
	
Ÿ	Metering Type - Functional (Proposed, Medium difficulty)
	
Ÿ	Program Type - Functional (Proposed, Medium difficulty)
	
Ÿ	Regulatory Authority - Functional (Proposed, Medium difficulty)
State or federal	
Ÿ	Tariff Indicator - Functional (Proposed, Medium difficulty)
Is it a tariff based program? 	

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
1.0 Administrate DR Program
 	Public  
1.1 Create DR Program

 

1.2 Udpate DR Program
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	1.0 Administrate DR Program     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{9F5BE04F-0AF7-4acc-A658-A13E878FBD83}

Once a DR program is initiated, changes in various elements of the program may be required or desired.  After indentifying the specific required modification, each of the considerations identified in the Create step should be investigated to insure that there are no unintended impacts.  If there are, then further investigation and modification is required.

A regulated Entity must then present the modifications to the Applicable Regulatory Authority for approval.  The modified DR program must then be submitted to the System Operator, approved, and the changes communicated to Customers.

(Same data requirements as Use Case 1.1)

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
1.0 Administrate DR Program
 	Public  
1.2 Udpate DR Program

 

1.3 Remove DR Program
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	1.0 Administrate DR Program     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{EFB7B083-6875-4ed3-9DE3-371EE447A5D0}

Termination of a DR program must take into account any DR resource long term commitments in System and Market Operator programs, contractual obligations with DR Aggregators or Load Serving Entities.  In addition, State and or Federal regulatory agency filings and approvals must be considered prior to terminating a DR program.  Termination of a DR program may involve the removal of DR infrastructure, such as Direct Load Control Devices, advanced metering and pulse devices used in the M+V of the program. All outstanding payments to the DR resources should be completed prior to the termination of the DR program.

Data Elements

·    Contractual Agreements
·    Any regulatory requirements
·    Customer Education activities
·    Payment Process
·    Method of communication
·    Third Party Participation
·    Registration / Enrollment Process

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
1.0 Administrate DR Program
 	Public  
1.3 Remove DR Program

 

2.0 Administrate Customer for DR 
Type:		Package 
Status:		Proposed. Version 1.0. Phase 1.0.
Package:	DR Use Cases
Detail:		Created on 10/26/2009. Last modified on 10/26/2009
GUID:		{06990D0C-8146-454a-A029-F0E52D5C984F}

2.0 Administrate Customer for DR - (Use Case diagram) 
Created By:	jzhou on 10/26/2009
Last Modified:	10/27/2009
Version:		1.0. Locked: False
GUID:		{F9BAF7BE-AF3C-42df-91D7-A8D41F4DA3A9}

Figure: 5

2.0 Administrate Customer for DR
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	2.0 Administrate Customer for DR     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{2B2E86B5-24AD-4ff6-9F17-FA00878D8943}

This is high level use case, see it sub use cases for details. 

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
System and Market Operator
 	Public  
2.0 Administrate Customer for DR

Association   
Unspecified 
	Public  
DR Aggregator
 	Public  
2.0 Administrate Customer for DR

Association   
Unspecified 
	Public  
Load Serving Entity
 	Public  
2.0 Administrate Customer for DR

Association   
Unspecified 
	Public  
Electricity Consumer
 	Public  
2.0 Administrate Customer for DR

Dependency   
Source -> Destination 
	Public  
1.0 Administrate DR Program
 	Public  
2.0 Administrate Customer for DR

Dependency   
Source -> Destination 
	Public  
2.0 Administrate Customer for DR
 	Public  
3.0 Administrate DR Resource

Include   
Source -> Destination 
	Public  
2.0 Administrate Customer for DR
 	Public  
2.1 Register / Enroll Customer for DR Program

Include   
Source -> Destination 
	Public  
2.0 Administrate Customer for DR
 	Public  
2.2 Update Customer Identity

Include   
Source -> Destination 
	Public  
2.0 Administrate Customer for DR
 	Public  
2.3 Remove Customer from DR Program

 

2.1 Register / Enroll Customer for DR Program
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	2.0 Administrate Customer for DR     Keywords:   
Detail:		Created on 10/26/2009.  Last modified on 10/26/2009.
GUID:		{0CC99E2F-F452-41eb-8E69-C305F32A25CC}

The registration/enrollment process must capture the key identifiers to enable accurate accounting of DR resources.  A requirement for a System and Market Operator or facilitating agency registration process for tracking registrations and movement of DR resources from one DR aggregator to another as may occur from time to time is required. An internet based application for the register/enrollment process is ideal for this type of program administration.  

Responsibilities (internal requirements)	
Ÿ	Approval Process -  (Proposed, Medium difficulty)
	
Ÿ	Baseline Calculations -  (Proposed, Medium difficulty)
	
Ÿ	Contractual Agreements -  (Proposed, Medium difficulty)
	
Ÿ	Customer Authorization -  (Proposed, Medium difficulty)
	
Ÿ	Delivery Period -  (Proposed, Medium difficulty)
	
Ÿ	DR Administrator -  (Proposed, Medium difficulty)
·    System and Operator
·    Utility
·    DR Aggregators
·    Energy Consultants
	
Ÿ	DR Resources -  (Proposed, Medium difficulty)

Ÿ	M&V Methodology -  (Proposed, Medium difficulty)
	
Ÿ	Metering Type -  (Proposed, Medium difficulty)
The type of metering to be used/required
	
Ÿ	Program Type -  (Proposed, Medium difficulty)
The type of program to be implemented; e.g. Direct Load Control, Firm Service Level, Guaranteed Load Drop, etc.
	
Ÿ	Registration / Enrollment Process -  (Proposed, Medium difficulty)

Ÿ	Third Party Participation -  (Proposed, Medium difficulty)

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
2.0 Administrate Customer for DR
 	Public  
2.1 Register / Enroll Customer for DR Program

 

2.2 Update Customer Identity
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	2.0 Administrate Customer for DR     Keywords:   
Detail:		Created on 10/26/2009.  Last modified on 10/26/2009.
GUID:		{57F7D5A5-0A97-4365-9657-B0FFEBEF769F}

Once a DR registration is completed, changes in various elements of the registration may be required or desired.  After indentifying the specific required modification, each of the considerations identified in the register/enroll step should be investigated to insure that is accurate and complete.  

All parties (Utility, Aggregators, Energy Consultants, DR resources, Regulatory Agencies) affected by the update should be given reasonable time to review, dispute, and approve/disapprove the update(s).

(Same Data Requirements as Use Case 2.1)

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
2.0 Administrate Customer for DR
 	Public  
2.2 Update Customer Identity

 

2.3 Remove Customer from DR Program
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	2.0 Administrate Customer for DR     Keywords:   
Detail:		Created on 10/26/2009.  Last modified on 10/26/2009.
GUID:		{2D0F76F9-2517-4c18-B3CE-872DE29DBB1F}

Removing a Customer Entity from a DR Program enrollment must take into account any DR resource long term commitments in System and Market Operator programs, contractual obligations with DR Aggregators or Load Serving Entities.  In addition, State and or Federal regulatory agency filings and approvals must be considered prior to removing a customer enrollment from a DR program.  

Data Elements

·    System and Operator
·    Utility
·    DR Aggregators
·    Energy Consultants
·    DR Resources
·    Third Party Participation
·    Approval Process
·    Contractual Agreements

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
2.0 Administrate Customer for DR
 	Public  
2.3 Remove Customer from DR Program

 

3.0 Administrate DR Resource 
Type:		Package 
Status:		Proposed. Version 1.0. Phase 1.0.
Package:	DR Use Cases
Detail:		Created on 10/26/2009. Last modified on 10/26/2009
GUID:		{03691035-1525-430f-8313-2CB043F47D1E}

3.0 Administrate DR Resource - (Use Case diagram) 
Created By:	jzhou on 10/26/2009
Last Modified:	10/27/2009
Version:		1.0. Locked: False
GUID:		{6778896C-D170-43eb-BB9F-ABC33D228A6D}

Figure: 6

3.0 Administrate DR Resource
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{15FA43C3-C778-4f8b-9D5C-45DFAA16FE5F}

This is high level use case, see it sub use cases for details. 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
3.2 Administrate Distribution DR Resource
 	Public  
3.0 Administrate DR Resource

Generalization   
Source -> Destination 
	Public  
3.1 Administrate Bulk Power DR Resource
 	Public  
3.0 Administrate DR Resource

Dependency   
Source -> Destination 
	Public  
3.0 Administrate DR Resource
 	Public  
4.0 Execute DR Event

Dependency   
Source -> Destination 
	Public  
2.0 Administrate Customer for DR
 	Public  
3.0 Administrate DR Resource

 

3.1 Administrate Bulk Power DR Resource
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{7A7C115A-2E7A-4b21-979A-5FEED81B7EB1}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
3.1 Administrate Bulk Power DR Resource
 	Public  
3.0 Administrate DR Resource

 

3.2 Administrate Distribution DR Resource
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{66B0EA6C-8EE7-4e91-9377-344CF407FCE2}

Used to administrate all the DR Resources and Assets. This includes a variety of activities surrounding the registration and management of information surrounding the DR Resources that a Controlling entity may call upon during a DR event. Before a DR Resource may be called upon it must be registered with the Controlling entity.  The administration of a DR Resource covers the following requirements:
•	Need by the Controlling entity to identify a DR Resource for communications pruposes
•	Need by the Controlling entity to establish DR Resource accounts for accounting purposes
•	Need by the Controlling entity to collect information from DR Resources prior to DR events for the purposes of detemrining which DR Resources to call upon during a DR Event
•	Need by the Controlling entity to collect information from DR Resources prior to DR events for the purposes of determining the nature of the DR signals to send to the DR Resources

Connections
Connector	Source	Target	Notes	
UseCaseLink   
Source -> Destination 
	Public  
DR Asset/Resource Owner
 	Public  
3.2 Administrate Distribution DR Resource

UseCaseLink   
Source -> Destination 
	Public  
DR Controlling Entity
 	Public  
3.2 Administrate Distribution DR Resource

Include   
Source -> Destination 
	Public  
3.2 Administrate Distribution DR Resource
 	Public  
3.2.3 Remove DR Resource

UseCaseLink   
Source -> Destination 
	Public  
Distribution Company
 	Public  
3.2 Administrate Distribution DR Resource

Include   
Source -> Destination 
	Public  
3.2 Administrate Distribution DR Resource
 	Public  
3.2.1 Declare DR Resource

UseCaseLink   
Source -> Destination 
	Public  
Load Serving Entity
 	Public  
3.2 Administrate Distribution DR Resource

Generalization   
Source -> Destination 
	Public  
3.2 Administrate Distribution DR Resource
 	Public  
3.0 Administrate DR Resource

UseCaseLink   
Source -> Destination 
	Public  
DR Aggregator
 	Public  
3.2 Administrate Distribution DR Resource

Include   
Source -> Destination 
	Public  
3.2 Administrate Distribution DR Resource
 	Public  
3.2.2 Register DR Resource

3.2.1 Declare DR Resource
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{C2F2E10E-441C-45bf-8BDC-1007614D3C0C}

Responsibilities (internal requirements)	
Ÿ	DR Resoruce Operational Constraints -  (Proposed, Medium difficulty)
The are constraints that define the amount load that can be made available during a DR event and includes the following:
•	Minimum load
•	Maximum load
	
Ÿ	DR Resource Bid -  (Proposed, Medium difficulty)
This is a bid from the DR Resource.  See the DR Bidding use case for a description of the information requirements.	
Ÿ	DR Resource Schedule Constraints -  (Proposed, Medium difficulty)
These are a set of constraints that specify when the DR Resource will be available.  It may contain such information as:
•	Time of day schedule constraints
•	Black out dates
•	Maximum consecutive days of participation
•	Maximum duration of DR event participation
•	Minimum duration of DR event participation
•	Max number of times per day the DR Resource may be called
•	Minimum advanced notification necessary
	
Ÿ	DR Resrouce Identifer -  (Proposed, Medium difficulty)
This identifies the DR Resoruce.	
Ÿ	Temporary Opt-Out -  (Proposed, Medium difficulty)
This is used to temporarily opt out of DR Events and is used to over ride the normal operational constraints. The opt-out can be specified using the following criteria:
•	All events in a program indefinitely
•	Specific DR Event
•	All events in a specific time period

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
3.2 Administrate Distribution DR Resource
 	Public  
3.2.1 Declare DR Resource

Include   
Source -> Destination 
	Public  
3.2.1 Declare DR Resource
 	Public  
3.2.6 DR Bidding

Sequence diagram: Declare DR Resource

Figure: 7

 

3.2.2 Register DR Resource
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{A9BF7F23-2E22-47e5-B445-579709FAE501}

Responsibilities (internal requirements)	
Ÿ	Customer Identifier -  (Proposed, Medium difficulty)
This is a customer identifier (e.g. account number) that signifies to the Utility who owns the DR Resource.	
Ÿ	DR Program Identifier -  (Proposed, Medium difficulty)
This identifies the DR program that this DR Resource is participating in.	
Ÿ	DR Resource Identifier -  (Proposed, Medium difficulty)
This identifies the DR Resrouce that is being registered.	
Ÿ	DR Resource Operational Constraints -  (Proposed, Medium difficulty)
The are constraints that define the amount load that can be made available during a DR event and includes the following:
•	Minimum load
•	Maximum load
	
Ÿ	DR Resource Schedule Constraints -  (Proposed, Medium difficulty)
These are a set of constraints that specify when the DR Resource will be available.  It may contain such information as:
•	Time of day schedule constraints
•	Black out dates
•	Maximum consecutive days of participation
•	Maximum duration of DR event participation
•	Minimum duration of DR event participation
•	Max number of times per day the DR Resource may be called
•	Minimum advanced notification necessary

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
3.2 Administrate Distribution DR Resource
 	Public  
3.2.2 Register DR Resource

Sequence diagram: Register DR Resource

Figure: 8

 

3.2.3 Remove DR Resource
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{72C55DDB-E175-4f12-9D97-D9B7EFDE95EB}

Responsibilities (internal requirements)	
Ÿ	DR Resource Identifier -  (Proposed, Medium difficulty)
This identifies the DR Resrouce that is being removed.	

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
3.2 Administrate Distribution DR Resource
 	Public  
3.2.3 Remove DR Resource

Include   
Source -> Destination 
	Public  
3.2.3 Remove DR Resource
 	Public  
3.2.4 Administrate DR Asset (Direct)

Sequence diagram: Remove DR Resource

Figure: 9

 

3.2.4 Administrate DR Asset (Direct)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{12672C25-1BF0-4f47-B6A9-21B0FD646ED7}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
3.2.5 Administrate DER for DR Purpose
 	Public  
3.2.4 Administrate DR Asset (Direct)

Include   
Source -> Destination 
	Public  
3.2.3 Remove DR Resource
 	Public  
3.2.4 Administrate DR Asset (Direct)

 

3.2.6 DR Bidding
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{94E15F04-6B4E-4f23-899D-8AFF5F849F52}

Responsibilities (internal requirements)	
Ÿ	DR Resource Identifier -  (Proposed, Medium difficulty)
The identifies the DR Resouce that the bid is being submitted for.	
Ÿ	Load Amount -  (Proposed, Medium difficulty)
This is the amount of load that the DR Resource can make available during the scheduled period.	
Ÿ	Load Profile Schedule -  (Proposed, Medium difficulty)
This is the schedule that the DR Resource's load profile will be available.	
Ÿ	Offer Price -  (Proposed, Medium difficulty)
This is the price at which the DR Resource is offering their shed resource.	

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
3.2.1 Declare DR Resource
 	Public  
3.2.6 DR Bidding

Sequence diagram: DR Bidding

Figure: 10

 

3.2.5 Administrate DER for DR Purpose
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	3.0 Administrate DR Resource     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{23F66FB7-634D-48ac-89E9-67E8E44BD4D7}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
3.2.5 Administrate DER for DR Purpose
 	Public  
3.2.4 Administrate DR Asset (Direct)

  

4.0 Execute DR Event 
Type:		Package 
Status:		Proposed. Version 1.0. Phase 1.0.
Package:	DR Use Cases
Detail:		Created on 10/26/2009. Last modified on 10/26/2009
GUID:		{87BDA2B0-DF30-4964-BB72-70242BEE0040}

Execute DR Event - (Use Case diagram) 
Created By:	Ed Koch on 10/17/2009
Last Modified:	10/27/2009
Version:		1.0. Locked: False
GUID:		{091A99D3-E9C3-4de5-A96E-BC953257EBCC}

Figure: 11

4.0 Execute DR Event
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{EEBEEC32-4EE4-43d8-92AA-8BEECC420BEC}

This is high level use case, see it sub use cases for details. 

Connections
Connector	Source	Target	Notes	
Dependency   
Source -> Destination 
	Public  
4.0 Execute DR Event
 	Public  
Check for Distribution Circuit Contraints

Dependency   
Source -> Destination 
	Public  
Check againts circuit operating limits
 	Public  
4.0 Execute DR Event

Generalization   
Source -> Destination 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
4.0 Execute DR Event

Generalization   
Source -> Destination 
	Public  
4.4 Broadcast Pricing (Retail) for DR Purpose
 	Public  
4.0 Execute DR Event

Dependency   
Source -> Destination 
	Public  
3.0 Administrate DR Resource
 	Public  
4.0 Execute DR Event

Generalization   
Source -> Destination 
	Public  
4.3 Broadcast Pricing (Wholesale) for DR Purpose
 	Public  
4.0 Execute DR Event

Generalization   
Source -> Destination 
	Public  
4.5 Dispatch DR Instructions (Bulk Power)
 	Public  
4.0 Execute DR Event

Dependency   
Source -> Destination 
	Public  
4.0 Execute DR Event
 	Public  
5.0 Post DR Event Management

Generalization   
Source -> Destination 
	Public  
4.8 DR Event Execution
 	Public  
4.0 Execute DR Event

Generalization   
Source -> Destination 
	Public  
4.6 Dispatch DR Instructions (Distribution)
 	Public  
4.0 Execute DR Event

Generalization   
Source -> Destination 
	Public  
4.7 DR Direct Load Control (Distribution)
 	Public  
4.0 Execute DR Event

Generalization   
Source -> Destination 
	Public  
4.1 Notify DR Event (Bulk Power)
 	Public  
4.0 Execute DR Event

 

4.1 Notify DR Event (Bulk Power)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/14/2009.  Last modified on 10/26/2009.
GUID:		{91C118B4-B306-410f-AE64-A9DEADFFC7C1}

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.1 Notify DR Event (Bulk Power)
 	Public  
4.1.1 Advanced Notification for DR (Bulk Power)

Include   
Source -> Destination 
	Public  
4.1 Notify DR Event (Bulk Power)
 	Public  
4.1.2 Update a DR Event (Bulk Power) 

Include   
Source -> Destination 
	Public  
4.1 Notify DR Event (Bulk Power)
 	Public  
4.1.3 Cancel a DR Event (Bulk Power)

Generalization   
Source -> Destination 
	Public  
4.1 Notify DR Event (Bulk Power)
 	Public  
4.0 Execute DR Event

4.1.1 Advanced Notification for DR (Bulk Power)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{376B0EF9-5547-4298-B231-E4EE21CF2399}

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.1 Notify DR Event (Bulk Power)
 	Public  
4.1.1 Advanced Notification for DR (Bulk Power)

Include   
Source -> Destination 
	Public  
4.1.1 Advanced Notification for DR (Bulk Power)
 	Public  
4.1.4 DR Resource Confirmation (Bulk Power)

 

4.1.2 Update a DR Event (Bulk Power) 
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{54A5F16F-998F-4935-8688-C4BE22BFB633}

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.1.2 Update a DR Event (Bulk Power) 
 	Public  
4.1.4 DR Resource Confirmation (Bulk Power)

Include   
Source -> Destination 
	Public  
4.1 Notify DR Event (Bulk Power)
 	Public  
4.1.2 Update a DR Event (Bulk Power) 

 

4.1.3 Cancel a DR Event (Bulk Power)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{D13D8603-DF8A-4739-8E4D-920A28FE0899}

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.1.3 Cancel a DR Event (Bulk Power)
 	Public  
4.1.4 DR Resource Confirmation (Bulk Power)

Include   
Source -> Destination 
	Public  
4.1 Notify DR Event (Bulk Power)
 	Public  
4.1.3 Cancel a DR Event (Bulk Power)

 

4.1.4 DR Resource Confirmation (Bulk Power)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{B46CC8CB-A176-40dd-9144-C2039F9E4806}

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.1.3 Cancel a DR Event (Bulk Power)
 	Public  
4.1.4 DR Resource Confirmation (Bulk Power)

Include   
Source -> Destination 
	Public  
4.1.2 Update a DR Event (Bulk Power) 
 	Public  
4.1.4 DR Resource Confirmation (Bulk Power)

Include   
Source -> Destination 
	Public  
4.1.1 Advanced Notification for DR (Bulk Power)
 	Public  
4.1.4 DR Resource Confirmation (Bulk Power)

  

4.2 Notify DR Event (Distribution)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{65D3226C-1933-4db0-8394-9253DDCDB330}

These set of interactions is used to notify a DR Resource of a DR event.

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
DR Asset

Association   
Unspecified 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
DR Asset/Resource Owner

Generalization   
Source -> Destination 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
4.0 Execute DR Event

Include   
Source -> Destination 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
4.2.2 Update a DR Event (Distribution)

Include   
Source -> Destination 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
4.2.3 Cancel a DR Event (Distribution)

Include   
Source -> Destination 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
4.2.1 Advanced Notification for DR (Distribution)

4.2.1 Advanced Notification for DR (Distribution)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{F4C69C3C-FC3A-41ab-BD54-1B431B9482CC}

This is used by the Controlling entity to send the DR Event notification (i.e. DR signal) to the DR Resource.

Responsibilities (internal requirements)	
Ÿ	Controlling Entity ID -  (Proposed, Medium difficulty)
An identifier for the controlling entity issuing the DR event.	
Ÿ	DR Program ID - Functional (Proposed, Medium difficulty)
Identifier of the program that this DR event was issued for.	
Ÿ	DR Resource Group ID - Functional (Proposed, Medium difficulty)
A group which this DR Resource belongs to. Can be used for multi-cast notifications.	
Ÿ	DR Resource ID - Functional (Proposed, Medium difficulty)
Identifier of the DR Resource that this Event is intended for.	
Ÿ	DR Resource Operation Mode (Schedule) - Functional (Proposed, Medium difficulty)
Operation modes are representations of how the DR Resource should respond to the Event Data that is part of this event. Operation modes allow DR logic to be implemented within the DR Controlling entity and allow the DR Resource to respond to a much simpler representation of the DR Event data. Operation modes are simple enumerations of the values which may be scheduled during the DR Event active period.  The possible values are the following:

NORMAL - This value is used to signify that no response to the DR Event is necessary by the DR Resource.

MODERATE - This is typically used to signify a moderate level of respeonse by the DR Resource.

HIGH- This is typically used to signify a high level of response by the DR Resoure.

SPECIAL- This is typically used to signify a special circumstance to the DR Resource.
	
Ÿ	DR Resource Specifications -  (Proposed, Medium difficulty)
This specifies which DR Assets within a DR Resources should be used and can be specified int he following fashion:
•	Geographic location
•	Grid location
•	DR Asset group ID
	
Ÿ	DR Resource Type ID - Functional (Proposed, Medium difficulty)
I program spewcific field that can be used to identify a type of DR Resource within a DR program.	
Ÿ	Event Data - Functional (Proposed, Medium difficulty)
A collection of information that is associated with a DR event.  An instance of such information represents a specific type of information that was defined to exist for DR events when the program was first set up. For example a DR program my have been set up to use real-time pricing as the values that are sent when DR events are issued.  In that caset he information would be prices. Furthermore each type of information may have a schedule of values that are valid across the entire period for then the DR event is active. Therefore a single type of information may have multiple values each of which are valid during a different time period during the event. Each type of information has the following attributes when it is defined:
•	name
•	data type

The following data types should be supported:
•	PRICE_ABSOLUTE - Price number
•	PRICE_RELATIVE - Change in price
•	PRICE_MULTIPLE - Multiple of current price
•	LOAD_LEVEL - Amount of load based on an enumeration, i.e. moderate, high, etc
•	LOAD_AMOUNT - Fixed amount of load to shed in KW
•	LOAD_PERCENTAGE - Percentage of load to shed, i.e. 10%
•	GRID_RELIABILITY - Number signifying the reliability of the grid

Ÿ	Event ID - Functional (Proposed, Medium difficulty)
Identifier for the DR event that was created when the DR event was first issued. Should be a globally unique identifier for each Controlling entity.	
Ÿ	Event Schedule - Functional (Proposed, Medium difficulty)
Schedule for the DR Event periods. Includes the following:
•	Notification date/time
•	Event start date/time
•	Ramp time (potentially randomized)
•	Event end date/time (possibly specificed as a duration)
	
Ÿ	Test Event Flag - Functional (Proposed, Medium difficulty)
This attribute signifies whether this is a test event or not.  Test events may be issued by the Utility/ISO like other DR Events.

Connections
Connector	Source	Target	Notes	
Extend   
Source -> Destination 
	Public  
4.2.1 Advanced Notification for DR (Distribution)
 	Public  
4.2.4 DR Resource Confirmation (Distribution)

Include   
Source -> Destination 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
4.2.1 Advanced Notification for DR (Distribution)

Sequence diagram: DR Event Notification

Figure: 12

 

4.2.2 Update a DR Event (Distribution)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{71B1A51A-1628-4808-9F21-55779A5647FE}

Used to update a DR event that has been previously notified.  The requirements for this use case are the same as those for the "Advanced Notification for DR" use case.

Responsibilities (internal requirements)	
Ÿ	Event -  (Proposed, Medium difficulty)
See the "Advanced Notification for DR" use case.	
Ÿ	Event Modification Number -  (Proposed, Medium difficulty)
Modification number of the DR event.  Used to indicate if the DR Event has been modified by the Utility. Each time it is modified this number is incremented.	
Ÿ	Modification reason code -  (Proposed, Medium difficulty)
The reason the event was modified.	

Connections
Connector	Source	Target	Notes	
Extend   
Source -> Destination 
	Public  
4.2.2 Update a DR Event (Distribution)
 	Public  
4.2.4 DR Resource Confirmation (Distribution)

Include   
Source -> Destination 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
4.2.2 Update a DR Event (Distribution)

Sequence diagram: Update DR Event

Figure: 13

 

4.2.3 Cancel a DR Event (Distribution)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{B8AB9C4F-218D-40de-8231-B43A11DE4790}

This is used by the Controlling entity to notify the DR Resrouce that a DR Event is being cancelled. It should only be executed if a DR Resouce has prviously receieved notifiation of a DR Event and that event has subsequently been cancelled.

Responsibilities (internal requirements)	
Ÿ	Cancellation reason code -  (Proposed, Medium difficulty)
The reason the event  is being cancelled.	
Ÿ	DR Event Identifier -  (Proposed, Medium difficulty)
Identifier for the event that is being canceled.	
Ÿ	Effective date/time -  (Proposed, Medium difficulty)
The date and time this cancellation takes effect.	

Connections
Connector	Source	Target	Notes	
Extend   
Source -> Destination 
	Public  
4.2.3 Cancel a DR Event (Distribution)
 	Public  
4.2.4 DR Resource Confirmation (Distribution)

Include   
Source -> Destination 
	Public  
4.2 Notify DR Event (Distribution)
 	Public  
4.2.3 Cancel a DR Event (Distribution)

Sequence diagram: Cancel DR Event

Figure: 14

 

4.2.4 DR Resource Confirmation (Distribution)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{61E146F4-D384-4f77-B388-C62843FB1787}

This is a confirmation messages that is sent by a DR Resource to the Controlling entity as a result of receiving a DR Signal form the Controlling entity. It may be used as an acknowledgement of the receipt of the DR signal, but it may lso contain a vaierty of information that is used to signify how the DR Resource will repsond to the DR Signal.

Responsibilities (internal requirements)	
Ÿ	DR Assets Charcterisitics -  (Proposed, Medium difficulty)
The expected response characteristics of each DR Asset that is part of the DR Resource. May be needed for aggreagated DR Assets and may be as simple as whether a DR Asset is participating or its actual load profile. For each DR Asset the following should be given following:
•	Location of Asset, either geograpic or grid location
•	Asset schedule of participating
•	Asset load profile (schedule)
	
Ÿ	DR Resouce ID -  (Proposed, Medium difficulty)
The identifier of the DR Resource	
Ÿ	DR Resource Load Profile Response -  (Proposed, Medium difficulty)
Load profile response characterization of the DR Resource in response to getting the DR signal.	
Ÿ	Notification Received Acknolwledgement -  (Proposed, Medium difficulty)
This is an acknowledgement of the receipt of a DR notification or dispatch. It should include any necessary provisions for non-repudiation.	
Ÿ	Opt in/out -  (Proposed, Medium difficulty)
This is used to temporarily opt in/out of DR Events and is used to over ride the normal operational constraints. The opt-in/out can be specified using the following criteria:
•	All events in a program indefinitely
•	Specific DR Event
•	All events in a specific time period

In addition there may be a schedule associated the opt in/out state.

Connections
Connector	Source	Target	Notes	
Extend   
Source -> Destination 
	Public  
4.2.1 Advanced Notification for DR (Distribution)
 	Public  
4.2.4 DR Resource Confirmation (Distribution)

Extend   
Source -> Destination 
	Public  
4.2.3 Cancel a DR Event (Distribution)
 	Public  
4.2.4 DR Resource Confirmation (Distribution)

Extend   
Source -> Destination 
	Public  
4.2.2 Update a DR Event (Distribution)
 	Public  
4.2.4 DR Resource Confirmation (Distribution)

Sequence diagram: DR Resource Confirmation

Figure: 15

  

4.3 Broadcast Pricing (Wholesale) for DR Purpose
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{0AA3ED46-6F79-454b-ADC9-662A12779343}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
4.3 Broadcast Pricing (Wholesale) for DR Purpose
 	Public  
4.0 Execute DR Event

 

4.4 Broadcast Pricing (Retail) for DR Purpose
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{20228EA6-8133-4f52-86E9-E142E646619A}

Demand Response programs are designed to address different power system concerns caused by the imbalance between generation, transmission and consumption or environmental concerns. Some DR programs are conducted on a voluntary basis, where the customer can opt to maintain the level or load; some DR programs are mandatory, where either the customer loads will be curtailed under certain conditions or customer will incur financial penalties for noncompliance.

In retail market, certain “DR Messages” can be broadcasted to DR resources either directly or through Service Providers.

Based on the OpenADR discussion, broadcasting function is mainly used for volunteer or non mission critical DR massage, therefore, message acknowledgement or confirmation is optional. 

DR Source of Power/Generation

“DR Message” also can be source of power or generation. ANSI C12.19-2008 defined the following source of power/generation in Standard Table 12. 

Precondition: 

The DR controlling entity sends the DR message to service providers. In the case of DR pricing, DR controlling entity calculates the wholesale price per location and communicates the appropriate price associated with the DR product to service providers. 

Post Condition:

DR Resources received the DR pricing information, and may or may not act based on the DR agreement or contract. 

Responsibilities (internal requirements)	
Ÿ	Same as the wholesale pricing use case -  (Proposed, Medium difficulty)

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
4.4 Broadcast Pricing (Retail) for DR Purpose
 	Public  
4.0 Execute DR Event

Sequence diagram: Broadcast DR Message

Figure: 16

 

4.5 Dispatch DR Instructions (Bulk Power)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{D74155BB-6A71-4267-A02C-C6D9A9E74BB7}

 

Connections
Connector	Source	Target	Notes	
Dependency   
Source -> Destination 
	Public  
4.5 Dispatch DR Instructions (Bulk Power)
 	Public  
4.8 DR Event Execution

Extend   
Source -> Destination 
	Public  
4.5 Dispatch DR Instructions (Bulk Power)
 	Public  
4.5.1 Monitor DR Event (Bulk) 

Generalization   
Source -> Destination 
	Public  
4.5 Dispatch DR Instructions (Bulk Power)
 	Public  
4.0 Execute DR Event

4.5.1 Monitor DR Event (Bulk) 
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{E3E612CB-FDED-4605-AC04-48F5623D8EB3}

 

Connections
Connector	Source	Target	Notes	
Extend   
Source -> Destination 
	Public  
4.5 Dispatch DR Instructions (Bulk Power)
 	Public  
4.5.1 Monitor DR Event (Bulk) 

Include   
Source -> Destination 
	Public  
4.5.1 Monitor DR Event (Bulk) 
 	Public  
4.9 Operational Coordination between Transmission and Distribution and DR Resources

 

4.6 Dispatch DR Instructions (Distribution)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{3A53F218-6E92-4acc-99F7-BBF747FF2FB0}

This interaction is used to dispatch DR Resources.  This type of interaction is used when the Contorlling entity needs to achieve specific objectives from the DR Resouces during DR events. This means that specific instructions will be given to the DR Resouce with obejctives (e.g. shed 100KW) for the load profile of the DR Resource. 

Note that for the retail use cases a Dispatch is considered a special type of DR Notification and thus it is very similar in nature to the requirements given for that interaction.

Responsibilities (internal requirements)	
Ÿ	Dispatch Instructions -  (Proposed, Medium difficulty)
A collection of dispatch instructions that is associated with a DR event.  An instance of such instructions represents a specific type of instruction that was defined specifically for the DR program.  Each type of instruction may have a schedule of values that are valid across the entire period for then the DR event is active. Therefore a single type of instruction may have multiple values each of which are valid during a different time period during the event. Each type of instruction has the following attributes when it is defined:
•	name
•	instruction type

The following instruction types should be supported:
•	LOAD_LEVEL - Amount of load based on an enumeration, i.e. moderate, high, etc
•	LOAD_AMOUNT - Fixed amount of load to shed in KW
•	LOAD_PERCENTAGE - Percentage of load to shed, i.e. 10%
	
Ÿ	DR Program Name -  (Proposed, Medium difficulty)
Identifier of the program that this DR event was issued for.	
Ÿ	DR Resource ID -  (Proposed, Medium difficulty)
Identifier of the DR Resource that this dispatch is intended for.	
Ÿ	Event ID -  (Proposed, Medium difficulty)
Identifier for the DR event that was created when the DR event was first issued.	
Ÿ	Event Modification Number -  (Proposed, Medium difficulty)
Modification number of the DR event.  Used to indicate if the DR Event has been modified by the Utility. Each time it is modified this number is incremented.	
Ÿ	Event Schedule -  (Proposed, Medium difficulty)
Schedule for the DR Event periods. Includes the following:
•	Notification date/time
•	Event start date/time
•	Event end date/time
	
Ÿ	Test Event Flag -  (Proposed, Medium difficulty)
This attribute signifies whether this is a test event or not.  Test events may be issued by the Utility/ISO like other DR Events.	

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
4.6 Dispatch DR Instructions (Distribution)
 	Public  
DR Asset

Association   
Unspecified 
	Public  
4.6 Dispatch DR Instructions (Distribution)
 	Public  
DR Asset/Resource Owner

Dependency   
Source -> Destination 
	Public  
4.6 Dispatch DR Instructions (Distribution)
 	Public  
4.8 DR Event Execution

Generalization   
Source -> Destination 
	Public  
4.6 Dispatch DR Instructions (Distribution)
 	Public  
4.0 Execute DR Event

Sequence diagram: Dispatch DR Instructions

Figure: 17

 

4.7 DR Direct Load Control (Distribution)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{8A9DCA38-58E1-4460-99B9-0A541A70AF76}

This use case covers direct interactions between the Controlling entity and a specific DR Asset for the purposes of putting that asset into a specific load control state (e.g. turn it on or off). In this case the DR Asset is a DR Resource with only one DR Asset and thus the interaction is directly with the DR Asset.

Responsibilities (internal requirements)	
Ÿ	Load Address/Identifier -  (Proposed, Medium difficulty)
This is an identifier for the load which is being controlled.
Note: Is this an ID or and address? What else is needed?	
Ÿ	Load Control Command -  (Proposed, Medium difficulty)
This is a command to a specific load.	

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
4.7 DR Direct Load Control (Distribution)
 	Public  
DR Asset

Dependency   
Source -> Destination 
	Public  
4.7 DR Direct Load Control (Distribution)
 	Public  
4.8 DR Event Execution

Generalization   
Source -> Destination 
	Public  
4.7 DR Direct Load Control (Distribution)
 	Public  
4.0 Execute DR Event

Extend   
Source -> Destination 
	Public  
4.7 DR Direct Load Control (Distribution)
 	Public  
4.7.1 Monitor DR Event (DR Resource)

Sequence diagram: Direct Load Control

Figure: 18

4.7.1 Monitor DR Event (DR Resource)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{8C13A794-C636-4790-AAB7-0CAA3EB5D65D}

This interaction is used to monitor A Resource's behaviour. It may be executed as a result of the DR Resource receiving a DR signal or it may be conducted continuously.  

Responsibilities (internal requirements)	
Ÿ	Operatinal Constraints -  (Proposed, Medium difficulty)
This is used to supply information about when and how a DR Resouce may participate in a DR Event. The following items may be supplied:
•	Limits on load profile performance
•	Schedule of participation

Note that this information may also be supplied as part fo the administration of the DR Resource and thus it may not be necessary that it be part of this interaction.	
Ÿ	Opt in/out state -  (Proposed, Medium difficulty)
This is used to temporarily opt in/out of DR Events and is used to over ride the normal operational constraints. The opt-in/out can be specified using the following criteria:
•	All events in a program indefinitely
•	Specific DR Event
•	All events in a specific time period

In addition there may be a schedule associated the opt in/out state.
	
Ÿ	Usgae Information -  (Proposed, Medium difficulty)
Information about the current electricity usage of the DR Resource.	

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.7.1 Monitor DR Event (DR Resource)
 	Public  
4.7.2 Monitor DR Event (DR Asset)

Include   
Source -> Destination 
	Public  
4.7.1 Monitor DR Event (DR Resource)
 	Public  
4.9 Operational Coordination between Transmission and Distribution and DR Resources

Extend   
Source -> Destination 
	Public  
4.7 DR Direct Load Control (Distribution)
 	Public  
4.7.1 Monitor DR Event (DR Resource)

Sequence diagram: Monitor DR Event (DR Resource)

Figure: 19

 

4.7.2 Monitor DR Event (DR Asset)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/17/2009.  Last modified on 10/26/2009.
GUID:		{E7CF174D-9A21-446a-B6A6-E4AE8A4A616E}

This interaction is used to monitor the state of a DR Asset.  It may be executed as a result of the DR Asset receiving a DR signal or it may be conducted continuously.

Responsibilities (internal requirements)	
Ÿ	Exception Conditions -  (Proposed, Medium difficulty)
This is used to report that the load controller may not behave as commanded because of a variety of conditions including:
•	Faults in device
•	Customer override
	
Ÿ	Load Control State -  (Proposed, Medium difficulty)
The state of the load. Includes both commanded states and user settings.  May include a schedule of future states if a particular control algorithm for the load controller is being executed.
	
Ÿ	Operational Constraints -  (Proposed, Medium difficulty)
Constraints on how the load maybe controlled. May include limits on the state of the load controller and also include schedules upon those constraints.	

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.7.1 Monitor DR Event (DR Resource)
 	Public  
4.7.2 Monitor DR Event (DR Asset)

Sequence diagram: Monitor DR Asset

Figure: 20

  

4.8 DR Event Execution
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/14/2009.  Last modified on 10/26/2009.
GUID:		{EDA61B17-9033-4a82-AB8A-B65923281D96}

 

Connections
Connector	Source	Target	Notes	
Dependency   
Source -> Destination 
	Public  
4.6 Dispatch DR Instructions (Distribution)
 	Public  
4.8 DR Event Execution

Dependency   
Source -> Destination 
	Public  
4.7 DR Direct Load Control (Distribution)
 	Public  
4.8 DR Event Execution

Dependency   
Source -> Destination 
	Public  
4.5 Dispatch DR Instructions (Bulk Power)
 	Public  
4.8 DR Event Execution

Generalization   
Source -> Destination 
	Public  
4.8 DR Event Execution
 	Public  
4.0 Execute DR Event

Dependency   
Source -> Destination 
	Public  
4.9 Operational Coordination between Transmission and Distribution and DR Resources
 	Public  
4.8 DR Event Execution

4.8.1 DR Execution - Dynamic Price-Based
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{06E849F9-0CA5-42d6-B801-295560ADB0BC}

 

Connections
Connector	Source	Target	Notes	
Dependency   
Source -> Destination 
	Public  
Check for Distribution Circuit Contraints
 	Public  
4.8.1 DR Execution - Dynamic Price-Based

Dependency   
Source -> Destination 
	Public  
Assess Congestion Uplift Charges
 	Public  
4.8.1 DR Execution - Dynamic Price-Based

Dependency   
Source -> Destination 
	Public  
4.8.1 DR Execution - Dynamic Price-Based
 	Public  
Identify Impacted Circuits

Sequence diagram: DR Execution - Dynamic Price-Based

Figure: 21

 

4.8.2 DR Execution - Notification Based
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{47720BE5-156A-4b17-9A3E-D6C42576474C}

 

Connections
Connector	Source	Target	Notes	
Dependency   
Source -> Destination 
	Public  
Check for Distribution Circuit Contraints
 	Public  
4.8.2 DR Execution - Notification Based

Dependency   
Source -> Destination 
	Public  
4.8.2 DR Execution - Notification Based
 	Public  
Identify Impacted Circuits

Sequence diagram: DR Execution - Notification Based

Figure: 22

 

4.8.2 DR Exedcution - Direct Load Control
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{D9FE657E-2E32-452a-B7CB-5707DA15AA52}

 

Connections
Connector	Source	Target	Notes	
Dependency  Adjusted Schedule 
Source -> Destination 
	Public  
Adjust Schedule
 	Public  
4.8.2 DR Exedcution - Direct Load Control

Dependency  DLC 
Source -> Destination 
	Public  
Check for Distribution Circuit Contraints
 	Public  
4.8.2 DR Exedcution - Direct Load Control

Include   
Source -> Destination 
	Public  
4.8.2 DR Exedcution - Direct Load Control
 	Public  
Identify Impacted Circuits

Sequence diagram: DR Exedcution - Direct Load Control

Figure: 23

Distribution Operator
Type:		Actor    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/24/2009.
GUID:		{D3E2F38A-062A-4b5e-AC41-865601C25842}

 

Load Forecast
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/24/2009.
GUID:		{02DA4CC4-571C-48c0-83B6-1B6E3BC7574A}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
Load Forecast
 	Public  
Assess Congestion Uplift Charges

Generalization   
Source -> Destination 
	Public  
Load Forecast
 	Public  
Check againts circuit operating limits

 

Load Forecast
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/24/2009.
GUID:		{CB006742-B1E5-4afc-954F-4E704C1EF537}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
Load Forecast
 	Public  
Assess Congestion Uplift Charges

Generalization   
Source -> Destination 
	Public  
Load Forecast
 	Public  
Check againts circuit operating limits

Sequence  Load Forecast by Circuit 
Source -> Destination 
	Public  
Load Forecast
 	Public  
DMS

Sequence  Aggregate and update forecast 
Source -> Destination 
	Public  
Energy Service Provider
 	Public  
Load Forecast

Sequence  Load Forecast by Circuit 
Source -> Destination 
	Public  
Load Forecast
 	Public  
DMS

   

4.9 Operational Coordination between Transmission and Distribution and DR Resources
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/9/2009.  Last modified on 10/26/2009.
GUID:		{B0F82E5E-84C6-458e-871D-C601D5B9486E}

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.7.1 Monitor DR Event (DR Resource)
 	Public  
4.9 Operational Coordination between Transmission and Distribution and DR Resources

Include   
Source -> Destination 
	Public  
4.5.1 Monitor DR Event (Bulk) 
 	Public  
4.9 Operational Coordination between Transmission and Distribution and DR Resources

Dependency   
Source -> Destination 
	Public  
4.9 Operational Coordination between Transmission and Distribution and DR Resources
 	Public  
4.8 DR Event Execution

Use Case diagram: 4.9 Operational Coordination Bettween T&D & DR Resources

Figure: 24

Adjust Schedule
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{F89C4740-5F48-4b30-A169-9177A1168109}

 

Connections
Connector	Source	Target	Notes	
Dependency  Adjusted Schedule 
Source -> Destination 
	Public  
Adjust Schedule
 	Public  
4.8.2 DR Exedcution - Direct Load Control

Generalization  Limit Violation 
Source -> Destination 
	Public  
Check againts circuit operating limits
 	Public  
Adjust Schedule

 

Apply Retail Uplift Charges
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{532FE11F-A3F0-4221-B65B-31790A1CB029}

 

Connections
Connector	Source	Target	Notes	
Dependency   
Source -> Destination 
	Public  
Apply Retail Uplift Charges
 	Public  
Assess Congestion Uplift Charges

Dependency   
Source -> Destination 
	Public  
Energy Service Provider
 	Public  
Apply Retail Uplift Charges

 

Assess Congestion Uplift Charges
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{5E514530-C77C-4a33-8978-59D5BF41F5DF}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
Load Forecast
 	Public  
Assess Congestion Uplift Charges

Dependency   
Source -> Destination 
	Public  
Check againts circuit operating limits
 	Public  
Assess Congestion Uplift Charges

Dependency   
Source -> Destination 
	Public  
Apply Retail Uplift Charges
 	Public  
Assess Congestion Uplift Charges

Generalization   
Source -> Destination 
	Public  
Load Forecast by Circuit
 	Public  
Assess Congestion Uplift Charges

Dependency   
Source -> Destination 
	Public  
Assess Congestion Uplift Charges
 	Public  
4.8.1 DR Execution - Dynamic Price-Based

Generalization   
Source -> Destination 
	Public  
Load Forecast
 	Public  
Assess Congestion Uplift Charges

 

Check againts circuit operating limits
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{BB1DD2EA-E537-47ef-A779-F39FD1540B4F}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
Load Forecast
 	Public  
Check againts circuit operating limits

Generalization  Limit Violation 
Source -> Destination 
	Public  
Check againts circuit operating limits
 	Public  
Adjust Schedule

Association   
Unspecified 
	Public  
Distribution Operator
 	Public  
Check againts circuit operating limits

Dependency   
Source -> Destination 
	Public  
Check againts circuit operating limits
 	Public  
Assess Congestion Uplift Charges

Generalization   
Source -> Destination 
	Public  
Load Forecast by Circuit
 	Public  
Check againts circuit operating limits

Dependency   
Source -> Destination 
	Public  
Identify Impacted Circuits
 	Public  
Check againts circuit operating limits

Dependency   
Source -> Destination 
	Public  
Check againts circuit operating limits
 	Public  
4.0 Execute DR Event

Generalization   
Source -> Destination 
	Public  
Load Forecast
 	Public  
Check againts circuit operating limits

 

Check for Distribution Circuit Contraints
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{F5DEB07A-6B66-4843-95A1-428802431550}

 

Connections
Connector	Source	Target	Notes	
Dependency  DLC 
Source -> Destination 
	Public  
Check for Distribution Circuit Contraints
 	Public  
4.8.2 DR Exedcution - Direct Load Control

Dependency   
Source -> Destination 
	Public  
Check for Distribution Circuit Contraints
 	Public  
4.8.1 DR Execution - Dynamic Price-Based

Dependency   
Source -> Destination 
	Public  
Check for Distribution Circuit Contraints
 	Public  
4.8.2 DR Execution - Notification Based

Dependency   
Source -> Destination 
	Public  
4.0 Execute DR Event
 	Public  
Check for Distribution Circuit Contraints

 

Identify Impacted Circuits
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{979C6BB7-069A-4450-82DE-D1735D7E694E}

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
4.8.2 DR Exedcution - Direct Load Control
 	Public  
Identify Impacted Circuits

Dependency   
Source -> Destination 
	Public  
4.8.2 DR Execution - Notification Based
 	Public  
Identify Impacted Circuits

Dependency   
Source -> Destination 
	Public  
Identify Impacted Circuits
 	Public  
Check againts circuit operating limits

Dependency   
Source -> Destination 
	Public  
4.8.1 DR Execution - Dynamic Price-Based
 	Public  
Identify Impacted Circuits

 

Load Forecast by Circuit
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{482B6D5B-7079-443f-B4C0-7833CE760E55}

 

Connections
Connector	Source	Target	Notes	
Generalization   
Source -> Destination 
	Public  
Load Forecast by Circuit
 	Public  
Assess Congestion Uplift Charges

Generalization   
Source -> Destination 
	Public  
Load Forecast by Circuit
 	Public  
Check againts circuit operating limits

Dependency   
Source -> Destination 
	Public  
Energy Service Provider
 	Public  
Load Forecast by Circuit

Sequence  Load Profile Forecast by Circuit 
Source -> Destination 
	Public  
Load Forecast by Circuit
 	Public  
DMS

 

Locational Wholesale Prices
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{4F41F7A1-89BC-44fe-B2E6-88320AD563EB}

 

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
Locational Wholesale Prices
 	Public  
Energy Service Provider

 

Specify Load Profile
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{8D571D42-DD1F-4654-B962-C5A71E085273}

 

Connections
Connector	Source	Target	Notes	
Association   
Unspecified 
	Public  
Electricity Consumer
 	Public  
Specify Load Profile

Dependency   
Source -> Destination 
	Public  
Specify Load Profile
 	Public  
Energy Service Provider

 

Wholesale Locational Prices
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	4.0 Execute DR Event     Keywords:   
Detail:		Created on 10/24/2009.  Last modified on 10/26/2009.
GUID:		{38D83763-50D5-4da0-8CC0-721EB6A7D064}

 

5.0 Post DR Event Management 
Type:		Package 
Status:		Proposed. Version 1.0. Phase 1.0.
Package:	DR Use Cases
Detail:		Created on 10/26/2009. Last modified on 10/26/2009
GUID:		{037D8CF3-94F0-4d55-A20B-8B0A26D9E14A}

5.0 Post DR Event Management - (Use Case diagram) 
Created By:	Ludo on 10/20/2009
Last Modified:	10/27/2009
Version:		1.0. Locked: False
GUID:		{D4E521BC-6643-4763-999E-6C5295161F2F}
This diagram shows the Use Cases for the functions which are performed after the DR Event has finished.

Figure: 25

5.0 Post DR Event Management
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/26/2009.
GUID:		{EC23451E-0A86-4e2c-BB04-CF03D965363E}

 

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
5.0 Post DR Event Management
 	Public  
5.3 Post DR Event M&V / Settlement (Open or Not Open Wholesale, Open Retail)

Include   
Source -> Destination 
	Public  
5.0 Post DR Event Management
 	Public  
5.2 Post DR Event M&V / Settlement (No Open Wholesale, No Open Retail)

Include   
Source -> Destination 
	Public  
5.0 Post DR Event Management
 	Public  
5.1 Post DR Event M&V / Settlement (Open Wholesale, No Open Retail)

Dependency   
Source -> Destination 
	Public  
4.0 Execute DR Event
 	Public  
5.0 Post DR Event Management

 

5.1 Post DR Event M&V / Settlement (Open Wholesale, No Open Retail)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/26/2009.
GUID:		{1E157D5E-B7B9-4775-9F09-442A811B0E97}

After DR Event has been completed, then Measurement and Verification (M&V) can take place to confirm action has been taken or measure the response.  After the M&V, then the Financial Settlement is calculated and sent to the Electricity Customer.

This Use Case covers the scenarios with an open Wholesale, but no Open Retail Markets.

Constraints	
Ÿ	RELEASE-RECALL: (Pre-condition, Status is Proposed)
DR has finished Deployment Period so calculations for M&V and Settlement can now take place.	

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
5.0 Post DR Event Management
 	Public  
5.1 Post DR Event M&V / Settlement (Open Wholesale, No Open Retail)

Sequence diagram: 5.1  Post DR M&V (Open Wholesale,  No Open Retail)

Figure: 26

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/20/2009.
GUID:		{1E306561-41D9-4265-9F56-CF3AA9926FAE}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/22/2009.
GUID:		{82236D05-5A7B-4531-BB08-2B0AEE7442F4}

 

Connections
Connector	Source	Target	Notes	
Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/22/2009.
GUID:		{A2FCB08C-2EA2-4f1f-B897-7B15AAA794BA}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/20/2009.
GUID:		{D68E38FD-624A-4851-98A7-A5663852D82D}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/23/2009.  Last modified on 10/23/2009.
GUID:		{ECFD1505-70B8-4762-8872-1CB2B847FF8A}

 

5.2 Post DR Event M&V / Settlement (No Open Wholesale, No Open Retail)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/26/2009.
GUID:		{803A324B-F4A6-49da-A58D-9AB2FEFCB00A}

After DR Event has been completed, then Measurement and Verification (M&V) can take place to confirm action has been taken or measure the response.  After the M&V, then the Financial Settlement is calculated and sent to the Electricity Customer.

This Use Case covers the scenarios with no open Wholesale and no Open Retail Markets.

Constraints	
Ÿ	RELEASE-RECALL: (Pre-condition, Status is Proposed)
DR has finished Deployment Period so calculations for M&V and Settlement can now take place.	

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
5.0 Post DR Event Management
 	Public  
5.2 Post DR Event M&V / Settlement (No Open Wholesale, No Open Retail)

Sequence diagram: 5.2 Post DR M&V (No Open Wholesale, No Open Retail)

Figure: 27

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/22/2009.
GUID:		{1056C875-6FEE-4a9a-82A4-4C3F643F2273}

 

Connections
Connector	Source	Target	Notes	
Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/22/2009.
GUID:		{11056A0C-1904-40f3-BD33-7A36476B942A}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/20/2009.
GUID:		{5B4A355B-1944-49a9-B0F3-5401CB6FE34D}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

  

5.3 Post DR Event M&V / Settlement (Open or Not Open Wholesale, Open Retail)
Type:		UseCase    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/26/2009.
GUID:		{D4AC7EC3-F7E3-4533-867B-D68AFF3DB924}

After DR Event has been completed, then Measurement and Verification (M&V) can take place to confirm action has been taken or measure the response.  After the M&V, then the Financial Settlement is calculated and sent to the Electricity Customer.

This Use Case covers the scenarios with no Open Retail Markets, and includes either Open or not Open Wholesale Markets..

Constraints	
Ÿ	RELEASE-RECALL: (Pre-condition, Status is Proposed)
DR has finished Deployment Period so calculations for M&V and Settlement can now take place.	

Connections
Connector	Source	Target	Notes	
Include   
Source -> Destination 
	Public  
5.0 Post DR Event Management
 	Public  
5.3 Post DR Event M&V / Settlement (Open or Not Open Wholesale, Open Retail)

Sequence diagram: 5.3 Post DR M&V (Open or Not Open Wholesale, Deregulated Retail)

Figure: 28

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/20/2009.
GUID:		{7931F82F-FE77-4e28-8E93-1B1055FD53B3}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/22/2009.
GUID:		{AA60E4CC-3A10-4b04-AA9B-C644FBD7A1D9}

 

Connections
Connector	Source	Target	Notes	
Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/20/2009.
GUID:		{BA45E48F-47D6-49b1-9F36-FFF564A58C53}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/20/2009.
GUID:		{C6459C1A-78F5-4003-A707-29DCB8DCE810}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Billing/Settlement-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

 

<anonymous>
Type:		Sequence    
Status:		Proposed.  Version 1.0.  Phase 1.0.
Package:	5.0 Post DR Event Management     Keywords:   
Detail:		Created on 10/20/2009.  Last modified on 10/20/2009.
GUID:		{EBFDE721-0A3D-4fec-AB02-B4766ED7801B}

 

Connections
Connector	Source	Target	Notes	
Sequence  Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>

Sequence  Ack-Metering/DR-Data-Message 
Source -> Destination 
	Public  
<anonymous>
 	Public  
<anonymous>