Maximo

Hi Manikanda,

First, it's very confusing that you're saying that mobile assets cannot have a location.  Of course, they can.  Let's discuss what mobile plant I am talking about.  You mentioned lifting equipment so that can be:

• Cranes, tracked
• Cranes, wheeled
• Cranes, HIAB
• Slings and strops
• Hydraulic power packs
• Bottle jacks
• D-shackles
• Pulleys
• etc...

So, if you have a piece of lifting equipment that is fixed to a vehicle, the vehicle is the location for the asset.  The vehicles' location can be:

• Nothing
• A 'home' location

Is there an advantage of one over the other?  In reality, it's about finding the asset or group of assets.  The location of the mobile plant can tends to be either:

• "Mobile plant", so you know where all the assets that don't have a fixed home reside
• A vehicle
• A cost center like a workshop
• A storeroom

Now we have that framework, let's say that we have used a storeroom as the home location.  When a piece of mobile plant is taken, it is (assumption) then placed onto or installed onto a vehicle.  A HIAB crane is installed onto vehicle "HB8218".  A 10T sling is removed from the sling storeroom and placed onto vehicle "HB8218" until it is returned to the storeroom.  There may be times when an asset is better off being issued to a person (aka a labor location).

But what about the vehicle "HB8218", well that will have a location like the workshop or other suitable location of where the costs for maintenance will be incurred, and that could be even an office, yard, or 'virtual' location.

Having any location is far better than no location because when you look at the asset, you know where you should be able to find it. This can be very useful because you need to be able to locate the asset so you can inspect or perform maintenance on it.

So, for the mobile plant, you would set-up the route stop using the asset number because the asset may have moved when the PM is generated.

There is one more thing to note.  This assumes that everything is/has:

• A serial number
• Has been made a rotating asset

Hi Manikanda,

The use case is very interesting, as Craig says it is better to have a location than not to have one, especially if you will later manage costs related to the work that will be carried out on the asset, whether preventive, corrective or predictive actions and that incorporate resources and efforts.

I recommend that you take a look at the ISO14224 standard, where you can see in section 8.2 taxonomy, here you will find a very useful reference within the 9 levels per standard (which you may or may not take, depending on the complexity of your locations and assets), there is a "section or system" level, which can group assets that perform a function in relation, in oil and gas examples from that sector are used, but to take it to the general level, this is aligned with ISO55000 in the definition of "asset systems" that defines all assets that are related to each other to perform a specific function such as: lifting equipment.

The previously mentioned asset system is known by standard as grouping locations or asset systems, the important thing here is as Craig mentioned each asset is unique and has its category and class and it is even more recommended that they have a location within the system, especially for the financial plan, the cost centers of locations often determine your levels and the groupings of asset systems.

For example, I have robot dogs for inspections and my company determined a cost center for all their maintenance and certifications, all service expenses, external labor and spare parts are charged specifically, this is why we have created the asset system as a location "BL1-1-LAB-AS1: building 1, first floor laboratory area, robot dog asset systems" because regardless of where they are servicing or moving their life cycle expenses will go to the same cost center, this is why it is good to have an operational perspective but also a financial one.

I hope this is helpful

David Iñiguez

We have several similar use cases when assets are not repaired on site but switched (the one in bad condition is removed, sent far away for repair and replaced immediately with one in good condition). Plus we dont want to intricate location hierarchy within asset hierarchy (simplicity is mother of robustness). So, as you, we would need to determine lately, at the wo generation the right assets to inspect (those in prod).

Currently we plan to create an autoscript to apply all assets from a certain itemnum under a certain location in MultiAssetLocCi.

We will probably add an extra attribute for itemnum ref on pm and create pm with a location AND a itemnum.