In this step of the process, you can rename any item listed. These items exist in the project backup file and were compared with your DeltaV balance-of-plant system. Conflicts are noted and should be corrected.
Renaming items before merging does not impact a commissioned PK controller.
Similar to a spreadsheet, you can filter information on this page based on the data in any column with a filter drop down list. Unselected or hidden (filtered) items are not modified. You can sort the data by clicking the column heading.
Clear all filters by clicking the clear filter button in the top right of the columnar view.
Warning icons are displayed next to the Revised Name. Hover over the icon to see the details of the warning.
The new name must adhere to DeltaV naming conventions.
Items in protected categories cannot be renamed. You can enter a new name on the Rename page, but the application will not apply the new name.
If you are renaming items and you have Version Control (VCAT) enabled, you must close all DeltaV database clients prior to renaming any items or the merge will not complete successfully. Use DeltaV Database Administration's Database Connections applet to see the active database connections. The PK Merge utility remains open.
If renaming a fieldbus device placeholder that will be merged with the balance-of-plant DeltaV system, you must decommission it first, then rename it, and then select it for loading.
If renaming a controller as part of the merge process, any fieldbus devices belonging to that renamed controller must be loaded at the same time as the controller (that is, both are selected to load on the Select page and are shown on the Load page).
Modules that use alarm types derived from the PCSD library and where those alarm type names also exist in the balance-of-plant DeltaV system always show a merge conflict (due to the alarm names). The alarm types cannot be renamed in the PK's project as they are system alarm types (and therefore read-only names). To successfully import these modules, do not select them for merging. Instead, export the modules with the conflicting alarm types and import those modules before the decommission (final step) in the Merge process.