Asset Hierarchy Corrections

Contents
Correcting Multiple Hierarchy Errors
Correcting the Most Recent Swap
Correcting a Previous Swap
Viewing Hierarchy Corrections
Technical Details
The asset hierarchy corrections feature transfers data recorded on the wrong asset(s) to the right asset(s) when a component swap was not recorded or was recorded incorrectly in APM. This set of procedures takes you through all of the steps necessary to correct your data.

Types of Errors

The asset hierarchy corrections feature addresses two types of component swap errors: a component installation that was not recorded, and a wrong component installation that was recorded in APM.
When a component installation is not recorded, a component was physically removed and its replacement was installed but the swap was not recorded in APM. As a result, data collected and activities performed against the installed component continue to be recorded against the component that was previously installed.
When the wrong component is recorded in APM, the wrong component was recorded as having been installed at a location. Data collected and activities performed against the installed component are recorded against the component that was incorrectly identified as having been installed.
If the component swap error involves an assembly (a component with child assets), then any data collected on the children will also be recorded against the wrong assets in APM.

Data Affected

Types of data that may be collected and processed incorrectly include the following:
•
Asset Installation History
•
Asset Lives
•
Indicator Readings (all types)
•
Indicator Alarms
•
Work Requests
•
Work Order Tasks
•
Planned Component Swaps
•
Maintenance Costs
•
PM Work Orders Generated Automatically From Standard Jobs
•
Standard Job Triggers
•
Downtime Incidents
•
Vendor Repair Purchase Order Lines
•
Asset Transfers

Functions of Asset Hierarchy Corrections Feature

The automated asset hierarchy correction process fixes the Asset Installation History, Asset Lives, Indicator Readings, Work Requests, and Work Order Tasks by transferring the data from the wrong asset to the correct asset. Indicator readings, except for calculated indicators, are then re-evaluated using the criteria on the correct asset to determine if any alarms or jobs should be triggered. See Technical Details describing how APM transfers the data.
Calculated indicators are not recalculated as part of the automated process. To update a calculated indicator, you have to enter a new reading for any of the indicators included in the calculation.
If you have a cumulative, accumulated value indicator (such as an odometer) collected on the component and location where the hierarchy correction error occurred (not cascaded from another asset in the hierarchy), the automated process assumes that the indicator readings are taken on the location’s indicator. APM copies the location’s reading to the component.
The adjustment value used to correct the cumulative indicator readings is calculated by subtracting the readings taken since the error from the component’s and location’s life-to-date value. As long as the reading is entered for the location, the adjustment value will work to correct the readings on both the location and component.
If you happen to have a situation where a cumulative, accumulated value indicator is collected on the location where the hierarchy error occurred, review the readings for the location and the component manually to determine what the correct readings should be. Once you run the automated hierarchy correction process, review the new readings to ensure they are correct. If they are not correct, enter the correct value as a new reading.

Multiple Hierarchy Errors

Multiple asset hierarchy errors can all be fixed, whether they are at the same location in the hierarchy or at different locations, as long as the components involved were not recorded as installed in other locations after the error. Once the components involved in the correction have been installed in another location, they are no longer available to be installed anywhere, even through the hierarchy correction transaction.
To fix asset hierarchy errors at different locations, repeat the appropriate set of procedures for each error.
It is not possible to return all of the data as it would have been if the swap had been recorded correctly when the physical swap occurred. By running the automated process and manually reviewing the remaining data, you can update the asset’s costs and various documents to ensure that the important data is correct going forward. If you are not concerned about the costs or other data affected by the error, you can simply run the automated process to transfer only the indicator readings to the correct assets.
It is very important to keep the information in APM as up-to-date and accurate as possible to ensure you have high-quality data.

Preparing for Hierarchy Corrections

Before you begin to follow the procedures, you should backup your database to ensure that you can retrieve your data if necessary. You may want to perform the hierarchy corrections at a time when no other APM users are logged into the system.
These procedures include manual steps to review PM work orders and the standard job triggers that created them, to correct maintenance costs, to correct downtime incidents, to update vendor repair purchase order lines, and to correct asset transfers.
Complete the set of procedures for the description that matches your situation.

Correcting the Most Recent Swap

Follow this set of procedures when the incorrect swap is the latest swap recorded in APM for the location. No swaps have occurred for this location since the error.

Correcting Multiple Hierarchy Errors

Follow this set of procedures when more than one hierarchy error has occurred at the same location. Two or more physical swaps for a given location have been recorded incorrectly, or not at all, in APM.

Correcting a Previous Swap

Follow this set of procedures when a component swap error happened before the current component installation. The current component installation in APM is correct, but a previous swap was recorded incorrectly or not at all.