Wind Plant Operator Data Guide

Transcription

1 GUIDE 9 Deleted: Forecast Wind Plant Operator Data Guide June 2010 Deleted: July April Deleted: 08

2 Version: 1.1 Revision Date: 06/15/2010 Deleted: 0 Deleted: 7 Deleted: 8 Deleted: 08 This document was prepared by: NYISO Customer Support New York Independent System Operator 3890 Carman Road Schenectady, NY (518) Deleted: Rd Disclaimer The information contained within this guide, along with the other NYISO documents, is intended to be used for informational purposes and is subject to change. The NYISO is not responsible for the user s reliance on these publications or for any erroneous or misleading material. Deleted: 2008 Copyright New York Independent System Operator

3 Table of Contents Table of Figures... iv Table of Tables... iv Revision History... v 1. Overview Terminology Static Plant Data Real-Time Data Transfer Process Wind Plant Operator Responsibility Availability Real-Time Data Elements Units and Precision Data Collection Points Frequency Data Transfer Technical Specification Plant Outages/Plant Availability Equipment Maintenance Testing and Calibration Software/Security Upgrades Upgrading Equipment Penalties and Procedures for Dispute Resolution of Data Issues Appendix A. Data Transfer Technical Specification... A-1 A.1 Web Service Definition... A-1 A.1.1 Send Wind Data Message... A-1 A.1.2 Web Service Operations... A-3 A Send Wind Data... A-3 A.2 Web Service Security... A-3 A.2.1 NYISO-Hosted Instance of Send Wind Data Message Web Service... A-3 A.2.2 NYISO Forecast Vendor-Hosted Instance of Send Wind Data Message Web Service... A-4 A.3 A.4 WSDL... A-4 Message Formats XSD... A-5 A.5 References... A-7 NYISO Customer Support iii

4 Table of Figures Figure 4-1 Plant Outage/Availability Reporting Web Page Figure A-1 SendWindData Message Elements... A-2 Table of Tables Table A.1 SendWindData Message Element Descriptions... A-2 iv NYISO Customer Support

5 Revision History Version Date Revisions /15/2010 Global Revised external-document links to explicitly cite URLs from which documents may be accessed. Changed the term meteorological to real-time throughout. Section 1 Generalized the terminology in the overview section to make it applicable to all data requirements described in this guide. Section 1.1 Added definition for Maximum Available Megawatts. Section 2 Added cut-in/cut-out/cut-back-in static data requirements and clarified expectations for keeping information up to date with the NYISO. Section Added column designating measurement type to table on Units and Precision. Added criteria for Maximum Available Megawatts to table on Units and Precision. Section Updated requirement for collection points to ensure that no turbine is more than 5km from a collection point. Section Updated data transfer frequency from once ever 5, 10, or 15 minutes to once every 30 seconds. Section 4 Changed title to from Plant Outages/Availability to Plant Outages/Plant Availability. Section 6 Removed language that was redundant to the tariff, and instead refer the reader to the appropriate section of the tariff. Appendix A Revised to reflect that NYISO and its forecast vendor each host an instance of the SendWindData Message Web service and that wind forecast data must be sent to both the NYISO and its forecast vendor. Updated Figure A-1, SendWindData Message Elements. Added information for MaxAvailableMW to Table A-1, SendWindData Message Element Descriptions. Added section A.2.1, NYISO-Hosted Instance of Send Wind Data Message Web Service. Added section A.2.2, NYISO Forecast Vendor-Hosted Instance of Send Wind Data Message Web Service. Revised section A.3, WSDL. Revised section A.4, Message Formats XSD, to reflected updated XML schema definition for the SendWindData Message Web service. Formatted: Table BL Formatted: Table BL Formatted: Table BL Formatted: Table BL Formatted: Table BL Formatted: Table BL Formatted: Table BL Formatted: Table BL Formatted: Table BL Formatted: Table BL NYISO Customer Support v

6 1.0 7/18/2008 Initial Release vi NYISO Customer Support

