Skip to content
DemonstrationProcess industry

Predictive Maintenance System

A demonstration of condition monitoring done end to end: instrumentation and edge processing on constrained hardware, through to a maintenance workflow that acts on a signal rather than a dashboard.

Industry
Process industry
Scenario
Illustrative — process industry operator
Status
In-house demonstration

This is an illustrative example of the kind of work we do, not a client engagement. The scenario is written to make the engineering decisions legible; the outcomes below describe what the system was designed to do, not verified client metrics.

Challenge

The constraint we designed against.

Predictive maintenance fails in two familiar ways. Either the sensing is too coarse to carry the signal — low sample rates, missing context, gaps whenever connectivity drops — or the model produces alerts that nobody is accountable for closing. Both end the same way: an expensive dashboard, and maintenance still running to a fixed calendar.

Solution

What we built, and why it is shaped this way.

Sensing is designed against the failure modes that matter, not against what is cheapest to install: vibration and current signatures at rates that preserve the diagnostic band, with temperature and process context alongside. An edge node performs windowing and feature extraction locally, so the uplink carries features rather than raw waveforms and a network outage degrades resolution instead of losing the record. Detection runs on residuals against a learned healthy baseline per asset, with drift monitoring on the baseline itself. Every alert opens a work order carrying its evidence, and the closing technician records the observed condition — which is what makes the next model revision possible.

Technology

The stack behind it.

  • C
  • FreeRTOS
  • Rust
  • MQTT
  • Python
  • Postgres
  • Grafana
  • Docker

Outcome

What the build achieves.

Illustrative outcomes from the demonstration environment. They describe the behaviour the design targets — they are not measured client results.

Edge autonomy
Feature extraction on-device; connectivity loss degrades resolution, not the record

Engineering outcome of the design. Illustrative, not a measured client result.

Alert accountability
Every alert opens a work order with its supporting evidence

Workflow design property.

Feedback loop
Technician-recorded condition closes the loop into the next model revision

Design constraint.

Detection lead time
Stated per failure mode during commissioning, against a measured baseline

Method, not a promised figure. We do not publish lead times we have not measured.

Demonstration figures — design intent, not client-verified

Start a conversation

Bring us the version of this that is actually yours.

We will read the constraint, say what we would change, and be direct about what we do not yet know.