1	Wholesale Use Cases

1.1	NAESB Demand Response Use Cases for NIST Smart Grid

Figure 1: NAESB-NIST-SMART-GRID-DR-USE-CASES 

1.1.1	Actors

Figure 2: Actors 

1.1.1.1	DR Aggregator
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. 

1.1.1.2	DR Asset
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.

1.1.1.3	DR Resource
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).

1.1.1.4	Demand Response Program
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.

1.1.1.5	Distributed Energy Resource (DER)
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

1.1.1.6	Electricity Consumer
Any entity that consumes electricity.

1.1.1.7	Load Serving Entity (LSE)
The entity that is responsible for serving the Electricity Customers Electricity needs. An LSE may also perform the role of DR Aggregator.

1.1.1.8	System Operator
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 ISO/RTO companies that perform this function

1.2	Primary Use Cases

Figure 3: Use Cases for DR Programs 

1.2.1	Activate Demand Response Event
Used to inform Recipients that a DR event has been called by the System Operator. DR Events may be called for reliability, emergency or other situations as determined by the System Operator.

The time periods, deadlines and transitions during which Demand Resources perform.  The System Operator shall specify the duration and applicability of a Demand Response Event.  All deadlines, time periods and transitions may not be not applicable to all Demand Response products or services.

1.2.1.1	Information Requirements

Information Requirement	Type	Status	Difficulty	Priority	    Description	
Effective-Start-Date-Time	Functional	Proposed	Medium	Medium	The starting date and time when DR resources are expected to comply with their obligations under a DR program.	
Estimated-Duration	Functional	Proposed	Medium	Medium	A decimal representation of the expected duration of the event with integers representing hours and decimal positions representing fractions of hours. For example:
•	1.5 indicates a duration of 1 hour and 30 minutes from the Effective-Start-Date-Time

Event-Description	Functional	Proposed	Medium	Medium	A description of the event that is being announced by the System Operator.	
Event-Identifier	Functional	Proposed	Medium	Medium	A unique identifer for the event. Should be expressed as a URI in accordance with http://www.w3.org/TR/uri-clarification/#uri-schemes	
Location	Functional	Proposed	Medium	Medium	An identifier used to indicate the location affected by this event.	
Location-type	Functional	Proposed	Medium	Medium	A value used to interpret the value contained in the Location element. Examples of Location-type include:
•	Zone
•	Node
•	Zip-code
•	USNG

Measurement	Functional	Proposed	Medium	Medium	Information provided by a DR Participant indicating consumption levels over time. A Measurement Message contains all required information needed by a System Operator to assess DR Asset or Resource Performance.	
Message-Exchange-Pattern	Functional	Proposed	Medium	Medium	The means by which DR event information is communicated between parties. The following are valid options: 
•	In-Only 
•	Robust In-Only
•	In-Out 

Refer to http://www.w3.org/TR/wsdl20-adjuncts/#patterns for complete descriptions.	
TimeStamp	Functional	Proposed	Medium	Medium	The date and time when the event was announced. MUST be in ISO 8601 standard format	

1.2.1.2	Sequence Diagram

	Activate Demand Response Event Sequence Diagram

1.2.2	Asset or Resource Registration and Declaration 
The capabilities of each asset or resource must be made known to the controlling entities that may dispatch the asset/resource as part of a demand response program. This use case may be used to register an asset/resource into a DR program or to declare an asset/resource capabilities/availability while in a program. For example a the owner of a DR resource or asset may wish to declare thier inability to shed load (an outage) due to Summer shutdown or may wish to reduce the available capacity of a resource/asset due to equipment maintenance or other causes.

