node-red-contrib-condition-monitoring 0.2.2

Node-RED Nodes for anomaly detection, predictive maintenance, and time series analysis

npm install node-red-contrib-condition-monitoring

node-red-contrib-condition-monitoring

A comprehensive Node-RED module for anomaly detection, predictive maintenance, and time series analysis.

---

Project Status: v0.2.2 Beta

Predictive Maintenance Enhancement Update

• 9 Unified Nodes - PCA, Training Data Collector, and enhanced core nodes
• ISO 10816-3 Integration - Vibration severity assessment with zones A-D
• Butterworth Filter - 2nd order IIR filter with zero-phase filtering (filtfilt)
• Hysteresis (Anti-Flicker) - Prevents rapid alarm on/off switching
• Dynamic Sensor Weighting - Auto-adjusts weights based on sensor reliability
• Robust RUL Calculation - Theil-Sen estimator, median filter, moving average smoothing
• High-Performance FFT - Radix-4 Cooley-Tukey algorithm via fft.js
• State Persistence - Optional context-based state saving across restarts
• Comprehensive Testing - 135 unit tests with Jest framework

---

Important Disclaimer

This software is provided for condition monitoring and predictive maintenance purposes.

• NOT a replacement for safety-critical systems
• NOT suitable as the sole means of safety decision-making
• Should be used as an additional monitoring layer
• Always validate results with domain experts
• Follow proper safety protocols and regulations for your industry

Use at your own risk. See LICENSE file for full legal terms.

Features

• 9 Powerful Nodes - Complete condition monitoring toolkit
• 10 Anomaly Detection Methods - Z-Score, IQR, Moving Average, Threshold, Percentile, EMA, CUSUM, Isolation Forest, PCA, Mahalanobis
• Signal Analysis - High-performance FFT (Radix-4), Vibration Features (RMS, Crest Factor, Kurtosis), Peak Detection, Envelope Analysis, Cepstrum, Autocorrelation (ACF), Sample Entropy, Periodicity Detection
• Correlation Analysis - Pearson, Spearman, Cross-Correlation with time lag detection
• Gearbox Diagnostics - Cepstrum analysis for gear mesh faults
• Reliability Analysis - Weibull distribution, B-life, MTTF, RUL
• Trend Prediction - Linear Regression, Exponential Smoothing, Rate of Change
• Multi-Value Processing - Split, Analyze, Correlate, Aggregate multiple sensors
• ML Inference - TensorFlow.js, ONNX, Keras, scikit-learn, TFLite, Google Coral (with persistent Python bridge)
• State Persistence - Optional buffer/statistics persistence across restarts

Installation

npm install node-red-contrib-condition-monitoring

Or install directly from Node-RED:

1. Menu → Manage palette
2. Install tab
3. Search for node-red-contrib-condition-monitoring
4. Click install

Quick Start

With Docker Compose (Recommended)

# Start Node-RED with the module
docker-compose up -d

# Access at http://localhost:1880

Import Example Flows

1. Open Node-RED: http://localhost:1880
2. Menu → Import → Examples
3. Select one of the example flows

Available Nodes (9 Nodes)

All nodes are in the condition-monitoring category.

Core Analysis Nodes

1. Anomaly Detector

7 detection methods in one node:

Method	Best For
Z-Score	Normal distributions, general purpose
IQR	Robust to outliers, skewed data
Threshold	Fixed min/max limits
Percentile	Dynamic bounds based on data distribution
EMA	Recent changes, adaptive baseline
CUSUM	Drift detection, gradual shifts
Moving Average	Smoothed baseline comparison

Hysteresis (Anti-Flicker):

• Prevents rapid alarm on/off switching near thresholds
• Configurable consecutive samples before triggering
• Deadband percentage for exiting anomaly state

Multi-Sensor JSON Input:

• Accepts JSON objects with multiple sensors: { "temp": 65.2, "pressure": 4.5 }
• Maintains separate buffers and hysteresis states per sensor
• Outputs combined result with per-sensor analysis

Example:

[MQTT Sensor] → [Anomaly Detector (Z-Score)] → [Normal] → [Dashboard]
                                              → [Anomaly] → [Alarm]

2. Isolation Forest

