Self-directed project
Predictive Maintenance: Industrial ML for Fault Detection
Condition-Monitoring Engineer · AI / ML · July 2026
A ProoV case study · educational project, not employment
Built an end-to-end rolling-bearing fault detector using vibration snapshots, physics-based time-domain features, and a compact decision tree trained only on the training bearings. Evaluated it on held-out healthy and faulty bearings, reported catch-rate and false-alarm rate, and justified an alarm threshold with concrete maintenance-cost tradeoffs while identifying the fault as an outer-race/BPFO issue.
Graded against
- Feature engineering (signal to honest numbers)25%
- Held-out evaluation (honest measurement)25%
- Cost-based threshold decision + memo25%
- Compact model + embedded-budget justification15%
- Plain-language explanation10%
Passed · pass mark 60/100
What stood out6
- Trained a depth-1 decision tree on training bearings only and stated the node count against the embedded budget.
- Used held-out evaluation metrics with both catch-rate and false-alarm rate instead of relying on training performance.
- Wrote a decision memo that ties the threshold to explicit euro costs and identifies the outer-race/BPFO fault from the dominant defect frequency.
- Leakage-Free Model Training
- Honest Held-Out Evaluation
- Cost-Based Threshold Selection
The work I submitted18 tasks
10 tasks · 6.1k characters · Python · 8 written answers · 445 words
- Initial Prediction62 characters
- Load Plot Signal CodePython · 1.8k characters
- Load Plot Signal205 characters
- Example Rms WorkedPython · 697 characters
- Time Features143 characters
- Freq FeaturesPython · 1.2k characters
- Train Classifier363 characters
- Evaluation Heldout288 characters
- Threshold Decision334 characters
- Decision Memo1.1k characters
- Initial Prediction9 words
- Load Plot Signal Code163 words
- Load Plot Signal15 words
- Example Rms Worked72 words
- Time Features10 words
- Freq Features121 words
- Train Classifier31 words
- Evaluation Heldout24 words
Summarised on purpose — the submitted code and writing stay private so this page cannot be reused as an answer key. The full submission sits behind the verified certificate.