AI Predictive Maintenance

Hear the failure coming — 48 to 96 hours early.

Machine-learning models score every machine's health from 0 to 100 each day from vibration, current and thermal trends. When a component starts to degrade, you get the likely component, an estimated time-to-fault and the part to pre-order, so the fix lands in a planned stop.

Per-machine baselinesSpeed-aware frequency bandsConfidence on every estimateOn-premises models
VMC-04 · SPINDLE FRONT BEARINGLIVE
94
HEALTH SCORE
ENVELOPE SPECTRUMBPFO + HARMONICS
Component
Bearing 6206
Time-to-fault
48–96 h
Action
Sat. stop
ILLUSTRATIVE DATATICKET #M-2291 RAISED · PART PRE-ORDERED
48–96hTypical early warning before functional failure
60–80%Fewer breakdowns on monitored machines
0–100Daily health score for every monitored machine
1 tapFrom prediction to an owned maintenance ticket
Why calendar maintenance is not enough

Every unplanned breakdown was once a prediction nobody made.

Sudden

“It just failed”

Machines rarely just fail. They announce it in their vibration signature for days or weeks. Nobody was listening; now something always is.

Calendar

Servicing the wrong machines

Fixed-interval PMs service healthy machines and miss dying ones. Condition data puts the effort where the risk actually is.

Spares

The part that isn't there

The repair takes four hours; waiting for the bearing takes four days. A time-to-fault estimate buys you the procurement window.

The P–F interval

Failure is a slope, not a moment. The earlier you see it, the cheaper it is.

Between the point where a defect first becomes detectable (P) and the point where the machine stops doing its job (F), each signal shows up at a different time. Vibration is almost always first. Heat and noise arrive late, when the only choice left is an unplanned stop.

CONDITIONTIME → MACHINEWISE WARNS IN THIS WINDOW P · Vibration Current & load Temperature Audible noise F · Failure
Early · plannedDetected by vibration trend. Order the part, choose the stop, change it in hours already lost.
Late · rushedDetected by heat or a technician's ear. Days left at best; production is being traded for repair time.
At failure · unplannedDetected by the machine stopping. Repair plus the wait for parts plus whatever was in the machine.
Try it

Drag through thirty days of a bearing failing.

A spindle bearing develops an outer-race defect. Watch the health score, the defect band and what MachineWise tells your team on each day, long before anything is audible.

Health score
97
Defect-band energy
0.35 g
Estimated time-to-fault
—
HEALTHY

Health score · 30 days● today
Envelope spectrum · todayouter-race defect + harmonics

ILLUSTRATIVE MODEL OF A TYPICAL BEARING DEGRADATION · REAL CURVES VARY BY MACHINE, LOAD AND FAILURE MODE

How it works

Six steps from a sensor on a bearing housing to a part on the shelf.

01

Sense

Tri-axial vibration at the bearing positions that matter, plus current, temperature, speed and load.

02

Baseline

Each machine learns its own healthy signature, per speed range, over its first weeks of normal running.

03

Detect

Spectral bands tracked at the real running speed; sustained slopes flagged, single spikes ignored.

04

Score

Evidence fused into one health score, 0–100, per machine per day. Fleet ranked worst first.

05

Predict

Time-to-fault estimated as a range with confidence, and the likely component named where the signature allows.

06

Act

Ticket, parts list and a suggested intervention window around production. Outcome logged to sharpen the model.

What it detects

Failure modes, their signatures, and how early they show.

These are the wear-out failures that account for most of the cost of unplanned downtime on rotating equipment. Work out the defect frequencies for your own bearings with the bearing frequency calculator.

Failure modeSignature MachineWise tracksTypical lead timeWhat your team is told
Rolling-element bearingsEnvelope energy at the bearing defect frequencies (BPFO, BPFI, BSF, FTF)Weeks to daysComponent, band, trend and the bearing to order
ImbalanceRising amplitude at 1× running speed, mainly radialWeeksImbalance flagged with the speed it appears at
MisalignmentEnergy at 2× (and 3×) running speed, strong axial componentWeeksCoupling and alignment check recommended
Mechanical loosenessMany harmonics of running speed, raised noise floorDays to weeksMounting or foundation inspection
Gear wearGear-mesh frequency with growing sidebandsWeeksStage and gear pair where the signature allows
Lubrication breakdownHigh-frequency floor rising, with bearing temperatureDaysLubrication task raised before damage starts
Motor and drive faultsCurrent signature changes, load drift at constant workDays to weeksDrive or winding inspection
Thermal degradationLonger warm-up, higher steady-state temperatureDays to weeksCooling, chiller or filter service

