ECC Tool Functional Definition
DRAFT
Version 12
Enhanced Curtailment Calculator (ECC)
Functional Requirements
By
Peak Reliability
With support from the ECC Task Force
MMM DD, YYY
ECC Tool Functional Definition
Table of Contents
1 Introduction 4
1.1 Phase I versus Phase II 6
1.2 What this Document Defines 6
1.3 What this Document Does Not Define 6
2 Inputs, Processes, Outputs and Mechanisms 8
2.1 Data Flow 9
2.2 Inputs 9
2.2.1 West-Wide System Model (WSM) 12
2.2.2 State Estimator Savecase Data 12
2.2.3 ECC Model 12
2.2.4 ECC Element Definitions 13
2.2.5 Mapping WSM to ECC 13
2.2.6 Real-Time Data 13
2.2.7 Scheduled Flow (e-Tags) 14
2.2.8 Look-Ahead Data Inputs 15
2.3 ECC Element and Calculations Processes 16
2.3.1 Element Management Process 17
2.3.2 Calculate Shift and Distribution Factors 20
2.3.3 Calculate Element Impacts 23
2.4 Outputs & Mechanisms 25
2.4.1 Visualization of Operational Results 26
2.4.2 User Interface and Displays 28
2.4.3 ECC Alarm Processing 32
2.4.4 Logging and Reporting 33
3 External Access, Controls, and Administration 33
3.1 Import, Export and API 33
3.2 Security 34
3.3 User Roles, Rights, and Access 34
3.4 Non-RC User Access 35
3.5 ECC Administration 35
3.6 Controls 35
3.7 Documentation 36
4 Performance Metrics 36
4.1 Performance 36
4.2 Availability 36
4.3 Data Retention 37
Appendix A: Terms, Acronyms, and Definitions 38
1 Introduction
This document was developed by Peak Reliability (Peak) in consultation with the ECC Task Force to define minimum functional requirements for the Enhanced Curtailment Calculator tool.
The ECC is envisioned to serve as a congestion management tool used by Reliability Coordinators to manage power system congestion within the Western Interconnection. Peak views the ECC as being a reliability tool that can be used in conjunction with other RC reliability tools to ensure acceptable system performance for the Bulk Electric System.
Peak, as well as many TOPs in the Western Interconnection, perform Real-time Assessments using a suite of real-time reliability tools to understand how the system is performing on a pre- and post-Contingency basis. These tools generally include SCADA, state estimation, and Real-time Contingency Analysis (RTCA), and may include other advanced applications such as real-time voltage and transient stability analysis. When real-time tools indicate that the system is performing unacceptably pre- or post-Contingency or is trending toward unacceptable performance (i.e., SOL exceedance is occurring or is expected to occur), system operators are expected to take action to prevent or mitigate the condition. This action can take several forms including making adjustments in the uses of the transmission system (i.e., schedule curtailments or adjustments).
Peak Reliability Coordinator System Operators (RCSOs) use a suite of reliability tools to assess pre- and post-Contingency performance. With the addition of the ECC to the RCSO’s toolkit, the RCSOs will not only have increased situational awareness (phase I), but it is also envisioned that the RCSOs will have the ability to initiate curtailments, if necessary, to ensure reliability (phase II). The ECC will have the ability to describe and quantify the contributors of flow on ECC defined elements. The RCSO will use the ECC to determine the cause (source) of unacceptably high flows that are observed in the RC’s suite of real-time tools. With this information, the RCSO in collaboration with the TOP or BA can choose to address the reliability issue through local actions or may choose to have the RC use the ECC to initiate curtailments and identify redispatch requirements necessary to relieve the condition. Any curtailments or redispatch requirements initiated by the ECC will be done in a fair and equitable manner according to the methodology and rules programmed into the tool; the methodology and rules will be consistent with the FERC pro forma tariff.
The current Western Interconnection congestion management tool, webSAS, is used to manage the impacts of unscheduled flow on the six Transmission Paths that have satisfied the qualification process criteria described in the WECC Unscheduled Flow Mitigation Plan (UFMP). While the webSAS tool manages congestion only on the six Qualified Paths consistent with the current approved methodology, the ECC will have the ability to manage congestion on any BES Facility (or grouping of Facilities) in the Western Interconnection through the use of defined ECC Elements. The ECC will have the flexibility to define and update monitored Elements as necessary to ensure reliability. Peak will collaborate with TOPs to define the list of Elements based on historical performance of areas prone to congestion. Elements can also be created on the fly by RCSOs as needed based on RCSO Real-time Assessments and Operational Planning Analysis results. It is envisioned that the ECC will address implementation of the FERC-approved curtailment methodology including any resulting modifications to the current UFMP as part of Phase II. The expectation is that the webSAS tool would be retired upon completion of Phase II of the ECC project. Any proposed modifications to the approved methodology or current UFMP will undergo a stakeholder vetting process prior to implementation as part of Phase II.
Note: In this document an “Element” or “Monitored Element” is defined as including all items listed in the NERC definition of element in addition to the individual or grouping of facilities, lines, paths, or flowgates as monitored by the RC. In most circumstances, this document is referring to a flowgate or a path when the term “Element” is used, but nothing in this document should be interpreted to imply the broader use of the word “Element” is not also acceptable.
1.1 Phase I versus Phase II
The ECC project will be broken into two phases. Phase I covers all aspects of the ECC core functionality except for the congestion management component, which falls under phase II. Phase I is intended to establish the basic functionality of the ECC that will serve as the basis for phase II functionality. Accordingly, phase I will allow the RC to identify contributing factors to SOL exceedances, but will be used for situational awareness until phase II is completed. All inputs that will be necessary to support curtailments will be included in phase I; however, the curtailment functionality itself will fall under phase II. The curtailment functionality implemented in phase II will be consistent with FERC approved methodologies and will undergo a stakeholder vetting process.
1.2 What this Document Defines
This document defines minimum functionality for the following Phase I objectives:
· Enhance the RC awareness of real-time and look-ahead operating conditions:
o Calculate impacts on up to 1,000 Elements
o , including contingencies if necessary, as defined and modeled by the RC:
§ Real-Time occupies the current hour (h)
§ Look-ahead occupies the next three hours (i.e. h+1, h+2, and h+3)
o The impact calculation will account for real-time updates of the transmission system data to include existing transmission and generation outages from the West-wide System Model (WSM) via the State Estimator solution provided to the ECC once every five minutes
· Calculation of shift factors every 15 minutes, or sooner, upon a manual execution.
Additionally, every 15 minutes new matrices of factors are created for each hour of the look-ahead time window.
· Identify the sources of power flow, including tagged transactions and untagged transactions including but not limited to Balancing Authority (BA) Area Control Error (ACE) contributions to flow, reserve sharing qualifying events, and tagged or untagged Dynamic Transfers.
· Interface with e-Tag systems for Interchange Transactions information required by the ECC.
· Interface with EIR for entities’ definitions, source/sink points definitions, and POR/POD definitions.
1.3 What this Document Does Not Define
This document does not define the following aspects of the ECC solution and instead, relies on the vendor to propose and define:
· System design constructs including architectures, connectivity, back-up, fail-over, or redundancy needs.
· Detailed definition of graphic user interface (GUI) view screens or displays.
· Detailed definition of data inputs and outputs (I/O).
o Data I/O are classified at the object level but not at the Element level where attributes and metadata are generally defined.
· Phase II detailed functionality as yet undefined due to the need for vetting changes to mitigation procedures in the stakeholder process.
2 Inputs, Processes, Outputs and Mechanisms
The following section defines the functional requirements for the following:
1. Inputs – data objects that flow into the ECC and either consumed by operations/calculations to produce new data objects or as a pass-through for display/reporting.
2. Processes – dimension of the system which perform a function and/or calculation on the input data and models.
3. Outputs – data objects that flow out of the ECC for either display/reporting or downstream application/process inputs.
4. Mechanisms – Ancillary processing outside of the core ECC functionality, consisting of visualization of data, alarming, reporting, etc.
2.1 Data Flow
The graphic below represents the data flow and components of the phase I ECC. Several key inputs, processes, and outputs are designated and further described by the numbers below.
2.2 Inputs
Inputs are data objects required by the ECC for performing operations, calculations, reporting, or display. For the purpose of this specification, each of the following data elements is classified by Data Group, Data Class Name, Description, and Source Name; these represent the anticipated data inputs for ECC.
Detailed definitions are expected to be provided by the vendor within a system design specification or similar artifact and shall include the following detail:
· ECC Use – name of calculation or operation consuming the input data.
· Attributes – data Element details (e.g. PSBank, Name, TapPosition, LastChange, QualityCode).
· Format – expected format of the data object (e.g. CSV, XML, Other).
· Frequency – expected temporal frequency of the data object (i.e. every 5 minutes).
· Trigger – what triggers the data to be an input to ECC.
· Accuracy/Precision – any adjustments to the accuracy or precision from the source data.
· Integration – specified integration methods for retrieving data (e.g. Web Services, Pub/Sub, ICCP).
The ECC will be tightly integrated with the real-time hour (h) data and forecast data for the next three hours (i.e. h+1, h+2, and h+3). To accurately determine the impacts on and contributions to power flows on monitored Elements, the ECC shall use the following inputs.
Source of Record / Data Type / Description /Coordinated Outage System (COS) / Generator Scheduled Outage Information / Forecasted and actual generator outages and derates provided to Peak by TOPs or BAs.
Coordinated Outage System (COS) / Transmission Scheduled Outage Information / Forecasted transmission outages provided to Peak by TOPs or BAs.
EIDE Database / Generator Unit or Generating Station Commitment forecast / Real-time and forecasted generator MW output, service load, and pump storage or aggregation of these values for a generating station.
EIDE Database / Load Forecast Data / Forecasted load for each Balancing Authority Area. The default data is the entire BA Area, but entities may work with Peak to define sub-BA areas to forecast, but Peak at a minimum would require the BA Area forecast.
NAESB EIR Registry / Mapping of Source/Sink and POR/POD data / Mapping will require a manual process by the BAs.
OATI Tagging System / E-Tag Data / E-Tag source/sink and/or POR/POD data, MW profile, transmission priority, and other relevant data for tagged transactions
OATI Tagging System / Net Scheduled Interchange / Net Scheduled Interchange profile for current and look-ahead hours.
OATI Tagging System / EIDE / Next-Hour Dynamic Transfers / Forecasted intra-hour coordinated transfer of energy between BAs.
Registration Reference Data / JOU Allocations (fixed) / Fixed percentage provided by Peak to determine allocation.
State Estimator / Actual Transmission Facility Flows / Actual Transmission flows are available through the SE solution interface.
SCADA / ACE Values / Real-time telemetered ACE values from Balancing Authorities
SCADA / Dynamic Transfer Telemetry / Real-time telemetered data for Dynamic Schedules and Pseudo-Ties reflecting the real-time value of the MW energy flow.
SCADA / BA ACE Offset Value for RSG Response / Real-time telemetered data of the ACE offset used by any BAs in response to their participation in a RSG event
State Estimator / DC Line Flow / MW flow over DC lines as an SE output.
State Estimator / Facility Ratings / Facility Ratings can be updated on the fly so they need to be retrieved from the SE solution instead of the base model WSM.
State Estimator / Path and Flowgate Limits / Interface limits are available through the SE solution interface.
State Estimator / Real-Time Pump Storage / Actual pump MW is available in the SE solution interface.
State Estimator / Real-Time Unit or Generating Station actual MW Output / Actual unit or generating station MW Output is available in the SE solution interface.
State Estimator / Phase Shifter and LTC Data – Real-Time Tap Position / Actual phase shifter and LTC tap is available in the SE solution interface.
State Estimator / Topology - Actual Transmission Outages / Actual values are obtained by the State Estimator.
State Estimator / Topology - Circuit Breaker and Switch Statuses / List of status of all circuit breakers and switches.
State Estimator / IROLs (the limit value) / IROLs are dynamic and are provided in the SE solution interface.
State Estimator / Topology / Actual values are obtained by the State Estimator.
State Estimator / SOLs (the limit value) / SOLs are dynamic and are provided in the SE solution interface.
State Estimator / Generator AGC Response to Generator Outages / State Estimator provides a list of generators that will respond to generator outages.
West-wide System Model / System Topology / Modeled system topology for the Western Interconnection.
2.2.1 West-Wide System Model (WSM)
Peak will provide a network model every four weeks that is used as the base model for all ECC calculations. The WSM base model will be provided in Common Information Model (CIM) format (or another selected format as defined through system design between OATI and Peak.) The WSM base model will include typical modeling attributes including, but not limited to:
· Unique identifiers for equipment