IV56052: INCONSISTENT LIFE TO DATE FIELDS AND THE UNITS TO GO FIELD

APAR status

• Closed as program error.

Error description

• ************************************
  TR Architect Carrey C. is aware of this issue and has
  authorized the APAR.
  ************************************
  
  
  PROBLEM:
  
   At a high level: process a series meter readings through the
     Telematics interface such that the newest reading goes in
     first and the oldest reading goes in last. This will result
     in MeterReading records where the oldest ReadingDate
     corresponds to the newest TransDate and vice versa.
     It may be possible to reproduce the problem by entering meter
     readings directly in an Assets application, rather than
     through the Telematics interface.
  
  MAXIMO VERSION:
  
  Version IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023
  DB
  Build V7504-00
  IBM Maximo for Transportation 7.5.0.0 Build 20110415-1936 DB
  Build
  V7500-06
  Tivoli's process automation engine 7.5.0.4-IFIX20130418-0906
  Build
  20130129-2023 DB Build V7504-38 HFDB Build HF7504-01
  IBM Maximo for Utilities 7.5.0.1 Build 20120710-0136 DB Build
  V7501-14
  IBM Maximo Spatial Asset Management 7.5.0.1 Build 20120714-2208
  DB
  Build V7501-13
  IBM Maximo for Oil And Gas 7.5.0.0 Build 20110418-1031 DB Build
  V7500-Page 6 of 36
  22
  
  Server OS Windows Server 2008 R2 6.1 build 7601 Service Pack 1
  
  Server DB Oracle 10.2 (Oracle Database 10g Enterprise Edition
  Release
  10.2.0.2.0 - 64bit Production With the Partitioning, OLAP and
  Data
  Mining options)
  
  ***********************************
  DETAILED DOCUMENT:
  https://ecurep.mainz.de.ibm.com/rest/download/54062%2C004%2C000/
  0-all_data/54062.004.000.43351.499.000.MDOT_Telematics_Meter_Rea
  ding_Logic_Erro.docx
  ***********************************
  
  DETAILED DESCRIPTION:
  
  In the Assets (Tr) application, if I open the View Meter
  Readings
  dialog (Select Action > Meter Readings > View Meter Readings)
  and look
  at the ODOM-M (Odometer-Miles) info (see the
  "ViewReadingsVsMetersTab"
  attachment), the "Life to Date" field in the dialog
  (METERREADING.
  PLUSTLTD = 40,271) matches the Reading field
  (METERREADING.READING =
  40,271) and is correct. And these values match the "Last
  Reading" field
  (ASSETMETER.LASTREADING = 40,271) for the meter, which you can
  see on
  the Meters tab (in the background). However, the "Life to Date"
  field
  (ASSETMETER.LIFETODATE = 54,183) on the Meters tab (in the
  background)
  has a very different reading!
  
  Then, if we go over to the PMs tab, the Units to Go field shows
  that
  the PM is overdue by 6,123 miles, which cannot be the case
  given our
  last reading of 40,271 and the reading in the Last Work Order
  Information section (PMMETER.LASTPMWOGENREAD = 38,682).
  Instead, Units
  to Go should be showing 2,411 miles, going by the Last Work
  Order Info
  plus the Frequency of 5,000.
  
  Where did these inconsistencies come from?
  
  Other information:
  
  * This vehicle (unit V0513040) has never had its odometer
  reset, its
  engine overhauled, or its unit number registered against
  another asset
  / vehicle.
  
  * We have readings arriving via the Telematics interface that
  comes
  with the Transportation solution.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users that use Maximo for Transportation 7.1.0.0 or high *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * INCONSISTENT LIFE TO DATE FIELDS AND THE UNITS TO GO         *
  * FIELD                                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * N/A                                                          *
  ****************************************************************
  

Problem conclusion

• New logic in cron task was addded
  

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:

Modules/Macros

• TRANS
  

Fix information

• Fixed component name

  MX TRANSPORTATI

• Fixed component ID

  5724R5500

Applicable component levels

• R750 PSY

     UP