A continuous emissions monitoring system exists to answer one question, repeatedly, in a form a regulator will accept: what came out of the stack, and can you prove it. The analysers do the measuring. Everything that turns those readings into a defensible record is the system around them — and that is the part we build.
What the system has to get right
| Requirement | Why it is harder than it looks |
|---|---|
| Continuity | A gap in the record is treated as a failure to monitor, not as missing data. Availability targets apply to the data, not just to the hardware |
| Validity | A reading taken while the analyser is calibrating, faulted or out of range is not a valid emission reading and must not be averaged in as one |
| Traceability | Every reported figure has to trace back to a raw measurement and to the analyser state at that moment |
| Reporting format | The regulator specifies averaging period, units and file format. Having the data is not the same as being able to report it |
Data validity handling
This is where home-grown emissions reporting usually falls apart. Raw analyser output is not emissions data until the system knows what state the analyser was in.
| State | How it is treated |
|---|---|
| Normal operation | Recorded as valid |
| Zero and span calibration | Period flagged and excluded from emission averages; drift recorded |
| Fault or out of service | Period flagged; substitution rules applied only where the regulator permits them |
| Out of range | Recorded with the exceedance marked rather than clipped |
| Plant not operating | Distinguished from monitoring downtime — for compliance these are not the same thing |
Where it sits
| Interface | Purpose |
|---|---|
| Analyser shelter | Reads the analysers and their status contacts |
| Plant control system | Process state, so emissions can be attributed to operating condition |
| Historian | Long-term retention alongside the rest of the plant record |
| Reporting output | Files in the format and on the cycle the authority requires |
What we take responsibility for
| Included | Not included |
|---|---|
| Acquisition, validation, averaging, retention and reporting | Supply and certification of the analysers themselves |
| Analyser shelter integration and cabinet build | Stack sampling system design and probe installation |
| Interfacing to the control system and historian | Regulatory approval of the installation |
Talk to an engineer
The useful conversation starts with which authority you report to, what analysers are installed, and how that data becomes a report today. Contact us.
Ask for a technical walkthrough
Tell us the plant, the authority you report to and what you run today. Screens and an architecture diagram beat a datasheet.