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.



Setting up PMs to repeat on the same day every 3 months

From: mshumack (2013-06-02 13:05)

I have been having trouble getting my PMs to reoccur on the same day every 3-months. Maybe Maximo 7.x won't do this.
I have a vehicle fleet. I want to set up the PMs for each vehicle so its Target Start date is the same every time it comes due. This is so I can spread the work load out evenly throughout the week and month. If I can get this worked out, I can plan (plot out) the work on a calendar and keep the work load even.
So if a vehicle is due for a quarterly PM on January 1st, and the frequency is set to 3 months, I want the next PM to be do on April 1st, and next time it would be due on July 1st. I have PM due date set to use "Start Date" each time (+ frequency). However, this is not working. My PMs do not always have the Target Start Date that I desire. Perhaps because the number of days in a month vary. I could see this being an issue if there are 29 days in one month a 31 in another. But even the PMs scheduled for the 1st don't come due (sometimes) on the 1st the next time.
Should this work?


From: Yahoo (2013-06-02 08:14)

What version of 7? 7.5 you can generate a pm forecast and manually change all the due dates as far out as you desire and the PM will always generate on that specific day. Other than the forecasting option Its not possible to make a pm generate on the same exact day, due to each month vary in number of days. Another option is to just let your pm's generate as they are and build a report that will allow you to see your due dates for months ahead to allow for scheduling, then if you have a conflict set the extend date. Pm's are never going to be a setup and leave, they always need constant adjustments based on your scheduling, labor availability and corrective/emergency work.
Shannon Sutton
Cell: (318) 334-8002
On Jun 2, 2013, at 8:05 AM, "mshumack" <mshumack@yahoo.com> wrote:
> I have been having trouble getting my PMs to reoccur on the same day every 3-months. Maybe Maximo 7.x won't do this.
>
> I have a vehicle fleet. I want to set up the PMs for each vehicle so its Target Start date is the same every time it comes due. This is so I can spread the work load out evenly throughout the week and month. If I can get this worked out, I can plan (plot out) the work on a calendar and keep the work load even.
>
> So if a vehicle is due for a quarterly PM on January 1st, and the frequency is set to 3 months, I want the next PM to be do on April 1st, and next time it would be due on July 1st. I have PM due date set to use "Start Date" each time (+ frequency). However, this is not working. My PMs do not always have the Target Start Date that I desire. Perhaps because the number of days in a month vary. I could see this being an issue if there are 29 days in one month a 31 in another. But even the PMs scheduled for the 1st don't come due (sometimes) on the 1st the next time.
>
> Should this work?
>
>


From: mshumack (2013-06-02 15:28)

We are on 7.2 but will be upgrading to 7.5 this summer I'm told.
I run a report to look at a Estimated Next Due (PM.NEXTDUEDATE)date but that is not really accurate. I need to see the Earliest WO Gen Date (something like PM.EARLYPMWOGENDATE) but apparently that is a calculated field so I can select that field in the report creator.
One of the problems I have is that we have Maximo setup to e-mail the Asset Custodian when to bring the vehicle in based on Target Start Date. But Target Start Date is only created when the WO is generated (about ten days in advance) so I can't be sure what date the Custodian is told his PM is due by Maximo until the WO is created.
I'm looking forward to 7.5.
--- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@...> wrote:
>
> What version of 7? 7.5 you can generate a pm forecast and manually change all the due dates as far out as you desire and the PM will always generate on that specific day. Other than the forecasting option Its not possible to make a pm generate on the same exact day, due to each month vary in number of days. Another option is to just let your pm's generate as they are and build a report that will allow you to see your due dates for months ahead to allow for scheduling, then if you have a conflict set the extend date. Pm's are never going to be a setup and leave, they always need constant adjustments based on your scheduling, labor availability and corrective/emergency work.
>
>
>
> Shannon Sutton
> Cell: (318) 334-8002
>
> On Jun 2, 2013, at 8:05 AM, "mshumack" <mshumack@...> wrote:
>
> > I have been having trouble getting my PMs to reoccur on the same day every 3-months. Maybe Maximo 7.x won't do this.
> >
> > I have a vehicle fleet. I want to set up the PMs for each vehicle so its Target Start date is the same every time it comes due. This is so I can spread the work load out evenly throughout the week and month. If I can get this worked out, I can plan (plot out) the work on a calendar and keep the work load even.
> >
> > So if a vehicle is due for a quarterly PM on January 1st, and the frequency is set to 3 months, I want the next PM to be do on April 1st, and next time it would be due on July 1st. I have PM due date set to use "Start Date" each time (+ frequency). However, this is not working. My PMs do not always have the Target Start Date that I desire. Perhaps because the number of days in a month vary. I could see this being an issue if there are 29 days in one month a 31 in another. But even the PMs scheduled for the 1st don't come due (sometimes) on the 1st the next time.
> >
> > Should this work?
> >
> >
>
>
>
>