Information Requirement	Type	Status	Difficulty	Priority	Description	
Asset ID	Functional	Proposed	Medium	Medium	Uniquely identifies a DR Asset	
Available-Capacity	Functional	Proposed	Medium	Medium	The total amount of power (negawatts) available from the asset/resource. Expressed in integer format representing the amount of kilowatts available.	
Effective-End-Date-Time	Functional	Proposed	Medium	Medium	The effective end date and time when an assets/resource is available/unavailable	
Effective-Start-Date-Time	Functional	Proposed	Medium	Medium	The start date and time which an asset/resource is available/unavailable	
Location	Functional	Proposed	Medium	Medium	An identifier to indicate the location of the asset/resource	
Location-type	Functional	Proposed	Medium	Medium	A value used to interpret the value contained in the Location element. Examples of Location-type include:
•	Zone
•	Node
•	Zip-code
•	USNG	
Maximum-Duration	Functional	Proposed	Medium	Medium	The maximum amount of time the asset/resource is capable of delivering power (negawatts). Expressed in hours using decimal notation. For example a value of 0.5 indicates a maximum duration of 30 minutes which the  asset/resource can reduce power consumption by the level indicated in Available-Capacity.	
Minimum-Duration	Functional	Proposed	Medium	Medium	The minimum amount of time that an Asset/Resource Owner is willing to allow the resource/asset to be utilized during a DR event. Expressed in decimal format representing hours. For example a value of 1.5 indicates that an asset/resource must be utilized for no less than one hour and 30 minutes during any DR event.	
Parent-Resource ID	Functional	Proposed	Medium	Medium	Used by an Asset to indicate that it "belongs to" a particular Resource. Assets may be aggregated into a Resource, but are not required to. Resources are atomic and may not be aggregated.	
Report-type	Functional	Proposed	Medium	Medium	Indicates the type or report being issued by the Asset or Resource Owner. This is an enumerated value containing one of the following:
•	REGISTRATION (to register a new asset/resource)
•	OUTAGE
•	DECLARATION (used to update asset/resource characteristics e.g. Available capacity, etc.)
•	RETIREMENT
	
Resource ID	Functional	Proposed	Medium	Medium	Uniquely identifies a DR Resource	
Response-time	Functional	Proposed	Medium	Medium	The amount of time before an asset/resource is capable of meeting its full performance, in response to a request by a controlling entity to shed load. Expressed as minutes in decimal format	

1.2.2.1	Constraints 
MIX-MAX-DURATION-CONSTRAINT
The Minimum-duration value MUST be less than the Maximum-duration value 

1.2.2.2	Sequence Diagram

Asset or Resource Registration and Declaration
1.2.3	Broadcast Locational Wholesale Price  
The System Operator calculates the price of products per location and communicates the price to interested parties

1.2.3.1	Information Requirements

Information Requirement	Type	Status	Difficulty	Priority	   Description	
Currency	Functional	Proposed	Medium	Medium	Identifier used to interpret the price element. MUST follow ISO 4217 standard.	
Duration	Functional	Proposed	Medium	Medium	The amount of time for which this price is valid, commencing at the Effective-Date-Time specified. A value of zero indicates infinity.
Specified in decimal notation where integers represent minutes and decimals represent fractions of minutes. For example:
•	5 indicates that prices will be published every 5 minutes
•	.5 indicates that prices will be published every 30 seconds

Effective-Date-Time	Functional	Proposed	Medium	Medium	The date and time which the electricity price is in effect. In ISO 8601 standard format.	
Location	Functional	Proposed	Medium	Medium	An identifier used to indicate an area which this price is in effect. A value of "null" indicates that the price is in effect for all areas.	
Location-type	Functional	Proposed	Medium	Medium	A value used to interpret the value contained in the Location element. Examples of Location-type include:
•	Zone
•	Node
•	Zip-code
•	USNG	
Message-Exchange-Pattern	Functional	Proposed	Medium	Medium	The means by which price information is communicated to any party that is interested in receiving this information. The following are valid options: 
•	In-Only 
•	Robust In-Only
•	In-Out 

Refer to http://www.w3.org/TR/wsdl20-adjuncts/#patterns for complete descriptions.	
Price	Functional	Proposed	Medium	Medium	Expressed in decimal notation with a precision up to 6 decimal places. Prices MAY be either positive or negative	
Product-Identifier	Functional	Proposed	Medium	Medium	Identifies the type of product (e.g. electricity, regulation, etc.) which this price pertains. Contains an enumeration of various products that may be offered. Extensibility MUST be supported in order to accommodate multiple jurisdictions and markets.	
Publishing-Interval	Functional	Proposed	Medium	Medium	Indicates the frequency with which price information is expected to be published. Specified in decimal notation where integers represent minutes and decimals represent fractions of minutes. For example:
•	5 indicates that prices will be published every 5 minutes
•	.5 indicates that prices will be published every 30 seconds	
TimeStamp	Functional	Proposed	Medium	Medium	Indicates the Date and Time when this information was published. MUST follow ISO 8601 standard representation.	
Unique-Identifier	Functional	Proposed	Medium	Medium	An identifier used to identify the message. Should be expressed as a URI in accordance with http://www.w3.org/TR/uri-clarification/#uri-schemes	
Unit-of-Measure	Functional	Proposed	Medium	Medium	Indicates the unit of measure for which the price pertains. MUST be complaint with the International System of Units as defined by NIST SP 330, ref: http://physics.nist.gov/Pubs/SP330/sp330.pdf

