Risk Based Inspection 581 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. GE Vernova recommends, however, that the tasks be completed in the order in which they are listed.
Step | Task | Notes |
---|---|---|
1 | Review and complete the steps required for deploying R Scripts. | This step is required. This will install R Scripts and other third-party software that is used by the RBI 581 module. |
2 | Review the RBI data model 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. |
3 | Assign Security Users to one or more of the Security Roles used in RBI. | This step is required. |
4 | Add the following types of RBI 581 users to at least one TM Security Group:
| This step is required only if you are using the integration between the RBI 581 and Thickness Monitoring modules |
5 | Select the Is a Unit? check box in Functional Location records that represent units in your facility. | This step is required, and marks Functional Location records as Process Units. |
6 | 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. |
7 | Add the RBI-581 tab to the datasheet of the following families:
| This step is required only for families for which you have customized the datasheet. |
8 | Using Configuration Management, import the following files located in the C:\Meridium\DbUpg\MI_DB_MASTER_4030000\4030000\20_IEU\50_Other\2_RecordsLinks folder:
| This step is required only if you are deploying RBI 581 on an existing database. This will create data mappings between families in RBI 581. Important: These data mapping records are used in RBI 581 and Risk Based Inspection. After you complete this step, all existing changes to data mapping in the RBI 581 and Risk Based Inspection will be reverted to baseline. All customization for data mappings will be lost. Do not perform this step unless your organization will be satisfied with the baseline data mappings, or you are prepared to customize the records again following the execution of the script. |
9 | Using Configuration Manager, import the following files located in the C:\Meridium\DbUpg\MI_DB_MASTER_4030000\4030000\20_IEU\50_Other\2_RecordsLinks folder:
| This step is required. This will update the RBI Strategy Mapping Composite entities, overwriting the existing ones. |
10 | Update Risk Matrix Mappings and Policies to account for overridden financial consequence for RBI 581 Risk Analyses. | The Operations Category on the Risk Matrix does not account for overridden financial consequence for RBI 581 Risk Analyses. If you are using this feature, you are required to update your Risk Matrix Mappings and Policies by following Article 000035710. |
11 | Using Configuration Manager, import the MI_REPFLUID_581.xml file located in the C:\Meridium\DbUpg\MI_DB_MASTER_4030000\4030000\_IEU_ManualImports folder. | This step is required to import the Representative Fluids that are used in RBI 581. If you want to use only RBI 581 (i.e., you do not want to use RBI 580), you must delete the existing content, and then import this file. This will remove all the information related to the RBI 580 representative fluids. If you want to verify that the file has been imported successfully, run the following query:
This will return a list of 30 records. If you want to use both RBI 580 and RBI 581, import these files without deleting the existing content. In this case, the aforementioned query returns a list of 111 records. |
12 | Using Configuration Manager, import the MI_CMT_FLE0.xml file located in the C:\Meridium\DbUpg\MI_DB_MASTER_4030000\4030000\_IEU_ManualImports folder. | This step is required to import the Component Damage Flammable records. If you want to use only RBI 581 (i.e., you do not want to use RBI 580), you must delete the existing content, and then import this file. This will remove all the information related to the RBI 580 Component Damage Flammable records. This will ensure that the content in this table is as per API 3rd Edition table 4.8. If you want to verify that the file has been imported successfully, run the following query:
This will return a list of 64 records. If you want to use both RBI 580 and RBI 581, import these files without deleting the existing content. |
13 | 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. |
14 | Using Configuration Manager, import the MI_FLD_VSCY_581.xml file located in the C:\Meridium\DbUpg\MI_DB_MASTER_4030000\4030000\_IEU_ManualImports folder. | This step is required to import the Fluid Viscosity records. If you want to use only RBI 581 (i.e., you do not want to use RBI 580), you must delete the existing content, and then import this file. This will remove all the information related to the RBI 580 Fluid Viscosity tables. This will ensure that the content in this table is as per API 3rd Edition table 6.1. If you want to verify that the file has been imported successfully, run the following query:
This will return a list of 5 records. If you want to use both RBI 580 and RBI 581, import these files without deleting the existing content. In this case, the aforementioned query returns a list of 10 records. |
15 | Using Configuration Manager, import the MI_PRL_CNS0.xml file located in the C:\Meridium\DbUpg\MI_DB_MASTER_4030000\4030000\_IEU_ManualImports folder. | This step is required to import the Personal Injury Flammable CE Constants records. If you want to use only RBI 581 (i.e., you do not want to use RBI 580), you must delete the existing content, and then import this file. This will remove all the information related to the RBI 580 Fluid Viscosity records. This will ensure that the content in this table is as per API 3rd Edition table 4.9. If you want to verify that the file has been imported successfully, run the following query:
This will return a list of 62 records. If you want to use both RBI 580 and RBI 581, import these files without deleting the existing content. In this case, the aforementioned query returns a list of 62 records. |
16 | On the APM Server, restart Redis. | This step is required, and has to be performed after you complete all the previous steps. |
17 | On the APM Server, reset IIS. | This step is required, and has to be performed after you complete all the previous steps. |
18 | 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. |
19 | 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. |
Add the RBI-581 Tab to Criticality RBI Component Datasheets
Before You Begin
If you have customized the datasheet for one or more of the Criticality RBI Components, after activating the RBI 581 license, you must perform the following procedure to add the RBI-581 section to those customized datasheets. The following table indicates the fields that must appear on each datasheet.
Caption | Field ID | Criticality RBI Component - Cylindrical Shell | Criticality RBI Component - Exchanger Bundle | Criticality RBI Component - Exchanger Header | Criticality RBI Component - Exchanger Tube | Criticality RBI Component - Piping | Criticality RBI Component - Tank Bottom |
---|---|---|---|---|---|---|---|
Base Material | Base MaterialMI_CCRBICOM_BASE_MATER_C | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Cladding Material | MI_CCRBICOM_CLADDING_MATERIL_C | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Cladding Present | MI_CCRBICOM_CLADDING_PRESENT_L | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
CM Corrosion Rate | MI_CCRBICOM_CM_COR_RT_C | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Coefficient Y Material | MI_CCRBICOM_COEFFICNT_Y_MTRL_C | ✕ | ✕ | ✕ | ✕ | ✓ | ✕ |
Corrosion Allow | MI_RBICOMPO_CORRO_ALLOW_N | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Detection System | MI_CCRBICOM_DETECTION_SYSTEM_C | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Fluid Velocity | MI_CCRBICOM_FLUID_VELOCITY_N | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Furnished Cladding Thk | MI_CCRBICOM_FRNSHD_CLDDG_THK_N | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Geometry Type | MI_CCRBICOM_GEOMETRY_TYPE_C | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
GFF Component Type | MI_CCRBICOM_GFF_COMPO_TYPE_CHR | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Has Release Prevention Barrier? | MI_CCRBICTB_HAS_RELEA_PREVE_F | ✕ | ✕ | ✕ | ✕ | ✕ | ✓ |
Is Intrusive? | MI_RBICOMPO_IS_INTRU_CHR | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Isolation System | MI_CCRBICOM_ISOLA_SYSTE_CHR | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Liner Present | MI_CCRBICOM_LINER_PRESE_CHR | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Liner Type | MI_CCRBICOM_LINER_TP_C | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Minimum Structural Thickness | MI_CCRBICOM_MNMM_STRCTRL_THS_N | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Mitigation System | MI_CCRBICOM_MITIGATION_SYSTM_C | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Percent Liquid Volume | MI_RBICOMPO_PER_LIQ_VOL_N | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
pH of Water | MI_CCRBICOM_PH_OF_WATER_N | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Specified Tmin | MI_CCRBICOM_SPECIFIED_TMIN_N | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Total Acid Number | MI_CCRBICOM_TOTAL_ACID_NUMBR_N | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Procedure
Add RBI Component Types
Procedure
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.