7 1. OVERVIEW This guide focuses on the data reporting required of Wind Plant Operators to support the integration of wind power into the New York Control Area. The NYISO requires that Wind Plant Operators provide static plant data, meteorological data, turbine availability, and outage information. This data, coupled with recent plant output megawatt data (provided by the NYISO to the forecast vendor) will be used to estimate Wind Plant power output for the NYISO dayahead market and real-time market runs. 1.1 Terminology The following terms are an integral part of this guide: Centralized Forecast Service The entire program of forecasting wind power in real-time and day-ahead for Wind Plants in NYS, using a centralized approach of collecting the data and predicting output for all plants. The NYISO has contracted with a forecast vendor to produce all of the forecasts. Static Plant Data Detailed layouts, locations, specifications, and configurations of an individual Wind Plant s turbines. Outage Data Schedules of outages and deratings for a specific Wind Plant. Maximum Available Megawatts Total number of potential megawatts available from turbines that are online and currently capable of producing power (including those turbines that are not producing any power due to low wind speeds). This value should exclude those turbines that are not producing power due to a fault condition or a netcomm condition or that are offline for service. Computer System Any or all such systems employed by the Wind Plant Operator for the distinct purpose of storing and transmitting local meteorological data. Meteorological Data The local weather data collected at a specific Wind Plant Operator s site. Meteorological Equipment The equipment used to collect meteorological data. Data Communications Interface The physical communication channels employed by the Wind Plant Operator to transmit meteorological data over the Internet to the NYISO forecast vendor. Meteorological Data Transfer Process The entire process of measuring, collecting, storing, and transmitting of meteorological data, including the Computer Systems, Meteorological Data itself, Meteorological Equipment, and Data Communications Interface. Deleted: NYISO s centralized wind forecasting program Deleted: collect and transmit site-level meteorological data to the NYISO forecast vendor, at least once every 15 minutes. In addition to meteorological data, the NYISO requires Wind Plant Operators to provide advanced notice of plant outages. Deleted: e Deleted: meteorological data and outage data Deleted: MW Deleted: MW Deleted: - Deleted: MWs Deleted: which Deleted:, Deleted:, Deleted: being NYISO Customer Support 1-1

8 This page intentionally blank. 1-2 NYISO Customer Support

9 2. STATIC PLANT DATA As part of the registration process, Wind Plant Operators are required to supply the NYISO with data describing the physical layout of their Wind Plants, details of the turbines being used, manufacturer s power curves, cut-in/cut-out/cut-back-in settings, and meteorological towers. Detailed instructions for providing this information are contained within the NYISO Registration Package, available from the NYISO Web site at the following URL: Wind Plant Operators shall notify the NYISO upon any changes to this static data. Deleted: as well as Field Code Changed NYISO Customer Support 2-1

10 This page intentionally blank. 2-2 NYISO Customer Support

11 3. REAL-TIME DATA TRANSFER PROCESS Deleted: METEOROLOGICAL Deleted: T This section presents the Meteorological Data Transfer Process requirements for Wind Plant Operators. 3.1 Wind Plant Operator Responsibility Each Wind Plant Operator is responsible for the cost assumed with purchase, installation, and appropriate maintenance of all equipment involved with the Real-Time Data Transfer Process. Each Wind Plant Operator is expected to monitor and control its computer systems, meteorological equipment, and data communications interfaces. The Wind Plant Operator shall transmit data according to the specification as defined in Appendix A Data Transfer Technical Specification of this guide. 3.2 Availability The Wind Plant Operator s Real-Time Data Transfer Process shall be designed to operate 24x7x Real-Time Data Elements Deleted: Meteorological Deleted: t Deleted: meteorological Deleted: Meteorological Deleted: t Deleted: t Deleted: Meteorological Units and Precision Measurement Max Available Megawatts Type Required/ Optional Height of measurement Unit Precision (to the nearest ) SCADA R N/A MW 0.1 MW Wind Speed Meteorological R Hub Meters/Second (m/s) 0.1 m/s Wind Direction Meteorological R Hub Degrees from True North Ambient Air Temperature Ambient Air Dewpoint Ambient Air Relative Humidity Barometric Pressure Meteorological O 2m and Hub Degrees Centigrade ( C) Meteorological O 2m Degrees Centigrade ( C) 1 degree 0.1 C 0.1 C Meteorological O 2m (Percentage) 1.0 % Meteorological O 2m HectoPascals (HPa) 60 Pa Deleted: Whole number Deleted: MW NYISO Customer Support 3-1