Examples of NIST compliant units of measure include:
•	kW
•	MW 	

1.2.3.2	Constraints 
MUST-SUPPORT-IN-ONLY-PATTERN
At a minimum the "IN-only" Exchange pattern MUST be supported. This will ensure that any party, DR Asset or DR Resource that wishes to receive prices may access this information. 
1.2.3.3	Sequence Diagram

Broadcast Locational Wholesale Price Sequence Diagram
1.2.4	Cease Demand Response Event
Occurs when a System Operator decides there is no further need for load reductions and notifies appropriate parties.

1.2.4.1	Information Requirements

Information Requirement	Type	Status	Difficulty	Priority	Description	
Effective-End-Date-Time	Functional	Proposed	Medium	Medium	The date and time when DR resources are no longer required to curtail load and consumption may return to normal levels.	
Event-Identifier	Functional	Proposed	Medium	Medium	A unique identifer that identifies the previously announced DR Event which is being ceased. MUST refer to an existing DR Event that is in effect.	
Location	Functional	Proposed	Medium	Medium	An identifier used to indicate the location affected by this "cease event".	
Location-type	Functional	Proposed	Medium	Medium	A value used to interpret the value contained in the Location element. Examples of Location-type include:
•	Zone
•	Node
•	Zip-code
•	USNG	
Measurement	Functional	Proposed	Medium	Medium	Information provided by a DR Participant indicating consumption levels over time. A Measurement Message contains all required information needed by a System Operator to assess DR Asset or Resource Performance.	
Message-Exchange-Pattern	Functional	Proposed	Medium	Medium	The means by which DR event information is communicated between parties. The following are valid options: 
•	In-Only 
•	Robust In-Only
•	In-Out 
Refer to http://www.w3.org/TR/wsdl20-adjuncts/#patterns for complete descriptions.	
TimeStamp	Functional	Proposed	Medium	Medium	The date and time when the "cease event" was announced. MUST be in ISO 8601 standard format	

1.2.4.2	Constraints 

MUST-BE-ACTIVE-DR-EVENT
Can only be issued for an active DR event 
1.2.4.3	Sequence Diagram

Cease Demand Response Event Sequence Diagram
1.2.5	Dispatch DR Asset or Resource
System Operator instructs a DR Asset or Resource to change consumption level.

1.2.5.1	Information Requirements
Information Requirement	Type	Status	Difficulty	Priority	Description	
Effective-Start-Date-Time	Functional	Proposed	Medium	Medium	The starting date and time when a DR Asset or Resource is expected to comply with the dispatch instruction.	
Load-Reduction-Amount	Functional	Proposed	Medium	Medium	The amount of electric power which is to be shed (reduced). Must be interpreted within the context of the Unit-of-Measure value, for example a value of 1 in this element combined with a Unit-of-Measure value of MW would indicate a reduction of 1 megawatt is expected from a DR Asset or Resource.

A value of zero indicates that no load reductions are needed and consumption may return to normal levels.	
Measurement	Functional	Proposed	Medium	Medium	Information provided by a DR Participant indicating consumption levels over time. A Measurement Message contains all required information needed by a System Operator to assess DR Asset or Resource Performance.	
Message-Exchange-Pattern	Functional	Proposed	Medium	Medium	The means by which Dispatch information is communicated between parties. The following are valid options: 
•	In-Only 
•	Robust In-Only
•	In-Out 
Refer to http://www.w3.org/TR/wsdl20-adjuncts/#patterns for complete descriptions.	
Target-Identifier	Functional	Proposed	Medium	Medium	A unique identifier for the DR Asset or DR Resource that is the intended recipient of this dispatch instruction.	
TimeStamp	Functional	Proposed	Medium	Medium	Indicates the Date and Time when the dispatch instruction was issued. MUST follow ISO 8601 standard representation.	
Unit-of-Measure	Functional	Proposed	Medium	Medium	Indicates the unit of measure for which the Load-Reduction-Amount pertains. MUST be complaint with the International System of Units as defined by NIST SP 330, ref: http://physics.nist.gov/Pubs/SP330/sp330.pdf

Examples of NIST compliant units of measure include:
•	kW
•	MW 	

1.2.5.2	 Sequence Diagram

Dispatch DR Asset or Resource Sequence Diagram