What Is a Tag Detail Display?

Back to Blog

What the Tag Detail Display Shows

A tag detail display drills into a single point. It shows the live value in engineering units and the raw signal behind it, the instrument range (for example 0-150 psig), and every alarm setpoint configured on the tag - high, high-high, low, low-low - with each one's current state. It reports data quality: whether the value is good, stale, or bad because communication to the field device has failed, and when the tag last updated. It typically also carries the tag's description, its scan or update rate, and a small trend of recent behavior.

For a calculated or control point, the display extends to show mode, setpoint, output, and tuning where relevant. The common thread is completeness: everything the system knows about that one tag is gathered in one place, which is exactly what someone needs when they are trying to decide whether a reading can be trusted.

How Operators and Engineers Use It

The tag detail display is a diagnostic tool. When a value on the mimic looks wrong - a flow reading pinned at zero, a pressure that has not moved in an hour - the operator opens the tag detail to investigate. There they can see whether the data quality is bad (pointing to a communication or instrument fault), whether the value is simply stale, or whether the tag is fine and the process really is doing that. Bad quality on the tag detail immediately redirects the investigation from process to instrumentation.

Engineers use the same display to verify configuration. Are the alarm limits set correctly? Is the range scaled to match the transmitter? Is the scan rate appropriate for how fast the variable moves? Because misconfigured limits and scaling are common causes of nuisance alarms and misleading readings, the tag detail display is where those settings are checked and corrected. In oil and gas SCADA, with thousands of tags across a field, the tag detail display is the standard way to confirm that any single measurement - a wellhead pressure, a tank level, a meter's flow - is configured right and reading true.

A Methodical Way to Read One

The tag detail display rewards a fixed reading order. Engineers who jump straight to the alarm limits or the trend often miss the one field that would have answered the question in seconds. The discipline is to rule out the cheap explanations first - quality, staleness, scaling - before concluding anything about the process, because a wrong number on a healthy process wastes far more time than a right number on a misbehaving one.

A practical order of checks when a reading looks suspect:

1. Data quality first. Bad or uncertain quality ends the process investigation immediately and redirects it to the instrument or the communication path.
2. Timestamp of the last update. A good-quality value that has not updated in far longer than the scan rate is stale, whatever the quality flag says.
3. Raw value against scaled value. If the raw counts are moving but the engineering value is frozen or absurd, the scaling is wrong, not the process.
4. Range against the transmitter. A value pinned exactly at the top or bottom of the configured range usually means the signal is out of range, not that the process is sitting there.
5. Alarm limits against the philosophy. Confirm the limits match what rationalization decided, not what someone typed years ago.
6. The embedded trend last, for context. Only once the tag itself is proven healthy does the shape of the trend say anything about the process.

Working the list top to bottom takes under a minute and prevents the classic mistake of troubleshooting a separator for an hour when the real fault was a dead transmitter loop.

Configuration Fields Worth Auditing

Beyond live diagnosis, the tag detail display is the natural place to audit configuration drift. The fields that go wrong most often are the quiet ones: the raw-to-engineering conversion after a transmitter was re-ranged in the field but not in SCADA, units that read psig on the screen while the device reports kPa, and deadbands copied from a template that never fit this signal. Each of these produces a number that looks plausible and is wrong, which is the most dangerous kind of error. The walkthrough on setting up engineering unit scaling for a tag covers what correct looks like.

Scan rate deserves the same scrutiny: a fast-moving pressure sampled slowly looks steadier than it is, while a slow tank level scanned aggressively wastes bandwidth for nothing, a trade covered in the guide on setting scan rates. When an audit turns up several tags with the same class of defect, treat it as a systemic finding and sweep the rest of the site rather than fixing tags one by one; the method in triaging bad data quality across a site scales that sweep.

A Worked Example: The Pinned Flow Reading

Suppose a gas flow on the mimic has read exactly zero since early morning. Opening the tag detail, the quality is good and the timestamp is current, so communications are fine. The raw input is sitting at the very bottom of its configured range rather than floating near it, and the embedded trend shows a clean step to zero at a specific time rather than a decay. That combination says the transmitter is alive and reporting a true bottom-of-range signal: either flow genuinely stopped at that moment, or something happened at the meter - a closed valve, a frozen impulse line, a failed sensing element. The tag detail cannot pick between those, but it has eliminated SCADA, scaling, and comms in about thirty seconds, so the next call is to the field.

Now invert the example: same zero on the mimic, but the tag detail shows bad quality and a timestamp hours old. Nothing about the process can be concluded at all - the number on the screen is just the last value the system ever received. The two cases look identical on the mimic and opposite on the tag detail, which is the whole argument for opening it before acting.

Frequently Asked Questions