12 3.3.2 Data Collection Points Each wind turbine at the plant site must be within 5 kilometers of a meteorological data collection point. This is the minimum requirement only; Wind Plant Operators are encouraged to collect and send this data from as many points at the Wind Plant as are available. Ideally, the minimum amount of data would be provided from a stand-alone meteorological tower(s) and augmented with additional sensor data from the turbines. If no such stand-alone tower exists on the site, data may be collected from turbine-mounted sensor equipment alone. Changes to the location of a Data Collection Point and the addition or deletion of Data Collection Points must be approved by the NYISO Frequency Real-time data must be transmitted to both the NYISO and to its wind forecast vendor at least once every 30 seconds. The values provided shall represent an instantaneous measurement of the data rather than an average. 3.4 Data Transfer Technical Specification Please see Appendix A for details of the data transfer technical specification that must be followed by Wind Plant Operators. Deleted: M Deleted: elements shall be transmitted to the NYISO forecast vendor from at least one point at the Wind Plant. Deleted: Meteorological Deleted: elements Deleted:, Deleted:, Deleted: five, ten, or fifteen minutes. Five-minute frequencies are preferred, but ten-minute and fifteen-minute frequencies are also acceptable. Five-minute intervals shall begin at :00, :05, :10, :15, :20, :25, :30, :35, :40, :45, :50, and :55. Ten-minute intervals shall begin at :00, :10, :20, :30, :40, and :50. Fifteen-minute intervals shall begin at :00, :15, :30, and :45. Deleted: n average value over the duration of that interval, using at least 6- second sampling of each measurement. 3-2 NYISO Customer Support

13 4. PLANT OUTAGES/PLANT AVAILABILITY In order to calculate forecasts as accurately as possible, it is critical that Wind Plant Operators provide the NYISO forecast vendor with available capacity ratings for their plants in advance of any reduction in plant output capacity. To report plant availability for the NYISO Centralized Forecasting Service, Wind Plant Operators may login into the NYISO forecast vendor s Web site at: Wind Plant Operators are each provided a username and password for the Web site when initially registering their plants with the NYISO. Once logged in, select Manage Availability from the left navigation bar, specify the beginning of the time period for which the availability is changing, enter the number of MWs available during the period, and click the Add Flag button (see Figure 4-1). If you know when the availability will change again, enter another flag for the time at which the availability is expected to change. Enter Available MW here Click to add Figure 4-1 Plant Outage/Availability Reporting Web Page This data must be reported for both planned and unplanned outages. Planned outages should be reported at least 2 operating days in advance to ensure that the NYISO day-ahead market runs get forecasts reflecting the true Wind Plant availability. Unplanned outages should be reported as soon as practicable. Please note, in addition to reporting plant outages/availability to the NYISO forecast vendor, Wind Plant Operators are still required to comply with the standard NYISO Outage Reporting NYISO Customer Support 4-1

