CEMS DAHS explained: how a data acquisition and handling system builds a reliable emissions record.
A Data Acquisition and Handling System (DAHS) is the layer of a CEMS installation that turns raw analyser output into the validated, time-stamped record used for regulatory reporting. A DAHS review examines how that configuration flags, substitutes, and averages data — a different exercise from an analyser calibration check. This guide explains what a DAHS does and the kinds of configuration issues a review is designed to catch.
What is a DAHS?
A Data Acquisition and Handling System is the software and hardware component of a CEMS installation that collects raw analyser output, applies calibration corrections, assigns data quality status flags, calculates period averages, and produces the validated data record used for regulatory reporting. It sits downstream of the analyser and upstream of the emissions report: the analyser measures a physical quantity, and the DAHS turns the resulting signal into the structured record a regulator, verifier, or permit inspector can actually assess.
In the CEMS market the same system is often labelled simply DAS. The two refer to the same product class here, but DAHS is the regulatory term of art — it is the term defined at 40 CFR 72.2 (as an "automated data acquisition and handling system") and the title of the European standard series EN 17255 — while DAS in general instrumentation means acquisition only, without the handling, validation and averaging layer that makes the system usable for regulatory reporting.
DAHS software vendors sell the platform. What determines whether the resulting data record actually holds up under regulatory scrutiny is how that platform has been configured — its flag logic, its substitution rules, and its averaging period definitions, checked against the standard or monitoring plan that applies to the installation. That configuration review is a distinct exercise from analyser calibration or platform selection, and it is where this guide is focused.
How a DAHS builds a data record
Signal ingestion and calibration correction
The DAHS receives the raw output signal from each analyser channel and applies the instrument's current calibration correction — derived from the site-specific calibration function where one applies — before the reading is treated as measured concentration data. If the calibration correction applied does not match the analyser's actual, current calibration status, every downstream figure inherits that error.
Data quality flagging
Every data point or averaging period is assigned a status flag indicating whether it is valid, affected by calibration or maintenance activity, invalid and requiring substitution, or excluded from the averaging calculation entirely. The flag attached to a period determines how — or whether — that period contributes to the reported figure, which makes flag logic one of the highest-leverage points in the whole system.
Missing data substitution
When a period is flagged invalid or missing, the applicable framework determines what happens next: some regimes require the DAHS to substitute a defined value rather than leave a gap — typically a high percentile of recent valid data or a conservatively calculated estimate — while others require the period to be invalidated and excluded from the average entirely, with limits on how many invalidated periods are tolerated before the operator must act. Substitution or invalidation logic that is misconfigured, or applied outside the conditions the standard allows, can undermine an otherwise-complete data record.
Averaging period calculation
The DAHS aggregates flagged, corrected, and substituted data into the averaging periods the permit or standard requires — commonly hourly, half-hourly or daily periods, though the applicable period depends on the installation and pollutant. An averaging window that is defined incorrectly, or that mixes valid and excluded data inconsistently, will produce a period average that does not reflect what was actually measured.
Emissions record output
The output of the pipeline is the validated data record that feeds the regulatory report — annual emissions figures, exceedance logs, and data availability statistics. Reviewing this stage means tracing the reported figure back through the averaging, substitution, and flagging logic to the underlying analyser output, to confirm the two are actually consistent with each other.
Common data quality flag categories
Much of CEMS data review work comes down to how flag categories like these have been applied over the assessment period. Getting the flag logic right is what makes a data record "reliable" in a regulatory sense — not just complete, but complete in a way that a regulator or verifier can actually check.
Valid
The data point or period was measured by an analyser operating within its calibrated, in-service condition, with no quality concern identified. Valid data is used in the averaging calculation without adjustment.
Under calibration or maintenance
The analyser was undergoing a scheduled calibration check, zero and span test, or maintenance activity during the period. Data captured during this window is typically treated separately from normal operating data rather than included at face value.
Invalid, requiring substitution
The data point failed a validity check — instrument fault, signal out of range, calibration function no longer valid — and cannot be used as measured. The applicable substitution method must be applied in its place.
Excluded from averaging
The period falls outside the conditions the standard defines for inclusion — for example, start-up or shut-down conditions under some frameworks — and is deliberately excluded from the reported average rather than substituted.
Why DAHS configuration depends on the applicable standard
A DAHS is a general-purpose platform: it can usually be configured to run flag logic, substitution rules, and averaging periods to more than one regulatory framework. The correct configuration for a given installation depends on which framework — or combination of frameworks — actually applies, and reviewing a DAHS in isolation, without reference to the applicable standard, will miss that.
Data acquisition and handling systems
The CEN standard series written specifically for DAHS: Part 1 covers requirements for handling and reporting data, Part 2 sets requirements on the DAHS itself, Part 3 defines the performance test, and Part 4 covers installation and ongoing QA/QC. It sets out how raw data becomes reported data — acquisition, validation, correction and averaging — and treats validity and status indicators as recommended intermediate data rather than prescribing a fixed set of flag codes.
CEMS quality assurance framework
Defines the QAL1/QAL2/QAL3/AST quality assurance framework for the analyser and measuring system itself at IED-regulated installations in Europe — the foundation a DAHS configuration review sits alongside, though EN 14181 does not itself define DAHS flag logic.
US CEMS data requirements
Sets federal requirements for CEMS data recording, quality assurance, and missing data substitution for units subject to the Acid Rain Program and related trading programmes in the United States. Its substitution hierarchy is prescriptive and tiered to monitor data availability — a different mechanism from the invalidation-based approach used under the EU's Industrial Emissions Directive.
Monitoring, reporting and verification
Requires DAHS configuration to match the installation's approved monitoring plan, including its data quality procedures and how data gaps are treated and disclosed in the annual emissions report submitted for verification.
Best available techniques
Sector-specific BAT conclusions under the Industrial Emissions Directive set monitoring data quality requirements, averaging periods, and reporting formats that a DAHS configuration must follow for the relevant industrial process.
Frequently asked questions
What does DAHS stand for in CEMS?
DAHS stands for Data Acquisition and Handling System. It is the component of a CEMS installation that collects raw analyser output, applies calibration corrections, assigns data quality flags, calculates period averages, and produces the validated data record used for regulatory reporting.
What is a CEMS data review?
A CEMS data review is an independent check of the DAHS data record against the applicable regulatory standard. It typically covers a defined period, reviews how data quality flags were applied, checks the substitution values used during data gaps, confirms the DAHS configuration against the analyser calibration log, and verifies that the aggregated period totals in the regulatory report are consistent with the underlying record.
How do you know if CEMS data is reliable?
Reliable CEMS data has a complete audit trail from analyser output through to the reported figure: data quality flags applied consistently with the applicable standard, substitution values calculated by an approved method during any gaps, and reported period averages that reconcile with the underlying record. Confirming this generally requires an independent review rather than relying on the DAHS output alone.
What is a data quality flag?
A data quality flag is a code applied to each data point or averaging period in the CEMS record to indicate its validity status. The typical categories are valid data, data under calibration or maintenance, invalid data requiring substitution, and data excluded from the averaging calculation. In the US, 40 CFR Part 75 prescribes a closed set of Method of Determination Codes for this purpose; in Europe, EN 17255 treats validity and status as recommended intermediate data without prescribing an equivalent fixed code set.
How is missing or invalid CEMS data handled?
It depends on the applicable framework. Some regimes require the DAHS to substitute a defined value rather than leave a gap — typically a high percentile of recent valid data or a conservatively calculated estimate — while others require the period to be invalidated and excluded, with limits on how many invalidated periods are tolerated before the operator must act. The exact rule, and the data capture rate below which further action is required, is set out in the applicable standard or approved monitoring plan.
DAHS or CEMS data review support.
Describe the DAHS platform, the regulatory framework, and the specific data concern. We will respond with a structured review approach.
Send an enquiry contact@futuregaz.com