Risk Based Inspection 580 Deployment

Deploy RBI 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.


Step	Task	Notes
1	Review the RBI 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 needed via Configuration Manager.	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 Security Roles used in RBI.	This step is required.
3	On the APM Server, using Configuration Manager, import the following files 101_MI_STMPCNFG.xml 102_MI_STRMAPP.xml These files are located in the following folder: C:\Meridium\DbUpg\MI_DB_MASTER_4030000\4030000\20_IEU\50_Other\2_RecordsLinks. You must extract the 4030000 archive from the MI_DB_MASTER_4300000 archive.	This step is required only if you are deploying Risk Based Inspection on an existing APM database. These data mapping records are used in RBI 581 and Risk Based Inspection. This will overwrite the existing Strategy Mapping Composite Entities. If you have customized your Strategy Mapping Content, you should instead follow the instructions in KBA 000029119.
4	Assign the following types of RBI users to at least one TM Security Group: Users who are responsible for completing the steps necessary to use TM Analysis values to calculate RBI 580 corrosion rates. Users who should be able to navigate to TM via RBI 580.	This step is required only if you are using the integration between the RBI and Thickness Monitoring modules.
5	Modify the MI_DEGRADATION_MECHANISM_TYPES System Code Table.	This step is required only if you want to create your own Potential Degradation Mechanisms records.
6	Select the Recommendation Creation Enabled check box in the Global Preferences workspace.	This step is required only if you do not want to create Recommendations in RBI, but want to use the Asset Strategy Management (ASM) module to recommend actions and manage mitigated risk. This check box is selected by default.
7	Select the Enable Recommendations to be Generated at Created State check box in the Global Preferences workspace.	This step is required only if you want to create RBI Recommendation records while RBI Analysis records are in the Created state. This check box is cleared by default.
8	Select the Allow Override of Calculated Unmitigated Risk Values check box in the Global Preferences workspace.	This step is required only if you want to override the calculated values of unmitigated risk because you use a custom calculator. This check box is cleared by default.
9	Select the Consider Half-Life when Determining Inspection Task Interval check box in the Global Preferences workspace.	This step is required only if you want additional values such as half-life to determine the inspection task interval. This check box is cleared by default.
10	Select the Is a Unit? check box in Functional Location records that represent units in your facility.	This step is required to mark Functional Location records as Process Units.
11	Using the Belongs to a Unit relationship, link Equipment records to Functional Location records representing units to which that equipment belongs (i.e., the Is a Unit? check box is selected).	This step is optional.
12	Configure the APM system to generate RBI Recommendation records automatically.	This step is optional.
13	Create Potential Degradation Mechanisms records.	This step is required only if you want to use additional Potential Degradation Mechanisms records that are not provided in the baseline APM database.
14	Assign a ranking to all Qualitative Potential Degradation Mechanisms records.	This step is required only if you want the Probability Category field in certain Criticality Degradation Mech Evaluation records to be populated automatically based on this ranking.
15	Configure Risk Based Inspection ActiveMQ settings for MIExecution Service.	This step is optional. You can perform this step if you want to modify the default retries or concurrency settings.
16	Ensure that the Meridium MIExecution Service is installed and running.	If the basic APM system architecture is already installed, the Meridium MIExecution Service is automatically installed, and the service runs automatically.
17	Add RBI Component Types to the MI RBI COMPONENT TYPES system code table.	This step is required only if you want to use additional RBI Component type records that are not provided in the baseline APM database.

Configure Risk Based Inspection ActiveMQ settings for MIExecution Service

The MIExecution Service,on each APM Server serves RBI, Inspection and Thickness Monitoring module queues. This service is configured to use a single shared ActiveMQ queue service across APM. Available queue configuration options include retries and concurrency limit.

Procedure

On the APM Server, access the folder that contains the MIExecution Service files.

Note: If you have installed APM in the default location, you can locate the folder in C:\Program Files\Meridium\ApplicationServer\mi-execution
Access the appsettings.json file in an application that can be used to modify JSON files (for example, Notepad++).
In the file, locate the following text:
```
"Queue_Config": {
	    "Queues": [
	      {
	        "Name": "MI_RBI_Queue", 
	        "ConcurrencyLimit": 100,
	        "Retries": 5,
               "LimitPerTenantRequired": true 
	      }
	    ]
          }
```
Note: ConcurrencyLimit indicates the maximum number of messages that will be consumed concurrently. Retries indicates the number of times it retries to send the messages to ActiveMQ if it fails. LimitPerTenantRequired indicates whether Maximum Concurrency limit per Tenant is specified in scheduler service for the queue.
Update the key values as desired.
Save and close the file.
The updated settings will be applied when the MIExecution Service is stopped and restarted.

Add RBI Component Types

Procedure

Log in to APM as an administrator.
Go to Admin > Configuration Manager > System Codes and Tables.
Search for MI RBI COMPONENT TYPES.
In the System Code section, select .
The Create System Code window appears.
Add the RBI Component Types to the system code table.
Select Save.
Log out of APM and log in.
To add existing RBI Component Types to the MI RBI COMPONENT TYPES system code table, perform the following steps:
1. Select , and enter EquipmentTypes.
  A blank EquipmentTypes datasheet appears.
2. In the CriticalityItemType box, select the existing RBI Component Type that you have added.
3. Enter values in the required boxes, and then select to save the record.