EP3559764A2 - Distributed data analysis system for wind power plants background - Google Patents

Distributed data analysis system for wind power plants background

Info

Publication number
EP3559764A2
EP3559764A2 EP17872896.0A EP17872896A EP3559764A2 EP 3559764 A2 EP3559764 A2 EP 3559764A2 EP 17872896 A EP17872896 A EP 17872896A EP 3559764 A2 EP3559764 A2 EP 3559764A2
Authority
EP
European Patent Office
Prior art keywords
data
wind power
analysis system
power plant
data analysis
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.)
Granted
Application number
EP17872896.0A
Other languages
German (de)
French (fr)
Other versions
EP3559764B1 (en
Inventor
Anders Rhod GREGERSEN
Jan Krogh JENSEN
Mehran Nourbakhsh
Morten Tim THORSEN
Martin QVIST
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.)
Vestas Wind Systems AS
Original Assignee
Vestas Wind Systems AS
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
Application filed by Vestas Wind Systems AS filed Critical Vestas Wind Systems AS
Publication of EP3559764A2 publication Critical patent/EP3559764A2/en
Application granted granted Critical
Publication of EP3559764B1 publication Critical patent/EP3559764B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G05B23/0286—Modifications to the monitored process, e.g. stopping operation or adapting control
    • G05B23/0294—Optimizing process, e.g. process efficiency, product quality
    • 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
    • F03D7/00—Controlling wind motors 
    • 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
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B13/00—Adaptive control systems, i.e. systems automatically adjusting themselves to have a performance which is optimum according to some preassigned criterion
    • G05B13/02—Adaptive control systems, i.e. systems automatically adjusting themselves to have a performance which is optimum according to some preassigned criterion electric
    • G05B13/0205—Adaptive control systems, i.e. systems automatically adjusting themselves to have a performance which is optimum according to some preassigned criterion electric not using a model or a simulator of the controlled system
    • G05B13/024—Adaptive control systems, i.e. systems automatically adjusting themselves to have a performance which is optimum according to some preassigned criterion electric not using a model or a simulator of the controlled system in which a parameter or coefficient is automatically adjusted to optimise the performance
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Program-control systems
    • G05B19/02—Program-control systems electric
    • G05B19/04—Program control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Program control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0421—Multiprocessor system
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
    • G05B23/0224—Process history based detection method, e.g. whereby history implies the availability of large amounts of data
    • G05B23/0227—Qualitative history assessment, whereby the type of data acted upon, e.g. waveforms, images or patterns, is not relevant, e.g. rule based assessment; if-then decisions
    • G05B23/0237—Qualitative history assessment, whereby the type of data acted upon, e.g. waveforms, images or patterns, is not relevant, e.g. rule based assessment; if-then decisions based on parallel systems, e.g. comparing signals produced at the same time by same type systems and detect faulty ones by noticing differences among their responses
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/26—Pc applications
    • G05B2219/2619—Wind turbines

