MOD Demand and Energy Data. Darrel Richardson, NERC Senior Standards Developer Jeff Rooker, SPP RE Lead Compliance Engineer May 12, 2016

Transcription

1 MOD Demand and Energy Data Darrel Richardson, NERC Senior Standards Developer Jeff Rooker, SPP RE Lead Compliance Engineer May 12, 2016

2 Administrative Items NERC Antitrust Guidelines It is NERC s policy and practice to obey the antitrust laws and to avoid all conduct that unreasonably restrains competition. This policy requires the avoidance of any conduct that violates, or that might appear to violate, the antitrust laws. Among other things, the antitrust laws forbid any agreement between or among competitors regarding prices, availability of service, product design, terms of sale, division of markets, allocation of customers or any other activity that unreasonably restrains competition. Notice of Open Meeting Participants are reminded that this webinar is public. The access number was widely distributed. Speakers on the call should keep in mind that the listening audience may include members of the press and representatives of various governmental authorities, in addition to the expected participation by industry stakeholders. 2

3 Overview Today s Objective Development History Effective Dates Applicability Purpose Requirements Questions & Answers 3

4 Today s Objective ERO Enterprise conducts outreach or education to industry and Regional Entities regarding Reliability Standards approved by FERC in FERC approved MOD on February 18, Today s webinar will focus on the MOD Reliability Standard, including version 1 and changes made to version 1 in version 2. 4

5 History MOD combined MOD-016 through MOD-019 and MOD- 021 Five standards into one standard Ten Requirements down to four requirements Addresses ten directives from FERC Order 693 MOD revised R3 and R4 in response to FERC directives 5

6 Effective Dates MOD goes into effect July 1, 2016 MOD-016 through MOD-019 and MOD-021 retired as MOD goes into effect MOD goes into effect October 1, 2016 MOD retired as MOD goes into effect 6

7 Applicability Planning Authority (PA) and Planning Coordinator (PC) (hereafter collectively referred to as the PC ) This proposed standard combines PA with PC in the list of applicable functional entities. The NERC Functional Model lists PC while the registration criteria list PA, and they are not yet synchronized. Until that occurs, the proposed standard applies to both PA and PC. Transmission Planner (TP) Balancing Authority (BA) Resource Planner (RP) Load-Serving Entity (LSE) Distribution Provider 7

8 Purpose Purpose To provide authority for applicable entities to collect Demand, energy and related data to support reliability studies and assessments and to enumerate the responsibilities and obligations of requestors and respondents of that data. 8

9 MOD Requirement R1 R1.Each PC or BA that identifies a need for the collection of Total Internal Demand, Net Energy for Load and Demand Side Management data shall develop and issue a data request to the applicable entities in its area. The data request shall include: 1.1. A list of TPs, BA, LSE, and DPs that are required to provide the data ( Applicable Entities ) A timetable for providing the data (A minimum of 30 calendar days must be allowed for responding to the request). 9

10 MOD Requirement R A request to provide any or all of the following actual data, as necessary: o Integrated hourly Demands in megawatts for the prior calendar year. o Monthly and annual integrated peak hour Demands in megawatts for the prior calendar year If the annual peak hour actual Demand varies due to weather-related conditions (e.g., temperature, humidity or wind speed), the Applicable Entity shall also provide the weather normalized annual peak hour actual Demand for the prior calendar year. o Monthly and annual Net Energy for Load in gigawatthours for the prior calendar year. 10

11 MOD Requirement R1 o Monthly and annual peak hour controllable and dispatchable Demand Side Management under the control or supervision of the System Operator in megawatts for the prior calendar year. Three values shall be reported for each hour: 1) the committed megawatts (the amount under control or supervision), 2) the dispatched megawatts (the amount, if any, activated for use by the System Operator), and 3) the realized megawatts (the amount of actual demand reduction). 11

