
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.
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 itData can come from industrial or public telemetry sources, and each run documents exact signals, labeling rules, windows, and any synthetic augmentation.
PoC snapshot: HQNN achieved accuracy of 94% (ROC-AUC 0.98) with fewer parameters than strong classical baselines.
Execution
Simulator
Qubits
8
Depth
2
Accuracy
94%
Model Size
Fewer trainable parameters
Parity
Strong baseline comparison
Deployment
Compact variational heads
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.
For a fault-detection case built on a different quantum method, see steel plate fault detection with QSVM.
| Dimension | Case 1 — Predictive Maintenance | Case 2 — Hydraulic Condition Monitoring |
|---|---|---|
| Task type | Binary classification — machine failure | Multiclass classification — cooler condition (3 classes) |
| Input data | 10,000 tabular telemetry readings, 5 features | 2,205 sensor cycles, 11 dimensions, 60 timesteps each |
| Quantum layer | 5-qubit variational block, depth 1 | 12-qubit Parallel Quantum Network, 4 layers, depth 3 |
| Test accuracy | 94% (HQNN) | 100% on 331 held-out cycles |
| Classical baseline | Boosting / random forest / neural network, comparable accuracy | CNN — 99.6% accuracy, 70s vs HQNN's 5s on the same split |
| Business impact | Up 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.
This landing is aimed at teams building predictive-maintenance and condition-monitoring workflows from telemetry or sensor time series, labels, and reproducible evaluation.
For teams that need earlier warnings to schedule maintenance before failures turn into downtime, on production lines or hydraulic equipment.
For groups comparing HQNN against established telemetry and sensor-monitoring pipelines and classical baselines.
For teams designing monitoring and alerting systems around labeled telemetry or sensor time series, with reproducible evaluation.
Up to $200K / unit
Annual savings
>90%
Downtime reduction
>400%
Year-1 ROI
$70K–85K / unit
Annual savings
Up to 85% fewer
Unplanned failures
55% shorter
Repair time
From telemetry or sensor time series to reproducible HQNN results and baseline comparisons, for either case
Ingest telemetry or sensor time-series signals, define warning horizons, and build rolling features with leakage control
Train boosting, random forest, neural-network, or CNN baselines on stratified splits, matched to the input shape
Attach a compact variational or parallel quantum network head over classical features and train it with a classical optimizer
Report accuracy, precision, recall, ROC-AUC or per-class F1, and confusion matrices while monitoring class imbalance
Capture seeds, config, environment logs, and the change log for full reruns
Algorithms, applied use cases and benchmarks connected to this page
Algorithms
Understand quantum neural networks (QNN) and hybrid QNN (HQNN): how each works, when to use which, real benchmarks, and NISQ hardware requirements.
Energy
Forecast short-term wind power with a Hybrid Quantum Neural Network, CAISO/NREL weather data, and a benchmarked classical MLP comparison.
Manufacturing
Detect additive manufacturing anomalies and classify melt-pool defect shapes with QSVM, reproducible benchmarks, and a classical baseline comparison.
Comparisons
Compare hybrid quantum neural networks with classical MLP and CNN baselines on parameters, training time, and accuracy across three benchmarked use cases.
Common questions about predictive maintenance and hydraulic condition monitoring with HQNN.
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.
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.
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.
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.
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.
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.
Run predictive maintenance on a simulator, compare HQNN against strong classical baselines, and download the code and report.
Try your first case for free