LEAD TIMES ARE TYPICAL RANGES, NOT GUARANTEES. SUDDEN EVENTS (CRASHES, PROGRAM ERRORS) ARE NOT PREDICTABLE AND ARE HANDLED BY CRASH DETECTION AND DOWNTIME CAPTURE.

Your numbers

What are breakdowns on your critical machines costing?

Enter your own figures. The range applies the 60–80% reduction plants typically see on monitored machines.

Count hours from the stop to the machine running good parts again, including the wait for parts. Cost per hour is the contribution the machine would have earned, plus overtime or outsourcing to recover it.

Breakdowns cost you today, per year
—
Recoverable (60%)
—
Recoverable (80%)
—
Breakdowns avoided per year
—
Full downtime cost calculator →
The honest version

Predictive maintenance handles wear. It does not predict accidents.

Predictable, with warning

  • Spindle, motor, gearbox and fan bearings
  • Imbalance, misalignment and looseness
  • Gear wear and lubrication breakdown
  • Drive, winding and thermal degradation
  • Tool changer and axis mechanics that wear gradually

Not predictable, by nature

  • A crash from a program or setup error
  • A tool that breaks on a bad insert
  • An unclamped fixture or out-of-spec bar
  • Operator error and power events
  • Anything with no measurable build-up

Events like these are caught the instant they happen and recorded with evidence, which is a different job. Component by component on a machining centre: what is predictable on a CNC, and what is not →

The maintenance maturity ladder

Five ways to maintain a machine. One platform runs all of them.

Most plants run all five at once on different machines, and that is correct. A spare-rich pump can run to failure; a constraint CNC cannot. MachineWise lets each machine sit on the stage its cost of failure justifies.

Questions

Straight answers.

What is AI predictive maintenance?
AI predictive maintenance uses machine learning on condition data (vibration, current, temperature and load) to detect that a component has started to degrade and to estimate how long it has left. Maintenance then happens in a planned stop, before the failure, instead of after it. MachineWise turns this into a daily health score of 0–100 per machine, a time-to-fault estimate and a recommended action.
How early can MachineWise warn before a machine fails?
The typical early-warning window is 48–96 hours before functional failure, and slow wear such as bearing degradation is often visible for considerably longer. How early depends on the failure mode: fast failure modes give shorter windows, and events like crashes or program errors give none.
Which machines and components can it monitor?
Any rotating or reciprocating equipment where the expensive failures are preceded by measurable change: CNC spindles, ballscrews and axis drives, gearboxes, air compressors, motors, pumps and fans, hydraulic power packs, presses and furnace blowers.
Which sensors are needed?
Tri-axial vibration sensors on the bearing positions that matter, plus current and temperature where they add information. Where the machine controller provides running speed and load, that is used too, because defect frequencies move with speed. The sensor plan is set per machine, not as a fixed kit.
How do you avoid false alarms?
Each machine is compared with its own learned baseline rather than a handbook limit, alerts trigger on sustained trends rather than single spikes, frequency bands track the actual running speed, and every estimate carries a stated confidence. An alert that is often wrong gets muted, so precision matters more than sensitivity.
What is the difference between preventive, condition-based and predictive maintenance?
Preventive maintenance services a machine on a fixed trigger, such as calendar days, run-hours or cycle counts. Condition-based maintenance services it when a measured reading crosses a limit. Predictive maintenance goes one step further and estimates when the failure will happen, so the intervention can be planned. MachineWise runs all three, machine by machine.
How many breakdowns does predictive maintenance prevent?
Plants typically see 60–80% fewer breakdowns on monitored machines. The exact figure depends on how much of a machine's downtime comes from wear-out failures, which are predictable, rather than events, which are not.
Does the data go to the cloud?
No. Models run on your MachineWise server inside the plant and machine data never leaves your deployment.
Ready when you are

Instrument one critical machine. See its health score within weeks.

Start with the machine whose breakdown hurts most. Two machines, thirty days, zero cost to start, with your data on-premises throughout.

Get a call back within one working day
No spam, no call centre. An engineer calls you.
FREE 2-MACHINE PILOT
Live OEE on two of your machines — this week. ₹0 to start.
Software-first setup in under an hour each · your data stays on-premises · plant-specific ROI model included.