Skip to content

Commit b0597f0

Browse files
authored
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]>
1 parent 980ac39 commit b0597f0

File tree

7 files changed

+58
-14
lines changed

7 files changed

+58
-14
lines changed

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/_static/redirect/index.html

Lines changed: 0 additions & 1 deletion
This file was deleted.

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/Overview.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff 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
26

37
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.
48

59
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.
610

711
## How it works
812

9-
## High-Level Architecture
13+
### High-Level Architecture
1014

1115
![Time Series AI Stack Architecture Diagram](./_images/time-series-ai-stack-architecture.png)
1216

1317
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).
1418

15-
### 1. **Data Simulators/Destinations**:
19+
#### 1. **Data Simulators/Destinations**:
1620
We have two data simulators - OPC-UA server and MQTT Publisher which read the data from
1721
the CSV file and writes the data to the OPC-UA and MQTT input plugins in Telegraf.
1822
The OPC-UA server and the MQTT broker can act as data destinations for receiving the alerts respectively
1923

2024
---
2125

22-
### 2. **Generic Time Series AI stack**
26+
#### 2. **Generic Time Series AI stack**
2327

2428
**Key Features**:
2529

@@ -29,7 +33,7 @@ As seen in the architecture diagram, the sample app at a high level comprises of
2933
- 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*.
3034
- 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.
3135

32-
#### 2.1 **Data Ingestion**
36+
##### 2.1 **Data Ingestion**
3337

3438
**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.
3539

@@ -38,7 +42,7 @@ As seen in the architecture diagram, the sample app at a high level comprises of
3842

3943
---
4044

41-
#### 2.2. **Data Storage**
45+
##### 2.2. **Data Storage**
4246

4347
**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).
4448

@@ -49,7 +53,7 @@ As seen in the architecture diagram, the sample app at a high level comprises of
4953

5054
---
5155

52-
#### 2.3. **Data Processing**
56+
##### 2.3. **Data Processing**
5357

5458
**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**.
5559
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
6569

6670
---
6771

68-
#### 2.4. **Data Visualization**
72+
##### 2.4. **Data Visualization**
6973

7074
**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.
7175

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/get-started.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -147,9 +147,12 @@ cd edge-ai-suites/manufacturing-ai-suite/wind-turbine-anomaly-detection
147147

148148
2. Deploy the sample app, use only one of the options below:
149149

150-
> **NOTE**: The sample app is deployed by pulling the pre-built container images of the sample app
151-
> from the docker hub OR from the internal container registry (login to the docker registry from cli and configure `DOCKER_REGISTRY` env
152-
> variable in `.env` file at `edge-ai-suites/manufacturing-ai-suite/wind-turbine-anomaly-detection`)
150+
> **NOTE**:
151+
> 1. The below `make up_opcua_ingestion` or `make up_mqtt_ingestion` fails if the above required fields are not populated
152+
> as per the rules called out in `.env` file.
153+
> 2. The sample app is deployed by pulling the pre-built container images of the sample app
154+
> from the docker hub OR from the internal container registry (login to the docker registry from cli and configure `DOCKER_REGISTRY` env
155+
> variable in `.env` file at `edge-ai-suites/manufacturing-ai-suite/wind-turbine-anomaly-detection`)
153156
154157
- **Using OPC-UA ingestion**:
155158
```bash

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/how-to-deploy-with-edge-orchestrator.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,8 @@ To deploy the **Wind Turbine Anomaly Detection** Sample Application with the Edg
2828

2929
1. Update the below fields in `timeseries-wind-turbine-values.yaml` in the above deployment package folder
3030

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
32+
3133
```sh
3234
INFLUXDB_USERNAME:
3335
INFLUXDB_PASSWORD:

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/how-to-deploy-with-helm.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@
3939

4040
## Configure and update the environment variables
4141

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
4343

4444
``` sh
4545
INFLUXDB_USERNAME:
@@ -58,6 +58,8 @@
5858
> **Note:**
5959
> 1. Please uninstall the helm charts if already installed.
6060
> 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.
6163

6264
- OPC-UA ingestion flow:
6365

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
11
# Release Notes
22

3-
TBD
3+
- [August 2025](./aug-2025.md)
4+
5+
```{toctree}
6+
:maxdepth: 5
7+
:hidden:
8+
aug-2025.md
9+
```
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# August 2025
2+
3+
## v1.0.0
4+
5+
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

Comments
 (0)