AI monitoring of emissions and environmental safety at a chemical plant

Manual control lags: exceedances are discovered after the fact, when the incident has already occurred. We develop and implement an end-to-end emissions monitoring system — with sensors, analytics, and a data transfer procedure. Warning arrives before a deviation becomes an accident.
Frequently Asked Questions

Why manual emissions monitoring lags

Manual sampling works like this: an operator walks the control points on a schedule, collects samples into containers, and sends them to the laboratory.

Hours pass between sampling and the result — transportation, preparation, and the analysis itself; the source condition changes several times during this time.

Laboratory analysis delay devalues monitoring where it is needed most. A burst release lasts minutes: by the time the laboratory reports the concentration, the plume has dispersed, and the exceedance of the emission limit remains only in an archived record with a timestamp.

The discrete nature of sampling makes the picture worse — an entire shift passes between two samples, and everything that happens in the interval does not make it into reporting.

Some sources are not covered by control points at all: vents, drainage tanks, dosing units — the operator visits them rarely according to the procedure, and an abnormal mode starts there without warning.

An exceedance of the emission limit is detected by an indirect sign — an odor at the boundary of the sanitary zone or a complaint.

Late notification of enterprise services means decisions after the fact: there is no longer any way to influence the process; all that remains is to record the consequences and prepare explanations.

We explain how this is addressed by continuous measurement at the source: the signal reaches the control room at the moment of deviation, not a shift later.

What changes after implementation: measurable effects

Reduction of time from release to signal

Previously, an exceedance was recorded in the laboratory protocol hours after the release had already occurred: samples are taken on schedule, not based on the deviation.

With continuous monitoring, the threshold rule triggers directly on the sensor reading, and the operator on duty sees the deviation within the polling cycle — while the process mode can still be restored.

The response time to a deviation drops from hours to minutes, and some incidents are closed as routine adjustment rather than as an event.

Growth in the share of automatic measurements

Stationary gas analyzers take on the components that previously made it into the report only during a scheduled round or on request.

The share of automatic measurements across controlled points reaches 80–90%, with the rest being specific substances that physically cannot be measured in flow. It is this share that determines how complete the emissions picture for a shift becomes.

The effect then ripples through the entire chain. The number of manual samples decreases severalfold, because the laboratory switches from routine rounds to investigating disputed and peak situations — the workload is redistributed rather than increased. Continuous monitoring removes the gaps between rounds in which unnoticed deviations accumulated.

Most importantly, the class of violations "detected after the fact" disappears: when an exceedance was identified through a complaint or inspection, there was nothing left to correct, only explanations to prepare. Now the signal arrives before the complaint.

Emissions monitoring methods: stations, laboratory, calculation

The main choice is between continuous measurement, periodic sampling, and balance calculation.

It is determined by the source class, the source coverage area, and what needs to be proven: an exceedance at the boundary of the sanitary protection zone or a gross emission for the reporting period. In practice, methods are combined and recorded in the industrial environmental control program.

Stationary monitoring stations

An automatic station provides a continuous series for priority substances and triggers at the moment of release — no scheduled sampling can do this.

Sampling frequency is replaced here by sensor polling, and verification frequency becomes critical: an uncalibrated channel produces false alarms and devalues the entire measurement archive.

Mobile sampling and calculation methods

A mobile laboratory covers sources outside the coverage area of stationary stations; sampling frequency is set by the hazard class of the substance and the operating mode of the shop.

The calculation method complements measurements — based on raw material consumption and material balance, it provides an estimate for the period where instrumental monitoring for each source is unprofitable.

The combination of "measurement plus calculation" passes verification under ISO 14001: it confirms both the fact of the release and the completeness of accounting.

Option When it fits Limitations
Stationary monitoring station Large source, real-time signal needed Narrow coverage area of one station, expensive maintenance network
Mobile laboratory Scattered sources, scheduled monitoring Snapshot at the time of sampling, does not catch a burst release
Calculation method Many small sources, reporting for the period Does not replace measurements in disputed situations

How implementation proceeds: from survey to operation

Implementation proceeds in stages: first the site is surveyed in full, then the system is assembled and tested on real shifts, and only after that is it handed over to operating personnel.

