Hi,

Maximo is calculating Average Units/Day depending on the below method 

1- Search the Meter reading table to see how many records there are between now and the previous date (now - ALL) ,sort this by desc;
2- Get the total Delta value of all records received from Step 1;
3- Calculate the day difference between the first record and the last record from the result getting from Step 1;
4- Average = Total Delta Value / Day Difference ( step 2 divided by step 3 )

But when ACM is installed I see that Asset(CM) and Work Order Tracking (CM) is calculating the average very differently in both applications.

In Asset (CM) application below is the calculation method:

Average Units/Day calculation: 

Numerator = Life to Date or Total of all the delta readings

Denominator = days ( Last reading datetime - Initial reading datetime (PLUSAANCHORDATE))

Average Units/Day = Numerator / Denominator

And Work Order Tracking (CM) is calculating a very strange average for which the calculation is unknown.

Any pointers would really help to understand here.

Thank you,

#maximo #maximoacm #acm #assetmeterreading #averageunits

------------------------------
Prashant Patil
------------------------------

Hi Prashant,

What version of ACM are you using? We did a recent fix (APAR DT381928) related to average meter calculations.

This was released as part of ACM Patch 8.1.14.

I assume the assets you are using are CM managed? (Have a related CM Item).

If the behaviour is different to meter readings entered via Work Order Tracking (CM) and Assets (CM) this sounds like a bug.

If I could ask you to retry with  ACM Patch 8.1.14 or later then if the behaviour is still reproducible then raise a support case with steps to reproduce so we can investigate.

Thanks.

------------------------------
Lee Cotton
Product Manager

Sustainability Software

IBM
------------------------------

Hi Lee, 

Thank you for your response,

Yes, the assets used is CM managed and has a related CM Item.

Below is the system information, shall try to add the IFIX if not will go for a IBM case then,

IBM Maximo Linear Management 7.6.1.0 Build 20200715-0100 DB Build V7610-04

IBM Tpae Integration Framework 7.6.1.2-MIF_7612_IFIX.20220308-1003 Build 20200715-1444 DB Build V7612-11 HFDB Build HF7612-02

IBM Maximo Asset Configuration Manager 7.6.7.3-20220308-1507 Build 20220308-1507 DB Build V7673-24 HFDB Build HF7673-14

IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build V7611-01

IBM Maximo for Transportation 7.6.2.6-20220318-1429 Build 20220318-1429 DB Build V7626-16 HFDB Build HF7626-18

Hi All, 

This is a bug in Maximo and IBM has released fix pack for the same. 

Things to look after if this issue is occurring with anyone else, check for Organizations setting for Transportation asset meter options if there is Transportation add on in the system.