ERCOT Real Time Operational Metering and Communication€¦ · Web viewTraditionally, utilities have used both analog and digital methods of transmission at existing facilities.

ERCOT Nodal Operating Guides

Section 8: Operational MeteringMeteringTelemetry and Communication

Draft (Month, Day, Year)

(Effective Upon Texas Nodal Market Implementation)

SECTION 8: OPERATIONAL METERINGMETERING TELEMETRY AND COMMUNICATION

Contents

8 OPERATIONAL METERINGTELEMETRY AND COMMUNICATION......8-38-28-3

8.1 OPERATIONAL METERING TELEMETRY 8-3 8-2 8-3 8.1.1 ERCOT Interface RTUs 8-48-28.1.2 ERCOT ICCP Interface 8-48-28-58-48.1.3 Validation of Real Time Signals with Settlement Metering for Resources 8-58-28-58-48.1.4 Data from ERCOT to QSE’s 8-58-28.1.5 Data From ERCOT to TDSPTSP 8-58-28.1.6 Data from QSE/TDSPTSP to ERCOT 8-68-28-68-58.1.7 TDSPTSP/QSE TelemetryMetering Restoration 8-108-288-18-88.1.8 QSE and TDSPTSP Data Acquisition8-108-288-18-8

8.2 CALIBRATION AND TESTING 8-11 8-2 8 8-1 8-8 8.2.1 Responsibility 8-118-288-18-88.2.2 Notification 8-118-288-18-88.2.3 Test Equipment 8-118-288-18-98.2.4 Disputes 8-118-288-18-98.2.5 Calibration Testing 8-118-288-18-98.2.6 Exchange of Information 8-128-288-18-98.2.7 Documentation 8-128-288-18-98.2.8 Operator One-line Displays 8-138-288-18-108.2.9 Notification of Changes 8-138-288-18-11

8.3 COMMUNICATIONS 8-13 8-2 8 8-1 8-1 28.3.1 ERCOT WAN 8-138-288-18-128.3.2 ERCOT Responsibilities 8-168-288-18-138.3.3 QSE and TDSPTSP Responsibilities 8-168-288-18-138.3.4 TDSPTSP and QSE Supplied Communications 8-178-288-18-158.3.5 Maintenance and Restoration8-188-288-18-16

8.4 Document Control 8-198-288-18-17

Protocol ReferencesREFERENCE: PROTOCOLS SECTION 12.4.4.1.1 QSE, RESOURCE AND TDSP TSP RESPONSIBILITIES 8- 4 8-3 REFERENCE: PROTOCOL SECTION 12.4.4.1.2, ERCOT RESPONSIBILITIES REFERENCE: PROTOCOLS SECTION 8.8.1, COORDINATION WITH ERCOT 8-11 8-9 REFERENCE: PROTOCOLS SECTION 8.8.2.1, TSP INFORMATION TO BE PROVIDED TO ERCOT 8-11 8-9 REFERENCE: PROTOCOLS SECTION 8.8.2.3, CHANGES TO WORK APPROVED BY ERCOT. 8-13 8-11

ERCOT OPERATING GUIDE – JUNE 1, 2006 2


8 Operational Metering Telemetry and Communication8.1 Operational Telemetry

(1) Metering QSE control centers required to supply real-time operational meteringmeteringtelemetry data to ERCOT

shall use an Inter-Control Area Communications Protocol (ICCP) interface through the ERCOT WAN. QSEs shall also and receive signals from ERCOT over the ICCP interface to implement frequency control. The QSE’s interface to ERCOT for this purpose is implemented through a QSE-supplied RTU or other device using DNP 3.0 protocol at the QSE control center.

(2) TDSPTSPs control centers required to supplying real-time operational meteringmeteringtelemetry data to ERCOT shall use an ICCP interface through the ERCOT WAN. TDSPs may use an RTU interface similar to QSE’s only with approval from ERCOT.

(3) Each QSE and/or TDSPTSP shall continuously provide to ERCOT the telemetry data quantities that they are responsible for providing to ERCOT. The frequency of update, means of communication to ERCOT, and format for each point provided by each Entity shall follow the specifications in also be as specified in Attachment 8AAttachment 9?, ERCOT Data Sets for that entity, unless otherwise approved specifiby ERCOT. At the frequency specified in the TablesAttachment 9?, each update cycle shall provide new readings of all data points being monitored, not averages linked to prior cycle readings or repetition of readings from a previous cycle. Design accuracy and availability of data points delivered to ERCOT, when compared with actual quantity measured at the source, shall satisfy the requirements and standards for tTelemetry pPerformace and Stat Estimator pPerformance as specifed under Section 8.1.6, ata from QSEs and /TDSTSPs to ERCOT.” of these guides.

(4) be no greater than 4The TSP shall maitinto any telemetered of the largest line rating at each busERCOT will identify the top 10% of MW/MVAR telemetry pairs and voltage points that are “essential”to reliability, system observability, support of State Estimator performance, or commercial Market concern which must meet the more stringent availability requirements defined below.

l provide data to ERCthang availability:99% of all data points will have an availability of at least 80% on a monthly basis

will be meas based on end-to-end connectivity of the communications path and teExceptions to the above may be made with agreement with ERCOT for data points not significant in the solution of the State Estimator or required for the reliable operation on the ERCOT Transmission System.

Reference: Protocols Section 12.4.4.1.1 QSE, Resource and TDSP Responsibilities QSEs, Resources and TDSPTSPs are required to provide power operation data to ERCOT including,

but not limited to:

(a) Real time generation data from QSEs;

(b) Planned Outage information from Resources;


ERCOT, 01/24/07,

Not defined or acronym

ERCOT, 01/24/07,

Check Section Reference

ERCOT, 01/24/07,

Spell Out?


(c) Transmission system nNetwork data used by any TDSPTSP’s control center, including:

(i) Breaker and line switch status of all ERCOT Transmission Grid devicesElements;

(ii) Line flow MW and MVAR;

(iii) Breaker, switches connected to all Resources;

(iv) Transmission Facility Voltages; and

(v) Transformer MW, MVAR and TAP.

(d) Real time generation and Load acting as a Resource telemetry meter data from QSEs;

(e) Real time Generation meter splitting telemetry datasignal from QSEs;

(f) Planned Transmission Outage information from TDSPTSPs;

(g) Transmission system nNetwork model transmission data including (model and constraints) from TDSPTSPs;

(h) Current Operating Resource Plans from QSEs; and

(i) Dynamic Schedules from QSEs.

;

(5) Real- Time telemetry data will be provided to ERCOT shall be at the same scan rate that as the TDSPTSP or QSE control computers and obtains the data collection system obtains the data from telemetry.



8.1.1 ERCOT Interface RTUs

ERCOT interface RTUs pass communications between the Market Participant responsible for supplying Operational MeteringMetering data and ERCOT. Suppliers of data must install and configure these RTUs according to ERCOT procedures. The RTU or other device shall reflect the data quality codes (ie. suspect, failed, manual, etc) of the individual data points found in the Market Participant’s control computers and data collection systems.

In order to ensure that real-time data can be exchanged in a timely manner, the connection concept has been extended to support the use of specified communications protocols. Specifically, the 2-second data sent to ERCOT, and the 4-second data received from ERCOT required for frequency control will be exchanged via DNP 3.0 communications protocol. The connection is designed around the following requirements:

The connection paths begin with the Market Participant’s RTU or SCADA system. Three serial ports provide for the redundant paths, two to the Point-to-Point network and one to the Frame Relay network. The path to the Point-to-Point network is passed through a modem, and the modulated signal connects to the Market Participant’s Channel Bank. Voice circuits to be placed on the Point-to-Point network are combined with the data circuit on a Fractional T1 connected between the Channel Bank and the Point-to-Point network CSU/DSU. RTU data sent over the Point-to-Point network will employ DNP 3.0.

The path to the Frame Relay network is accomplished by connecting the RTU/SCADA to a data Gateway via a serial interface. The Gateway communicates with the RTU/SCADA using DNP 3.0 only. The Gateway then exchanges the data with a compatible Data Server at ERCOT. The protocol used for this data exchange is TCP/IP.

This connection design supports redundancy for both data exchange and voice circuits between the Market Participant and ERCOT. Data exchange redundancy is provided as described here. The Public Switched Telephone Network (PSTN) provides backup for voice circuits.

8.1.21 ERCOT ICCP Interface

The Iter-Control Area Communications Protocol (ICCP) over the ERCOT WAN Ethernet provides the real-time Operational MeteringMeteringtTelemetry data from Market Participant computers, computer networks, or other devices. Market Participants providing the to the ERCOT WAN. Suppliers of data using an ICCP link must format their data and coordinate installation according to ERCOT procedures (ERCOT WAN Agreement). The telemetry data furnished by a Market Participant’s ICCP link shall reflect the data quality codes (ie, suspect, failed, manual, com_failed etc) of the individual data points as coordinated with ERCOT found in the Market Participant’s control computers and data collection system. Market Participant’s shall provide documentation to ERCOT upon ERCOT’s request describing their control native system quality codes and the mapping defining the conversion of their RTU quality codeso the ERCOT defined quality codes.


ERCOT, 01/24/07,

Parenthese use - location of agreement on the ERCOT MIS?


8.1.1.1 Quality Codes

Status and analogstelemeteedydata provided toERCOT shall have willed with the associated quality codes:

(1) “ alid” – represents analog or status data that the TSPmarket participant considers valid;.

(2) “ anual” – represents analog or status data that is manually entered manually ainket participant control system (not received from the field electronically);.

(3) “ uspect” - rRepresentsanalog or status data that the market participant in which thSP sure alidity;.

(4) “ nvalid” – rRepresentsanalog or status data that which the mparticipant considers to be has identified asity limits; and.

(5) “ om_fail” – represents informs ERstatus data that the market participant considers to be not current due to communications failureprovided ERCOT is not current.

8.1.1.2 Availability Rf ICCP Links

(1) ICCP links must achieve a monthly availability of -eightercent, excproved Pplanned Ooutages. Avaiability wll be measured based on end-to-end connectivity of the communications path and the passing of Real-Time data. A link will be considered as available when at least eighty-five (85%) percent efined on that lnkessfully transferred to ERCOT with a “Valid” or “Manual” quality code. This will include establishing a process to coordinate downtime for ICCP links and database maintenance.

(2) ICCP links shall use fully redundant data communication between the QSE and TSPlinks between itsol center systems anthe Ssystems such ty single element of the communcationsystem can fail and:

(a) For server failures, complete real-time data transfer must be re-established within five minutes by automatic failover to alternate server(s); and

(b) For all other failures, complete real-time data transfer must continue to flow between the TSP’s, QSE’s, and ERCOT’s control systemscenters withs of all data continuing at a 30 second or less scan rate.



8.1.32 Validation of Real Time Signals Telemetry Data with Settlement Metering for Resources

(1) Real-Time telemetry data The integrated real time MW signal obtained from a resources shall be validated.

Signals from resources used to supply power or Aancillary Sservices shall be integrated by ERCOT and checked against settlement meter values on a monthly basis.

(2) Where multiple generators share a single net settlement meter, the ratio of integrated Rreal- time datasignals from each generator shall be used to proportion the total settlement total quantity.

8.1.43 Data from ERCOT to QSE’s

ERCOT shall provide operational data and issue instructions and information to QSE’s in accordance with the Operating Guide and the Protocols. Attachment 8A in this guide provides the instructional and informational data sets that ERCOT will send to the QSEs. to satisfy the requirements in the Operating Guides and the Protocols.

8.1.54 Data fFrom ERCOT to TDSPTSP

(1) ERCOT shall will provide operational data and issue instructions to the TDSPTSP in accordance with the Operating Guide and the Protocols.

Reference: Protocol Section 12.4.4.1.2, ERCOT Responsibilitie (2) s ERCOT is required to provide the following power operation data to TDSPTSPs for the purpose of

providing reliability information as determined by ERCOT:, in accordance with confidentiality as defined in Section 1.3, Confidentiality of these COProtocols:

(a) Relevant information for the purpose of providing reliability as determined by ERCOT, including but not limited to:

Status of any breakers and switches in ERCOT's Real- Time data base;

(b) State Eestimator solutions;

(c) Transmission line flows and voltages;