From: Yahoo (2013-06-02 10:35)

A workorder should always generate at the next due date if your basing it on the workorder start date and not workorder completion date. Also if you have a lead time set then write you sql in the escalation to do a pm.nextdate minus leadtime and minus 10 days..etc.. Your don't have to base the escalation off the workorder target start date. I might be inaccurate but i've never seem the EARLYPMWOGENDATE field.. Is this custom? Has the pmwogen been modified?
Shannon Sutton
Sutton EAM Consutling
Cell: (318) 334-8002
On Jun 2, 2013, at 10:28 AM, "mshumack" <mshumack@yahoo.com> wrote:
> We are on 7.2 but will be upgrading to 7.5 this summer I'm told.
>
> I run a report to look at a Estimated Next Due (PM.NEXTDUEDATE)date but that is not really accurate. I need to see the Earliest WO Gen Date (something like PM.EARLYPMWOGENDATE) but apparently that is a calculated field so I can select that field in the report creator.
>
> One of the problems I have is that we have Maximo setup to e-mail the Asset Custodian when to bring the vehicle in based on Target Start Date. But Target Start Date is only created when the WO is generated (about ten days in advance) so I can't be sure what date the Custodian is told his PM is due by Maximo until the WO is created.
>
> I'm looking forward to 7.5.
>
> --- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@...> wrote:
> >
> > What version of 7? 7.5 you can generate a pm forecast and manually change all the due dates as far out as you desire and the PM will always generate on that specific day. Other than the forecasting option Its not possible to make a pm generate on the same exact day, due to each month vary in number of days. Another option is to just let your pm's generate as they are and build a report that will allow you to see your due dates for months ahead to allow for scheduling, then if you have a conflict set the extend date. Pm's are never going to be a setup and leave, they always need constant adjustments based on your scheduling, labor availability and corrective/emergency work.
> >
> >
> >
> > Shannon Sutton
> > Cell: (318) 334-8002
> >
> > On Jun 2, 2013, at 8:05 AM, "mshumack" <mshumack@...> wrote:
> >
> > > I have been having trouble getting my PMs to reoccur on the same day every 3-months. Maybe Maximo 7.x won't do this.
> > >
> > > I have a vehicle fleet. I want to set up the PMs for each vehicle so its Target Start date is the same every time it comes due. This is so I can spread the work load out evenly throughout the week and month. If I can get this worked out, I can plan (plot out) the work on a calendar and keep the work load even.
> > >
> > > So if a vehicle is due for a quarterly PM on January 1st, and the frequency is set to 3 months, I want the next PM to be do on April 1st, and next time it would be due on July 1st. I have PM due date set to use "Start Date" each time (+ frequency). However, this is not working. My PMs do not always have the Target Start Date that I desire. Perhaps because the number of days in a month vary. I could see this being an issue if there are 29 days in one month a 31 in another. But even the PMs scheduled for the 1st don't come due (sometimes) on the 1st the next time.
> > >
> > > Should this work?
> > >
> > >
> >
> >
> >
> >
>
>


From: mshumack (2013-06-02 16:26)

