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.

Ah, that makes perfect sense.  Thanks Nancy!

Hi Nate. 

I came across your thread while searching for the answer to the same question.

To me, it would make much more sense if it were a comment on the measured value rather than a comment on the meter itself. I don't see why our end-user should be able to add comments to the meter; that should be reserved for us as admins.

Steffen Lund Schjoldager

Maximo Specialist • Engineering Systems
SundogBaelt

www.sundogbaelt.dk

Hi Nate,

Sometimes it seems that there is no logic.  There are two use cases here:

1. As a technician, I need to see any specialist information about either the meter or, more specifically, how to take the reading for that meter, so that I can correctly take a reading.
2. As a technician, I need to be able to record commentary about that specific reading, so that the engineer or the like, when reviewing the meter reading history, can see my comments, so that they can take any action that may be necessary.

As Steffen has said, based on use case #1, it would seem to be illogical to give the technician the ability to edit the remarks field based on the premise that it's information to do with that meter on that asset.  It's great that the field is available when taking a reading, but in truth, not many technicians take the time to expand the row to ready it.  Therefore, the field should be promoted to the summary row of the table, made read-only, and, as Nancy mentioned, also relabelled.

Also, as Nancy said, you can add a memo field for use case #2.

I have raised the following IBM Ideas

• IBM Ideas MASM-I-1913 raised
• IBM Ideas MASM-I-1914 raised

Hi Nate, 

The simple answer is the meter reading is related to the asset. See the high-level visualization can be found in the attached ERDs (Maximo 7.1 - 7.5). The relationships and logic can be found in Database Configuration for the Asset Meter table. For additional related tables, (e.g. MEASUREPOINT)

• METERREADING Table (Transaction Log): This operates as a historical log. Every single time a technician inputs a value, a row is created here with a unique METERREADINGID.
  • Asset-to-Reading Flow (Third Diagram): The relationship uses the ASSET table's primary keys (ASSETNUM, SITEID) to look up corresponding transaction history rows inside METERREADING.

• MEASUREMENT Table (Condition Monitoring Point): This table is populated when a reading is tied to a specific MEASUREPOINT (as shown in your final diagram layout). Maximo copies valid values here specifically to evaluate if an action boundary has been crossed (e.g., triggering a PM or Work Order).
  • Asset-to-Measurement Flow (Second Diagram): The MEASUREMENT record maps to an active MEASUREPOINT linked directly to your ASSET record. Maximo's application layer references this relationship framework to evaluate condition boundaries and fire cron tasks or background automation.

                  ┌───────────────┐
                  │     METER     │
                  └───────┬───────┘
                          │ (metername)
        ┌─────────────────┴─────────────────┐
        ▼                                   ▼
┌───────────────┐                   ┌───────────────┐
│ METERREADING  │                   │  MEASUREMENT  │
└───────┬───────┘                   └───────┬───────┘
        │ (assetnum)                        │ (assetnum)
        └─────────────────┬─────────────────┘
                          ▼
                  ┌───────────────┐
                  │     ASSET     │
                  └───────────────┘

The attached query example. 

Attachment(s)

MeterReading_Asset_Measurement.pdf   58 KB 1 version