(d) Transformer information;

(e) QSE Resource data; and

(f) Voltage schedules at major transmission busses.;

(3) ERCOT will give notice to the Entities supplying the above list of data to ERCOT upon the initial provision of such data to the TDSPTSP.


ERCOT, 01/24/07,

Attachment Section 9 - reference


8.1.65 Data from QSEs and /TDSPTSPs to ERCOT

QSEs and TDSPTSPs shall provide Real- Time monitoring of power system quantities to ERCOT as defined in the Operating Guides and Protocols. Attachment 8A of this guide,Operating Guide specifies gives the format and description parameters for the content of each type of data point that ERCOT may request from TDSPTSPs and QSEs to satisfy the requirements in the Operating Guides and the Protocols. Not all data points in Attachment 8A are necessarily required from each Entity. ERCOT shallwill inform TDSPTSPs and QSEs if additions to presently furnished data are required. All involved entities shallparties will seek to jointly resolve a means and schedule for providing data to ERCOT, including changes to existing data. ERCOT shallwill consider alternatives and exceptions, on a case-by-case basis, to the extent that ERCOT determines that the does not believe its operational and reliability needs of the ERCOT system are not compromised. Ultimately, it is the responsibility of the TDSPTSPs and QSEs to provide all data requested by ERCOT as set forth in the ERCOT Protocols and Operating Guides.

8.1.5.1 Weather Zone Data

(1) A SPTP that is responsible for providing Weather Zone tie-line measurement data to ERCOT is , they areo establish a backup to the primary source. using the method one option

(2) SPTPs having an EMS with a native ICCP application capable of four4 seond periodic data set transfers with minimum 300 points per data set, and hot standby backup ICCP servers with automatic fail-over capability, shall provide an additional ICCP association across the ERCOT WAN for the transfer of Weather Zone tie line measurements. ICCP nodes should exist at primary and backup facilities.


ERCOT, 01/24/07,

Spell out - not an acronym


SPnot hanclude the EMS data quality codes. RTUs should exist at primary and backup facilities.2 State EstimatorTeleme Measurements Data

ERCOT uses a state estimator to produce load flow base cases which are used to analyze the reliability of the transmission grid. The state estimator is dependent on accurate MW, MVAR, and voltage telemetry in determining the current transmission conditions.Acquisition of good telemetry status and analog measurements data (Telemetry) for the transmission power system (System) together with an accurate model of the System are processed by a state estimator to provide an optimal estimate of the System state at a given point in time while filtering measurement noise (error) and detecting gross errors. The quality and availability of Telemetry provided to ERCOT are important to the performance of ERCOT’s State Estimator.

Beyond general Telemetry performance criterion there are more stringent criterion needed at locations where state estimates are “critically important” (e.g., locations where reliability, security, and Market impact are of more focused concern).

5

(1) ERCOT is required to monitor transmission assets operated at 60 kV or above and direct its operation within safe facility limits to preventfrom da This may requireTo do this, Etorequest that addital MW, MVAR, and voltage telemetry be installed, while attempting to minimize adding telemetry equipment to as few locations as practicable.

(2) ERCOT may also request additional telemetry when it determines that network observability or the measurement redundancy are not adequate to produce acceptable Sstte Eestmator results per the established State Estimator TAC dards approved by the Technical Advisory Committee (TAC).

(3) Prior to making a request for additional telemetry, ERCOT will provide evidence supporting a congestion or reliability problem requiring additional observability and specify what depected improvements in system observibility are needed. If the request is for telemetry additions at more than one location, ERCOT shallwill prioritize the requested additions.

(4) Upon receipt of a ERCOT request for additional telemetry, the TDSPTSP or QSE shall willacknowledgement receipt of the request and shall have sixty (60 ) days to either:

(1a) Accept ERCOT’s request for additional telemetry, andprovide the telemetry within 18 months, and notify ERCOT of the provide a schedule for its implementation schedule;

(b2) Provide an alternative solutionproposal to ERCOT, for implementation within the next 18 months, which meets the requirements described by ERCOT;

(c3) Propose a normal topology change (change normal status of switch(es)) in the area which would eliminate the security violations which are ERCOT’s concern. (i.e. eliminates the possibility of flow through a networked Transmission Eelement thus


ERCOT, 01/24/07,

Where do these standards reside? ERCOT MIS?


changingand turns the security problem into a planning problem which is un-affected by unitgeneration dispatch);

(d) Indicate that the requested telemetry point is at a location where the TPTS or QSE does not have the authority to install the requested telemetry. For points on privately owned facilities connected to the ERCOT Transmission Grid, an attempt will be made to facilitate ERCOT's telemetry request; or

(e) File a request with the Public Utility Commission of Texas (PUCT) requesting expedited action for an Order directing that the responsibility for operational monitoring and reliability af this specific element or elements of the transmission system be withdrawn from ERCOT and assigned to the requesting TPTS. ERCOT will then immediately remove the elements from its Real- Time Congestion Maagement system as monitored elements pending the PUCT decision.

(5) If ERCOT rejects the alternate solution provided by the TSP or QSE then that entity may appeal the original request to TAC within 30 days. If, after receiving an appeal, TAC does not resolve the appeal within 65 days, the TSP or QSE may present its appeal to the ERCOT Board.

(6) ERCOT shall contract the TSP or QSE for verification of receipt of a ERCOT request for additional telemetry if ERCOT has not received acknowledgement from the TSP or QSAE that a request has been received by within thi days of is sending., E QSE for verification of rece

(7) Nothing in this section shall limit the SPTP’s or QSE’s appeal process outlined in Protocol Section 3.10.7.4, Telemetry Criteria.

8.1.65.2.1 General Telemetry Performance Criterion

The following criterion will apply in general to Real-Time telemetry provided to ERCOT:

(1) be greater than 4% of full scale.(2) The TSP shall maintain the sum of flows into any telemetered bus less than the greater of 5 MW or 5% of the largest line rating at each bus.

(2) Each QSE or TPTS shall provide telemetry data to ERCOT such thatllowing availNinety-eight (98%) percent of all telemetry provided to ERCOT must achieves a montquarterly availability of at least eighty (80%) percent., exc Availability will be measured based on end-to-end connectivity of the comunications path and the passing of Real-Time data with good quality codes at the scheduled periodicity.

(b) ICCP links must achieve a monthly availability of ninety-eight (98%) percent of the time, excluding approved planned outages. Availability will be measured based on end-to-end connectivity of the communications path and the passing of Real-Time data. A link will be considered as available when at least eighty-five (85%) percent of the data defined on that link is successfully transferred to ERCOT with a quality code. This will include establishing a process to coordinate downtime for ICCP links and database maintenance.

3 TDSSP’s shll make reasonable efforts to obtain telemetry this from retail Ccustomers asociated with new Ccustomer-ownd substations to meet this standard or obtain agreement from ERCOT that these retail Ccustomers hav entered into arrangements with ERCOT to provide this data to


ERCOT, 01/24/07,

Not an acronym - spell out

ERCOT, 01/24/07,

parentheses use is incorrect/confusing


ERCOT. If the data cannot be obtained under either of these methoids ERCOT shall report such case to the PUCT Wholesale Electric Market Monitor.

(4) Tsubstations to provide this data and meet this standard obtain into agreements with ERCOT to provide this data.(5)Exceptiogtpc shall not significant toin the solution of the State Estimator or required for the reliable operation onf the ERCOT Transmission System. Some examples of these are:

(a) Substation with no more than two transmission lines and less than 10 MW of load;

(b) Connection of Loads along a continuous, non-branching circuit that may be combined for telemetry purposes;

(c) Substations connected radially to the bulk transmission system.

8.1.5.2.2 Critically Important Telemetry Performance Criterion

(1) ERCOT shall create a list of those MW/MVAR tTelemetry pairs, nt exceedin 10% of the lines Transmission Elements in ERCOT, and up to twenty (20) voltage points thaidentified as “critically important” to reliability, system observability, support of State Estimator performance, or are of a commercial Market concern. TheseThis list of itically important telemetry must meet more stringent criterion for accuracy and availability where specifically addressed. ERCOT willshall review and publish thist annually. ERCOT willshall use the following criterio identify critically important tTelemetry:

(a) Loss of a telemetry point that results in the inability of ERCOT to monitor loading on a transmission line operated at 345 kV or above.

(b) Loss of a telemetry point that results in the inability of ERCOT to monitor loading on a 345/138 kV autotransformer.

(c) Loss of a telemetry point that results in the inability of ERCOT to monitor loading on transmission facilities designated as critically important to transmission reliability by ERCOT. A list of these critical facilities will be published annually.

(d) Telemetry necessary to monitor transmission elements identified as causing 80% of congestion cost in the year for which the most recent data is available..

(e) Telemetry necessary to monitor the t0) most votage critical buses designated by ERCOT and approved by TAC each October.

(2) itically important Telemetry provided toCrit Each QSE or TDSPTSP shall provide identified critical telemetry data to ERCOT such that meets the

following availability:Nrast (980%) percent of h dingneges. Avalabil-end connectivity of the communicationsd the

passing of Real-Time data with Vvalid or Mmanual good uality codes at the schedlty. A link ll be onsiderablishing process to coordinate downtime for ICCP links, critically iortant RTU’s and database maintenance.


ERCOT, 01/24/07,

not a defined term


8.1.5.23 State Estimator Data

The ERCOT State Estimator produces load flow base cases which are used to analyze the reliability of the transmission grid. The state estimator is dependent on aAccurate and redundant MW, MVAR, and voltage telemetry in determiningtelemetry and an accurate transmission power system model the current transmission conditionsare required by sState eEstimator in orderto prodce an optimal estimation of the transmission power system state. The sState eEstimator results are used in contingency analysis, and also in transmission congestion management., and other network analysis real-time sequence functions.

8.1.5.3.1 Telemetry Status and Analog Measurements Data

(1) The quality and availability of telemetry provided to ERCOT are important to the performance of the ERCOT State Estimator. Acquisition of good telemetry status and analog measurements data (Telemetry) for the transmission power system (System) together with an accurate model of the System are processed by a state estimator to provide an optimal estimate of the System state at a given point in time while filtering measurement noise (error) and detecting gross errors.

telemetry provided to ERCOT are mT State Estimator. (2) Telemetry is not needed at every bus of the System network model to arrive at a good estimate

of the System’s state. There are general telemetry performance criterion, such that sufficient numbers and placement of measurements and accuracy of measurements thatavailable to achieve System observability and an overall good State Estimator performance.

(3) Beyond general telemetry performance criterion there are more stringent criterion needed at locations where state estimates are “critically important” due to reliability, security, and Market impact are of more focused con

8.1.65.3.2 State Estimator Performance RequirmentsRequirements

(1) The ERCOT e Estimator performance shall converges for 97%of run during a one wemonthly est period.

(2) (bje EpfTElshaelementemergency rating on at least 95% of samples measured in a one month trialow. (3) tTansmission eElements identified as causing 80% of congestion cost in the latest year for

which data is available, the difference between the MW telemetry value and the MW State Estimator vale shall be less than 3% of the associated element emergency rating on at least 95% of samples measured in a one month trial.

(4) ERCOT will confirm that the MW base case element flows used in contingency analmato line flows used in creaObjective met if difference of all identified elements < 3% of equipment over 95% of samples measured during a 1 month trial. To be measured on all State estimator samples of each month and posted.


ERCOT, 01/24/07,

Definition of critically important if going to put in quotes

ERCOT, 01/24/07,

parenthese use in this section is odd


each October; Telemeter bus voltage minus state estimator voltage within 2% orObjective met if difference of all identified voltages < equipment accuracy or 2% of nominal voltage over 95% of samples measured during a 1 month trial. To be measured on all State estimator samples of each month and posted.On the twenty (20) most voltage critical buses designated by ERCOT and approved by TAC each October,; tThe difference between the telemetered bus voltage and the minus sState eEstimator voltage shall be within the greater of 2% or the accuracy of the telemetered voltage measurement involved for at least 95% of samples measured during a one1 month trial.

(5) On all Transmission Eeements greater than 100kV, ; e difference between sSate eEsimator MW solution and the SCADA measurement will be less than 10 MW or 10% of the associated emergency rating (whichever is greater) on 99.5% of all elements during a 30 day period. All equipment failing this test will be reported to the associated TSP providing the measurement data for investigation and correction repaithi0 days of detection.

On all transmission elements > 100KV; the difference between state estimator MW solution and the scada measurement will be less than 10 MW or 10% of the associated emergency rating (whichever is greater) on 99.5% of all equipment. All equipment failing this test will be reported to the associated TSP for repair within 10 days of detection.

(6) To meet these State Estimator objectives ERCOT shallwill:

(a) Work with TSP’s to resolveidentified problems in accordance with ERCOT these Opg Guides prior to requesting directing adquipment;.

(b) In event of failure to meet the standard in 8.1.6.3.2 2 and ERCOT may requestdirect additionemetry be installed on llements contributing most to 80% of congestion costs for the latest year for which data is available, to l protocols. 65.5.2 (7)). If the TSP disputes the ERCOT request for additional telemetry, the TSP shall have the appeals process available under Operating Guide Section 8.1.56.2, ERCOT Requests for Telemetry;.

