Phone: 0850 346 41 09  |  Weekdays 10:00–18:00 · Technical support 24/7

🇹🇷 TR

Digital Bridge Blog

Industry 4.0

What Is Predictive Maintenance? How It Works, Predictive vs Preventive, Costs and Pilot Steps

What is predictive maintenance and how does it work? Differences from preventive maintenance, sensor data, cost drivers, savings data and a 6-step pilot plan.

12 min read  · Digital Bridge Engineering Team
What Is Predictive Maintenance? How It Works, Predictive vs Preventive, Costs and Pilot Steps

Predictive maintenance is a maintenance strategy that monitors vibration, temperature and motor current with sensors, spots the drift towards failure early and schedules maintenance when the machine actually needs it. Reactive maintenance acts after a breakdown and preventive maintenance follows a calendar; predictive maintenance relies on the machine's own data, cutting unplanned downtime, needless part changes and emergency labour.

Key takeaways

  • Predictive maintenance bases maintenance decisions on a machine's vibration, temperature and current data rather than the calendar, so failures are caught while developing.
  • According to Siemens' The True Cost of Downtime 2024, the 500 largest companies lose almost $1.4 trillion a year to unplanned downtime.
  • The US Department of Energy (DOE) guide says a properly functioning predictive maintenance programme can save 8–12% over preventive maintenance alone.
  • Predictive maintenance is not needed for every machine; the real value lies in critical equipment whose failure is expensive and stops the line.
  • The safest start is a pilot on one to three critical machines, with success metrics such as unplanned downtime hours measured beforehand.

Why scheduled maintenance is not enough

In most plants, maintenance swings between two extremes. When a critical pump or compressor fails, the line stops, the maintenance team switches into emergency mode, a supplier is chased if the spare part is not on the shelf, and overtime is booked. Afterwards the reflex is to tighten the preventive schedule: bearings are swapped at fixed hours even when they are healthy, and machines that are running well are stopped for service.

Preventive (scheduled) maintenance is progress, but it has two blind spots. It misses failures that begin before the scheduled date, and it spends money and production time replacing parts with life left in them. Maintenance managers often cannot answer a simple question: "Is this machine in better or worse shape today than it was last month?"

Predictive maintenance answers that question. A baseline of normal operation is established, deviations from it are tracked, and maintenance decisions follow the machine's actual condition rather than the calendar. In our Industry 4.0 roadmap for SMEs, this is the prediction stage that follows data collection, visibility, production management and quality.

How much does unplanned downtime cost?

Unplanned downtime is the most expensive outcome of a maintenance strategy and the core loss that predictive maintenance targets.

According to Siemens' The True Cost of Downtime 2024, the world's 500 largest companies lose almost $1.4 trillion a year to unplanned downtime, equivalent to 11% of their revenues.

The same 2024 Siemens report finds that large plants average 25 unplanned downtime incidents a month (42 in 2019) and lose 27 hours of production a month (39 in 2019). According to the report, an hour of unplanned downtime costs $2.3 million in a large automotive plant and $36,000 in fast-moving consumer goods (FMCG) plants. The good news: nine out of ten respondents now do some form of condition monitoring, and almost half have dedicated predictive maintenance teams.

The most widely cited official source on the returns from predictive maintenance is the US Department of Energy's (DOE) maintenance guide. The U.S. Department of Energy Operations & Maintenance Best Practices Guide, Chapter 5 (2010) states that a properly functioning predictive maintenance programme can save 8–12% over preventive maintenance alone, and that facilities relying heavily on reactive maintenance could see savings opportunities above 30–40%.

Independent surveys cited in the DOE guide report industry-average reductions of 35–45% in downtime and 25–30% in maintenance costs. These are averages, not promises for every site, but the direction is clear.

What is the difference between reactive, preventive, condition-based and predictive maintenance?

The key question that separates the four maintenance strategies is what triggers the work:

StrategyWhat triggers the work?StrengthWeakness
Reactive (run to failure)The machine breaks downNeeds no planningUnplanned downtime, emergency labour, secondary damage
Preventive / scheduledCalendar or running hoursSimple and predictableMisses early failures, replaces healthy parts
Condition-basedA measured value crosses a thresholdLooks at real conditionPoorly set thresholds alarm too late or too often
PredictiveData trends and model forecastsSees failures developing, makes maintenance plannableRequires sensors, data infrastructure and analytical discipline

Predictive maintenance is not needed for every machine. For cheap, redundant equipment whose failure does not affect output, run-to-failure can be a deliberate and sensible choice. The real value lies in critical equipment whose failure is expensive and stops the line.

Which data and sensors does predictive maintenance use?

In predictive maintenance, the signal to monitor is chosen according to the equipment's failure mode. The four most common data types and the problems they reveal early are:

Monitored signalWhat it reveals earlyTypical equipment
VibrationImbalance, misalignment, looseness, bearing and gear damageMotors, pumps, fans, gearboxes, CNC spindles
TemperatureOverheating, lubrication problems, friction, hot connection pointsBearing housings, motor casings, electrical panels, transformers
Motor currentLoad changes, mechanical strain, jammingMotors, conveyors, compressors
Oil qualityWear particles, contamination, oil degradationGearboxes, hydraulic systems, compressors

A single signal is often not enough: vibration rising together with temperature is a stronger sign of failure than either changing alone. That is why several signals are monitored together on critical machines.

How does predictive maintenance work?

The predictive maintenance process runs in four steps:

  1. Sensor installation: vibration, temperature, current and, where relevant, oil-quality sensors are fitted to critical equipment such as motors, pumps, compressors, bearings and gearboxes. Wired or wireless connections are both options; for remote or scattered equipment we compare the choices in LoRa vs NB-IoT vs cellular.
  2. Continuous data collection: sensors generate data at a defined sampling rate; an edge gateway on site pre-processes it and forwards it to the server. Why that pre-processing happens on site is explained in edge computing in manufacturing. If the internet connection drops, a local buffer takes over.
  3. Analysis: first, a baseline of normal operation is established. An AI model then evaluates changes in the vibration spectrum, anomalies at bearing frequencies and temperature rises together. Technical detail such as which fault shows at which frequency, ISO 20816 limits and sensor choice is covered in vibration analysis for fault detection. The approach that combines sensor data with a physical model of the machine to test scenarios is discussed in our digital twin article.
  4. Alerts and action: when a threshold is crossed, the maintenance team receives an email, SMS or app notification; with integration into a computerised maintenance management system (CMMS), a work order opens automatically. How a predicted failure becomes a work order assigned to a technician, with parts and time recorded, is covered in our field service management guide.

The least discussed gain from the predictive maintenance cycle is planning. When a failure is spotted while it develops, the work can be moved to a shift break or weekend when production stops anyway, spares arrive on normal lead times rather than by emergency order, and a prepared team does the job instead of a technician called out at night. So measure the value not only in avoided failures but also in the share of interventions that became planned. A mobile service report app that records fault types and readings consistently on every visit becomes one of the data sources for this analysis.

What does predictive maintenance cost?

The cost of predictive maintenance is set by the scope of the project, not by an off-the-shelf package price. The main budget drivers are:

  • Number of machines and measurement points: how many machines are monitored, and at how many points on each.
  • Sensor types: which of vibration, temperature, current and oil-quality sensors are needed.
  • Connectivity: wired or wireless connections and the number of gateways on site.
  • Analysis method: simple threshold and trend tracking, or an AI model that evaluates several signals together.
  • Integration: data exchange with a computerised maintenance management system (CMMS), MES or ERP.
  • Existing machine infrastructure: reading data from a machine with a PLC is a different workload from fitting external sensors to an older machine.

Digital Bridge does not sell off-the-shelf packages; after a needs analysis it prepares a written proposal covering scope, phases and price. The most effective way to keep costs under control is to limit the scope to critical machines and start with a pilot.

Where to start with predictive maintenance: a six-step pilot plan

  1. List your critical equipment. Rank machines whose failure stops the line, that have no standby and that take a long time to repair.
  2. Review two years of breakdown records. Which equipment failed, how often and why? If there are no records, that is a finding in itself.
  3. Choose one to three machines for the pilot. Equipment with a failure history and failure modes that show up in vibration or temperature is ideal.
  4. Define success up front. Measure unplanned downtime hours, emergency call-outs, mean time between failures (MTBF) and similar metrics before the pilot starts, so there is a baseline to compare against.
  5. Bring the maintenance team into the process. Write down who checks what when an alert arrives and at what level a planned stop is scheduled; otherwise alerts get ignored.
  6. Scale on the evidence. Roll out to other lines for the equipment types where the pilot proved its value; for adding sensors to older machines, see retrofitting legacy machines.

Tracking downtime alongside OEE (overall equipment effectiveness) is the easiest way to translate gains into production terms; we show the calculation step by step in how to calculate OEE.

Common mistakes in predictive maintenance projects

When predictive maintenance projects fail to deliver, the cause is usually execution rather than technology. These are the mistakes we see most often on site:

  • Putting sensors on everything. Covering non-critical equipment raises costs, multiplies alerts and scatters the team's attention. Keep the scope to machines whose failure is expensive.
  • Setting alarms before learning normal behaviour. Every machine has its own vibration and temperature signature. Thresholds taken from a catalogue alarm either too late or too often; collect a few weeks of normal operating data first. Methods that learn normal behaviour and catch deviations are covered in our anomaly detection guide.
  • Leaving alerts without an owner. If it is not written down who looks at an alert, how quickly, and when a planned stop is triggered, the system gets ignored after the first few false alarms.
  • Separating data from maintenance records. If sensor data and the work actually done are not kept together, you cannot measure the model's accuracy or improve it over time. Record "what was found?" after every intervention.
  • Scaling without measuring. If downtime hours and emergency call-outs were not measured before the pilot, nobody can say whether it worked. The roll-out decision should rest on comparison, not impressions.
  • Leaving networking and security for later. Sensor gateways connect to the production network; which device reaches which network, and how, must be designed from the start (OT security for SCADA).

