1

Smart Grid Communication Standardsfor Demand Response –

Data Requirements

Presentation to NAESBApril 15, 2010

2

IRC’s Approach to Smart Grid Communication Standards for Demand Response

• Create the business process models of interactions between system operator and market participants– Aligns with PAP09 task for NAESB SGTF Phase 1

• Modeling process– Identify the data requirements

• Aligns with PAP09 task for NAESB SGTF Phase 2 and supports PAP09 task for OASIS

– Develop the information model• Aligns with PAP09 task for OASIS

– Generate message profiles• Aligns with PAP09 task for OASIS

3

IRC Project Status

• IRC has nearly completed the entire process for wholesale DR

• Complete– Business process models – Data requirements

• Finalizing– Information model– Message profiles

• Estimated time to complete data requirements, model and profiles for 35 message flows – Over 2,000 person-hours with approximately 75% of the time

on data requirements• Does not include work for message security

4

Sample Output – Data Requirements*

2.2 Scheduling and Award Notification (Reliability)

2.2.2 Advanced Notification - SP 3.1.1 Regulation Signal - SE

Business Data Element Business DescriptionMandatory or

Optional

0.10-Submittal Date Timestamp for the sender's use M

1.10-Facility ID Identifier assigned to the Facility O

1.11-Facility Name Name of the Facility O

1.20-Resource ID Identifier assigned to the Resource O

1.21-Resource Name Name of the Resource O

2.30-Zone IDIdentifier assigned to the Zone in which the Facility is located M

2.31-Zone (from CIM)Name of the Zone in which the Facility is located O

5.11-SP ID Identifier assigned to the Service Provider M

5.12-SP Name Name of the Service Provider M

5.70-Scheduling Entity ID Identifier assigned to the Scheduling Entity M

5.71-Scheduling Entity Name Name of the Scheduling Entity O

5.80-Designated Dispatch Entity IDIdenitifier assigned to the Designated Dispatch Entity M

5.81-Designated Dispatch Entity Name Name of the Designated Dispatch Entity O

7.10-Program ID Identifier assigned to the Program M

* Partial list of one of 35 message flows

5

Identify Data Requirements

• Started with a representative ISO/RTO data set

• Consolidated and categorized the final list of data elements

• Collaboratively developed operational definitions for each element

• Created worksheet with complete list of data elements, operational definitions and messages

• Each ISO/RTO identified which data elements used in each message flow

• Consolidated worksheet contains the standardized list of data elements for each wholesale message

6

Data Element Categories• 0 - Common Parameters

• Message information that is not related to the facility, resource, external entity, program or market product

• 1- General Resource Information• Data that identifies the facility or resource

• 2 - Location Information• Physical and logical location information

• 3 - Contact Information• Contact information for the facility or resource

• 4 - General Resource Attributes• Characteristics specific to the facility or resource

• 5 - External Entity Relationships• External entities that relate to a facility or resource

• 6 - Device and Qualification Data• Device information, such as meter and generator information

7

Data Element Categories, continued• 7 - General Market/Program Enrollment Data

• Data elements that apply to enrollment in any market or demand response program

• 8 - Offer Parameters• Data elements used in making an offer into a market

• 9 - Energy Market Data• Data elements specific to energy market products/services

• 10 - Ancillary Service Market Data• Data elements specific to ancillary service market

products/services

• 11 - Capacity Market Data• Data elements specific to capacity market products/services

• 12 - Event and Performance• Demand response event data elements and information associated

with measurement and verification

8

Example – 2.2.2 Advanced NotificationActivity Diagram

Scheduling & Award Notification - Reliability

Sys

tem

Ope

rato

r (S

O)

Sch

edul

ing

Ent

ity

(SE

)S

ervi

ce P

rovi

der

(SP

)

2.2.1(Availability Parameters)

(Anticipated Reliability Issue)

(Reliability Event Parameters)

No

2.2.2(Advanced Notification)

Yes

(System Conditions)

CO

MM

UN

I CA

TE

US

ING

P

RO

PR

IET

AR

Y S

YS

TE

MS

Submit Availability

End

Create Notification for Reliability

Need for DRSystem Secure

Start

Perform Load Forecast and Supplemental Commitment

Identify Resources to Advise

Reassess Reliability

Activity Diagram ConventionsMessaging - The source of the message is depicted by the message text description swimlane location, the arrow depicts the message destination.

Process out of scope

Process in scope

Predefined Process in scope

Primary Data Flow (Message in Scope)

Optional Primary Data Flow (Message in Scope)

Secondary Data Flow (Message out of Scope)

Optional Secondary Data Flow (Message out of Scope)Decision

Iterative Process

Process Steps Specific Use Case

Yes

No

9

Example – 2.2.2 Advanced NotificationData Element Worksheet

10

How the IRC process could be used for Phase 2 of NAESB SGTF

• Identify the interactions for which data requirements are needed in PAP 03, PAP 04 and PAP 09-Retail– Update the Data Element Worksheet to capture the list of

interactions in column headers

• Use the sequence diagrams or extend wholesale business process models to identify data elements for each interaction – Specify the data elements in the Data Element Worksheet

• Extend the list of data elements as necessary consistent with the established categories– Include the term and the operational definition for each new data

element, as well as the category in which it belongs