Skip to main content
Question

PM Grouping for Condition based PM Actions

  • May 27, 2026
  • 6 replies
  • 32 views
H
Sidekick (Partner)
Forum|alt.badge.img+5

According to the customer scenario, I created 3 PM Actions with the same starting value and intervals for 3 different objects, and then grouped them using a PM Group.

After that, measurements were entered for all 3 objects.

For PM 1 and PM 2, the entered measurements exceeded the threshold value. However, for PM 3, the measurement was below the Planned Value.

After running the condition generation job:

  • For PM 1 and PM 2, the same Work Request was created due to the PM Grouping.
  • For PM 3, no Work Request was created since the valid measurement was not met, which seems correct.

However, my concern is that since all 3 PM Actions are grouped together, is this the expected standard behavior? Should the system also create the same Work Request for the 3rd PM Action because it belongs to the same PM Group?

Could someone please clarify the standard system behavior in this scenario?

Thanks. 

 

 

6 replies

geirsigve
Hero (Employee)
Forum|alt.badge.img+9
  • geirsigve
  • Hero (Employee)
  • May 27, 2026

Hi,

Are you using PM Group or PM Grouping ID? These behave differently.

If you are using PM Group, work requests should only be grouped if the due date for the maintenance plan lines is the same.

Geir Sigve

H
Sidekick (Partner)
Forum|alt.badge.img+5
  • HoiLakshG
  • Author
  • Sidekick (Partner)
  • May 27, 2026

Hi I entered PM Group under PM Action as follows

 

geirsigve
Hero (Employee)
Forum|alt.badge.img+9
  • geirsigve
  • Hero (Employee)
  • May 27, 2026

Hi.

Then you should get one work order containing the work list items for each PM Action, IF the due date is exactly the same (i.e. due date being e.g. May 15, disregarding time).

What you should do is to check the Maintenance Plan for each PM Action and verify the Due Date and Wo No.  If the due date is the same for PM 1 and 2, and these have the same Wo No, while the Due Date is different for PM 3, and there is no, or a different Wo No for this PM Action, it works correctly.

 

Geir Sigve

H
Sidekick (Partner)
Forum|alt.badge.img+5
  • HoiLakshG
  • Author
  • Sidekick (Partner)
  • May 27, 2026

Thank you for the details.

  1. But For PM No 1 & 2 has the same Due Date while 3rd PM has a one-day difference. But still the same Work Order is created due to the PM Group.

PM 1

PM 2

PM 3

 

  1. What I explained previously was that for PM 1 and PM 2, the same Work Order was created due to the PM Group setup. However, for the 3rd PM, the Work Order was not created because the last entered measurement was 500, which did not reach the required threshold level, even though it has the same PM Group ID.

    My concern is whether the same Work Order should also be generated for the 3rd PM as part of the PM Group, despite it not reaching the required threshold value.

Further PM 1 & 2 has different due dates although it combines according to the PM Group

 

PM 1

PM 2

PM 3

 

geirsigve
Hero (Employee)
Forum|alt.badge.img+9
  • geirsigve
  • Hero (Employee)
  • May 27, 2026

Based on what I know, PM 1 and PM 2 are correctly grouped on WO 391154, while PM 3 should not be included.

WO 391155 should likewise not be grouped.

Looks like this needs some more detailed investigation

 

Geir Sigve

C
Do Gooder (Customer)
Forum|alt.badge.img+1
  • ChristianB
  • Do Gooder (Customer)
  • June 8, 2026

​@HoiLakshG 
this looks correct to me.

when you run “condition generation”, it should check if there is any generation values on the maintenance plan lines. As PM1 and PM2 has this, they should be generated as Work Orders. PM3 should not be generated as a Work Order, because you have not yet reached the triggering point.

Then when generated the system looks if they should be grouped or not. In this case, they should, so PM1 and PM2 will end up as tasks on the same WO.

Terms & ConditionsAccessibility statement