Thickness Monitoring Upgrade

Upgrade Thickness Monitoring

The following tables outline the steps that you must complete to upgrade this module to the latest version of APM.

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
1Install the GE Devices Service on all of the machines that will connect to devices that will be used with Thickness Monitoring.This step is required only if using any device to collect data that is connected using a serial connection or if using the Olympus Epoch 650 device.

Install the GE Device Service

Before You Begin

You need administrative access to the machine on which you want to install the service.
Important: You must repeat this procedure on every machine to which a datalogger will be connected.

About This Task

For APM to communicate with physical devices connected to your machine, the GE Device Service must be installed.

You can download the installer from KBA 000059233.

What To Do Next

If you want to use an HTTPS connection or a port number other than the default one (2014), configure the GE Device Service.

Configure the GE Device Service

Before You Begin

  • You need administrative access to the machine on which you want to configure the service.
  • Install the GE Device Service.
Important: You must repeat this procedure on every machine to which a datalogger will be connected.

About This Task

In most cases, the default configuration of the GE Device Service will suffice. However, depending on how you access APM and your computer’s port configuration, you may need to change the configuration.
This topic describes how to configure the settings, which is required only if:
  • Your APM connection uses HTTPS.
  • The default port 2014 is not available.
If using HTTP or the default port, changes to the configuration are not required.

Procedure

  1. In Windows Explorer, navigate to C:\Program Files\Meridium\Services.
  2. Using a text editor, open the Meridium.Service.Devices.exe.config file.
  3. In the appSettings section:
    1. If using a port other than 2014, update the entry for UrlPort with a port number that is available on your computer.
    2. If using HTTPS, update the value for BaseURL with https://*.
    3. On line 26, edit the timeout value in milliseconds. By default, the value for this setting is 60000, or 1 minute.
  4. Save your changes, and restart the GE Device Service.
    The GE Device Service configuration settings are updated.

Results

On initial startup, the service will attempt to install an SSL certificate required to communicate with APM when using an HTTPS connection. It will also bind the certificate with the configured port on the machine and add an entry in the hosts file in order to use the meridium.device.local URL. If you change the port number again, restarting the service will remove any current binding to the previous port and recreate a binding to the newly configured port.

Update the Query Parameter Type

After the database upgrade for APM, if the entity key fields are of the type string, you must modify the catalog query parameters to use the correct type by performing the following steps.

Procedure

  1. Access the Query page.
  2. Select Browse.
    The Select a query from the catalog window appears.
  3. Navigate to the folder containing the query that you want to update, and select the link for the query.
    The Results workspace appears.
  4. Select the SQL tab.
    The SQL workspace appears, where you can modify the SQL code.
  5. Modify all the entity key numeric parameters to key.
    For example, (? :n) must be updated to (? :k).
  6. Select Save.
    The modified query is saved.

Revert the Thickness Monitoring Queries to Baseline

This action is required only if you have modified the Thickness Monitoring queries.

About This Task

If you have modified the following Thickness Monitoring queries, perform the following steps to revert the queries to baseline:
  • Assets Near or Past Retirement
  • Assets with TM Tasks
  • Corrosion Distribution
  • Excessive Corrosion
  • Remaining Life Less than 180 Months
  • Thickness Inspections
  • TM Assets
  • TM Assets Requiring a Calculation

Procedure

  1. Access the Catalog page.
  2. Navigate to the Public folder for the query that you want to revert.
    For Thickness Monitoring, the public queries are stored in the following folder:
    Public/Meridium/Modules/Thickness Monitoring/Queries
  3. Select the check box next to the query that you want to revert, and then select .
    The Confirm Delete window appears, asking you to confirm if you want to delete the selected query.
  4. Select OK.
    The selected query is deleted.
  5. Navigate to the Baseline folder for queries.
    For Thickness Monitoring, the baseline queries are stored in the following folder:
    Baseline/Meridium/Modules/Thickness Monitoring/Queries
  6. Select the check box next to the query that you want to revert, and then select .
    The Catalog Folder Browser window appears.
  7. Navigate to the folder containing the public query that you deleted in step 3.
  8. Select OK.
    A success message appears indicating that the selected item has been copied successfully.
  9. Repeat Steps 2-8 for each query that you want to revert to baseline.

Configure Thickness Monitoring 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

  1. 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
  2. Access the appsettings.json file in an application that can be used to modify JSON files (for example, Notepad++).
  3. In the file, locate the following text:
    "Queue_Config": {
    	    "Queues": [
    	      {
    	        "Name": "MI_TM_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.
  4. Update the key values as desired.
  5. Save and close the file.
    The updated settings will be applied when the MIExecution Service is stopped and restarted.