Conflict management for Auto-Commissioning Policies

Auto-Commissioning Policies determine how DeltaV Device Commissioner resolves conflicts that it encounters during the commissioning process.

For each of the following types of conflict, you can select one of the listed methods of resolution:

• What do you want DeltaV Device Commissioner to do if the Manufacturer, Model, and Revision of the HART device do not match the configured Manufacturer, Model, and Revision of the device placeholder?
  • If the Manufacturer, Model, and Revision of the device placeholder are undefined, update the device placeholder to match the sensed field device. Otherwise, move the device to the Punch List for manual resolution of the conflict.
  • Move the device to the Punch List for manual resolution of the conflict.
• If the device placeholder and the sensed field device have conflicting supplementary information, which source do you want DeltaV Device Commissioner to use?
  Note

  If a Device Signal Tag generation policy is defined in DeltaV Explorer, it is important to select a source for conflict resolution that does not conflict with that policy. Otherwise, DeltaV Device Commissioner could, for example, improperly overwrite correct supplementary information on a field device.

  • For HART Description?
    • Device placeholder
    • Field device
  • For HART Long Tag?
    • Device placeholder
    • Field device
• Auto-Commissioning Policy specifies that DSTs come from field devices--What do you want DeltaV Device Commissioner to do if it does not find a matching unallocated device placeholder for a sensed field device that is referenced by a control module?
  • Automatically create a device placeholder using a default device master for the sensed field device.
  • Automatically create a device placeholder using system default values.
  • Move the device to the Punch List for manual resolution of the conflict.
• Auto-Commissioning Policy specifies that DSTs come from field devices--What do you want DeltaV Device Commissioner to do if a non-matching device placeholder is already allocated to a CHARM to which a matching device placeholder is supposed to be allocated?
  • Unallocate the non-matching device placeholder and allocate the matching device placeholder to the CHARM.
  • Move the device to the Punch List for manual resolution of the conflict.
• Auto-Commissioning Policy specifies that DSTs come from CHARMs--What do you want DeltaV Device Commissioner to do if a device placeholder allocated to a CHARM does not match the tag coming from the field device?
  • Rename the tag in the field device to match the name of the device placeholder.
  • Do not rename either the device placeholder or the field device.
  • Move the device to the Punch List for manual resolution of the conflict.
• Auto-Commissioning Policy specifies that both CHARMs and field devices are configured with matching DSTs--What do you want DeltaV Device Commissioner to do if the device placeholder allocated to a CHARM does not match the tag coming from the field device?
  • Do not rename either the device placeholder or the field device.
  • Move the device to the Punch List for manual resolution of the conflict.