Skip to content

PREDICTIVE MAINTENANCE · MINING FLEETS · ENGINE HEALTH

Predictive maintenance for mining haul trucks.

I build multi-signal monitoring that reads every engine against today’s load and ambient conditions, not a fixed alarm limit. In production 24/7 at sea and in power plants; in a retrospective backtest on vessel history it flagged 11 of 12 developing failures, one week to five months ahead.

ONE CALL · ONE MACHINE · ONE MONTH OF DATA · NO COMMITMENT

  • IN PRODUCTION 24/7 AT SEA
  • MINING: READY TO DEPLOY
  • MADRID / REMOTE
EGT · CYL 4 · AT RATED LOAD · °CSTATUS: WATCH
EGT · CYL 4 · AT RATED LOAD · °CLine chart of exhaust gas temperature on cylinder 4 at rated load over the last 120 days. The measured signal drifts upward from about 415 to 456 degrees Celsius. A projected trend, drawn as a dashed line, crosses the 472 degree alarm limit in approximately 34 days. Illustrative data.ALARM LIMIT · 472 °CNOW420440460−120−80−400+40DAYS
TIME-TO-ALARM ≈ 34 DAYSMEASUREDPROJECTEDALARM LIMITillustrative data
  • MARINE

    IN PRODUCTION

    High-speed engines, generators and navigation on vessels at sea, tolerant of intermittent connectivity.

  • ENERGY

    IN PRODUCTION

    Power plants running around the clock: gensets, running hours, load and temperature under real operating conditions.

  • MINING

    READY TO DEPLOY

    Haul trucks and LHDs emit the same ECU signals over J1939/CAN. The approach reads that telemetry and sits alongside the OEM systems already on the fleet (Caterpillar VIMS, Komatsu KOMTRAX Plus, Epiroc Certiq, Sandvik OptiMine), touching nothing.

01

FIELD EVIDENCE

FAILURES FLAGGED IN BACKTEST *
11/12
ENGINE-YEARS OF HISTORY
25+y
MAX EARLY WARNING
160d
VESSELS · TWO INDEPENDENT FLEETS
3
* PROTOCOL
Retrospective validation on multi-year histories from three vessels in service: two independent fleets, more than 25 engine-years. On the second fleet the findings were written down before the failure log arrived.
NOTICE
Eleven of the twelve developing failures in the record were flagged ahead of the event, with one week to five months of warning.
THE ONE MISSED
The twelfth was a cooling-water pump that burst with no leading phase in the data. No trend system catches that one, and a vendor who claims otherwise is selling.
NOISE DISCIPLINE
At most one observation worth raising per engine per quarter. The most severe escalation level stayed practically silent across four years.
02

WHY TRUCKS ARE DIFFERENT

A marine engine ignores the weather. A haul truck cannot.

THE PHYSICS

A marine engine rejects its heat into seawater: thermally stable, effectively infinite. A haul truck rejects its heat into the air itself, and every degree of ambient rise spends cooling margin. Going from 15 °C to 40 °C costs about 25 degrees of cooling reserve, so a fixed alarm threshold is not really a threshold. It is a calendar.

THE PAYOFF

The failures most worth catching consume that same margin: dust-fouled radiators and intercoolers, low coolant, tired pumps, slipping fans. In winter the spare margin hides them; the first hot week exposes them all at once, as a wave of alarms that reads like noise. Score each signal against the value it should have today, in today’s conditions, and the climate turns from a source of false alarms into the input that sharpens real ones.

THE FLEET EFFECT

A fleet holds a reference a single machine never has: peers. Every truck in the pit works in the same weather, so when heat moves the whole fleet together, the unit that separates from the pack is separating for its own reasons. And the comparison keeps working in autumn, when falling temperatures pull a faulty unit back under the fixed limit and a threshold would go quiet.

