Replacement Causes
In this module, you can view all the Replacement Causes registered for the current asset. Each cause can be associated with components or subgroups. When maintenance is performed, the replacement cause will only be applicable to the components it is associated with.
Adding Replacement Causes
To add a replacement cause, use the Add Replacement Cause button, which opens a window where the required data can be entered (Image B). The information to be provided is as follows:
Cause Code: unique code identifying the cause;
Severity: an integer value indicating the severity of the cause;
FMECA: flag specifying whether the current replacement cause should be considered as FMECA (relevant breakage I want to further inspect) type or not;
Translations: for each cause, translations must be entered both for the effects and for the cause name itself. Translations must be provided in all project languages.
Associating Components and Subgroups
To associate components and subgroups with a cause, use the Select Components and Subgroups button highlighted in Image C. A window will open as shown in Image D, displaying the full component hierarchy and allowing you to select objects.
If a component is selected, only that object will be linked to the replacement cause. If an entire subgroup is selected, all components currently included in it and any added in the future will automatically be associated with the cause.
Uploading Attachments
Each replacement cause can have multiple attachments associated with it. The Attachments button in Image C opens the view shown in Image E. Here, all attachments related to the specific cause can be managed. In addition to adding or deleting files, it is also possible to download a zip file containing all of them.
Excel Catalog Upload
To upload multiple replacement causes at once, an Excel file can be used. The buttons allow you to either import an Excel file or download one containing the application’s current data.
For more information on the file structure and guidelines on how to complete it, please refer to the dedicated documentation.