Troubleshooting Scenarios

The following topics can help you troubleshoot issues that you may have with the Failure Modes and Effects Analysis module:

Dashboard Tile Count Does not Appear or Takes Longer Time to Load the Count in the RCM/FMEA Overview Screen

Description

In the Applications menu, navigate to the STRATEGY section, and then select Failure Modes and Effects Analysis. The dashboard tile count takes longer time to load or it does not appear in the module overview page.

Cause

This issue may occur if any of the database indexes are missing.

Solution

Perform the following step:

Run the following script for the RCM/FMEA equipment, recommendation, and the RCM/FMEA recommendation families. This improves the loading performance of the Failure Modes and Analysis Overview page.

CREATE NONCLUSTERED INDEX [<N_MI_RCMEQPMT_ID_NK>]
ON [dbo].[MI_RCMEQPMT] ([MI_RCMEQPMT_EQUIP_ID_C])
INCLUDE ([ENTY_KEY])

CREATE NONCLUSTERED INDEX [<N_MI_REC_ANALY_KEY_FK>]
ON [dbo].[MI_REC] ([MI_REC_ANALY_KEY_NBR])
INCLUDE ([ENTY_KEY])

CREATE NONCLUSTERED INDEX [<N_MI_RECRCM_ACTIO_TYPE_FK>]
ON [dbo].[MI_RECRCM] ([MI_RECRCM_ACTIO_TYPE_C])
INCLUDE ([ENTY_KEY])

These indexes have been added to the baseline product, in version 4.4. This step is applicable to Version 4.x and earlier versions.

Note: Run the script directly in the database.

Data Loader Does not Load Recommendations Instead a Warning Message Check for Possible Orphaned Records

Description

In the Applications menu, navigate to Tools > Data Loader > APM Strategy > Failure Modes and Effect Analysis (FMEA) and then import the attached file.

When you load the data loader, the following warning messages appear:

<Date/Time>|Batch [0001]| Warn - The Assets table contains 1 records but only 0 were loaded. Check for possible orphaned records.
<Date/Time>|Batch [0001]| Warn - The Recommendations table contains 7 records but only 3 were loaded. Check for possible orphaned records.

Cause

The failure effect names may not be unique.

Solution

Procedure

Ensure the failure effect name is unique, so that the data loads without errors.

RCM Data Loader Gives an Error After Loading the RCM Data

Description

The following error appeared when loading the RCM/FMEA data loader:

2021-11-02 10:19:44.0206|Batch [0015]|ERROR| RCM FMEA Recommendation '<Recommendation name …> ' was processed more than once due to ambiguity in reference column information.

2021-11-02 10:19:44.0215|Batch [0015]|DEBUG| Finished processing Batch [0015]

Or

2019-11-25 11:47:47.635412|Batch [0001]| Error - RCM FMEA Failure Mode ‘<Failure Mode name…>' was processed more than once due to ambiguity in reference column information.

2019-11-25 11:47:49.104147|Batch [0001]| Debug - Finished processing Batch [0001]

Cause

The dataloader file contains duplicate names in the Failure Effect, Failure Modes, Recommendations, and Secondary Action sheet as there is no option to differentiate the duplicate names in the datasheet.

Solution

Perform one of the following options:

Do not have same Failure effect or Failure mode or Recommendation or Secondary action names.
If you cannot implement the first option, then the column Related Asset ID must be added in the Failure Mode, Failure Effect, Recommendations, and Secondary action sheet.

FMEA Analysis Templates Data Loader Error

Description

Importing a Failure Modes and Effects Analysis (FMEA) templates data loader triggers an Internal Server error if length of the field input file exceeds 200 character. This error occurs with specific users and templates.

Cause

The length of the data loader template file name exceeds 200 characters.

Solution

The data loader template file name must be reduced to a maximum length of 200 characters to mitigate this error.