Overview

Within the AVEVA Batch Management environment, tags are used to interconnect with the batch control program. Each tag has a unique name and is associated with a specific class of data. You create tags during AVEVA Batch Management application development.

For AVEVA Batch Management applications to communicate with other applications and control systems, you must properly configure all the required tags. Communication between AVEVA Batch Management and other applications is accomplished using SuiteLink. AVEVA Batch Management can also integrate to an ArchestrA environment using the Message Exchange (MX) protocol.

Note: It is required that only SuiteLink I/O Servers be used with AVEVA Batch Management. SuiteLink provides the robust and reliable communications protocol that AVEVA Batch Management demands.

Use Tag Linker to select, edit, and then export AVEVA Batch Management tags to a comma separated variable (.csv) file. The .csv file contains InTouch-compliant tagnames, including access names. You can then import the tags in the .csv file into the InTouch application using the InTouch DBLoad utility.

For more information on browsing and referencing remote AVEVA Batch Management tags from InTouch, see InTouch Batch Tag Browsing and Referencing.

Tag Linker is associated with two categories of AVEVA Batch Management tags; process model tags and AVEVA Batch Management function tags.

Process model tags are all the unit, connection, and segment tags that are generated when you develop the process model. These are the only tags that are shown and can be edited by the Tag Linker. Process model tags are divided into two types: system tags and equipment tags.

• System tags are associated with units, connections, and segments and are generated by AVEVA Batch Management as the units, connections, and segments are created in the model. System tags are not associated with phases and are therefore distinguished by a triple-dot in the tagname.

  Most of these tags are string tags. Although the Access of these tags can be changed, we strongly recommend that these tags be left as AVEVA Batch Management memory tags. Adverse performance can occur if these tags are written to by anything but AVEVA Batch Management. The exception to this rule is the equipment status tag (Unit...USTAT or Segment...USTAT).

• Equipment tags are associated with a specific phase or phase parameter and are generated when a phase is created. These tags are generally owned by an I/O Server, InTouch, or another server application; however, they can be defined as AVEVA Batch Management memory tags for simulation purposes.

  Note: Your work is dynamically saved in the configuration link database as you edit and make changes to the linker configuration.