Smart Grid Communication Standards for Demand by oox83341

VIEWS: 8 PAGES: 10

									    Smart Grid Communication Standards
          for Demand Response –
             Data Requirements
               Presentation to NAESB
                   April 15, 2010




1
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

2
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


3
Sample Output – Data Requirements*
                                  2.2 Scheduling and Award Notification (Reliability)
                                           2.2.2 Advanced Notification - SP
                                                                                                     Mandatory or
              Business Data Element                           Business Description                     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
                                                  Identifier assigned to the Zone in which the
    2.30-Zone ID                                  Facility is located                            M

                                                  Name of the Zone in which the Facility is
    2.31-Zone (from CIM)                          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
                                                  Idenitifier assigned to the Designated
    5.80-Designated Dispatch Entity ID            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

4                          * Partial list of one of 35 message flows
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
5 wholesale message
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
6    • Device information, such as meter and generator information
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


7
  Example – 2.2.2 Advanced Notification
  Activity Diagram
Scheduling & Award Notification - Reliability                                                                                                                                         Activity Diagram Conventions
                                                                                                                                                                                                                                  Messaging - The source of the message is depicted by the message text
                                                                                                                                                                                                                                  description swimlane location, the arrow depicts the message destination.

                                                                                                                                                                                                Process out of scope                             Primary Data Flow (Message in Scope)
  Scheduling Entity Service Provider




                                                                                                                                                                                                Process in scope                                 Optional Primary Data Flow (Message in Scope)




                                                                                                                                                                PROPRIETARY SYSTEMS
                                                                                                                                                                 COMMUNICATE USING
                                                                                                                                                                                                Predefined Process in scope                      Secondary Data Flow (Message out of Scope)
                          (SP)




                                                                                                                                                                                                Decision                                         Optional Secondary Data Flow (Message out of Scope)

                                                                                                                                                                                                Iterative Process

                                                                                                                                                                                                Process Steps Specific Use Case




                                       Start                                                                                                            Identify Resources
       (SE)




                                                    Submit Availability
                                                                                                                                                            to Advise


                                               2.2.1(Availability Parameters)




                                                                                                                                                    2.2.2(Advanced Notification)




                                                                                                                                                         Create Notification
                                                                                                                                                           for Reliability



                                                      Perform Load
                                                                                              (System Conditions)
           System Operator (SO)




                                                      Forecast and              Reassess
                                                                                                                                               (Reliability Event Parameters)
                                                      Supplemental              Reliability
                                                      Commitment



                                                                                                                                                                 Yes
                                                                                                                         (Anticipated Reliability
                                                                                                                                 Issue)
                                                                                                        System      No
                                                                                                                                                            Need for DR
                                                                                                        Secure


                                                                                                                                                                   No
                                                                                                          Yes




                                                                                                                                                              End




      8
Example – 2.2.2 Advanced Notification
Data Element Worksheet




9
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
10

								
To top