Reliability Analytics Deployment

Deploy Reliability Analytics 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 following data models to determine which relationship definitions you will need to modify to include your custom equipment and location families:
Via Configuration Manager, modify the relationship definitions as needed.		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 Reliability Analytics Security Groups and Roles.This step is required.
3 Ensure that the Meridium Simulation Service is installed and running.If the basic APM system architecture is already installed, the Meridium Simulation Service is automatically installed and run.
Note: Reliability Simulation service is required to execute the tasks that take a long time. APM Client (browser) will keep polling the APM Server to check the progress of the such tasks and report the progress to the end user in the background.
4 Configure ActiveMQ Settings for the Simulation Service.This step is optional. Default values exist for the concurrency limit, number of retries, number of threads, and the time limit of the Simulation Service. You can change these values as needed.

Configure ActiveMQ Settings for the Simulation Service

Before You Begin

Ensure that the Simulation Service is running. If the basic APM system architecture is already installed, the Simulation Service is automatically installed and run.

About This Task

The Simulation Service processes simulation requests. It is required to execute the tasks that take a long time. APM Client (browser) will keep polling the APM Server to check the progress of the such tasks and report the progress to the end user in the background.

This topic describes how to chance the concurrency limit, number of retries, number of threads, and the time limit of the Simulation Service.

Procedure

  1. On the APM server, access the folder that contains the Simulation Service files. If you have installed APM in the default location, the files are located in C:\Program Files\Meridium\ApplicationServer\SimulationService.
  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 3. You can enter a number between 1 and 3.
    RetriesThe number of times to retry sending messages to ActiveMQ in case of a failure.The default value is 1.
    NumberOfThreadsPerSimulationThe number of threads to run per simulation.The default value is 1.
    TimeLimitInMinutesThe time limit, in minutes, after which the simulation ends.The default value is 240. You can enter a value up to 240.
    "ReliabilitySimulation":{  
   "ConcurrencyLimit": 2,
   "Retries": 10
   "NumberOfThreadsPerSimulation": 1,
    "TimeLimitInMinutes": 240 
}
  4. Save and close the file.
  5. Restart the Simulation Service.
    The Simulation Service is configured.