IJ45409: INCORRECT NEXT METER READING AND UNITS TO GO VALUES FOR A METER-BASED PM WHEN METER IS FIRST ADDED

APAR status

• Closed as program error.

Error description

• PROBLEM DESCRIPTION:
  The Next Meter Reading and Units to Go values for a meter-based
  PM are incorrectly calculated when a meter is first added. This
  occurs because the Meter Reading [PMMETER.LASTPMWOGENREAD] value
  is blank at that stage due to no Work Order being generated yet
  when the Frequency has not been reached yet. The calculation
  does not take the Assets Life To Date value into account.
   
  STEPS TO REPRODUCE: 
  - Go to Assets application.
  - Create a new Asset record
  - In Meters tab, add existing Meter ODOM-KM (Type = Continuous,
  Unit of Measure = MILES) and add Average Calculation Method =
  ALL, Reading Type = ACTUAL, Accept Rolldown from = ASSET. Save
  the record.
  - Go to Enter Meter Readings option and enter value 10,000.
  - The Life to Date fore Asset field [ASSETMETER.LIFETODATE]
  now has the same value = 10,000 
  - Change status of Asset to OPERATING.
  - Go to Preventive Maintenance.
  - Create a new PM and add the newly-created Asset.
  - In Frequency tab / Meter-Based Frequency, add the Meter
  (ODOM-KM), Frequency = 400, Generate WO Ahead By = 10.
  - Generate Work Order Based on Meter Readings (Do Not Estimate)?
  = checked, and Generate Work Order When Meter Frequency is
  Reached? = checked
  - Save the PM.
  - Change the PM status to ACTIVE.
  - It shows Next Meter Reading = 400 and Units to Go = -9,610
  - Those values are incorrect: it should be Next Meter Reading =
  10,400 and Units to Go = 390
  - Go to the Assets application, select the record and do Enter
  Meter Readings.
  - For that Meter ODOM-KM, enter Reading = 10,500 and OK. This is
  500 above the initial Reading value and therefore above the
  Frequency of 400.
  - Open the PM in the Preventive Maintenance application.
  - It has Counter = 1, so one WO has been generated because the
  Frequency has been reached. 
  - In Frequency tab / Meter-Based Frequency, it now shows new
  values: Meter Reading = 10,500 (which is correct) and in Next
  Work Order Projections: Next Meter Reading = 10,900 (this is
  latest Meter Reading + Frequency) and Units to Go = 390 (ie
  Frequency - Generate WO Ahead By).
  
  RESULTS: 
  The Next Meter Reading and Units to Go values are incorrect in
  the PM record until the Frequency has been reached because the
  Meter Reading [PMMETER.LASTPMWOGENREAD] value is still blank at
  that stage.
  
  EXPECTED RESULTS:
  
  The Life To Date value on the Asset should be taken into
  account while the PMs Meter Reading value is still blank.
  
  REPORTED IN VERSION: 
  Maximo 7.6.1.3
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * INCORRECT NEXT METER READING AND UNITS TO GO VALUES FOR A    *
  * METER-BASED PM WHEN METER IS FIRST ADDED                     *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels