Custody measurement is not just a stream of numbers; it is a stream of numbers each carrying a statement about how much it can be trusted. When a flow computer computes the energy delivered over an interval using a gas composition, it also records whether that composition and that interval were sound or suspect. The questionable gas quality flag is the marker it raises when something has gone wrong with the composition input, such as the chromatograph alarming, timing out, or failing a limit check, so that the interval is not silently accepted as good. This flag is central to defensible measurement because it separates data you can bill on from data that needs review, editing, or a correction. This guide explains what raises a questionable flag, why every energy interval carries a quality status under the API 21.1 electronic gas measurement standard, and how flagged intervals drive measurement editing and prior-period adjustments.
Questionable quality flag in one line: A questionable gas quality flag is a status marker that a flow computer or SCADA system attaches to a gas composition or energy interval when the validity of that data is in doubt, typically because the chromatograph alarmed, timed out, failed a limit check, or otherwise did not deliver a trustworthy analysis. It signals that the interval should not be accepted as good without review, and it triggers measurement editing where a bad composition is replaced with a representative one and the affected volumes are recalculated. Under the API 21.1 electronic gas measurement standard every energy interval carries a quality status, so questionable data is preserved and traceable rather than silently used.
A questionable flag is raised whenever the system has reason to doubt the gas composition being used to compute energy. The most direct cause is a chromatograph alarm: if the GC itself reports a fault, an out-of-tolerance calibration, a failed analysis, or a stream not analysed, the flow computer knows the composition it received is untrustworthy and flags the interval accordingly. A timeout is another common trigger; if the flow computer expects a fresh analysis on a schedule and none arrives because the GC has stopped communicating or has stalled mid-cycle, the composition it holds is stale and the interval is flagged as questionable rather than assumed to be current.
Limit checks catch the more subtle failures where the GC delivers a number that is not obviously a fault but is not credible either. A well-designed flow computer checks the incoming composition against reasonable bounds: the components should sum to essentially one hundred percent, each component should fall within a plausible range for the stream, and derived quantities such as heating value and relative density should sit inside expected limits. A composition that fails one of these checks, for example a total that does not normalise correctly or a heating value that jumps far outside the stream's normal band, is flagged because it points to a bad analysis even when the GC did not raise its own alarm. These validation checks are the last line of defence against a plausible-looking but wrong composition entering the energy calculation.
It is worth being clear that the flag is a statement about confidence, not necessarily a statement that the number is definitely wrong. A questionable flag says the normal conditions for trusting this interval were not met, so it must be reviewed rather than accepted automatically. Some flagged intervals turn out fine on inspection; many need correction. The point of the flag is to force that judgement to happen rather than to let a suspect interval flow through into billing unexamined, and to leave a permanent record that this interval was suspect at the time it was recorded.
The reason every custody interval carries a quality status, rather than only the bad ones being noted, comes from how electronic gas measurement is meant to work under the API 21.1 standard. The standard is built around the idea that a flow computer records the measurement data along with the information needed to verify and audit it, and part of that information is the status of each interval, including whether the data was good, estimated, or questionable. Carrying a status on every interval means an auditor or an analyst reviewing the record can see at a glance which intervals were sound and which were not, without having to reconstruct the state of the instruments after the fact. The quality is data in its own right, stored alongside the volumes and energies.
This approach preserves the integrity of the record in a way that simply discarding or overwriting bad data would not. When an interval is questionable, the original suspect values and the flag are kept, so the history shows both that a problem occurred and how it was handled. That traceability is what makes the measurement defensible: a party to a custody transaction, or a regulator, can follow exactly what happened during a period when the GC was down or alarming, rather than finding an unexplained gap or a silently substituted number. The quality status is the thread that connects the raw event to whatever correction was applied.
Because the status travels with the data, it also lets downstream systems and people apply consistent rules. An accounting or allocation process can treat good intervals one way and questionable intervals another, holding the questionable ones for review before they are used, and reporting on how much of a period's energy rested on questionable data. This is far more robust than a system where the quality of the underlying data is invisible once the numbers reach the office, because the office can see the same quality picture the field instrument recorded and act on it. The flag is what makes the quality of the measurement portable from the field computer all the way to the settlement.
A questionable flag is not the end of the process; it is the trigger for measurement editing, which is the disciplined replacement of bad data with a defensible estimate. When a composition interval is flagged because the GC was down, the standard practice is to substitute a representative composition, often the last known good analysis or an agreed default for the stream, and recompute the energy for the affected interval on that basis. The edit is documented, the reason is recorded, and the original questionable value is preserved, so the correction is transparent rather than hidden. This editing is what turns a period of untrustworthy data into a defensible, corrected record that both parties can accept.
When the flagged period spans data that has already been reported or billed, the correction becomes a prior-period adjustment, a formal restatement of a previously issued measurement figure once the true or best-estimate values are known. If a GC was later found to have been reading wrong for a stretch, or a run of questionable intervals is edited after the fact, the resulting change to the energy for that period is issued as an adjustment against the original statement. The quality flags are what make these adjustments possible and bounded, because they identify exactly which intervals were suspect and therefore which volumes need restating, rather than forcing a wholesale re-examination of a period.
A cloud SCADA platform such as Merobix supports this whole workflow by surfacing quality flags in real time and preserving them through the historical record. Rather than a flag being buried in a flow computer log that no one sees until an audit, the platform can raise the questionable condition to operators and measurement staff as it happens, so a GC that has gone into alarm or stopped communicating is noticed and can be fixed before a long run of intervals is lost. Trending which intervals carry questionable status across a facility shows measurement teams where their data quality is weakest and which analyzers are causing the most editing, and holding the flags alongside the compositions and energies gives the analysts the auditable basis they need to perform editing and prior-period adjustments confidently. The flag, surfaced and trended, is what lets a measurement operation manage data quality proactively instead of discovering problems only at settlement.
It is raised whenever the flow computer has reason to doubt the gas composition it is using, most commonly because the chromatograph alarmed or reported a fault, because an expected fresh analysis timed out and the composition is stale, or because the composition failed a validity check such as not summing to one hundred percent or producing a heating value outside its normal band. The flag marks the interval for review rather than letting a suspect composition flow into the energy calculation unexamined.
The API 21.1 electronic gas measurement standard is built so that the flow computer records not just the measurement but the information needed to verify and audit it, and the quality status of each interval is part of that. Carrying a status on every interval, whether good, estimated, or questionable, lets an auditor see immediately which data was sound and preserves both the original values and how any problem was handled. This traceability is what makes the measurement defensible in a custody transaction.
Through measurement editing, where a flagged interval's bad composition is replaced with a representative one, often the last known good analysis or an agreed default, and the energy is recomputed on that basis, with the edit documented and the original preserved. If the flagged period was already reported or billed, the correction is issued as a prior-period adjustment that formally restates the earlier figure. The quality flags identify exactly which intervals need editing, keeping the corrections transparent and bounded.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.