Maximo Open Forum

 Continuous Meters- Sliding Days

  • Everything Maximo
  •   IBMChampion
David Pattengale's profile image
David Pattengale posted 10-08-2024 12:04

I am wanting to confirm a meter plan I am working on. I cannot find the specific answer I am looking for, so I am hoping someone can confirm if I am correct- (or not)

I have a group of assets that all have the ability to send readings to Maximo.  I want to add continuous meters to them to measure  pressure. When I look at the samples, the readings vary a lot , higher, and lower. My thought was to use the Sliding - Days calculation, set for (1) day. When I pivot the data like that in excel I get a very predictable trend  graph.  What I need to know is: does Maximo collect the days worth of readings, and then perform the calculation that ends up as the meter reading?  Thanks in advance for any assistance.

Steve Norris's profile image
Steve Norris

Hi David,

Could you confirm the use case for these meters? Typically continuous meters are used for readings that always increase like run hours or kms driven. For pressure readings, that is typically a use case for a meter type of "gauge", used in conjunction with condition monitoring points that generate CM work orders when the readings are not within the established "normal operating range".

Regards,

Steve

David Pattengale's profile image
David Pattengale

Sorry, a gauge meter is more appropriate for this- same question applies though. The equip. is reporting readings every 15 minutes. Can I use sliding Days for a gauge meter?  I am looking for a way to work with the constant stream of variable readings coming in.

Steve Norris's profile image
Steve Norris

Hi David,

Gauge meters do not utilize calculation methods, that is reserved for continuous meters. Rather the gauge meter readings are stored against a measurement point associated to the asset in the Condition Monitoring application. From there, the data can be extracted for analysis, but perhaps consider a KPI within Maximo. Again, not fully understanding your use case it is difficult to recommend a solution. For reference, https://www.ibm.com/docs/en/mam/7.6.1.2?topic=module-condition-monitoring-application

Regards,

Steve

David Pattengale's profile image
David Pattengale

Thank you for your help so far Steve, really appreciate it. The customer has a group of air handler assets that they want us to attach meters to. the assets are currently generating readings every 15 minutes that are sent to a report that can be dropped into Excel. At this moment, those readings are collected and stored, but there is nothing setup in Maximo other than the Asset's info. Adding the meters would be easy, the issue is how often the data is being sent, and the variation in those readings throughout the day. I took the data and did a pivot of each day for a month. When I do that you can clearly see the asset readings consistently trending towards needing a filter change PM. I was envisioning some way of grouping a day's worth of readings, then sending the average to Maximo as the meter reading. If I take one reading, I think I may get unreliable results. Is there a way to group those readings then produce an average reading each day that gets imported into Maximo?  Hope I made it clearer.

Craig Kokay's profile image
Craig Kokay

Hi Steve,

Firstly, Maximo is bad at interpreting data that float between a range and trending (i.e. no trending) to estimate when it will breach the nominated threshold.

Second, gauge meters are designed for readings that float and to take action ONLY when the threshold is breached.  This means that literally nothing occurs until that point.  Some will say "Well, we should have seen that it was about to breach and do something about it!", but this is not the case for Maximo's interpretation of condition monitoring.  You need to set the action value such that when breached there is sufficient time to do "something" about bringing the asset back into line with the desired performance.

An example is with a differential gauge set across the filter, it has a 0 to 50 bar range.  The condition monitoring point warning is set to 0 bar for lower warning and -5 bar for an action to take place.  The upper warning is 40, action is 45.  What should occur is that as the filter gets blocked the differential increases. So, the 5-bar allowance 45-50 bars is designed to provide sufficient time to replace the filter, and the 10-bar allowance 40-50, provides an indication that something may exceed the action in the near future, though that time is an unknown.  Please note that a low bar reading means that there is no issue, so a reading of 0 means all is perfect.  A vacuum is not expected for this scenario.

In Maximo, only the upper/lower action points cause a work order to be generated, there is nothing for the warning.  You would need to create some mechanism (escalation) that polls the CM points for those exceeding the warning value.

What else can be done?

  • Create a report the displays all the gauge meters exceeding the warning, but not yet the action.
  • Implement Maximo Monitor and have that report a single daily figure and to monitor the trend, and where the trend exceeds a nominated value, create a work order.
  • Use BI to monitor and report

Maximo is not designed to store and interpret high-volume data; that is for other external systems such as Maximo Monitor or PI or SCADAs, and Maximo receives, maybe(?), information once a day like the average reading for the past 24 hrs.

Regards, Craig Kokay

Principal Consultant, COSOL

#IBMChampion

David Pattengale's profile image
David Pattengale

Thank you for the explanation, Craig, That was very helpful. it looks like Monitor would be the way to go. We will look into it!