Skip to main content
Question

PM Maintenance plan is not considering already generated plan lines with WO in Status Released

  • October 9, 2026
  • 1 reply
  • 28 views
Do Gooder (Partner)

We are currently using PMs with Performed Date Based set to Yes. We have a customer scenario where this setting needs to be changed to No.

Our plan is to enable Revision Control and make the change to the active PMs. However, these PMs already have work orders (WOs) generated, and the WOs are in different statuses.

When we change Performed Date Based to No, the system adjusts the plan based on the Valid From date and Calendar criteria. 

In this concerned scenario, WOs have been generated for future maintenance periods as their lead time (30-day in below example). It looks like the system skips the months where the WOs are already in Finished status, as expected. However, it creates duplicate plan lines for months where a plan line already exists with an associated WO in Released status.
 


Please help to understand the best options other than marking duplicated lines Generatable = No 



 

1 reply

Do Gooder (Employee)
Forum|alt.badge.img+5
  • gleb.batov
  • Do Gooder (Employee)
  • October 21, 2026

Hi ​@Mithila Nuwan Rathnayake 

 

From what you've described, this looks like expected behavior when recalculating the maintenance plan after changing the PM logic.

When Performed Date Based is changed from Yes to No, the plan is regenerated based on the calendar definition and Valid From date. The generation logic typically treats completed occurrences differently from active WOs. Plan lines linked to Finished WOs can be recognized as completed maintenance events, while Released or other open-status WOs may still be considered future or active work and therefore do not always prevent a new plan line from being created for the same period.

I'm not aware of a standard option that automatically reconciles those open plan lines during this type of PM strategy change. In practice, customers often need to review the generated plan and either:

  • Set duplicate lines to Generatable = No, or
  • Clean up/restructure future plan lines before activating the revised PM

It would also help to know:

  • Which IFS Cloud version you are using?
  • Do the duplicate lines point to the exact same maintenance period and WO generation window?
  • Does the behavior occur for WOs in Released only, or also for Work Request and Under Preparation statuses?

Those details may help determine whether this is standard behavior or a defect.

 

Best regards,

Gleb

Terms & ConditionsAccessibility statement