This order makes it possible to start monitoring by area without waiting for the entire plant to be ready, and to immediately compare readings with the actual picture.

Survey and design

  1. Production survey — we walk the site, record emission sources, equipment operating modes, the ventilation scheme, and the zones where concentrations change fastest.
  2. Control point layout — we tie each point to a source and the boundary of the sanitary zone so that measurements reflect the actual picture rather than local gas contamination near a wall.
  3. Data collection and transmission setup — we define the polling frequency, buffering in case of channel interruption, trigger thresholds, and the notification route for the dispatcher.

Verification and launch

  • Installation and commissioning — we install sensors, connect them to collection units, and check communication channels and power.
  • Testing on real shifts — we compare readings with laboratory samples and manual measurements across different modes, including equipment startup and shutdown.
  • Personnel training — we cover response to triggering, working with the event log, and the procedure for communication loss.
  • Handover to operation — we hand over the maintenance procedure, instructions, and notification settings, after which we support the first weeks of operation.

The key result of this stage is that the system begins to provide reliable data before responsibility is transferred to it.

System datasheet, procedures, and data transfer schemes

An emissions monitoring system is operated for years, and its fate is decided not at implementation but when the contractor or engineer changes for the first time.

If only monitoring panels remain at the site, there is nothing with which to restore the logic of the thresholds, prove measurement reliability, or pass supervisory inspection.

Therefore, the deliverable includes a set of documents that remains with the customer and does not depend on us.

Procedure for actions in case of exceedance

The most in-demand document on a shift.

It contains threshold levels and response time for each, automatic actions when triggered (sample capture, switching to a backup circuit, line shutdown), and the escalation procedure: who receives the notification first, who is called at night, and where the operator's decision is recorded.

A separate block covers behavior during a false trigger and sensor failure, so the shift does not have to guess and does not silence the signal.

The site retains:

  • control system datasheet — circuit composition, sampling points, ranges, and purpose of each unit;
  • procedure for actions in case of exceedance — thresholds, response time, automation, escalation;
  • data flow diagram — the path from sensor to archive and external reporting, with places where losses are possible;
  • access policy for measurements — who sees raw values, who can change setpoints, and how edits are recorded;
  • verification and maintenance log — calibrations, replacements, and verifications tied to specific points;
  • shift instructions and failure recovery plan — what to do before the engineer arrives;
  • setpoint map with justification — why the threshold is exactly this value and how to change it legally.

How monitoring changed at an operating production facility: before and after figures

An operating production facility with a continuous cycle: several process lines, its own gas analyzers, and a laboratory that manually confirmed every deviation. Burst releases were caught after the fact — through complaints, shift records, or laboratory data the next day.

The task was not to change the fleet of instruments but to assemble a continuous picture from their readings and teach the system to distinguish normal operating variation from a burst release.

What changed in figures

Metric Before implementation After implementation
Share of detected burst releases 46% 97%
Time from release to operator signal 4–6 hours 3–8 minutes
Manual samples per shift 30–40 5–7, only by deviation
Share of episodes handled according to procedure 55% 92%

The key change is not the accuracy of an individual sensor but the thresholds. Previously, a single common standard applied to the area, and a short burst release against the background of planned fluctuations simply did not stand out.

The system calculates a profile for each source separately, takes into account the line mode and weather conditions, so the signal arrives tied to a specific unit rather than "somewhere at the site".

The second effect is the economics of attention. Four fifths of manual samples are gone because sampling has become selective: the laboratory goes to check a specific event rather than stand watch on a schedule. The operator receives a signal while the episode can still be closed with a procedural operation.

The data align with external reporting — we verify the methodology against open emissions registers, for example European Pollutant Release and Transfer Register, and this removes supervisory authorities' questions about the completeness of the picture.

What to do if sensors and an in-house laboratory are already in place

At an operating site, stationary stations and gas analyzers are usually already installed, and the enterprise laboratory maintains its own sampling protocols.

There is no need to replace this circuit entirely: certified measuring instruments are tied to methods and verification, and their readings are already integrated into reporting.

