Maximo Open Forum

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

If the Use Last Word Order's Start Date to Calculate Next Due Date is checked , then Due date calculation should be based on the Last Start date. Can you share screenshots if possible?

Note: 

Finish Constraint Offset is to set "Finish no later than" date. Value given in this field is the time (say 43:20). This would be added to the Target Finish date of the PM work order and arrives the "Finish no later than" date in the Work Order.

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Lead Time is 60

I don't know if the PMWOGen Cron Task is used to generate the Work Orders.  How can I tell?

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Two ways to tell if PMWOGen is in use:

1) Go to Organizations, open the Org record, use the PM Options action from the side menu, and about half way down, in the 

"Stand Alone PM Work Order Generation Process Settings" section, is the box "Automatic PM WO Generation?" checked

2) Go to Cron Task Setup application, open the record for PMWoGenCronTask, and look to see if the "Active?" box is checked.  Here, you can also see the cadence it runs at, such as once a day, or every 3 hours, or whatever.

Or, if you instinctively know that the PM Work Orders just magically get created, with no human intervention, then you're using PMWOGen.  :-)

Lead Time is 60

I don't know if the PMWOGen Cron Task is used to generate the Work Orders.  How can I tell?

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Apologize for my ignorance but where is the Organizations in MAXIMO?

Two ways to tell if PMWOGen is in use:

1) Go to Organizations, open the Org record, use the PM Options action from the side menu, and about half way down, in the 

"Stand Alone PM Work Order Generation Process Settings" section, is the box "Automatic PM WO Generation?" checked

2) Go to Cron Task Setup application, open the record for PMWoGenCronTask, and look to see if the "Active?" box is checked.  Here, you can also see the cadence it runs at, such as once a day, or every 3 hours, or whatever.

Or, if you instinctively know that the PM Work Orders just magically get created, with no human intervention, then you're using PMWOGen.  :-)

Lead Time is 60

I don't know if the PMWOGen Cron Task is used to generate the Work Orders.  How can I tell?

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Also when I generated a forecast the next date was in 2024

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

That makes me believe that the one that should generate in 2023, has already generated for 2023.  That is:

--on the PM record, you see that the Last Completion Date was 5/16/22. 

--So there's some Work Order, presumably the WO that generated in 2022, that has an Actual Finish Date on 5/16/22.

--If my hunch is correct, the WO for 2023 has already generated, but it isn't completed yet, which is what we'd expect. . .its not due for another two months.  So on this Work Order, the Actual Finish Date is NULL.

--Since this WO's Actual Finish is NULL, the PM record has no reason to update the Last Completion Date.  It would still show 5/16/22.

--Since the 2023 WO has already generated, the next one it would need to generate would happen in 2024.

Also when I generated a forecast the next date was in 2024

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

Looking at WO history, there are no WOs generated in 2023.

All have actual finish dates.....the last one that was completed on 5/16/22 strangely enough has the actual start date blank.

That makes me believe that the one that should generate in 2023, has already generated for 2023.  That is:

--on the PM record, you see that the Last Completion Date was 5/16/22. 

--So there's some Work Order, presumably the WO that generated in 2022, that has an Actual Finish Date on 5/16/22.

--If my hunch is correct, the WO for 2023 has already generated, but it isn't completed yet, which is what we'd expect. . .its not due for another two months.  So on this Work Order, the Actual Finish Date is NULL.

--Since this WO's Actual Finish is NULL, the PM record has no reason to update the Last Completion Date.  It would still show 5/16/22.

--Since the 2023 WO has already generated, the next one it would need to generate would happen in 2024.

Also when I generated a forecast the next date was in 2024

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

When you are searching for the Work Orders that have been generated from this PM, how -- exactly -- are you doing that?  Hopefully, you are in the Work Order Tracking application, using Advanced Search, removing the History = N filter, and searching upon the PMNUM, and then sorting the results by Report Date.

Better, if you can just enter a WHERE clause:

pmnum = 'thisPMNum' and siteid = 'mySiteID' order by reportdate desc

(in descending order so the newest is at the top, for convenience)

Also, I'm assuming that your user account has full access to the system -- no Object Restrictions or any such limitations that would hide records from you.

