Tags are points of data and may have static values or dynamic values that come from an OPC address, an expression, or a SQL query. The values can be used on screens, in transaction groups, and more.
There are two types of tags; internal and external tags. By default, a fresh Ignition installation will have an internal tag provider - this can be thought of as a standard internal tag database, and stored in the Ignition Gateway. Additionally, it is possible to create external Database-based tag providers, thus turning your SQL database into the tag database, and stored in Tag Providers. This ability opens up some very flexible architectures.
Despite their low initial learning curve, however, Tags offer a great amount of power in system design and configuration. The ability to aggregate tags from a variety of installations in a central SQL database means that you can build widely distributed SCADA systems more easily than ever before, with a high level of performance and relatively easy configuration. Tag User Defined Types (UDTs) provide an object-oriented approach to tag building, allowing you to define parameterized data types, extend and override types, and then rapidly generate instances. A change to the type definition is then inherited by all instances, drastically saving time when making routine changes. The UDT data types are fully supported by Vision templates, which means you can configure templates for your custom data types and take advantage of drag-and-drop binding to rapidly build complex screens.
To learn more about tags, refer to the section on Understanding Tags.
A lot of time you will hear people refer to tags in a PLC as "Tags" as well as tags in Ignition as "Tags." It gets a little confusing sometimes but in this manual if you see "Tags" by itself, we are talking about Tags inside Ignition. Any mentions of tags from a PLC or another OPC Server will be called "PLC Tags" or "OPC Tags."