You make a valid point, but this concern has been addressed by Symbotic's Maximo partner, JLL. JLL created a custom PM Forecast Mgr application that offers visibility to the anticipated labor and materials.
Original Message:
Sent: 03-11-2025 10:13
From: Darrell Thomas
Subject: 10% PM Compliancy using Maximo Application Suite
From the standpoint of Operations, generating the PM so few days in advance of the actual start time does not provide an opportunity for the planner/scheduler to develop a schedule based upon the availability of parts. If the items are not available in the storeroom, the negative impacts on scheduling are severe, and having too many items in stock is also not wise.
I had someone write a script to automatically populate the target finish date with a 20% compliance date giving 1.4 days for a weekly before it was considered late. I generated the PM with a lead time of thirty days (or an extra fourteen days in advance of the lead time of the storeroom item we chose not to stock it) to account for purchasing/procurement. The target start date was set for the day the PM was to be scheduled to start, and the target finish date was based upon the job plan factoring in the most frequent use. The logic to be considered is this: if the PM is generated monthly but is sequenced with an annual, you can't allow 65+ days to complete the annual because the monthly would have already generated twice more.
------------------------------
Darrell Thomas
Senior Asset Management Consultant
CHA Solutions, Inc.
Original Message:
Sent: 03-06-2025 08:09
From: Will Zurkan
Subject: 10% PM Compliancy using Maximo Application Suite
Hi Viet:
I did not explain the problem very well. The crontask doesn't run daily since the lowest cadence we have is seven days, the script runs every 5 days... making sure to update based on the next job plan sequence. At any rate, you make all valid points... Leadtime is rounded up to integer.
As for standard, I cite this excerpt here... where 10% PM compliancy is reference by reliability web:
https://reliabilityweb.com/tips/article/the-10-rule-of-preventive-maintenance#:~:text=The%2010%25%20rule%20of%20preventive%20maintenance%20simply%20states%20that%3A,it%20is%20out%20of%20compliance.
Essentially, the idea is that a 28 day (1M) PM has 2.8 days to complete, a 164 day (6M) PM has 16.4 days to complete. So, the objective is to have the report date as start and PM Due date as end... so the Target Start date is the actual date of PM schedule. I hope this makes better sense in terms of the objective. Again, the scripting seems to work fine but I find it complicated when 10% compliancy is so widely used... would be nice to have a checkbox that does it.
------------------------------
Will Zurkan
Symbotic
Original Message:
Sent: 03-05-2025 16:22
From: Viet Tran
Subject: 10% PM Compliancy using Maximo Application Suite
Why do you want to have PM generated accurately to the hours?
Your requirement doesn't sound "standard" to me. What industry standard does this come from? I've been through many Maximo implementations. The Lead Time field is an integer field, i.e. you can't entered 1.5.
Also, in most cases, the PM crontask is setup to run daily, thus even if you change the field to support decimal value, it still doesn't work. Of course, you can set the crontask to run every hour, but I advise against it. This is an expensive task and it can affect system performance. Anyway, none of this is "standard" to me.
The most common way I saw Lead time being setup is something like:
Weekly, Bi-weekly task: 3 days lead
Monthly, 6-monthly task: 7-14 days
Yearly task: 30 days
5-yearly task: 90 days
------------------------------
Viet Tran
Relia App Development & Consulting
https://relia.app
Original Message:
Sent: 03-04-2025 12:39
From: Will Zurkan
Subject: 10% PM Compliancy using Maximo Application Suite
10% PM Compliancy is an industry standard. That is, the idea that a 28 day work order will be created 1.4 Leadtime (for report date) before PM Start Date and 1.4 after for PM Target Due Date. Another example, a 84 day work order will be created 4.2 before Target Start Date and 4.2 for Target Due Date.
Yet, it is difficult to support this functionality as it requires scripting to set the Lead Time and PM Target Due Date. Lead times are whole integers. It just seems unnecessarily difficult for an industry standard. Ideally, MAS would have a checkbox to enable 10% PM Compliancy that would automatically create report, target start and due dates.
#EverythingMaximo
#Integrations
#IoT
#MaximoApplicationSuite
------------------------------
Will Zurkan
Symbotic
------------------------------