Root Cause Analysis Deployment

Deploy RCA for the First Time

The following table outlines the steps that you must complete to deploy and configure this module for the first time. These instructions assume that you have completed the steps for deploying the basic system architecture.

These tasks may be completed by multiple people in your organization. We recommend, however, that the tasks be completed in the order in which they are listed.

StepTaskNotes
1Review the RCA data model to determine which relationship definitions you will need to modify to include your custom equipment and location families. Modify any relationship definitions as required.This step is required only if you store equipment and location information in families other than the baseline Equipment and Functional Location families.
2 Assign Security Users to one or more of the RCA Security Groups and Roles. This step is required. Users will not be able to access Root Cause Analysis unless they belong to an RCA Security Group.
3 Specify the Team Charter after you create a new Root Cause Analysis record.This step is optional. A default Team Charter exists in the baseline APM database. You can select the default Team Charter or define your own.
4 Specify the Critical Success Factors after you create a new Root Cause Analysis record.This step is optional. Default Critical Success Factors exist in the baseline APM database. You can select one or more default Critical Success Factors or define your own.
5 Configure ActiveMQ for the Reliability Execution ServiceThis step is optional. Default values exist for the concurrency limit and number of retries for the Reliability Execution Service. You can change these values as needed.

Configure ActiveMQ for the Reliability Execution Service

About This Task

The Reliability Execution Service processes RCA email notification requests. The service uses a single ActiveMQ queue service across APM.

This topic describes how to change the concurrency limit and number of retries for the Reliability Execution Service.

Procedure

  1. On the APM server, access the folder that contains the Reliability Execution Service files. If you have installed APM in the default location, the files are located in C:\Program Files\Meridium\ApplicationServer\ReliabilityExecution.
  2. Access the appsettings.json file.
  3. As needed, modify values of the following parameters.
    ParameterDescriptionNotes
    ConcurrencyLimitThe maximum number of messages to be consumed concurrently.The default value is 2. You can enter 1 or 2.
    RetriesThe number of times to retry sending messages to ActiveMQ in case of a failure.The default value is 10. You can enter a number between 1 and 10.
    "Queue_Config":{
    "Queues": [
        {
            "Name": "RCA_Alert_Queue",
            "IsCancelAllowed": false,
            "ConcurrencyLimit": 2,
            "Retries": 10
        }
    ]
}
  4. Save and close the file.
  5. Restart the Reliability Execution Service.
    The Reliability Execution Service is configured.