Understanding Tag names

Historian tag names vary according to the type of collector. By default, the tag name is the source address prepended with a string.

It is recommended that tag names use only characters available for folders and file names to avoid the problems (limitations) with some clients and filtering. You can use tag names that contain the characters & and + in the Non-Web Historian Administrator.

iFIXCollector Tagnames

The format of Historian tag names for an iFIX collector generally is
Node.Tag.Field
where
  • Node, by default, is the name of the SCADA node, the data source. This field is configurable, however.
  • Tag is the database tag.
  • Field is the database field.
Examples of typical tag names:
NODE8.WATER-_SWITCH.F_CV 
NODE2.MASH_LEVEL.B_CUALM 
USGBS1.FIC101.F_CV 
USGBS1.FT102.A_LAALM
where

  • NODE8, NODE2, and USGBS1 are the names of the iFIX SCADA nodes.

  • WATER_SWITCH, MASH_LEVEL, FIC101, and FT102 are the names of the database tags.

  • 4F_CV means single floating point, current value.
  • B_CUALM means current alarm status.
  • A_LAALM means analog input, latched alarm.

OPC or Simulation Collector Tagnames

The format of Historian tags for an OPC or Simulation collector is: 
ComputerName.ItemID
where
  • ComputerName, by default, is the name of the machine on which the collector is installed. This field is configurable, however.
  • ItemID is the data point being polled.

Calculation Collector Tagnames

There is no specified format for Historian tags for a Calculation Collector. We recommend that you select a consistent naming convention so the tags are easily and clearly identifiable. You should avoid using spaces and other special characters or reserved words used in SQL or VBScript. This applies to any tag being used as a source tag in the formula.

Server-to-Server Collector Tagnames

There is no specified format for Historian tags for a Server-to-Server Collector. We recommend that you select a consistent naming convention so the tags are easily and clearly identifiable. Server-to-Server Collectors allow you to specify a prefix to add to the Server-to-Server Collector tags.
Note: In cases where you want the destination tag's data to be a duplicate of the source tag, then the tag name would be identical. This is especially important so that all messages and alerts are included.