I am not at my Maximo workstation right now and the field name I used is from memory (I'll recheck tomorrow) - but this is the "third field down" in the PM application on the PM tab. Top one is "Last Start Date", next one is "Last Completion Date", then the third one is "Estimated Next Due Date" (or maybe it's "Earliest Next Due Date"). If you highlight the field and hit ALT+F1 it displays the name of field, as I'm sure you know.
I don't know how much customization has been done (but I don't think much. BTW - I'm using the Transportation application).
Thanks for your time.
--- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@...> wrote:
>
> A workorder should always generate at the next due date if your basing it on the workorder start date and not workorder completion date. Also if you have a lead time set then write you sql in the escalation to do a pm.nextdate minus leadtime and minus 10 days..etc.. Your don't have to base the escalation off the workorder target start date. I might be inaccurate but i've never seem the EARLYPMWOGENDATE field.. Is this custom? Has the pmwogen been modified?
>
>
>
> Shannon Sutton
> Sutton EAM Consutling
> Cell: (318) 334-8002
>
> On Jun 2, 2013, at 10:28 AM, "mshumack" <mshumack@...> wrote:
>
> > We are on 7.2 but will be upgrading to 7.5 this summer I'm told.
> >
> > I run a report to look at a Estimated Next Due (PM.NEXTDUEDATE)date but that is not really accurate. I need to see the Earliest WO Gen Date (something like PM.EARLYPMWOGENDATE) but apparently that is a calculated field so I can select that field in the report creator.
> >
> > One of the problems I have is that we have Maximo setup to e-mail the Asset Custodian when to bring the vehicle in based on Target Start Date. But Target Start Date is only created when the WO is generated (about ten days in advance) so I can't be sure what date the Custodian is told his PM is due by Maximo until the WO is created.
> >
> > I'm looking forward to 7.5.
> >
> > --- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@> wrote:
> > >
> > > What version of 7? 7.5 you can generate a pm forecast and manually change all the due dates as far out as you desire and the PM will always generate on that specific day. Other than the forecasting option Its not possible to make a pm generate on the same exact day, due to each month vary in number of days. Another option is to just let your pm's generate as they are and build a report that will allow you to see your due dates for months ahead to allow for scheduling, then if you have a conflict set the extend date. Pm's are never going to be a setup and leave, they always need constant adjustments based on your scheduling, labor availability and corrective/emergency work.
> > >
> > >
> > >
> > > Shannon Sutton
> > > Cell: (318) 334-8002
> > >
> > > On Jun 2, 2013, at 8:05 AM, "mshumack" <mshumack@> wrote:
> > >
> > > > I have been having trouble getting my PMs to reoccur on the same day every 3-months. Maybe Maximo 7.x won't do this.
> > > >
> > > > I have a vehicle fleet. I want to set up the PMs for each vehicle so its Target Start date is the same every time it comes due. This is so I can spread the work load out evenly throughout the week and month. If I can get this worked out, I can plan (plot out) the work on a calendar and keep the work load even.
> > > >
> > > > So if a vehicle is due for a quarterly PM on January 1st, and the frequency is set to 3 months, I want the next PM to be do on April 1st, and next time it would be due on July 1st. I have PM due date set to use "Start Date" each time (+ frequency). However, this is not working. My PMs do not always have the Target Start Date that I desire. Perhaps because the number of days in a month vary. I could see this being an issue if there are 29 days in one month a 31 in another. But even the PMs scheduled for the 1st don't come due (sometimes) on the 1st the next time.
> > > >
> > > > Should this work?
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
>
>
>
>


From: Yahoo (2013-06-02 15:00)

