Corrective, Preventive and Predictive Maintenance: When to Use Each Strategy

Key takeaway

Understand corrective, preventive and predictive maintenance as different responses to asset risk, balancing failure consequence, maintenance cost and available condition data.

Explanation

Corrective maintenance responds after a defect or failure is discovered. It is appropriate for low-criticality assets where planned replacement after failure is economically acceptable. Preventive maintenance schedules work by calendar or usage interval to reduce failure probability before condition is known. Predictive or condition-based maintenance uses measurements, sensor data or analytical indicators to act when deterioration is detected.

The strategies are complementary. A plant may use preventive lubrication, predictive vibration monitoring and corrective response for noncritical accessories on the same production line.

Choose strategy from asset criticality, failure mode, detectability and economics. Preventive work performed too often can create unnecessary downtime and cost. Predictive programs require reliable sensor/measurement data and a response process; dashboards without maintenance actions create no value.

SAP supports these strategies through notifications, orders, maintenance plans, measuring points/counters and integrations with condition-monitoring solutions.

Reliability teams should review actual failure history to adjust strategy rather than fixing intervals forever at design time.

Real project scenario

A pump was serviced every month even though failures were rare and condition stable. Moving to quarterly preventive work plus vibration monitoring reduced downtime while still detecting bearing deterioration early.

Common mistakes

Assuming preventive is always better than corrective.
Buying sensors without response processes.
Using the same strategy for all assets.
Never reviewing maintenance intervals.
Measuring only maintenance cost, not failure consequence.

Best practices

Use asset criticality.
Match strategy to failure mode.
Review intervals with history.
Connect condition alerts to work execution.
Measure reliability and cost together.

Interview angle

Compare corrective, preventive and predictive maintenance and give one asset example for each.

Practice this lesson

Quick check

1. In the lesson "Corrective, Preventive and Predictive Maintenance: When to Use Each Strategy", consider this project situation: A pump was serviced every month even though failures were rare and condition stable. Which statement is correct?

2. As an architect designing a predictive maintenance capability that combines IoT sensor telemetry with Fiori-based analytics for asset strategists, what architectural decisions must you make regarding data latency, role-based access, and integration between the IoT platform and S/4HANA notification generation? Choose the response that best aligns with the expected SAP approach.

3. You are designing the work center strategy for a multi-plant PM implementation where maintenance crews are shared across plants but cost accounting must remain plant-specific. What architectural approach would you recommend for work centers and their linkage to task lists? Choose the response that best aligns with the expected SAP approach.

Interview questions

1. Using this SAP project situation — A pump was serviced every month even though failures were rare and condition stable — explain Corrective, Preventive and Predictive Maintenance: When to Use Each Strategy. What should happen, which concepts or process steps matter, and what common mistake would you avoid?

Answer it in your own words first, then compare.

2. How do maintenance strategies bridge corrective and predictive maintenance when IoT-based condition data is introduced into the planning process?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.