14 procedures that apply to all generators. These procedures can be found in Technical Bulletin 44, "Generator Outage Notification" (available from the NYISO Web site at and the NYISO Outage Scheduling Manual (available from the NYISO Web site at Deleted: : Deleted: Technical Bulletin #44 Generator Outage Notification and NYISO s Outage Scheduling Manual. 4-2 NYISO Customer Support

15 5. EQUIPMENT MAINTENANCE 5.1 Testing and Calibration Meteorological Equipment should be tested and, if appropriate, calibrated, per manufacturer s recommendations or when indications are suspect or maintenance has been performed that may have interrupted or otherwise adversely impacted the accuracy of operational data. 5.2 Software/Security Upgrades Computer system hardware and software should be maintained and upgraded, per manufacturer s recommendations. 5.3 Upgrading Equipment Equipment not meeting the accuracy specified by the manufacturer s standards should be repaired or replaced. NYISO Customer Support 5-1

16 This page intentionally blank. 5-2 NYISO Customer Support

17 6. PENALTIES AND PROCEDURES FOR DISPUTE RESOLUTION OF DATA ISSUES Please see NYISO Services Tariff, Article 5.8a for details of the financial sanctions that may be applicable due to a failure to comply with the requirement of collecting and communicating meteorological data. The Tariff is available from the NYISO Web site at the following URL: Deleted: Pursuant to the NYISO Procedures, Wind Plant Operators shall maintain in good working order equipment to: collect meteorological data at its site and transmit meteorological data to the NYISO forecast vendor in the manner identified in this guide. The NYISO may impose financial sanctions for consistent failure to comply with the Meteorological Data Transfer Process requirements outlined in this guide. Upon making a determination of consistent failure to comply with the Meteorological Data Transfer Process requirements outlined in this guide, the NYISO shall take the following actions. The Wind Plant Operator shall be notified in writing that the NYISO has determined consistent failure to comply with the requirement and may impose financial sanctions if the consistent failure is not corrected. The NYISO shall offer a reasonable opportunity to correct the failure. If, following such reasonable opportunity to cure, such failure is not cured, the NYISO may impose daily sanctions of the greater of $500 or $20/MW of nameplate capacity on the Wind Plant Operator until such failure is cured. The NYISO shall offer the Wind Plant Operator an opportunity to be heard by senior officers of the NYISO prior to imposing sanctions. NYISO Customer Support 6-1

18 This page intentionally blank. 6-2 NYISO Customer Support

19 A. Appendix A. Data Transfer Technical Specification This specification details the formats and protocols that must be followed to enable data exchange between individual Wind Plant Operators and the NYISO (and its forecast vendor). The Web service can be implemented with any Web services technology such as J2EE or Microsoft -based products. Adherence to this specification guarantees interoperability regardless of technology platform. During the registration process, Wind Plant Operators will provide the NYISO with detailed static data including descriptions of their individual site configuration, turbine locations, met tower locations, make/model information, and unique identifiers for each meteorological data collection point. The NYISO forecast vendor will model the Wind Plant s site using this information. Once the Wind Plant s site is modeled in the NYISO forecast vendor s systems, the Wind Plant Operator can begin sending real-time data to the NYISO and its forecast vendor. A.1 Web Service Definition Web Service Description Language (WSDL) is used to describe the technical details of each message and operation defined in the service to be called. WSDL describes a Web service in two fundamental stages: one abstract and one concrete. At an abstract level, it is specified in terms of the messages it sends and receives; messages are described independent of a specific wire format using a type system, typically XML Schema. At a concrete level, a binding specifies transport and wire format details for one or more interfaces; an endpoint associates a network address with a binding; and, finally, a service groups together endpoints that implement a common interface. A.1.1 Send Wind Data Message The NYISO and its forecast vendor host their own instances of the following Web service. SendWindData message: Consumed by Wind Plant Operators to send meteorological data. SendWindData message is used to send the real-time data for each wind plant. Figure A-1 illustrates the elements of the SendWindData message, while Table A.1 provides descriptions of these elements. Deleted: meteorological Deleted: the Deleted: s Deleted: meteorological NYISO Customer Support A-1

20 Figure A-1 SendWindData Message Elements Table A.1 SendWindData Message Element Descriptions Element GenPTID BeginTimeStamp EndTimeStamp SendWindData WindParameters MaxAvailableMW MetData MetID WindSpeed WindDirection Description The GenPTID element is the NYISO s unique representation of the Wind Plant. This is a unique ID given to each Wind Plant Operator as part of the registration process. The BeginTimeStamp element represents the start time of the data collection interval. The EndTimeStamp element represents the end time of the data collection interval. The SendWindData element is the root element for the WindParameters message. It may contain zero or more WindParameters elements. The WindParameters element provides a mechanism for grouping wind unit parameters that may have common attributes. The MaxAvailableMW element represents the total number of MWs available from turbines which are online and operational. The MetData element represents a single set of meteorological data. It contains the required elements MetID, WindSpeed, BarometricPressure, AmbientTemperature, DewPoint, and Humidity. The MetID element is the unique representation of the point (turbine ID/met tower ID) at the Wind Plant Operator s site where the met data was collected. The WindSpeed element represents the Wind speed at hub height collected from each met tower. The WindDirection element represents the Wind direction at hub height collected from each met tower. A-2 NYISO Customer Support

21 Element BarometricPressure AmbientTemperature Dew Point Humidity Description The BarometricPressure element represents the pressure at 2m (WMO standard height) or 30m collected from each met tower. The AmbientTemperature element represents the Temperature at 2m (WMO standard height) or 30m collected from each met tower. The Dew Point element represents the dew point at 2m (WMO standard height) or 30m collected from each met tower. The Humidity element represents the humidity at 2m (WMO standard height) or 30m collected from each met tower. A.1.2 A Web Service Operations Send Wind Data The NYISO and its forecast vendor will each host their own instance of the SendWindData message Web service. Wind Plant Operators will send real-time data (wind parameters) collected from each collection point to both the NYISO and to its forecast vendor by calling their respective instances of this service. The data sent using this operation will be constrained according to the definition of Wind Parameters Message. A.2 Web Service Security Services will be available only over two-way SSL over HTTP. The requestor opens a connection to the Web service using a secure transport, i.e., SSL. In this scenario, the message confidentiality and integrity are handled using the existing transport security mechanisms. Wind Plant Operators will interact with both the NYISO-hosted instance of the Send Wind Data message Web service and the forecast vendor-hosted instance of the Send Wind Data message Web service. Existing RTU/ICCP integration is not affected by this project. A.2.1 NYISO-Hosted Instance of Send Wind Data Message Web Service The NYISO will enforce two-way SSL for all hosted services. The NYISO requires a client certificate signed by NYISO CA (Certificate Authority). This client certificate is required in order to successfully send a message to the NYISO-hosted instance of the Web service. To request this certificate, please follow the instructions on the NYISO Web site at the following URL: Additionally, the NYISO Send Wind Data message Web service requires that a valid userid and password be provided with the transmittal to ensure that only authorized processes are able to deliver data to the NYISO. Your company's Market Information System (MIS) administrator can create this userid/password using the NYISO MIS Marketplace application by establishing a new user for your organization with the appropriate Wind Service privilege of MetDataGroup. Deleted: Deleted: meteorological Deleted: the Deleted: Deleted: the NYISO forecast vendor s hosted service only. Deleted: h Deleted: i Deleted: m Deleted: s Deleted: w Formatted: Hyperlink Formatted: Hyperlink Deleted: 's Deleted: " Deleted: " NYISO Customer Support A-3

22 A.2.2 NYISO Forecast Vendor-Hosted Instance of Send Wind Data Message Web Service The NYISO forecast vendor will utilize a Server Certificate signed by Verisign certificate authority. Additionally, Wind Plant Operators will each obtain a username and password from the NYISO forecast vendor in order to ensure that only authorized processes are able to deliver data to the Forecast Vendor. A.3 WSDL WSDL allows a Web service to document the messages it receives and sends. Following is the WSDL describing various functions of the service hosted by the NYISO forecast vendor for Wind Plant Operators to send meteorological data. Deleted: h Deleted: i Deleted: m Deleted: s Deleted:, which will be used for HTTP Basic Authentication over SSL connection <?xml version="1.0" encoding="utf-8"?> <definitions name="weatherwindserviceporttype" targetnamespace=" xmlns:ns2=" xmlns=" xmlns:ns1=" xmlns:tns=" xmlns:xsd=" xmlns:soap=" <types> <xs:schema elementformdefault="qualified" targetnamespace=" version="1.0" xmlns:tns=" xmlns:xs=" <xs:element name="sendwinddata" nillable="true" type="tns:sendwinddatatype"/> <xs:element name="sendwinddataresponse" nillable="true" type="tns:sendactualmwresponsetype"/> <xs:complextype name="sendwinddatatype"> <xs:sequence> <xs:element maxoccurs="unbounded" minoccurs="0" name="windparameters" type="tns:windparameterstype"/> </xs:sequence> </xs:complextype> <xs:complextype name="windparameterstype"> <xs:sequence> <xs:element name="genptid" type="xs:string"/> <xs:element name="maxavailablemw" type="xs:decimal"/> <xs:element maxoccurs="unbounded" name="metdata" type="tns:mettype"/> </xs:sequence> </xs:complextype> <xs:complextype name="mettype"> <xs:sequence> <xs:element name="metid" type="xs:string"/> <xs:element name="windspeed" type="xs:decimal"/> <xs:element name="winddirection" type="xs:decimal"/> <xs:element name="barometricpressure" type="xs:decimal"/> <xs:element name="ambienttemperature" type="xs:decimal"/> <xs:element name="dewpoint" type="xs:decimal"/> <xs:element name="humidity" type="xs:decimal"/> <xs:element name="begintimestamp" type="xs:datetime"/> <xs:element name="endtimestamp" type="xs:datetime"/> </xs:sequence> </xs:complextype> <xs:complextype name="sendactualmwresponsetype"> <xs:sequence> <xs:element name="status" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:schema> </types> <message name="weatherwindserviceporttype_sendwinddataresponse"> <part name="sendwinddataresponse" element="ns1:sendwinddataresponse"> </part> </message> <message name="weatherwindserviceporttype_sendwinddata"> <part name="sendwinddata" element="ns1:sendwinddata"> </part> A-4 NYISO Customer Support

23 </message> <porttype name="weatherwindserviceporttype"> <operation name="sendwinddata" parameterorder="sendwinddata"> <input message="ns2:weatherwindserviceporttype_sendwinddata"> </input> <output message="ns2:weatherwindserviceporttype_sendwinddataresponse"> </output> </operation> </porttype> <binding name="weatherwindserviceporttypebinding" type="ns2:weatherwindserviceporttype"> <soap:binding style="document" transport=" <operation name="sendwinddata"> <soap:operation soapaction=" <input> <soap:body use="literal"/> </input> <output> <soap:body use="literal"/> </output> </operation> </binding> </definitions> A.4 Message Formats XSD XML schema allows service providers to define XML types for data structures. Below is the XML schema definition for the SendWindData message service. <!--========== Message Type for SendWindData ===========--> <xs:element name="sendwinddata" type="sendwinddatatype"> <xs:documentation>root element for the SendWindData message</xs:documentation> <xs:element name="sendwinddataresponse" type="sendwinddataresponsetype"> <xs:documentation>root element for the SendWindData message Response</xs:documentation> <xs:complextype name="sendwinddatatype"> <xs:documentation>a collection of wind parameters for each wind unit</xs:documentation> <xs:sequence> <xs:element name="windparameters" type="windparameterstype" minoccurs="0" maxoccurs="unbounded"> <xs:documentation>a group of wind parameters</xs:documentation> </xs:sequence> </xs:complextype> <xs:complextype name="windparameterstype"> <xs:documentation>a collection of wind parameters related data for each wind unit</xs:documentation> <xs:sequence> <xs:element name="genptid" type="xs:string"> <xs:documentation>unique Identifier for the Generator</xs:documentation> <xs:element name="maxavailablemw" type="xs:decimal"> <xs:documentation>max Available MW value</xs:documentation> NYISO Customer Support A-5

24 <xs:element name="metdata" type="mettype" maxoccurs="unbounded"> <xs:documentation>a single Met Type Data</xs:documentation> </xs:sequence> </xs:complextype> <xs:complextype name="mettype"> <xs:documentation>a collection of meterological Data</xs:documentation> <xs:sequence> <xs:element name="metid" type="xs:string"> <xs:documentation>unique Identifier for the Met Tower</xs:documentation> <xs:element name="windspeed" type="xs:decimal"> <xs:documentation>wind speed at hub height</xs:documentation> <xs:element name="winddirection" type="xs:decimal"> <xs:documentation>wind direction at hub height</xs:documentation> <xs:element name="barometricpressure" type="xs:decimal"> <xs:documentation>pressure at 2 m (WMO standard height) or 30 m</xs:documentation> <xs:element name="ambienttemperature" type="xs:decimal"> <xs:documentation>temperature at 2 m (WMO standard height) or 30 m</xs:documentation> <xs:element name="dewpoint" type="xs:decimal"> <xs:documentation>dew Point</xs:documentation> <xs:element name="humidity" type="xs:decimal"> <xs:documentation>humidity</xs:documentation> <xs:element name="begintimestamp" type="xs:datetime"> <xs:documentation>interval Begin time-stamp</xs:documentation> <xs:element name="endtimestamp" type="xs:datetime"> <xs:documentation>interval End time-stamp</xs:documentation> </xs:sequence> </xs:complextype> <xs:complextype name="sendwinddataresponsetype"> <xs:documentation>response for SendWindData</xs:documentation> <xs:sequence> <xs:element name="status" type="xs:string"> <xs:documentation>status Indicator for the response</xs:documentation> A-6 NYISO Customer Support

25 </xs:sequence> </xs:complextype> A.5 References Web Services: WSDL: WS Security standard: NYISO Customer Support A-7

26 This page intentionally blank. A-8 NYISO Customer Support