Check out this blog. It might get you what you need and believe this will work in 7.2
http://maximodev.blogspot.com/2011/04/how-to-schedule-preventive-maintenance.html?m=1
Shannon Sutton
Cell: (318) 334-8002
On Jun 2, 2013, at 11:26 AM, "mshumack" <mshumack@yahoo.com> wrote:
> I am not at my Maximo workstation right now and the field name I used is from memory (I'll recheck tomorrow) - but this is the "third field down" in the PM application on the PM tab. Top one is "Last Start Date", next one is "Last Completion Date", then the third one is "Estimated Next Due Date" (or maybe it's "Earliest Next Due Date"). If you highlight the field and hit ALT+F1 it displays the name of field, as I'm sure you know.
> I don't know how much customization has been done (but I don't think much. BTW - I'm using the Transportation application).
> Thanks for your time.
>
> --- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@...> wrote:
> >
> > A workorder should always generate at the next due date if your basing it on the workorder start date and not workorder completion date. Also if you have a lead time set then write you sql in the escalation to do a pm.nextdate minus leadtime and minus 10 days..etc.. Your don't have to base the escalation off the workorder target start date. I might be inaccurate but i've never seem the EARLYPMWOGENDATE field.. Is this custom? Has the pmwogen been modified?
> >
> >
> >
> > Shannon Sutton
> > Sutton EAM Consutling
> > Cell: (318) 334-8002
> >
> > On Jun 2, 2013, at 10:28 AM, "mshumack" <mshumack@...> wrote:
> >
> > > We are on 7.2 but will be upgrading to 7.5 this summer I'm told.
> > >
> > > I run a report to look at a Estimated Next Due (PM.NEXTDUEDATE)date but that is not really accurate. I need to see the Earliest WO Gen Date (something like PM.EARLYPMWOGENDATE) but apparently that is a calculated field so I can select that field in the report creator.
> > >
> > > One of the problems I have is that we have Maximo setup to e-mail the Asset Custodian when to bring the vehicle in based on Target Start Date. But Target Start Date is only created when the WO is generated (about ten days in advance) so I can't be sure what date the Custodian is told his PM is due by Maximo until the WO is created.
> > >
> > > I'm looking forward to 7.5.
> > >
> > > --- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@> wrote:
> > > >
> > > > What version of 7? 7.5 you can generate a pm forecast and manually change all the due dates as far out as you desire and the PM will always generate on that specific day. Other than the forecasting option Its not possible to make a pm generate on the same exact day, due to each month vary in number of days. Another option is to just let your pm's generate as they are and build a report that will allow you to see your due dates for months ahead to allow for scheduling, then if you have a conflict set the extend date. Pm's are never going to be a setup and leave, they always need constant adjustments based on your scheduling, labor availability and corrective/emergency work.
> > > >
> > > >
> > > >
> > > > Shannon Sutton
> > > > Cell: (318) 334-8002
> > > >
> > > > On Jun 2, 2013, at 8:05 AM, "mshumack" <mshumack@> wrote:
> > > >
> > > > > I have been having trouble getting my PMs to reoccur on the same day every 3-months. Maybe Maximo 7.x won't do this.
> > > > >
> > > > > I have a vehicle fleet. I want to set up the PMs for each vehicle so its Target Start date is the same every time it comes due. This is so I can spread the work load out evenly throughout the week and month. If I can get this worked out, I can plan (plot out) the work on a calendar and keep the work load even.
> > > > >
> > > > > So if a vehicle is due for a quarterly PM on January 1st, and the frequency is set to 3 months, I want the next PM to be do on April 1st, and next time it would be due on July 1st. I have PM due date set to use "Start Date" each time (+ frequency). However, this is not working. My PMs do not always have the Target Start Date that I desire. Perhaps because the number of days in a month vary. I could see this being an issue if there are 29 days in one month a 31 in another. But even the PMs scheduled for the 1st don't come due (sometimes) on the 1st the next time.
> > > > >
> > > > > Should this work?
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
> >
>
>


From: mshumack (2013-06-02 20:50)

