Hi Scott,
There are misconceptions about how meters work. After setting the initial LTD say 200hrs, you then have a freq=200. So that means the WO is ready at 400hrs, but of course the next answer depends if this is fixed or floating. When floating, the next date that the PM will generate doesn't exist until the WO is completed. At this point, the value for the next PM is based on the current LTD value + Freq. So if you have taken additional readings between generating the PM and completing the WO, its all about the last reading.
If it's fixed, then the PM's will always generate based on the Freq.
In both cases the forecast does require an average for the forecast.
I have a doc explaining this in better detail, but happy to have a chat.
------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================
#IBMChampion2022
------------------------------
Original Message:
Sent: Fri July 07, 2023 03:33 AM
From: Scott Taylor
Subject: Preventive Maintenance Units to Go showing Negative Value
I too am a little interested in this as we had a very similar scenario.
From what I understand, because we are not [re]setting the meter back to zero as a part of updating the work order meter value that is linked to the PM (updating meter value directly via the Location application), Maximo is calculating how long till we reach the PM frequency, which is now in the past (-50 in your example). As we're looking at introducing rotating assets at the moment, I don't want to lose the life-to-date meter value for the asset, but want it refurbished say every 10,000 hours of use. This has also affected our PM forecasting as it doesn't appear to be picking up the correct values from the latest location meter reading, but more what is recorded on the PM as the last reading?
My initial reading/understanding was the PM would act like car servicing, eg every 12 months or 15,000kms, whatever comes first, and then keep checking this as the meter was updated. However, when we go past the 15,000kms, it starts wanting to use negative numbers to reach the frequency.
The formula provided to me was:
New Next Meter Reading = (Life to Date Next Meter Reading - Life to Date) + New Reading
PMMETER.READINGATNEXTWO = (PMMETER.LTDREADATNEXTWO - LOCATIONMETER.LIFETODATE) + LOCATIONMETER.LASTREADINGNEW
Looking forward to any reference material / examples people may have on this as I'm still a little confused.
Regards,
------------------------------
Scott Taylor
Specialist Business Systems
Port Waratah Coal Services
Original Message:
Sent: Wed July 05, 2023 10:46 AM
From: AYAN DE
Subject: Preventive Maintenance Units to Go showing Negative Value
We have a Meter based Preventive Maintenance with frequency as 100 units. We have all 3 checkboxes checked ( Use Last Work Order's Start Date to Calculate Next Due Date? , Generate Work Order Based on Meter Readings (Do Not Estimate)? and Generate Work Order When Meter Frequency is Reached? ).
PMWOGENCRONTASK is not running.
We also have the Asset Meter Rolldown from Location.
Transaction : We are entering Meter Read as Delta (150) in the Location Application. Meter Read is greater than the Frequency 100.
Observation : Automatic Workorder Generation is happening. But in the Next Work Order Projection section of the PM ; Next Meter Reading is not updated. Also and Units to Go is negative. (-50)
Expectation : As workorder is generated Next Meter Reading should be 250. Units to Go should be. (100)
Attachment : Attached
------------------------------
AYAN DE
------------------------------