ML-based anomaly detection with online learning:

• Unsupervised learning - no training labels required
• Detects complex, multivariate anomalies
• 3 learning modes:
  • Batch - Retrain when buffer full
  • Incremental - Periodic retraining (configurable interval)
  • Adaptive - Auto-adjust threshold based on feedback
• Configurable number of trees and samples per tree

3. Multi-Value Processor

4 modes for multi-sensor data:

Mode	Function
Split	Extract individual values from arrays/objects
Analyze	Anomaly detection per value (Z-Score, IQR, Threshold, Mahalanobis)
Correlate	Pearson, Spearman, or Cross-Correlation between two sensors
Aggregate	Reduce to single value (Mean, Median, Min, Max, Sum, Range, StdDev)

Mahalanobis Distance: Detects multivariate anomalies considering correlations between sensors.

Cross-Correlation: Finds time lag between sensors - detects propagation delays (e.g., temperature wave through pipe).

Example:

[Sensors] → [Multi-Value (Split)] → [Anomaly Detector] → ...
[Sensors] → [Multi-Value (Aggregate)] → Mean value for dashboard

4. Signal Analyzer

5 modes for signal analysis:

Mode	Output
FFT	Frequency peaks, spectral features
Vibration	RMS, Crest Factor, Kurtosis, Skewness, Health Score, ISO 10816-3 assessment
Peaks	Local maxima/minima detection
Envelope	Bearing fault detection (BPFO, BPFI, BSF, FTF) with Butterworth filter
Cepstrum	Gearbox fault detection (GMF, sidebands)

ISO 10816-3 Vibration Severity:

• Machine classes I-IV (small to large machines)
• Zones A-D with severity levels and recommendations
• Automatic alarm/warning thresholds

Butterworth Filter:

• 2nd order IIR filter for envelope analysis
• Zero-phase filtering (filtfilt) - no phase distortion
• Automatic fallback for edge cases

Example:

[Vibration Sensor] → [Signal Analyzer (Vibration)] → RMS, ISO 10816 Zone
                   → [Signal Analyzer (FFT)] → Frequency Peaks
                   → [Signal Analyzer (Envelope)] → Bearing faults

5. Trend Predictor

3 modes for trend analysis:

Mode	Output
Prediction	Future values, trend direction
RUL	Remaining Useful Life with confidence intervals
Rate of Change	First/second derivative, acceleration

RUL Features:

• Configurable failure and warning thresholds
• Multiple time units (hours, minutes, days, cycles)
• Confidence intervals for predictions
• Status: healthy/warning/critical/failed
• Degradation models: Linear, Exponential, Weibull (reliability-based)
• Robust calculation: Theil-Sen estimator, median filter, moving average smoothing

Multi-Sensor JSON Input:

• Accepts JSON objects with multiple sensors: { "temp": 65.2, "vibration": 2.5 }
• Calculates trends/RUL for each sensor independently
• Tracks threshold exceedance per sensor

Weibull Analysis:

• Automatic Weibull parameter estimation (β, η)
• B-Life calculation (B1, B5, B10, B50) - time when X% have failed
• Failure mode classification (infant_mortality, useful_life, wear_out, rapid_wear_out)
• MTTF calculation

Example:

[Temperature] → [Trend Predictor (RUL)] → "RUL: 48.5h (95% confidence)"

6. Health Index

Multi-sensor health aggregation:

• Weighted combination of sensors
• 0-100% health score
• Configurable aggregation methods (Weighted, Dynamic, Minimum, Average, Geometric)
• Dynamic weighting - Auto-adjusts weights based on sensor reliability
• Visual threshold configuration with slider-based UI
• Configurable status levels (healthy, warning, degraded, critical)
• Automatic worst sensor identification with reliability metrics

7. ML Inference

Machine Learning model inference with multiple runtime options:

JavaScript Runtimes (npm install)

Work immediately after installation - no additional setup:

• ONNX (.onnx) - PyTorch, TensorFlow, scikit-learn models
• TensorFlow.js (model.json + .bin) - Keras, TensorFlow models

Python Runtimes (Docker/Python required)

Require Python environment with ML libraries:

• TFLite (.tflite) - Edge/mobile optimized models
• Keras (.keras, .h5) - Native Keras models
• scikit-learn (.pkl, .joblib) - Classic ML (Random Forest, SVM, etc.)

Hardware Accelerated

• Google Coral / Edge TPU - 10-100x faster inference

Tip: Use ONNX format for best compatibility across frameworks. The node automatically detects available runtimes and shows warnings for Python-dependent formats.

8. PCA Anomaly Detection

Principal Component Analysis for multi-sensor anomaly detection:

• Reduces high-dimensional data to principal components
• Detects anomalies using Hotelling's T² and SPE statistics
• Auto-selects components based on explained variance threshold
• Contribution analysis - identifies which sensor caused the anomaly

Method	Use Case
T²	Variations within normal operating space
SPE	New patterns not seen during training
Combined	Both T² and SPE (recommended)

9. Training Data Collector

Collects sensor data for ML model training:

Feature	Description
3 Collection Modes	Batch, Streaming (JSONL), Time-Series Windows
Multiple Export Formats	CSV, JSONL, JSON with metadata
Auto-Compression	.gz compression for large datasets (>10k samples)
Train/Val/Test Split	Automatic dataset splitting with configurable ratios
Label Modes	Manual, from message, RUL countdown, unlabeled
S3 Upload	Direct upload to AWS S3 buckets
Data Validation	Rejects NaN/Infinity, tracks statistics

Use Cases:

• Collect labeled training data from live sensors
• Create datasets for the training notebooks
• Export time-series windows for LSTM/Transformer training
• Automatic cloud backup to S3

Control Actions:

msg.action = "export";   // Export current buffer
msg.action = "clear";    // Clear buffer
msg.action = "stats";    // Get collection statistics
msg.action = "pause";    // Pause collection
msg.action = "resume";   // Resume collection
msg.action = "resetRul"; // Reset RUL counter

Example:

[Sensors] → [Multi-Value Processor] → [Training Data Collector] → [S3/File]
                                              ↑
                              [Inject: action="export"]

---

Which Node Should I Use?

Quick Decision Tree

What do you want to detect?
├─ Simple threshold violations → Anomaly Detector (Threshold)
├─ Statistical outliers → Anomaly Detector (Z-Score/IQR)
├─ Gradual drift → Anomaly Detector (CUSUM)
├─ Complex patterns → Isolation Forest (with Online Learning)
├─ Multi-sensor anomalies → PCA Anomaly Detection
├─ Vibration issues → Signal Analyzer (Vibration/FFT)
├─ Bearing faults → Signal Analyzer (Envelope Mode)
├─ Gearbox faults → Signal Analyzer (Cepstrum)
├─ Multiple sensors → Multi-Value Processor
├─ Multivariate anomalies → Multi-Value Processor (Mahalanobis)
├─ Aggregate sensors → Multi-Value Processor (Aggregate Mode)
├─ Remaining Useful Life → Trend Predictor (RUL + Weibull)
├─ Future prediction → Trend Predictor (Prediction)
├─ Overall health → Health Index (Visual Thresholds)
└─ Custom ML model → ML Inference

---

Usage Examples

Simple Temperature Monitoring

[MQTT] → [Anomaly Detector] → [Normal] → [Dashboard]
                             → [Anomaly] → [Email Alert]

Motor Predictive Maintenance

[Sensors] → [Multi-Value (Split)] → [Anomaly Detector]
                                  → [Trend Predictor] → RUL Display
                                  → [Signal Analyzer (FFT)] → Frequency Chart
          → [Health Index] → Dashboard

Bearing Vibration Analysis

[Vibration] → [Signal Analyzer (Vibration)] → Features
            → [Signal Analyzer (FFT)] → Frequencies
            → [Signal Analyzer (Envelope)] → Bearing Faults
            → [Anomaly Detector (IQR)] → Outliers

ML Anomaly Detection

[Features] → [ML Inference (Autoencoder)] → Reconstruction Error → [Anomaly Detector (Threshold)]

---

Migration Guide (v0.1.x → v0.2.0)

Node Mapping

