Continuous parametric monitoring is how operators prove a control device is working when they are not measuring the emissions coming out of it directly. Instead of a stack analyzer, a CPMS continuously logs a surrogate operating parameter - a temperature, a flow, a pressure - that is known to track the device's performance. This guide explains what a CPMS is, why surrogate parameters are used, and how the logged data demonstrates compliance.
Continuous Parametric Monitoring (CPMS) in one line: A continuous parametric monitoring system (CPMS) continuously measures and records surrogate operating parameters - such as combustion temperature, flow rate, or pressure - that indicate whether a control device is operating in the range that keeps it compliant, without directly measuring the emissions themselves. It provides the ongoing record that proves a device stayed within its established operating limits between performance tests.
Directly and continuously measuring the emissions leaving every control device would require analyzers that are expensive, delicate, and unnecessary for many small sources. Continuous parametric monitoring takes a different route. Regulators and operators identify an operating parameter that reliably indicates whether the device is performing - for a combustion device, that is often the firebox or combustion temperature, because a device kept hot enough is destroying the target pollutant, while a device that cools off is not.
The logic is that the parameter serves as a surrogate. Once a performance test establishes that the device achieves its required efficiency at, say, a certain minimum temperature, then continuously keeping the device above that temperature is treated as evidence it is still performing. The CPMS is the equipment that measures and records that parameter around the clock, so the surrogate becomes a continuous, auditable indicator rather than an occasional spot check.
Different control devices use different parameters. A thermal oxidizer or combustor leans on temperature; a scrubber might rely on liquid flow or pressure drop; a carbon adsorber might track breakthrough indicators. The common thread is choosing a measurable quantity that moves with the device's effectiveness and watching it continuously.
A CPMS does not stand alone; it is anchored to a monitoring plan and an operating limit. The plan documents which parameter is monitored, how the instrument is installed and calibrated, how data is averaged, and what limit the parameter must stay within. The operating limit - for example a minimum temperature averaged over a defined period - is the line that separates compliant operation from a problem.
When the monitored parameter crosses that line, the event is an exceedance or a deviation, and it triggers a defined response: it must be recorded, often investigated, and in many cases reported. This is the compliance teeth of parametric monitoring. The continuous record is not just for reassurance; it is the document that either shows a device stayed inside its limits for the reporting period or flags the periods it did not, along with corrective action.
Because averaging periods and limits are specific to each device and rule, operators configure the CPMS and its data handling to match the applicable monitoring plan exactly. A reading that would be an exceedance under one averaging convention might be acceptable under another, so the plan definitions govern how the raw parameter stream is turned into compliance status.
Parametric monitoring is a natural fit for SCADA, because the parameters it relies on - temperatures, flows, pressures - are already the kind of signals a field control system reads and trends. A combustor temperature transmitter feeding a controller is doing exactly what a CPMS needs; the additional work is applying the correct averaging, comparing against the operating limit, and preserving the record in a form auditors accept.
A cloud SCADA platform like Merobix supports parametric monitoring by continuously acquiring those parameters, retaining a time-stamped history, and alarming the moment a value drifts toward or past its operating limit. Merobix does not itself certify a monitoring plan or replace the regulatory determination of which parameter and limit apply, but it provides the continuous, tamper-evident record and the real-time alerts that let operators catch a cooling combustor or a dropping flow before it becomes a reportable exceedance.
The practical payoff is that compliance stops being a periodic reconstruction from scattered logs and becomes a live property of the operation. An operator can see at a glance whether every controlled source is sitting inside its parametric window, and can pull the supporting record for any period on demand rather than assembling it after the fact.
Direct continuous emissions measurement needs analyzers that are costly and complex, and is unnecessary for many smaller control devices. Parametric monitoring instead watches an operating parameter, such as combustion temperature, that reliably indicates whether the device is performing. Keeping that parameter within an established limit serves as continuous evidence the device is still working.
It is when the monitored operating parameter crosses the limit set in the device's monitoring plan - for example a combustion temperature falling below its required minimum over the defined averaging period. An exceedance is recorded, often investigated, and in many cases reported, along with any corrective action. The continuous record is what documents both compliant periods and exceedances.
It depends on the control device. Combustion devices such as thermal oxidizers and combustors usually monitor firebox or combustion temperature. Scrubbers may monitor liquid flow or pressure drop, and other devices use their own indicators. The chosen parameter is one shown to track the device's effectiveness, so keeping it in range indicates continued compliant operation.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.