Definitions

  • Embodiments presented in this disclosure generally relate to techniques for analyzing wind turbine data from one or more wind power plants and determining operational parameter adjustments to be performed across wind power plants based on the analyzed data.
  • Wind turbines generally include a variety of sensors that are used to monitor operating parameters of a wind turbine. These sensors generally gather data about turbine components (e.g., turbine rotational speed, system temperature, blade pitch and yaw, power output), the turbine electrical system, weather data ⁇ e.g. , wind speed and direction), and so on.
  • turbine components e.g., turbine rotational speed, system temperature, blade pitch and yaw, power output
  • weather data ⁇ e.g. , wind speed and direction
  • the SCADA system generally provides systems for monitoring and processing data received from a wind turbine.
  • the SCADA system can display operations data for the wind turbines in a wind farm, for example, by requesting data from one or more wind turbines according to a pre-configured interval for each of the sensors and/or turbine data points that are to be monitored. Additionally, SCADA systems allow a technician to control a wind turbine by providing control signals to modify operating parameters ⁇ e.g. , maximum rotational speed, temperature settings, and so on).
  • SCADA systems are generally local to a single wind power plant and perform data analysis and parameter adjustment for the wind turbines in the wind power plant monitored by a SCADA system. Because SCADA systems generally gather operational data from wind turbines at a local wind power plant but may not be able to gather operational data from wind turbines at other wind power plants (even if the wind power plants are operated by the same operator), the data analysis and operational parameter adjustments performed by the SCADA system may not take into account conditions experienced by similar models of wind turbines across power plants. Additionally, the locality of data analysis and parameter adjustment to the wind power plant monitored by a SCADA system may not allow for a manufacturer of wind turbines to aggregate operational data from various operators for use in recommending changes to operational parameters to wind turbines installed by the various operators.
  • Embodiments of the present disclosure process wind turbine data in a distributed data analysis system.
  • the distributed data analysis system may be divided into a hierarchy of "zones" in which data analysis systems operate.
  • a wind power plant zone generally encompasses a single wind power plant and may be the location at which wind turbine data is initially gathered.
  • a wind power plant comprises a plurality of wind turbines and is also known as a wind park or a wind farm.
  • Regional zones may be positioned above wind power plant zones in the hierarchy of zones and may obtain data from multiple wind power plant zones (e.g., wind power plants) for analysis.
  • a regional zone may be established, for example, on a per-operator basis or on a geographical basis (e.g., a regional zone for wind power plants in a given state, province, or country).
  • a central zone generally is positioned above regional zones in the hierarchy and may receive wind turbine data from multiple wind power plants through one or more connected regional zones.
  • a central zone may be, for example, established by a wind turbine manufacturer to obtain and analyze data from wind power plants within a given country or across groups of countries.
  • One embodiment of the present disclosure is a method for processing wind turbine data in a distributed data analysis system.
  • the method generally includes obtaining, at a first data analysis system operational data from a plurality of wind turbines in a first wind power plant.
  • the first data analysis system determines one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data and pushes the one or more adjustments to the first wind power plant.
  • the first data analysis system further transmits the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant.
  • the second data analysis system transmits the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a central data analysis system.
  • the method advantageously allows for the distribution of data analysis and operational parameter adjustment across wind power plants owned by the same or different operators.
  • Bulk sensor data and other operational information may be obtained from wind turbines using a data acquisition system local to each wind power plant and forwarded to a data acquisition system in another data analysis zone (e.g., a regional or operator-specific data analysis zone).
  • the data acquisition systems installed in a regional or operator-specific data analysis zone can analyze data received from multiple wind power plants (e.g., on a per-wind turbine model basis) and identify, based on the received data, operational parameter changes to recommend to various operators of a specific model of wind turbine.
  • a wind power plant operator can obtain data analysis and changes to operational parameters for wind turbines based on conditions experienced across a larger fleet of wind turbines and, in some cases, across different operators of the same model of wind turbine.
  • FIG. 1 Another embodiment of the present disclosure is a computer program product comprising a computer-readable device having computer-readable program code embodied therewith, the computer-readable program code configured to perform an operation for processing wind turbine data in a distributed data analysis system.
  • the operation generally includes obtaining, at a first data analysis system operational data from a plurality of wind turbines in a first wind power plant.
  • the first data analysis system determines one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data and pushes the one or more adjustments to the first wind power plant.
  • the first data analysis system further transmits the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant.
  • the second data analysis system transmits the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a central data analysis system
  • the computer program product advantageously allows for the distribution of data analysis and operational parameter adjustment across wind power plants owned by the same or different operators.
  • Bulk sensor data and other operational information may be obtained from wind turbines using a data acquisition system local to each wind power plant and forwarded to a data acquisition system in another data analysis zone ⁇ e.g. , a regional or operator-specific data analysis zone).
  • the data acquisition system installed in a regional or operator-specific data analysis zone can analyze data received from multiple wind power plants (e.g. , on a per-wind turbine model basis) and identify, based on the received data, operational parameter changes to recommend to various operators of a specific model of wind turbine.
  • a wind power plant operator can obtain data analysis and changes to operational parameters for wind turbines based on conditions experienced across a larger fleet of wind turbines and, in some cases, across different operators of the same model of wind turbine.
  • Another embodiment of the present disclosure is a system comprising a processor and memory having instructions thereon configured to perform an operation for processing wind turbine data in a distributed data analysis system.
  • the operation generally includes obtaining, at a first data analysis system operational data from a plurality of wind turbines in a first wind power plant.
  • the first data analysis system determines one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data and pushes the one or more adjustments to the first wind power plant.
  • the first data analysis system further transmits the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant.
  • the second data analysis system transmits the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a central data analysis system.
  • the system advantageously allows for the distribution of data analysis and operational parameter adjustment across wind power plants owned by the same or different operators.
  • Bulk sensor data and other operational information may be obtained from wind turbines using a data acquisition system local to each wind power plant and forwarded to a data acquisition system in another data analysis zone (e.g., a regional or operator-specific data analysis zone).
  • the data acquisition systems installed in a regional or operator-specific data analysis zone can analyze data received from multiple wind power plants (e.g., on a per-wind turbine model basis) and identify, based on the received data, operational parameter changes to recommend to various operators of a specific model of wind turbine.
  • a wind power plant operator can obtain data analysis and changes to operational parameters for wind turbines based on conditions experienced across a larger fleet of wind turbines and, in some cases, across different operators of the same model of wind turbine.
  • Figure 1 illustrates an example distributed data acquisition and control system, according to an embodiment of the present disclosure.
  • Figure 2 illustrates an example data analysis system for obtaining and analyzing wind turbine data from a plurality of wind power plants, according to an embodiment of the present disclosure.
  • Figure 3 illustrates example operations that may be performed by a data analysis system to apply operational parameter adjustments to wind turbines installed in one or more wind power plants, according to an embodiment of the present disclosure.
  • Figure 4 illustrates example operations that may be performed by a data analysis system to recommend operational parameter adjustments to wind turbines installed in one or more wind power plants and provide the recommended adjustments to a customer for approval, according to an embodiment of the present disclosure.
  • Figure 5 illustrates an example data analysis system for wind turbine data, according to an embodiment of the present disclosure.
  • Embodiments presented herein provide techniques for collecting data from wind turbines in multiple wind power plants and generating adjustments to wind turbine operational parameters based on the data collected from multiple wind power plants.
  • data acquisition and control of wind turbines and/or wind power plants may be performed in a distributed data analysis system which may be structured into multiple zones in which data hubs may be deployed.
  • Data hubs may be implemented at the wind power plant (which may be referred to as a wind power plant zone) and in multiple zones encompassing multiple wind power plants ⁇ e.g. , regional zones which may be manufacturer-specific zones or linked to a specific geographic region) and central zones (which may be maintained by a wind turbine manufacturer to manage wind turbine installations across geographical regions and operators).
  • the data hubs installed at a wind power plant receive data from one or more wind turbines in the wind power plant (by periodically requesting sensor data from one or more wind turbines or asynchronously receiving data from one or more wind turbines in the wind power plant) and perform a power plant- specific analysis of the data.
  • the power plant-specific data analysis may allow for the wind power plant data hub to adjust, in real time (or close to real time) operational parameters for one or more wind turbines in the power plant.
  • the wind power plant data hubs can also establish connections with and forward the gathered sensor data to one or more regional data hubs.
  • the regional data hubs can aggregate sensor data from wind turbines in multiple wind power plants to identify, for example, operational trends and adjustments to be performed on wind turbines monitored by the connected wind power plant data hubs.
  • the regional data hubs can recommend operational parameter adjustments on a per-turbine model basis, and in some cases, the operational parameter adjustments may be forwarded to a customer-facing control center.
  • a wind power plant manager can view the recommended adjustments and determine whether or not to apply the recommended operational parameters to one or more wind turbines in the wind power plant.
  • a distributed data acquisition system can leverage operational information gathered from multiple wind power plants to optimize the performance of wind turbines across different operators and different wind power plant sites. Doing so allows for regional data analysis systems to obtain data from wind power plants without generating periodic requests for wind turbine data from multiple wind power plants, as data is generally gathered at a data hub local to each wind power plant and forwarded to regional data analysis systems. Additionally, operators can leverage operational data gathered across the wind power plants owned by the operator to optimize performance of wind power plants, and manufacturers of wind turbines can leverage operational data gathered from different installations to recommend adjustments to operational parameters (or generate updated default parameters) that can be applied as a "base" parameter set to wind turbines operated by different operators.
  • FIG. 1 illustrates an example zone-based data hub architecture for data acquisition and control of wind turbines and/or wind power plants, according to an embodiment.
  • zone-based data hub architecture 100 includes a power plant zone 102, a regional data analysis zone 104, and a central data analysis zone 106.
  • a regional analysis zone 104 may encompass a geographic area or may encompass wind power plants operated by a particular operator.
  • Central data analysis zone 106 may, in some cases, be implemented to allow manufacturers of wind turbines to obtain data from various wind turbine installations (e.g., from data forwarded to a data hub 1 10 3 in central data analysis zone 106 from a data hub 1 10 2 in regional data analysis zone 104).
  • a wind turbine manufacturer may maintain multiple central data analysis zones 106, for example, based on legal requirements that may restrict the export of data outside of national borders.
  • Power plant zone 102 generally encompasses a wind power plant and an associated data hub 1 10i .
  • power plant zone 102 includes data hub 1 10i and one or more wind turbines 1 16.
  • Each wind turbine 1 16 may be connected to data hub 1 10i (e.g., via a wired network connection and/or a wireless connection).
  • Each of the wind turbines 1 16 generally include a plurality of sensors that monitor various operating conditions within a wind turbine 1 16.
  • the sensors may include temperature sensors at various locations within a wind turbine 1 16, speed sensors used to monitor the rotational speed of various components within a wind turbine 1 16 (e.g., main shaft, gearbox components, and so on), vibration sensors, power production sensors, and so on.
  • the sensors may generate real-time data that may be, for example, buffered at each wind turbine 1 16.
  • the sensors can generate raw data as voltage outputs that can be correlated to an actual data point ⁇ e.g. , rotational speed in revolutions per minute, generated power in watts (or megawatts), component temperatures in degrees Celsius, and so on).
  • Data hub 1 10 ⁇ as illustrated, includes a data relay 1 12 and a data analysis system 1 14. Because data hub 1 10i is located within power plant zone 102, data hub 1 10i may be configured to request data from sensors at each wind turbine 1 16 in power plant zone 102 according, for example, to a schedule defined for each sensor installed in the wind turbine. For example, an internal rotational speed sensor for a gearbox in a wind turbine 1 16 may be pulled continuously or substantially continuously, while data from other sensors may be pulled with a lower periodicity. In some cases, data hub 1 10i may receive data generated by a wind turbine 1 16 in response to events that occur irregularly. For example, a wind turbine 1 16 may generate data based on alarms or events that occur during wind turbine operations.
  • An alarm may include, for example, gearbox overspeed or overheating events, and wind turbine 1 16 can, in some cases, buffer the generated alarms until data hub 1 10i requests information about generated alarms according to a schedule for requesting alarm data from wind turbines 1 16 in the wind power plant. In response, the wind turbine 1 16 can transmit an indication of the alarm, a timestamp, and the conditions that generated the alarm to data hub 1 10i .
  • data relay 1 12 When data hub 1 10i receives data from one or more wind turbines 1 16 in the wind power plant, data relay 1 12 generally forwards the data to data hubs in a regional zone 104 and/or central zone 106, according to a data forwarding configuration defined for data hub 1 10i.
  • the data forwarding policy may, for example, indicate a specific regional zone 104 that data hub 1 10i is to forward wind turbine operational data (or sensor data), such as a regional zone 104 associated with a specific wind power plant operator.
  • data hub 1 10 ! may convert the raw data to the actual data points before data relay 1 12 forwards the sensor data and/or other operational data to the data hubs in regional zone 104 and/or central zone 106.
  • Data analysis system 1 14 in data hub 1 10i generally receives the data obtained from wind turbines 1 16 and commits the received data to a data store in which data hub 1 10i saves historical data related to wind turbine operations at the wind power plant covered by power plant zone 102.
  • Data analysis system 1 14 may save the data, for example, in a searchable data store (e.g., a database), and each saved data point may be associated with a source wind turbine 1 16 and a timestamp.
  • data analysis system 1 14 may host a historical data viewer that allows an operator to view historical wind power plant data.
  • Data analysis system 1 14 can provide, for example, an overview screen that displays information about the health of wind turbines 1 16 in the wind power plant and instantaneous power generation readings for each wind turbine 1 16 in the wind power plant as well as additional screens that provide more granular details regarding the operating status of specific wind turbines 1 16 in the wind power plant.
  • data analysis system 1 14 may additionally include one or more data query screens that allow a technician to specify one or more operational data points gathered from wind turbines 1 16 in the wind power plant over a specified date range to view.
  • the data analysis system 1 14 may allow a technician or wind power plant operator to view and print the data in a tabular format and generate plots of the retrieved operational data to identify operational trends for one or more wind turbines 1 16 in the wind power plant.
  • data analysis system 1 14 can generate, for example, reports indicating operational trends in the wind power plant. Data analysis system 1 14 can periodically generate reports of operational trends in the wind power plant according to a configuration defined for data hub 1 10i. Additionally, data analysis system 1 14 provides a platform for deploying a variety of data analysis applications on data hub 1 10 ⁇ to identify operational issues in a wind power plant and perform real-time monitoring of wind turbines 1 16 in the wind power plant. In some cases, data analysis system 1 14 may include performance forecasting applications that obtain historical weather and wind speed data for a given tie period at a given location.
  • the performance forecasting applications can predict future performance of wind turbines 1 16 in the wind power plant and provide reports of the predicted performance to an operator of the wind power plant managed within power plant zone 102.
  • one or more applications installed in data analysis system 1 14 can use historical performance data gathered from wind turbines 1 16 installed in a wind power plant to identify performance trends of wind turbines in the wind power plant. Based on the performance trends identified from the historical data, data analysis system 1 14 can identify adjustments to perform to operational parameters applied to one or more wind turbines 1 16 in the wind power plant managed within power plant zone 102 and apply the adjustments to the one or more wind turbines.
  • regional zone 104 may host a data hub 1 10 2 and an action queue 120.
  • Regional zone 104 may be, for example, be structured as an operator- specific management zone that receives data from multiple power plant zones 102 operated by the same operator. By receiving data from multiple power plant zones 102, an operator can identify performance trends of wind turbines in different wind power plants and generate, for example, adjustments to wind turbine operational parameters that can be applied across different wind power plants.
  • Data relay 1 12 in data hub 1 10 2 is generally configured to receive data forwarded from one or more power plant zones 102 and commit the data to a historical data store. Data relay 1 12 additionally forwards the data received from the one or more power plant zones 102 to a data hub 1 10 3 in a central zone 106, where, as discussed herein, wind turbine data from various operators may be aggregated and analyzed (e.g. , by a manufacturer of the wind turbines) to identify and deploy recommended operational parameters across wind power plant operators. In some cases, data relay 1 12 in data hub 1 10 2 may forward data to a data hub 1 10 3 in a central zone 106 specified in a configuration file. The specified central zone may be selected, for example, based on restrictions on the export of technical data.
  • Data analysis system 1 14 in data hub 1 10 2 commits the received data to a data store in which data hub 1 10 2 saves historical data related to wind turbine operations at the one or more wind power plants that forward data to data hub 1 10 2 in regional zone 104.
  • Data analysis system 1 14 may save the received data, for example, in a searchable data store, and each data point received at data hub 1 10 2 and saved in the data store may be associated with an identifier of the source wind power plant, the source wind turbine 1 16, and a timestamp.
  • data analysis system 1 14 in data hub 1 10 2 may host, in some cases, a historical data view that allows an operator to view historical wind power data.
  • data analysis system 1 14 in data hub 1 10 2 may allow a technician or operator to compare operational data trends across wind power plants. To generate a comparison, data analysis system 1 14 may generate one or more reports (in tabular or graphical form) and, for example, indicate outliers or deviations from operational performance trends experienced across multiple wind power plants.
  • data analysis system 1 14 in data hub 1 10 2 can analyze the historical data and identify adjustments to perform to operational parameters applied to wind turbines in the one or more wind power plants that forward data to data hub 1 10 2 .
  • Data analysis system 1 14 can, in some cases, automatically push adjusted operational parameters to one or more wind power plants to apply the adjusted operational parameters to one or more identified wind turbines (e.g. , individual turbines, specific models of wind turbines, and so on).
  • data analysis system 1 14 can push the adjusted operational parameters to an action queue 120 in regional zone 104, where an operator can view the adjusted operational parameters (e.g., through a connection between action queue 120 and operator control center 140) and determine whether to apply the adjusted operational parameters to turbines in the wind power plants managed by the operator.
  • Data analysis system 1 14 may additionally host additional applications that use and process the data obtained from wind power plants, for example, to perform power generation forecasting, predict when maintenance may need to be performed on wind turbines in a wind power plant, predict wind turbine downtime, and so on.
  • central zone 106 may host a data hub 1 10 3 and an action generator 130.
  • Central zone 106 may be, for example, be managed by a manufacturer of wind turbines and be structured as a management zone that receives data from multiple power plant zones 102 operated by a variety of operators. By receiving data from multiple power plant zones 102, a manufacturer can identify performance trends of wind turbines in different wind power plants and generate adjustments to wind turbine operational parameters to optimize the performance of wind turbines operated by a variety of operators in a variety of locations. In some cases, a manufacturer may maintain multiple central zones 106 according to, for example, restrictions on data locality ⁇ e.g. , where or if technical data can be exported outside of national boundaries).
  • Data relay 1 12 in data hub 1 10 3 is generally configured to receive data forwarded from data hubs in one or more regional zones 104 and commit the data to a historical data store.
  • the data forwarded from data hubs in one or more regional zones 104 may include wind turbine operational data from multiple wind power plants operated by one or more operators.
  • Data analysis system 1 14 in data hub 1 10 3 commits the received data to a data store in which data hub 1 10 3 saves historical data related to wind turbine operations at wind power plants operated by a variety of operators.
  • Data analysis system 1 14 may save the received data, for example, in a searchable data store, and each data point received at data hub 1 10 3 and saved in the data store may be associated with an identifier of the source regional zone 104, the source wind power plant, the source wind turbine 1 16, and a timestamp.
  • data analysis system 1 14 in data hub 1 10 3 may host, in some cases, a historical data view that allows an operator to view historical wind power data.
  • data analysis system 1 14 in data hub 1 10 2 may allow a technician or operator to compare operational data trends across wind power plants (operated by the same or different operators) and/or across operators of wind power plants. To generate a comparison, data analysis system 1 14 may generate one or more reports (in tabular or graphical form) and, for example, indicate outliers or deviations from operational performance trends experienced across multiple wind power plants.
  • These reports may include, for example, statistical analyses of operational data that can identify operational conditions at specific turbines or wind power plants that are outliers from operational conditions across multiple wind power plants (e.g., identifying, after controlling for weather and wind speed, power plants that are producing multiple standard deviations more or less power on a per-turbine basis than the average per-turbine generated power across multiple wind power plants).
  • Data analysis system 1 14 in data hub 1 10 3 generally hosts a variety of applications that analyze the operational data received from one or more wind power plants ⁇ e.g. , sensor data from wind turbines, weather information, and so on). In some cases, applications hosted on data analysis system 1 14 can analyze the historical data and identify adjustments to perform to operational parameters applied to wind turbines across different wind power plants operated by different operators.
  • applications hosted on data analysis system 1 14 can analyze the historical data and identify adjustments to perform to operational parameters applied to wind turbines across different wind power plants operated by different operators.
  • data analysis system 1 14 in data hub 1 10 3 can generate a recommended or "default" set of operational parameters to apply to different models of wind turbines and push the operational parameters to action generator 130 for transmission to action queue 120 in one or more regional zones 104, where, as discussed above, recommended adjustments to wind turbine operating parameters may be stored and made available for wind power plant operators to view and determine whether to apply the recommended adjustments to one or more wind turbines.
  • the applications hosted by data analysis system 1 14 in data hub 1 10 3 may include forecasting tools that use and process the data obtained from wind power plants, for example, to perform power generation forecasting, predict when maintenance may need to be performed on wind turbines in a wind power plant, predict wind turbine downtime, and so on.
  • the forecasting tools can, for example, generate forecasts on a per-operator basis.
  • the applications hosted by data analysis system 1 14 in data hub 1 10 3 can identify performance differences and operational parameter differences between wind power plants operated by different operators. Based on the identified differences, data analysis system 1 14 can recommend changes to operational parameters applied to turbines operated by specific operators to optimize power generation, maintenance scheduling, and other performance parameters in the wind power plant.
  • Operator control center 140 is connected to action queue 120 in a regional zone 104 ⁇ e.g. , a customer management zone that analyzes data gathered from wind power plants operated by a common operator) and allows a wind power plant operator to view recommended actions to perform with respect to one or more wind turbines operated by a wind power plant operator.
  • Operator control center 140 can retrieve a list of recommended actions from action queue 120 and display information about each recommended action to an operator.
  • the information about each recommended action may include, for example, information about models of wind turbines (or specific wind turbines) for which the action is recommended, the actions to be performed, and information about why the action was recommended.
  • operator control center 140 transmits an indication to action queue 120 to to push instructions to implement the recommended actions to one or more wind turbines in wind power plants operated by the operator. If an operator declines to implement the recommended action, operator control center 140 can transmit instructions to action queue 120 to remove the recommended action from the action queue or move the recommended action to an archive of recommended actions. In some cases, operator control center 140 can additionally provide an interface that allows a wind power plant operator to view archived actions and subsequently choose to implement an archived action.
  • Figure 2 illustrates an example data analysis system 1 14, according to an embodiment.
  • data analysis system 1 14 includes an operational data analyzer 210, operational parameter generator 220, analysis applications 230, and a data adaptor 240.
  • Operational data analyzer 210 generally receives operational data, such as wind turbine sensor data, estimated power generation data, and so on, and environmental information (e.g. , wind speed, weather, and so on), from one or more wind power plants for analysis.
  • the amount of data operational data analyzer 210 receives for analysis may vary based on where data analysis system 1 14 is implemented.
  • a data analysis system 1 14 in data hub 1 10i located in a power plant zone 102 may receive data from wind turbines in the wind power plant covered by the power plant zone.
  • Data analysis systems 1 14 in data hubs deployed in regional (or operator-specific) zones 104 may receive data from wind turbines in multiple wind power plants operated by a specific operator.
  • Data analysis systems 1 14 in data hubs deployed in central zones 106 may receive data from wind turbines in multiple wind power plants operated by a variety of power plant operators.
  • operational data analyzer 210 can identify, for example, operational trends for each wind turbine (and/or each type of wind turbine) installed at one or more wind power plants.
  • the operational trends can indicate, for example, changes in power generation during time periods with similar weather conditions and wind speeds, trends related to component operating temperatures, and so on.
  • operational data analyzer 210 can use information about an alert generation frequency and/or alert criticality to determine trends in a wind power plant that indicate when maintenance and/or component replacement may be needed.
  • Operational parameter generator 220 uses the operational trends generated by operational data analyzer 210 to identify adjustments to perform to one or more wind turbine operating parameters. Operational parameter generator 220 may identify adjustments to wind turbine operating parameters on, for example, a per- wind-turbine basis or on a per-model basis. If data analysis system 1 14 is deployed in a regional zone 104, operational parameter generator 220 can identify adjustments to wind turbine operating parameters across different wind power plants (e.g. , a fleet- wide adjustment) or within particular wind power plants ⁇ e.g. , to improve wind turbine performance in wind power plants having lower performance (e.g., power generation relative to a target generated power) than other wind power plants).
  • operational parameter generator 220 can identify a "default" set of wind turbine operational parameters ⁇ e.g. , on a per- model basis).
  • data analysis system 1 14 in a central zone 106 may store information about operational parameters applied to wind turbines in different wind power plants and, based on the stored information and the identified "default" set of wind turbine operational parameters, operational parameter generator 220 can generate adjustments to be performed on wind turbine operational parameters at each wind power plant that transmits data to data hub 1 10 3 in central zone 106.
  • Applications 230 deployed in data analysis system 1 14 include data analysis and forecasting applications that can be used, for example, to perform power generation forecasting, predict when maintenance may need to be performed on wind turbines in a wind power plant, predict wind turbine downtime, and so on.
  • the applications 230 deployed in data analysis system 1 14 may be customized based on the location in which data analysis system is deployed. For example, forecasting applications may be deployed in data analysis systems 1 14 located in a power plant zone or regional zone (or operator-specific zone) to allow wind power plant operators to predict shortfalls or excess power generation capacity at one or more wind power plants.
  • Predictive analytics applications which can analyze operational data to identify, for example, equipment failure, required maintenance, and so on, may be hosted in data analysis systems 1 14 located in a power plant zone 102 or regional zone 104 to allow wind power plant operators to predict and plan for maintenance and outage events. Meanwhile, predictive analytics applications may be deployed in a data analysis system 1 14 located in a central zone 106 to allow wind turbine manufacturers to analyze time to failure and other predictive data points, which may identify components that should be redesigned to meet or exceed component longevity guarantees.
  • other predictive analytics applications may be deployed in a data analysis system 1 14 located in a central zone 106 to allow wind turbine manufacturers to monitor power generation information from a plurality of wind turbines and use the monitored data to identify, for example, if wind turbine components should be redesigned to meet or exceed power generation targets for different wind turbines.
  • Data adaptor 240 generally allows for data analysis and recommendations to be communicated between wind power plant operators and wind turbine manufacturers. As discussed above, data analysis and recommendations for service and operational changes may be generated by operational parameter generator 220 and/or other applications 230 deployed in data hub 1 10 3 located in a central zone 106 and transferred to action queues 120 in regional zone 104 via data adaptor 240. In some cases, data adaptor 240 can provide an interface to a satellite transceiver, wired network connection, or other network interfaces to transmit operational data recommendations to action queues 120 in regional zone 104.
  • FIG. 3 illustrates example operations that may be performed by a data hub 1 10 to generate adjustments to wind turbine operational parameters for one or more wind turbines in a wind power plant, according to an embodiment.
  • operations 300 begin at step 310, where data hub 1 10 receives wind turbine operational data from one or more wind power plants.
  • a data hub 1 10 installed in a power plant zone can request sensor data from one or more wind turbines in a wind power plant according to a schedule defined for each type of sensor installed in the wind turbines.
  • data hubs 1 10 can receive wind turbine operational data asynchronously.
  • a data hub 1 10 installed in a regional zone 104 can receive data pushed from a data hub 1 10 installed in a power plant zone 102 and can, in turn, push the received data to a data hub 1 10 installed in a central zone 106.
  • data hub 1 10 determines, based on the received wind turbine operational data, one or more adjustments to perform on operational parameters for one or more turbines in the one or more wind power plants.
  • the one or more adjustments may be determined, for example, on a per-wind-turbine basis or on a per-model basis.
  • Operational parameter adjustments to be performed on a per- turbine basis may be generated by data hubs 1 10 installed in a power plant zone 102 or a regional (operator-specific) zone 104, while per-model operational parameter adjustments may be generated by data hubs installed in a power plant zone 102, regional zone 104, or central zone 106.
  • data hub 1 10 pushes the adjusted operational parameters to the one or more wind power plants for application to one or more wind turbines.
  • operational parameter adjustments may be pushed to one or more wind turbines an applied automatically ⁇ e.g. , without needing an operator to review and determine whether to apply the adjustments).
  • adjustments to operational parameters generated by a data hub 1 10 installed in a regional zone 104 or a central zone 106 may be pushed to a power plant zone 102 for application to identified wind turbines in a wind power plant.
  • FIG. 4 illustrates example operations for generating recommended adjustments to wind turbine operational parameters, according to an embodiment.
  • operations 400 begin at step 410, where a data hub 1 10 aggregates operational data from a plurality of wind power plants for a first type of wind turbine.
  • a data hub 1 10 2 in a regional zone 104 can aggregate data from a plurality of wind power plants operated by a common operator, while a data hub 1 10 3 in a central zone 106 can aggregate data from wind power plants operated by different operators.
  • data hub 1 10 determines one or more operational parameter adjustments to perform on the first type of wind turbine.
  • data analysis applications deployed on data hub 1 10 can examine the data received from one or more wind power plants to identify, for example, performance trends for wind turbines in different wind power plants and identify outliers in the performance trends.
  • a data hub 1 10 can determine that performance trends for a first type of wind turbine deviate from trends common to other types of wind turbines (e.g., that average power generation for a first type of wind turbine does not scale with weather and/or wind speed in a similar manner to average power generation for other types of wind turbines).
  • data hub 1 10 can identify an "optimal" set of wind turbine operational parameters and adjustments to the operational parameters applied to the first type of wind turbine based on the "optimal" set of parameters.
  • data hub 1 10 pushes the parameter adjustments to operator control centers at each of the plurality of regional zones (or operator-specific zones) for operator review.
  • information about the determined parameter adjustments may be pushed to an action queue that an operator control center can connect to.
  • an operator can view the recommended adjustments to perform on one or more wind turbines in a wind power plant and determine whether to perform the identified adjustments on the specified wind turbines ⁇ e.g. , specific wind turbines or specific models of wind turbines).
  • Figure 5 illustrates an example data hub 500 that receives data from one or more wind turbines, forwards the received data to a data hub in a different management zone, and analyzes the received data to generate operational parameter adjustments to be performed on one or more wind turbines, according to an embodiment.
  • the data hub 500 includes, without limitation, a central processing unit (CPU) 502, one or more I/O device interfaces 504 which may allow for the connection of various I/O devices 514 to the data hub 500, network interface 506, a memory 508, storage 510, and an interconnect 512.
  • CPU central processing unit
  • CPU 502 may retrieve and execute programming instructions stored in the memory 508. Similarly, the CPU 502 may retrieve and store application data residing in the memory 508.
  • the interconnect 512 transmits programming instructions and application data, among the CPU 502, I/O device interface 504, network interface 506, memory 508, and storage 510.
  • CPU 502 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, and the like.
  • the memory 506 is included to be representative of a random access memory.
  • the storage 510 may be a disk drive.
  • the storage 510 may be a combination of fixed and/or removable storage devices, such as fixed disc drives, fixed solid state drives, removable memory cards or optical storage, network attached storage (NAS), or a storage area- network (SAN). In some cases, a number fixed storage devices may be combined into a logical storage device to provide fault tolerance for storage 510.
  • fixed disc drives such as fixed disc drives, fixed solid state drives, removable memory cards or optical storage
  • NAS network attached storage
  • SAN storage area- network
  • a number fixed storage devices may be combined into a logical storage device to provide fault tolerance for storage 510.
  • memory 508 includes a data relay 520 and a data analysis system 530.
  • Data relay 520 and data analysis system 530 may execute directly on data hub 500 or in a virtual machine hosted by a hypervisor executing on a computer system.
  • data relay 520 generally obtains data from one or more wind turbines and forwards the data to other data hubs in regional zones 104 and/or central zones 106.
  • data relay 520 in a data hub 500 deployed in a power plant zone 102 data relay 520 can periodically request or asynchronously receive sensor data and other operational data from one or more wind turbines or other external sources and forward the received data to a data hub 500 deployed in a regional zone 104.
  • a data hub 500 deployed in a regional zone 104 can asynchronously receive wind turbine operational data from one or more wind power plants and forward the data to a data hub deployed in a central zone 106.
  • Data analysis system 530 generally includes an operational data analyzer 532, operational parameter generator 534, applications 536, and data adaptor 538.
  • Operational data analyzer 532 receives wind turbine operational data from one or more wind power plants through data relay 520 for analysis.
  • the analysis may include, for example, identifying operational trends for each wind turbine and/or each model of wind turbine installed at one or more wind power plants.
  • the operational trends can indicate changes in power generated at different wind power plants during periods of similar weather conditions and wind speeds, trends in component operating temperatures, and so on.
  • Operational parameter generator 534 uses the operational data trends analyzed by operational data analyzer 532 and other wind turbine data to identify adjustments to perform to one or more wind turbine operating parameters. Operational parameter generator 534 may, as discussed above, identify adjustments to wind turbine operating parameters on a per-turbine basis or a per-turbine model basis and on a per-wind-farm, per-operator, or worldwide basis. The operational parameter adjustments may be established, for example, to optimize performance relative to a baseline (or expected) performance model. In some cases, operational parameter generator 534 can identify one or more wind power plants to use as a "model" or "target” power plant and can identify adjustments to perform to wind turbine operational parameters at other power plants based on differences between operational parameters established at the "model" power plant and the other power plants.
  • Applications 536 deployed in data analysis system 530 generally include data analysis and forecasting applications that can be customized for each operator or zone in which a data hub is deployed, according to embodiments.
  • the applications 536 may, for example, include forecasting applications that predict power generation, maintenance intervals, turbine downtime, and so on.
  • Data adaptor 538 provides an interface for data hub 500 to transmit and receive data analysis and operational parameter recommendations between wind power plant operators and wind turbine manufacturers.
  • Data adaptor 538 may include authentication and connection routines to establish connections with customer systems (e.g., operator control center 140) through one or more network interfaces 506 (e.g. , satellite transceivers, wired network connections, and so on).
  • customer systems e.g., operator control center 140
  • network interfaces 506 e.g. , satellite transceivers, wired network connections, and so on.
  • storage 510 includes a historical data repository 540.
  • Historical data repository 540 generally provides a location in which data hub 500 can store wind turbine operational data obtained from one or more wind turbines for use in future data analysis and operational parameter adjustments, as discussed herein.
  • historical data repository may be a database in which sensor data is stored and associated with source information.
  • the source information saved in historical data repository may vary based on a location in which data hub 500 is deployed. For example, if data hub 500 is deployed in a power plant zone 102, the source information may identify a specific wind turbine. If data hub 500 is deployed in a regional zone, the source information may identify a specific wind power plant and wind turbine. Meanwhile, if data hub 500 is deployed in a global zone, the source information may identify a wind turbine operator, a specific wind power plant, and a specific wind turbine.
  • aspects may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit,” “module,” or “system.”
  • aspects may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • General Physics & Mathematics (AREA)
  • Chemical & Material Sciences (AREA)
  • Combustion & Propulsion (AREA)
  • Mechanical Engineering (AREA)
  • General Engineering & Computer Science (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Sustainable Energy (AREA)
  • Sustainable Development (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Evolutionary Computation (AREA)
  • Medical Informatics (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Wind Motors (AREA)

Abstract

A method, controller, wind turbine, and computer program product are disclosed for processing and analyzing wind turbine operational data in a distributed data analysis system. An example method generally includes obtaining, at a first data analysis system, operational data from a plurality of wind turbines in a first wind power plant, determining adjustments to wind turbine operational parameters based on the operational data, pushing the adjustments to the first wind power plant, transmitting the operational data to a second data analysis system not located at the first wind power plant, and transmitting the operational data from the first wind power plant and atleast a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a global data analysis system.

Description

DISTRIBUTED DATA ANALYSIS SYSTEM FOR WIND POWER PLANTS
BACKGROUND
Field of the Invention
Embodiments presented in this disclosure generally relate to techniques for analyzing wind turbine data from one or more wind power plants and determining operational parameter adjustments to be performed across wind power plants based on the analyzed data.
Description of the Related Art
Wind turbines generally include a variety of sensors that are used to monitor operating parameters of a wind turbine. These sensors generally gather data about turbine components (e.g., turbine rotational speed, system temperature, blade pitch and yaw, power output), the turbine electrical system, weather data {e.g. , wind speed and direction), and so on. To allow a technician to monitor and control a wind turbine, the wind turbine generally provides data to a supervisory data acquisition and control (SCADA) system via a network connection. The SCADA system generally provides systems for monitoring and processing data received from a wind turbine. The SCADA system can display operations data for the wind turbines in a wind farm, for example, by requesting data from one or more wind turbines according to a pre-configured interval for each of the sensors and/or turbine data points that are to be monitored. Additionally, SCADA systems allow a technician to control a wind turbine by providing control signals to modify operating parameters {e.g. , maximum rotational speed, temperature settings, and so on).
SCADA systems are generally local to a single wind power plant and perform data analysis and parameter adjustment for the wind turbines in the wind power plant monitored by a SCADA system. Because SCADA systems generally gather operational data from wind turbines at a local wind power plant but may not be able to gather operational data from wind turbines at other wind power plants (even if the wind power plants are operated by the same operator), the data analysis and operational parameter adjustments performed by the SCADA system may not take into account conditions experienced by similar models of wind turbines across power plants. Additionally, the locality of data analysis and parameter adjustment to the wind power plant monitored by a SCADA system may not allow for a manufacturer of wind turbines to aggregate operational data from various operators for use in recommending changes to operational parameters to wind turbines installed by the various operators.
SUMMARY
Embodiments of the present disclosure process wind turbine data in a distributed data analysis system. As discussed herein, the distributed data analysis system may be divided into a hierarchy of "zones" in which data analysis systems operate. A wind power plant zone generally encompasses a single wind power plant and may be the location at which wind turbine data is initially gathered. A wind power plant comprises a plurality of wind turbines and is also known as a wind park or a wind farm. Regional zones may be positioned above wind power plant zones in the hierarchy of zones and may obtain data from multiple wind power plant zones (e.g., wind power plants) for analysis. A regional zone may be established, for example, on a per-operator basis or on a geographical basis (e.g., a regional zone for wind power plants in a given state, province, or country). A central zone generally is positioned above regional zones in the hierarchy and may receive wind turbine data from multiple wind power plants through one or more connected regional zones. A central zone may be, for example, established by a wind turbine manufacturer to obtain and analyze data from wind power plants within a given country or across groups of countries.
One embodiment of the present disclosure is a method for processing wind turbine data in a distributed data analysis system. The method generally includes obtaining, at a first data analysis system operational data from a plurality of wind turbines in a first wind power plant. The first data analysis system determines one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data and pushes the one or more adjustments to the first wind power plant. The first data analysis system further transmits the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant. The second data analysis system transmits the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a central data analysis system.
The method advantageously allows for the distribution of data analysis and operational parameter adjustment across wind power plants owned by the same or different operators. Bulk sensor data and other operational information may be obtained from wind turbines using a data acquisition system local to each wind power plant and forwarded to a data acquisition system in another data analysis zone (e.g., a regional or operator-specific data analysis zone). The data acquisition systems installed in a regional or operator-specific data analysis zone can analyze data received from multiple wind power plants (e.g., on a per-wind turbine model basis) and identify, based on the received data, operational parameter changes to recommend to various operators of a specific model of wind turbine. By pushing data from more local data acquisition systems to more geographically diverse data acquisition systems, a wind power plant operator can obtain data analysis and changes to operational parameters for wind turbines based on conditions experienced across a larger fleet of wind turbines and, in some cases, across different operators of the same model of wind turbine.
Another embodiment of the present disclosure is a computer program product comprising a computer-readable device having computer-readable program code embodied therewith, the computer-readable program code configured to perform an operation for processing wind turbine data in a distributed data analysis system. The operation generally includes obtaining, at a first data analysis system operational data from a plurality of wind turbines in a first wind power plant. The first data analysis system determines one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data and pushes the one or more adjustments to the first wind power plant. The first data analysis system further transmits the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant. The second data analysis system transmits the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a central data analysis system
The computer program product advantageously allows for the distribution of data analysis and operational parameter adjustment across wind power plants owned by the same or different operators. Bulk sensor data and other operational information may be obtained from wind turbines using a data acquisition system local to each wind power plant and forwarded to a data acquisition system in another data analysis zone {e.g. , a regional or operator-specific data analysis zone). The data acquisition system installed in a regional or operator-specific data analysis zone can analyze data received from multiple wind power plants (e.g. , on a per-wind turbine model basis) and identify, based on the received data, operational parameter changes to recommend to various operators of a specific model of wind turbine. By pushing data from more local data acquisition systems to more geographically diverse data acquisition systems, a wind power plant operator can obtain data analysis and changes to operational parameters for wind turbines based on conditions experienced across a larger fleet of wind turbines and, in some cases, across different operators of the same model of wind turbine.
Another embodiment of the present disclosure is a system comprising a processor and memory having instructions thereon configured to perform an operation for processing wind turbine data in a distributed data analysis system. The operation generally includes obtaining, at a first data analysis system operational data from a plurality of wind turbines in a first wind power plant. The first data analysis system determines one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data and pushes the one or more adjustments to the first wind power plant. The first data analysis system further transmits the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant. The second data analysis system transmits the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a central data analysis system.
The system advantageously allows for the distribution of data analysis and operational parameter adjustment across wind power plants owned by the same or different operators. Bulk sensor data and other operational information may be obtained from wind turbines using a data acquisition system local to each wind power plant and forwarded to a data acquisition system in another data analysis zone (e.g., a regional or operator-specific data analysis zone). The data acquisition systems installed in a regional or operator-specific data analysis zone can analyze data received from multiple wind power plants (e.g., on a per-wind turbine model basis) and identify, based on the received data, operational parameter changes to recommend to various operators of a specific model of wind turbine. By pushing data from more local data acquisition systems to more geographically diverse data acquisition systems, a wind power plant operator can obtain data analysis and changes to operational parameters for wind turbines based on conditions experienced across a larger fleet of wind turbines and, in some cases, across different operators of the same model of wind turbine.
BRIEF DESCRIPTION OF THE DRAWINGS
So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the disclosure, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this disclosure and are therefore not to be considered limiting of its scope, for the disclosure may admit to other equally effective embodiments.
Figure 1 illustrates an example distributed data acquisition and control system, according to an embodiment of the present disclosure. Figure 2 illustrates an example data analysis system for obtaining and analyzing wind turbine data from a plurality of wind power plants, according to an embodiment of the present disclosure.
Figure 3 illustrates example operations that may be performed by a data analysis system to apply operational parameter adjustments to wind turbines installed in one or more wind power plants, according to an embodiment of the present disclosure.
Figure 4 illustrates example operations that may be performed by a data analysis system to recommend operational parameter adjustments to wind turbines installed in one or more wind power plants and provide the recommended adjustments to a customer for approval, according to an embodiment of the present disclosure.
Figure 5 illustrates an example data analysis system for wind turbine data, according to an embodiment of the present disclosure.
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one embodiment may be beneficially utilized on other embodiments without specific recitation.
DESCRIPTION OF EXAMPLE EMBODIMENTS
Embodiments presented herein provide techniques for collecting data from wind turbines in multiple wind power plants and generating adjustments to wind turbine operational parameters based on the data collected from multiple wind power plants. As discussed herein, data acquisition and control of wind turbines and/or wind power plants may be performed in a distributed data analysis system which may be structured into multiple zones in which data hubs may be deployed. Data hubs may be implemented at the wind power plant (which may be referred to as a wind power plant zone) and in multiple zones encompassing multiple wind power plants {e.g. , regional zones which may be manufacturer-specific zones or linked to a specific geographic region) and central zones (which may be maintained by a wind turbine manufacturer to manage wind turbine installations across geographical regions and operators). The data hubs installed at a wind power plant receive data from one or more wind turbines in the wind power plant (by periodically requesting sensor data from one or more wind turbines or asynchronously receiving data from one or more wind turbines in the wind power plant) and perform a power plant- specific analysis of the data. The power plant-specific data analysis may allow for the wind power plant data hub to adjust, in real time (or close to real time) operational parameters for one or more wind turbines in the power plant. The wind power plant data hubs can also establish connections with and forward the gathered sensor data to one or more regional data hubs. The regional data hubs can aggregate sensor data from wind turbines in multiple wind power plants to identify, for example, operational trends and adjustments to be performed on wind turbines monitored by the connected wind power plant data hubs. In some cases, the regional data hubs can recommend operational parameter adjustments on a per-turbine model basis, and in some cases, the operational parameter adjustments may be forwarded to a customer-facing control center. At the customer-facing control center, a wind power plant manager can view the recommended adjustments and determine whether or not to apply the recommended operational parameters to one or more wind turbines in the wind power plant.
By implementing a hierarchical data hub model for collecting data from wind turbines and analyzing the collected data, a distributed data acquisition system can leverage operational information gathered from multiple wind power plants to optimize the performance of wind turbines across different operators and different wind power plant sites. Doing so allows for regional data analysis systems to obtain data from wind power plants without generating periodic requests for wind turbine data from multiple wind power plants, as data is generally gathered at a data hub local to each wind power plant and forwarded to regional data analysis systems. Additionally, operators can leverage operational data gathered across the wind power plants owned by the operator to optimize performance of wind power plants, and manufacturers of wind turbines can leverage operational data gathered from different installations to recommend adjustments to operational parameters (or generate updated default parameters) that can be applied as a "base" parameter set to wind turbines operated by different operators.
Figure 1 illustrates an example zone-based data hub architecture for data acquisition and control of wind turbines and/or wind power plants, according to an embodiment. As illustrated, zone-based data hub architecture 100 includes a power plant zone 102, a regional data analysis zone 104, and a central data analysis zone 106. As discussed herein, a regional analysis zone 104 may encompass a geographic area or may encompass wind power plants operated by a particular operator. Central data analysis zone 106 may, in some cases, be implemented to allow manufacturers of wind turbines to obtain data from various wind turbine installations (e.g., from data forwarded to a data hub 1 103 in central data analysis zone 106 from a data hub 1 102 in regional data analysis zone 104). In some cases, a wind turbine manufacturer may maintain multiple central data analysis zones 106, for example, based on legal requirements that may restrict the export of data outside of national borders.
Power plant zone 102 generally encompasses a wind power plant and an associated data hub 1 10i . As illustrated, power plant zone 102 includes data hub 1 10i and one or more wind turbines 1 16. Each wind turbine 1 16 may be connected to data hub 1 10i (e.g., via a wired network connection and/or a wireless connection). Each of the wind turbines 1 16 generally include a plurality of sensors that monitor various operating conditions within a wind turbine 1 16. For example, the sensors may include temperature sensors at various locations within a wind turbine 1 16, speed sensors used to monitor the rotational speed of various components within a wind turbine 1 16 (e.g., main shaft, gearbox components, and so on), vibration sensors, power production sensors, and so on. The sensors may generate real-time data that may be, for example, buffered at each wind turbine 1 16. In some cases, the sensors can generate raw data as voltage outputs that can be correlated to an actual data point {e.g. , rotational speed in revolutions per minute, generated power in watts (or megawatts), component temperatures in degrees Celsius, and so on).
Data hub 1 10^ as illustrated, includes a data relay 1 12 and a data analysis system 1 14. Because data hub 1 10i is located within power plant zone 102, data hub 1 10i may be configured to request data from sensors at each wind turbine 1 16 in power plant zone 102 according, for example, to a schedule defined for each sensor installed in the wind turbine. For example, an internal rotational speed sensor for a gearbox in a wind turbine 1 16 may be pulled continuously or substantially continuously, while data from other sensors may be pulled with a lower periodicity. In some cases, data hub 1 10i may receive data generated by a wind turbine 1 16 in response to events that occur irregularly. For example, a wind turbine 1 16 may generate data based on alarms or events that occur during wind turbine operations. An alarm may include, for example, gearbox overspeed or overheating events, and wind turbine 1 16 can, in some cases, buffer the generated alarms until data hub 1 10i requests information about generated alarms according to a schedule for requesting alarm data from wind turbines 1 16 in the wind power plant. In response, the wind turbine 1 16 can transmit an indication of the alarm, a timestamp, and the conditions that generated the alarm to data hub 1 10i .
When data hub 1 10i receives data from one or more wind turbines 1 16 in the wind power plant, data relay 1 12 generally forwards the data to data hubs in a regional zone 104 and/or central zone 106, according to a data forwarding configuration defined for data hub 1 10i. The data forwarding policy may, for example, indicate a specific regional zone 104 that data hub 1 10i is to forward wind turbine operational data (or sensor data), such as a regional zone 104 associated with a specific wind power plant operator. In some cases, if data hub 1 10i receives data from one or more wind turbines 1 16 as raw data (e.g. , voltage data), data hub 1 10! may convert the raw data to the actual data points before data relay 1 12 forwards the sensor data and/or other operational data to the data hubs in regional zone 104 and/or central zone 106.
Data analysis system 1 14 in data hub 1 10i generally receives the data obtained from wind turbines 1 16 and commits the received data to a data store in which data hub 1 10i saves historical data related to wind turbine operations at the wind power plant covered by power plant zone 102. Data analysis system 1 14 may save the data, for example, in a searchable data store (e.g., a database), and each saved data point may be associated with a source wind turbine 1 16 and a timestamp. In some cases, data analysis system 1 14 may host a historical data viewer that allows an operator to view historical wind power plant data. Data analysis system 1 14 can provide, for example, an overview screen that displays information about the health of wind turbines 1 16 in the wind power plant and instantaneous power generation readings for each wind turbine 1 16 in the wind power plant as well as additional screens that provide more granular details regarding the operating status of specific wind turbines 1 16 in the wind power plant. In some cases, data analysis system 1 14 may additionally include one or more data query screens that allow a technician to specify one or more operational data points gathered from wind turbines 1 16 in the wind power plant over a specified date range to view. The data analysis system 1 14 may allow a technician or wind power plant operator to view and print the data in a tabular format and generate plots of the retrieved operational data to identify operational trends for one or more wind turbines 1 16 in the wind power plant.
Based on the historical data, data analysis system 1 14 can generate, for example, reports indicating operational trends in the wind power plant. Data analysis system 1 14 can periodically generate reports of operational trends in the wind power plant according to a configuration defined for data hub 1 10i. Additionally, data analysis system 1 14 provides a platform for deploying a variety of data analysis applications on data hub 1 10Ί to identify operational issues in a wind power plant and perform real-time monitoring of wind turbines 1 16 in the wind power plant. In some cases, data analysis system 1 14 may include performance forecasting applications that obtain historical weather and wind speed data for a given tie period at a given location. Using the historical data and forecasted weather and wind speed data, the performance forecasting applications can predict future performance of wind turbines 1 16 in the wind power plant and provide reports of the predicted performance to an operator of the wind power plant managed within power plant zone 102. In some cases, one or more applications installed in data analysis system 1 14 can use historical performance data gathered from wind turbines 1 16 installed in a wind power plant to identify performance trends of wind turbines in the wind power plant. Based on the performance trends identified from the historical data, data analysis system 1 14 can identify adjustments to perform to operational parameters applied to one or more wind turbines 1 16 in the wind power plant managed within power plant zone 102 and apply the adjustments to the one or more wind turbines.
As illustrated, regional zone 104 may host a data hub 1 102 and an action queue 120. Regional zone 104 may be, for example, be structured as an operator- specific management zone that receives data from multiple power plant zones 102 operated by the same operator. By receiving data from multiple power plant zones 102, an operator can identify performance trends of wind turbines in different wind power plants and generate, for example, adjustments to wind turbine operational parameters that can be applied across different wind power plants.
Data relay 1 12 in data hub 1 102 is generally configured to receive data forwarded from one or more power plant zones 102 and commit the data to a historical data store. Data relay 1 12 additionally forwards the data received from the one or more power plant zones 102 to a data hub 1 103 in a central zone 106, where, as discussed herein, wind turbine data from various operators may be aggregated and analyzed (e.g. , by a manufacturer of the wind turbines) to identify and deploy recommended operational parameters across wind power plant operators. In some cases, data relay 1 12 in data hub 1 102 may forward data to a data hub 1 103 in a central zone 106 specified in a configuration file. The specified central zone may be selected, for example, based on restrictions on the export of technical data. Data analysis system 1 14 in data hub 1 102 commits the received data to a data store in which data hub 1 102 saves historical data related to wind turbine operations at the one or more wind power plants that forward data to data hub 1 102 in regional zone 104. Data analysis system 1 14 may save the received data, for example, in a searchable data store, and each data point received at data hub 1 102 and saved in the data store may be associated with an identifier of the source wind power plant, the source wind turbine 1 16, and a timestamp. As discussed above with respect to data hub 1 10^ data analysis system 1 14 in data hub 1 102 may host, in some cases, a historical data view that allows an operator to view historical wind power data. In some cases, because the historical wind power plant data saved in data hub 1 102 may encompass data from multiple wind power plants, data analysis system 1 14 in data hub 1 102 may allow a technician or operator to compare operational data trends across wind power plants. To generate a comparison, data analysis system 1 14 may generate one or more reports (in tabular or graphical form) and, for example, indicate outliers or deviations from operational performance trends experienced across multiple wind power plants.
In some cases, based on the historical data obtained from multiple wind power plants, data analysis system 1 14 in data hub 1 102 can analyze the historical data and identify adjustments to perform to operational parameters applied to wind turbines in the one or more wind power plants that forward data to data hub 1 102. Data analysis system 1 14 can, in some cases, automatically push adjusted operational parameters to one or more wind power plants to apply the adjusted operational parameters to one or more identified wind turbines (e.g. , individual turbines, specific models of wind turbines, and so on). In some cases, data analysis system 1 14 can push the adjusted operational parameters to an action queue 120 in regional zone 104, where an operator can view the adjusted operational parameters (e.g., through a connection between action queue 120 and operator control center 140) and determine whether to apply the adjusted operational parameters to turbines in the wind power plants managed by the operator. Data analysis system 1 14 may additionally host additional applications that use and process the data obtained from wind power plants, for example, to perform power generation forecasting, predict when maintenance may need to be performed on wind turbines in a wind power plant, predict wind turbine downtime, and so on.
As illustrated, central zone 106 may host a data hub 1 103 and an action generator 130. Central zone 106 may be, for example, be managed by a manufacturer of wind turbines and be structured as a management zone that receives data from multiple power plant zones 102 operated by a variety of operators. By receiving data from multiple power plant zones 102, a manufacturer can identify performance trends of wind turbines in different wind power plants and generate adjustments to wind turbine operational parameters to optimize the performance of wind turbines operated by a variety of operators in a variety of locations. In some cases, a manufacturer may maintain multiple central zones 106 according to, for example, restrictions on data locality {e.g. , where or if technical data can be exported outside of national boundaries).
Data relay 1 12 in data hub 1 103 is generally configured to receive data forwarded from data hubs in one or more regional zones 104 and commit the data to a historical data store. The data forwarded from data hubs in one or more regional zones 104 may include wind turbine operational data from multiple wind power plants operated by one or more operators.
Data analysis system 1 14 in data hub 1 103 commits the received data to a data store in which data hub 1 103 saves historical data related to wind turbine operations at wind power plants operated by a variety of operators. Data analysis system 1 14 may save the received data, for example, in a searchable data store, and each data point received at data hub 1 103 and saved in the data store may be associated with an identifier of the source regional zone 104, the source wind power plant, the source wind turbine 1 16, and a timestamp. As discussed above with respect to data hubs 1 10i and 1 102, data analysis system 1 14 in data hub 1 103 may host, in some cases, a historical data view that allows an operator to view historical wind power data. In some cases, because the historical wind power plant data saved in data hub 1 103 may encompass data from multiple wind power plants operated by various operators, data analysis system 1 14 in data hub 1 102 may allow a technician or operator to compare operational data trends across wind power plants (operated by the same or different operators) and/or across operators of wind power plants. To generate a comparison, data analysis system 1 14 may generate one or more reports (in tabular or graphical form) and, for example, indicate outliers or deviations from operational performance trends experienced across multiple wind power plants. These reports may include, for example, statistical analyses of operational data that can identify operational conditions at specific turbines or wind power plants that are outliers from operational conditions across multiple wind power plants (e.g., identifying, after controlling for weather and wind speed, power plants that are producing multiple standard deviations more or less power on a per-turbine basis than the average per-turbine generated power across multiple wind power plants).
Data analysis system 1 14 in data hub 1 103 generally hosts a variety of applications that analyze the operational data received from one or more wind power plants {e.g. , sensor data from wind turbines, weather information, and so on). In some cases, applications hosted on data analysis system 1 14 can analyze the historical data and identify adjustments to perform to operational parameters applied to wind turbines across different wind power plants operated by different operators. In some cases, data analysis system 1 14 in data hub 1 103 can generate a recommended or "default" set of operational parameters to apply to different models of wind turbines and push the operational parameters to action generator 130 for transmission to action queue 120 in one or more regional zones 104, where, as discussed above, recommended adjustments to wind turbine operating parameters may be stored and made available for wind power plant operators to view and determine whether to apply the recommended adjustments to one or more wind turbines. In some cases, the applications hosted by data analysis system 1 14 in data hub 1 103 may include forecasting tools that use and process the data obtained from wind power plants, for example, to perform power generation forecasting, predict when maintenance may need to be performed on wind turbines in a wind power plant, predict wind turbine downtime, and so on. The forecasting tools can, for example, generate forecasts on a per-operator basis. Using the per-operator forecasts, the applications hosted by data analysis system 1 14 in data hub 1 103 can identify performance differences and operational parameter differences between wind power plants operated by different operators. Based on the identified differences, data analysis system 1 14 can recommend changes to operational parameters applied to turbines operated by specific operators to optimize power generation, maintenance scheduling, and other performance parameters in the wind power plant.
Operator control center 140, as illustrated, is connected to action queue 120 in a regional zone 104 {e.g. , a customer management zone that analyzes data gathered from wind power plants operated by a common operator) and allows a wind power plant operator to view recommended actions to perform with respect to one or more wind turbines operated by a wind power plant operator. Operator control center 140 can retrieve a list of recommended actions from action queue 120 and display information about each recommended action to an operator. The information about each recommended action may include, for example, information about models of wind turbines (or specific wind turbines) for which the action is recommended, the actions to be performed, and information about why the action was recommended.
An operator can choose to implement the recommended action, and in response, operator control center 140 transmits an indication to action queue 120 to to push instructions to implement the recommended actions to one or more wind turbines in wind power plants operated by the operator. If an operator declines to implement the recommended action, operator control center 140 can transmit instructions to action queue 120 to remove the recommended action from the action queue or move the recommended action to an archive of recommended actions. In some cases, operator control center 140 can additionally provide an interface that allows a wind power plant operator to view archived actions and subsequently choose to implement an archived action.
Figure 2 illustrates an example data analysis system 1 14, according to an embodiment. As illustrated, data analysis system 1 14 includes an operational data analyzer 210, operational parameter generator 220, analysis applications 230, and a data adaptor 240.
Operational data analyzer 210 generally receives operational data, such as wind turbine sensor data, estimated power generation data, and so on, and environmental information (e.g. , wind speed, weather, and so on), from one or more wind power plants for analysis. The amount of data operational data analyzer 210 receives for analysis may vary based on where data analysis system 1 14 is implemented. For example, a data analysis system 1 14 in data hub 1 10i located in a power plant zone 102 may receive data from wind turbines in the wind power plant covered by the power plant zone. Data analysis systems 1 14 in data hubs deployed in regional (or operator-specific) zones 104 may receive data from wind turbines in multiple wind power plants operated by a specific operator. Data analysis systems 1 14 in data hubs deployed in central zones 106 may receive data from wind turbines in multiple wind power plants operated by a variety of power plant operators. Using the data obtained from the one or more wind turbines {e.g. , data forwarded from a data hub 1 10i in power plant zone 102 and/or data forwarded from a data hub 1 102 in regional zone 104), operational data analyzer 210 can identify, for example, operational trends for each wind turbine (and/or each type of wind turbine) installed at one or more wind power plants. The operational trends can indicate, for example, changes in power generation during time periods with similar weather conditions and wind speeds, trends related to component operating temperatures, and so on. In some cases, where operational data analyzer 210 receives information about alerts generated at one or more wind turbines, operational data analyzer 210 can use information about an alert generation frequency and/or alert criticality to determine trends in a wind power plant that indicate when maintenance and/or component replacement may be needed.
Operational parameter generator 220 uses the operational trends generated by operational data analyzer 210 to identify adjustments to perform to one or more wind turbine operating parameters. Operational parameter generator 220 may identify adjustments to wind turbine operating parameters on, for example, a per- wind-turbine basis or on a per-model basis. If data analysis system 1 14 is deployed in a regional zone 104, operational parameter generator 220 can identify adjustments to wind turbine operating parameters across different wind power plants (e.g. , a fleet- wide adjustment) or within particular wind power plants {e.g. , to improve wind turbine performance in wind power plants having lower performance (e.g., power generation relative to a target generated power) than other wind power plants). If data analysis system 1 14 is deployed in a central zone 106, operational parameter generator 220 can identify a "default" set of wind turbine operational parameters {e.g. , on a per- model basis). In some cases, data analysis system 1 14 in a central zone 106 may store information about operational parameters applied to wind turbines in different wind power plants and, based on the stored information and the identified "default" set of wind turbine operational parameters, operational parameter generator 220 can generate adjustments to be performed on wind turbine operational parameters at each wind power plant that transmits data to data hub 1 103 in central zone 106.
Applications 230 deployed in data analysis system 1 14 include data analysis and forecasting applications that can be used, for example, to perform power generation forecasting, predict when maintenance may need to be performed on wind turbines in a wind power plant, predict wind turbine downtime, and so on. The applications 230 deployed in data analysis system 1 14 may be customized based on the location in which data analysis system is deployed. For example, forecasting applications may be deployed in data analysis systems 1 14 located in a power plant zone or regional zone (or operator-specific zone) to allow wind power plant operators to predict shortfalls or excess power generation capacity at one or more wind power plants. Predictive analytics applications, which can analyze operational data to identify, for example, equipment failure, required maintenance, and so on, may be hosted in data analysis systems 1 14 located in a power plant zone 102 or regional zone 104 to allow wind power plant operators to predict and plan for maintenance and outage events. Meanwhile, predictive analytics applications may be deployed in a data analysis system 1 14 located in a central zone 106 to allow wind turbine manufacturers to analyze time to failure and other predictive data points, which may identify components that should be redesigned to meet or exceed component longevity guarantees. In some cases, other predictive analytics applications may be deployed in a data analysis system 1 14 located in a central zone 106 to allow wind turbine manufacturers to monitor power generation information from a plurality of wind turbines and use the monitored data to identify, for example, if wind turbine components should be redesigned to meet or exceed power generation targets for different wind turbines.
Data adaptor 240 generally allows for data analysis and recommendations to be communicated between wind power plant operators and wind turbine manufacturers. As discussed above, data analysis and recommendations for service and operational changes may be generated by operational parameter generator 220 and/or other applications 230 deployed in data hub 1 103 located in a central zone 106 and transferred to action queues 120 in regional zone 104 via data adaptor 240. In some cases, data adaptor 240 can provide an interface to a satellite transceiver, wired network connection, or other network interfaces to transmit operational data recommendations to action queues 120 in regional zone 104.
Figure 3 illustrates example operations that may be performed by a data hub 1 10 to generate adjustments to wind turbine operational parameters for one or more wind turbines in a wind power plant, according to an embodiment. As illustrated, operations 300 begin at step 310, where data hub 1 10 receives wind turbine operational data from one or more wind power plants. As discussed herein, a data hub 1 10 installed in a power plant zone can request sensor data from one or more wind turbines in a wind power plant according to a schedule defined for each type of sensor installed in the wind turbines. For data hubs 1 10 installed in a regional zone 104 or a central zone 106, data hubs 1 10 can receive wind turbine operational data asynchronously. As discussed above, a data hub 1 10 installed in a regional zone 104 can receive data pushed from a data hub 1 10 installed in a power plant zone 102 and can, in turn, push the received data to a data hub 1 10 installed in a central zone 106. At step 320, data hub 1 10 determines, based on the received wind turbine operational data, one or more adjustments to perform on operational parameters for one or more turbines in the one or more wind power plants. The one or more adjustments may be determined, for example, on a per-wind-turbine basis or on a per-model basis. Operational parameter adjustments to be performed on a per- turbine basis may be generated by data hubs 1 10 installed in a power plant zone 102 or a regional (operator-specific) zone 104, while per-model operational parameter adjustments may be generated by data hubs installed in a power plant zone 102, regional zone 104, or central zone 106. At step 330, data hub 1 10 pushes the adjusted operational parameters to the one or more wind power plants for application to one or more wind turbines. In some cases, where data hub 1 10 is installed in a power plant zone 102, operational parameter adjustments may be pushed to one or more wind turbines an applied automatically {e.g. , without needing an operator to review and determine whether to apply the adjustments). Meanwhile, adjustments to operational parameters generated by a data hub 1 10 installed in a regional zone 104 or a central zone 106 may be pushed to a power plant zone 102 for application to identified wind turbines in a wind power plant.
Figure 4 illustrates example operations for generating recommended adjustments to wind turbine operational parameters, according to an embodiment. As illustrated, operations 400 begin at step 410, where a data hub 1 10 aggregates operational data from a plurality of wind power plants for a first type of wind turbine. A data hub 1 102 in a regional zone 104 can aggregate data from a plurality of wind power plants operated by a common operator, while a data hub 1 103 in a central zone 106 can aggregate data from wind power plants operated by different operators.
At step 420, data hub 1 10 determines one or more operational parameter adjustments to perform on the first type of wind turbine. As discussed above, data analysis applications deployed on data hub 1 10 can examine the data received from one or more wind power plants to identify, for example, performance trends for wind turbines in different wind power plants and identify outliers in the performance trends. For example, a data hub 1 10 can determine that performance trends for a first type of wind turbine deviate from trends common to other types of wind turbines (e.g., that average power generation for a first type of wind turbine does not scale with weather and/or wind speed in a similar manner to average power generation for other types of wind turbines). Based on differences in the identified performance trends and information about operational parameters applied to wind turbines in different wind power plants, data hub 1 10 can identify an "optimal" set of wind turbine operational parameters and adjustments to the operational parameters applied to the first type of wind turbine based on the "optimal" set of parameters.
At step 430, data hub 1 10 pushes the parameter adjustments to operator control centers at each of the plurality of regional zones (or operator-specific zones) for operator review. As discussed above, information about the determined parameter adjustments may be pushed to an action queue that an operator control center can connect to. Through the operator control center, an operator can view the recommended adjustments to perform on one or more wind turbines in a wind power plant and determine whether to perform the identified adjustments on the specified wind turbines {e.g. , specific wind turbines or specific models of wind turbines). Figure 5 illustrates an example data hub 500 that receives data from one or more wind turbines, forwards the received data to a data hub in a different management zone, and analyzes the received data to generate operational parameter adjustments to be performed on one or more wind turbines, according to an embodiment. As shown, the data hub 500 includes, without limitation, a central processing unit (CPU) 502, one or more I/O device interfaces 504 which may allow for the connection of various I/O devices 514 to the data hub 500, network interface 506, a memory 508, storage 510, and an interconnect 512.
CPU 502 may retrieve and execute programming instructions stored in the memory 508. Similarly, the CPU 502 may retrieve and store application data residing in the memory 508. The interconnect 512 transmits programming instructions and application data, among the CPU 502, I/O device interface 504, network interface 506, memory 508, and storage 510. CPU 502 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, and the like. Additionally, the memory 506 is included to be representative of a random access memory. Furthermore, the storage 510 may be a disk drive. Although shown as a single unit, the storage 510 may be a combination of fixed and/or removable storage devices, such as fixed disc drives, fixed solid state drives, removable memory cards or optical storage, network attached storage (NAS), or a storage area- network (SAN). In some cases, a number fixed storage devices may be combined into a logical storage device to provide fault tolerance for storage 510.
As shown, memory 508 includes a data relay 520 and a data analysis system 530. Data relay 520 and data analysis system 530 may execute directly on data hub 500 or in a virtual machine hosted by a hypervisor executing on a computer system. As discussed, data relay 520 generally obtains data from one or more wind turbines and forwards the data to other data hubs in regional zones 104 and/or central zones 106. For a data relay 520 in a data hub 500 deployed in a power plant zone 102, data relay 520 can periodically request or asynchronously receive sensor data and other operational data from one or more wind turbines or other external sources and forward the received data to a data hub 500 deployed in a regional zone 104. A data hub 500 deployed in a regional zone 104 can asynchronously receive wind turbine operational data from one or more wind power plants and forward the data to a data hub deployed in a central zone 106.
Data analysis system 530, as illustrated, generally includes an operational data analyzer 532, operational parameter generator 534, applications 536, and data adaptor 538. Operational data analyzer 532 receives wind turbine operational data from one or more wind power plants through data relay 520 for analysis. The analysis may include, for example, identifying operational trends for each wind turbine and/or each model of wind turbine installed at one or more wind power plants. In some cases, the operational trends can indicate changes in power generated at different wind power plants during periods of similar weather conditions and wind speeds, trends in component operating temperatures, and so on.
Operational parameter generator 534 uses the operational data trends analyzed by operational data analyzer 532 and other wind turbine data to identify adjustments to perform to one or more wind turbine operating parameters. Operational parameter generator 534 may, as discussed above, identify adjustments to wind turbine operating parameters on a per-turbine basis or a per-turbine model basis and on a per-wind-farm, per-operator, or worldwide basis. The operational parameter adjustments may be established, for example, to optimize performance relative to a baseline (or expected) performance model. In some cases, operational parameter generator 534 can identify one or more wind power plants to use as a "model" or "target" power plant and can identify adjustments to perform to wind turbine operational parameters at other power plants based on differences between operational parameters established at the "model" power plant and the other power plants.
Applications 536 deployed in data analysis system 530 generally include data analysis and forecasting applications that can be customized for each operator or zone in which a data hub is deployed, according to embodiments. The applications 536 may, for example, include forecasting applications that predict power generation, maintenance intervals, turbine downtime, and so on.
Data adaptor 538 provides an interface for data hub 500 to transmit and receive data analysis and operational parameter recommendations between wind power plant operators and wind turbine manufacturers. Data adaptor 538 may include authentication and connection routines to establish connections with customer systems (e.g., operator control center 140) through one or more network interfaces 506 (e.g. , satellite transceivers, wired network connections, and so on).
As shown, storage 510 includes a historical data repository 540. Historical data repository 540 generally provides a location in which data hub 500 can store wind turbine operational data obtained from one or more wind turbines for use in future data analysis and operational parameter adjustments, as discussed herein. In some cases, historical data repository may be a database in which sensor data is stored and associated with source information. The source information saved in historical data repository may vary based on a location in which data hub 500 is deployed. For example, if data hub 500 is deployed in a power plant zone 102, the source information may identify a specific wind turbine. If data hub 500 is deployed in a regional zone, the source information may identify a specific wind power plant and wind turbine. Meanwhile, if data hub 500 is deployed in a global zone, the source information may identify a wind turbine operator, a specific wind power plant, and a specific wind turbine.
In the preceding, reference is made to embodiments presented in this disclosure. However, the scope of the present disclosure is not limited to specific described embodiments. Instead, any combination of the preceding features and elements, whether related to different embodiments or not, is contemplated to implement and practice contemplated embodiments. Furthermore, although embodiments disclosed herein may achieve advantages over other possible solutions or over the prior art, whether or not a particular advantage is achieved by a given embodiment is not limiting of the scope of the present disclosure. Thus, the preceding aspects, features, embodiments, and advantages are merely illustrative and are not considered elements or limitations of the appended claims except where explicitly recited in a claim(s). Likewise, reference to "the invention" shall not be construed as a generalization of any inventive subject matter disclosed herein and shall not be considered to be an element or limitation of the appended claims except where explicitly recited in a claim(s). As will be appreciated by one skilled in the art, the embodiments disclosed herein may be embodied as a system, method, or computer program product. Accordingly, aspects may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module," or "system." Furthermore, aspects may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments presented in this disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In view of the foregoing, the scope of the present disclosure is determined by the claims that follow.

Claims

WHAT IS CLAIMED IS:
1 . A method for processing wind turbine data in a distributed data analysis system, comprising:
obtaining, at a first data analysis system operational data from a plurality of wind turbines in a first wind power plant;
determining one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data;
pushing the one or more adjustments to the first wind power plant;
transmitting the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant; and
transmitting the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a global data analysis system.
2. The method of claim 1 , further comprising:
at the third data analysis system, determining one or more adjustments to perform to operational parameters applied to one or more wind turbines; and
pushing the one or more adjustments to an action queue in the second data analysis system.
3. The method of claim 2, further comprising:
transmitting the one or more adjustments in the action queue to an operator control center; and
upon receiving approval to apply the one or more adjustments to wind turbines in one or more wind power plants, pushing the one or more adjustments from the action queue in the second data analysis system to at least the first wind power plant.
4. The method of claim 1 , wherein determining one or more adjustments to perform to operational parameters of the plurality of wind turbines comprises determining one or more adjustments to perform for each type of wind turbine in the first wind power plant.
5. The method of claim 1 , wherein pushing the determined one or more adjustments to the first wind power plant comprises pushing the determined one or more adjustments to the plurality of wind turbines in the wind power plant.
6. The method of claim 1 , wherein pushing the determined one or more adjustments to the first wind power plant comprises pushing the determined one or more adjustments to a management system at the first wind power plant for approval by a wind power plant manager.
7. The method of claim 1 , wherein obtaining turbine operational data from the plurality of wind turbines in the first wind power plant comprises periodically requesting data from the one or more wind turbines.
8. The method of claim 1 , wherein transmitting at least the obtained turbine operational data to the second data analysis system comprises asynchronously transmitting at least the operational data to the second data analysis system.
9. A system, comprising:
a processor; and
a memory comprising instructions which, when executed by the processor, performs an operation for processing wind turbine data in a distributed data analysis system, the operation comprising:
obtaining, at a first data analysis system, operational data from a plurality of wind turbines in a first wind power plant;
determining one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data; pushing the one or more adjustments to the first wind power plant;
transmitting the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant; and
transmitting the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a global data analysis system.
10. The system of claim 9, wherein the operations further comprise:
at the third data analysis system, determining one or more adjustments to perform to operational parameters applied to one or more wind turbines; and
pushing the one or more adjustments to an action queue in the second data analysis system.
1 1 . The system of claim 10, wherein the operations further comprise:
transmitting the one or more adjustments in the action queue to an operator control center; and
upon receiving approval to apply the one or more adjustments to wind turbines in one or more wind power plants, pushing the one or more adjustments from the action queue in the second data analysis system to at least the first wind power plant.
12. The system of claim 9, wherein pushing the determined one or more adjustments to the first wind power plant comprises pushing the determined one or more adjustments to a management system at the first wind power plant for approval by a wind power plant manager.
13. The system of claim 9, wherein obtaining turbine operational data from one or more wind turbines in the first wind power plant comprises periodically requesting data from the plurality of wind turbines.
14. The system of claim 9, wherein transmitting at least the obtained turbine operational data to the second data analysis system comprises asynchronously transmitting at least the operational data to the second data analysis system.
15. A computer-readable medium comprising instructions which, when executed by one or more processors, performs an operation for processing wind turbine data in a distributed data analysis system, the operation comprising:
obtaining, at a first data analysis system, operational data from a plurality of wind turbines in a first wind power plant;
determining one or more adjustments to perform to operational parameters of one or more of the wind turbines based on the operational data;
pushing the one or more adjustments to the first wind power plant;
transmitting the operational data to a second data analysis system, wherein the first data analysis system is located at the first wind power plant and the second data analysis system comprises a regional data analysis system not located at the first wind power plant; and
transmitting the operational data from the first wind power plant and operational data from at least a second wind power plant to a third data analysis system, wherein the third data analysis system comprises a global data analysis system.
16. The computer-readable medium of claim 15, wherein the operations further comprise:
at the third data analysis system, determining one or more adjustments to perform to operational parameters applied to one or more wind turbines; and
pushing the one or more adjustments to an action queue in the second data analysis system.
17. The computer-readable medium of claim 16, wherein the operations further comprise: transmitting the one or more adjustments in the action queue to an operator control center; and
upon receiving approval to apply the one or more adjustments to wind turbines in one or more wind power plants, pushing the one or more adjustments from the action queue in the second data analysis system to at least the first wind power plant.
18. The computer-readable medium of claim 15, wherein pushing the determined one or more adjustments to the first wind power plant comprises pushing the determined one or more adjustments to a management system at the first wind power plant for approval by a wind power plant manager.
19. The computer-readable medium of claim 15, wherein obtaining turbine operational data from one or more wind turbines in the first wind power plant comprises periodically requesting data from the plurality of wind turbines.
20. The computer-readable medium of claim 15, wherein transmitting at least the obtained turbine operational data to the second data analysis system comprises asynchronously transmitting at least the operational data to the second data analysis system.
EP17872896.0A 2016-12-22 2017-11-24 Distributed data analysis system for wind power plants background Active EP3559764B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DKPA201671024 2016-12-22
PCT/DK2017/050392 WO2018113864A2 (en) 2016-12-22 2017-11-24 Distributed data analysis system for wind power plants background

Publications (2)

Publication Number Publication Date
EP3559764A2 true EP3559764A2 (en) 2019-10-30
EP3559764B1 EP3559764B1 (en) 2022-07-27

Family

ID=62624734

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17872896.0A Active EP3559764B1 (en) 2016-12-22 2017-11-24 Distributed data analysis system for wind power plants background

Country Status (3)

Country Link
US (1) US11053915B2 (en)
EP (1) EP3559764B1 (en)
WO (1) WO2018113864A2 (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018113864A2 (en) 2016-12-22 2018-06-28 Vestas Wind Systems A/S Distributed data analysis system for wind power plants background
US20230054705A1 (en) * 2017-08-31 2023-02-23 Energy Internet Corporation Software-defined modular energy system design and operation
US11345462B2 (en) * 2019-03-22 2022-05-31 Northrop Grumman Systems Corporation System control architecture monitoring system
US20210115901A1 (en) * 2019-10-18 2021-04-22 General Electric Company Systems and methods for optimizing scheduling of health checks for wind turbines during periods of low wind speeds
US11261846B2 (en) * 2019-11-01 2022-03-01 General Electric Company System and method for designing and operating a wind turbine power system based on statistical analysis of operational and/or grid data thereof
CN113984111A (en) * 2021-09-30 2022-01-28 北京华能新锐控制技术有限公司 Wind turbine control method and device based on external environment changes
CN115822894B (en) * 2022-12-13 2025-05-16 苏交控如东海上风力发电有限公司 An operation and maintenance method and system for offshore wind power equipment

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
WO2008086801A2 (en) 2007-01-15 2008-07-24 Vestas Wind Systems A/S A system and method for monitoring and control of wl-nd farms
WO2009016020A1 (en) 2007-07-31 2009-02-05 Vestas Wind Systems A/S Wind turbine monitoring system
EP2607690B1 (en) 2011-12-22 2017-06-14 Siemens Aktiengesellschaft Control system for a wind park
ES2428407B1 (en) * 2012-04-17 2014-09-16 Gamesa Innovation & Technology S.L System and procedure to configure, commission and control the operation of a wind power plant
US20130300115A1 (en) * 2012-05-08 2013-11-14 Johnson Controls Technology Company Systems and methods for optimizing power generation in a wind farm turbine array
US20140228976A1 (en) * 2013-02-12 2014-08-14 Nagaraja K. S. Method for user management and a power plant control system thereof for a power plant system
CA2810823A1 (en) 2013-03-28 2014-09-28 John Brandon Graham-Knight Method, system and apparatus for accessing and managing a plurality of wind turbines via a network
BR112015025412B1 (en) 2013-04-04 2022-02-08 General Electric Company MANAGEMENT SYSTEM AND METHOD PERFORMED BY THE MANAGEMENT SYSTEM
DK178241B1 (en) * 2013-06-17 2015-09-21 Wind Solutions As Kk Data communication system for a wind farm
US9845789B2 (en) 2014-10-23 2017-12-19 General Electric Company System and method for monitoring and controlling wind turbines within a wind farm
WO2016099558A1 (en) * 2014-12-19 2016-06-23 Hewlett Packard Enterprise Development Lp Automative system management
WO2016144297A1 (en) * 2015-03-06 2016-09-15 General Electric Company Automatic deployment of control code
KR101789923B1 (en) * 2016-06-02 2017-10-25 두산중공업 주식회사 Wind farm supervision monitoring method
US10247170B2 (en) * 2016-06-07 2019-04-02 General Electric Company System and method for controlling a dynamic system
WO2018113864A2 (en) 2016-12-22 2018-06-28 Vestas Wind Systems A/S Distributed data analysis system for wind power plants background

Also Published As

Publication number Publication date
WO2018113864A2 (en) 2018-06-28
US20200095979A1 (en) 2020-03-26
WO2018113864A3 (en) 2018-09-07
US11053915B2 (en) 2021-07-06
EP3559764B1 (en) 2022-07-27

Similar Documents

Publication Publication Date Title
US11053915B2 (en) Distributed data analysis system for wind power plants background
EP3440349B1 (en) Data collection system for wind turbine data
US11470157B2 (en) Cloud gateway for industrial automation information and control systems
US11499734B2 (en) Cloud and edge integrated energy optimizer
EP3037901B1 (en) Cloud-based emulation and modeling for automation systems
US10656627B2 (en) Managing big data in process control systems
US9218000B2 (en) System and method for cloud computing
EP2660667B1 (en) Cloud gateway for industrial automation information and control systems
EP1958738B1 (en) Remote diagnostic system for robots
KR101789923B1 (en) Wind farm supervision monitoring method
CN104950837A (en) Cloud manifest configuration management system
KR20160017681A (en) System and method for managing wind plant
EP2414904A2 (en) Cloud computing as a basis for equipment health monitoring service
US11774124B2 (en) Systems and methods for managing building signature intelligent electronic devices
CN115963775B (en) PLC state monitoring system and method based on characteristic signal data
JP7728801B2 (en) Method for predictive maintenance of automated machines for manufacturing or packaging consumer products
CN112950401A (en) Method, device and system for managing factory resource consumption
CN109542079A (en) Information Collection System, system collect mediation device, information collects Intermediary method and recording medium
CN120928829A (en) Inspection system, method, equipment, storage medium and program product for wind power plant
CN121585930A (en) A Real-Time Monitoring Method for Underground Equipment in Coal Mines Based on Mining Systems
WO2014133762A1 (en) Ambient conditions monitoring system for machinery

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190710

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL 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 RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210219

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20220413

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): AL 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 RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602017060021

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1507472

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220815

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20220727

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

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: 20220727

Ref country code: RS

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: 20220727

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: 20221128

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: 20221027

Ref country code: NL

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: 20220727

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: 20220727

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: 20220727

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: 20220727

Ref country code: ES

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: 20220727

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1507472

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220727

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

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: 20220727

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: 20221127

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: 20220727

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: 20221028

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: 20220727

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: 20220727

Ref country code: DK

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: 20220727

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: 20220727

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: 20220727

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602017060021

Country of ref document: DE

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

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: 20220727

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: 20220727

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

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

Effective date: 20230521

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220727

Ref country code: AL

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: 20220727

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

26N No opposition filed

Effective date: 20230502

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20221130

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

Ref country code: LI

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

Effective date: 20221130

Ref country code: CH

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

Effective date: 20221130

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

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: 20220727

Ref country code: LU

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

Effective date: 20221124

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: 20221124

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

Ref country code: BE

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

Effective date: 20221130

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

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: 20171124

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: 20220727

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

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: 20220727

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: 20220727

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: 20220727

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

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: 20220727

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: 20220727

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

Ref country code: DE

Payment date: 20251126

Year of fee payment: 9

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

Ref country code: GB

Payment date: 20251125

Year of fee payment: 9

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

Ref country code: FR

Payment date: 20251124

Year of fee payment: 9