COOLANT TEMP AT RATED LOAD · 8 TRUCKS · °CSTATUS: ONE UNIT SEPARATING
COOLANT TEMP AT RATED LOAD · 8 TRUCKS · °CLine chart of coolant temperature at rated load for eight haul trucks across twelve months. A shaded envelope holds seven healthy units that rise and fall together with the seasons, from about 83 degrees Celsius in winter to 96 in summer, close to but under the fixed 98 degree alarm. One unit, drawn in amber, tracks the pack through winter, separates from April onward, crosses the alarm limit in June and peaks at 102 in July. From October it drops back below the alarm as temperatures fall, while remaining about seven degrees above the fleet median. The gap from the fleet, not the alarm crossing, is the earliest and most persistent signal of the fault. Illustrative data.FIXED ALARM · 98 °CUNIT 07FLEET849096JANAPRJULOCTDEC
UNIT 07 · +7.7 °C VS FLEET MEDIANFLEET ENVELOPE · 7 UNITSFLEET MEDIANUNIT 07FIXED ALARMillustrative data

Summer pushes the whole fleet toward the fixed limit at once: that is the false-alarm season. Unit 07 crosses the limit in early summer, and by mid-autumn cooling weather has pulled it back under, so the fixed alarm goes quiet while the fault is still there. Against its peers it never stops being seven degrees adrift.

The faults you most want to catch only show themselves when it’s hot.

The season that produces your false alarms is the season that holds your real ones.

03

HOW I WORK

The full cycle, not a slice of it.

COLLECTMAPPREDICTACT

  1. 01

    Ingest

    Sensor & ECU telemetry: pressures, temperatures, load, running hours. Tolerant of intermittent connectivity.

  2. 02

    Store

    Time-series at scale: InfluxDB, PostgreSQL, retention and downsampling.

  3. 03

    Trend

    Per-signal health trends against reference behaviour, not raw thresholds.

  4. 04

    Project

    Time-to-alarm: when each signal will cross its limit, weeks ahead.

  5. 05

    Act

    Triage dashboards maintenance teams actually work with every day.

04

SELECTED WORK

2024–present

Real-time vessel monitoring platform

Integrated software + hardware platform monitoring high-speed engines, generators and navigation on vessels at sea. Continuous acquisition tolerant of intermittent connectivity, alarm processing and prioritisation, dashboards for crew and shore teams.

  • React
  • NestJS
  • InfluxDB
  • MQTT
  • Grafana
  • Docker

OUTCOME

RUNNING IN PRODUCTION ON VESSELS AT SEA · USED FOR WARRANTY VALIDATION

2023–present

Mobile apps, end to end

Personal and client apps, owned end to end: architecture, design, testing, deployment and production maintenance. Published on the App Store and Google Play with international distribution; subscription and payment flows, 2FA, SMS validation and ID verification.

  • SwiftUI
  • React Native
  • Expo
  • Firebase
  • TypeScript
  • Stripe/RevenueCat

OUTCOME

2M+ CUMULATIVE IMPRESSIONS ACROSS PUBLISHED APPS

2026–present

Predictive maintenance services

Per-signal engine trend analysis, fleet-wide condition classification, time-to-alarm projection and prioritisation of interventions. Ingestion of historical manufacturer data for retrospective degradation analysis; LLM-assisted analysis of engine charts.

  • NestJS
  • PostgreSQL
  • InfluxDB
  • AWS
  • Claude Agent SDK

OUTCOME

FAILURES CAUGHT AS TRENDS, WEEKS BEFORE ALARMS

2019–2025

Payments & enterprise systems

Earlier career across high-stakes enterprise software: real-time web platforms for digital entertainment, full-stack delivery at Solera, software architecture at Accenture, and high-volume banking and payment gateways at Worldline. Java/Spring microservices, backend architecture, deployment and monitoring.

  • Java
  • Spring
  • Microservices
  • Jenkins
  • Kubernetes
  • OpenShift

OUTCOME

THE RELIABILITY DISCIPLINE MACHINE HEALTH IS BUILT ON

05

APPS

Shipped to the stores, end to end.