12 MOD Requirement R A request to provide any or all of the following forecast data, as necessary: o Monthly peak hour forecast Total Internal Demands in megawatts for the next two calendar years. o Monthly forecast Net Energy for Load in gigawatthours for the next two calendar years. o Peak hour forecast Total Internal Demands (summer and winter) in megawatts for ten calendar years into the future. o Annual forecast Net Energy for Load in gigawatthours for ten calendar years into the future. o Total and available peak hour forecast of controllable and dispatchable Demand Side Management (summer and winter), in megawatts, under the control or supervision of the System Operator for ten calendar years into the future. 12

13 MOD Requirement R A request to provide any or all of the following summary explanations, as necessary, about: o The assumptions and methods used in the development of aggregated Peak Demand and Net Energy for Load forecasts. o The Demand and energy effects of controllable and dispatchable Demand Side Management under the control or supervision of the System Operator. o How Demand Side Management is addressed in the forecasts of its Peak Demand and annual Net Energy for Load. o How the controllable and dispatchable Demand Side Management forecast compares to actual controllable and dispatchable Demand Side Management for the prior calendar year and, if applicable, how the assumptions and methods for future forecasts were adjusted 13

14 MOD Requirement R1 o How the peak Demand forecast compares to actual Demand for the prior calendar year with due regard to any relevant weather-related variations (e.g., temperature, humidity, or wind speed) and, if applicable, how the assumptions and methods for future forecasts were adjusted. 14

15 Requirement R1 Requirement R1 Defines o Who is to provide the data o The timeframe for providing the data o The data allowed to be collected Compliance Was a data request issued? o Yes Request must contain: Who is to provide the data The timeframe for providing the data At least one item from Requirement R1 parts 1.3 through 1.5 o No There is no compliance obligation 15

16 MOD Requirement R2 R2. Each Applicable Entity, identified in a data request, shall provide the data requested by its PC or BA in accordance with the data request issued pursuant to Requirement R1. 16

17 Requirement R2 Requirement R2 Requires an entity defined in the data request to provide the data Compliance Was a data request received? o Yes Did the entity provide the data in accordance with the data request defined in Requirement R1? o No There is no compliance obligation 17

18 MOD Requirement R3 R3. The PC or the BA shall provide the data collected under Requirement R2 listed under Requirement R1 Parts 1.3 through 1.5 for their area to the applicable Regional Entity within 75 days of receiving a request for such data, unless otherwise agreed upon by the parties. 18

19 Requirement R3 Requirement R3 Ensures data is passed on from the PC or BA to the Regional Entity (RE) Compliance Was a request issued by the RE? o Yes Did the entity receiving the request provide the data defined in the request? Did the entity respond to the data request within the timeframe defined in R3? o No There is no compliance obligation 19

20 MOD Requirement R4 R4. Any Applicable Entity shall, in response to a written request for the data included in parts of Requirement R1 from a PC, BA, TP or RP with a demonstrated need for such data in order to conduct reliability assessments of the Bulk Electric System, provide or otherwise make available that data to the requesting entity. This requirement does not modify an entity s obligation pursuant to Requirement R2 to respond to data requests issued by its PC or BA pursuant to Requirement R1. Unless otherwise agreed upon, the Applicable Entity: 20

21 MOD Requirement R4 shall not be required to alter the format in which it maintains or uses the data; shall provide the requested data within 45 calendar days of the written request, subject to part 4.1 of this requirement; unless providing the requested data would conflict with the Applicable Entity s confidentiality, regulatory, or security requirements and 4.1 If the Applicable Entity does not provide data requested under this requirement because (1) the requesting entity did not demonstrate a reliability need for the data; or (2) providing the data would conflict with the Applicable Entity s confidentiality, regulatory, or security requirements, the Applicable Entity shall, within 30 calendar days of the written request, provide a written response to the requesting entity specifying the data that is not being provided and on what basis 21

22 Requirement R4 Requirement R4 Allows for neighboring entities to obtain data Requires a response even if the entity is not providing the data Compliance Did the entity receive a request from a neighboring entity? o Yes Did the entity provide the data? Yes» Did the entity provide all of the requested data within the timeframe defined in Requirement R4? No» Did the entity provide written notification within the timeframe why it was not responding to the data request? o No There is no compliance obligation 22

23 Jeff Rooker, PE Lead Compliance Engineer SPP RE Phone Darrel Richardson Senior Standards Developer