Onshore Wind Turbine Condition-Monitoring Data Under the EU Data Act
Condition-monitoring systems produce an onshore turbine maintenance record: temperatures, vibration, operating states, alarms, timestamps and other signals show component behaviour between visits. The EU Data Act can make some readily available product data easier for an eligible user to access or share with an independent provider. It does not turn every OEM dashboard, diagnosis or predictive model into a free deliverable. This is practical guidance for owners, operators and planners, not legal advice. Apply the Regulation to the actual turbine, contracts and data architecture. The legal starting point is Regulation (EU) 2023/2854, the Data Act.
What the Data Act changes for an onshore turbine
The Data Act is an access-and-use framework, not a blanket declaration of ownership over every digital record. For Chapter II, a user of a connected product can access the raw or pre-processed data generated by using it when that data is readily available to the data holder. The user can also ask the data holder to make that data available to a third party of the user's choice. For a land-based turbine, this can support maintenance planning, condition review and aftermarket competition, including predictive maintenance planning, when the requested fields and roles fit the Regulation. The Commission's overview describes the Data Act's wider objective and its application to industrial equipment in its current Data Act policy page.
| Date | What changes | Practical boundary |
|---|---|---|
| 11 January 2024 | The Regulation entered into force. | Entry into force is not the same as the general application date. |
| 12 September 2025 | The Data Act applies; Chapter IV covers contracts concluded after this date. | Product-design duties have their own later transition. |
| After 12 September 2026 | Article 3(1) applies to connected products and related services placed on the EU market after this date. | This is a design obligation, not general permission to withhold eligible data from older equipment. |
| 12 September 2027 | Chapter IV starts to cover older contracts that are indefinite or expire no earlier than ten years from 11 January 2024. | It does not bring every earlier fixed-term contract into Chapter IV. |
Which onshore turbine data is in scope
The Commission's Data Act explained guidance distinguishes data that is raw or pre-processed from highly enriched, inferred or derived output. In a turbine context, product data may include readings from a single sensor or connected sensors about performance, use or environment, where those readings are generated by the product and readily available to the data holder. Relevant metadata needed to interpret the data is included. Readily available means the data holder can lawfully obtain it without disproportionate effort beyond a simple operation; it does not require the holder to create a new dataset or store data that the product was never designed to store or transmit.
| Category | Wind turbine examples | Data Act treatment to assess |
|---|---|---|
| Raw or pre-processed product data | Bearing, gearbox, generator and converter temperatures; vibration or acceleration; rotor speed; pitch and yaw; wind and power measurements; states, events and alarms. | Potentially in Chapter II when generated by the turbine and readily available to the data holder. |
| Relevant metadata | Timestamps, time zone, asset and component IDs, units, collection frequency, quality flags, operating mode, calibration context and known gaps. | Included where available and necessary to interpret eligible measurements. |
| Inferred, derived or proprietary output | Failure probability, remaining-useful-life estimate, anomaly score, diagnosis, recommendation, fleet benchmark, model weights, training set or algorithm. | Not an automatic Chapter II entitlement; may also involve content, intellectual property or trade secrets. |
The practical distinction is important. An owner may be able to request the temperature and vibration history that underlies an alert without being able to demand the OEM's analytic model or the conclusion produced by that model. The access right should not be used to imply that a data holder must reproduce a proprietary transformation, carry out a new engineering analysis or disclose every insight derived from a raw signal. A usable request names the existing fields, time range and metadata rather than asking vaguely for all condition-monitoring intelligence. This data governance should sit within the wider onshore wind farm maintenance programme.
Related services, users and data holders
A communicating onshore wind turbine will often be a connected product because it generates data about performance, use or environment and can communicate it. Classification still depends on the product and its EU-market facts. A related service is a digital service connected at purchase, or later to add, update or adapt a product function. The Commission's FAQ notes that it must affect the product's functions or operation; auxiliary consulting, analytics and regular repair or maintenance are not automatically related services. A portal that only analyses turbine data therefore needs a technical and contractual assessment before it is labelled a related service.
| Role | Regulatory meaning | Wind-sector example |
|---|---|---|
| User | A natural or legal person that owns a connected product, has contractually received temporary rights to use it, or receives related services; the Chapter II territorial scope concerns users in the EU. | The owner, lessee or qualifying operator may be the user, and more than one user can exist depending on rights and use. |
| Data holder | The natural or legal person with the right or obligation under the Regulation or applicable law to use and make data available. | Often a manufacturer, component or platform provider, or related-service provider; the actual contract and architecture determine the role. |
| Third party or data recipient | A person or business selected by the user to receive eligible data for the agreed purpose, subject to Chapter II conditions. | An independent maintenance planner or inspection provider is not automatically a user or data holder merely because it works on the turbine. |
Legacy turbines and the dates that matter
Do not reduce the transition to old turbines exempt or every historical file claimable. The Commission's version 1.4 Data Act FAQs says that, for Chapter II, data generated or collected after 12 September 2025 is the relevant starting point. Stored records may still matter to a later user, but retention, personal-data rights, trade secrets and earlier users' rights constrain the request. Pre-application data is not automatically within the new Chapter II access right.
| Connected product placed on the EU market | Chapter II access position | Article 3(1) design position |
|---|---|---|
| Before 12 September 2025 | Not automatically outside Chapter II for eligible data generated after the application date. | No general retrofit duty; the existing architecture may support indirect access only. |
| 12 September 2025 to 12 September 2026 | Assess access and third-party sharing rights for eligible readily available data. | Do not assume the later product-design obligation applies to this turbine. |
| After 12 September 2026 | Chapter II rights continue to apply subject to the Regulation's scope and safeguards. | Article 3(1) applies, subject to technical feasibility; pre-contract information must also cover data type, format, volume, collection, storage and access. |
For legacy assets, audit the historian, gateway, sensor and cloud path. The Data Act does not create a missing measurement, restore a deleted archive or force a component to generate a signal it never produced. The Commission FAQ says Article 4(13)'s contract requirement for a data holder's use of non-personal readily available data applies from 12 September 2025 to products placed on the market before and after that date. Record this separately from installation, commissioning and O&M dates.
What independent maintenance access can and cannot deliver
Under Chapter II, a user can request readily available data and metadata, or ask the holder to share it with a selected third party. The holder must provide it without undue delay, at the same quality, securely, in a structured machine-readable format and, where relevant and technically feasible, continuously and in real time. Access is free to the user. A data holder may agree reasonable compensation with an independent B2B recipient for the access operation; it is not a price for ownership of the data.
For maintenance, the useful question is whether a temperature trend, vibration series, operating-state history or alarm log justifies closer inspection or a different maintenance window. A gearbox planner, for example, can compare available load, temperature, vibration and event history with a proposed gearbox oil analysis versus borescope inspection decision. The data still need quality checks and engineering judgement; they do not select a test or prove a defect on their own.
A third-party recipient must stay within the purpose and conditions agreed with the user, comply with data-protection law, and erase data when it is no longer needed unless continued storage of non-personal data is agreed. It must not use the data to develop a competing connected product. That restriction does not prohibit competition in repair, maintenance or other related and aftermarket services.
Contracts, compensation and B2B terms
Check the purchase, lease, O&M, remote-monitoring, warranty and cloud contracts together. They should identify roles and data categories, state the holder's uses, explain retention and access, and address selected third parties. The Commission's non-binding Model Contractual Terms for data access and use are a drafting reference, not a substitute for the turbine's facts.
| Route | When it applies | Cost and contract rule |
|---|---|---|
| Chapter II user access | The user requests eligible connected-product or related-service data. | Access is free to the user. |
| Chapter II third-party sharing under Chapter III terms | The user asks the holder to send eligible data to an independent business recipient. | Terms must be fair, reasonable and non-discriminatory; reasonable compensation may apply to the recipient, subject to statutory limits. |
| Other mandatory B2B sharing under Chapter III | EU or national law creates an obligation to make data available to another business. | Compensation can reflect making the data available and may include a margin; eligible SMEs and non-profit research organisations cannot be charged more than the relevant costs. |
| Chapter IV unfair-term control | A stronger business unilaterally imposes a take-it-or-leave-it term on data access, use, liability or remedies. | The term can be tested for unfairness; an O&M template does not validate a broad exclusion or unexplained fee. |
Trade secrets, intellectual property and cybersecurity limits
The Data Act preserves other intellectual-property rules and the existing protection of trade secrets under Directive (EU) 2016/943. A data holder cannot make a bare trade-secret label do all the work: before sharing, it should identify protected data and agree proportionate technical and organisational safeguards with the user or third party, such as confidentiality terms, strict access controls and handling rules. If no agreement is reached, the safeguards are not implemented or confidentiality is undermined, sharing can be withheld or suspended. An exceptional refusal of specific data requires a written, case-by-case demonstration that serious economic damage is highly likely despite the safeguards, with notification to the competent authority.
The security limit is similarly specific. The user and data holder may contractually restrict or prohibit access, use or further sharing where the request could undermine security requirements of the connected product laid down in EU or national law and cause serious adverse effects to people's health, safety or security. That is not a general exemption for commercial sensitivity or a convenient excuse for a poor export process. Use proportionate controls such as authenticated accounts, least-privilege or read-only access, encryption, audit records, segregation of personal data and defined retention. The controls should protect the turbine and the people who operate it without quietly blocking a lawful user request.
If a data package points to a physical concern, the data is an input to an engineering decision, not a remote authorisation to continue operating. A condition-monitoring signal may need a site visit, visual examination or NDT and steel surface coating inspection with the correct procedure, access controls and acceptance basis. Keep the distinction between a data-access right, an inspection finding and a fitness-for-service decision clear.
How to Prepare an EU Data Act Turbine Data Request
Treat readiness as a traceable maintenance process, not as a demand for a large undifferentiated export. Before making a request, the owner or operator should be able to answer what decision the data will support, who is entitled to request it, who holds it, and how the recipient will protect it.
- Define the maintenance decision: state whether the request is for a baseline, an alarm review, a component trend, a warranty or handover record, a repair window, or evidence for a planned inspection. Set the turbine, component and time window.
- Map roles and dates: identify the EU user, data holder, possible related-service provider and intended third party. Record ownership or lease rights, market-placement date, relevant contract dates and whether more than one user or data subject is involved.
- Classify the fields: separate product data, related-service data and metadata from inferred or derived insights. Mark personal and non-personal data, trade-secret candidates, retention limits and fields that are not generated or not readily available.
- Specify the usable output: ask for field names, units, timestamps, time zone, sampling frequency, asset and component identifiers, quality flags, missing intervals, format, expected latency and the available direct or indirect access method. Do not request a model output when the maintenance decision needs the underlying series.
- Agree safeguards and purpose: define the named recipient, permitted use, authentication, read-only or other least-privilege access, confidentiality measures, personal-data legal basis, retention and deletion, onward sharing and the response or compensation terms.
- Submit and record: keep the request, identity checks, data-holder response, files or API details, quality statement, fee basis, refusal reasoning, trade-secret or security measures and any complaint or escalation route together.
- Validate before acting: check time alignment, units, resets, missing data, sensor plausibility, operating modes, curtailment and other confounders. Correlate the result with inspection, safety and engineering records; do not treat a clean export or a single alert as proof that a defect is absent or present.
The Commission's Data Act Legal Helpdesk can clarify the Regulation, but an asset-specific dispute may need a lawyer, data-protection specialist or competent authority. For maintenance teams, preserve the chain from request to defined dataset, protected sharing method and proportionate engineering decision, whether the turbine is new or legacy.