An analyzer that is powered on is not necessarily doing its job. What matters is whether it is producing data a facility can actually use and defend. Analyzer availability captures exactly that: the fraction of time an analyzer delivers valid measurements. For emissions and custody analyzers this is more than a maintenance statistic, because regulators and contracts often set a minimum availability an installation must meet. This guide defines the metric, explains why thresholds exist, describes what drags availability down, and shows how a SCADA system computes and reports it.
Analyzer Availability & Uptime in one line: Analyzer availability, also called uptime or data availability, is the percentage of time over a period that an analyzer produces valid, usable data rather than being down or reporting data flagged as invalid. It is a reliability metric because emissions monitoring systems and custody analyzers frequently must meet a minimum availability set by regulation or contract, and falling short can require corrective action or substitute data.
The key idea behind availability is that only valid data counts. An analyzer that is switched on but reporting readings known to be untrustworthy, because it is mid-calibration, in a fault state, out of its calibrated range, or has failed a quality check, is not producing valid data during that time. Availability therefore measures the proportion of the period in which the analyzer delivered measurements that pass the criteria for being usable, and every interval that fails those criteria counts against it even though the instrument may be physically running.
This distinction matters because the reason to run an analyzer is to have data you can act on, report, or defend. A reading that cannot be trusted is worse than useless in a regulatory or custody setting, so availability is defined around validity rather than mere operation. The exact rules for what makes data valid, such as whether calibration periods are excluded or how out-of-range readings are handled, come from the applicable standard or contract, but the underlying principle is constant: availability is the share of time the analyzer's output could actually be used.
Availability is normally expressed as a percentage over a defined window, such as a quarter or a rolling period, and computed from how many of the possible measurement intervals in that window were valid. A window with more invalid intervals yields a lower availability, and because the metric is a ratio it lets very different analyzers and sites be compared on the same footing regardless of how much data each nominally produces.
For a continuous emissions monitoring system, the data the analyzer produces is the basis for demonstrating that a facility is meeting its permit limits, so gaps in that data are gaps in the proof of compliance. Regulators therefore set minimum data availability requirements: the monitoring system must produce valid data for at least a stated fraction of the operating time, and if it does not, the facility may have to fill the gaps with conservative substitute data, take corrective action, or face a compliance shortfall. The threshold exists so that an operator cannot simply let a monitor sit broken and claim ignorance of what was emitted.
Custody and fiscal analyzers face a parallel pressure from the commercial side. When an analyzer's composition or quality measurement feeds the calculation of how much energy or product changed hands, a period without valid data means the transaction has to be valued using fallback assumptions or the last good reading, which both parties would rather avoid. Contracts and measurement standards often set expectations for how available such an analyzer should be and how to handle the periods when it is not, giving availability a direct financial weight.
Because of these consequences, availability becomes a managed target rather than an afterthought. Maintenance is scheduled to minimize valid-data loss, calibrations are timed and, where the rules allow, excluded from the calculation, and outages are tracked and explained. The threshold turns availability from a passive statistic into an operational obligation, and demonstrating that it was met is part of the record a facility keeps.
Downtime comes from several familiar sources. Scheduled calibrations and validations take the analyzer offline or produce data that is deliberately not counted while the check runs. Faults such as sample-system leaks, pump failures, fouled optics, depleted reagents, or a lost communications link produce invalid data or none at all. Preventive and corrective maintenance, from replacing a filter to swapping a detector, removes the analyzer from service. Even a sample conditioning problem upstream of the analyzer, such as a plugged probe or a moisture breakthrough, can invalidate readings while the instrument itself appears healthy.
To compute availability, a system counts the measurement intervals in the reporting window and classifies each as valid or invalid according to the applicable rules, then expresses the valid ones as a percentage of the total. This requires that the reason for each invalid interval be captured, whether it was a calibration, a fault code, an out-of-range condition, or a communications loss, because the rules often treat these categories differently and because the record must be explainable later. Good practice logs not just that data was missing but why, so the availability figure can be justified.
A cloud SCADA platform such as Merobix is well placed to do this because it is already receiving each analyzer reading with a quality flag and the analyzer's own status and fault signals as continuous tags. It can classify every interval as valid or invalid as the data arrives, accumulate the availability percentage over the reporting period automatically, and attach the reason to each downtime interval so the record explains itself. For an operator responsible for many remote analyzers, seeing each unit's availability trend and being alerted when one drifts toward its threshold turns availability from a figure computed painfully after the fact into a live indicator that prompts action before a shortfall is locked in.
You count the measurement intervals in a reporting window and classify each as valid or invalid, then express the valid intervals as a percentage of the total possible intervals. Whether periods like calibrations are excluded from the total depends on the applicable standard or contract. The result is a single percentage describing how much of the time the analyzer produced usable data.
It depends on the rules that apply. Under some regulatory schemes, required calibration and quality-check periods are excluded from the availability calculation rather than counted as downtime, while under others they reduce availability. Because the treatment varies, the applicable standard or contract defines exactly which intervals count, which is why the reason for each invalid interval must be recorded.
For a regulated emissions monitor, falling short can require filling the data gaps with conservative substitute values, taking corrective action, and explaining the shortfall to regulators. For a custody analyzer, missing valid data may mean valuing a transaction with fallback assumptions or the last good reading. In both cases, the shortfall becomes something the operator must document and address rather than ignore.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.