IBM Support

IJ20953: WORK ORDERS ARE NOT AUTOMATICALLY GENERATED WHEN METER READING IS ENTERED ON PARENT ASSET AND PM IS AGAINST CHILD ASSET

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Problem
    If a child asset that is associated on a preventive maintenance
    record inherits a meter reading from the parent asset a work
    order is not automatically generated.
    
    
    Steps to Reproduce
    
    Go the Asset application
    Create 2 assets make one the parent and one the child
    Click on Meters tab
    Add runhours meter
    Frequency = 200
    Average Calculation Method = ALL
    Reading Type= DELTA
    Accept Rolldown From = Asset
    Associate the same meter for  parent and child asset
    Change status to operating for both
    
    Go to the Preventive Maintenance application
    Create a new PM
    Populate the Asset field = child asset
    Click on the Frequency tab
    Click on the Meter Based Frequency
    Meter field= Runhours
    Frequency = 200
    Uncheck Use Last Work Order's Start Date to Calculate Next Due
    Date? field
    Check Generate Work Order Based on Meter Readings (Do Not
    Estimate)? field
    Check Generate Work Order When Meter Frequency is Reached?
    Change the status to Active
    
    Go to the Asset application filter for the parent asset
    More Actions>Enter meter reading > new reading enter 250
    Go to the child asset > More Actions> Manage Meter Reading
    History you will see inherited meter reading of 250 from the
    parent asset
    
    
    Go to the Preventive Maintenance application
    Filter for the PM created above notice the pm counter is still
    set to 0 a work order was not automatically generated
    
    Go the Asset application
    Filter for the child asset enter a new reading on the child
    asset of 300
    
    Go to the Preventive Maintenance application
    Filter for the PM record
    Notice the PM counter is set to 1
    Click on the Frequency Tab> Meter Based Frequency
    Notice that the Last Work Order Information meter reading and
    Meter reading date fields are populated a work order was
    generated.
    
    
    Results
    
    A work order is generated when the meter reading is entered
    directly on the child asset
    
    
    Expected Results
    
    If the child asset inherits the meter reading from the parent a
    work order should be generated
    
    Reported In Version
    
    Maximo 7.6.0.9
    

Local fix

  • no work around
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users who have assets and PMs that use automatic work *
    * order generation when a meter reading is entered.            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Meter-based PMs that are supposed to automatically generate  *
    * a work order when meter frequency is met do not do so for    *
    * PMs on child assets that inherit meter readings from their   *
    * parent assets.                                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Steps to Reproduce
    
    Go the Asset application
    Create 2 assets make one the parent and one the child
    Click on Meters tab
    Add runhours meter
    Frequency = 200
    Average Calculation Method = ALL
    Reading Type= DELTA
    Accept Rolldown From = Asset
    Associate the same meter for  parent and child asset
    Change status to operating for both
    
    Go to the Preventive Maintenance application
    Create a new PM
    Populate the Asset field = child asset
    Click on the Frequency tab
    Click on the Meter Based Frequency
    Meter field= Runhours
    Frequency = 200
    Uncheck Use Last Work Order's Start Date to Calculate Next Due
    Date? field
    Check Generate Work Order Based on Meter Readings (Do Not
    Estimate)? field
    Check Generate Work Order When Meter Frequency is Reached?
    Change the status to Active
    
    Go to the Asset application filter for the parent asset
    More Actions>Enter meter reading > new reading enter 250
    Go to the child asset > More Actions> Manage Meter Reading
    History you will see inherited meter reading of 250 from the
    parent asset
    
    
    Go to the Preventive Maintenance application
    Filter for the PM created above notice the pm counter is still
    set to 0 a work order was not automatically generated
    
    Go the Asset application
    Filter for the child asset enter a new reading on the child
    asset of 300
    
    Go to the Preventive Maintenance application
    Filter for the PM record
    Notice the PM counter is set to 1
    Click on the Frequency Tab> Meter Based Frequency
    Notice that the Last Work Order Information meter reading and
    Meter reading date fields are populated a work order was
    generated.
    
    
    Results
    
    A work order is generated when the meter reading is entered
    directly on the child asset
    
    
    Expected Results
    
    If the child asset inherits the meter reading from the parent a
    work order should be generated
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	| release\fix pack\interim fix for Release 7.6.1.2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ20953

  • Reported component name

    ASSETS

  • Reported component ID

    5724R46AS

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-18

  • Closed date

    2020-07-06

  • Last modified date

    2020-07-06

  • 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

    ASSETS

  • Fixed component ID

    5724R46AS

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
07 July 2020