What these predictive maintenance mistakes have in common is that the project should be managed as a change to the maintenance process, not as an equipment purchase.

Where else is predictive maintenance used beyond the factory?

The same predictive approach works for energy losses as well as machine failures. We cover catching leaks early from compressor and pipework data in our article on compressed air leak detection.

Usage-based maintenance works in hospitals as well as factories: servicing planned on real run hours means fewer medical devices pulled out of use just because the calendar says so. We explain the approach in our article on hospital medical equipment tracking.

How Digital Bridge runs predictive maintenance projects

We run predictive maintenance projects on a start-small, scale-on-evidence basis:

  • A free site assessment. For Industry 4.0 projects we review your critical equipment list, breakdown history and existing infrastructure on site, at no charge.
  • A pilot on one to three critical machines. We keep the pilot tight so that you see the system's value in concrete metrics within the first 30–60 days, and you decide on roll-out based on that data.
  • One team from sensor to dashboard. Software and hardware come from the same team: where needed, our device manufacturing and IoT engineers handle electronics design, enclosures and embedded software, and technical feasibility for hardware is free.
  • Analysis and alerts. We build the normal operating profile, track deviations with anomaly detection models and deliver alerts to your maintenance team by email, SMS or app notification.
  • Integration with what you already run. We connect to our remote monitoring platform for dispersed sites, to MES on the production side, and to your maintenance management system.

For the equipment types we monitor and how the pilot runs, see our predictive maintenance page.

Cutting unplanned downtime enlarges usable capacity without new investment; our manufacturing capacity planning guide shows how that feeds into the calculation.

Next step: find your pilot candidate

This week, sit down with your maintenance lead for half an hour and list the three breakdowns that stopped the line longest in the past year. For each one, ask: was there an early warning sign, such as noise, heat or rising current? If the answer is yes, that machine is your pilot candidate. Get in touch and we will define the pilot scope together during a site assessment.

To see how maintenance fits with production, quality and energy, browse our complete Industry 4.0 guide.

Let us look at your case

Tell us about your process; after a needs analysis we send a written proposal with scope, phases and cost.

Request a Quote 0850 346 41 09
Questions we hear most often

Frequently Asked Questions

What is the difference between predictive and preventive maintenance?

Preventive (scheduled) maintenance replaces parts according to the calendar or running hours, without looking at the machine's actual condition. Predictive maintenance continuously monitors data such as vibration, temperature and current, spots the drift towards failure early and schedules maintenance when it is needed. It catches early failures and avoids replacing healthy parts.

Which machines are suitable for predictive maintenance?

Rotating equipment whose failure is expensive, stops the line and has a measurable failure mode is the best candidate: motors and gearboxes, pumps, compressors, fans, CNC spindles, conveyors, transformers and generators. For cheap, redundant equipment, run-to-failure may be more economical. Base the choice on the hourly cost of downtime and the repair time.

What does predictive maintenance cost?

The cost of predictive maintenance is set by scope rather than an off-the-shelf package price. The main drivers are the number of machines and measurement points, the sensor types, wired or wireless connectivity, whether threshold tracking or an AI model is used, integration with maintenance management and MES systems, and the machines' existing infrastructure. Limiting scope to critical machines and starting with a one-to-three-machine pilot keeps costs under control.

How much can predictive maintenance save?

Savings depend on where a site starts. According to the US Department of Energy's maintenance guide, a properly functioning predictive maintenance programme can save 8–12% over preventive maintenance alone, and facilities relying on reactive maintenance may see opportunities above 30–40%. Surveys cited in the guide report average reductions of 35–45% in downtime and 25–30% in maintenance costs; these are industry averages, not guarantees.

Can predictive maintenance be applied to older machines?

Yes. Vibration, temperature and current sensors can be mounted externally without touching the machine's control system, so predictive maintenance also works on machines with no PLC or on older generations. Connectivity and data transfer are designed around the site, with wireless sensors and gateways where cabling is difficult.

How soon do predictive maintenance results appear?

A baseline of normal operation has to be established first. Digital Bridge starts pilots with one to three critical machines and aims for the value to be visible in metrics within the first 30–60 days; the roll-out decision is based on those results. On equipment that fails often, the first early warnings usually appear within that window.

Is AI essential for predictive maintenance?

Simple threshold and trend tracking already delivers value at the start. AI models improve the accuracy of early warnings by evaluating several signals together and catching small deviations from the normal profile. The right method depends on the equipment and its failure modes; most projects start with thresholds and move to models as data builds up.

Have a different question? Ask Us

Talk to an Engineer

Tell us what you need to solve. We'll come back with a written proposal.