Load

Loading items does not impact a commissioned PK controller. However, this step will affect your DeltaV balance-of-plant configuration.

Similar to a spreadsheet, you can filter information on this page based on the data in any column with a filter drop down list. Clear all filters by clicking the clear filter button in the top right of the columnar view. You can sort the data by clicking the column heading.

Merging into the DeltaV balance-of-plant system requires that you have the appropriated keys for the affected areas or nodes. For example, you will need the Can Configure key site-wide for all non-SIS modules across all DeltaV areas and the SIS Can Configure site-wide for all SIS modules across all DeltaV areas.

Note

The regional settings of your balance-of-plant DeltaV system must match the settings of the project you are merging or the merge will fail.

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.

If merging operator displays, you cannot have Version Control (VCAT) for Displays in the DeltaV system enabled. Either disable VCAT for Displays or do not merge any displays from the Standalone DeltaV PK controller's project.

Decommission and unassign all CSLS logic solvers and decommission SLS1508 logic solvers configured in the standalone system prior to starting the merge sequence. Failure to do so results in the orphaning of these objects in the balance-of-plant DeltaV system.

Simulated Logic Solvers cannot be retrieved from another project and cannot be merged into a balance-of-plant DeltaV system.

Custom (user-created) alarm priorities do not merge into the balance-of-plant DeltaV system. Either create the custom alarm priorities in the balance-of-plant DeltaV system, or change the standalone system to use an alarm priorities that also exist in the balance-of-plant DeltaV system.

Columnar View: Lists the item's Name (if revised, it is the revised name), Item Type, Load Action value.; To change the list of items being merged, click Back and select or deselect the item on the Select Items to Load page.
Load into DeltaV button: Merges the items listed into the DeltaV balance-of-plant system. This process is not reversible.; A confirmation dialog displays. If any items will overwrite a DeltaV database object, a warning dialog is displayed.; Click the Load button on the confirmation (or warning) dialog to load the items as they are. Click Cancel and Back to change anything about the list.
Load Progress: Shows the progress of the merge.
Load Log Location: Displays the path to the log file created by the merge process.
Rename File Location: Displays the location of the file with the list of items you renamed. Use this list when updating your merged operator displays. Operator displays are part of the merge process.

When the loading completes, you can open DeltaV Explorer and see the merged configuration.

Tip

You may need to refresh DeltaV Explorer (press F5) to see recent changes.