IBM Support

IZ44162: INCORECT AVERAGE IS CALCULATED WITH THE SLIDING-READING OPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • Requested steps to replicate with details and screenshots
    supplied by customer on ecurep
    
    
    
    Brief step by step from customer:-
    
    1. Create new location with new meter.
    
    2. The new meter with type= CONTINOUS and reading type = REEL /
    ACTUAL
    
    3. The meter on the location with average calc method =
    SLIDING-READINGS and sliding window side = 2
    
    4. Create 3 readings
    
    0.5   0.5
    0.75  0.25
    1.75  1.0
    
    5. Create a new ASSET with the same meter reading.
    
    6. The new asset has no parent and no location
    
    7. The meter will be the same meter with the same attributes
    with calc method = SLIDING READINGS  and sliding window side =
    2.
    
    8. Create 3 readings
    
    0.10   0.10
    0.15   0.05
    0.50   0.35
    
    
    9. Create a new reading on the Location
    
    2.00   0.25
    
    10. Check the Average reading and last reading for the location
    and asset. The calculated averages seem to be very high.
    
    
    11. Place the asset on the location.
    
    12. Create a new reading on the location
    
    2.20   0.20
    
    13. The average reading on the locations increases significantly
    
    14. The average reading on the asset also changes. Should it?
    
    15. Create another new reading on the location
    
    2.75   0.55
    
    16. The average reading on the locations increases significantly
    
    17. The average reading on the asset also changes. Should it?
    
    18. After 3 readings on the location with the asset on it, the
    averages are not the same. It should be the same because sliding
    window size is set to 2). So one of the averages on the location
    or the asset is wrong.
    

Local fix

  • N/A
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • The average calculation is a 'per day' average calculation.  If
    you enter several readings (even small readings) within a
    couple of minutes, the average will be high.
    
    
    
    
    
    The ASSETMETER will inherit readings from the location (thus
    impacting the asset meter's average) if it has the same meter
    as its location, and the 'Accept Rolldown From' value is set to
    LOCATION on the ASSETMETER.
    
    
    
    
    
    As for the asset and location SLIDING-READING average never
    becoming equal, the reason is that the reporter was using
    ACTUAL readings.  Several were entered on the location before
    the asset was created and readings were entered on the asset.
    Since the asset will only inherit DELTA (not ACTUAL) values,
    the averages will never be in synch because the deltas for the
    last 'n' readings probably won't be the same.
    
    
    
    
    
    While this APAR is not a defect, APAR IZ43712 fixes a defect
    that does affect the calculation of meter averages using
    SLIDING-READINGS AND SLIDING-DAYS.  The fix excludes the first
    delta in the range of 'n' readings as this delta in a sliding
    average calculation is actually accrued outside the range of
    interest.  As a result, SLIDING average calculations were
    higher than expected.
    

APAR Information

  • APAR number

    IZ44162

  • Reported component name

    ASSETS

  • Reported component ID

    5724R46AS

  • Reported release

    620

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-02-19

  • Closed date

    2009-03-26

  • Last modified date

    2009-03-26

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

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

Fix information

Applicable component levels

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

Document Information

Modified date:
09 April 2023