(c) Enforce the requirements of Protocol 3.10.7.4.2 (5), Continuous Telemetry of the Real-Time Measurements of Bus Load, Voltages, Tap Position, and Flows, by alarming any sum of flow around a bus the greater of 5% of the largest line rating connected to the bus or 5MW, and requesting that the applicable TSP or QSE correct the failure;.

(d) Post monthly results for compliance with Section 8.1.6.3.2 items 1 through 5 above; and.

(e5) ERCOT shall consider the quality codes sent by the data provider in assigning confidence factors for the data to be used in the State Estimator. Valid and Manual quality codes shall be considered as good quality. Quality codes sent as not good quality shall be considered at a lower confidence. The confidence shall continue to decrease over time.


ERCOT, 01/24/07,

check Section Reference

ERCOT, 01/24/07,

check Section Reference


8.1.76 TDSPTSP and /QSE Metering Telemetry Restoration

Real-time Operational Meter telemetryedata shall be provided continuously. Data that is inaccurate or of bad qualityLost data or signals, whether failed or in error, must be restored promptly by the provider of the telemeterye Operational Metering data. It is recognized that some data may be of more importance critical than other data. ERCOT will inform the TDSPTSP or QSE of if a data in this category that item is critical and needs to be repaired to service as quickly as possible. QSE’s and DSPTSP’s shall provide information to ERCOT of any and all corrective actions taken to restore reported telemetry errors repair procedures and records shall be made available to ERCOT upon request. When ERCOT notifies a data provider of a data element which is providing telemetry data inconsistent with surrounding measurements, the provider shall, within 2b3 days, take corrective action to either

(a) Calibrate/repair the mis-behaving equipment;

(b) Request an outage to schedule calibration/repair of the mis-behaving equipment;

(c) Provide ERCOT with a plan to re-calibrate or repair the equipment in a reasonable time frame; or

(d) Provide ERCOT with engineering analysis proving the data element is providing accuracy within its specifications.

Before ERCOT requests review/re-calibration of a telemetry problem with a piece of equipment it shall discuss the problem with the provider to attempt to arrive at a consensus decision for the most appropriate action.

8.1.87 QSE and TDSPTSP Data Acquisition

Suppliers of Real-Ttme Operational MeteringMeteringtelemetry must collect and process telemetry data from field equipmentdata at their control centers before passing to the ERCOT interface. The equipment and processes are owned and operated entirely by the supplier. Traditionally, utilities have used both analog and digital methods of transmission at existing facilities. It is the responsibility of the QSEs and TDSPTSPs who supply other Eentities’ data to ERCOT to also arrange for reliable delivery of telemetry data from the field dataequipment from the other entities in order to support the requirements in theise Operating Guides.



8.2 Calibration and Testing

8.2.1 Responsibility

It is the responsibility of the owner of telemetry equipment to insure that calibration, testing and other routine maintenance of equipment is done on a timely basis, and that accuracy meets or exceeds that which is specified in this these Operating GuidesAppendix, for both the overall system and for individual equipment where detailed herein. Coordination of Ooutages required for these activities with ERCOT is also the responsibility of the owner. Upon ERCOT’s request, eEach SP and QSE shall upon Rest furnisde ERCOT access to its preventive maintenance and calibration test procedures and records for purposes of assureing accurate telemetry of data. If a TSP and/or QSE epeatedly fails other telemetry metrics defined in these Operating Ggides, ERCOT may require the owner to revise its procedures to ensure accuracy and availability of telemetry dataa revision of this plan.

8.2.2 Notification

ERCOT and all affected parties shall be notified at least 72 hours in advance, or at a mutually acceptable advance notice, prior to any calibrations or planned maintenance. In Eemergency conditionsConditions, the owner of the operational meteringmeteringtelemetry and associated equipment may make necessary repairs with notification to affected parties within 24 hours. ERCOT or other parties sharing data from the equipment may request copies of the repair and calibration records.

8.2.3 Test Equipment

Test equipment and test standards intended to be used for the calibration of operational meteringmeteringtelemetry and associated equipment shall have an be certified to values of accuracy and precision that are equal to or better than the accuracy of the equipment under test.

8.2.4 Disputes

Where a dispute over the accuracy or performance of any operational meteringmeteringtelemetry equipment exists, ERCOT may request a comparison of standards and/or a joint calibration of affected equipment.



8.2.5 Calibration Testing

All operational meteringmeteringtelemetry and associated equipment for analog data quantities (MW, MVAR, Volts, LTC tap positions, etc.) shall be tested as needed to ensure accuracy and performance. Entities providing Operational MeteringMeteringtelemetry data to ERCOT shall make their test records, procedures and maintenance criteria available to ERCOT upon request.

8.2.6 Exchange of Information

REFERENCE: Protocols Section 8.8.1, Coordination with ERCOT

Before energizing and placing into service any new or relocated facility connected to the ERCOT Transmission Grid, a TSP, QSE, or Resource Entity shall enter appropriate information in the Outage Scheduler and coordinate with ERCOT, and receive written notice of approval from, ERCOT, as specified in Protocol Section 3.3.1, ERCOT Approval of New or Relocated Facilities.

Prior to energizing and placing into service any new or relocated Facility connected to the ERCOT Transmission Grid, TSPs shall coordinate with and receive approval from ERCOT.

8.2.7 Documentation

(1) Reference: Protocols Section 8.8.2.1, TSP Information to be provided to ERCOT Information on existing and future ERCOT System components and topology is necessary for

ERCOT to create databases and perform tests. To ensure that such information is made available to ERCOT, each TSP, or its designated agent, shall provide accurate information for all ERCOT Transmission Facilities owned or planned by the TSP. The information provided shall include, but not be limited to, the following:

(a).Information necessary to represent the TSP’s Transmission Facilities in any model of the ERCOT Transmission Grid whose creation has been approved by ERCOT, including modeling information detailed in procedures of ERCOT and the Network Data Support Working Group (NDSWG); a

(b)2. Identification of a designated TSP contact person thate ERCOT can contact regarding questions ERCOT may have on the information provided;.

(c).Consistent data with existing ERCOT Transmission Facilities owned or operated by the TSP represented in the appropriate pPlnning mModl. At a minimum, the impedance data (resistance, reactance, and charging), Continuous Rating, and Emergency Rating shall exactly match corresponding data represented in the pPlaning mModel TSPs shall provide reasons for any data that does not exactly match.


ERCOT, 01/24/07,

parenthese use


(2) The energization or removal of equipment in the Network Operations Model shall be done in accordance with Protocol Section 3.3.2.1, Information to Be Provided to ERCOT.(a) Proposed energize date;

(c) TSP(s) responsible for rating affected transmission element(s); (e) Identification of existing Transmission Facilities involved and new Transmission Facilities (if

any) being added or existing Transmission Facilities being permanently removed from service; (g) Outages required (clearly identify each Outage if multiple Outages are required), including

sequence of Outage and estimate of Outage duration; (i) Supervisory Control and Data Acquisition modification work, including descriptions of the

telemetry points or changes to existing telemetry, providing information on equipment being installed, changed, or monitored;

(k) Statement of completion, including: (ii) Statement to be made at completion of total project. (i) Existing status; (iii) Proposed final configuration.



(3) TSPs The TSP shall notify ERCOT at least thirty (30) days before starting to energize or place into service any new or relocated Facility. The Notice shall be submitted in accordance with formats and procedures adopted by ERCOT and TSPs. For Notices involving co-owned, co-operated, or co-rated Transmission Facilities, the TSP submitting the initial Notice shall communicate with the other Market Participants responsible for co-owning, co-operating, or co-rating said Transmission Facilities prior to the Notice submittal. The Notice shall include the following information:

(1) Proposed energize date;

(2) TSP performing work;

(3) TSP(s) responsible for rating affected transmission element(s);

(4) Location Code if applicable (e.g. station code);

(5) Identification of existing Transmission Facilities involved and new Transmission Facilities (if any) being added or existing Transmission Facilities being permanently removed from ser-vice;

(6) Ratings of existing Transmission Facilities involved and new Transmission Facilities (if any) being added;

(7) Outages required (clearly identify each Outage if multiple Outages are required), including sequence of Outage and estimate of Outage duration;

(8) General statement of work to be completed with intermediate progress dates and events iden-tified;

(9) Supervisory Control and Data Acquisition modification work including descriptions of any new data telemetry points or changes to existing telemetry;

(10) Additional data determined by ERCOT and TSP(s) as needed to complete the ERCOT model representation of existing Transmission Facilities involved and new Transmission Facilities (if any) being added;

(11) Statement of completion, including:

(a) Statement to be made at the completion of each intermediate stage of project; and

(b) Statement to be made at completion of total project.

(12) Drawings to be attached, including:

(a) Existing status;

(b) For each intermediate stage; and

(c) Proposed completion of job.



The parties involved shall furnish pertinent information to ERCOT on request, including the follow-ing:

(a) Connection diagrams;

(b) Metering one line diagram;

(c) Substation one line diagram;

(d) Panel schematics and one line diagrams;

(e) Instrument transformer (CT and PT) data (ratios, test reports, nameplate);

(f) Transducer conversion constants;

(g) Meter constants;

(h) RTU and digital device configuration details

Certified calibration test reports of any device used for operational meteringtelemetry; and

(i) Other data as may be requested.

8.2.8 Operator One-line Displays

Market Participants Operations staff at each entity providing Operational MeteringMeteringTelemetry data to ERCOT shall have one-line diagrams displayable on their Energy Management System or other computer systems for viewing by its operations staff. Displays shall be provided for all substations or power plant switchyards that include data passed to the ERCOT interface.

8.2.9 Notification of Changes

REFERENCE : Protocols Section 8.8.2.3(11) rk Opemetry , Changes to Work Approved by ERCOT.

(1) ERCOT shall review the information and notify the requestor of any required modifications in ccordance with Protocol Section 3.10 (11), Network Operations Modeling and Telemetry. ERCOT may, at its discretion, require changes or more details regarding the work plan for the The TSP shall notify ERCOT and any other affected TSPs as soon as practicable of any requested changes to the work plan. ERCOT shall review and approve or reject changes to the work in accordance with Section 8.8, Coordination for System Topology Modifications.

(2) ERCOT and any other affected parties shall be informed of changes to operational meteringmeteringtelemetry and associated equipment 30 days prior to placing in serviceper Protocol Section 3.10.1, Time Line for Network Operations Model Change Requests. All parties must be notified so a mutually agreeable time can be set for the changes. All parties involved must be satisfied prior to the making of any changes.





8.3 Communications

The following sections describe the communications There are two types of data communication that will be implemented in the ERCOT System: Real-Time Communications (Operational), and Commercial Market Communications (Settlement). This Operating Guide defines the path standards of the wide area network (WAN) utilized for Rreal-Ttime data communications (Operational) and voice communications (Operational) that shall be used to exchange security and reliability information between:

(a) ERCOT and a QSE;, and

(b) ERCOT and a TDSPTSP.

As Operational signals may originate with or be destined for organizations connected to a QSE or TDSP, path standards are also defined for real-time data communications (Operational) and voice communications (Operational) required by QSEs and TDSPs that impact or contribute to security and reliability information required by ERCOT.

