Maximo Open Forum

 View Only

 Last PM Work Order Meter Reading - can it be set to when work order is completed instead of when it generated?

  • Assets
  • Customizations
  • Everything Maximo
  • Scheduling
  • Transportation
  • Work Management
Danny Richardson's profile image
Danny Richardson posted 03-29-2023 16:47

If the Oil Change is scheduled every 5,000 miles, but you actually run the vehicle 6,000, the Work Order will generate at 5,000 and so for the next work order it will generate at 4,000 having been run instead of 5,000, because the Work Order was generated at 5,000 but the work performed at 6,000.

Is there a way to automatically have the "Last PM Work Order Meter Reading" be set to when the Work Order is closed out instead of when it is generated?  The question has been posed to me by my leadership and so just seeing if Maximo can do this.  Thank you in advance.

Danny Richardson's profile image
Danny Richardson

I know there is something called a floating schedule for calendar based, but wondering what options are available for Meter based.  Thank you

Gina Leonard's profile image
Gina Leonard

Hi Danny,

When using a meter-based frequency in PMs, the meter value always drives the PM generation.  Unlike a time-based PM, the WO generates based only on the meter value against that asset.  So if the 5,000 mile oil change is done at 6,000, Maximo will act exactly as you described and generate the next PM WO after 4,000 miles. It is a fixed value that Maximo calculates from the frequency.   Hope this helps.

Thanks

Gina

gail smith's profile image
gail smith

It works are you expect.  However, if you don't do a meter reading between the time it the WO launches and the time you COMP it, it will look like it used the reading that generated the WO in the first place.  It looks for the closest reading before the WO hits COMP status and pulls that into the PM.

Maybe add a task line to the Job Plan requiring them to enter a meter reading as the last task before they complete the work...  

Subhransu Sekhar Sahoo's profile image
Subhransu Sekhar Sahoo

Hi Danny,

This is quite possible when you have a floating scheduled defined in your PM. 

you need to uncheck the "Use Last Work Order’s Start Date to Calculate Next Due Date?" checkbox in your PM, that will help you to use the later of the ‘Meter Reading Date’ field or ‘Last Completion Date’ field while calculating the Estimated Next due date.

You need to check below two check boxes :
  Generate Work Order Based on Meter Readings (Do Not Estimate) 
  Generate Work Order When Meter Frequency is Reached 
 Uncheck : Use Last Work Order’s Start Date to Calculate Next Due Date

For Example, PM generated a WO based on meter frequency value, maximo enters the meter reading date (i.e. Last WO generation date) in the Meter frequency tab. When the WO gets completed, maximo populates the "Last completion Date" in the Main Tab. 

if you have "Use Last Work Order’s Start Date to Calculate Next Due Date" checkbox unchecked, Maximo takes the later of the "meter reading date" and "last completion date" while calculating the "Estimated Next Due Date" for the next Wo generation. 

Hope this clears your doubt. You don't need to set the Last PM Work Order Meter Reading to Last completion date of WO. Maximo takes care of that I think.

Craig Kokay's profile image
Craig Kokay

Hi Danny,

As Subhransu mentioned, please use those settings.  It's not unusual to run a vehicle longer that the interval (5,000Km) that is defined on the PM.  Using those settings, when the PM is generated, in effect the PM is paused until the work order is completed.  I recommend that you take a reading as part of the work order steps.  This way when the work order is completed, it will take that reading being the last actual reading and it doesn't matter if it's taken from the work order or the asset, it just whatever is the last reading.

I would also recommend that you should also be looking if the asset is being maintained at the 5,000 interval.  Looking at your use case initially the asset is due at current reading + interval because vehicle usually don't start with zero on the odometer.  Say , 6,500 + 5,000 = 11,000.  When 11,000 is hit the PM will generate and pause.  When the vehicle comes in it's at 11,100 and of course doesn't 'move' during the maintenance (not allowing for testing).  So the next PM will be 11,100 + 5,000 = 15,100, but when the vehicle comes in, it's at 17,300.

So the initial PM was actually done at 6,100 and the next at 6,200 intervals.  So each exceeded the 5,000 interval.  By exceeding the recommended interval (5,000) there is an increased risk, is that acceptable?  Why is the vehicle exceeding by ~1,100.  Is it a high running vehicle?  Is it that just no one noticed?

Finally,  let me also put these thoughts out there noting you have made the PM floating.

  Generate Work Order Based on Meter Readings (Do Not Estimate) Means stop using the next due date.  it will still be calculated.  Also, it now pays attention to the meter reading.  If you have also set a meter-based lead then it will also use that.  You want to generate the PM when the meter hits the 5,000 interval, but in reality you need the work order generated 100 units before the 5,000 i.e. at 4,900. This gives you the time to recall the vehicle so that it's able to be in the maintenance bay at the 5,000 i.e. you don't exceed the interval.  That is an idealised goal, but if you don't do this, you can't achieve it.

  Generate Work Order When Meter Frequency is Reached  the work order will be automatically generated when the actual meter reading has reached or exceeded, nothing the meter lead.  You are not having to wait for the cron task, it's instant.