Maximo Open Forum

Anyone understand IBM's logic behind this, or would you consider this a bug?

If you have a characteristic meter on an asset, and you enter a meter reading, you can enter a remark.   Maximo writes the meter reading to both the asset meter table (which is what is shown on the asset meters tab), as well as the measurement table (which is what is shows on the manage meter reading history screen).  

When a new meter reading is entered for the asset, Maximo writes a new entry to the measurement table, and overwrites the assetmeters table.  So, the remark is not stored, and there is no way to add it to the manage meter readings history screen.

Curious to get your thoughts.. is this a bug, or is there a reason for this that I cannot think of. 

Thanks!

I think the intent was to provide a place to store a remark about the meter itself, such as notes about where the meter is located.  Changing the label to something like "Meter Location Notes"  would help clarify the purpose of the field. There is not a field in the measurement table to store a memo, and the only "comment-like" field available in the meterreading table is the reason field, which is supposed to be for an explanation of a reading modification.  You could add a memo field to both the measurement and meterreading tables to capture comments about a specific reading/measurement/observation.

Anyone understand IBM's logic behind this, or would you consider this a bug?

If you have a characteristic meter on an asset, and you enter a meter reading, you can enter a remark.   Maximo writes the meter reading to both the asset meter table (which is what is shown on the asset meters tab), as well as the measurement table (which is what is shows on the manage meter reading history screen).  

When a new meter reading is entered for the asset, Maximo writes a new entry to the measurement table, and overwrites the assetmeters table.  So, the remark is not stored, and there is no way to add it to the manage meter readings history screen.

Curious to get your thoughts.. is this a bug, or is there a reason for this that I cannot think of. 

Thanks!