That's a neat tip. I'm going to save that procedure. It looks like it would work, but I have several hundred Assets to schedule. That would be a lot of work. I think my best bet is to wait for 7.5. If the upgrade doesn't happen as/when promised, at least I have a procedure now.
I appreciate your help.
--- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@...> wrote:
>
> Check out this blog. It might get you what you need and believe this will work in 7.2
> http://maximodev.blogspot.com/2011/04/how-to-schedule-preventive-maintenance.html?m=1
>
>
>
> Shannon Sutton
> Cell: (318) 334-8002
>
> On Jun 2, 2013, at 11:26 AM, "mshumack" <mshumack@...> wrote:
>
> > I am not at my Maximo workstation right now and the field name I used is from memory (I'll recheck tomorrow) - but this is the "third field down" in the PM application on the PM tab. Top one is "Last Start Date", next one is "Last Completion Date", then the third one is "Estimated Next Due Date" (or maybe it's "Earliest Next Due Date"). If you highlight the field and hit ALT+F1 it displays the name of field, as I'm sure you know.
> > I don't know how much customization has been done (but I don't think much. BTW - I'm using the Transportation application).
> > Thanks for your time.
> >
> > --- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@> wrote:
> > >
> > > A workorder should always generate at the next due date if your basing it on the workorder start date and not workorder completion date. Also if you have a lead time set then write you sql in the escalation to do a pm.nextdate minus leadtime and minus 10 days..etc.. Your don't have to base the escalation off the workorder target start date. I might be inaccurate but i've never seem the EARLYPMWOGENDATE field.. Is this custom? Has the pmwogen been modified?
> > >
> > >
> > >
> > > Shannon Sutton
> > > Sutton EAM Consutling
> > > Cell: (318) 334-8002
> > >
> > > On Jun 2, 2013, at 10:28 AM, "mshumack" <mshumack@> wrote:
> > >
> > > > We are on 7.2 but will be upgrading to 7.5 this summer I'm told.
> > > >
> > > > I run a report to look at a Estimated Next Due (PM.NEXTDUEDATE)date but that is not really accurate. I need to see the Earliest WO Gen Date (something like PM.EARLYPMWOGENDATE) but apparently that is a calculated field so I can select that field in the report creator.
> > > >
> > > > One of the problems I have is that we have Maximo setup to e-mail the Asset Custodian when to bring the vehicle in based on Target Start Date. But Target Start Date is only created when the WO is generated (about ten days in advance) so I can't be sure what date the Custodian is told his PM is due by Maximo until the WO is created.
> > > >
> > > > I'm looking forward to 7.5.
> > > >
> > > > --- In MAXIMO@yahoogroups.com, Yahoo <shannonsuttondale@> wrote:
> > > > >
> > > > > What version of 7? 7.5 you can generate a pm forecast and manually change all the due dates as far out as you desire and the PM will always generate on that specific day. Other than the forecasting option Its not possible to make a pm generate on the same exact day, due to each month vary in number of days. Another option is to just let your pm's generate as they are and build a report that will allow you to see your due dates for months ahead to allow for scheduling, then if you have a conflict set the extend date. Pm's are never going to be a setup and leave, they always need constant adjustments based on your scheduling, labor availability and corrective/emergency work.
> > > > >
> > > > >
> > > > >
> > > > > Shannon Sutton
> > > > > Cell: (318) 334-8002
> > > > >
> > > > > On Jun 2, 2013, at 8:05 AM, "mshumack" <mshumack@> wrote:
> > > > >
> > > > > > I have been having trouble getting my PMs to reoccur on the same day every 3-months. Maybe Maximo 7.x won't do this.
> > > > > >
> > > > > > I have a vehicle fleet. I want to set up the PMs for each vehicle so its Target Start date is the same every time it comes due. This is so I can spread the work load out evenly throughout the week and month. If I can get this worked out, I can plan (plot out) the work on a calendar and keep the work load even.
> > > > > >
> > > > > > So if a vehicle is due for a quarterly PM on January 1st, and the frequency is set to 3 months, I want the next PM to be do on April 1st, and next time it would be due on July 1st. I have PM due date set to use "Start Date" each time (+ frequency). However, this is not working. My PMs do not always have the Target Start Date that I desire. Perhaps because the number of days in a month vary. I could see this being an issue if there are 29 days in one month a 31 in another. But even the PMs scheduled for the 1st don't come due (sometimes) on the 1st the next time.
> > > > > >
> > > > > > Should this work?
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
>
>
>
>