| 1 |
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:
SELECT Count( [MI_REPFLUID].[MI_REPFLUID_FLUID_C]) "Fluid" FROM [MI_REPFLUID]
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.
|
| 2 |
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:
SELECT Count( [MI_CMT_FLE0].[MI_CMT_FLE0_FLUID_C]) "Fluid" FROM [MI_CMT_FLE0]
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.
|
| 3 |
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:
SELECT Count( [MI_FLD_VSCY].[MI_FLD_VSCY_FLUID_C]) "Fluid" FROM [MI_FLD_VSCY]
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.
|
| 4 |
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:
SELECT Count( [MI_PRL_CNS0].[MI_PRL_CNS0_FLUID_C]) "Fluid" FROM [MI_PRL_CNS0]
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.
|
| 5 |
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:
- 06_MI_DATA_GRP.xml
- 07_MI_MPPG_QRY.xml
- 08_MI_CLMND_PR.xml
|
This step is required only if you have not performed it during a previous upgrade. This will create data mappings between families in RBI 581.
IMPORTANT: After you complete this step, all existing changes to data mapping in the RBI 581and Risk Based Inspection modules 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.
|
| 6 |
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:
- 101_MI_STMPCNFG.xml
- 102_MI_STRMAPP.xml
|
This step is required. This will update the RBI Strategy Mapping Composite entities, overwriting the existing ones.
|
| 7 |
Add the RBI-581 tab to the datasheet of the following families:
- 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
|
This step is required only for families for which you have customized the datasheet and if you have not performed it during a previous upgrade. |
| 8 |
Review and complete the steps required for deploying R Scripts.
|
This step is required. This will install R-Script and other third-party software that is used by the RBI 581 module. |
| 9 |
Using the Query tool, run the following query:
UPDATE [MI_RMMPG]
SET [MI_RMMPG].[MI_RMMPG_SOURCE_FLD_C] = 'MI_RBDEMECH_TOTAL_PF_RBI_DTE_N'
WHERE [MI_RMMPG].[MI_RMMPG_SOURCE_FLD_C] = 'MI_RBDEMECH_POF_N'
|
This step is required. This will update the RBI Risk Matrix Mapping records such that Total POF - RBI Date value is used to plot probability of failure (POF) on the risk matrix, instead of the Total POF With Plan value.
IMPORTANT: After you complete this step, any customization done on the POF data mapping 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 query.
|
| 10 |
On the GE Digital APM Server, reset IIS. |
This step is required, and has to be performed after you complete all the aforementioned steps. |
