The music is called Busy City from a group called TrackTribe.
Hello, and welcome back to Maximo Bite Size. A series of videos on the functional aspects of Maximo Manage.
Good evening, it is Andrew Jeffery here and welcome to the third episode in the series on Asset Management. Today we’ll be introducing you to three closely related applications, Meters, Meter Groups and Condition Monitoring. In the fourth episode we’ll dive a little deeper in the use of meters on assets and A physical place where assets exist and where work can be performed. More, so stay tuned for that.
Please subscribe to this channel so that you don’t miss out on new episodes as they are published.
We’ll start today in the Meters application and we’ll explain the three types of meter used in Maximo.
Meters have been around in Maximo for at least 25 years, but Meter Groups, where we will head next, only appeared in version 6.0, around 2004, and I expect some Maximo clients are not using these. It is in the Meter Groups application where you may add more details for run-time meters, so we’ll take a closer look at this.
Finally, we will take a look at the Condition Monitoring application, and its linkage with meter readings.
So, let’s get started.
The Meters application is a simple one with only a few fields. It defines a meter that is used on an asset or location. There is no status field for a Meter and Meters are added at the System level in Maximo.
There are three types of meter.
A CONTINUOUS meter is one where the meter reading increments over time unless it is reset, or it rolls over. Think of a utility meter or the meter in your car that tells you how many miles or kilometres have been travelled. This is the most common meter type as it is the type used with meter-based Preventive Maintenance. With a CONTINUOUS meter you need to decide whether the meter reading type is an ACTUAL or a DELTA reading when compared to the previous reading.
A CHARACTERISTIC meter is used for an observation, the values of which can be selected from a domain set of values. This might be how filthy your car is from Clean, Minor Dirt, Dirty, to Very Dirty, and you would take action when the observation value you make at the beginning of the week assesses your car as Dirty or Very Dirty. With a CHARACTERISTIC meter you will need to specify the ALN Domain to be used for the observations, other types of domain can’t be used.
The third type is a GAUGE meter that records a numeric measurement the readings of which can fluctuate over time. Think of the pressure gauge on a car tyre, you could record the measurement at the start of each week and when it drops below a certain level you need to take action.
For a CONTINUOUS or GAUGE meter it is a good idea to indicate the unit of measure, this is not needed for a CHARACTERISTIC meter.
The Where Used tab indicates where the meter has been referenced, and there are five tabs to show the Assets, Locations, PMs, Items, or Condition Monitoring records where the meter is used. A meter on an Item or Tool is most often used for measuring fluid consumption, for example the diesel or petrol you put in your car.
There is also an action for viewing the meter groups where the meter has been referenced, and it is the Meter Groups application where we are heading next.
A Meter Group as the name implies is a set of meters that are used together. When a meter group is applied to an asset or location, the meters in the meter group are copied over to become asset meters or location meters. The Sequence field is used to sort the meters in the meter group. All three meter types can exist in a meter group.
One advantage of using a meter group is that a new meter can be added to the meter group, and you can choose whether it should also be added to all assets and locations that reference this meter group. The table field ‘Apply This Meter Where Group Is Used?’ is defaulted from the header field ‘Apply New Meters Where Group Is Used?’ . When adding a new meter the table field can be modified until you save the meter to the meter group, when it then becomes read-only.
There is no status field for a Meter Group and Meters Groups are added at the System level in Maximo, the same as for Meters.
Meter Groups can be referenced on an Asset Template, and this adds the associated meters to the asset template.
A Meter Group can also be referenced on an Item or Tool of type Rotating. When an asset is created and references the item or tool, then the meter group is copied, and the asset meters created for the set of meters in the meter group. The same process also applies to a location that references a Rotating Item.
For CONTINUOUS meters only, additional setup is required in the details area of the meter in the meter group as shown on the right.
For continuous meters you should add the point at which the meter will rollover , and I would use the decimal places.
The field Average Calculation Method determines how the average units per day field is calculated for the asset or location meter. This is used by meter-based Preventive Maintenance to determine when the PM will fall due. The Select Value shows four options:
- ALL is the default and takes into account all previous meter readings. This is fine to use where an asset is in constant operation and does not stand idle for long periods of time.
- STATIC is where there is no recalculation and you enter an average value in the Static Average field at the bottom right corner of the details area. This might be used when you don’t have a history of meter readings in Maximo but you can work out a historical average, or you have an average that you wish to apply for meter based PMs.
- SLIDING-DAYS is used where the use of the asset is variable and where you are taking meter readings on a relatively frequent basis, at least once per week, with regularity, i.e. at roughly the same time each day or week. With a SLIDING-DAYS setting and a Sliding Window Size of 5 , the calculation will be based on the average delta change over the last 5 days.
- For a SLIDING-READINGS setting and a Sliding Window Size of 5, the calculation will be based over the average delta change over the last 5 meter readings.
If a meter reading is performed each day of the week, the SLIDING-READINGS will give the same result as SLIDING-DAYS. However, if no meter readings are taken on a Saturday or Sunday, then there will be a difference in the average between the two calculation methods.
To determine whether to use SLIDING-READINGS or SLIDING-DAYS you need to ascertain how often you take a meter reading and whether the pattern is regular or irregular. With either of these two settings you need to bear in mind that an average over two readings is not a good average, you do need a larger number of readings. You also need to consider the pattern of use of the asset and you may need to take meter readings more frequently to use these settings.
The Condition Monitoring application is used to create measurement points for GAUGE meters or observation points for CHARACTERISTIC meters. The application is not used with CONTINUOUS meters. As these records will always reference either a location or asset (and not both), then this is a A structural element of a Maximo database that is used for data separation. More level object in Maximo. There is no status field for a Condition Monitoring Point.
To create a Condition Monitoring Point you need to reference a location or asset , and a meter. The Point field , called POINTNUM in the table, is often a field which has been generated by the autokey, it is the unique identifier for the record. Some clients use a prefix aligned with the asset class. However, I would leave this as an autokey with no prefix for the reason that the proliferation of sensors and alarm conditions would slow down the process of creating MEASUREPOINT records if you gave meaning to the structure of the identifier. You can always configure the asset class onto the application using a relationship back to the ASSETS object and add it to the Advanced Search or List tab to make it easier to query.
The measurement or observation is recorded as part of a meter reading. You create a Condition Monitoring point if you wish to take action when a measurement exceeds upper or lower action limits, or an observation reaches a certain value. If you are not going to generate work orders when this occurs then there is little point in creating a Condition Monitoring record. You can record the measurement or observation direct in the Condition Monitoring application or through an integration point from an external source, but it is now normal to record these values through meter readings because meter readings are also used for CONTINUOUS meters.
Meters of type GAUGE or CHARACTERISTIC can be referenced with their asset or location to create a condition monitoring point. When a record is created in the Condition Monitoring application the key field, POINTNUM, is copied to the asset meter or location meter record, which must, obviously, exist first. For GAUGE or CHARACTERISTIC meters the meter reading is copied through to the MEASUREMENTS table and the Measurement or Observation fields using the POINTNUM field as the key.
When setting up a Condition Monitoring point you need to specify the upper/lower action limits and the Job Plan or PM that will be used to generate a work order if the action limits are exceeded. The work order’s priority is also normally set. It is slightly different for CHARACTERISTIC meters in that you enter the values from the meter’s ALN domain that require an action, which does mean that you could use different job plans, PMs or priorities for each value.
Work orders are generated either manually or through a background Cron Task and the work orders generated are visible in the Condition Monitoring record. The work order status will be Waiting to be Approved (WAPPR) and there will be a blank work type.
For GAUGE meters you can also enter the upper/lower warning limits but there is no Maximo functionality that uses this. There is also no Maximo functionality that allows Condition Monitoring records to be created from a template and unusually for a Maximo application there is no Duplicate action. An Application Import could be configured to allow condition monitoring points to be created from a spreadsheet.
Thank you for watching
I hope you have enjoyed this episode on Meters, Meter Groups and Condition Monitoring and found it useful, and thank you for listening. We would like to see you back in our next episode when we will return to the Assets module and take a closer look at Meter Readings. Don’t forget to hit the Subscribe button, and if you enjoyed this video please give it a thumbs up.
Until another time, Goodbye.