Maximo Open Forum

We have some cases recently where the time-based PMs are not triggering properly - namely, they're creating work orders early.  When looking at the Earliest Next Due Date, I can see that it's incorrect, but the only way I've found to change it is by changing the frequency units temporarily and then changing them back again.

This problems seems to have started when we started using the PM forecast on a regular basis, so I'm suspicious here.  We're NOT using the PM forecast to set the next due date, so it shouldn't be related, but I'm not sure about this.  It seems to me we had a problem like this a few years ago when we tried to use the PM forecast before.  We stopped using PM forecasting, and only started using it again recently.

Maximo version:  7.6.0.9

If anyone has any insight into this, I'd appreciate it.

Thanks.

We have some cases recently where the time-based PMs are not triggering properly - namely, they're creating work orders early.  When looking at the Earliest Next Due Date, I can see that it's incorrect, but the only way I've found to change it is by changing the frequency units temporarily and then changing them back again.

This problems seems to have started when we started using the PM forecast on a regular basis, so I'm suspicious here.  We're NOT using the PM forecast to set the next due date, so it shouldn't be related, but I'm not sure about this.  It seems to me we had a problem like this a few years ago when we tried to use the PM forecast before.  We stopped using PM forecasting, and only started using it again recently.

Maximo version:  7.6.0.9

If anyone has any insight into this, I'd appreciate it.

Thanks.

Hi Shannon,

There is some key information left out.  Namely, are the PM's meter or day-based? 

That said, when you're using the PM forecast, the PM generation now uses that information.  There are some great articles by Andrew Jeffery see Maximo Secrets and there is information from IBM using this link.

In essence, it takes over when the PM is to generate based on the forecast date.

There are rules around when a forecasted date is calculated, and it may be that you've not noticed that the forecasted date is different to the earliest due date.

For both types of PM have you set the generate ahead by (or leadtime).  Remember this says to the system to decrease the interval when the PM is generated.  Note, that this does not affect the target start date of the PM, it's just that you've said "I need 10 days before working on the PM to schedule and organise materials (or the like)".

For meter-based PMs it is recommended that you delete and regenerate the forecast regularly (i.e. daily) as the meter average units vary each time the reading is taken.  We've found that it is very important to delete, and then regenerate because it doesn't seem to reforecast if there are existing dates.  There are a couple of cron tasks to assist with this.

I would also recommend turning on eAudit on the PM and PMMETER tables as this has helped many times when there have been questions like yours as it captures the state of the PM.

I happy to have a chat if needed.

We have some cases recently where the time-based PMs are not triggering properly - namely, they're creating work orders early.  When looking at the Earliest Next Due Date, I can see that it's incorrect, but the only way I've found to change it is by changing the frequency units temporarily and then changing them back again.

This problems seems to have started when we started using the PM forecast on a regular basis, so I'm suspicious here.  We're NOT using the PM forecast to set the next due date, so it shouldn't be related, but I'm not sure about this.  It seems to me we had a problem like this a few years ago when we tried to use the PM forecast before.  We stopped using PM forecasting, and only started using it again recently.

Maximo version:  7.6.0.9

If anyone has any insight into this, I'd appreciate it.

Thanks.