Industrial stacks in India are subject to increasing regulatory scrutiny. State Pollution Control Boards and the Central Pollution Control Board (CPCB) expect plants running boilers, furnaces, kilns and incinerators, where covered by applicable directions, to demonstrate that their emissions stay within prescribed limits. This has led many operators to compare two very different approaches: a Continuous Emission Monitoring System (CEMS) and traditional manual stack testing. Understanding the difference is not just a compliance exercise. It can also affect plant uptime, regulatory exposure and long-term operating cost.
What Is a Continuous Emission Monitoring System (CEMS)?
A CEMS is a permanently installed analyser system that samples flue gas directly from the stack and reports pollutant concentrations, typically SO₂, NOx, CO, CO₂, O₂, particulate matter and, where relevant, HCl, HF, NH₃ and TOC, every few seconds. The data is logged locally and transmitted to a central server and, where required, to the regulator’s server.
Because a CEMS never stops sampling, it produces a continuous, time-stamped emission history rather than a single point-in-time reading. This matters for combustion processes, where pollutant concentrations can swing sharply during start-up, load changes, fuel switching or upset conditions, moments a manual test is unlikely to capture.
CEMS and OCEMS: how the terms differ
The two terms are related but not interchangeable. CEMS refers specifically to continuous monitoring of stack emissions, which is the subject of this blog. OCEMS (Online Continuous Emission and Effluent Monitoring Systems) is the broader online monitoring framework used in regulatory contexts, which also covers online effluent monitoring at discharge points. A stack CEMS is the emission-monitoring part of that wider framework.
Manual Stack Testing: How It Works and Where It Falls Short
Manual stack testing involves a technician visiting site with portable sampling equipment, extracting flue gas over a defined period (often 30 to 60 minutes), and sending samples to a laboratory or reading them on a calibrated field analyser. It has long been a standard method for demonstrating compliance and remains useful for analyser validation and for parameters that are difficult to measure continuously.
The limitations, though, are well recognised. A manual test is a snapshot: it reflects conditions during that single sampling window and says nothing about the other 8,759 hours in the year. Testing is usually scheduled in advance, so it may coincide with optimal rather than typical operating conditions. Results also take days or weeks to come back from the laboratory, by which time any exceedance has already passed uncorrected. For plant managers trying to run a stable, compliant process, this delay is a significant drawback of manual stack testing.
CEMS vs. Manual Stack Testing: A Side-by-Side Comparison
Set side by side, the operational differences are clear:
- Frequency of data: CEMS reports continuously, 24×7; manual testing offers a handful of readings a year.
- Detection of upset conditions: CEMS can flag an excursion within minutes; manual testing may never coincide with the upset at all.
- Regulatory reporting: where required, CEMS data can be transmitted to CPCB and SPCB servers in near real time; manual test reports are compiled and submitted manually, often weeks after sampling.
- Operational feedback: CEMS lets combustion or scrubber teams adjust process parameters during the same shift an exceedance appears; manual testing offers no such feedback loop.
- Long-term cost: CEMS typically involves a higher upfront capital cost, while repeated manual testing adds recurring laboratory, travel and technician costs over a plant’s operating life. The balance depends on the facility.
CEMS requirements apply to specified industries and facilities based on applicable CPCB/SPCB directions and regulatory conditions. Where CEMS is required, manual stack testing generally continues alongside it as a periodic cross-check.
Why Real-Time Reporting from CEMS Matters for Compliance
Real-time reporting is one of the main differences between the two approaches. When a CEMS transmits live data to a plant server and, where applicable, to the pollution control board’s central server, it offers three practical benefits that periodic manual testing is not designed to provide.
First, exceedances are visible immediately, to the plant and, where connected, to the regulator, which shortens the window between a process upset and a corrective response. Second, continuous data builds a detailed compliance record. Instead of relying on a handful of annual snapshots, operators have an auditable trail covering every hour of operation. Third, real-time visibility supports better process control: combustion engineers can correlate emission spikes with fuel quality, load changes or maintenance events and investigate root causes rather than only symptoms.
Key Components of a CEMS
A properly engineered CEMS is more than an analyser bolted onto a stack. It typically includes:
- Extractive or in-situ gas analysers suited to the stack’s temperature, dust load and moisture content
- A sampling probe and heated line to prevent condensation and analyser fouling
- A data acquisition system (DAS) that logs, time-stamps and validates readings before transmission
- Calibration gas cylinders and an automatic zero/span check routine
- Secure telemetry to the CPCB/SPCB server where required, with local data backup
Matching these components correctly, with analyser technology suited to stack conditions and sampling design suited to dust and moisture levels, is central to a system that performs consistently over its service life.
How CEMS Data Moves from Analyser to Regulator
A CEMS passes data through two separate stages, and it helps to think of them separately.
Stage 1: inside the plant (analyser to data acquisition system). The analysers measure the flue gas and send their readings to the data acquisition system over a local wired connection. Two common methods are used. A 4–20 mA signal is a simple analogue signal, where the strength of the current represents the measured value. Modbus is a digital communication protocol that lets the analyser send readings to the DAS as data. Both are used for short, local links between instruments.
Stage 2: outside the plant (data acquisition system to servers). Once the DAS has logged and validated the readings, a separate telemetry link sends them over the internet or a dedicated line to the plant’s central server and, where required, to the CPCB/SPCB server. This link typically uses a cellular (GPRS) connection or a leased line, depending on site connectivity.
Keeping the two stages separate makes the system easier to design and troubleshoot. A fault in the analyser signal and a fault in the internet link have different causes and different fixes.
Choosing a CEMS System Engineering Partner in India
Specifying and commissioning a CEMS is a technical decision that benefits from system engineering, not just equipment supply. Aaxis Nano works as a system engineering partner for CEMS, using continuous emission monitoring technology from technology partner ABB. Our scope includes:
- CEMS system engineering: configuring the system around your stack conditions, pollutants and reporting requirements
- Analyser integration: bringing analysers, sampling systems and calibration arrangements together into one working system
- Data acquisition and telemetry: data logging, validation and transmission to plant and regulatory servers
- Commissioning: installation, testing and verification of the system against its specification
- Lifecycle support: calibration, preventive maintenance and service support across the life of the installation
Talk to our experts to evaluate your stack emission monitoring requirements and design a CEMS with the appropriate analyser, sampling, data acquisition and telemetry architecture for your site.
Regulatory Drivers Behind CEMS Adoption in India
CPCB has issued directions under Section 18(1)(b) of the Water and Air Acts to State Pollution Control Boards and Pollution Control Committees, asking them to require online monitoring from the 17 categories of highly polluting industries, such as thermal power, cement, sugar, pulp and paper, iron and steel and fertiliser. These directions also extend to certain other facilities, including common effluent treatment plants, sewage treatment plants and common biomedical and hazardous waste incinerators. CPCB has also published guidelines on CEMS covering technical specifications and calibration and verification.
CEMS requirements apply to specified industries and facilities based on applicable CPCB/SPCB directions and regulatory conditions. Which parameters must be monitored, and by when, depends on the sector, the stack and the directions issued to the individual facility. Non-compliance with monitoring directions can lead to regulatory action by the relevant Board under applicable law, and the consequences depend on the circumstances of each case. Operators should confirm the requirements that apply to their own facility with the relevant State Pollution Control Board, ideally well before an expansion or renewal application, so that any CEMS installation can be planned rather than arranged under deadline pressure.
Common Pitfalls When Comparing CEMS and Manual Stack Testing
Plants moving from manual stack testing to a CEMS often underestimate a few practical issues. Sampling design matters: a sampling point too close to a bend or damper can produce unrepresentative readings regardless of instrument quality. Heated sampling lines are sometimes under-specified for high-moisture or high-dust stacks, leading to condensation and drift. Calibration discipline can also slip once a system is installed. A CEMS still needs a documented zero/span routine and periodic manual stack testing cross-checks to remain audit-ready. Addressing these details at the design stage, rather than after commissioning, helps a CEMS produce data that is suitable for regulatory reporting over its service life.
Conclusion: CEMS for Continuous Stack Emission Monitoring
Manual stack testing still has a role in validating analyser accuracy, but it does not provide continuous data. A CEMS delivers real-time reporting, a continuous data history and operational feedback, which improves data availability and supports better-informed decisions on combustion and emission control.
Aaxis Nano delivers CEMS as an engineered solution rather than a set of components: system engineering, analyser integration with ABB technology, data acquisition and telemetry, commissioning, and lifecycle support across India. Talk to our experts to discuss the CEMS requirements for your stacks.
FAQs
What is the core difference between a CEMS and manual stack testing?
CEMS uses analysers connected to the stack to measure pollutants such as SPM, SO₂, NOx and CO continuously, 24/7, and can transmit data automatically to the plant and, where required, to regulators. Manual stack testing, by contrast, involves periodic sampling (often quarterly or annually) by a technician, followed by laboratory analysis, giving only a snapshot of emissions at that specific moment.
Why does real-time reporting from a CEMS matter for regulatory compliance?
Real-time data means deviations or exceedances can be identified as they happen, allowing industries to take corrective action promptly rather than discovering an issue months later during a scheduled test. Where a CEMS is connected to regulatory servers, CPCB and SPCBs can also review data remotely and continuously, which reduces reliance on periodic self-reported data.
Can a CEMS fully replace manual stack testing?
Generally no. Where CEMS is required, periodic manual testing is typically still used to verify calibration, cross-check analyser accuracy and validate CEMS readings (for example, through Relative Accuracy Test Audits). The two work together rather than one replacing the other. Exact requirements depend on the applicable directions and consent conditions.