Commercial Market Communications (Settlement) are not defined in this Operating Guide, other than facilities needed to provide common communications. Operational Communication requirements take precedence over Commercial Market Communication requirements.

8.3.1 ERCOT WAN

ERCOT shall provide for a wide area network (ERCOT WAN) for secure communications path between ERCOT and the Market Participants iIn order to facilitate wholesale operations and frequency control as a single control area. , ERCOT provides a wide area network (the ERCOT WAN). This communications network uses redundant, digital communications between ERCOT control centers and one or more facilities at each QSE and TDSPTSP. The ERCOT WAN shall havehas sufficient bandwidth capacity and speed to enable:

(1) Real- time (operational meteringtelemetry) data exchange for frequency control and transmission security;

(2) Operational voice communications for both normal and emergency use. The ERCOT WAN supports both off-premise exchanges (OPX) with ERCOT’s control facilities and the ERCOT hotlines; and

. (3) Data exchange to support applications programming interface (API) routines. These include

power scheduling, operating plans, outage requests, dispatch instructions, posting of information and other applications.


ERCOT, 01/24/07,

parentheses use

ERCOT, 01/24/07,

parentheses use


8.3.1.1 QSE Use of Domain Name Service (DNS) or ERCOT Web-Based Front Page for Site Failover

A QSE possessing backup sites must utilize one of the following two options:

(a) A AN (Wide Area Network) Domain Name Service (DNS) server; or

(b) An nCOT provided web-based DNS service to facilitate the failover process when moving its operations between primary and backup sites.

The requirements of these options are specified below.

8.3.1.1.1 DNS Server Configuration for Failover Support

(1) A QSE is required to provide and maintain its own DNS servers that must be accessible by the ERCOT WAN. The failover process requires the following:

(a) DNS servers must support zone transfers over TCP port 53;.

(b) Firewalls must allow zone transfers to ERCOT DNS servers;.



(c) Zone files for the QSE's domains, (.g. ww w. examplepower.com , ) ut reside on its WAN accessible DNS servers;.

(d) DNS servers must be set up as the master for its zone;.

(e) DNS servers must allow ERCOT DNS servers to transfer the zone files (ERCOT will be set up as a secondary/slave server for the zone);.

(f) The zone files must contain names for all local servers the QSE will need ERCOT services to access. At a minimum, it must contain entries for the servers that can be switched over to the backup site. The zone file must also contain entries for the QSE's primary website address, .g. www.examplepower.com, ) a other common internet accessible sites that ERCOT servers may have occasional need to access; and.

(g) Time to Live (TTL) values for backup host entries in the zone file must be set to 0 in order to prevent the host to IP address mappings from being cached on the client machines. This allows any changes made to a zone file to take effect immediately upon a zone transfer.

(2) Once its DNS servers are operational, the QSE shall timely contact its ERCOT Client Ser-vices Representative and request that an ERCOT network administrator work with the QSE to test the functionality of the DNS setup. The QSE must contact the ERCOT Client Ser-vices Representative at least five Business Days before testing.

(3) After the zone transfer testing is complete, the QSE shall supply its ERCOT Client Services Representative with a list of participant servers, their DNS names, and their roles on the net-work. The ERCOT Client Services Representative will then contact the application owners at ERCOT to change application communications to use the DNS name instead of IP ad-dresses.

(4) After successful completion of the test, when a QSE backup site failover is desired, the QSE shall update the zone file with its disaster recovery IP addresses and publish it to the ER-COT DNS servers. The change will be effective immediately. The QSE shall also imple-ment a DNS server at its backup site. This allows updated zone files to be published regard-less if the primary site is up or not.

8.3.1.1.2 Web-Based DNS Access

(1) This access is provided as an alternative method for any QSE that does not wish to maintain its own DNS servers. Access is provided over the ERCOT WAN only. The QSE is responsi-ble for access through its networks to the web servers located on the ERCOT WAN. The QSE shall adhere to ERCOT password requirements.

(2) To failover to or from a backup site, the QSE shall update the IP address of the existing entry. ERCOT servers will accept the change and start using the new IP immediately.

(3) Once the QSE has connectivity to the web server over the ERCOT WAN, it shall contact its ERCOT Client Services Representative and request that an ERCOT network administrator work with the QSE to test the functionality of the DNS setup. The QSE shall contact the ER-COT Client Services Representative at least five Business Days before testing. After testing


ERCOT, 01/24/07,

parentheses use

http://www.examplepower.com/

http://www.examplepower.com/


is completed, the Client Services Representative will contact the application owners at ER-COT to change application communications to use DNS names instead of IP addresses.

(4) After successful completion of the test, when a QSE site failover is desired, the QSE shall change the Web page entries with the active site information and the change will be effective immediately.

8.3.2 ERCOT Responsibilities

ERCOT supplies interface requirements, equipment, installation and 24-hour maintenance for the entire ERCOT WAN, including equipment at each QSE and TDSPTSP control facility, as well as ERCOT’s control centers. ERCOT’s responsibilities include:

(a) Supply and install fully configured and tested Customer Premises Equipment including routers, CSU/DSUs, LAN switch/hub and all support equipment for management purposesl.

(b) Order and provision of local loop, network access point and transport;.

(c) Design, configure, test, and install network monitoring and management service;.

(d) Provide 24-hour network monitoring and management;.

(e) Provide 24X7 maintenance, with 4-hour response, for all ERCOT equipment located at participant site; and.

(f) ERCOT will be the single point of contact for all network issues.

8.3.3 QSE and TDSPTSP Responsibilities

(1) TDSPTSPs and QSEs whose facilities connect to the ERCOT WAN are required to sign an agreement with ERCOT governing installation, operation and maintenance. Users of the ERCOT WAN shall provide signal connections, uninterruptible power, and physical space for ERCOT-supplied WAN interface equipment at their control centers, as well as 24-hour access for ERCOT installation and maintenance personnel.

(2) At these facilities, computer and communications equipment connected to ERCOT WAN interfaces is the complete responsibility of the QSE or TDSPTSP. Facilities shall have uninterruptible power supplies (UPS) capable of independently supplying all equipment connected to the ERCOT WAN for at least 72 hours.

(3) Any TDSPTSP or QSE facility, whether primary or backup, involved in the transfer of the data sets identified in Attachment 8A, will be required to connect directly to the ERCOT WAN



Frame RelayPrimary Private Network and Point-to-Point paths. If a TDSPTSP and QSE utilize the same EMS and server network at one location and do not have an equipped backup center, ERCOT will only connect to this one location for the transfer of data. If a TDSPTSP and QSE share a centralized PBX, separate OPX circuits will be terminated for each participant. The Hotline will not be allowed to connect through the PBX system and is required for each participant.

(4) A QSE or TDSPTSP involved in the transfer of the critical data identified in Attachment 8A of this guide, will be required to provide the following communication resources to support the connection to the ERCOT private network:

(a) Private Network

Provide an analog business phone line or PBX analog extension for trouble-shooting and maintenance of equipment;.

(b) Provide a height of 24” of rack space in a 19” wide rack;.

(c) Provide two separate UPS single-phase 115 VAC 20 amp circuits, each with 4 receptacles in the 19” rack listed above;.

(d) Provide building wiring from circuit termination to equipment rack;.

(e) Within 24-hours notice, provide ERCOT employees or contractors access to the communication facility;.

(f) Within 1-hour notice, provide emergency access to the facility to ERCOT employees or contractors;.

(g) Provide on site personnel to escort ERCOT employees or contractors;.

(h) Provide a Firewall or router, located at the Market Participant site, for the network address translation of internal Market Participant addresses to external addresses on the ERCOT LAN;.

(i) Market Participant will be required to sign a security connection agreement with ERCOT;.

(j) Provide connectivity from Market Participant Firewall or Router to ERCOT LAN located at Market Participant site. Market Participants are responsible for their own security through this connection;.

(k) Provide a channel bank with at least one T1 interface, 4 FXS and two 4 wire analog ports. Connect FXS (e.g. PBX, key system) and 4 wire ports to the appropriate equipment (e.g. RTU). On the digital T1 stream, levels for voice are zero dpm for transmit and receive; and levels for RTU are –13 dpm for transmit and receive.

(l) Hotline must be a 500 set not attached to the Market Participant’s Phone System;.

(m) Dual cable entrances to Market Participant, connecting to different Telco Central Offices highly recommended; and.

(n) Provide ERCOT with internal IP addressing scheme as needed for network design. This will be kept confidential..

(5) Internet (optional)



A QSE or TDSPTSP not involved in the transfer of the data identified in Attachment 8A of these Operating Guides, is not required to, but, may request ERCOT to provide an optional connection to the ERCOT private network. When such a request is met by ERCOT, the QSE or TDSPTSP must then provide the above stated communications resources.

C SU/DS U

FIRE

WA

LL OR

RO

UTE

R

C SU/DS U

RO U T ER

RO U T ER

SW

ITCH

SW

ITCH

ERCOT PROVIDEDEQUIPM ENT

CH AN N ELBA N K

Taylor H otline (FX S)

T aylor O P X (F X S )

4WIR

E

2W IRE

FR AM ENET W O RK

D ACSNET W O R K

PARTICIPANT SITE

V isual T 1 C S U/D SU Fram e R elayT 1 C S U/DS U

17.5"1.75"

(1) R ack Unit = 1.75 inches(10) R ack Units are required (w ith spacing)to support (2) 2610 R ou ters , (2) 2912Sw itches, (1) Larscom T1 C SU /DS U andO ne V isual N etworks T1 CSU /D S U.

ERCOT EQUIPMENTRACK SPACE

TO PA

RTIC

IPAN

T NETW

OR

KR

S232

GA

TEW

AY

Fractiona l T 1

Austin O P X (FX S )

Austin H otline (FX S)

2W IRE

2W IR E

Larscom T 1 C SU /DS U DAC S N etwork

C isco 2610

C isco 2610

C ata lys t 2912 E thernet Sw itch

C ata lys t 2912 E thernet Sw itch

2W IR E

4WIR

E

RT U W IT H 3ER CO TP O R T S

8.3.4 TDSPTSP and QSE Supplied Communications

(1) Each TDSPTSP and QSE must provide internal facilities and communications to collect and furnish data and voice signals to the ERCOT WAN. For TDSPTSPs these include, but may not be limited to, voice communications and SCADA for substations and other Ttransmission Ffacilities. For QSEs, these include, but may not be limited to, voice and SCADA for generating plants and loads.

(2) QSEs and TDSPTSPs shall supply, implement and maintain all data and voice communication facilities required to fulfill the obligations set forth in the these Operating Guides.

(3) Proper performance, maintenance and testing of communication paths not directly connected to the ERCOT WAN shall be the responsibility of the TDSPTSP or QSE providing the path.



(4) QSEs communicating with connected resources and TDSPTSPs communicating with substations are encouraged to use privately owned communication facilities. Backup facilities utilizing common carriers, different privately owned facilities, or communications paths to a site are encouraged to provide increased reliability, (i.e., separate paths to a site using different carrier, having multiple microwave paths leaving a site, etc.).

8.3.5 Maintenance and Restoration

(1) It is the joint responsibility of ERCOT WAN-connected parties to coordinate maintenance and restoration activities so its reliability is not compromised. Coordination and notification procedures defined by ERCOT are to be followed by all parties.

(2) All circuits shall be tested annually or as otherwise requested by ERCOT for end-to-end performance. Special attention shall be given to circuits not used for routine communications (including backup circuits).

(3) The hotline and any backup (alternate path) voice circuits shall be used regularly to insure proper performance. ERCOT will specify test procedures for hotline circuits.

(4) Scheduled outages of communication circuits that could reduce the reliability of interconnected operations shall be coordinated between the affected companies and ERCOT.

(5) In the event of wide spread communication failures, priority shall be given to restoring communication circuits between QSE Control Centers/TDSPTSP Control Centers and ERCOT Control Area Authority first, and then between QSEs and TDSPTSPs second.

(6) Test equipment and test standards intended to be used for the calibration or repair of communication equipment shall be certified to values of accuracy and precision, which are equal to or better than the accuracy of the equipment under test.



8.4 Document Control

Authorities

Prepared by Date Completed Reviewed by Date AuthorizedB. Brodie December 29, 2000 B. Garza, Chair – Joint Operating

