Dynamic Maintenance Plan based on completion of previous Maintenance

Hi Thilini, 

Thank you very much for your reply! I will start a trial right away. Would be amazing if it was that simple.

When you reference “Actual completion date of the last work order” do you know if that means when the WO was set into status “Work Done” for the first time? (Work Done status on all linked Work Tasks)

And my next question would be: How frequently does the system check whether the previous WO has reached that status? 

Kind regards, 
Adrian

Hi ​@Adrian P 

You are most welcome.

Even though the help text mention “Actual completion date of the last work order”, the system actually checks the connected work task. This is because in earlier IFS Applications versions, the direct connection was between the PM Action and the Work Order, but from App 10 onwards (including Cloud) the connection is between the PM Action and the work task.

For example, let's say you have a PM Action that aims to do the maintenance work once a month, then the due dates will be as follows.

Then let’s generate a work order for January.

Work order and task created and the PM Action true connection lies with the work task. See the source reference fields.

Now let’s say we add another task to the work order. This task has no connection to the PM Action.

Now let’s say I set the PM connected work task to “Work Done” on 10th January.

Now the maintenance plan gets adjusted according to the work completion date 10th January. Work order is still in started status with a pending work task. However, the PM connected work task is completed (Work Done) and it updates the maintenance plan.

Note: Please note that if 10th day falls on a holiday/weekend etc, then it is forward to the next working day. That’s why you see 12th May instead of 10th May.

Best Regards,

Thilini

Hi Thilini, thanks again for your clarification!

I was able to recreate what you described above and it seems to do the trick!

I have a follow up question from this:

We have started using the replacement function, which allows a PM Action to be superseded by other PM Actions (e.g. if you have to perform a monthly service on an asset, a 3 monthly service including additional tasks and a yearly service including even more tasks. In that case every 12 months three WO would be generated for the same point in time: one monthly, one 3-monthly and one 12-monthly WO. The replacement function allows to only generate the WO from the 12-montlhy PM Action)

We have found out that the generation of all WOs that are in a replacement relation needs to occur at the same time for the system to only generate the WOs from the highest ranking PM A. 

With the Date based option enabled and the target date for the next service moving with the actual completion of the last service , I assume the date of generating WOs from these PMs would also move and therefore get out of sync with the WO generation date of the replacing PM As. 

A bit confusing, but have you come across that in the past or any experience on it?  
 

Hi ​@Adrian P 

You are most welcome!

Regarding the follow up question, I have not come across that scenario in past, but I did some testing and yes, if both replacements and performed date-based options used, there can be confusion.

In your example, if the work order is generated from the 12-month PM Action, it would not be a problem since the dates in both PM Actions will get adjusted based on the actual finish date of the created work task. But if a work order is generated from 3-month PM Action, it will change the dates of that PM Action only and then the common dates in the 2 PM Actions will get changed.

However in such instances, we can still get the desired outcome, but manual intervention is needed. I.e the planner will have to adjust the due date of the common period manually so that same date is available in both PM Actions. Then the replacement functionality will work.

Best Regards,

Thilini