Old Node(s)	New Node	Notes
zscore-anomaly	anomaly-detector	Set method: zscore
iqr-anomaly	anomaly-detector	Set method: iqr
threshold-anomaly	anomaly-detector	Set method: threshold
percentile-anomaly	anomaly-detector	Set method: percentile
ema-anomaly	anomaly-detector	Set method: ema
cusum-anomaly	anomaly-detector	Set method: cusum
moving-average-anomaly	anomaly-detector	Set method: moving-average
multi-value-splitter	multi-value-processor	Set mode: split
multi-value-anomaly	multi-value-processor	Set mode: analyze
correlation-anomaly	multi-value-processor	Set mode: correlate
fft-analysis	signal-analyzer	Set mode: fft
vibration-features	signal-analyzer	Set mode: vibration
peak-detection	signal-analyzer	Set mode: peaks
trend-prediction	trend-predictor	Set mode: prediction
rate-of-change	trend-predictor	Set mode: rate-of-change
isolation-forest-anomaly	isolation-forest	(unchanged)
health-index	health-index	(unchanged)
ml-inference	ml-inference	(unchanged)

Configuration Mapping

Anomaly Detector:

// Old (zscore-anomaly)
{ threshold: 3.0, warningThreshold: 2.0, windowSize: 100 }

// New (anomaly-detector)
{ method: "zscore", zscoreThreshold: 3.0, zscoreWarning: 2.0, windowSize: 100 }

---

Node Configuration Examples

Anomaly Detector (Z-Score)

// Input
msg.payload = 42.5;

// Output
{
  "payload": 42.5,
  "isAnomaly": true,
  "severity": "critical",
  "method": "zscore",
  "zScore": 3.2,
  "mean": 35.0,
  "stdDev": 2.3,
  "threshold": 3.0,
  "warningThreshold": 2.0,
  "bufferSize": 100,
  "windowSize": 100
}

Signal Analyzer (FFT)

// Input (continuous stream)
msg.payload = 0.45;

// Output
{
  "payload": 0.45,
  "peaks": [
    { "frequency": 30, "magnitude": 0.5 },
    { "frequency": 157, "magnitude": 0.3 }
  ],
  "dominantFrequency": 30,
  "features": {
    "spectralCentroid": 85.2,
    "crestFactor": 3.5,
    "rms": 0.42
  }
}

Trend Predictor (RUL Mode)

// Input
msg.payload = 75.2;
msg.timestamp = Date.now();

// Output (RUL Mode)
{
  "payload": 75.2,
  "rul": {
    "value": 48.5,
    "unit": "hours",
    "lower": 42.1,          // Lower confidence bound
    "upper": 55.2,          // Upper confidence bound
    "confidence": 0.87,     // R-squared
    "status": "warning"     // healthy/warning/critical/failed
  },
  "degradation": {
    "percent": 75.2,        // % toward failure threshold
    "rate": 0.5,            // Degradation rate per sample
    "trend": "increasing"
  },
  "thresholds": {
    "failure": 100,
    "warning": 80
  }
}

---

Dynamic Configuration (msg.config)

All major nodes support dynamic runtime configuration via msg.config. This allows you to override node settings on a per-message basis without redeploying the flow.

Supported Nodes and Parameters

Anomaly Detector

msg.config = {
  method: "zscore",           // Override detection method
  zscoreThreshold: 2.5,       // Override Z-score threshold
  zscoreWarning: 1.8,         // Override warning threshold
  iqrMultiplier: 1.5,         // Override IQR multiplier
  minThreshold: 10,           // Override min threshold
  maxThreshold: 100,          // Override max threshold
  hysteresisEnabled: false,   // Enable/disable hysteresis
  consecutiveCount: 5         // Override consecutive count
};
msg.payload = 42.5;

Trend Predictor

msg.config = {
  mode: "rate-of-change",     // Override mode (prediction/rate-of-change/rul)
  threshold: 80,              // Override prediction threshold
  rocThreshold: 5,            // Override rate of change threshold
  failureThreshold: 100,      // Override RUL failure threshold
  warningThreshold: 80,       // Override RUL warning threshold
  predictionSteps: 10         // Override prediction horizon
};
msg.payload = 75.2;

Signal Analyzer