Personal and client apps, designed, built, published and maintained by me. Every listing below is live; go press the buttons.

  • Loothy

    2026 · iOS

    Peer-to-peer messaging between iPhones over AirDrop and Bluetooth. No internet, no servers, no accounts; built for emergencies and offline situations.

  • VoleyScore

    2026 · iOS / Android / Web

    Volleyball scoreboard for live match points, sets and statistics.

  • Futsaleros

    2026 · iOS / Android

    Futsal team and match management: squads, stats, videos, push notifications and full season tracking.

  • Mowing Simulator

    2026 · iOS

    Relaxing lawnmower simulator with realistic mechanics and equipment progression.

  • Drill Simulator

    2026 · iOS

    Casual drill game with realistic physics, destructible materials and unlockable tools.

  • Lampost

    2025 · iOS / Android

    Second-degree social network: find people for services through your contacts and theirs. No spam, just trust.

  • Farmalendar

    2025 · iOS / Android

    Shift calendar for pharmacists: colour-coded shifts, automatic hours and monthly statistics.

  • We Are Go In

    2025 · iOS / Android

    Join and organise collaborative sporting activities with people nearby.

  • BurnBucks

    2025 · iOS

    Fitness with a rewards system: burn calories, earn points, cash them in.

  • Facenticator

    2024 · iOS

    Facial authentication via ARKit gesture recognition. Biometric security without fingerprints.

  • Grouppy

    2023 · iOS

    Create and manage friend groups and events: plans, voting and coordination.

2M+ CUMULATIVE IMPRESSIONSAPP STORE + GOOGLE PLAYINTERNATIONAL DISTRIBUTION

06

STACK

Data & telemetry
SAE J1939CAN busInfluxDBMQTTGrafanaPostgreSQLtime-series
Backend
NestJSNode.jsTypeScriptJavaSpringGroovymicroservices
Mobile
SwiftUIReact NativeExpoFirebaseTwilioStripeRevenueCat
Web
ReactNext.jsAngularTailwind
Ops
DockerKubernetesAWSOpenShiftJenkinsGitLab CITerraform
AI tooling
Claude Agent SDK
07

ABOUT

Before machine health I built enterprise software: real-time web platforms, full-stack delivery at Solera, software architecture at Accenture, and high-volume payment gateways at Worldline, where a failed transaction is a real problem for a real person. That is where the discipline comes from. Software that is tested, observable, and able to run unattended for months.

Since late 2024 I have been fully focused on machine health: engine telemetry, time-series storage, per-signal trend analysis and time-to-alarm projection for vessels and power plants. The same approach is ready for heavy machinery fleets, mining trucks and LHDs included, and it is brand-agnostic: I work with the ECU signals the equipment already emits (Sandvik, Caterpillar, Komatsu, Epiroc, Volvo) instead of asking anyone to replace hardware.

On the side I design, ship and maintain my own mobile apps, with over two million impressions across the App Store and Google Play. I am based in Madrid and work remotely. English C2. I like the problems where the data is messy, the connectivity drops, and someone downstream has to make a maintenance decision from what I put on screen.

08

WHERE TO START

Three steps, each one earning the next.

No new hardware, no downtime, no rip-and-replace: the platform reads the ECU and telemetry signals your machines already emit (J1939/CAN) and layers on top of the OEM system in place. Every step has an exit.

  1. 01

    Telemetry review

    Bring one machine and one month of data. I map signal coverage, baselines and alarm logic, and show you where fixed thresholds are hiding faults or creating noise.

    ONE CALL · NO COMMITMENT
  2. 02

    Historical backtest

    The same test the platform passed at sea, run on your fleet’s history: findings written down first, then compared against the failures your team actually logged. Your own data decides.

    YOUR DATA · VERIFIABLE
  3. 03

    Pilot on live telemetry

    A defined subset of the fleet, streaming live, with success criteria agreed before it starts. When the pilot earns it, scale to the rest.

    CRITERIA AGREED UPFRONT
09

CONTACT

Bring one machine and one month of telemetry.

I’ll review the signal coverage, baselines and alarm logic, then show you where fixed thresholds are hiding faults or creating noise. If your machines already log telemetry, the evidence is already sitting in your files.

REQUEST A TELEMETRY REVIEW