Why use a Location hierarchy?

I am with a client who has created a detailed asset hierarchy (for Trams) using "virtual" assets to manage rotables.

There is no System and only one Location that covers all 6000+ assets. Asset moves have 'kind of' worked but occasionally non rotable children of the rotable become orphaned.

Finance is also handled in an unconnected system.

I have modelled alternative structures for these assets with a short and a long location hierarchy.

Apart from the basic rationale that IBM supply, has anyone gone into further detail about the value of a well built Asset location hierachy in maximo?

I'm looking for the compelling business argument and benefit to change. It's easier to sell with a vanilla implementation.

Thanks in advance.

Geoff

Cheers

Geoff

The rationale that is often used is that Location Hierarchy should reference the overall "Asset" that is being maintained and Locations represent the elements that do not regularly change. It might relate down to an individual P&ID reference, a UWI or Padmount etc. i.e. the place that an Asset is physically located. The individual Asset (Equipment) that currently resides at that Location is recorded as such because it is interchangeable. This is often referred to as one is operating, one is spare and one in repair. The Location in the overall Asset does not change but the serialized, rotating item (asset) does. This makes the moving of Assets much simpler because the Location is independent from the Asset Hierarchy. Asset Hierarchies can then be used for complex Assets and components that have to tracked such as a Aero Engine.

Helen Fisher

Marketing Manager at BPD Zenith

Happy to be contacted at: helen.fisher@bpdzenith.com

Hi Geoff
We can make this simple to complex, let's try simple.  The value of a good location hierarchy establishes when the maintainable item is located, therefore making it easy to find, thus reducing time = reduce costs.

Sometimes in transportation we need to think differently as there are so many parts that make up as machine/vehicle and parts of those vehicles can be rotated.  In your case, the rail upon which the trams run are usually designated on the lines or routes that they run = locations (system 1), then using linear they are broken into maintainable sections = assets.  Whereas as those things that run on top = trams (single mobile asset...or that really true?), you can have them assigned as a single location assigned to a depot i.e. where the usually reside when not in operation or the workshop to which they return, then you may have high-level sub-systems (more locations) for the key operational/maintainable areas (system 2) such as control gear, catenary, running gear (boggies), passenger system, and safety systems.  At those discrete level, then you can start to add the maintainable assets.

Maximo for Transportation can offer you another view, having one location and one asset, then whenever you report work or set-up PM's, you can then say the system involved.

By having the space (location) where there asset resides, this makes it very easy to rotate the asset.  The most important thing is to auto-number the assets.  Think of it like, I have a computer (asset #1) that reside in the office (location 1) and I plug-in a USB thumb drive (asset #2), I remove the USB, and insert a USB hard drive (asset #3).  I didn't have to have a sub-location to recognise that a USB was connected to Asset #1, nor did I have to have a child-location.  I can look at the computer (location) and see all the assets connected at any point in time.  What I wouldn't get is a description of a hierarchy. Is that needed?  What is the reporting requirement.  Can I location where the USB is currently?

Let's extend that thought.  If the computer only had 2x =USB3.0 and 1xUSB2.0 ports how can I recognise that?  The simplistic view is to create three sub-locations with each having a respective spec describing the type of USB allowed.  Then when ever I connect a USB to the computer I need to find the computer, then select the correct sub-location.  The one thing with this is that OOTB Maximo does not enforce the number and type of USB connected i.e. I cannot attach four USB's, but I can put a USB2.0 into a 3.0 port, but it may not be the reverse.

Therefore the extension, and this applies for transport and complex assets where it is important that the configuration must be enforced is to use Asset Configuration Manager (ACM), an extension to Maximo.

So, Geoff, the answer has to be feedback to you.  What is it that's hurting your business with the current structure?  Does is support the maintenance plan?  Is it easy to use and find assets in order to report work.  What about your meters?  Will what you have today, work for you when mobility is implemented?

As always, happy to have a chat.

Regards, Craig Kokay

Maximo Practice Lead

Ph: +61-411-682-040

email: ckokay@isw.net.au