Maximo Open Forum

Scenario:  an asset with some time-based PMs is taken out of service for 3 months.

Problem:  ideally, all of the time-based PMs would be automatically pushed back 3 months, to account for the outage.

Current Solution:  put Extended Date in all of the PM schedules.

However, this requires a user to go through all of the PM schedules and make manual changes.  Does anyone have a way of doing this automatically? 

TIA for any ideas!

TBH, I always go through the PM schedules and make manual changes like you said.  However, assuming you use automatic PM generation, maybe you could go into the Org Settings --> PM Options and change the Where Clause on the PMWoGen, so it filters them out? (Just remember to go back and undo that later!)

Hey Travis!  Long time no talk to!  

That gives me an idea - we could add a PM status called PAUSED, and then tell Maximo not to generate those ones.

But I don't think that would work, because Maximo  would still follow the same schedule, right?  Once they change back to ACTIVE, they would come out right away, instead of, say, 3 months after the machine came up.

A couple of suggestions that come top of mind from a technical perspective

1. Use Graphical Scheduler and define a query for your PMs based on the Assets for your outage. You can then easily see what is coming do and move them to new dates.
2. Use MXLoader or Application Import/Export to extract the Assets modify the dates and push it back in

I would also ask the question that even though there is an outage and the Asset is down likely due to the outage, some organizations still want to keep the the time based PMs on that schedule whether the Asset is in use or not. I'm sure there would be a good debate on this topic from a functional perspective. 

Mike

Hi Michael:  thanks for the idea about using Scheduler.  We actually don't use a scheduling tool right now since our scheduling is too primitive, but it's an area that's been targeted for improvement.  I'll pass that on ..

Yes, I expect that we have some PMs that AREN'T supposed to be paused, in addition to those that do.  There really should be a debate in Maximo functional circles over this - I could see an option being added to the PM record along the lines of "pause this PM when the asset is down", maybe.  Maximo would then use the asset status or the downtime status to adjust the PM schedule as needed.  (I can see some flaws already, but it's a starting point.)

Making use of Seasonal Dates-> Active Dates could be one way if it matches the business. A quick example as above. Generate a forecast and observe that PM is not set to generate for the inactive months