Define the Device Signal Tag generation policy

When you auto-sense a wired HART device, the system generates a DST. By default, the system uses tag (the short tag) as the DST name. If there is no tag, the system names the DST based on where the device is wired. For wireless devices, by default, the system uses the HART long tag as the DST when the device is auto-sensed.

You can override the default behavior by defining a Device Signal Tag generation policy as described below. The policy defines the source of the tag and enables you to further process the tag name if desired.

Note:

The auto-commissioning policy and the Device Signal Tag (DST) generation policy work together. When configuring the Conflict Management settings for the auto-commissioning policy in I/O Studio, be aware of the source of DSTs and of whether a DST generation policy is defined in DeltaV Explorer.

Lack of coordination between the policies can lead to conflicts. For example, if the DST generation policy uses the HART Long Tag and the auto-commissioning policy defines the field device as the source of DSTs, be sure to select the field device (not the device placeholder) as the source for resolution in the event of a HART Long Tag conflict. Selecting the device placeholder as the source for conflict resolution can result in changing the HART Long Tag in the field device. For this and similar conflicts, I/O Studio detects the conflict and displays a warning.

  1. Navigate to DeltaV System → Setup.
  2. Click Smart Commissioning Policies.
  3. In the right pane, click Device Signal Tag Generation Policy then right-click, Properties.
    The software displays the Device Signal Tag Generation Policy Properties dialog.
  4. Select the appropriate check boxes to define and enable a policy for the devices in your system:
    • Enable DeltaV Device Signal Tag Generation for HART 5 and earlier devices
    • Enable DeltaV Device Signal Tag Generation for HART 6 and later devices
    The software displays additional tabs for defining the tag generation policies.
    Note:
    When you enable a tag generation policy, the policy affects device names system-wide. For example, device names can change in DeltaV Explorer and the DeltaV Device Commissioner applications. If the policy specifies new tags based on fixed position extraction or a regular expression, the system applies the tag generation policy as devices are auto-sensed. It also renames decommissioned wireless devices.
  5. Click a HART tab (HART 5 or HART 6 and Later) to define a policy.
  6. Refer to the dialog help for information on the fields.