We currently have the majority of our assets setup with a classification of ‘Maintainable Asset’. We are looking to re-class assets from ‘Maintainable Asset’ to ‘Component’ & ‘Component Location’. We have several years of history captured on the assets that we do not wish to loose.
Do you have a preferred method to convert the classification of an asset from ‘Maintainable Asset’ to ‘Component’ & ‘Component Location’ without losing the history contained in the Work Management, Work ID & Reliability Program views?
There are two options:
Either option will have some limitations, however.
Option 1
With this option you get indicators, standard tasks, and standard jobs copied from one to the other. The indicators is OK, since you probably do want indicators on both the location and the component. However, the duplicate standard tasks and jobs mean there will likely be some clean up required. Someone will need to review the tasks and jobs to determine whether they belong on the location asset, the component asset, or perhaps both.
Typically, the location asset will have the tasks and jobs that are applicable to any component installed into the location. These are the tasks/jobs that pertain to the component while installed and operating. The component asset will likely only have task and jobs that pertain to the component when it is uninstalled. These tasks may be for activities such as a rebuild, or routine maintenance to be done on an uninstalled (spare) component.
As you might expect, the work orders and work order tasks are not copied, and will remain linked to the asset for which they were originally written. There is no way to link the work orders to the new asset. This will require custom programming, if you want this.
The duplicate indicators are not a problem, and likely what you want. The location asset tracks the indicator for any installed component. The component asset tracks the indicator for the asset when it is installed in any location (or while uninstalled, if that makes sense).
Option 2
With this option, there is less clean up, perhaps. In this case, the indicators, standard tasks, and standard jobs remain only on the original asset. For this option, you would want to make the original maintainable asset be the location asset. The component asset would be created new.
When the component is installed into the location, the location's indicators will be duplicated on the new component asset. The end result is the same would be for option 1.
The difference now, is that someone would review the standard tasks and jobs on the location asset, and reassign some of them to the component asset, for the same reasons as outlined for option 1. The work orders created from the standard task and jobs will remain linked to the location. You will still require custom programming to also link the work order tasks to the new component asset.
We suggest that you continue to explore both options in a test environment, until you have worked out the logistics of having both location and component asset have the information you want.
N/A.