Calibration Management Upgrade
Upgrade or Update Calibration Management to V5.0.6.0.0
Upgrading or updating to the V5.0.6.0.0 is a two-step process. You need to first upgrade to APM V4.6.2.0.0 or later and then follow the steps to upgrade or update to V5.0.6.0.0.
The following table provides you the reference to procedures to upgrade from an earlier APM version to the latest version.
Upgrade from | Upgrade to | Procedure |
---|---|---|
V5.0.0.0.0 through V5.0.5.0.0 | V5.0.6.0.0 | Upgrade from any version V5.0.0.0.0 through V5.0.5.0.0 |
V4.6.2.0.0 through V4.6.10.0.0 | V5.0.6.0.0 | Upgrade from any version V4.6.2.0.0 through V4.6.10.0.0 |
Upgrade from any version V5.0.0.0.0 through V5.0.5.0.0
This module will be upgraded to V5.0.6.0.0 automatically when you upgrade the components in the basic APM system architecture. No additional steps are required.
Upgrade from any version V4.6.2.0.0 through V4.6.10.0.0
The following tables outline the steps that you must complete to upgrade this module to V5.0.6.0.0. These instructions assume that you have completed the steps for upgrading the basic APM 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.
- The Calibration Strategy and Device Type fields in each Calibration Profile are populated automatically.
- If using a GE Druck calibrator, in a Calibration Template that was created before the upgrade, if the value in the Temperature Element Type field is None, you must modify the value. Otherwise, you will not be able to link the Calibration Template to an Asset.
Step | Task | Notes |
---|---|---|
1 | Update entity key parameters from :n to :k for the following catalog queries:
| This step is required only if you have previously modified the queries. This step will be completed automatically when you upgrade the components in the basic APM system architecture. |
2 | Update Asset Hierarchy parameter from -1 to #ahhome for the following catalog queries: For example, (? :ah :id=entity_key) = '-1'must be updated to (? :ah :id=entity_key) = (#:ahhome)
| This step is required only if you have previously modified the queries. This step will be completed automatically when you upgrade the components in the basic APM system architecture. |
3 | Following queries have been modified to improve the performance. Revert these queries to Baseline to avoid any issues while using Postgres Database.
| This step is required only if you have previously modified the queries. |
Install the Meridium Device Service
About This Task
The Meridium Device Service can be installed as part of the workflow when you try to send data to calibrator or verify the settings of the calibrator.
Procedure
Update the Query Parameter Type
About This Task
After the database for APM is upgraded, 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
Revert the Calibration Management Queries to Baseline
This action is required only if you have modified the Calibration Management queries.