Maximo List Archive

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



Overdue PM Work Orders based on PM interval/frequency.

From: (2013-11-19 11:26)

A supervisor has asked me to give him a KPI or saved query that shows him the PM work orders that are overdue. By "overdue" he wants it calculated off the target finish date in work order.


Weekly 1 day past
Monthly 7 days past
Quarterly 30 days past
Annual 60 days past


I was able to select PM work orders that are overdue based on targcompdate < sysdate (this is Oracle database)... but I am not sure how to include the PM frequency and interval calculation as part of the where clause in workorder.


Any thoughts?


From: Incomm Solutions Inc. (2013-11-20 09:09)

Are your PMs time-based, or meter-based?

Also: normally the definition of an overdue PM is calculated from the Last Completion Date of the last work order, i.e. the work order’s Actual Completion Date. Does he have a reason for using a different date?



From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of swkim@getty.edu
Sent: November-19-13 11:26 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Overdue PM Work Orders based on PM interval/frequency.


A supervisor has asked me to give him a KPI or saved query that shows him the PM work orders that are overdue. By "overdue" he wants it calculated off the target finish date in work order.

Weekly 1 day past
Monthly 7 days past
Quarterly 30 days past
Annual 60 days past

I was able to select PM work orders that are overdue based on targcompdate < sysdate (this is Oracle database)... but I am not sure how to include the PM frequency and interval calculation as part of the where clause in workorder.

Any thoughts?


From: (2013-11-21 09:59)

> Are your PMs time-based, or meter-based?

Some are time-based, some are meter-based, and some are both (we track vehicle maintenance this way).


> Actual Completion Date


This is ACTFINISH in the WORKORDER table?
I think Target Finish Date is what they see in the Maximo fields. I know that many fields were hidden for our work order table, so Actual Finish may be one of them.


What happens if there are multiple labor entries in the actuals tab? Does ACTFINISH change based on the labor entries, or does it record whatever the first labor entry is? Sometimes PM WOs have multiple entries from different crafts...

---In maximo@yahoogroups.com, <shannonrotz@...> wrote:

Are your PMs time-based, or meter-based?



Also: normally the definition of an overdue PM is calculated from the Last Completion Date of the last work order, i.e. the work order’s Actual Completion Date. Does he have a reason for using a different date?







From: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com] On Behalf Of swkim@... mailto:swkim@...
Sent: November-19-13 11:26 AM
To: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Overdue PM Work Orders based on PM interval/frequency.





A supervisor has asked me to give him a KPI or saved query that shows him the PM work orders that are overdue. By "overdue" he wants it calculated off the target finish date in work order.



Weekly 1 day past

Monthly 7 days past

Quarterly 30 days past

Annual 60 days past



I was able to select PM work orders that are overdue based on targcompdate < sysdate (this is Oracle database)... but I am not sure how to include the PM frequency and interval calculation as part of the where clause in workorder.



Any thoughts?