A single number is not enough to describe a reading in an industrial system. To know what a value means you also need to know when it was true and whether it can be trusted. VQT - value, quality, timestamp - is the three-part unit that every historian and OPC interface uses to carry all of that together. This guide explains the VQT triple, why the three parts are inseparable, and how it unifies the concepts of quality and time into one data model.
Value-Quality-Timestamp (VQT) in one line: VQT stands for Value, Quality, and Timestamp - the atomic three-part unit that a historian or OPC interface uses to represent a single tag reading. The value is the measurement, the quality says how trustworthy it is, and the timestamp says when it was true. All three travel together because a value without its quality and time is ambiguous or misleading.
The value is the obvious part: the number or state the tag holds - a pressure, a flow, an on/off status. On its own it is incomplete, because a bare number does not say whether it is current, whether it can be trusted, or what instant it describes. The other two parts supply exactly that missing context, which is why serious industrial data models never store a value alone.
The quality says how much confidence to place in the value. At minimum it distinguishes good, bad, and uncertain: good means the source is healthy and the reading is valid, bad means it cannot be trusted because a device failed or communication was lost, and uncertain means the value is available but its reliability is in doubt. Many systems carry a richer quality code that also encodes the reason - a comms failure, an out-of-range sensor, a manual override, a value substituted or carried forward. Without quality, a stale or failed reading is indistinguishable from a good one.
The timestamp says when the value was true, not merely when it was received or stored. This is the provenance that makes a history meaningful, and it is why the source of the timestamp matters: a device timestamp reflects the moment of measurement, while an ingest timestamp reflects arrival. Bound into the VQT triple, the timestamp lets a buffered value land at its real time and lets events be ordered correctly, rather than being smeared by network delay.
The power of VQT is that it treats the three parts as one inseparable unit rather than three loosely related fields. Detach any one and the reading becomes ambiguous. A value plus a timestamp with no quality can be a failed sensor's frozen number masquerading as real data. A value plus a quality with no timestamp cannot be placed on a timeline or compared to anything. A quality and timestamp with no value is empty. Only the complete triple fully describes what was known, how well, and when.
This is why OPC interfaces and historians pass VQT end to end. A collector reads a source and produces a VQT; it forwards the whole triple to the historian; the historian stores the whole triple; a client that queries the tag gets the whole triple back. Quality and timestamp are not added or invented along the way - they originate with the reading and stay attached to it. That continuity is what lets a value carry its own trustworthiness and its own time across every hop in the system.
VQT also unifies concepts that are otherwise discussed separately. A data quality flag is the Q of a VQT; the debate over device versus server time is a debate about the T; deadband compression decides which VQTs to keep. Seeing them as facets of one triple rather than unrelated features clarifies how they interact - for instance, that a compressed archive stores VQTs, so a reconstructed value between stored points still needs a sensible quality and time, and that a backfilled point is a VQT inserted into the past with its original T intact.
For oil and gas monitoring, VQT is what lets a cloud SCADA platform be honest about data from unreliable remote sites. Every reading from a wellpad arrives as a value with a quality and a timestamp, so the platform can show an operator not just a number but whether it is current and when it was true. A pressure that reads normally but carries a bad quality and an old timestamp is immediately recognizable as a lost link rather than a healthy well, which is the difference between an informed decision and a dangerous assumption.
The triple also makes the whole data pipeline coherent. Buffered data backfills at its original timestamp, gaps are marked with bad-quality boundary points, calculated tags inherit the worst quality of their inputs, and events are ordered by their source timestamps - all of these are just operations on VQTs. Treating every reading as a value-quality-timestamp unit from the field device through the archive to the operator's screen is what keeps trust, time, and measurement aligned across the entire system.
Merobix carries VQT through the full path from field gateway to cloud archive to dashboard. Values keep their source timestamps so buffered data and events land correctly, quality travels so a stale or failed reading is never mistaken for a good one, and the archive stores the complete triple rather than a bare number - so an operator watching a remote site always knows what a value is, how far to trust it, and exactly when it was true.
VQT stands for Value, Quality, and Timestamp - the three-part unit used to represent a single tag reading in historians and OPC interfaces. The value is the measurement itself, the quality indicates how trustworthy it is, and the timestamp indicates when it was true. The three are treated as one inseparable unit because a value without its quality and time is ambiguous or misleading.
Because a bare number cannot say whether it can be trusted or when it applies. Without quality, a frozen value from a failed sensor looks identical to a healthy reading. Without a timestamp, the value cannot be placed on a timeline, compared, or correctly reordered after buffering. Only the complete triple describes what was known, how reliable it was, and at what moment, which is why serious industrial systems never store a value alone.
The data quality flag is the Q component of a VQT, and OPC quality codes are a standardized way of expressing that Q. Rather than being a separate feature, quality is one of the three parts of every reading, alongside the value and the timestamp. Seeing them as facets of one triple explains how they interact - compression stores VQTs, backfill inserts VQTs at their original time, and calculated tags combine the qualities of the VQTs they consume.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.