Guide Working Group

I. Flores December 1, 2002 OGRTF & ROS November, 2002

I. Flores March 1, 2003 OGRTF

Distribution List

Name OrganizationOperating Guide Working Group ERCOT

Operations ERCOT

Technical Advisory Committee ERCOT

Reliability Operations Subcommittee Technical Advisory Committee

Operating Guides Revision Task Force Reliability Operations Subcommittee

Change History

Issue/Draft Reason for issue DateVersion 0.1 Draft for Review December 29, 2000

Version 0.2 2nd Draft for Review January 18,2001

Version 0.3 Stakeholder Review January 19, 2001

Version 0.4 Stakeholder Review February 5, 2001

Version 1.0 Updated from Working Group comments.Submitted to Technical Advisory Committee to approve handover to the Reliability Operating Subcommittee

February 28, 2001

December 1, 2002

OGRR117; added language from “Communicating with ERCOT” and Protocols references.

December 1, 2002

March 1, 2003 Revised header. March 1, 2003

December 1, 2004

Admin OGRR160 December 1, 2004

September 1, 2005

OGRR163 September 1, 2005

February 1, 2006 OGRR180 February 1, 2006



Attachment 8A: ERCOT Data Sets

For any required data, the following table describes how the data is to be provided to ERCOT or is provided from ERCOT.

ACTION DATA QUANTITY PURPOSE SUPPLIED BY

RECEIVED BY FREQUENCY

MODE OF

COMM.FORMAT PROTOCOLS REFERENCE /

COMMENTS

DAY-AHEAD SCHEDULING PROCESS

Extend Day-Ahead Scheduling Process

Notification to extend Day-Ahead Scheduling Process to Two-Days-Ahead

Emergency Notification ERCOT QSE Demand API XML

Protocols Section 4.4.19, Decision to Extend Day-Ahead Scheduling Process to Two-Day-Ahead Scheduling Process

Day Ahead Notification

Network Operations Model topology which includes Transmission Outages

Day-Ahead Planning ERCOT QSE Daily byefore

0600

API & APIMIS Secure Area

XML

Protocols Section 4.42.23 (a), Advance Publication of Forecasted System ConditionsPosting Forecasted ERCOT System Conditions

Weather assumptions used by ERCOT to forecast system conditions

Day-Ahead Planning ERCOT QSE Daily by 0600

API & APIMIS

Secure Area

XMLProtocol Section 4.2.3 (b), Posting Forecasted ERCOT System Conditions

Any weather-related changes to the transmission contingency listTotal Transmission Capacity

Day-Ahead PlanningDay-Ahead Planning

ERCOTERCOT QSEQSE

Daily by 0600Daily before

0600

API & MIS

Secure Area API

XMLXML

Protocol Section 4.2.3 (c), Posting Forecasted ERCOT System Conditions Protocols Section 4.4.2, Advance Publication of Forecasted System Conditions

ERCOT System, Weather Zone, and Load Zone Load forecasts for next seven days


API & MIS

Secure Area

XMLProtocol Section 4.2.3 (d), Posting Forecasted ERCOT System Conditions

Load forecast distribution factors


API & MIS

Secure Area

XMLProtocol Section 4.2.3 (e), Posting Forecasted ERCOT System Conditions

Load Profiles for non-IDR metered Customers


API & MIS

Secure Area MIS

Secure Area

Protocol Section 4.2.3 (f), Posting Forecasted ERCOT System Conditions

Transmission and Distribution Loss EstimatesDistribution Loss Factors and forecasted ERCOT-wide Transmission Loss Factors


API & MIS

Secure Area

APIMIS Secure Area

XML

Protocol Section 4.2.3 (g), Posting Forecasted ERCOT System Conditions Protocols Section 4.4.6, Notification to QSEs of Transmission Loss Estimates

Current list of Settlements Points that may be used for market processes & transactions


API & MIS

Secure Area MIS

Secure Area

Protocol Section 4.2.3 (h), Posting Forecasted ERCOT System Conditions


ERCOT, 01/24/07,

Move to Section 9




MODE OF


COMMENTS

Mapping of Settlement Points to Electrical Buses in the Network Operations Model


API & MIS

Secure Area MIS

Secure Area

Protocol Section 4.2.3(i), Posting Forecasted ERCOT System Conditions

Mandatory Balancing Energy Service Down Bid Percentage requirements

Day-Ahead Planning ERCOT QSE Daily by 0600 API XML

Protocols Section 4.4.5, Notification to QSEs of Mandatory Balancing Energy Service down Bid Percentage Requirements

Wind-Powered Generation Resource Production Potential forecasts

Day-Ahead Planning ERCOT QSE Each Hour

API & MIS

Certified Area

XMLProtocol Section 4.2.2 (4), Wind-Powered Generation Resource Production Potential

Aggregated Wind-Powered Generation Resource Production Potential forecasts

Day-Ahead Planning ERCOT QSE Each Hour

API & MIS

Secure Area

XMLProtocol Section 4.2.2 (5), Wind-Powered Generation Resource Production Potential

Ancillary Services Plan


API & APIMIS

Public Area

XML Protocol Section 4.2.1.1(1), Ancillary Services Plan

Ancillary Service Obligations


API & MIS

Certified Area API

XMLProtocol Section 4.2.1.2 (2), Ancillary Service Obligation Assignment and Notice

QSE’s Load Ratio Share used for the Ancillary Service Obligation calculation


API & APIMIS

Certified Area

XMLProtocol Section 4.2.1.2 (3), Ancillary Service Obligation Assignment and Notice

Self-Arranged Ancillary Services

Self-Arranged Provided Regulation, Responsive Reserve & Non-Spinning ReserveAncillary Service Quantities, by service

Ancillary Services QSE submit Self-Arranged Ancillary Service

QSE ERCOTDaily before by 1000, @ 1300, then as needed

API XMLProtocol Section 4.4.7.1 (2), Self-Arranged Ancillary Services Quantities





MODE OF


COMMENTS

Ancillary Service Offers

Generation Resource-specific Ancillary Service Offers

QSE submit Ancillary Service OffersAncillary Services

QSE ERCOT Daily byefore 1000 API XML Protocol Section 4.4.7.2 (1),


Load Resource-specific Ancillary Service Offers

QSE submit Ancillary Service OffersAncillary Services

QSE ERCOT Daily beforey 1000 API XML Protocol Section 4.4.7.2 (2),


Ancillary Service Offer Validation

Notify QSE of invalid Offers ERCOT QSE As needed API XML

Protocol Section 4.4.7.2.2 (3), Ancillary Service Offer Validation

Corrected Ancillary Service Offers

QSE submit corrected Offers QSE ERCOT Daily by 1000 API XML

Protocol Section 4.4.7.2.2 (3), Ancillary Service Offer Validation

Ancillary Service Trades

QSE submit Ancillary Service Trades

QSE ERCOT Daily by 1430 API XML Protocol Section 4.4.7.3 (2), Ancillary Service Trades

Ancillary Service Trades Validation

Notify QSE of invalid Trades ERCOT QSE As needed

APIXML Protocol Section 4.4.7.3 (3),

Ancillary Service Trades

Corrected Ancillary Service Trades

Submit Corrected Trades

QSE ERCOT Daily by 1430 API XML Protocol Section 4.4.7.3 (3), Ancillary Service Trades

Valid TradesNotify both buying and selling QSE

ERCOT QSE As needed

API & MIS

Certified Area

XMLProtocol Section 4.4.7.3.2 (2), Ancillary Service Trade Validation

Current Operating Plan (COP)

Submit for any Resource and for Resources that will provide Ancillary Service

QSE submit COP QSE ERCOT Daily by 1430 API XML

Protocol Section 3.9.1, Current Operating Plan (COP) Criteria and 4.4.7.4 (3), Ancillary Service Supply Responsibility

Current Operating Plan Validation

Notify QSE of invalid COP ERCOT QSE As needed API XML

Protocol Section 3.9.2 (4), Current Operating Plan Validation





MODE OF


COMMENTS

Capacity TradesQSEs Submit Balanced Schedules of Obligations and Supply

Balanced Schedules

QSE submit Capacity TradesCSC Congestion and Capacity Insufficiency

QSEQSE ERCOTERCOT

Daily bye1430 will n the

DRUC prDaily before 1100, @ 1300, then as

needed

APIAPI XMLXML

Protocol Section 4.4.1 (2), Capacity Trades Protocols Section 4.4.8 & 4.4.10, Submittal of Day-Ahead Schedules and Ancillary Services Schedules

, if feill be u 3), Capacity Trades

Capacity Trade Validation

Notify QSE of invalid Capacity Trades

ERCOT QSE As needed

API & MIS

Certified Area

XML Protocol Section 4.4.1.2 (2), Capacity Trade Validation

Corrected Capacity Trades

QSE submit corrected Trades

QSE ERCOT Daily by 1430 API XML Protocol Section 4.4.1 (4), Capacity Trades

Energy Trades QSE submit Energy Trades QSE ERCOT Daily by 1430 API XML Protocol Section 4.4.2 (2),

Energy Trades

Invalid Capacity Trades

Energy Trades Validation

