# Formula for PM Work Order Generation

## Question

What are the things to consider when the system generates meter based PM Work Orders?

Formula for Meter based PM:

1. Units to Go = Life to Date Meter Reading (UI,PMMETER.LASTPMWOGENREAD) + Frequency (PMMETER.FREQUENCY) - Life to Date Current Meter Reading (ASSETMETER.LIFETODATE) - Generate WO Ahead by (PMMETER.TOLERANCE)

2. PM Meter's Estimated Next Due Date (PMMETER.DATEOFNEXTWO) on the "Meter Based Frequency" tab is populated according the following rules:

A) If Units to Go is zero or negative:

PMMETER.DATEOFNEXTWO = Today's date + (Units to Go / Average (PMMETER.AVERAGE))

B) If the Last Start Date (PM.LASTSTARTDATE) exists and is after the Meter Reading Date (ASSETMETER.READINGDATE):

B.1) If any of these checkboxes are selected:

"Use Last Work Order's Start Information to Calculate Next Due Date?
" (PM.USETARGETDATE)
"Generate Work Order Based on Meter Readings (Do Not Estimate)?"
(PM.PMACTMETER)
"Generate Work Order When Meter Frequency is Reached?"
(PM.PMASSETWOGEN)

Below is an example screen shot to show these checkboxes:

PMMETER.DATEOFNEXTWO = Last Start Date + (Units to Go / Average)

B.2) If the none of those checkboxes are selected, and PM.LASTCOMPDATE exists:

PMMETER.DATEOFNEXTWO = PM.LASTCOMPDATE (Completion date of the last work order) + (Units to Go / Average)

C) If the checkbox "Use Last Work Order's Start Information to Calculate Next Due Date?" (PM.USETARGETDATE) is not selected:

C.1) If PM.LASTCOMPDATE exists and is after the Meter Reading Date:
PMMETER.DATEOFNEXTWO =  PM.LASTCOMPDATE + (Units to Go / Average)

C.2) Otherwise:
PMMETER.DATEOFNEXTWO = Meter Reading Date + (Units to Go / Average)

D) If none of the criteria for A, B, or C, are met:
PMMETER.DATEOFNEXTWO = Today's date + (Units to Go / Average)

When a value is specified for PM.LEADTIME, Maximo will generate work order through PM Work Order generation crontask (PMWoGenCronTask) as if the current due date is today plus this value.

4. If the PM is a time-based as well as meter based PM, then the Earliest Next Due Date (PM.ERLSTWOGENDATE) is populated by the earlier of Estimated Next Due Date (PM.NEXTDATE) on the "Time Based Frequency" tab and Estimated Next Due Date (PMMETER.DATEOFNEXTWO) on the "Meter Based Frequency" tab.

Case 1:

Estimated Next Due Date (PM.NEXTDATE) shows May 11, 2011 from the Time Based Frequency tab.

Screen shot of the Estimated Next Due Date (PMMETER.DATEOFNEXTWO) shows July 7, 2017 on the Meter Based Frequency tab.

Since both Estimated Next Due Dates on the Time-Based and Meter-Based Frequency tabs are in the past, then the Earliest Next Due Date on the PM tab will default to today's date.

Case 2:

If Time Based Frequency shows the Estimated Next Date of July 27th, 2018.

If Meter Based Frequency shows next date of Aug 23, 2017.

Since the Estimated Next Due Date showed on the "Meter Based Frequency" tab are both in the future and the Estimated Next Due Date on the Meter-Based Frequency tab is earlier, the "Earliest Next Due Date" on the PM tab will use the "Estimated Next Due Date" on the "Meter Based Frequency" tab.

For example: August 23, 2017

5. Earliest Next Due Date in the Work Order Information section on the PM tab

PM.ERLSTWOGENDATE = Earliest of PM.NEXTDATE and PMMETER.DATEOFNEXTWO

PM.NEXTDATE is calculated on the Time-Based Frequency tab.

A) If the checkbox "Use Last Work Order's Start Information to Calculate Next Due Date?" (PM.USETARGETDATE) is selected:

PM.NEXTDATE = PM.LASTSTARTDATE + PM.FREQUENCY

B) If the checkbox "Use Last Work Order's Start Information to Calculate Next Due Date?" (PM.USETARGETDATE) is not selected:

PM.NEXTDATE = PM.LASTCOMPDATE + PM.FREQUENCY

PMMETER.DATEOFNEXTWO is calculated as outlined in section 2 above.

## Related Information

[{"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Prev Maint","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Modified date:
17 June 2018

swg22005704