IZ85350: MAXIMO 7.1.1.6 - AVERAGE UNIT GOES INTO NEGATIVE CAUSING RUNAWAYPMWOGEN

APAR status

• Closed as program error.

Error description

• 1. Create a new asset record NEGTEST1in Site BEDFORD, in
  Operating Location BOILER, using rotating item PUMP100.
  2. Add Continuous Meter RUNHOURS to the asset, using Average
  Calculation Method ALL, Reading Type ACTUAL, and Accept Rolldown
  From ASSET.
  3. Our scenario is the new asset actually arrived at the site
  3 days ago, on 9/18/10, and had an existing physical meter with
  a reading at that time of 718 hrs. However, we want to start the
  Life to Date value of this asset at zero, since it is new to us
  at this site. Therefore, we use the Reset/Replace Meters action
  to create the first meter reading entry for 718 hrs on 9/18/10.
  4. 4. So now we have the desired Life to Date for Asset reading
  of zero, and a Last Reading value of 718 on 9/18/10
  5. Now it's 3 days later, and we have a new reading of 801hrs
  that we want to enter, in the normal manner, using the Enter
  Meter Readings action
  
  6. 6. So now we have our Life to Date for Asset at 83hrs, which
  is correct?. but?. look at the Average Units per Day?.. it's
  negative
  
  7.Open PM and create a new PM for this asset
  8. Make it a meterbased pm
  9. have Estimation enabled, and we want to have the Due to Start
  be in sync with the 250hr frequency, so the "Use Last WO's Start
  Information?." flag is checked.
  10. 9. When we Activate the PM and run the Generate WO action,
  the system starts creating WOs and will never stop. This is
  because the Average Units per Day is negative; the "Use Last
  WO's Start Information" flag is set which allows duplicate WOs;
  and the Estimating feature is enabled. It thinks it's always
  overdue from an Estimated Date Due standpoint, so it
  continuously generates WOs attempting to catch up, but it never
  will. We have had over 22,000 WOs created for a single meter
  based PM in our production system before we noticed it and
  stopped it by changing the offending PM's status to DRAFT.
  
  This was reproduced on the Maximo IBM Demo site
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Maximo users                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When reporting meter readings on assets *
  *                      or locations negative average           *
  *                      calculations sometimes result when the  *
  *                      ALL meter average calculation method is *
  *                      used and the earliest (oldest) reading  *
  *                      for the meter has a reading type of     *
  *                      'RESET'. These negative average meter   *
  *                      calculations are incorrect and can lead *
  *                      to the erroneous generation of          *
  *                      additional work orders when PM work     *
  *                      order generation is executed.           *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  When reporting meter readings on assets or locations negative
  average calculations sometimes result when the ALL meter
  average calculation method is used. These negative average
  meter calculations are incorrect and can lead to the erroneous
  generation of additional work orders when PM work order
  generation is executed.
  

Problem conclusion

• Meter readings on assets or locations are calculated correctly
  when using the ALL meter average calculation method and the
  earliest (oldest) reading for the meter has a reading type of
  'RESET'. As a result, when executing PM work order generation,
  the erroneous creation of additional work orders does not
  occur.
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | REL 7.1.1.8 - BS
  

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

• MAXIMO
  

Fix information

• Fixed component name

  PREVENTIVE MAIN

• Fixed component ID

  5724R46PM

Applicable component levels

• R711 PSY

     UP