You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wind-turbine-anomaly-detection: Added release notes and minor improvements
This PR updates the documentation for the Wind Turbine Anomaly Detection sample application, focusing on release notes, deployment instructions, and an improved overall guide.
Adds release notes for August 2025 and updates the release note overview to reference the new release.
Enhances deployment guides for Helm and Edge Orchestrator with additional precheck notes.
Revises the general overview to improve readability and hierarchy consistency.
Signed-off-by: Vinod K B <[email protected]>
Copy file name to clipboardExpand all lines: manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/Overview.md
+12-8Lines changed: 12 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,29 @@
1
-
# Overview
1
+
# Wind Turbine Anomaly Detection
2
+
3
+
Time Series predictive maintenance use case to detect the anomalous power generation patterns relative to wind speed for the wind turbines.
4
+
5
+
## Overview
2
6
3
7
In the Energy Sector, such as wind turbines for power generation, unexpected equipment failures result in costly downtime and operational inefficiencies. Using AI-driven predictive analytics, edge devices can monitor equipment health through sensor data (e.g. power generation and wind speed), detect anomalous trends indicative of wear or failure, and alert operators to schedule maintenance proactively. This enhances productivity, reduces costs, and extends equipment lifespan.
4
8
5
9
This sample application demonstrates a time series use case by detecting the anomalous power generation patterns relative to wind speed. By identifying deviations, it helps optimize maintenance schedules and prevent potential turbine failures, enhancing operational efficiency.
6
10
7
11
## How it works
8
12
9
-
## High-Level Architecture
13
+
###High-Level Architecture
10
14
11
15

12
16
13
17
As seen in the architecture diagram, the sample app at a high level comprises of data simulators(can act as data destinations if configured) - these in the real world would be the physical devices, the generic Time Series AI stack based on **TICK Stack** comprising of Telegraf, InfluxDB, Time Series Analytics microservice using Kapacitor and Grafana. The Model Registry microservice helps to achieve the MLOps flow by uploading the **UDF deployment package**(comprises of UDF, TICKScripts, models).
14
18
15
-
### 1. **Data Simulators/Destinations**:
19
+
####1. **Data Simulators/Destinations**:
16
20
We have two data simulators - OPC-UA server and MQTT Publisher which read the data from
17
21
the CSV file and writes the data to the OPC-UA and MQTT input plugins in Telegraf.
18
22
The OPC-UA server and the MQTT broker can act as data destinations for receiving the alerts respectively
19
23
20
24
---
21
25
22
-
### 2. **Generic Time Series AI stack**
26
+
####2. **Generic Time Series AI stack**
23
27
24
28
**Key Features**:
25
29
@@ -29,7 +33,7 @@ As seen in the architecture diagram, the sample app at a high level comprises of
29
33
- Extensible **Time Series Analytics Microservice** capable of running Deep Learning models by updating its container image, in addition to Machine Learning models accelerated by Intel® Extension for Scikit-learn*.
30
34
- Enables users to ingest their own data via **Telegraf** and implement custom User-Defined Functions (UDFs) in the **Time Series Analytics Microservice** to address specific time series use cases.
31
35
32
-
#### 2.1 **Data Ingestion**
36
+
#####2.1 **Data Ingestion**
33
37
34
38
**Telegraf** is a plugin-driven server agent that collects and reports metrics from various sources. It uses input plugins to ingest data and sends it to **InfluxDB** for storage.
35
39
@@ -38,7 +42,7 @@ As seen in the architecture diagram, the sample app at a high level comprises of
38
42
39
43
---
40
44
41
-
#### 2.2. **Data Storage**
45
+
#####2.2. **Data Storage**
42
46
43
47
**InfluxDB** is a high-performance time series database designed to handle large volumes of write and query operations. It stores both raw ingested data and processed data, which can be organized into different measurements (tables).
44
48
@@ -49,7 +53,7 @@ As seen in the architecture diagram, the sample app at a high level comprises of
49
53
50
54
---
51
55
52
-
#### 2.3. **Data Processing**
56
+
#####2.3. **Data Processing**
53
57
54
58
**Time Series Analytics Microservice** uses **Kapacitor** - a real-time data processing engine that enables users to analyze time series data. It supports both streaming and batch processing and integrates seamlessly with **InfluxDB**.
55
59
Time Series Analytics Microservice has the Intel® Extension for Scikit-learn* python package which when used in the User Defined Functions (UDFs) of Kapacitor would improve the performance of the Machine Learning algorithms.
@@ -65,7 +69,7 @@ The Time Series Analytics microservice allows customization by reading the UDF d
65
69
66
70
---
67
71
68
-
#### 2.4. **Data Visualization**
72
+
#####2.4. **Data Visualization**
69
73
70
74
**Grafana** provides an intuitive user interface for visualizing time series data stored in **InfluxDB**. It allows users to create custom dashboards and monitor key metrics in real time.
Copy file name to clipboardExpand all lines: manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/how-to-deploy-with-edge-orchestrator.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,8 @@ To deploy the **Wind Turbine Anomaly Detection** Sample Application with the Edg
28
28
29
29
1. Update the below fields in `timeseries-wind-turbine-values.yaml` in the above deployment package folder
30
30
31
+
> **Note**: Please note the `helm install` command fails if the above required fields are not populated as per the rules called out in `timeseries-wind-turbine-values.yaml` file
Copy file name to clipboardExpand all lines: manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/how-to-deploy-with-helm.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@
39
39
40
40
## Configure and update the environment variables
41
41
42
-
1. Update the below fields in`edge-ai-suites/manufacturing-ai-suite/wind-turbine-anomaly-detection/helm/values.yaml` file in the helm chart
42
+
1. Update the below fields in`values.yaml` file in the helm chart
43
43
44
44
``` sh
45
45
INFLUXDB_USERNAME:
@@ -58,6 +58,8 @@
58
58
>**Note:**
59
59
> 1. Please uninstall the helm charts if already installed.
60
60
> 2. If the worker nodes are running behind proxy server, then please additionally set env.HTTP_PROXY and env.HTTPS_PROXY env like the way env.TELEGRAF_INPUT_PLUGIN is being set below with helm install command
61
+
> 3. Please note the `helm install`command fails if the above required fields are not populated
62
+
> as per the rules called out in`values.yaml` file.
This is the first version of the Wind Turbine Anomaly detection sample app
6
+
showcasing a time series use case by detecting the anomalous power generation patterns relative to wind speed.
7
+
8
+
# Deployments
9
+
10
+
- Docker compose deployment on single node
11
+
- Helm deployment on kubernetes single cluster node
12
+
- Helm deployment with Edge Manageability Framework
13
+
14
+
# Features
15
+
16
+
- Added sample OPC-UA server and MQTT publisher data simulators to ingest the wind turbine data
17
+
- Generic Time Series AI stack supporting the data ingestion, data analytics,
18
+
data storage and data visualization
19
+
- Data Analytics is powered by [Time Series Analytics Microservice](https://github.com/open-edge-platform/edge-ai-libraries/tree/main/microservices/time-series-analytics/docs)
20
+
which from the sample app context takes in the configuration related to wind turbine
21
+
sample app and the User Defined Function(UDF) deployment package and provides
22
+
below capabilities:
23
+
- Provides the OPC-UA connector to publish the anomaly alerts to configured
24
+
OPC-UA server
25
+
- Provides support to publish the anomaly alerts to configured MQTT server
26
+
- Provides support to customize the UDF deployment package
27
+
28
+
More details at [user-guide](../../user-guide/index.rst)
0 commit comments