Identify asset tracked cores for repair - HxGN EAM - 11.07.01 - Feature Briefs - Hexagon

HxGN EAM Core Repair

Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
11.7.1

For parts tracked by asset, the same two options exist as described above for parts that are not tracked by asset. With respect to the equipment structure, both screens will remove the returned core asset from its parents but only the Issue/Return Parts screen has an Attach To field in which you can identify the new parent of the issued asset. The system will automatically create a dependent structure relationship between the issued asset (the child) and the equipment selected in Attach To (the parent). On the Parts tab of the Work Orders screen, without the Attach To field, the work order header equipment will become the parent of the issued asset.

Additionally, there are two more screens where the repair requirement can be identified:

  1. Child Equipment Replacement - On this screen you identify this information:

    • The Parent Equipment of the broken asset to be removed.

    • The Child Equipment which is the asset (part) that is broken and needs to be replaced.

    • The type of transaction. The options are a core return, a return to store or, if the child equipment is beyond repair, a scrap transaction.

    • The New Equipment that will be installed in the place of the old child equipment. If the child equipment has a part number, the new equipment must also have the same part number. Note that this does not allow room for substitute parts.

    • Once all data is entered click the Replace button to execute the swap and the system will remove the child equipment from its parents and will move it back to the store in the quantity to repair if you opted for core return.

      This screen offers additional buttons to attach and detach equipment. Using the Detach button you can also identify a child asset that requires repair.

      All options so far offer similar functionality. They all create a proper return for repair transaction, remove the child equipment from all its parents, and attach the new equipment to the selected parent, either using the Attach To field on the Issue/Return Parts screen, the work order header equipment on the Parts tab of the Work Orders screen, or the Parent Equipment on the Child Equipment Replacement screen as a dependent child. This may work for most implementations, but if multiple parents were attached to the broken child equipment you still must manually create additional structure records, and possibly also change the dependency flag, for the new equipment. These issues do not exist on the Equipment Replacement tab of the Work Orders screen.

  2. Equipment Replacement tab on the Work Orders screen - On this screen you identify this information:

    • The Child Equipment which is the asset (part) that is broken and needs to be replaced. This asset must be a child under the structure of the equipment of the work order. That means finding it will be easy, compared to for example the Issue/Return Parts screen where this context is not used, and you get the complete list of all assets with the selected part number. If the part that is associated to the child equipment is tracked by condition, you can also specify the new return condition of the child equipment. This return condition selection does depend on the type of transaction you select and is controlled by the part condition template setup.

    • The type of transaction. Options again are core return, return to store or scrap.

    • The New Equipment that will be installed in the place of the old equipment. This new equipment may be associated to the same part number as the one removed, but you may also select another (substitute) part and therefore a different set of assets. And if the selected part is tracked by condition, you can further limit the selection of the new equipment to only include assets with that same condition.

    • Once all data is entered click the Replace button to execute the swap and the system will remove the child equipment from its parents and will move it back to the store in the quantity to repair if you opted for a core return. The new equipment will be issued from the storeroom and will inherit all parents from the removed child equipment, including the dependency settings, and will inherit the System Level, Assembly Level, Component Level, and Component Location values from same child equipment as well.

One more remark regarding the Issue/Return Parts screen. For an issue transaction the Swap check box becomes optional if the equipment on the screen (the work order equipment) is associated to the same part as the part that is selected for the issue. However, for a typical core repair swap, this check box may not be so useful since the work order may not be associated to the broken component, but more likely associated to a parent of that broken component. After all, most of the time you do not know yet what is wrong or which part failed when you create the work order. But even if you did write the work order to the broken child equipment that must be removed, or alternatively you have changed the work order equipment to the broken component, it would still only use the Attach To and therefore only create a structure relationship with only one parent. It also does not support substitute parts.

To verify all cores are returned you can use the Unreturned Cores screen. This screen only lists core tracked parts that were issued over a certain period and where the quantity returned is less than the quantity issued. This is the indicator that some cores have not yet been returned.