Notify QSE of invalid Trades ERCOT QSE As needed API XML Protocol Section 4.4.2 (24,

Energy Trades Val

Corrected Energy Trades

QSE submit corrected Trades

QSE ERCOT Daily by 1430 API XML Protocol Section 4.4.2 (4), Energy Trades

Three-Part Supply Offers

Energy Offer Curve, Startup offers and Minimum-Energy Offers

QSE submit Offers QSE ERCOT Daily by 1000 API XML

Protocol Section 4.4.9.2.1 (2), Startup Offer and Minimum-Energy Offer Criteria

MIS Certified

Area





MODE OF


COMMENTS

Three-Part Supply Offer Validation


Protocol Section 4.4.9.2.2 (3), Startup Offer and Minimum-Energy Offer Validation

Corrected Three-Part Supply Offers

QSE submit correct Offers QSE ERCOT Daily by 1000 API XML

Protocol Section 4.4.9.2.2 (3), Startup Offer and Minimum-Energy Offer Validation

DAM Energy-Only Offer Curve

QSE submit DAM Energy-Only Offer Curve

QSE ERCOT Daily by 1000 API XMLProtocol Section 4.4.9.5 (1), DAM Energy-Only Offer Curves

Energy-Only Offer Curve Validation


Protocol Section 4.4.9.5.2 (2), DAM Energy-Only Offer Validation

Corrected Energy-Only Offer Curve

QSE submit corrected Offers QSE ERCOT Daily by 1000 API XML

Protocol Section 4.4.9.5.2 (2), DAM Energy-Only Offer Validation

DAM Energy Bids

QSE submit DAM Energy Bids

QSE ERCOT Daily by 1000 API XML Protocol Section 4.4.9.6 (1), DAM Energy Bids

Energy Bid Validation

Notify QSE of invalid Bids ERCOT QSE As needed API XML Protocol Section 4.4.9.6 (2),

DAM Energy Bid Validation

Corrected Energy Bids

QSE submit corrected bids QSE ERCOT Daily by 1000 API XML Protocol Section 4.4.9.6 (2),

DAM Energy Bids Validation

Energy Offer Curve

QSE submit Energy Offer Curve

QSE ERCOT Daily by 1000 API XML Protocol Section 4.4.9.3 (2), Energy Offer Curve

Energy Offer Curve Validation

Notify QSE of invalid Offer Curve

ERCOT QSE As needed API XML Protocol Section 4.4.9.3.2 (2), Energy Offer Curve Validation





MODE OF


COMMENTS

Corrected Energy Offer Curve

QSE submit corrected Offer Curve

QSE ERCOT Daily by 1000 API XML Protocol Section 4.4.9.3.2 (2), Energy Offer Curve Validation

Self-Schedules QSE submit Self-Schedules QSE ERCOT

Any interval before the end

of the Adjustment

Period

API XML Protocol Section 4.4.3 Self-Schedules

Self-Schedules Validation

Notify QSE of invalid Self-Schedules

ERCOT QSE As needed API XML Protocol Section 4.4.3 (3), Self-Schedules

Corrected Self-Schedules

QSE submit corrected Self-Schedules

QSE ERCOT As needed API XML Protocol Section 4.4.3 (3), Self-Schedules

Validate Schedules and Bids

Notification of invalid or mismatched schedules

Validate Schedules ERCOT QSE Daily @ 1100 &

1300 API XML

Protocols Section 4.4.12, ERCOT Validation of Qualified Scheduling Entity's Day-Ahead Schedules and Bids

Corrected Schedules

Submit corrected information

QSE ERCOT Daily @ 1115 & 1315 API XML

Protocols Section 4.4.12, ERCOT Validation of Qualified Scheduling Entity's Day-Ahead

Schedules and Bids

Notification of CSC Congestion and/or Capacity Insufficiency

Update Schedules ERCOT QSE Daily by 1115 API XML

Protocols Section 4.4.9, ERCOT Notification of CSC Congestion and/or Capacity Insufficiency based on 1100

DC Tie Schedules

QSE’s Submit DC-Tie Schedules

QSE ERCOT Daily by 1430 API XML Protocol Section 4.4.4 (3), DC Tie Schedules

Validation DC-Tie Schedule Validation

Notify QSE of invalid DC-Tie Schedule

ERCOT QSE As needed API XML Protocol Section 4.4.4 (4), DC Tie Schedules

Corrected DC-Tie Schedules

QSE submit corrected information

QSE ERCOT Daily by 1430 API XML Protocol Section 4.4.4 (4), DC Tie Schedules





MODE OF


COMMENTS

CRR OffersCRR Account Holders to sell CRRs in DAM

QSE submit CRR Offers QSE ERCOT Daily by 1000 API XML Protocol Section 4.4.5, CRR

Offers

CRR Offer Validation

Notify QSE of invalid Offers ERCOT QSE As needed API XML Protocol Section 4.4.5.2 (3),

CRR Offer Validation

Corrected CRR Offers

QSE submit corrected Offers QSE ERCOT Daily by 1000 API XML Protocol Section 4.4.5.2 (3),

CRR Offers

PTP Obligation Bids

QSE submit PTP Obligation Bids

QSE ERCOT Daily by 1000 API XML Protocol Section 4.4.6.1 (1), PTP Obligation Bid Criteria

PTP Obligation Bid Validation

Notify QSE of invalid Bids ERCOT QSE As needed API XML Protocol Section 4.4.6.2 (3),


Corrected PTP Obligation Bids

QSE submit corrected Bids QSE ERCOT Daily by 1000 API XML Protocol Section 4.4.6.2 (3),


DAM Results Awarded DAM Transactions ERCOT QSE Daily, no later

than 1330 API XML Protocol Section 4.5.3 (1), Communicating DAM Results

MCPC, Settlement Point Prices, LMPs, Shadow Prices, Quantities

View additional information ERCOT QSE Daily, no later

than 1330

API & MIS

Public Area

XML Protocol Section 4.5.3 (2), Communicating DAM Results

Procure Ancillary Services

AS Bids to ERCOT Ancillary Services Market QSE ERCOT Daily by 1300 API XML Protocols Section 4.4.11,

Ancillary Services Bid





MODE OF


COMMENTS

Purchase Regulation Up

Complete Day-Ahead Ancillary Services Plan

ERCOT QSE Daily by 1330 API XMLProtocols Section 4.4.13, ERCOT Day-Ahead Ancillary Services Procurement Process

Purchase Regulation Down



Purchase Responsive Reserves



Purchase Non-Spinning Reserves



Ancillary Services Schedules

Notification of Selected Ancillary Services Bids


Publish Day-Ahead MCPs for Capacity (MCPCs) for each Day-Ahead Ancillary Service

Complete ERCOT's Day-Ahead Ancillary Services Plan

ERCOT QSE Daily @ 1330 API XMLProtocols Section 4.4.13, ERCOT Day-Ahead Ancillary Services Procurement Process

Final Ancillary Services Schedules

Updated Day Ahead Ancillary Services Schedule

QSE ERCOT Daily @ 1500 API XMLProtocols Section 4.4.14, ERCOT Day-Ahead Ancillary Services Procurement Process

QSE Present ResourceCurrent Operating Plan

ResourceUnit Availability Status

Generation Planning, AS VerificationQSE submit COP

QSE ERCOTDaily @ 1600 by 1430, then as needed

API XML

Protocols Section 3.9, Current Operating Plan (COP) 4.44..15.4, 3AnclaQSE Resource Plans

Unit Planned Net Hourly Generation MW

Notify QSE of invalid COPGeneration Planning, AS Verification

ERCOTQSE ERCOTQSE

As neededDaily @ 1600, then

as neededAPIAPI XMLXML

Protocol Section 3.9.2 (1), Current Operating Plan ValidationProtocols Section 4.4.15, QSE Resource Plans

Unit Planned High Net Hourly Operating Limit MW

QSE correct COPGeneration Planning, AS Verification

QSEQSE ERCOTERCOT

Daily by 1430, then as needed Daily @ 16000, then as needed

APIAPI XMLXML

Protocol Section 3.9.2 (1), Current Operating Plan ValidationProtocols Section 4.4.15, QSE Resource

Unit Planned Low Net Hourly Operating Limit MW

Generation Planning, AS Verification

QSE ERCOT Daily @ 1600, then as needed API XML Protocols Section 4.4.15, QSE

Resource Plans

Load acting as a Resource


QSE ERCOT Daily @ 1600, then as needed API XML Protocols Section 4.4.15, QSE

Resource Plans

Notification to QSE for insufficient resources


ERCOT QSE Daily by 1600 API XML Protocols Section 4.1.1, QSE Resource Plans





MODE OF


COMMENTS

Procure Replacement Reserve Service

Unit-Specific Replacement Reserve Service (RPRS) Bids

QSEs may submit Replacement Reserve Service (RPRS) Bids

QSE ERCOT Daily by 1600, then as needed API XML

Protocols Section 4.4.16, ERCOT Receipt of Replacement Reserve Service Bids

Resource Specific Premiums

QSEs may submit hourly Resource specific premiums

QSE ERCOT Daily by 1430, then as needed API XML

Protocols Section 4.5.3, ERCOT Receipt of Resource Specific Premiums for Operational Congestion Management

Procurement of Replacement Reserve

ERCOT purchase RPRS ERCOT QSE Daily by 1800 API XML

Protocols Section 4.4.17, ERCOT Procurement of Replacement Reserve Service As Needed

Adjustments to schedules of Reliability Must-Run (RMR) resources

Adjustments to the QSE's schedules

ERCOT QSE Demand API XML

Protocols Section 4.5.11 , ERCOT Deployment of Reliability Must-Run Generators

ADJUSTMENT PERIOD

Adjustment Period Schedule Changes

Current Operating Plan

QSE submit and update Resource Status

QSE ERCOT

As needed during

Adjustment Period

API XML Protocol Section 6.4.5, Resource Status

Capacity Trades, Energy Trades, Self-Schedules, and Ancillary Service Trades

QSE submit and update Trades and Schedules

QSE ERCOT

As needed during

Adjustment Period

API XML

Protocol Section 6.4.1, Capacity Trades, Energy Trades, Self-Schedule, and Ancillary Service Trades

Output SchedulesQSE submit and update Output Schedules

QSE ERCOT

As needed during

Adjustment Period

API XML Protocol Section 6.4.2, Output Schedules

Non-DSR Resource

QSE submit and update Output schedule for a non-DSR Resource

QSE ERCOT

As needed during

Adjustment Period

API XML

Protocol Section 6.4.2.1, Output Schedules for Resources Other than Dynamically Scheduled Resources

QSE submit Incremental and Decremental Energy Offer Curves for DSRs

QSE ERCOT

As needed during

Adjustment Period

API XMLProtocol Section 6.4.2.2, Output Schedules Dynamically Scheduled Resources





MODE OF


COMMENTS

Energy Offer CurveQSE submit and update Energy Offer Curves

QSE ERCOT

As needed during

Adjustment Period

API XML Protocol Section 6.4.3 (3), Energy Offer Curve

Three-Part Supply Offers

QSE submit Three-Part Supply Offers for Off-line Generation Resources

QSE ERCOT

As needed during

Adjustment Period

API XMLProtocol Section 6.3.1 (1), Activities for the Adjustment Period

Notify QSEs of HRUC results ERCOT QSE As needed API XML

Protocol Section 5.5.3 (2), Communication of RUC Commitments and Decommitments

Supplemental Ancillary Service Market

Notify QSEs of intent to procure additional Ancillary Services

ERCOT QSE

As needed during

Adjustment Period

API XMLProtocol Section 6.4.8.2 (2), Supplemental Ancillary Service Market

QSEs may resubmit Ancillary Service Offers

QSE ERCOT30 minutes from time of

noticeAPI XML Protocol Section 6.4.8.2 (2),


Notify QSEs with awards ERCOT QSE As needed API XML Protocol Section 6.4.8.2 (2),


QSE submit updated COP and updated Ancillary Service Schedule

QSE ERCOT As needed API XML Protocol Section 6.4.8.2 (2), Supplemental Ancillary Service Market

QSE's can make schedule adjustments and ERCOT can request additional bids.

Time T is the start of the Operating

Period

The Adjustment Period (AP) begins following the close of the Day-Ahead market and continues until one (1) hour prior to the beginning of the Operating Hour.

Adjustment Period Schedule Changes

Submit or change Energy Schedule and Ancillary Services Schedules

Adjustment Period Scheduling Process

QSE ERCOT T minus 60 minutes API XML

Protocols Section 4.5.1, Receipt of Adjustment Period Schedule Changes

Submit, change, or remove Balancing Energy Service Up and Down Bids








MODE OF


COMMENTS

Submit, change, or remove RPRS Bids




Require mandatory Balancing Energy Service Down Bid Curves


ERCOT QSE T minus 60 minutes API XML

Protocols Section 4.5.2, Receipt of QSE's Balancing Energy Bid Curves

Submit Balancing Energy Service Up and Down Bid Curves



Protocols Section 4.5.2, Receipt of QSE's Balancing Energy Bid Curves

Announce need to procure RPRS

Procure Submitted Bids ERCOT QSE T minus 60

minutes API XML

Protocols Section 4.5.6, ERCOT Notice of Need to Procure Replacement Reserve Service Resources

Announce need to procure additional Ancillary Services

Procure Submitted Bids ERCOT QSE T minus 60

minutes API XML

Protocols Section 4.5.8, ERCOT Notice of Need to Procure Additional Ancillary Services

QSE Update their Resource Plan

Update prior to close of the Adjustment Period

QSE ERCOT T minus 60 minutes API XML Protocols Section 4.5.10,

Updated Resource Plans

QSE Update their Balanced Schedules


QSE ERCOT T API XMLProtocols Section 4.5.6 & 4.5.8, Updated Balanced Schedules

QSE Resubmit Corrected Balanced Schedule


QSE ERCOT T plus 15 minutes API XML

Protocols Section 4.5.6 & 4.5.8, Corrected Balanced Schedule

Procure RPRS ERCOT purchase RPRS ERCOT QSE T plus 30

minutes API XML Protocols Section 4.5.6,

Procure additional Ancillary Services

ERCOT purchase additional ancillary service

ERCOT QSE T plus 30 minutes API XML Protocols Section 4.5.8,

OPERATING PERIOD

DNP 3.0 protocol will be used for new ports to RTUs or SCADA systems.

FCSLFC InputsFrequencyReal-Time Monitoring and Control

ERCOT/QSE ERCOT 2 sec RTUICCP

DNP 3.0Blocks

1 & 2

Protocols Section 6.5.7.6.1(3)6.10.5, QSELFC Process. Real Power Performance Criteria

UnitGeneration MonitoringResource Data

Generating Generation ResourceUnit MW

Real-Time Monitoring, SCED & Security Analysis

QSE ERCOT 2 sec RTUICCP

Blocks1 & 2DNP

3.0

Protocols Section 6.5.51.2 (2) a1, Operational Data Requirements for Operating Period Data for System Reliability and Ancillary Service ProvisionNet and Gross Generation is requiredpreferred. If gross MW is supplied, aux load should also be provided..


ERCOT, 01/24/07,

Waiting for PRR 647 to pass




MODE OF


COMMENTS

Generationg ResourceUnit Mvar


QSE ERCOT 10 sec RTU/ICCP

Blocks1 & 2DNP

3.0

Protocols Section 6.5.5.2 (2) b1.1, Operational Data Requirements for Operating Period Data for System Reliability and Ancillary Service ProvisionNet and Gross ReactiveGeneration is requiredpreferred. If gross MVar is supplied, aux load should also be provided.

Plant Auxiliary Load


QSE ERCOT 10 sec ICCP Blocks1 & 2

Protocol Section 6.5.5.2 (2) c, Operational Data Requirements.

Private NetworkNet Interchange High Limit

Real-Time Monitoring & Security Analysis

QSE ERCOT 10 sec RTU/ICCP DNP 3.0

For private networks, the high operating limit will reflect the maximum generation available at the point of interconnection to ERCOT.

Private NetworkNet Interchange Low Limit

Real-Time Monitoring & Security Analysis

QSE ERCOT 10 sec RTU/ICCP DNP 3.0

For private networks, the low operating limit will reflect the minimum generation available at the point of interconnection to ERCOT.

Status of switching devices in the plant switchyard not monitored by the TDSPTSP affecting flows on the ERCOT System


QSE ERCOT 10 sec RTU/ICCP

Blocks1 & 2DNP

3.0

Protocols Section 6.5.5.2 (2) d, 1.1, Operational Data Requirements. for Operating Period Data for System Reliability and Ancillary Service Provision

Generationng UnitResource Breaker and Switch Status


QSE ERCOT 10 2 sec RTU/ICCP

Blocks1 & 2DNP

3.0

Protocols Section 6.5.5.2 (2) f1.1, Operational Data Requirements. for Operating Period Data for System Reliability and Ancillary Service Provision

Generator Step-up Transformers Tap Position


QSE ERCOT 10 sec ICCPBlocks1 & 2

Protocol Section 6.5.7.1.13 (1) (d) (ii) (A), Data Inputs and Outputs for the Real-Time Sequence and SCED.

Generatioinng UnitResource High Sustained Operating Limit (HSL)



Blocks1 & 2DNP

3.0

Protocol Section 6.4.5 (1), Resource Status, Protocols Section 6.5.5.2 (2) g1.1, Operational Data RRequirements and Protocol Section 6.5.7.1.13 (1) (d) (ii) (B), Data Inputs and Outputs for the Real-Time Sequence and SCED. for Operating Period Data for System Reliability and Ancillary Service Provision


ERCOT, 01/24/07,

Waiting for PRR 647 to pass




MODE OF


COMMENTS

Generation Resource Low Sustained Limit (LSL)



Protocol Section 6.4.5 (1), Resource Status, Protocol Section 6.5.5.2 (2) j, Operational Data Requirements and Protocol Section 6.5.7.1.13 (1) (d) (ii) (C), Data Inputs and Outputs for the Real-Time Sequence and SCED.

Generation Resource High Emergency Limit (HEL)



Protocol Section 6.5.5.2 (2) h, Operational Data Requirements.

Generationg UnitResource Low Emergency Operating Limit (LEL)


QSE ERCOT 10 2 secICCPRT

U/ICCP

Blocks1 & 2DNP

3.0

Protocol Section 6.5.5.2 (2) j, Operational Data Requirements.Protocols Section 6.5.1.1, Requirements for Operating Period Data for System Reliability and Ancillary Service Provision

Text reason for any Resource where a ramp rate is deviating from a standard ramp rate curve for the resource, or the HSL is less than, or LSL is greater than, the normal high and low limits set in protocol section 3.7.1, Resource Parameter Criteria



Protocol Section 6.4.5 (1), Resource Status

Generation Resource Normal Ramp Rate



Protocol Section 6.4.5 (1), Resource Status.

Generation Resource Emergency Ramp Rate


QSE ERCOT 2 sec ICCP Blocks 1 & 2

Protocol Section 6.4.5 (1), Resource Status.

Generation Resource Status



Protocol Section 6.4.5 (1), Resource Status and 6.5.5.1(1).

Unit Monitoring

Generationg UnitResource Regulation Up Schedule


QSE ERCOT 10 2 sec ICCP DN Blocks 1 & 2P 3.0

Protocol Section 6.5.5.2 (2) k, Operational, Operational Data Requirements.

Unit Monitoring

Generationg ResourceUnit Regulation Down Schedule


QSE ERCOT 10 2 sec RTUICCP

Blocks 1 & 2






MODE OF


COMMENTS

Unit Monitoring

Generationg UniResourcet Responsive Reserve Schedule


QSE ERCOT 10 2 sec ICCP Blocks 1 & 2


Unit MonitoringGenerationg UnitResource Non-Spin Schedule



Protocol Section 6.5.5.2 (2) k, Operational Data Requirements.

Unit Monitoring

Generationg UnitResource Regulation Up Participation Factor



Protocol Section 6.5.5.2 (2) l, Operational Data Requirements.

Unit Monitoring

Generationg UnitResource Regulation Down Participation Factor




Unit Monitoring

Generationg UnitResource Responsive Reserve Participation Factor




Unit Monitoring

Generationg UnitResource Inhibit Blocked Regulation Up Status



Protocol Section 6.5.5.2 (6), Operational Data Requirements.

Unit Monitoring

Generationg UniResourcet Inhibit Blocked Regulation Down Status




Combined-Cycle Configuration



Protocol Section 6.5.5.2 (8) b, Operational Data Requirements.

Generation Resource DSR Base Point



Protocol Section 6.5.7.6.1(8) j, LFC Process Description.

Private Network Net Interchange to ERCOT


QSE ERCOT 2 Sec RTUICCP

Blocks 1 & 2DNP

3.0

For private networks, the net interchange shall be provided along with gross MW and MVar per generationg unitResource.

NOTE: perating Period data from QSE units can be made available to the PGCs host TDSP on request.

Wind Powered Generation Resource Data

Wind Speed




Load Resource Data

Load used as a Resource MW

Real-Time Monitoring, SCED & Security Analysis Real-Time Monitoring

QSE ERCOT 2 sec RTUICCP

DN Blocks 1 & 2P 3.0

Protocols Section 6.5.5.2(4) a1.1, Operational Data Requirements. Shall be telemetered to ERCOT using a (-) sign convention. for Operating Period Data for





MODE OF


COMMENTS

System Reliability and Ancillary Service Provision

Resource Status



Protocol Section 6.4.5 (1), Resource Status, Protocol Section 6.5.5.1(1), Changes in Resource Status, Protocol Section 6.5.5.2 (8) b & c, Operational Data Requirements.

Load Resource Breaker Status



DNP Blocks

1 & 2 3.0

Protocols Section 6.5.5.2 (4) c1.1, Operational Data Requirements. for Operating Period Data for System Reliability and Ancillary Service Provision

Load Resource Low Power Consumption (LPC)



Protocol Section 6.5.5.2(4) d, Operational Data Requirements. Shall be telemetered to ERCOT using a (-) sign convention

Load Resource Maximum Power Consumption (MPC)



Protocol Section 6.5.5.2 (4) e, Operational Data Requirements. Shall be telemetered to ERCOT using a (-) sign convention

Load Resource (providing Responsive Reserve) High-Set Under-frequency Relay Status (if RRS resource)



DN Blocks 1 & 2P 3.0

Protocols Section 6.5.5.2 (4) g1.1, Operational Data Requirements. for Operating Period Data for System Reliability and Ancillary Service Provision

Load Responsive Reserve Schedule



Protocol Section 6.5.5.2 (4) f, Operational Data Requirements.

Load Resource Responsive Reserve Participation Factor



Protocol Section 3.6, Load Participation (implied).

Load Regulation Down Schedule




Load Resource Regulation Down Participation Factor




Load Resource Regulation Up Schedule








MODE OF


COMMENTS

Load Resource Regulation Up Participation Factor




Load Resource Non-Spin Schedule




Load Resource Inhibit Regulation Up Status




Load Resource Inhibit Regulation Down Status




Load Resource NRAMP




Load Resource ERAMP




Load Resource DSR Output Schedule



Protocol Section 6.5.5.2 (2) e, Operational Data Requirements

Note: Requirements were written with the May 5, 2006 Protocols. This requirement came after that date.

Controllable Load Resource Scheduled Power Consumption that represents zero Ancillary Service Deployments

Real-Time Monitoring QSE ERCOT 10 sec ICCP Blocks

1 & 2

Protocol Section 6.5.5.2 (4) h, Operational Data Requirements

Note: Requirements were written with the May 5, 2006 Protocols.

Controllable Load Resource Net Reactive Power (in MVar)


1 & 2

Protocol Section 6.5.5.2 (4) i, Operational Data Requirements





MODE OF


COMMENTS

This requirement came after that date.

DSR LoadDynamicSR ResourceLoad Power Schedules

Real-Time Monitoring QSE ERCOT 210 sec RTUICC

P

DNP 3.0Blocks

1 & 2

Protocols Sections 4.9 Implementation Principles for Dynamic Load Schedules and 6.10.4.3 - Schedule Control Error6.4.2.5 (3) a, DSR Load.

DSR Output Schedules


1 & 2Protocol Section 6.4.2.5 (3) a, DSR Load.

Bus Data Unit High Side Bus Voltage kV


1 & 2

Protocol Section 6.5.5.2, Voltage Support Service, May be supplied by the TSP. Low Side with appropriate transformer model may be substituted.

Bus Voltage at Private Network connection to ERCOT


1 & 2This voltage may be supplied by the TSP.

Data sent to QSE

LMPs created by each SCED process for each Resource Node and the Settlement Point Price at each Hub and Load Zone

SCED Results ERCOT QSE 5 min ICCP Blocks1 & 2

Protocol Section 6.3.2, Activities for Real-Time Operations

Deploy Ancillary Services

Instructed Regulation Up / Down MW

FCSLFC Instruction ERCOT QSE 4 sec RTUICC

P

DNP 3.0Blocks

1 & 2

Protocols Section 6.5.7.6.2.1 (8)1.1, Deployment of Regulation Service.

Instructed Responsive Reserve MW

FCSLFC Instruction ERCOT QSE 4 sec RTUICC

P

DNPBlocks

1 & 2 3.0

Protocols Section 6.5.7.6.2.2 (11), Deployments of Responsive Reserve Service.1.1, Requirement for Operating Period Data for System Reliability and Ancillary Service Provision & 6.7.3(1), Responsive Reserve Service

Non-Spinning Dispatch Instruction (on/off)

LFC ERCOT QSE 4 sec ICCP Blocks1 & 2

Protocol Section 6.5.7.6.2.3 (4), Non-Spinning Reserve Service Deployment.

Generation Resource Data sent to QSE

Resource identifier LFC ERCOT QSE 4 sec ICCP Blocks1 & 2

Protocol Section 6.5.7.4 (a), Base Points.





MODE OF


COMMENTS

Generator base point MW LFC ERCOT QSE 4 sec ICCP Blocks

1 & 2Protocol Section 6.5.7.4 (b), Base Points.

Generator LMP LFC ERCOT QSE 4 sec ICCP Blocks1 & 2

Protocol Section 6.3.2 (2), Activities for Real-Time Operations.

Generator Suspend Ramping to Base Point (on/off)


Protocol Section 6.5.7.6.1 (9), LFC Process Description

Generator base point above HASL due to RRS (on/off)


Protocol Section 6.5.7.4 (c), Base Points.

Time of Dispatch LFC ERCOT QSE 4 sec ICCP Blocks1 & 2

Protocol Section 6.5.7.4 (d), Base Points.

Pseudo unit dispatch (on/off) LFC ERCOT QSE 4 sec ICCP Blocks

1 & 2Protocol Section 6.5.7.4 (e), Base Points.

Emergency Base Point Data Packet

Resource Identifier LFC ERCOT QSE 4 sec ICCP Blocks1 & 2

Protocol Section 6.5.9.2 (3) c, Failure of the SCED Process.

Emergency base point (on/off) LFC ERCOT QSE 4 sec ICCP Blocks

1 & 2Protocol Section 6.5.9 (1), Emergency Operations.

Time of Dispatch Instruction - Start LFC ERCOT QSE 4 sec ICCP Blocks

1 & 2Protocol Section 6.5.9.2 (3) c, Failure of the SCED Process.

Time of Dispatch Instruction - Duration


Protocol Section 6.5.9.2 (3) c, Failure of the SCED Process.





MODE OF


COMMENTS

Governor Response Monitoring ERCOT QSE 10 sec RTU DNP 3.0

ERCOT calculated governor response from QSE frequency bias. Protocols Section 6.Control Error

Generating Unit Governor Response

Real-Time Monitoring ERCOT QSE 10 sec. RTU DNP 3.0

Protocols Section 6.5.1.1 Requirements for Operating

Period Data for System Reliability and Ancillary

Service Provision.

Bus Data Set HUB or Load zone LMP LFC ERCOT QSE 4 sec ICCP Blocks

1 & 2

Protocol Section 6.3.2 (2), Activities for Real-Time Operations.

Ancillary Services Capacity Monitor

Responsive Reserve Capacity from Generation Resources

ERCOT QSE 10 sec ICCP Blocks1 & 2

Protocol Section 6.5.7.5 (1) a, Ancillary Services Capacity Monitor.

Responsive Reserve Capacity from Load Resources


Protocol Section 6.5.7.5 (1) b, Ancillary Services Capacity Monitor.

Non-Spinning Reserve available from On-Line Generation Resources with Energy Offer Curves


Protocol Section 6.5.7.5 (1) c, Ancillary Services Capacity Monitor.

Non-Spinning Reserve available from undeployed Load Resources


Protocol Section 6.5.7.5 (1) d, Ancillary Services Capacity Monitor.

Non-Spinning Reserve available from Off-Line Generation Resources


Protocol Section 6.5.7.5 (1) e, Ancillary Services Capacity Monitor.

Non-Spinning Reserve available from Resources with Output Schedules


Protocol Section 6.5.7.5 (1) f, Ancillary Services Capacity Monitor.

Undeployed Regulation Up and Undeployed Regulation Down


Protocol Section 6.5.7.5 (1) g, Ancillary Services Capacity Monitor.

Available capacity with Energy Offer Curves in the ERCOT System that can used to increase Base Points in SCED


Protocol Section 6.5.7.5 (1) h, Ancillary Services Capacity Monitor.

Available capacity with Energy Offer Curves in the ERCOT System that can used to decrease Base Points in SCED


Protocol Section 6.5.7.5 (1) i, Ancillary Services Capacity Monitor.

Available capacity without Energy Offer Curves in the ERCOT System that can used to increase Base Points in SCED


Protocol Section 6.5.7.5 (1) j, Ancillary Services Capacity Monitor.





MODE OF


COMMENTS

Available capacity with Energy Offer Curves in the ERCOT System that can used to decrease Base Points in SCED


Protocol Section 6.5.7.5 (1) k, Ancillary Services Capacity Monitor.

Note: Requirements were written with the May 5, 2006 Protocols. This requirement came after that date.

Responsive Reserve Capacity from Controllable Load Resources


Protocol Section 6.5.7.5 (1) c, Ancillary Services Capacity Monitor

FCS Control Instructions

Instructed Non-Spinning Reserve MW

Instruction ERCOT QSE Every 15 minutes API XML Protocols Section 6.7.4(6),

Non-Spinning Reserve Service

Instructed Balancing Energy MW (Up / Down)

Instruction ERCOT QSEEvery 15 minutes with 10 minutes notice

API XMLProtocols Section 6.5.2, & 6.7.1.1(8) Balancing Energy Service

Reliability Instructions

Instructed Replacement Reserve Instruction ERCOT QSE As needed API XML

Protocols Section 6.5.6, Replacement Reserve Service

Instructed Voltage Support Instruction ERCOT QSE As needed API XML

Protocols Section 6.5.7, Voltage Support Service

Instructed Black Start Instruction ERCOT QSE As needed API XML

Protocols Section 6.5.8, Black Start Service

Instructed Reliability Must-Run Instruction ERCOT QSE As needed API XML Protocols Section 6.5.9,

Reliability Must-Run Service

Instructed Out-of-Merit Capacity Instruction ERCOT QSE As needed API XML

Protocols Section 6.5.10, Out-of-Merit Capacity and Out-of-Merit Energy Services

Instructed Out-of-Merit Energy Instruction ERCOT QSE As needed API XML

Protocols Section 6.5.10, Out-of-Merit Capacity and Out-of-Merit Energy Services

Security Analysis

Generation Generating data is provided by QSEs as defined above under Operating Period Data

Bus

Bus Data Bus Voltage kV


TDSPTSP ERCOT 10 sec ICCP Blocks 1&2

Protocol Section 6.5.7.1.13(1)(a)(i), Data Inputs and Outputs for the Real-Time Sequence and SCED

Bus Frequency Hz Real-Time Monitoring TDSP ERCOT 10 sec ICCP Blocks

1&2

Transformer

Transformer Transformer Flow Real-Time TDSPTSP ERCOT 10 sec ICCP Blocks Protocol Section 6.5.7.1.13(1)





MODE OF


COMMENTS

Data MW

Monitoring, SCED & Security Analysis Real-Time Monitoring

1&2

(a)(ii), Data Inputs and Outputs for the Real-Time Sequence and SCED. Positive flow is into the transformer.

Transformer Flow Mvar



Protocol Section 6.5.7.1.13(1)(a)(ii), Data Inputs and Outputs for the Real-Time Sequence and SCED. Positive flow is into the transformer

LTC Tap Position



Protocol Section 6.5.7.1.13(1)(a)(v), Data Inputs and Outputs for the Real-Time Sequence and SCED.

Transformer Status Real-Time Monitoring TDSP ERCOT 10 sec ICCP Blocks

1&2Used if the computer(s) have a Network Topology Processor

Line Circuit Breaker data may be used instead of line data.

Transmission Line Data Line Flow MW



Protocol Section 6.5.7.1.13(1)(a)(ii), Data Inputs and Outputs for the Real-Time Sequence and SCED. Positive flow is out of the station

Line Flow Mvar



Protocol Section 6.5.7.1.13(1)(a)(ii), Data Inputs and Outputs for the Real-Time Sequence and SCED. Positive flow is out of the station

Circuit Status Real-Time Monitoring TDSP ERCOT 10 sec ICCP Blocks

1&2Used if the computer(s) have a Network Topology Processor

Shunt

Shunt (Inductive or Capacitive Data

MW


TSP ERCOT 10 sec ICCP Blocks 1&2

Protocol Section 6.5.7.1.13(1)(a)(ii), Data Inputs and Outputs for the Real-Time Sequence and SCED. Positive for supplying VAR Negative for absorbing VAR

Reactive Support from Shunt Mvar



Protocol Section 6.5.7.1.13(1)(a)(ii), Data Inputs and Outputs for the Real-Time Sequence and SCED. Positive for supplying VAR Negative for absorbing VAR

Bank Breaker Status



Protocol Section 6.5.7.1.13(1)(a)(iii), Data Inputs and Outputs for the Real-Time Sequence and SCED. Used if the computer(s) have a Network Topology Processor

Circuit Breaker

Includes: Circuit Breaker (CB), Line Switch (LS), and Disconnect Switch (DCS) (where applicable)Line data may be used instead of circuit breaker data.

Circuit Breaker Data

CB Circuit Breaker MW flow

Real-Time Monitoring, TDSPTSP ERCOT 10 sec ICCP Blocks

1&2Protocol Section 3.10.7.4 (2), Telemetry Criteria. Positive





MODE OF


COMMENTS

SCED & Security Analysis Real-Time Monitoring

flow is from bus section to equipment (optional)

Circuit Breaker Mvar



Protocol Section 3.10.7.4 (2), Telemetry Criteria. Positive flow is from bus section to equipment (optional)

Breaker StatusSwitch Position



Protocol Section 3.10.7.4 (2), Telemetry Criteria.

Load Data

Load metering is preferred from the high side of the transformation point of the substation distribution transformer.

Load in MW



Protocol Section 3.10.7.4 (2), Telemetry Criteria. (Implied). Negative for Load MW.

Load in Mvar



Protocol Section 3.10.7.4 (2), Telemetry Criteria. (Implied). Negative for Load Mvar.

DC Injection

DC Tie Injection Data DC Injection in MW



Protocol Section 3.10.7.2 (3), Modeling of Resources and Transmission Loads. Positive flow is out of the station.

DC Injection in Mvar



Protocol Section 3.10.7.2 (3), Modeling of Resources and Transmission Loads. Positive flow is out of the station

DC Tie Breaker Status



Protocol Section 3.10.7.2 (3), Modeling of Resources and Transmission Loads. (Implied)Used if the Computer(s) have a Network Topology Processor

Weather Zone Tie Line Datas

Line Flow MWTemperature


TDSPTSP ERCOT 10 sec ICCPDNP 3.0

Blocks 1&2

TDSP’s responsible for supplying weather zone tie line data must provide a redudant path from their normal ICCP link. This second path may be a second ICCP association to ERCOT or an RTU or other device using DNP 3.0 protocol.Protocol Section 6.5.7.1.13 (1) e, Data Inputs and Outputs for the Real-Time Sequence and SCED.





MODE OF


COMMENTS

Wind Speed (if available)


TSP ERCOT 10 sec ICCP Blocks 1&2

Protocol Section 6.5.7.1.13 (1) e, Data Inputs and Outputs for the Real-Time Sequence and SCED.

Dynamic Rating Data Line ID


TSP ERCOT 60 secICCP

Blocks 1&2

Protocol Section 3.10.8.1 (1) a, Dynamic Ratings Delivered via ICCP.

From Status



Blocks 1&2

Protocol Section 3.10.8.1 (1) b, Dynamic Ratings Delivered via ICCP.

To Station



Blocks 1&2

Protocol Section 3.10.8.1 (1) c, Dynamic Ratings Delivered via ICCP.

Normal Rating Real-Time Security Analysis

TSP ERCOT 60 min ICCP Blocks1 & 2

Protocol Section 3.10.8.1 (1) d, Dynamic Ratings Delivered via ICCP.

Emergency Rating Real-Time Security Analysis



15-Minute Rating Real-Time Security Analysis



Weather Zone Data

Current Temperature for each applicable Weather Zone

Real-Time Security Analysis


Protocol Section 3.10.8.1, Dynamic Ratings Delivered via ICCP

Block Load Transfer Point Data

Switching Device Status at BLT points.

BLT Transfers TSP ERCOT 10 sec ICCP Blocks1 & 2

Protocol Section 6.5.9.5(i), Block Load Transfers between ERCOT and Non-ERCOT Control Areas

Other Modeled Devices (SVCs, etc.)

MW TSP ERCOT 10 sec ICCP Blocks1 & 2

Protocol Section 6.5.7.1.13, Data Inputs and Outputs for the Real-Time Sequence and SCED.

MVar TSP ERCOT 10 sec ICCP Blocks1 & 2


Status TSP ERCOT 10 sec ICCP Blocks1 & 2




NOTE: Real-Time data for Security Analysis can be provided to TDSPTSPs on request.Private Network refers to generators with self-serve private load behind a single meter at the point of injection into the ERCOT grid.

LEGEND:Supplied by/Received byERCOT - ERCOT Independent System OperatorQSE - Qualified Scheduling EntityTDSP - Transmission, Distribution Service ProviderPGC - Power Generating Company

Mode of CommunicationWeb Portal - Online application available to market participants via the World Wide Web.TCH - Transaction Clearinghouse. The mechanism used to send/receive EDI transactions.API - Programmatic API. A message protocol used to automate data exchange between ERCOT and market participants.ICCP - Inter-Control Center Communication Protocol. A standard protocol used to automate data exchange real-time control information between the ERCOT and participants.RTU - Remote Terminal Unit. Used to gather real-time control/monitoring information.

FormatEDI - Electronic Data Exchange format. EDI formats are specified by the Texas SET working group and are based on standard EDI transaction protocols.XML - eXtensible Markup Language. XML is a self-describing meta language used to facilitate the exchange of data. XML will format requests and receive replies using the API.CSV - Comma Separated Values. A generic file format where elements of data are separated by commas within a file.Office Document - One of the common Microsoft Office file formats such as MS Word or MS Excel.


ERCOT Real Time Operational Metering and Communication€¦ · Web viewTraditionally, utilities have used both analog and digital methods of transmission at existing facilities.

Documents