msg.config = {
  mode: "vibration",          // Override mode (fft/vibration/peaks/envelope/cepstrum)
  fftSize: 1024,              // Override FFT size
  sampleRate: 1000,           // Override sample rate
  vibrationThreshold: 5,      // Override vibration threshold
  peakThreshold: 0.3          // Override peak detection threshold
};
msg.payload = [0.5, 0.7, 0.3, ...];

Health Index

msg.config = {
  healthyThreshold: 90,       // Override healthy threshold
  warningThreshold: 70,       // Override warning threshold
  degradedThreshold: 50,      // Override degraded threshold
  criticalThreshold: 25,      // Override critical threshold
  aggregationMethod: "min",   // Override aggregation (weighted/min/average)
  sensorWeights: {            // Override sensor weights
    "temp": 2.0,
    "vibration": 1.5
  }
};
msg.payload = { temp: 45, vibration: 2.3 };

Use Cases

1. Adaptive Thresholds: Adjust thresholds based on time of day, operating mode, or external conditions
2. A/B Testing: Compare different detection parameters on the same data stream
3. Contextual Sensitivity: Use tighter thresholds during critical operations
4. Batch Processing: Process historical data with different configurations

---

Docker Setup

For ML Inference Node

The ML Inference node requires a Debian-based container with native dependencies.

# Use the provided docker-compose.dev.yml
docker-compose -f docker-compose.dev.yml up

# This builds a custom image with:
# - Python 3 + build tools
# - TensorFlow.js Node bindings
# - ONNX Runtime Node bindings

Standard Setup

# Production mode
docker-compose up

# Development mode (hot-reload)
docker-compose -f docker-compose.dev.yml up

---

Dependencies

Required

• Node-RED >= 2.0.0
• Node.js >= 14.0.0

Core Dependencies

• fft.js - High-performance FFT (Radix-4 Cooley-Tukey algorithm)
• ml-isolation-forest - For Isolation Forest node
• simple-statistics - For statistical functions

Optional - JavaScript ML Runtimes

• @tensorflow/tfjs-node - TensorFlow.js support
• onnxruntime-node - ONNX Runtime support

Optional - Python ML Runtimes (Docker or manual)

For TFLite, Keras, and scikit-learn models:

pip install numpy tensorflow scikit-learn joblib tflite-runtime
# Use numpy<2 for tflite-runtime compatibility
pip install "numpy<2"

---

Performance Features

High-Performance FFT

The Signal Analyzer uses fft.js with the Radix-4 Cooley-Tukey algorithm:

• O(n log n) complexity vs O(n²) for naive DFT
• 10-100x faster for large signal buffers (2048+ samples)
• Automatic power-of-2 sizing and windowing (Hann, Hamming, Blackman)

Persistent Python Bridge

For Python-based ML models (Keras, scikit-learn, TFLite), a persistent subprocess is maintained:

• Single Python process shared across all ML Inference nodes
• Model caching - models stay loaded in memory between inferences
• 10-100x faster compared to spawning a new process per inference
• Automatic restart if the bridge crashes

Check bridge status via API: GET /ml-inference/python-bridge

State Persistence

Enable Persist State in node configuration to save:

• Data buffers and training history
• Calculated statistics (mean, std, thresholds)
• Trained model states (PCA, Isolation Forest)

States survive Node-RED restarts when using file-based context storage:

// settings.js
contextStorage: {
    default: { module: "localfilesystem" }
}

Or use the provided Docker image which includes all dependencies.

---

Documentation

• models/README.md - ML models guide and training instructions
• CHANGELOG.md - Version history and changes

---

Contributing

Contributions are welcome! Please:

1. Fork the repository
2. Create a feature branch
3. Add tests if applicable
4. Submit a pull request

License

MIT License - see LICENSE file for details.

Author

blanpa

---

Roadmap

• Consolidate nodes into unified components
• ML Inference with Model Registry
• Google Coral / Edge TPU support
• PCA Anomaly Detection
• Bearing fault detection via Signal Analyzer (Envelope Mode)
• Weibull reliability analysis
• Cepstrum analysis for gearbox diagnostics
• Mahalanobis distance for multivariate anomalies
• ISO 10816-3 vibration severity assessment
• Hysteresis (anti-flicker) for anomaly detection
• Pre-trained models for common use cases

---

Made with ❤️ for the Node-RED community