Assuming that what you've said is true, that no WO generated in 2023, go back through some of the stuff we've previously talked about.  (I get the sense that the PM we're talking about today is not the same one as we talked about earlier.)  Is there an Extended Date?  Seasonal Dates? Active Days? Generating on meters in addition to date?

And for that one having the Actual Start Date blank. . .sounds like someone deleted that data.  Then you'd have to figure out if that was an accident or if that's part of someone procedure they were taught to follow.  And unless you have eAudit turned on, figuring out who did it would be nearly impossible.  The best you could do is query the database for the value of CHANGEBY on that record, and/or look at the status history and see who changed the status (especially to INPRG and COMP).

Looking at WO history, there are no WOs generated in 2023.

All have actual finish dates.....the last one that was completed on 5/16/22 strangely enough has the actual start date blank.

That makes me believe that the one that should generate in 2023, has already generated for 2023.  That is:

--on the PM record, you see that the Last Completion Date was 5/16/22. 

--So there's some Work Order, presumably the WO that generated in 2022, that has an Actual Finish Date on 5/16/22.

--If my hunch is correct, the WO for 2023 has already generated, but it isn't completed yet, which is what we'd expect. . .its not due for another two months.  So on this Work Order, the Actual Finish Date is NULL.

--Since this WO's Actual Finish is NULL, the PM record has no reason to update the Last Completion Date.  It would still show 5/16/22.

--Since the 2023 WO has already generated, the next one it would need to generate would happen in 2024.

Also when I generated a forecast the next date was in 2024

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling

I am confused, Please help. I didn't develop this but don't understand why the estimated and earliest are 8/10/23.  I calculated the next due should be 6/27/22.

What am I not seeing?

I have an 18M PM, Use Last Word Order's Start Date to Calculate Next Due Date (Checked)

Estimated Next Due Date: 8/10/23

Last Start Date: 12/27/20

Last Completion Date: 1/7/21

Earliest Next Due Date: 8/10/23

Finish Constraint Offset: 4320.........not idea why this is here.

#EverythingMaximo

------------------------------
Wade Redd
3rd Coast Consulting
------------------------------

I was simply looking at the work history tab when looking at the PM work orders.  What is the difference between that and the advance search for work orders under the same PM?

Assuming that what you've said is true, that no WO generated in 2023, go back through some of the stuff we've previously talked about.  (I get the sense that the PM we're talking about today is not the same one as we talked about earlier.)  True

Is there an Extended Date?  Seasonal Dates? Active Days? Generating on meters in addition to date? None

When you are searching for the Work Orders that have been generated from this PM, how -- exactly -- are you doing that?  Hopefully, you are in the Work Order Tracking application, using Advanced Search, removing the History = N filter, and searching upon the PMNUM, and then sorting the results by Report Date.

Better, if you can just enter a WHERE clause:

pmnum = 'thisPMNum' and siteid = 'mySiteID' order by reportdate desc

(in descending order so the newest is at the top, for convenience)

Also, I'm assuming that your user account has full access to the system -- no Object Restrictions or any such limitations that would hide records from you.

Assuming that what you've said is true, that no WO generated in 2023, go back through some of the stuff we've previously talked about.  (I get the sense that the PM we're talking about today is not the same one as we talked about earlier.)  Is there an Extended Date?  Seasonal Dates? Active Days? Generating on meters in addition to date?

And for that one having the Actual Start Date blank. . .sounds like someone deleted that data.  Then you'd have to figure out if that was an accident or if that's part of someone procedure they were taught to follow.  And unless you have eAudit turned on, figuring out who did it would be nearly impossible.  The best you could do is query the database for the value of CHANGEBY on that record, and/or look at the status history and see who changed the status (especially to INPRG and COMP).

Looking at WO history, there are no WOs generated in 2023.

All have actual finish dates.....the last one that was completed on 5/16/22 strangely enough has the actual start date blank.

That makes me believe that the one that should generate in 2023, has already generated for 2023.  That is:

--on the PM record, you see that the Last Completion Date was 5/16/22. 

--So there's some Work Order, presumably the WO that generated in 2022, that has an Actual Finish Date on 5/16/22.

--If my hunch is correct, the WO for 2023 has already generated, but it isn't completed yet, which is what we'd expect. . .its not due for another two months.  So on this Work Order, the Actual Finish Date is NULL.

--Since this WO's Actual Finish is NULL, the PM record has no reason to update the Last Completion Date.  It would still show 5/16/22.

--Since the 2023 WO has already generated, the next one it would need to generate would happen in 2024.

Also when I generated a forecast the next date was in 2024

"Received" is not an out-of-the-box status for a Work Order.  You'd have to go to the Domains application, find the WOSTATUS domain, and look inside it to see which "Internal Value" it matches up with.  I would guess that it is a synonym of WAPPR, but please correct me if I am wrong.  But if I'm right. . .it doesn't make sense that the Work Order would be at an early stage in its lifecycle but has a value in the Actual Finish field.

Since the last WO was completed 5/16/22, and it is on a 1 Year floating schedule, then yes, the next WO would have a Target Start Date of 5/16/23.  But that's still 2 months in the future.  Do you expect it to create the Work Order this far in advance?

--Look at the PM record, on the main tab, and look at the value in the Lead Time field.  To generate this far in advance, the value would need to be greater than 63 to have generated today.

--Also, is the "Lead Time Active" checkbox is checked?

--Do you use the PMWOGen Cron Task to generate the Work Orders?  If so, go to Organizations, open the Org record, and use the PM Options action from the side menu.  Look at the setting for "Generate WOs Due on the Current Date Plus This Number of Days"

Thanks

I've a PM on a 1Y, floating schedule. Last work order completed 5/16/22 however it is in received status.  Would this be why the next work order has not generated yet for what I believe should be 5/16/23?

Can't say I can answer that completely, authoritatively.  What I do know is that when I use that field, I also check the box below it "Adjust Next Due Date."  With that, I've never had to manually delete the Extended Date later.

I don't know how it behaves if you don't check the Adjust Next Due Date box.

But also, make sure that the status on the PM is ACTIVE, and that whatever process you use to generate the Work Orders from the PMs doesn't somehow exclude that PM.  Assuming you use the PMWOGen Cron Task, then you need to go to Organizations, find and open the Organization record, choose PM Options, and examine the "WO Generation Where Clause."

(If the PM has a status of INACTIVE or DRAFT, then yes, the value in the Extended Date could be well in the past.)

Ah,

I was looking at the entire list and not the individual WO.

Also, a side question, when you use the extended date field, do manually need to delete it after the PM WO is generated?  I've got one with an old date in the extended date field and no next due.

Are you saying it's not on the screen, someone removed it from the UI?  It should be here:

If it's not on the screen, can you query the database directly?

SELECT targstartdate FROM workorder WHERE wonum = 'yourWorkOrderNumber' AND siteid = 'yourSiteID'

When I pull the work order tracking there is no Target Start Date field

The PM is looking for the Last Work Order's Target Start Date field.

But I believe you are saying that the last Work Order has a NULL value for the Target Start Date.

That's bad.  How is it supposed to add 18 months to NULL?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 17:37
From: Wade Redd
Subject: PM Scheduling

Sorry no target date field

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-09-2023 17:24
From: Travis Herron
Subject: PM Scheduling

>>The work order tracking doesn't give me a start date only target finish.

When the PM generates the Work Order, it will populate the Target Start and Target Finish fields.

When, on the PM record, the box Use Last Work Order's Start Date to Calculate Next Due Date is checked, it is looking at the Work Order's Target Start Date.

But now you've said -- if I'm reading this correctly -- that the Work Order's Target Start Date field is blank (NULL).  That would mean someone deleted the value from that field.  And. . .I could see how that could really mess up Maximo's ability to figure out when the next Work Order should generate.

>>Status is WAPPR

If the PM definition has this as having the generated Work Order starting at WAPPR status. . .I don't know, maybe others will chime in with their opinions and experience, but I wouldn't recommend that at all.  To me, the fact that someone bothered to create a PM schedule means approval was given at that point; it's just that they just don't need the Work Order now, they need it later, when the job is due to be done; and repetitively after that on some cadence.  Having it start as WAPPR makes it that much more tempting to Cancel it.  I have ALL of my PMs start at WSCH.

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-09-2023 12:40
From: Wade Redd
Subject: PM Scheduling

Sorry for the delay, multitasking...

Version 7.6

The work order tracking doesn't give me a start date only target finish.

No meters

Only one job plan listed in the sequence

Status is WAPPR

And to answer your followup post yes the start 12/27/20 and last completion is 1/7/21 on same work order and most recent

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 11:18
From: Travis Herron
Subject: PM Scheduling

Help me gather more info: go to Work Order Tracking, Advanced Search, remove the History flag filter, and search for where PMNUM = <the pmnum that we're talking about here>.  Look at the Target Start Dates on all of them, in chronological order, starting at the oldest.  Does it match the pattern you'd expect?  How many times has it generated?

Unfortunately, there's no way -- unless you have eAudit turned on for PMs -- to tell what changes users have made to the PM schedule in the past.  For example, maybe the PM used to be scheduled on a 1 year frequency, but later it was decided to change it to 18 months.

Also, please confirm that there are no meters involved with this PM.  And (not that I believe it could contribute to the problem, but it is one more thing that can complicate things) confirm whether or not there are Job Plan Sequences involved.

On the PM record, on the main tab, most of the way down, what is the status that the Work Order is set to begin at?  I'm starting to wonder if a Work Order generated from the PM at some point and a user deleted it.  I honestly don't know what kind of chaos that would cause to the PM schedule, if it's even possible.  I presume that if it starts at WAPPR (or a synonym thereof), then it could be deleted.  Also, look at the Status History on the Work Orders that have been generated from this PM, and make sure they all follow the same pattern.

Have you mentioned yet which version of Maximo you are using?

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-06-2023 10:56
From: Wade Redd
Subject: PM Scheduling

Thanks Travis,

1. Look at the Forecast tab, and see if the date has been manually overridden by a user. No forecast dates were generated
2. Look on the Frequency tab, and see if there is a value in the Extended Date field. No extended dates 
3. Are there any Seasonal Dates applied to the PM? No seasonal dates or days
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked? Not part of a hierarchy.
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it). How can I understand how MAXIMO's logic is when a WO is cancelled....Seeing a pattern of troubled PMs that may be related....just can't tell.  If I knew how MAXIMO responds to cancelled work orders I could place some guidance how to deal with them.
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  Earliest and Next have the same dates.
7. Just not sure where to go from here.  On the PM in question on this thread especially.

------------------------------
Wade Redd
3rd Coast Consulting

Original Message:
Sent: 03-06-2023 09:54
From: Travis Herron
Subject: PM Scheduling

My best guess is that someone has manually overridden the date. Examine these things:

1. Look at the Forecast tab, and see if the date has been manually overridden by a user.
2. Look on the Frequency tab, and see if there is a value in the Extended Date field.
3. Are there any Seasonal Dates applied to the PM?
4. Is the PM part of a hierarchy? Does it have a Parent PM? If so, on the main tab, is the field "Use this PM to Trigger PM Hierarchy?" checked?
5. Other than that, this may be related to all the other posts you've made about cancelling a Work Order that came from the PM, and it not being reinstated (or even giving the option to reinstate it).
6. Also, on the "main" tab there's a field labelled "Earliest Next Due Date" (PM.ERLSTWOGENDATE) and there's a different field on the Frequency tab labelled "Estimated Next Due Date" (PM.NEXTDATE).  Do these have different values?  For example, I just took a look at one in my production system, where it generates a Work Order every year on a fixed schedule (use last start date is checked, and I feel confident that that checkmark has not changed in a long, long time).  On the Work Order side of things, the one from

year 2020: completed, actual finish date 5/5/20

year 2021: is still APPR,

year 2022: is CAN (and apparently the user did not reinstate the PM -- otherwise the PM would have generated another Work Order at the next run of PMWoGen, which for us is every morning), and

year 2023: is set to happen next month, on 4/25/23. 

So, on the PM, the two date fields I mentioned above have the same value.  Then I unchecked the box.  This made the "Estimated Next Due Date" on the Frequency tab to be 5/5/21, since the last finish date was 5/5/20.  This is the behavior I would expect.  However, the "Earliest Next Due Date" on the main tab changed to today, 3/6/23.  I then checked the box again, and both fields returned to 4/25/23.

Some other things you can try:

• change some of the values on the PM, and see if that changes what you're seeing.
• analyze all the Work Orders that generated from this PM, including those in History, and see if you can determine a pattern
• duplicate the PM in question, and see if it behaves the way you would expect, or if it behaves like this unruly one you're asking about.

Regarding the Finish Constraint: 4320 hours  = 180 days, so I think whoever set up the PM wanted to convey the idea of "We're going to generate this Work Order with a Target Start Date, and you absolutely must have it finished within 6 months."

------------------------------
Travis Herron
Pensacola Christian College

Original Message:
Sent: 03-03-2023 16:24
From: Wade Redd
Subject: PM Scheduling