Upgrade

Upgrade from PDI to OT Connect

About This Task

The initial release of OT Connect is in APM Version 4.4.0. Although OT Connect is a new module, there are a number of customers who were using the Process Data Integration module in an older version of APM. As these customers upgrade to APM Version 4.4.0, they will want to upgrade their existing OPC Tags and any Health Indicators or Policies that utilize those tags.

OT Connect includes the OT Connect Upgrade Utility, a console application that can be used to migrate content that previously relied upon Process Data Integration.

During the database upgrade to APM Version 4.4.0, the content of the OPC Systems will be migrated to OT Sources, and OPC Tags will be migrated to Source Tags, if they are in use by Health Indicators or Policy Instances. After the database upgrade, and before using Health, Policy or OT Connect, you must run this utility. This utility performs the following:

  1. Updates the OT Source Ids
  2. Updates the Source Tag Ids
  3. Creates Content Map records for every Health Indicator that is linked to an OPC Tag and upgrades those Health Indicators
  4. Upgrades Policies that use the OPC Tag node to use the OT Connect Tag node
  5. Creates Content Map records for all Policy Instances that reference OPC Tags in OPC Tag nodes and upgrades those Policy Instances.
Note:
  • Policies that use obsolete fields from the OPC Tag node will be upgraded automatically, however these Policies may no longer function as expected and will be deactivated. You can open such upgraded Policies in Policy Designer to review the obsolete field usage and reconfigure the Policies.
  • Policies that reference OPC Tag records in Entity nodes or Policy Instances that reference OPC Tag records in Point Value nodes are NOT upgraded automatically.
  • The upgrade process identifies any Policies and Policy Instances that cannot be upgraded automatically and adds a warning to the log. Please contact GE Vernova Support for advice on modifying any such Policies or Policy Instances to work with the OT Connect module.

Results

StepTaskNotes
1In APM, ensure that your new APM OT Connect license has been applied.This step is required.

Apply and verify licenses in Operations Manager > Activate Licenses.

Note: Your new license must show that APM OT Connect is ACTIVE. And if upgrading from PDI, the OPC Interfaces must also show as ACTIVE.
2On the APM Server, invoke the OTConnectUpgradeUtility.exe executable from the Windows Command Prompt.

This step is required.

Locate the OTConnectUpgradeUtility.exe in C:\Program Files\Meridium\OTConnect\Upgrade.

Execute the following command, replacing <datasource_id> with the name of the APM Datasource that you wish to connect to and upgrade. Please note that there is a space after datasource.

.\OTConnectUpgradeUtility.exe datasource: <datasource_id>
3On the APM Server, review the upgrade log and ensure that no errors were logged during the upgrade process.

This step is required.

Locate OTConnectUpgradeUtility_APM_<date>.log in C:\ProgramData\Meridium\Logs.

You may also need to look into the following two log entries:

Upgrading 312 Health Indicators.

312 Health Indicators were upgraded.

If those two numbers do not match in your log, then some errors have occurred that have prevented the upgrade utility from successfully completing all of the required tasks.

Note: After resolving any issues reported in the log, re-run the Utility.

Warnings will be added to the log in the following circumstances:

  • A Policy uses an obsolete field in an OPC Tag node. The policy will be inactivated.
  • A Policy uses an Entity node configured to reference the OPC Tag family. The policy will be inactivated.
  • A Policy Instance references an OPC Tag record in a Point Value node.
  • A Policy Instance references a record (not limited to OPC Tag records) which is not found in the APM Database. Usually this means that the referenced record was deleted after the Policy Instance was last saved. The invalid reference will be removed.

You may need to redesign the Policy or reconfigure the Policy Instance to work with the OT Connect module, after the upgrade is completed. Consult GE Vernova Support for advice.

4Migrate additional datasources.Repeat steps 2 and 3 for each datasource that you want to migrate.
5Once the log has been reviewed and no errors have occurred, the Upgrade is complete.You are now ready to Deploy OT Connect for the First Time.