Tag Placement

There are a number of use cases where you may require information on the condition of devices in the field other than device state, but where the use of alarms is either not appropriate, or the condition will persist long after the alarm clears. One such example is the lockout trip state of pumps.

The Tag Placement application monitors status and multistate input points, and places flex tags on the associated outpoint points based on triggering conditions to the input. When a said point enters the trigger state, the system places the indicated flex tag type on its associated outpoint point to act as the required indicator.

The application may automatically place multiple flex tags at a time on the output point if multiple triggers match their trigger state. The icon that appears on the summary display will correspond to one of the following:

• The trigger configured with the highest priority Flexible Tag Type on the Input Triggers tab of the fieldDrivenCondition Row Edit dialog box, or

• The most recently activated trigger in the case where two triggers have been configured with the same priority.

The flex tags created may prevent Controller or programmatic (that is, Application Calculation Engine [ACE]) commands to the record depending upon the configured Flexible Tag Type for the trigger. For example, if a point is attributed with a field-driven condition such as "local override", "remote lockout", or similar, there is nothing preventing you from issuing a command. In such a case, the flex tag could merely be an informational tag.

Notes: In order to make use of this application, an Administrator must configure the system to use flex tags, not tags.

Standard tag maintenance rules apply to any tags placed by the application. Controllers with sufficient permission can add tags to, or delete tags from, a specific point, and the application will not replace or restore the tags until the system reevaluates the trigger condition.