A tag is the atom of a SCADA system - a single named data point that ties a real-world value, like a wellhead pressure, to everything the software does with it: the display, the alarm, the trend, the report. Build the tag database well and the system is clear and maintainable; build it poorly and nothing else can save it. This guide explains what a tag is, what it carries, and how tags map to field addresses.
SCADA Tag in one line: A SCADA tag is a named data point that represents a single value from the field - such as a pressure, a pump status, or a setpoint - along with its metadata, linking that value to displays, alarms, trends, and historical logging.
A tag is more than a number. Beyond its live value, a tag typically holds a name (a unique identifier like WELL_04_CSG_PSI), a data type (analog float, discrete boolean, integer, string), engineering units and scaling, a source address that tells the system where to read the value, and configuration such as alarm limits, deadband, quality/status, and timestamp. Some tags are read from the field; others are writable, like a remote setpoint or a start command; some are calculated inside the SCADA itself.
This metadata is what lets one field value power many features at once. The same casing-pressure tag drives the number on the operator display, the red high-pressure alarm, the pressure trend, and the value stored in the historian - all from a single point of truth.
Because a large operation can have tens or hundreds of thousands of tags, a consistent naming convention is essential. Good tag names encode location and meaning in a predictable structure - site, equipment, measurement, and often instrument type - so an engineer can read a name like PAD12_SEP1_LVL and know exactly what it is. Many operators base their scheme on ISA-style identifiers. Sloppy, ad-hoc names are one of the most expensive mistakes in a SCADA build because they make every later task harder.
Each tag that reads from the field is mapped to a specific address in a controller: a Modbus register, a DNP3 point index, an OPC UA node, an EtherNet/IP or S7 address. The SCADA driver polls that address and updates the tag. In practice, commissioning a site is largely the work of building this tag-to-address map correctly. Merobix models field values as tags and reads them from controllers over Modbus, DNP3, OPC UA, and other supported protocols, so every point at a remote site becomes a named, alarmable, historized tag in the cloud.
The terms are largely interchangeable. Point tends to refer to the raw field value and its address, while tag refers to the named, configured object in the SCADA database that wraps that value with units, alarm limits, and history.
A large operation can have hundreds of thousands of tags. A consistent naming convention that encodes site, equipment, and measurement lets engineers read a name and instantly know what it is, which makes displays, alarms, and troubleshooting far easier to build and maintain.
Each field-read tag maps to a specific address in a controller - a Modbus register, DNP3 point, OPC UA node, or similar. The SCADA driver polls that address and updates the tag's value, quality, and timestamp.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.