Therefore, the basic logic is enhancement instead of replacement: a collection and analysis layer is built on top of the already installed measuring instruments.

The first step is inventory: which instruments actually output data, at what frequency, what is written to the local archive, and what exists only on paper.

The results show where it is sufficient to take a signal via the standard interface, where a converter is needed, and where a sensor will have to be replaced — in a targeted way, by group, without stopping the rest of the circuit.

Integration with existing systems is a separate task. We do not break or duplicate the current dispatching: the flow runs in parallel, on a unified time scale, together with the laboratory records of manual samples.

Then a spike on an instrument is compared with the analysis result, and the decision is made based on two independent sources rather than one.

We migrate archived data at the start, not after launch. We export history from previous storage systems, bring it to common units and timestamps, and load it into the new circuit — past periods remain available for comparison.

For emissions monitoring this is fundamental: without historical data, a one-off spike cannot be distinguished from a systematic trend.

Monitoring does not stop in the process: work proceeds in stages, and the old circuit continues to record data until the moment of switchover.

Common technical doubts before starting work

Doubts before starting usually concern not analytics but how the system behaves in a live production environment: how it withstands interference, whether it diverges from the laboratory, and what happens when the shop stops. Below are answers on the units most often checked before signing the work plan.

How are interference and false triggers filtered out?

An exceedance is recorded only when the signal persists over several consecutive polling cycles, plus cross-confirmation from neighboring points. Steam, dust, and equipment warm-up are filtered by response profile rather than by a single threshold.

Why do readings diverge from the laboratory?

The laboratory has a different sampling point and a different averaging time — the divergence comes from the methodology, not from an instrument error.

We reconcile through parallel sampling and calibration coefficients for the period; the history of verifications and coefficients is stored so the result is reproducible.

Can it be implemented without stopping the shop?

Yes. We install sensors on standard fittings and bypasses, and perform commissioning during process windows. The new system launches in parallel with the old one, and rollback to the previous configuration is possible within a shift.

Does the enterprise circuit remain closed?

Deployment is inside the perimeter; only aggregated indicators go outside. Access is role-based, and all changes are logged. Maintenance and verification follow a procedure with a list of operations and a calibration schedule.

What about reliability in bad weather?

Wind, fog, and inversion change dilution, so the system runs a dispersion model based on weather data and distinguishes between "emissions increased" and "conditions did not allow dispersion." If the weather channel is lost, a conservative mode is enabled with a note about reduced reliability.

Let's discuss your task and come back with a work plan

So that the assessment is for your site and not a standard template, source data is enough for us — after that we will consolidate it into a scheme ourselves and calculate the load on the measurement channels.

The more specific the inputs, the fewer assumptions in the project and the shorter the path to launching the monitoring system.

It is useful to send:

  • list of emission sources: stacks, ventilation emissions, flare lines, raw material warehouses — with a note on which are already monitored and which are not;
  • operating modes: continuous, periodic, startups and shutdowns, emergency releases — they determine the trigger logic and notification thresholds;
  • supervisory requirements: which indicators are regulated, how often reporting is submitted, and in what form it is accepted;
  • existing sensors and control systems: what is installed now and which interfaces are available for data acquisition;
  • conditions at sampling points: temperature, corrosiveness of the medium, dust, humidity — this determines the selection of measurement channels;
  • historical data for past periods: we use it to test the model on real emissions, not synthetic data;
  • response procedure: who receives the signal, within what time, and which actions are considered routine.

In response, you receive a solution scheme with the channel composition, the order of stages with acceptance points, and a list of what is required from your side at each step. Describe the task — we will come back with an assessment for your site and a work plan.

AI Development Areas

Latest works

  • Development of a web application for FEEDME
    Development of a web application for FEEDME
    1393
  • Development of an online store for the company FURNORO
    Development of an online store for the company FURNORO
    1368
  • B2B Advance company logo design
    B2B Advance company logo design
    815
  • Development of a web application for Enviok
    Development of a web application for Enviok
    1139
  • AIDER company logo development
    AIDER company logo development
    1057
  • CRM development for Chasseurs
    CRM development for Chasseurs
    1152