Maximo Open Forum

I am looking for some help on the best method to address a situation we have. I have done some searching and cannot find a solution. Scenario: we have large assets like bulldozers, tractors, hoists, generators, etc. all of which are assets themselves. Some of these assets are actually used to do maintenance work on other assets. At times multiples. So we have a WO to do maintenance on Asset 1. Asset 2 and 3 are used to perform the maintenance on Asset 1. We want to log the time each of Asset 2 and 3 was used in performing the maintenance on Asset 1. In the past, they have been using the asset field on the Actual Labor row to log this time OR were putting it in a Work log (which is impossible to report against). My question is, is there a better way to track the time on Asset 2 and 3 besides using the asset field on the labor row?

------------------------------
Diane Carr
PAE
------------------------------

Hello Diane,

What if you create Asset 2 and Asset 3 as Rotating Tools and declare them in JobTool ?

------------------------------
Frederic Conti
Maxinfortech
------------------------------

Yes, that was my first choice but, I was told today that we can't implement Rotating Assets or Tools because they were told they had to set it up when they implemented Maximo and they did not do that so now we cannot use them. Is this true? I have used Maximo for many years and have never heard this.

------------------------------
Diane Carr
PAE
------------------------------

Original Message:
Sent: 10-05-2021 15:24
From: Frederic Conti
Subject: Assets used in Mainttennce

Hello Diane,

What if you create Asset 2 and Asset 3 as Rotating Tools and declare them in JobTool ?

------------------------------
Frederic Conti
Maxinfortech
------------------------------

As usual, the devil is in the details . . . I can't say for sure without knowing the specifics of your Maximo configuration and customization , but in out-of-the-box Maximo you can associate an existing asset with a Stocked Tool.  The result will be a rotating asset that you can add to the Actuals tab of a work order allowing you to capture the specific asset and hours and costs.

------------------------------
Mack Parrott
Projetech Inc.
------------------------------

Original Message:
Sent: 10-08-2021 19:25
From: Diane Carr
Subject: Assets used in Mainttennce

Yes, that was my first choice but, I was told today that we can't implement Rotating Assets or Tools because they were told they had to set it up when they implemented Maximo and they did not do that so now we cannot use them. Is this true? I have used Maximo for many years and have never heard this.

------------------------------
Diane Carr
PAE
------------------------------


Original Message:
Sent: 10-05-2021 15:24
From: Frederic Conti
Subject: Assets used in Mainttennce

Hello Diane,

What if you create Asset 2 and Asset 3 as Rotating Tools and declare them in JobTool ?

------------------------------
Frederic Conti
Maxinfortech

Diane, I see a couple of options here . . . some requiring more keystrokes than others, so the business benefit-effort needs to be considered.

1. As Frederic mentions below, you could change the 'support-assets' to rotating tools and add time for them on the Actuals tab of the work order similar to Labor
2. On the 'fix-the-machine', add one or more child work orders that are associated with support-assets. The child WO(s) would be associated with the support-asset as a work order hierarch
     - All actuals (time, material, etc.) charged to the child support WOs would roll up to the parent and this would create good history records to report on
3. On the 'fix-the-machine' work order, add one or more job operations for the support-assets (the asset on a job operation can be different between the parent WO and the job operation).
     - This would have the benefit of including support-assets time on the parent WO although the time reporting would be a labor transaction.
4. Not sure of your Maximo version but you should be able to add the support-assets to the Multiple Assets and Locations table of the primary work order. The disadvantage here is that the time worked by the support-assets can't be individually tracked. This would just reflect the fact that the support-assets were related

Option one is probably the cleanest as the support-assets are truly tools.  Converting to tools may require some painful master data revisions.  My favorite is option two which could be implemented with existing data.

Good luck!

------------------------------
Mack Parrott
Projetech Inc.
------------------------------

Thanks these are good Ideas, I will let you know what we come up with.

------------------------------
Diane Carr
PAE
------------------------------

Original Message:
Sent: 10-07-2021 09:11
From: Mack Parrott
Subject: Assets used in Mainttennce

Diane, I see a couple of options here . . . some requiring more keystrokes than others, so the business benefit-effort needs to be considered.

1. As Frederic mentions below, you could change the 'support-assets' to rotating tools and add time for them on the Actuals tab of the work order similar to Labor
2. On the 'fix-the-machine', add one or more child work orders that are associated with support-assets. The child WO(s) would be associated with the support-asset as a work order hierarch
     - All actuals (time, material, etc.) charged to the child support WOs would roll up to the parent and this would create good history records to report on
3. On the 'fix-the-machine' work order, add one or more job operations for the support-assets (the asset on a job operation can be different between the parent WO and the job operation).
     - This would have the benefit of including support-assets time on the parent WO although the time reporting would be a labor transaction.
4. Not sure of your Maximo version but you should be able to add the support-assets to the Multiple Assets and Locations table of the primary work order. The disadvantage here is that the time worked by the support-assets can't be individually tracked. This would just reflect the fact that the support-assets were related

Option one is probably the cleanest as the support-assets are truly tools.  Converting to tools may require some painful master data revisions.  My favorite is option two which could be implemented with existing data.

Good luck!

------------------------------
Mack Parrott
Projetech Inc.
------------------------------