Maximo Open Forum

So the scenario is:  we want to generate meter-based PMs at 80% due.

1. Global 7-day lead time specified in the Organization settings.  HOWEVER
2. Generate Work Order Based on Meter Readings (Do Not Estimate) is ON.  This means that the Global setting DOES NOT WORK (it's working fine for time-based PMs).
3. So we added a value for "Generate Work Order Ahead by".
4. Maximo generated the work order at approx. 80%, alright - but it ALSO changed the Target Start Date to the 80% mark, not the 100% mark.  This defeats the purpose of trying to add Lead Time!

Anyone got any insight into this?  

Yep, we had it like this for years.  It was annoying, and we just excluded MPMs from overdue metrics.  However, last year we wrote a script to run on WO generation's Save that if WORKTYPE=MPM, to recalculate the Target Start Date something along the lines of: (PMMETER.TOLERANCE / PMMETER.AVERAGE) + GETDATE().  So now WOs can generate early enough for material planning, and there's a relatively accurate Target Start Date.  

So the scenario is:  we want to generate meter-based PMs at 80% due.

1. Global 7-day lead time specified in the Organization settings.  HOWEVER
2. Generate Work Order Based on Meter Readings (Do Not Estimate) is ON.  This means that the Global setting DOES NOT WORK (it's working fine for time-based PMs).
3. So we added a value for "Generate Work Order Ahead by".
4. Maximo generated the work order at approx. 80%, alright - but it ALSO changed the Target Start Date to the 80% mark, not the 100% mark.  This defeats the purpose of trying to add Lead Time!

Anyone got any insight into this?  

Yep, we had it like this for years.  It was annoying, and we just excluded MPMs from overdue metrics.  However, last year we wrote a script to run on WO generation's Save that if WORKTYPE=MPM, to recalculate the Target Start Date something along the lines of: (PMMETER.TOLERANCE / PMMETER.AVERAGE) + GETDATE().  So now WOs can generate early enough for material planning, and there's a relatively accurate Target Start Date.  

So the scenario is:  we want to generate meter-based PMs at 80% due.

1. Global 7-day lead time specified in the Organization settings.  HOWEVER
2. Generate Work Order Based on Meter Readings (Do Not Estimate) is ON.  This means that the Global setting DOES NOT WORK (it's working fine for time-based PMs).
3. So we added a value for "Generate Work Order Ahead by".
4. Maximo generated the work order at approx. 80%, alright - but it ALSO changed the Target Start Date to the 80% mark, not the 100% mark.  This defeats the purpose of trying to add Lead Time!

Anyone got any insight into this?  

Hi Gail and Shannon,

This is yet another one of those things with Maximo that without observation, I never saw happening.  May I ask if this behaviour has been out through to IBM as an bug or have you raised an IBM Idea?  The issue you've raised is a bit of a fundamental thing for IBM to get right.

Further as part of the fix for the target start date, do you also look at reframing the SNTL, FNLT, and target finish dates as all of these are centric on the target start date?

Yep, we had it like this for years.  It was annoying, and we just excluded MPMs from overdue metrics.  However, last year we wrote a script to run on WO generation's Save that if WORKTYPE=MPM, to recalculate the Target Start Date something along the lines of: (PMMETER.TOLERANCE / PMMETER.AVERAGE) + GETDATE().  So now WOs can generate early enough for material planning, and there's a relatively accurate Target Start Date.  

So the scenario is:  we want to generate meter-based PMs at 80% due.

1. Global 7-day lead time specified in the Organization settings.  HOWEVER
2. Generate Work Order Based on Meter Readings (Do Not Estimate) is ON.  This means that the Global setting DOES NOT WORK (it's working fine for time-based PMs).
3. So we added a value for "Generate Work Order Ahead by".
4. Maximo generated the work order at approx. 80%, alright - but it ALSO changed the Target Start Date to the 80% mark, not the 100% mark.  This defeats the purpose of trying to add Lead Time!

Anyone got any insight into this?  

Hi Gail and Shannon,

This is yet another one of those things with Maximo that without observation, I never saw happening.  May I ask if this behaviour has been out through to IBM as an bug or have you raised an IBM Idea?  The issue you've raised is a bit of a fundamental thing for IBM to get right.

Further as part of the fix for the target start date, do you also look at reframing the SNTL, FNLT, and target finish dates as all of these are centric on the target start date?

Yep, we had it like this for years.  It was annoying, and we just excluded MPMs from overdue metrics.  However, last year we wrote a script to run on WO generation's Save that if WORKTYPE=MPM, to recalculate the Target Start Date something along the lines of: (PMMETER.TOLERANCE / PMMETER.AVERAGE) + GETDATE().  So now WOs can generate early enough for material planning, and there's a relatively accurate Target Start Date.  

So the scenario is:  we want to generate meter-based PMs at 80% due.

1. Global 7-day lead time specified in the Organization settings.  HOWEVER
2. Generate Work Order Based on Meter Readings (Do Not Estimate) is ON.  This means that the Global setting DOES NOT WORK (it's working fine for time-based PMs).
3. So we added a value for "Generate Work Order Ahead by".
4. Maximo generated the work order at approx. 80%, alright - but it ALSO changed the Target Start Date to the 80% mark, not the 100% mark.  This defeats the purpose of trying to add Lead Time!

Anyone got any insight into this?  

So the scenario is:  we want to generate meter-based PMs at 80% due.

1. Global 7-day lead time specified in the Organization settings.  HOWEVER
2. Generate Work Order Based on Meter Readings (Do Not Estimate) is ON.  This means that the Global setting DOES NOT WORK (it's working fine for time-based PMs).
3. So we added a value for "Generate Work Order Ahead by".
4. Maximo generated the work order at approx. 80%, alright - but it ALSO changed the Target Start Date to the 80% mark, not the 100% mark.  This defeats the purpose of trying to add Lead Time!

Anyone got any insight into this?  

Shannon, we run Generate WO number XX of hours ahead by using these fields. The hours ahead vary depending on asset priority and annual usage. We have ample lead time on stock ordering and downtime scheduling.

Greg

So the scenario is:  we want to generate meter-based PMs at 80% due.

1. Global 7-day lead time specified in the Organization settings.  HOWEVER
2. Generate Work Order Based on Meter Readings (Do Not Estimate) is ON.  This means that the Global setting DOES NOT WORK (it's working fine for time-based PMs).
3. So we added a value for "Generate Work Order Ahead by".
4. Maximo generated the work order at approx. 80%, alright - but it ALSO changed the Target Start Date to the 80% mark, not the 100% mark.  This defeats the purpose of trying to add Lead Time!

Anyone got any insight into this?