Skip to main content
Question

PM generation issue

  • March 16, 2026
  • 1 reply
  • 14 views
M
Sidekick (Partner)
Forum|alt.badge.img+3

We have a customer running IFS Cloud 23R2 who encountered the following scenario.

Their Preventive Maintenance (PM) plans are configured with Calendar + Criteria, where both Performed Date and Performed Value are considered.

In one instance, an incorrect measurement was entered for an object. This triggered the Condition-Based PM plan line and generated a Work Order. The Work Order was subsequently cancelled, and the incorrect measurement was invalidated/marked as incorrect.

However, the issue is that the PM plan continues to generate Work Orders, since the Generation Value on the PM Plan was not updated after correcting the measurement.
The current workaround is to regenerate the PM plan, which resolves the issue.

Although this is an infrequent scenario, the customer manages thousands of PM plans, and this situation occurs occasionally, requiring manual intervention each time.

We would appreciate guidance on the following:

  1. What is the exact background job/process that updates active PM plans based on newly entered measurements?

  2. How frequently should this job ideally be scheduled to ensure PM generation values remain accurate?

  3. Is there a recommended configuration or best practice to minimize manual intervention in cases where incorrect measurements trigger PM generation?

Any insights or best practices from the community would be greatly appreciated.

1 reply

jbush0419
Do Gooder (Customer)
Forum|alt.badge.img+3
  • jbush0419
  • Do Gooder (Customer)
  • March 16, 2026

​@Mithila N Rathnayake  this is a scenario many companies face when managing large volumes of condition-based maintenance plans.

Based on the IFS Cloud 23R2 architecture, here's what's happening and how to address it:

Background Process for PM Plan Updates

When measurements are entered in IFS Cloud, the system creates PM plan regeneration as a background job rather than updating immediately. This design prevents measurement entry delays, as the process expects quick response times. The background job is automatically triggered, but until it executes, the plan remains "out of sync."

The key background job to monitor is "Extend Plan for Calendar Generation" - you can check its execution status in the background job management interface. Active PM Actions are typically grouped into blocks of 500, creating several background jobs, and all must complete for the operation to finish properly.

Recommended Scheduling and Best Practices

For your scenario with thousands of PM plans, I'd suggest:

Frequency: Schedule the PM regeneration job to run daily or even more frequently (every 4-6 hours) depending on your measurement entry volume. This reduces the window where plans remain out of sync.

Configuration Tips:

  • Set up monitoring alerts for failed regeneration jobs
  • Consider batching measurement corrections during planned maintenance windows when possible
  • Implement a process where measurement invalidation automatically triggers a manual regeneration request

Addressing the Root Issue

The core problem you're describing - where the Generation Value doesn't update after measurement correction - suggests the background regeneration isn't consistently picking up invalidated measurements.

Immediate Actions:

  • Verify the background job scheduling is consistent and not failing
  • Check if there are any error logs when regeneration runs after measurement invalidation
  • Consider implementing a custom event or process that automatically triggers regeneration when measurements are marked invalid

Long-term Strategy:

  • Train users to manually trigger regeneration immediately after correcting measurements in critical scenarios
  • Implement a dashboard to identify PM plans that are "out of sync" for proactive management
  • Consider scheduling more frequent automatic regenerations during high measurement entry periods

The manual regeneration workaround you're using is actually the correct approach - the challenge is making it more automated for your scale.

Hope this helps! 

-jason

    Terms & ConditionsCookie settingsAccessibility statement