Smart Commissioning Glossary

Allocated device: A device placeholder that is associated with a particular CHARM or wireless I/O card (WIOC). In I/O Studio, device and associated CHARM properties are consolidated. For HART devices, the device placeholder includes HART properties as well as settings for automatic loop tests.

Auto-Commissioning Policies

The collection of DeltaV objects that define the manner in which DeltaV Device Commissioner creates the devices or device placeholders in the system. The policies contain the rules for how to commission, how to resolve conflicts, whether to download as part of commissioning, and so on. Smart Commissioning policies are created and defined in I/O Studio.

Automated Loop Test Template

A DeltaV object created by the user in I/O Studio to standardize the automated loop test performed when using DeltaV Device Commissioner when commissioning devices. The loop test checks the basic response for a single device.

Device Signal Tag Generation Policy

A policy that determines how the system generates DSTs when a HART device is auto-sensed. This policy is defined and enabled in DeltaV Explorer.

The policy defines the source of the tag and enables you to further process the tag name if desired.

For wired devices, if the Device Signal Tag generation policy is not enabled, the system uses the device's HART tag (the short tag) as the DST when the device is auto-sensed. If there is no tag, the system generates a DST based on the wired location of the device. For wireless devices, if the Device Signal Tag generation policy is not enabled, the system uses the HART long tag as the DST when the device is auto-sensed.

Device Master

A DeltaV object created by the user to define and standardize certain device properties to facilitate the creation of identical devices using the DeltaV Device Commissioner. Masters can also be used to create multiple unallocated device placeholders directly in I/O Studio. Device masters are created and defined in I/O Studio.

Device placeholder

A DeltaV object that allows configuration of supported devices independent of a parent I/O Node or I/O Channel. DeltaV software enables you to define HART, wireless HART and conventional field devices for your DeltaV system before you define the system's physical I/O. You don't need to define I/O nodes (such as CIOCs, CSLSs and WIOCs) or CHARMs before you define the devices. You create HART and wireless HART placeholders in I/O Studio. When you create a new device placeholder in I/O Studio, it is unallocated. An unallocated device is one that is not associated with a CHARM or WIOC.

HART Device Template

A DeltaV object created by the user to define and standardize the configuration of HART Device Placeholders or HART device masters. HART device templates are created and defined in both DeltaV Explorer (under Library → Device Templates) and in I/O Studio.

I/O Interface Configuration Template

A DeltaV object created by the user to define and standardize the configuration of I/O interface properties of device placeholders or device masters. I/O Interface Configuration templates are created and defined in I/O Studio.

SIS Device Master

A DeltaV object created by the user to define and standardize certain SIS device properties to facilitate the creation of identical SIS devices using the DeltaV Device Commissioner. SIS device masters are created and defined in I/O Studio.

SIS I/O Interface Configuration Template

A DeltaV object created by the user to define and standardize the configuration of I/O interface properties of SIS device placeholders or SIS device masters. SIS I/O Interface Configuration templates are created and defined in I/O Studio.

Unallocated device

A device placeholder that is not associated with a particular CHARM or Wireless I/O Card (WIOC). Unallocated devices enable you to configure both device and CHARM properties without knowing where the I/O will be located. You can allocate an unallocated device in DeltaV Explorer, I/O Studio, or the DeltaV Device Commissioner (DDC automatically allocates devices during binding). When an unallocated device is allocated (and also when an allocated device is unallocated), all device properties are preserved.

Unassigned I/O reference

A device signal tag (DST) that is referenced in a control strategy but has not been associated with an I/O node or I/O channel.