Quantum predictive maintenance visualization
    Hybrid Quantum–Classical Networks

    Predictive Maintenanceand Condition Monitoring with HQNN

    Predict impending component failure from production-line telemetry, and classify hydraulic-system wear from sensor time series, with the same reproducible HQNN pipeline.

    What you get: two end-to-end HQNN case studies on a simulator — tabular production telemetry and hydraulic sensor time series — with explicit windowing and feature engineering for each.

    How it's delivered: one-click run results, zipped code and report, and baseline comparisons against boosting, random forests, neural networks, and CNNs.

    Why trust it: transparent preprocessing, feature-window ablations, confidence intervals, and versioned seeds for reruns.

    Predict Impending Failure and Wear from Sensor Data

    Goal and Method Overview

    The goal is to turn production telemetry and equipment sensor streams into an early, reliable warning of failure or wear, in time to schedule maintenance instead of reacting to it. This page covers two worked cases built on the same method: predicting machine failure from production-line telemetry, and classifying the condition of a hydraulic system's cooler from sensor time series.

    Unplanned downtime is costlier than planned service, and early warnings reduce scrap, missed deliveries, and emergency repairs. The classical baselines differ by case — gradient boosting, random forests, and neural networks for tabular telemetry; CNNs for sensor time series — but the quantum approach is the same across both: a hybrid quantum–classical neural network (HQNN) with a shallow variational circuit that can match strong baselines with fewer trainable parameters in compact encodings.

    Mechanically, both cases follow the same recipe after classical preprocessing. Each feature controls the rotation angle of one or more single-qubit gates — angle encoding — which maps the classical sample into a quantum state. A stack of variational layers then applies trainable rotations interleaved with entangling gates (CNOT or CZ) that couple qubits, spreading local feature information across multi-qubit correlations. The circuit is measured to produce expectation values (Pauli-Z or Pauli-Y, depending on the case), and that low-dimensional vector feeds a small classical head that makes the final prediction. The whole model — classical layers and quantum gate angles together — is trained end-to-end with gradient-based methods such as the adjoint or parameter-shift rule.

    What you get on the platform
    • • Two end-to-end HQNN pipelines on a simulator, one per case, with explicit windowing and feature engineering.
    • • Metrics for accuracy, precision, recall, ROC-AUC, and seed-controlled reproducibility.
    • • Reports with methods, assumptions, references, and executable Python code.

    Case 1: Predictive Maintenance from Production Telemetry

    The primary case is a binary classification task: predict impending component failure from production-line telemetry (temperatures, rotational speed, torque, tool wear).

    How we solve it
    1. Ingest telemetry signals, define warning horizons and failure labels, and build rolling and statistical features with leakage control.
    2. Train boosting, random forest, and neural-network baselines with stratified temporal splits and logged hyperparameters.
    3. Attach an 5-qubit variational block with depth 1 as a compact head over classical features and train it with a classical optimizer.
    4. Report accuracy, precision, recall, ROC-AUC, and PR curves while monitoring class imbalance.
    5. Capture seeds, config, environment logs, and a change log for full reruns.

    Data can come from industrial or public telemetry sources, and each run documents exact signals, labeling rules, windows, and any synthetic augmentation.

    Strengths

    • Shallow variational circuits can match strong baselines with fewer trainable parameters in compact encodings.
    • The pipeline uses explicit windowing, feature engineering, and transparent label definitions for both tabular and time-series inputs.
    • Parity checks are reported against boosting, random forests, neural networks, and CNNs on the same splits.

    Weaknesses & Risks

    • Results vary with data quality and labeling choices.
    • Class imbalance needs resampling, class weights, threshold tuning, and cost-sensitive metrics.
    • The quantum block runs on simulators today; hardware notes are included for transparency rather than deployment.

    What to Expect — Case 1

    PoC snapshot: HQNN achieved accuracy of 94% (ROC-AUC 0.98) with fewer parameters than strong classical baselines.

    Execution

    Simulator

    Qubits

    8

    Depth

    2

    Key Outcomes

    Accuracy

    94%

    Model Size

    Fewer trainable parameters

    Parity

    Strong baseline comparison

    Deployment

    Compact variational heads

    Case 2: Hydraulic System Condition Monitoring

    The second case is a multiclass time-series problem: determine the condition of a hydraulic system's cooler from raw process-sensor streams (pressures, volume flows, temperatures) recorded over 60-second duty cycles on a test rig. It's the same predictive-maintenance goal as Case 1 — turn sensor readings into an early, reliable condition signal — applied to a system where the input is a multivariate time series rather than a row of tabular features.

    Time series need a different front end than a row of tabular features. Here, a classical LSTM first summarizes each 60-step cycle, and a Parallel Quantum Network (PQN) — several small quantum circuits run side by side rather than one wide circuit — takes the compressed representation from there. Splitting the quantum work across parallel narrow circuits keeps each one shallow and easier to run on near-term hardware, while the parallel blocks together still reach 12 qubits of representational capacity.

    Dataset
    • • 2,205 cycles, 11 sensor dimensions, 60 timesteps per cycle.
    • • Target: cooler condition, 3 balanced classes; no missing values.
    • • Min-Max scaled to [0, 1]; split 70% train / 15% validation / 15% test.
    Setup
    • • A classical LSTM feature extractor reduces each 11×60 cycle before a stack of linear layers.
    • • A 12-qubit Parallel Quantum Network head (4 layers, depth 3, ≈852k weights) takes over from there, with angle encoding and a PauliY measurement basis.
    • • Baseline: a convolutional neural network (CNN) trained on the same split.
    • • Training ran on a simulator in 58 seconds.
    Results
    • • 100% accuracy on 331 held-out cycles, with precision, recall, and F1 all at 1.00 across all three condition classes, confusion matrix 107 / 119 / 105 correct.
    • • HQNN inference ran in 5 seconds versus 70 seconds for the CNN baseline, which reached 99.6% accuracy on the same test set.
    • • Estimated business impact: $70K–85K in annual savings per unit, up to 85% fewer unplanned failures, and 55% shorter repair time.

    For a fault-detection case built on a different quantum method, see steel plate fault detection with QSVM.

    Case 1 vs. Case 2, Side by Side

    DimensionCase 1 — Predictive MaintenanceCase 2 — Hydraulic Condition Monitoring
    Task typeBinary classification — machine failureMulticlass classification — cooler condition (3 classes)
    Input data10,000 tabular telemetry readings, 5 features2,205 sensor cycles, 11 dimensions, 60 timesteps each
    Quantum layer5-qubit variational block, depth 112-qubit Parallel Quantum Network, 4 layers, depth 3
    Test accuracy94% (HQNN)100% on 331 held-out cycles
    Classical baselineBoosting / random forest / neural network, comparable accuracyCNN — 99.6% accuracy, 70s vs HQNN's 5s on the same split
    Business impactUp to $200K/unit savings, >90% downtime reduction, >400% year-1 ROI$70K–85K/unit savings, up to 85% fewer unplanned failures, 55% faster repairs

    Both reports draw the same conclusion: quantum-enhanced HQNN architectures are worth evaluating for mission-critical predictive-maintenance and condition-monitoring systems where fault-classification fidelity and inference latency matter, and the advantage tends to grow once a feature space exceeds roughly 32 correlated signals. Classical models — boosting, random forests, MLPs, or CNNs — remain sufficient and cheaper for small-scale, low-dimensional monitoring tasks or where infrastructure cost is the binding constraint.

    Who it's for

    This landing is aimed at teams building predictive-maintenance and condition-monitoring workflows from telemetry or sensor time series, labels, and reproducible evaluation.

    Maintenance and reliability engineers

    For teams that need earlier warnings to schedule maintenance before failures turn into downtime, on production lines or hydraulic equipment.

    Manufacturing analytics and operations teams

    For groups comparing HQNN against established telemetry and sensor-monitoring pipelines and classical baselines.

    OEMs building monitoring products

    For teams designing monitoring and alerting systems around labeled telemetry or sensor time series, with reproducible evaluation.

    Estimated Business Impact, by Case

    Case 1 — Predictive Maintenance

    Up to $200K / unit

    Annual savings

    >90%

    Downtime reduction

    >400%

    Year-1 ROI

    Case 2 — Hydraulic Condition Monitoring

    $70K–85K / unit

    Annual savings

    Up to 85% fewer

    Unplanned failures

    55% shorter

    Repair time

    How it works

    From telemetry or sensor time series to reproducible HQNN results and baseline comparisons, for either case

    01

    Data & Labeling

    Ingest telemetry or sensor time-series signals, define warning horizons, and build rolling features with leakage control

    02

    Baselines

    Train boosting, random forest, neural-network, or CNN baselines on stratified splits, matched to the input shape

    03

    HQNN Design

    Attach a compact variational or parallel quantum network head over classical features and train it with a classical optimizer

    04

    Evaluation

    Report accuracy, precision, recall, ROC-AUC or per-class F1, and confusion matrices while monitoring class imbalance

    05

    Reproducibility

    Capture seeds, config, environment logs, and the change log for full reruns

    Frequently Asked Questions

    Common questions about predictive maintenance and hydraulic condition monitoring with HQNN.

    Is HQNN predictive maintenance the same model for any equipment?

    The method is the same — a shallow variational or parallel quantum circuit attached to a classical feature extractor — but the encoding and classical baseline change with the data. The predictive-maintenance case uses tabular telemetry with a 5-qubit variational block; the hydraulic case uses an LSTM front end and a 12-qubit Parallel Quantum Network over 60-second sensor cycles.

    What data do I need to try this on my own equipment?

    For tabular telemetry: rows of sensor readings (temperatures, speed, torque, wear, etc.) with a failure label. For time-series condition monitoring: fixed-length sensor cycles (pressures, flows, temperatures) with a condition or severity label per cycle. Both platform runs document exact signals, windows, and labeling rules used.

    Does the HQNN run on real quantum hardware?

    Both case studies here run on a simulator, limited to 16 qubits with no noise modeling. The reports include hardware implementation notes — qubit counts, circuit depth, and backend guidance — for teams evaluating a future move to quantum hardware, but today's numbers are simulator results.

    How does HQNN compare with classical baselines?

    On production telemetry, HQNN reaches 94% accuracy (ROC-AUC 0.98) with fewer trainable parameters than boosting, random forest, and neural-network baselines at comparable accuracy. On hydraulic sensor cycles, HQNN reached 100% test accuracy versus 99.6% for a CNN baseline, at 5 seconds of inference against 70 seconds.

    Are the results reproducible?

    Yes. Every run captures seeds, configuration, environment logs, and a change log, and the report documents preprocessing, splits, and any class-imbalance handling so a rerun should reproduce the same metrics.

    Can I run this on a dataset that isn't one of the two examples here?

    Yes — the platform maps your problem to the closest use case, tabular or time-series, confirms the approach and assumptions with you, and then runs the HQNN pipeline against your data with the same baseline comparisons and reporting shown here.

    Try Superpositions Studio

    Run predictive maintenance on a simulator, compare HQNN against strong classical baselines, and download the code and report.

    Try your first case for free