EP2372479B1 - Systèmes et procédés pour la réalisation du suivi et de l'identification des améliorations pour éoliennes - Google Patents

Systèmes et procédés pour la réalisation du suivi et de l'identification des améliorations pour éoliennes Download PDF

Info

Publication number
EP2372479B1
EP2372479B1 EP10382075A EP10382075A EP2372479B1 EP 2372479 B1 EP2372479 B1 EP 2372479B1 EP 10382075 A EP10382075 A EP 10382075A EP 10382075 A EP10382075 A EP 10382075A EP 2372479 B1 EP2372479 B1 EP 2372479B1
Authority
EP
European Patent Office
Prior art keywords
performance data
wind turbine
wind turbines
target
performance
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Revoked
Application number
EP10382075A
Other languages
German (de)
English (en)
Other versions
EP2372479A1 (fr
Inventor
Nizar Yaghi
Aniruddha Gadre
Abraham Morales
Venkata Subramaniyan
Valika Wan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
General Electric Co
Original Assignee
General Electric Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=42734757&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP2372479(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by General Electric Co filed Critical General Electric Co
Priority to EP10382075A priority Critical patent/EP2372479B1/fr
Priority to DK10382075.9T priority patent/DK2372479T3/da
Priority to ES10382075T priority patent/ES2398205T3/es
Priority to US12/947,444 priority patent/US8295987B2/en
Priority to CN201110093501.5A priority patent/CN102208050B/zh
Publication of EP2372479A1 publication Critical patent/EP2372479A1/fr
Application granted granted Critical
Publication of EP2372479B1 publication Critical patent/EP2372479B1/fr
Revoked legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F03—MACHINES OR ENGINES FOR LIQUIDS; WIND, SPRING, OR WEIGHT MOTORS; PRODUCING MECHANICAL POWER OR A REACTIVE PROPULSIVE THRUST, NOT OTHERWISE PROVIDED FOR
    • F03D—WIND MOTORS
    • F03D17/00—Monitoring or testing of wind motors, e.g. diagnostics

Definitions

  • the subject matter described herein relates generally to monitoring wind turbines and, more particularly, to a system and method for comparing performance data for one or more wind turbines to performance data for other wind turbines and evaluating potential performance-enhancing upgrades.
  • Wind turbines utilize wind energy to generate or produce electrical power. Multiple wind turbines may be installed at a site to form a wind farm. To facilitate effective operation of a wind turbine, at least some known monitoring systems collect performance data from one or more wind turbines. An operator, for example, may review performance data for a particular wind turbine or a wind farm over time. However, such monitoring systems do not provide any indication of how the performance of a wind turbine or a wind farm compares to other wind turbines or wind farms. As a result, it may not be evident to an operator that a wind turbine or wind farm is operating at a performance level below its potential.
  • a system for indicating a performance of a wind turbine includes a database system for storing performance data for a plurality of known wind turbines.
  • the system also includes a server system coupled to the database system.
  • the server system is configured to acquire, from the database system, performance data corresponding to one or more target wind turbines to create target performance data.
  • the target wind turbines include a subset of the known wind turbines.
  • the server system is also configured to acquire, from the database system, performance data corresponding to one or more baseline wind turbines to create baseline performance data.
  • the baseline wind turbines include a subset of the known wind turbines that are not included in the target wind turbines.
  • the server system is further configured to provide, to a client system, a relative performance profile relating the target performance data to the baseline performance data.
  • a method for indicating a performance of a wind turbine includes acquiring performance data for one or more target wind turbines to create target performance data.
  • Baseline performance data are calculated by a processor based at least in part on performance data for a plurality of baseline wind turbines.
  • the target performance data are compared, by the processor, to the baseline performance data to create a relative performance profile.
  • a graphical representation of the relative performance profile is created for display by a user computer device.
  • a system for indicating a predicted performance improvement for an upgrade to a wind turbine includes a database system for storing performance data for a plurality of known wind turbines and a server system coupled to the database system.
  • the server system is configured to provide, to a client system, a relative performance profile relating performance data for a target wind turbine to performance data for one or more baseline wind turbines.
  • the server system is also configured to identify an available upgrade not included in the target wind turbine and to compare the performance data corresponding to the target wind turbine to performance data corresponding to one or more known wind turbines including the available upgrade to determine a predicted performance improvement.
  • the server system is further configured to provide the predicted performance improvement to the client system.
  • Fig. 1 is a perspective view of an exemplary wind turbine.
  • Fig. 2 is a block diagram illustrating an exemplary system for monitoring the wind turbine or multiple wind turbines as shown in Fig. 1 .
  • Fig. 3 is a block diagram illustrating an exemplary wind turbine controller for use with the system shown in Fig. 2 .
  • Fig. 4 is a block diagram illustrating an exemplary server computer device for use with the system shown in Fig. 2 .
  • Fig. 5 is a block diagram illustrating an exemplary user computer device for use with the system shown in Fig. 2 .
  • Fig. 6 is a flowchart of an exemplary method for indicating a performance of a wind turbine.
  • Fig. 7 is an exemplary user interface for providing a graphical representation of a relative performance profile for wind turbines at a wind turbine site of interest as shown in Fig. 2 .
  • Fig. 8 is an exemplary user interface for determining available upgrades for a wind turbine such as shown in Fig. 1 .
  • Fig. 9 is an exemplary user interface for viewing upgrade search results produced by initiating a search in the user interface shown in Fig. 8 .
  • Fig. 10 is an exemplary user interface for viewing an upgrade summary for an upgrade listed in the user interface shown in Fig. 9 .
  • the embodiments described herein facilitate comparative performance monitoring of one or more wind turbines of interest (referred to as “target wind turbines”) and evaluation of potential upgrades by providing a relative performance profile for the target wind turbines.
  • a relative performance profile describes performance of the target wind turbines in relation to performance of other wind turbines, referred to as “baseline wind turbines.”
  • the target wind turbines and the baseline wind turbines are intersecting or non-intersecting subsets of a population of known wind turbines.
  • An upgrade for a wind turbine may include, without limitation, a hardware component (e.g., a pitch control mechanism), a software component (e.g., control software), and/or a consumable component (e.g., a lubricant).
  • a relative performance profile includes and/or is based on target performance data corresponding to the target wind turbines and to baseline performance data corresponding to the baseline wind turbines.
  • performance data may include, without limitation, fault occurrence data, electrical output data, availability data, and/or any data describing operation of one or more wind turbines.
  • Fault occurrence data include, without limitation, an occurrence of an excessively high temperature ("overtemperature"), an occurrence of an excessive rotor speed (“overspeed”), an occurrence of a deviation between a desired operating parameter and an actual operating parameter (e.g., a pitch control deviation), and/or an occurrence of any condition deemed detrimental to operation of a wind turbine.
  • a wind turbine controller creates an operating condition value (e.g., based on a signal from a sensor) and transmits the operating condition value to a first server computer device, which transmits the operating condition value to a second server computer device.
  • the wind turbine controller, the first server computer device, and/or the second server computer device may calculate performance data based at least in part on the operating condition value.
  • An exemplary technical effect of the methods and systems described herein includes at least one of: (a) acquiring performance data for one or more target wind turbines to create target performance data; (b) calculating baseline performance data based at least in part on performance data for a plurality of baseline wind turbines; (c) comparing the target performance data to the baseline performance data to create a relative performance profile; and, (d) creating a graphical representation of the relative performance profile for display by a user computer device.
  • Fig. 1 is a perspective view of an exemplary wind turbine 100.
  • Wind turbine 100 includes a nacelle 102 that houses a generator (not shown in Fig. 1 ). Nacelle 102 is mounted on a tower 104 (only a portion of tower 104 is shown in Fig. 1 ).
  • Tower 104 may have any suitable height that facilitates operation of wind turbine 100 as described herein.
  • wind turbine 100 also includes a rotor 106 that includes three rotor blades 108 coupled to a rotating hub 110.
  • wind turbine 100 may include any number of rotor blades 108 that enable operation of wind turbine 100 as described herein.
  • wind turbine 100 includes a gearbox (not shown) that is rotatingly coupled to rotor 106 and to the generator.
  • wind turbine 100 includes one or more sensors 120 (shown in Figs. 2 and 3 ). Sensors 120 sense or detect wind turbine operating conditions.
  • sensor(s) 120 may include a turbine speed sensor, an electrical output sensor, an anemometer, a gear ratio sensor, and/or any sensor suitable for use with wind turbine 100.
  • Each sensor 120 is located according to its function.
  • an electrical output sensor may be positioned within nacelle 102 or tower 104, inline with or adjacent to an output cable coupled to the generator, such that the electrical output sensor detects a voltage, a current, and/or a power transmitted via the output cable.
  • Each sensor 120 generates and transmits one or more signals corresponding to a detected operating condition.
  • an electrical output sensor transmits a signal indicating a voltage, a current, and/or a power detected on an output cable.
  • each sensor 120 may transmit a signal continuously, periodically, or only once, for example, though other signal timings are also contemplated.
  • each sensor 120 may transmit a signal either in an analog form or in a digital form. Operation conditions and/or performance data may be created based on one or more sensor signals.
  • Fig. 2 is a block diagram illustrating an exemplary system 200 for monitoring one or more wind turbines 100.
  • System 200 includes a network 202.
  • network 202 may include, without limitation, the Internet, a local area network (LAN), a wide area network (WAN), a wireless LAN (WLAN), a mesh network, and/or a virtual private network (VPN).
  • System 200 also includes a client system 204, a server system 206, and a database system 208.
  • Client system 204 includes one or more user computer devices 210 and one or more server computer devices 215.
  • Server system 206 and database system 208 include one or more server computer devices 215.
  • System 200 also includes one or more wind turbine controllers 220.
  • User computer device 210, server computer device 215, and wind turbine controller 220 communicate with each other and/or network 202 using a wired network connection (e.g., Ethernet or an optical fiber), a wireless communication means, such as radio frequency (RF), an Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (e.g., 802.11(g) or 802.11(n)), the Worldwide Interoperability for Microwave Access (WIMAX) standard, a cellular phone technology (e.g., the Global Standard for Mobile communication (GSM)), a satellite communication link, and/or any other suitable communication means.
  • RF radio frequency
  • IEEE Institute of Electrical and Electronics Engineers
  • 802.11 e.g., 802.11(g) or 802.11(n)
  • WiX Worldwide Interoperability for Microwave Access
  • GSM Global Standard for Mobile communication
  • GSM Global Standard for Mobile communication
  • system 200 includes a first wind turbine site 230 and a second wind turbine site 235.
  • First wind turbine site 230 and second wind turbine site 235 each include a site network 240.
  • Wind turbine controllers 220 and, optionally, site server computer devices 245 are coupled in communication with network 202 via site networks 240.
  • one or more server computer devices 215 may be communicatively coupled to network 202 from a location other than a wind farm.
  • one or more central server computer devices 250 included in server system 206 are communicatively coupled to network 202.
  • central server computer device 250 may be located in a centralized monitoring and/or control facility.
  • Central server computer device 250 communicates with one or more site server computer devices 245 and/or one or more wind turbine controllers 220 at one or more wind turbine sites 230, 235. Such an embodiment facilitates monitoring multiple wind turbine sites 230, 235 from a remote location.
  • Database server computer device 255 includes a database 260 for storing wind turbine data, including, without limitation, wind turbine site attributes, wind turbine attributes, and/or wind turbine performance data.
  • Each of user computer device 210, server computer devices 215, and wind turbine controllers 220 includes a processor, as shown in Figs. 3-5 .
  • a processor may include a processing unit, such as, without limitation, an integrated circuit (IC), an application specific integrated circuit (ASIC), a microcomputer, a programmable logic controller (PLC), and/or any other programmable circuit.
  • a processor may include multiple processing units (e.g., in a multi-core configuration).
  • Each of user computer device 210, server computer device 215, and wind turbine controller 220 is configurable to perform the operations described herein by programming the corresponding processor.
  • a processor may be programmed by encoding an operation as one or more executable instructions and providing the executable instructions to the processor by embodying the executable instructions in a memory area (also shown in Figs. 3-5 ) coupled to the processor.
  • a memory area may include, without limitation, one or more random access memory (RAM) devices, one or more storage devices, and/or one or more computer readable media.
  • RAM random access memory
  • Client system 204, server system 206, and database system 208 each include one or more computer devices 214, 215.
  • Client system 204, server system 206, and database system 208 may be configured to operate as described herein by configuring and/or by programming computer devices 210, 215.
  • server system 206 may be considered coupled to network 202 because central server computer device 250 is coupled to network 202.
  • Fig. 3 is a block diagram illustrating an exemplary wind turbine controller 220 for use with system 200.
  • Wind turbine controller 220 includes a processor 305 for executing instructions.
  • instructions may be stored in a memory area 310, which is coupled to processor 305, to program processor 305.
  • Wind turbine controller 220 also includes a communication interface 315.
  • Communication interface 315 is configured to be coupled in communication with one or more remote devices, such as user computer device 210 and/or server computer devices 215.
  • communication interface 315 may be coupled in communication with a remote device via network 202.
  • wind turbine controller 220 includes one or more sensor interfaces 320.
  • Sensor interface 320 is configured to be coupled in communication with one or more sensors 120 of wind turbine 100.
  • Sensor interface 320 may be configured to receive one or more signals from each sensor 120.
  • wind turbine controller 220 receives one or more signals from sensor 120 via sensor interface 320 and processes the signal(s) by processor 305 to create one or more operating condition values.
  • processor 305 is programmed (e.g., with executable instructions in memory area 310) to sample a signal produced by sensor 120.
  • processor 305 may receive a continuous signal from sensor 120 and, in response, produce an operating condition value based on the continuous signal periodically (e.g., once every five seconds).
  • processor 305 normalizes a signal received from sensor 120.
  • an electrical output sensor may produce an analog signal with a parameter (e.g., voltage) that is directly proportional to a measured power output.
  • Processor 305 may be programmed to convert the analog signal to a power output value (e.g., expressed in kilowatts).
  • processor 305 is programmed to create performance data based at least in part on one or more operating condition values.
  • performance data may include operating condition values.
  • processor 305 may calculate performance data based on operating condition values.
  • processor 305 may calculate a hourly average power output based on operating condition values corresponding to a one-hour duration.
  • Processor 305 may be programmed to record performance data in memory area 310.
  • Wind turbine controller 220 may be configured to provide operating condition values and/or performance data to a remote device, such as server computer devices 215 or user computer device 210, via communication interface 315. In one embodiment, wind turbine controller 220 is configured to provide performance data to central server computer device 250.
  • connections are available between sensor interface 320 and sensor 120.
  • Such connections include, without limitation, an electrical conductor, a low-level serial data connection, such as Recommended Standard (RS) 232 or RS-485, a high-level serial data connection, such as Universal Serial Bus (USB) or Institute of Electrical and Electronics Engineers (IEEE) 1394 (a/k/a FIREWIRE), a parallel data connection, such as IEEE 1284 or IEEE 488, a short-range wireless communication channel such as BLUETOOTH, a private (e.g., accessible only inside or proximate to wind turbine 100) network connection, whether wired or wireless, and/or any other connection type suitable for carrying communication and/or data signals.
  • BLUETOOTH is a registered trademark of Bluetooth SIG, Inc., of Bellevue, Washington.
  • Fig. 4 is a block diagram illustrating an exemplary server computer device 215 for use with system 200.
  • Server computer device 215 includes a processor 405 for executing instructions. Instructions may be stored in a memory area 410, for example. Instructions may be provided for executing server applications including, without limitation, a wind turbine monitoring system, a wind turbine upgrade planning system, and/or database 260.
  • Processor 405 is operatively coupled to a communication interface 415 such that server computer device 215 is capable of communicating with a remote device, such as one or more user computer devices 210, wind turbine controllers 220, and/or other server computer devices 215.
  • Processor 405 may also be operatively coupled to a storage device 420.
  • Storage device 420 is any computer-operated hardware suitable for storing and/or retrieving data.
  • storage device 420 is integrated in server computer device 215.
  • server computer device 215 may include one or more hard disk drives as storage device 420.
  • storage device 420 is external to server computer device 215 and may be accessed by a plurality of server computer devices 215.
  • storage device 420 may include multiple storage units, such as hard disks or solid state disks, in a redundant array of inexpensive disks (RAID) configuration.
  • Storage device 420 may include a storage area network (SAN) and/or a network attached storage (NAS) system.
  • SAN storage area network
  • NAS network attached storage
  • processor 405 is operatively coupled to storage device 420 via a storage interface 425.
  • Storage interface 425 is any component capable of providing processor 405 with access to storage device 420.
  • Storage interface 425 may include, for example, an Advanced Technology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, a Small Computer System Interface (SCSI) adapter, a RAID controller, a SAN adapter, a network adapter, and/or any component providing processor 405 with access to storage device 420.
  • ATA Advanced Technology Attachment
  • SATA Serial ATA
  • SCSI Small Computer System Interface
  • Server computer device 215 may be configured to store wind turbine data in memory area 410 and/or storage device 425.
  • storage device 425 may include wind turbine site data and/or wind turbine data for a plurality of users 520.
  • Wind turbine site data include wind turbine site attributes, such as an identification attribute (e.g., a name), an operator attribute (e.g., an entity that operates the wind turbine site), a dimensional attribute (e.g., an area), a geographic attribute (e.g., a latitude, a longitude, and/or an elevation), a locale (e.g., a city and/or a country), and/or an environmental attribute.
  • an identification attribute e.g., a name
  • an operator attribute e.g., an entity that operates the wind turbine site
  • a dimensional attribute e.g., an area
  • a geographic attribute e.g., a latitude, a longitude, and/or an elevation
  • a locale e.g., a city and/or a country
  • environmental attribute e.g., a city and/or a country
  • Wind turbine data include wind turbine attributes, such as an identification attribute (e.g., a name), an operator attribute, a dimensional attribute (e.g., a rotor disc area and/or a tower height), a component attribute (e.g., a set of included components), an electrical output attribute (e.g., a maximum power output), a geographic attribute (e.g., a latitude, a longitude, and/or an elevation), and/or an environmental attribute.
  • Environmental attributes include, without limitation, temperature, humidity, salinity, and/or a wind condition, such as wind direction and/or wind speed.
  • Environmental attributes may be expressed as a yearly average, a seasonal average, a moving average, and/or any other form suitable for describing an operating environment of a wind turbine.
  • memory area 410 and/or storage device 425 is also configured to store performance data corresponding to a plurality of wind turbines 100.
  • Fig. 5 is a block diagram illustrating an exemplary user computer device 210 for use with system 200.
  • User computer device 210 includes a processor 505 for executing instructions.
  • executable instructions are stored in a memory area 510.
  • Memory area 510 is any device allowing information, such as executable instructions and/or other data, to be stored and retrieved.
  • User computer device 210 also includes at least one presentation device 515 for presenting information to user 520.
  • Presentation device 515 is any component capable of conveying information to user 520.
  • Presentation device 515 may include, without limitation, a display device (e.g., a liquid crystal display (LCD), organic light emitting diode (OLED) display, or "electronic ink” display) and/or an audio output device (e.g., a speaker or headphones).
  • presentation device 515 includes an output adapter, such as a video adapter and/or an audio adapter.
  • An output adapter is operatively coupled to processor 505 and configured to be operatively coupled to an output device, such as a display device or an audio output device.
  • user computer device 210 includes an input device 525 for receiving input from user 520.
  • Input device 525 may include, for example, a keyboard, a pointing device, a mouse, a stylus, a touch sensitive panel (e.g., a touch pad or a touch screen), a gyroscope, an accelerometer, a position detector, and/or an audio input device.
  • a single component, such as a touch screen, may function as both an output device of presentation device 515 and input device 525.
  • User computer device 210 also includes a communication interface 530, which is configured to be coupled in communication with network 202, server computer devices 215, and/or wind turbine controllers 220.
  • Stored in memory area 510 are, for example, computer readable instructions for providing a user interface to user 520 via presentation device 515 and, optionally, receiving and processing input from input device 525.
  • a user interface may include, among other possibilities, a web browser and/or a client application.
  • Web browsers and client applications enable users, such as user 520, to display and interact with media and other information from a remote device, such as server computer devices 215.
  • Exemplary client applications include, without limitation, a wind turbine monitoring and/or management application.
  • wind turbine controllers 220 and/or site server computer devices 245 are configured to record performance data corresponding to one or more known wind turbines 100.
  • site server computer devices 245 may be configured to acquire performance data for wind turbines 100 from wind turbine controllers 220 within a corresponding wind turbine site 230, 235.
  • Database server computer device 255 is configured to store the performance data for one or more known wind turbines 100.
  • database server computer device 255 is configured to receive the performance data from site server computer devices 245 and/or wind turbine controllers 220.
  • central server computer device 250 is configured to acquire the performance data from site server computer devices 245 and/or wind turbine controllers 220 and to store the acquired performance data in database 260 of database server computer device 255.
  • Database server computer device 255 may be configured to store performance data for a wind turbine site 230, 235 that is provided by site server computer device 245 and/or wind turbine controllers 220.
  • the site performance data may be included in target performance data and/or baseline performance data.
  • performance data corresponding to wind turbine sites 230, 235 may include performance data corresponding to individual wind turbines 100. If all wind turbines 100 within a wind turbine site 230, 235 are defined as target wind turbines, the site performance data may be used as the target performance data. If one wind turbine 100 within a wind turbine site 230, 235 is defined as a target wind turbine, the performance data corresponding to the individual wind turbine 100 may be used as the target performance data.
  • Target performance data and/or baseline performance data may include performance data corresponding to multiple wind turbine sites 230, 235.
  • database server computer device 255 is configured to store recent (e.g., generated in the previous day, the previous week, or the previous month) performance data for one or more wind turbines 100.
  • database server computer device 255 and/or central server computer device 250 may be configured to repeatedly acquire and store performance data for one or more wind turbines 100.
  • central server computer device 250 is configured to periodically acquire performance data from site server computer devices 245 and/or wind turbine controllers 220 and store the performance data in database 260.
  • central server computer device 250 may be configured to transmit a performance data request to a site server computer device 245 according to an interval, such as one minute, thirty minutes, one hour, or twenty-four hours.
  • the recent performance data may be included in target performance data and/or baseline performance data when creating a relative performance profile, as described in more detail below. Such embodiments facilitate comparative performance monitoring in real time or near real time.
  • Central server computer device 250 is configured to acquire, from database 260, performance data corresponding to one or more target wind turbines to create target performance data.
  • the target wind turbines include a subset of known wind turbines 100.
  • Central server computer device 250 is also configured to acquire, from database 260, performance data corresponding to one or more baseline wind turbines to create baseline performance data.
  • the baseline wind turbines include a subset of known wind turbines 100 that are not included in the target wind turbines.
  • the target performance data may correspond to first wind turbine site 230, and the baseline performance data may correspond to second wind turbine site 235.
  • the target wind turbines may or may not also be included in the baseline wind turbines.
  • the performance data are continually updated in database 260.
  • the target performance data and the baseline performance data reflect current and/or recent performance of the corresponding wind turbines 100.
  • the target wind turbines and/or baseline wind turbines may be defined at user computer device 210 by user 520.
  • input device 525 may be configured to receive a definition of target wind turbines and/or baseline wind turbines
  • communication interface 530 may be configured to transmit the definition of target wind turbines to central server computer device 250.
  • central server computer device 250 is configured to receive a definition of target wind turbines from client system 204 and to define the baseline wind turbines based on the definition of target wind turbines.
  • central server computer device 250 may be configured to identify known wind turbines 100 having at least one attribute that is substantially similar to an attribute of the target wind turbines. Attributes may include, without limitation, a geographic attribute and/or an environmental attribute.
  • central server computer device 250 may be configured to identify known wind turbines 100 having different (e.g., upgraded) components when compared to the target wind turbines. Such embodiments facilitate automatic selection and/or generation of baseline data for one or more target wind turbines, without requiring user 520 to determine which known wind turbines 100 are suitable for comparison to the target wind turbines.
  • Central server computer device 250 is further configured to provide, to client system 204, a relative performance profile relating the target performance data to the baseline performance data. For example, central server computer device 250 may be configured to compare the target performance data to the baseline performance data to create a relative performance profile for the target wind turbines.
  • Central server computer device 250 may also be configured to calculate target performance data and/or baseline performance data based at least in part on the performance data. In one embodiment, central server computer device 250 calculates the baseline performance data and stores the baseline performance data in database 260. In an alternative embodiment, central server computer device 250 calculates the baseline performance data dynamically (e.g., to create the relative performance profile) and subsequently discards and/or deletes the baseline performance data.
  • the performance data include fault occurrence data.
  • Central server computer device 250 is programmed to compare fault occurrence data from the target performance data with fault occurrence data from the baseline performance data to create the relative performance profile.
  • Other forms of performance data such as electrical output and availability, may also be compared to create the relative performance profile.
  • Central server computer device 250 may also be configured to create a graphical representation of the relative performance profile.
  • communication interface 415 is configured to transmit the relative performance profile and/or the graphical representation thereof to a remote device, such as user computer device 210.
  • communication interface 530 is configured to receive a graphical representation of a relative performance profile from a remote device, such as central server computer device 250.
  • Presentation device 515 is configured to display the graphical representation of the relative performance profile.
  • communication interface 530 is configured to receive the relative performance profile
  • processor 505 is programmed to create a graphical representation of the relative performance profile
  • presentation device 515 is configured to display the graphical representation of the relative performance profile.
  • the target performance data corresponds to wind turbines 100 at first wind turbine site 230.
  • central server computer device 250 may be configured to create the target performance data by selecting from database 260 the performance data corresponding to wind turbines 100 included in first wind turbine site 230.
  • Central server computer device 250 is further configured to calculate baseline performance data based at least in part on performance data corresponding to wind turbines 100 at second wind turbine site 235.
  • Central server computer device 250 is also configured to compare the target performance data to the baseline performance data to create a relative performance profile for first wind turbine site 230. Such an embodiment facilitates monitoring the performance of first wind turbine site 230 relative to the performance of second wind turbine site 235.
  • central server computer device 250 is configured to calculate, as the baseline performance data, an average performance metric based at least in part on a portion of the stored performance data.
  • An average performance metric may include, without limitation, an average fault occurrence rate, an average availability rate, and an average electrical output.
  • central server computer device 250 is also configured to calculate a target performance metric based at least in part on the target performance data.
  • the target performance metric corresponds to the average performance metric. For example, both the average performance metric and the target performance metric may indicate fault occurrence rates.
  • Central server computer device 250 is further configured to compare the target performance metric to the average performance metric to create the relative performance profile.
  • Central server computer device 250 is configured to create a graphical representation of the relative performance profile by creating a graphical representation of the target performance metric relative to the average performance metric.
  • processor 405 may be programmed to create a chart including the target performance metric and the average performance metric (e.g., in juxtaposition).
  • central server computer device 250 facilitates evaluating an upgrade to a component of one or more wind turbines 100.
  • Processor 405 is programmed to identify an available upgrade for a first target wind turbine of the target wind turbines. The first target wind turbine does not already include the available upgrade.
  • Processor 405 is also programmed to compare target performance data corresponding to the first target wind turbine to baseline performance data corresponding to one or more known wind turbines 100 that include the available upgrade to determine a predicted performance improvement. For example, a predicted performance improvement may be expressed as an increase in availability or a reduction in fault occurrences.
  • Central server computer device 250 is configured to provide the predicted performance improvement to client system 204 (e.g., via communication interface 415).
  • Fig. 6 is a flowchart of an exemplary method 600 for indicating a performance of a wind turbine, such as wind turbine 100, using an exemplary system as described herein.
  • Method 600 includes acquiring 610 performance data for one or more target wind turbines to create target performance data.
  • Baseline performance data are calculated 620 by a processor based at least in part on performance data for a plurality of baseline wind turbines.
  • the baseline wind turbines may be defined 615 by a user or automatically (e.g., by system 200 or central server computer device 250) based on one or more attributes of the target wind turbines.
  • the baseline wind turbines may be defined 615 by identifying known wind turbines having at least one attribute that is substantially similar to an attribute of the target wind turbines.
  • Baseline performance data may be calculated 620 based on performance data corresponding to the defined baseline wind turbines.
  • a wind turbine attribute may include, without limitation, a dimensional attribute (e.g., a rotor disc area and/or a tower height), a component attribute (e.g., a set of included hardware components, software components, and/or consumable components), an electrical output attribute (e.g., a maximum power output), a geographic attribute (e.g., a latitude, a longitude, and/or an elevation), and/or an environmental attribute (e.g., an average temperature and/or a wind condition).
  • Wind conditions include, for example, an average wind speed and/or an occurrence rate of wind in one or more directions.
  • the baseline wind turbines may be defined 615 based on one or more component attributes of the target wind turbines.
  • known wind turbines having components similar and/or equivalent to the components of the target wind turbines may be defined 615 as the baseline wind turbines.
  • known wind turbines having components that represent upgrades to the components of the target wind turbines are defined 615 as the baseline wind turbines.
  • the target performance data are compared 630, by the processor, to the baseline performance data to create a relative performance profile.
  • a graphical representation of the relative performance profile is created 640 for display by a user computer device.
  • the graphical representation of the relative performance profile is provided 660 to a remote device, such as user computer device 210.
  • the performance data include fault occurrence data.
  • Target fault occurrence data are compared 630 to baseline fault occurrence data to create the relative performance profile.
  • performance data are acquired 610 for wind turbines within one wind turbine site to create the target performance data.
  • the baseline performance data may be calculated 620 based on performance data for wind turbines within one or more wind turbine sites.
  • the target performance data are compared 630 to the baseline performance data to create a relative performance profile for the wind turbine site.
  • an available upgrade is identified 670 for a first target wind turbine that does not currently include the available upgrade.
  • Target performance data for the first target wind turbine are compared 680 to performance data for at least one known wind turbine that includes the available upgrade to determine a predicted performance improvement that may be achieved upon implementation of the available upgrade.
  • the wind turbines having the available upgrade may or may not be included in the baseline wind turbines.
  • the wind turbines with the available upgrade have at least one wind turbine attribute (e.g., a wind condition) that is substantially similar to a wind turbine attribute of the first target wind turbine.
  • the predicted performance improvement is provided 690 to a remote device, such as user computer device 210.
  • a remote device such as user computer device 210.
  • the availability of the first target wind turbine may be compared to the availability of the wind turbines including the available upgrade to determine an improvement in availability that would result from adding the available upgrade to the first target wind turbine.
  • Some embodiments facilitate determining an actual performance improvement achieved by an upgrade. For example, a user may implement an upgrade to one or more wind turbines based on a predicted performance improvement. After the upgrade is implemented, performance data for the upgraded wind turbine(s) is acquired 610 to create target performance data.
  • the baseline wind turbines may be defined 615 as the same set of wind turbines previously used to determine the predicted performance improvement. Alternatively, the baseline wind turbines may be defined 615 to include any other wind turbines based on one or more attributes of the upgraded wind turbine(s), as described above.
  • baseline performance data is calculated 620 from performance data for the upgraded wind turbine(s) prior to application of the upgrade.
  • the target performance data is compared 630 to the baseline performance data to create a relative performance profile that indicates an actual performance improvement achieved by implementing the upgrade.
  • a graphical representation of the relative performance profile may be created 640 and may be further provided 660 to a remote device.
  • the target wind turbines are associated with an operator attribute indicating that the target wind turbines are operated by a first operator.
  • the baseline performance data include and/or are based on performance data for at least one wind turbine operated by a second operator.
  • the baseline performance data may be calculated based on performance data corresponding to multiple operators.
  • baseline performance data are provided with no identifying information for the corresponding operators. Such an embodiment facilitates comparing performance of a target wind turbine or a wind turbine site to performance of wind turbines and/or wind turbine sites owned and/or operated by other entities while keeping wind turbine operation details for each operator confidential.
  • Method 600 may facilitate purchasing an upgrade for one or more wind turbines. For example, providing 690 the predicted performance improvement to a remote device may include providing an option to purchase the available upgrade. In some embodiments, multiple available upgrades for one or more wind turbines may be selected for purchase, and the selected upgrades may be purchased in a single operation.
  • Fig. 7 is an exemplary user interface 700 providing a graphical representation of a relative performance profile for wind turbines 100 at a wind turbine site of interest, such as first wind turbine site 230.
  • the relative performance profile includes, as performance metrics, unavailability of wind turbines 100 due to various fault occurrences.
  • User interface 700 may be displayed by user computer device 210, for example.
  • User interface 700 includes a title 702 indicating the wind turbine site of interest and a date range for which performance data are displayed.
  • User interface 700 also includes a bar chart 704 with an x-axis 706 and a y-axis 748.
  • Plotted on x-axis 706 is a plurality of fault conditions 710.
  • Plotted on y-axis 708 are unavailability (expressed as a percentage of time), denoted by graduations 712, and a quantity of affected turbines, denoted by graduations 714.
  • bar chart 704 For each fault condition 710, bar chart 704 includes an average unavailability indicator 720, a site unavailability indicator 722, and an affected turbines indicator 724. As shown in Fig. 7 , average unavailability indicator 720 and site unavailability indicator 722 are displayed as juxtaposed vertical bars. Affected wind turbines indicator 724 graphically represents a quantity of wind turbines 100 at the wind turbine site of interest that are associated with at least one occurrence of the corresponding fault condition.
  • Such an embodiment facilitates quickly comparing site performance to average performance and further facilitates identifying potentially beneficial upgrades. For example, an operator may determine, based on average unavailability indicator 720, site unavailability indicator 722, and/or affected wind turbines indicator 724, that an upgrade to pitch control components used at the wind turbine site of interest is desirable.
  • Fig. 8 is an exemplary user interface 800 for determining available upgrades for a wind turbine, such as wind turbine 100.
  • User 520 may interact with user interface 800 via user computer device 210.
  • information presented in user interface 800 may be customized for user 520.
  • user interface 800 may acquire wind turbine site data and/or wind turbine data for user 520 from user computer device 210 and/or server computer devices 215.
  • Model selector 804 includes a list of wind turbine models.
  • Country selector 806 includes a list of countries in which the wind turbine model selected in model selector 804 is available.
  • Frequency selector 808 includes a list of available electrical output frequencies.
  • user interface 800 includes a site selector 810 and a wind turbine selector 812.
  • Site selector 810 includes a list of wind turbine sites associated with user 520.
  • site selector 810 may include wind turbine sites operated by user 520.
  • Wind turbine selector 812 includes a list of wind turbines associated with the wind turbine site selected in site selector 810.
  • user interface 800 in response to user 520 selecting a wind turbine in wind turbine selector 812, user interface 800 automatically selects a model, a country, and/or a frequency corresponding to the selected wind turbine.
  • User interface 800 also includes a customer value selector 814.
  • Customer value selector 814 includes a list of benefit categories associated with available upgrades. For example, an upgrade such as a guardrail may be associated with a benefit category of "safety.”
  • User interface 800 also includes a component selector 816, a sub-component selector 818, and a supplier selector 820.
  • Component selector 816 includes a list of wind turbine components.
  • Sub-component selector 818 includes a list of sub-components for the component or components selected in component selector 816.
  • Supplier selector 820 includes a list of suppliers for the sub-component or sub-components selected in sub-component selector 818.
  • user interface 800 determines the lists of values within component selector 816, sub-component selector 818, and/or supplier selector 820 based at least in part on the values selected model selector 804, country selector 806, frequency selector 808, and/or customer value selector 814.
  • user 520 may interact with wind turbine diagram 822 to select one or more components and/or sub-components. For example, user 520 may select a position within wind turbine diagram 822 corresponding to a component. In response, user interface 800 may automatically select the corresponding component in component selector 816.
  • User interface 800 also includes a submit button 824. In response to user 520 engaging submit button 824, user interface 800 initiates a search for upgrades using the values selected in model selector 804, country selector 806, frequency selector 808, site selector 810, wind turbine selector 812, customer value selector 814, component selector 816, sub-component selector 818, and/or supplier selector 820 as search criteria.
  • Fig. 9 is an exemplary user interface 900 for viewing upgrade search results 902 produced by initiating a search in user interface 800.
  • Search results 902 may be produced, for example, by user computer device 210 or central server computer device 250.
  • Each search result 902 corresponds to an available upgrade.
  • an upgrade may include, without limitation, a hardware component, a software component, and/or a consumable component.
  • user interface 900 includes an upgrade name 904, an upgrade description 906, a wind turbine model 908, an electrical output frequency 910, and a country 912.
  • User interface also includes a summary link 914 and a datasheet link 916 for each search result 902.
  • user interface 900 initiates a download of detailed information for the corresponding upgrade.
  • user interface 900 displays an upgrade summary, as shown in Fig. 10 .
  • Fig. 10 is an exemplary user interface 1000 for viewing an upgrade summary for an upgrade listed in user interface 900.
  • User interface 1000 may be displayed for one or more wind turbines.
  • user interface 1000 may include information for a single wind turbine or all wind turbines within a wind turbine site.
  • User interface 1000 includes upgrade name 904, upgrade description 906, wind turbine model 908, electrical output frequency 910, and country 912.
  • User interface 1000 also includes performance data 1002 for a wind turbine and/or wind turbine site.
  • user interface 1000 includes a current availability 1004 for a wind turbine.
  • Current availability 1004 corresponds to target performance data, such as shown in Fig. 7 .
  • User interface 1000 also includes a predicted availability 1006.
  • predicted availability 1006 may be calculated based on performance data corresponding to wind turbines including the upgrade.
  • User interface also includes a performance improvement 1008 indicating the difference between predicted availability 1006 and current availability 1004.
  • User interface 1000 also graphically represents performance data 1002.
  • user interface 1000 includes a bar chart 1010 graphically representing current availability 1004 and predicted availability 1006.
  • Bar chart 1010 includes a y-axis 1012 corresponding to availability, expressed as a percentage of time.
  • Current availability 1004 is graphically represented as a current availability indicator 1014.
  • Predicted availability 1006 is graphically represented as a predicted availability indicator 1016. As shown in Fig. 10 , current availability indicator 1014 and predicted availability indicator 1016 are displayed as juxtaposed vertical bars. Such an embodiment facilitates convenient evaluation of a potential upgrade.
  • the methods described herein may be encoded as executable instructions embodied in a computer readable medium including, without limitation, a memory area of a computer device. Such instructions, when executed by a processor, cause the processor to perform at least a portion of the methods described herein.
  • Exemplary embodiments of a wind turbine monitoring system are described above in detail.
  • the system, devices, wind turbine, and included assemblies are not limited to the specific embodiments described herein, but rather each component may be utilized independently and separately from other components described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Sustainable Development (AREA)
  • Sustainable Energy (AREA)
  • Chemical & Material Sciences (AREA)
  • Combustion & Propulsion (AREA)
  • Mechanical Engineering (AREA)
  • General Engineering & Computer Science (AREA)
  • Wind Motors (AREA)

Claims (9)

  1. Système (200) d'indication d'un rendement d'une éolienne (100), le système comprenant :
    un système de base de données (208) pour stocker des données de rendement (1002) pour une pluralité d'éoliennes connues; et
    un système serveur (206) couplé au système de base de données, le système serveur (206) étant configuré pour :
    acquérir, à partir du système de base de données (208), des données de rendement correspondant à une ou plusieurs éoliennes cibles, afin de créer des données de rendement visées, les éoliennes cibles comprenant un sous-ensemble des éoliennes connues;
    acquérir, à partir du système de base de données (208), des données de rendement correspondant à une ou plusieurs éoliennes de base de référence, afin de créer des données de rendement de base de référence, les éoliennes de base de référence comprenant un sous-ensemble des éoliennes connues qui ne sont pas inclues dans les éoliennes cibles; et
    fournir, à un système client (204), un profil de rendement relatif, mettant en relation les données de rendement visées et les données de rendement de base de référence;
    caractérisé en ce que :
    le système serveur (206) est en outre configuré pour définir les éoliennes de base de référence, en identifiant les éoliennes (100) connues présentant au moins un attribut qui est sensiblement similaire à un attribut des éoliennes cibles, l'attribut, au nombre d'au moins un, comprenant au moins un des attributs suivants : un attribut géographique et un attribut environnemental.
  2. Système (200) selon la revendication 1, dans lequel le système serveur (206) est en outre configuré pour :
    identifier, pour une première éolienne cible (100) parmi les éoliennes cibles, une augmentation disponible de la capacité, non inclue dans la première éolienne cible;
    comparer les données de rendement visées, correspondant à la première éolienne cible, à des données de rendement de base de référence, correspondant à une éolienne connue, présentant l'augmentation disponible de la capacité, pour déterminer une amélioration de rendement prédite (1008); et
    fournir l'amélioration de rendement prédite au système client.
  3. Système (200) selon la revendication 1, dans lequel le système serveur (206) est en outre configuré pour :
    recevoir des données de rendement (1002) récentes, correspondant à une première éolienne (100) connue de la pluralité d'éoliennes connues; et
    stocker les données de rendement récentes dans le système de base de données (208),
    les données de rendement de base de référence comprenant les données de rendement récentes.
  4. Système (200) selon la revendication 3, dans lequel le système serveur (206) est en outre configuré pour recevoir de manière répétée et stocker des données de rendement (1002) récentes, correspondant à la première éolienne (100) connue.
  5. Système (200) selon la revendication 1, comprenant en outre :
    un dispositif d'ordinateur serveur de site (245) configuré pour recevoir des données de rendement de site pour une pluralité d'éoliennes (100) connues sur un site d'éoliennes (230, 235),
    le système serveur (206) étant en outre configuré pour :
    recevoir les données de rendement de site du dispositif d'ordinateur serveur de site; et
    stocker les données de rendement de site dans le système de base de données (208); et
    les données de rendement visées ou les données de rendement de base de référence englobant les données de rendement de site.
  6. Système (200) selon la revendication 5, dans lequel les données de rendement de site sont des premières données de rendement de site pour un premier site d'éoliennes (230), et le système serveur est en outre configuré pour :
    recevoir des deuxièmes données de rendement de site pour un deuxième site d'éoliennes (235); et
    comparer les premières données de rendement de site aux deuxièmes données de rendement de site, afin de créer le profil de rendement relatif.
  7. Système (200) selon la revendication 1, dans lequel les données de rendement (1002) comprennent des données d'apparition de défauts, et le système serveur (206) est en outre configuré pour comparer les données cibles d'apparition de défauts, à partir des données de rendement visées, avec les données d'apparition de défauts de base de référence, provenant des données de rendement de base de référence, afin de créer le profil de rendement relatif.
  8. Système (200) selon la revendication 1, dans lequel le système serveur (206) est en outre configuré pour fournir le profil de rendement relatif au système client (204), en produisant une représentation graphique du profil de rendement relatif.
  9. Système (200) selon la revendication 8, comprenant en outre le système client (204), le système client étant configuré pour visualiser la représentation graphique du profil de rendement relatif, en utilisant un dispositif de présentation (515).
EP10382075A 2010-03-31 2010-03-31 Systèmes et procédés pour la réalisation du suivi et de l'identification des améliorations pour éoliennes Revoked EP2372479B1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP10382075A EP2372479B1 (fr) 2010-03-31 2010-03-31 Systèmes et procédés pour la réalisation du suivi et de l'identification des améliorations pour éoliennes
DK10382075.9T DK2372479T3 (da) 2010-03-31 2010-03-31 Systemer og fremgangsmåder til effektovervågning og identificering af opgraderinger til vindmøller
ES10382075T ES2398205T3 (es) 2010-03-31 2010-03-31 Sistemas y procedimientos para la monitorización del rendimiento y la identificación de actualizaciones para turbinas eólicas
US12/947,444 US8295987B2 (en) 2010-03-31 2010-11-16 Systems and methods for performance monitoring and identifying upgrades for wind turbines
CN201110093501.5A CN102208050B (zh) 2010-03-31 2011-03-31 对风力涡轮机进行性能监测和识别升级的系统和方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP10382075A EP2372479B1 (fr) 2010-03-31 2010-03-31 Systèmes et procédés pour la réalisation du suivi et de l'identification des améliorations pour éoliennes

Publications (2)

Publication Number Publication Date
EP2372479A1 EP2372479A1 (fr) 2011-10-05
EP2372479B1 true EP2372479B1 (fr) 2012-11-28

Family

ID=42734757

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10382075A Revoked EP2372479B1 (fr) 2010-03-31 2010-03-31 Systèmes et procédés pour la réalisation du suivi et de l'identification des améliorations pour éoliennes

Country Status (5)

Country Link
US (1) US8295987B2 (fr)
EP (1) EP2372479B1 (fr)
CN (1) CN102208050B (fr)
DK (1) DK2372479T3 (fr)
ES (1) ES2398205T3 (fr)

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8977403B2 (en) 2011-06-22 2015-03-10 Mitsubishi Heavy Industries, Ltd. Remote monitoring apparatus, wind turbine generator system, and method of controlling remote monitoring apparatus
AU2011313837A1 (en) * 2011-06-22 2013-01-17 Mitsubishi Heavy Industries, Ltd. Remote monitoring apparatus, wind turbine generator system, and method of controlling remote monitoring apparatus
US8769345B2 (en) * 2011-07-29 2014-07-01 General Electric Company Computing device and methods of presenting data to identify faults within power systems
CN102621971B (zh) * 2012-04-17 2014-04-30 上海探能实业有限公司 一种保证风电机组正常运行的共享维护系统及其实现方法
CN102878015B (zh) * 2012-10-19 2014-12-10 国电南瑞科技股份有限公司 一种适用于风力发电机组的液压变桨系统控制柜
DK3077668T3 (da) * 2013-11-21 2020-10-26 Gen Electric System og metode til vurdering af ydeevneindvirkningerne af vindmølleopgraderinger
US9157415B1 (en) * 2014-03-21 2015-10-13 General Electric Company System and method of controlling an electronic component of a wind turbine using contingency communications
US9644612B2 (en) 2014-09-23 2017-05-09 General Electric Company Systems and methods for validating wind farm performance measurements
US10253758B2 (en) * 2014-09-23 2019-04-09 General Electric Company System and method for optimizing wind farm performance
US10100813B2 (en) 2014-11-24 2018-10-16 General Electric Company Systems and methods for optimizing operation of a wind farm
US10487804B2 (en) * 2015-03-11 2019-11-26 General Electric Company Systems and methods for validating wind farm performance improvements
US10712717B2 (en) 2015-05-15 2020-07-14 General Electric Company Condition-based validation of performance updates
CN104989602B (zh) * 2015-07-28 2017-11-03 太原理工大学 一种风力发电机状态远程监测装置
WO2017088877A1 (fr) 2015-11-26 2017-06-01 Vestas Wind Systems A/S Procédé de surveillance et d'évaluation des changements de performances énergétiques d'une éolienne
US10989173B2 (en) 2015-11-26 2021-04-27 Vestas Wind Systems A/S Method for assessing performance impact of a power upgrade
US10794366B2 (en) 2015-11-26 2020-10-06 Vestas Wind Systems A/S Method for monitoring and assessing power performance changes of a wind turbine
US11098698B2 (en) * 2016-04-07 2021-08-24 General Electric Company System and method for auto-calibrating a load sensor system of a wind turbine
US10385829B2 (en) 2016-05-11 2019-08-20 General Electric Company System and method for validating optimization of a wind farm
US10371124B2 (en) 2016-05-17 2019-08-06 General Electric Company System and method for determining wind farm wake loss
CN107524562A (zh) * 2016-06-22 2017-12-29 北京天诚同创电气有限公司 用于风力发电机组的程序升级方法及装置
US10260481B2 (en) 2016-06-28 2019-04-16 General Electric Company System and method for assessing farm-level performance of a wind farm
EP3336349B1 (fr) * 2016-12-14 2021-01-27 Siemens Wind Power A/S Procédé et système de configuration d'éoliennes
CN110168220B (zh) * 2016-12-30 2021-03-26 远景能源有限公司 一种评估风力涡轮机发电机性能的方法和系统
US10841176B2 (en) * 2017-03-30 2020-11-17 Siemens Wind Power A/S Systems and methods for managing a plurality of wind power plants
US10697439B2 (en) 2017-06-14 2020-06-30 General Electric Company Offset toggle method for wind turbine operation
US20200213315A1 (en) * 2017-07-30 2020-07-02 Windstack Ivs Method for Controlled Sharing of Wind Farms and Wind Turbines Data, Data Analysis Algorithms, and Results of Data Analysis
CN111164304A (zh) * 2017-09-27 2020-05-15 维斯塔斯风力系统集团公司 评估风力涡轮机软件升级的方法
US10815972B2 (en) * 2019-03-22 2020-10-27 General Electric Company System and method for assessing and validating wind turbine and wind farm performance
JP7196027B2 (ja) * 2019-07-04 2022-12-26 株式会社日立製作所 データ処理装置およびデータ処理方法
US11649804B2 (en) 2021-06-07 2023-05-16 General Electric Renovables Espana, S.L. Systems and methods for controlling a wind turbine

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7690840B2 (en) * 1999-12-22 2010-04-06 Siemens Energy, Inc. Method and apparatus for measuring on-line failure of turbine thermal barrier coatings
US20020029097A1 (en) * 2000-04-07 2002-03-07 Pionzio Dino J. Wind farm control system
US6925385B2 (en) * 2003-05-16 2005-08-02 Seawest Holdings, Inc. Wind power management system and method
US7013203B2 (en) * 2003-10-22 2006-03-14 General Electric Company Wind turbine system control
DE102004056254B4 (de) * 2004-11-22 2006-11-09 Repower Systems Ag Verfahren zum Optimieren des Betriebs von Windenergieanlagen
US8032614B2 (en) * 2006-04-30 2011-10-04 General Electric Company Method for configuring a windfarm network
US7840332B2 (en) * 2007-02-28 2010-11-23 General Electric Company Systems and methods for steam turbine remote monitoring, diagnosis and benchmarking
WO2009016020A1 (fr) * 2007-07-31 2009-02-05 Vestas Wind Systems A/S Système de surveillance d'éolienne
US20090192868A1 (en) * 2008-01-24 2009-07-30 Vrinda Rajiv Method and System for Analyzing Performance of a Wind Farm
US7908035B2 (en) * 2009-08-31 2011-03-15 General Electric Company System and method for wind formulary

Also Published As

Publication number Publication date
EP2372479A1 (fr) 2011-10-05
US8295987B2 (en) 2012-10-23
ES2398205T3 (es) 2013-03-14
CN102208050A (zh) 2011-10-05
US20110145277A1 (en) 2011-06-16
CN102208050B (zh) 2016-10-05
DK2372479T3 (da) 2013-02-04

Similar Documents

Publication Publication Date Title
EP2372479B1 (fr) Systèmes et procédés pour la réalisation du suivi et de l'identification des améliorations pour éoliennes
US9262371B2 (en) System for monitoring multiple building automation systems
US10210037B2 (en) Interface tool for asset fault analysis
EP2333329B1 (fr) Système, dispositif et procédé pour la surveillance acoustique et visuelle d'une éolienne
EP3252689A1 (fr) Procédé de surveillance de supervision de parc éolien
US8162788B2 (en) System, device and method for wind turbine control based on operating profiles
EP3252556A2 (fr) Système de surveillance de supervision de parc éolien
US11258855B2 (en) System and method for analyzing and monitoring smart meter network communications
JP2019516163A (ja) 予測モデルに基づいてアセット関連タスクを生成するコンピュータシステム及び方法
US20150066468A1 (en) Data acquisition system and a method of acquiring data from a wind turbine
TWI629495B (zh) 用於使用點觀測精緻化氣象預報之方法與系統
US20180012173A1 (en) Devices, methods, and systems for multi-user commissioning
CN102607850A (zh) 用于检测风力涡轮机中的异常的系统和方法
US9958291B1 (en) Self-service connection, data collection, and automation of metering and building systems, controls, and devices
US20190086452A1 (en) Systems and methods for managing resource consumption
US20190086234A1 (en) Systems and methods for displaying resource savings
US11710104B2 (en) Predictive data objects
Ko et al. Condition-based joint maintenance optimization for a large-scale system with homogeneous units
EP2339420A2 (fr) Système, dispositif et procédé de surveillance d'une éolienne à l'aide des indicateurs de qualité de données
JP2023541887A (ja) 農業用地中センサの異常検知および管理
EP2657916A2 (fr) Affichage de gestionnaire automatique d'équipement mobile
Smith Development of a generic wind farm SCADA system
AU2014284103A1 (en) Computer-implemented management of aids to navigation

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

AX Request for extension of the european patent

Extension state: AL BA ME RS

RIN1 Information on inventor provided before grant (corrected)

Inventor name: SUBRAMANIYAN, VENKATA

Inventor name: MORALES, ABRAHAM

Inventor name: GADRE, ANIRUDDHA

Inventor name: WAN, VALIKA

Inventor name: YAGHI, NIZAR

17P Request for examination filed

Effective date: 20120405

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602010003840

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G05B0023020000

Ipc: F03D0011000000

RIC1 Information provided on ipc code assigned before grant

Ipc: F03D 11/00 20060101AFI20120530BHEP

Ipc: G05B 23/02 20060101ALI20120530BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 586320

Country of ref document: AT

Kind code of ref document: T

Effective date: 20121215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010003840

Country of ref document: DE

Effective date: 20130124

REG Reference to a national code

Ref country code: DK

Ref legal event code: T3

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2398205

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20130314

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 586320

Country of ref document: AT

Kind code of ref document: T

Effective date: 20121128

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130328

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130301

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

PLBI Opposition filed

Free format text: ORIGINAL CODE: 0009260

26 Opposition filed

Opponent name: RWE INNOGY GMBH

Effective date: 20130821

Opponent name: VESTAS WIND SYSTEMS A/S

Effective date: 20130827

Opponent name: ENERCON GMBH

Effective date: 20130828

Opponent name: REPOWER SYSTEMS SE

Effective date: 20130827

PLAX Notice of opposition and request to file observation + time limit sent

Free format text: ORIGINAL CODE: EPIDOSNOBS2

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130331

REG Reference to a national code

Ref country code: DE

Ref legal event code: R026

Ref document number: 602010003840

Country of ref document: DE

Effective date: 20130821

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130331

PLAF Information modified related to communication of a notice of opposition and request to file observations + time limit

Free format text: ORIGINAL CODE: EPIDOSCOBS2

PLBB Reply of patent proprietor to notice(s) of opposition received

Free format text: ORIGINAL CODE: EPIDOSNOBS3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20140331

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140331

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140331

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140331

RDAF Communication despatched that patent is revoked

Free format text: ORIGINAL CODE: EPIDOSNREV1

APBM Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNO

APBP Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2O

APAH Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNO

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

APBQ Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3O

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130331

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20100331

PLAB Opposition data, opponent's data or that of the opponent's representative modified

Free format text: ORIGINAL CODE: 0009299OPPO

R26 Opposition filed (corrected)

Opponent name: VESTAS WIND SYSTEMS A/S

Effective date: 20130827

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121128

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

PLAB Opposition data, opponent's data or that of the opponent's representative modified

Free format text: ORIGINAL CODE: 0009299OPPO

R26 Opposition filed (corrected)

Opponent name: REPOWER SYSTEMS SE

Effective date: 20130827

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

APAH Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNO

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602010003840

Country of ref document: DE

Representative=s name: ZIMMERMANN & PARTNER PATENTANWAELTE MBB, DE

APBY Invitation to file observations in appeal sent

Free format text: ORIGINAL CODE: EPIDOSNOBA2O

APCA Receipt of observations in appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNOBA4O

PLAB Opposition data, opponent's data or that of the opponent's representative modified

Free format text: ORIGINAL CODE: 0009299OPPO

R26 Opposition filed (corrected)

Opponent name: SIEMENS GAMESA RENEWABLE ENERGY SERVICE GMBH

Effective date: 20130827

PLAB Opposition data, opponent's data or that of the opponent's representative modified

Free format text: ORIGINAL CODE: 0009299OPPO

REG Reference to a national code

Ref country code: DE

Ref legal event code: R103

Ref document number: 602010003840

Country of ref document: DE

Ref country code: DE

Ref legal event code: R064

Ref document number: 602010003840

Country of ref document: DE

APBU Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9O

R26 Opposition filed (corrected)

Opponent name: SENVION GMBH

Effective date: 20130827

RDAG Patent revoked

Free format text: ORIGINAL CODE: 0009271

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: PATENT REVOKED

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DK

Payment date: 20220218

Year of fee payment: 13

Ref country code: DE

Payment date: 20220217

Year of fee payment: 13

REG Reference to a national code

Ref country code: FI

Ref legal event code: MGE

27W Patent revoked

Effective date: 20211209

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20220217

Year of fee payment: 13

Ref country code: FR

Payment date: 20220221

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20220401

Year of fee payment: 13

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230530