Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



PM & Job Plan Best Practices

From: (2014-03-04 13:46)

We’ve been using Maximo for about 20 years now and for the most part have just been doing the upgrades and continuing to use the application the way we always have and likely missing out on probably a lot of major improvements. I’ve been tasks to take a detailed look at the PM and Job Plan modules and identify these potential areas for improvement. Spent the better part of a couple days combing through IBM’s websites trying to find some good detailed documentation on recommendations on developing Job Plans and PM without much luck. I’ve read some of the older posts here as well but was hoping maybe someone could point me to some documentation on developing and setting up PM’s and Job Plan. Or even some best practices that you have developed and are willing to share.
We are on 7.5 SQL Server
Thanks in advance, I look forward to seeing your suggestions
Larry


From: wwilliams (2014-03-04 14:53)

Hi Larry,
In 20 years you should have a history of breakdowns and resolutions. I would start there and also get with your skilled trades. If you have used failure codes, Brandon should be able to put together reports which would provide you the information that should point you in the right direction as far as what breaks and how frequently.
If you didn't have failure codes and the breakdown descriptions on the work orders were more than "broke" etc. Those descriptions could be grouped, in both cases a frequency should become obvious.
Interviewing the skilled trades should give you although sometimes anecdotal information from their perspective on what they think needs the most attention. 
What kind of equipment are we talking about? Anything rotating should have information available. There are many other variables that can determine the PM frequency and job plans, it will just take some work, but with 20 years of history you should have a wealth of information to help.
Back in the day when we had new machining cells purchased we had vibration sensors added to each axis so the techs could first take the baseline then as part of the PM measure and compare.
I may have some old examples from my days at Sundstrand (I doubt I can find them), or I can reach-out and see if they will share.
-Wes
________________________________
From: "larry.mccown@ngc.com" <larry.mccown@ngc.com>
To: MAXIMO@yahoogroups.com
Sent: Tuesday, March 4, 2014 3:46 PM
Subject: [MAXIMO List] PM & Job Plan Best Practices

 
We’ve been using Maximo for about 20 years now and for the most part have just been doing the upgrades and continuing to use the application the way we always have and likely missing out on probably a lot of major improvements.  I’ve been tasks to take a detailed look at the PM and Job Plan modules and identify these potential areas for improvement.  Spent the better part of a couple days combing through IBM’s websites trying to find some good detailed documentation on recommendations on developing Job Plans and PM without much luck.  I’ve read some of the older posts here as well but was hoping maybe someone could point me to some documentation on developing and setting up PM’s and Job Plan.  Or even some best practices that you have developed and are willing to share.
We are on 7.5 SQL Server
Thanks in advance, I look forward to seeing your suggestions
Larry 


From: (2014-03-04 15:14)

Hello Wes,
Would be nice to get predictive maintenance on our radar but I’ve had a hard time convincing management to stress the need and follow up on work order closed without failure code. If you recall in Maximo 4.0.3 we were able to force the little popup screen forcing users to enter failure codes but from 6.2 on I’ve had difficulty stressing the need for it. But really my current issue is just identifying how PM’s and Job Plans should be built not specifically for what equipment.
We’ve been on 7.5 for about 10 months and just recently uncovered within the PM module “Target Start Time” and the ability to auto assign work orders to laborers. Just today I was asked about the Start and Finish Constraint Offset and there purpose and use, I’ve reviewed PM Forecasting and Nested Job plan but not finding “user friendly” documentation on them.
So in a roundabout way I’m looking for documentation on how to use the PM and Job Plan modules just as if we were a new company planning on using the PM and Job Plan modules for the first time. Or what has worked or not worked from others
Thanks for the feedback


From: (2014-03-05 14:44)

It sounds like Constraint Offset is a tolerance that is allowed to start work earlier than your target start or to end later than your target finish.


http://thrue.org/javadocs/Javadocs7500/psdi/app/workorder/WO.html http://thrue.org/javadocs/Javadocs7500/psdi/app/workorder/WO.html calculateConstaintDates

Uses the passed Start and Finish Constraint Offsets, if any, and the workorder's target dates, if any, to calculate the constaint dates, if possible. The start offset is subtracted from the target start to determine the start constraint; the finish offset is added to the target finish to determine the finish constraint. Without a start offset, the start constraint cannot be calculated; without a finish offset, the finish constraint cannot be calculated. There must be at least one target date. If the target finish is null, the finish constraint is calculated as the target start plus the passed wo duration plus the finish offset, and similarly for the start constraint if the target start is null. WODur may be either a jpduration, if a jobplan is involved, or an estdur, if one isn't.


---In MAXIMO@yahoogroups.com, <larry.mccown@...> wrote :

Just today I was asked about the Start and Finish Constraint Offset and there purpose and use, I’ve reviewed PM Forecasting and Nested Job plan but not finding “user friendly” documentation on them.





From: Ian Wright (2014-03-06 08:08)

I have done away with target start dates and work on scheduled dates and the target finish is the drop dead date after which its in backlog this effectively gives me float. Depending on the duration of the PM I set the SNET date the FNLT is always set to 0

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of swkim@getty.edu
Sent: 05 March 2014 22:45
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] PM & Job Plan Best Practices


It sounds like Constraint Offset is a tolerance that is allowed to start work earlier than your target start or to end later than your target finish.

http://thrue.org/javadocs/Javadocs7500/psdi/app/workorder/WO.html
calculateConstaintDates

Uses the passed Start and Finish Constraint Offsets, if any, and the workorder's target dates, if any, to calculate the constaint dates, if possible. The start offset is subtracted from the target start to determine the start constraint; the finish offset is added to the target finish to determine the finish constraint. Without a start offset, the start constraint cannot be calculated; without a finish offset, the finish constraint cannot be calculated. There must be at least one target date. If the target finish is null, the finish constraint is calculated as the target start plus the passed wo duration plus the finish offset, and similarly for the start constraint if the target start is null. WODur may be either a jpduration, if a jobplan is involved, or an estdur, if one isn't.


---In MAXIMO@yahoogroups.com, <larry.mccown@...> wrote :

Just today I was asked about the Start and Finish Constraint Offset and there purpose and use, I’ve reviewed PM Forecasting and Nested Job plan but not finding “user friendly” documentation on them.



GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.

**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
**************************************************************************************************************