A single missed rapper firing sequence on an electrostatic precipitator can turn into a stack opacity spike within minutes, and on a UK power plant working under an Environment Agency permit, that spike becomes a compliance finding the moment it shows up in the CEMS data feed. Most ESP compliance failures are not caused by equipment that suddenly breaks. They are caused by maintenance evidence that cannot prove the rapper sequence ran on schedule, that the transformer-rectifier set held voltage and spark rate within range, or that the CEMS analyser was calibrated to BS EN 14181 before the reporting window closed. One UK power plant carried repeat ESP-related findings through three consecutive Operator Monitoring Assessment cycles before restructuring its entire ESP compliance evidence trail around a connected maintenance platform, and within nine months it recorded zero ESP compliance findings. This case study walks through exactly what changed, and you can see the same rapper, TR-set, and CEMS tracking workflow by visiting OxMaint directly.
OxMaint · ESP Compliance Tracking
See What a Complete ESP Evidence Trail Looks Like Before Your Next Audit
Rapper sequence logs, TR-set trend data, and CEMS calibration records, all tied to the same asset and the same reporting period, ready the moment an auditor asks for them.
Case Study · Power Plant · ESP Compliance
From Three Consecutive OMA Findings to Zero ESP Compliance Findings in Nine Months
A UK power plant restructured its rapper sequence records, TR-set health data, and CEMS calibration evidence around OxMaint, closing the compliance gaps that Environment Agency auditors and internal OMA reviewers kept flagging quarter after quarter.
0
ESP compliance findings recorded across every audit cycle since month nine of the OxMaint rollout
3
consecutive Operator Monitoring Assessment cycles with ESP-related findings before the programme changed
9 mo
from baseline audit to a fully evidenced, zero-finding ESP compliance record
72%
Across UK combustion plant audits, a large share of ESP-related permit findings trace back to missing or incomplete maintenance evidence rather than an actual equipment failure at the time of inspection. Rapper timing was adjusted but never logged. A TR-set spark rate crept upward for weeks with no trend record. A CEMS QAL3 drift check was completed but filed nowhere an auditor could find it. The equipment was often fine. The evidence trail was not, and that is exactly what an Environment Agency audit or an OMA review is built to catch. Auditors are not asking whether the ESP is running today. They are asking whether the plant can prove, for any date in the reporting period, that the rapper sequence ran to schedule, the TR-set stayed within its normal band, and the CEMS analyser was calibrated on time, and most plants cannot answer that question quickly enough.
Where the ESP Compliance Findings Kept Coming From
01
Rapper Sequence Drift With No Timing Record
The rapping system controls how often and how hard each collecting and discharge electrode field is struck to shake dust cake into the hoppers below. Under-rapping lets dust cake build up until it re-entrains at high gas velocity. Over-rapping strips the cake before it settles. Both push opacity upward, and both had been happening on this plant without anyone noticing, because rapper intensity and frequency settings were adjusted manually during outages and never logged against a baseline. By the time an auditor asked which zones had been touched during the last three outages, nobody on shift could answer with confidence.
02
TR-Set Degradation Nobody Was Trending
Each ESP field runs on its own transformer-rectifier set, and a TR-set that is slowly losing secondary voltage or drifting toward a higher spark rate is an early warning sign of collection efficiency loss, long before opacity actually breaches the permit limit. TR-set readings were recorded on paper log sheets during rounds, but nobody was plotting the trend across weeks, so a field could be quietly degrading for a month before anyone connected it to the opacity numbers. The readings existed. The pattern hiding inside them did not, because no one had time to sit down with a stack of log sheets and chart six fields by hand every week.
03
CEMS Calibration Evidence Scattered Across Systems
BS EN 14181 requires QAL2 calibration after installation or major change and ongoing QAL3 drift checks on a routine cycle. Those checks were being completed, but the calibration certificates, drift-check results, and analyser service records lived across a shared drive, a supplier portal, and a filing cabinet. When an auditor asked for the full evidence chain behind a specific reporting period, the plant's environmental team spent days assembling it, and gaps in that assembly became findings of their own. Two of the three OMA findings in the previous cycles were not about a missed calibration at all, but about the plant being unable to produce proof of a calibration that had, in fact, taken place on time.
The Nine-Month Turnaround, Phase by Phase
Months 1–2
Baseline Audit and Asset Register Build
The environmental and maintenance teams mapped every ESP field, TR-set, and CEMS analyser into a single OxMaint asset register, then pulled twelve months of historical rapper adjustment notes, TR-set log sheets, and CEMS calibration certificates to establish what evidence actually existed and where the gaps sat against BS EN 14181 and the plant's Environment Agency permit conditions. This baseline mapping alone surfaced two assets with no calibration record on file at all, despite calibration having reportedly been carried out.
Months 3–5
Structured Checklists Replace Paper Log Sheets
Zone-by-zone rapper verification checklists, TR-set readings with mandatory voltage and spark-rate fields, and CEMS QAL3 drift-check templates went live on mobile devices for shift technicians. Every entry required a measured value, not a checkmark, and every completed check fed directly into a timestamped, asset-linked compliance record. Technicians who had spent years filling in paper log sheets adjusted within the first few shifts, since the mobile checklist took less time than the form it replaced.
Months 6–7
Trend Alerts Catch Two Developing Issues Early
With TR-set data now trended automatically, the team caught a slow spark-rate climb on one field and a rapper motor current drift on another, both weeks before either would have shown up as an opacity exceedance. Both were corrected during planned maintenance windows instead of as emergency interventions during a running unit, and both corrections were logged directly against the assets involved, ready to show an auditor exactly when the issue was caught and how it was resolved.
Months 8–9
First Fully Evidenced Zero-Finding Audit Cycle
The next Operator Monitoring Assessment review and the following Environment Agency permit compliance check both closed with zero ESP-related findings. Every rapper sequence, TR-set reading, and CEMS calibration record for the reporting period was produced from OxMaint in one export, with no manual assembly required. The environmental manager described it as the first audit in years where the team was waiting on the auditor, rather than the other way around.
Three Systems Now Verified Every Shift
Pillar 1 · Rapper Sequence
Rapper Sequence Verification by Zone
Every ESP zone now has a defined rapping intensity and frequency baseline recorded in OxMaint, and each shift check confirms the live setting against that baseline before a technician can close the checklist. Rapper motor current is logged per rapper group, so a jammed mechanism or a seized rapper shows up as a flagged reading rather than a silent gap in cleaning coverage. Acoustic horn cycle counts on gas-side rapping are logged the same way, with every entry tied to a timestamp and technician identity for the audit record. Any override of the standard rapping schedule, planned or unplanned, requires a reason code, so the record explains itself without anyone having to ask the shift supervisor months later.
Pillar 2 · TR-Set Health
Transformer-Rectifier Set Trend Tracking
Secondary voltage, secondary current, and spark rate are logged per TR-set at every round and plotted as a rolling trend rather than a single point-in-time reading. OxMaint flags a field when its trend line moves outside the plant's defined normal band, well before the change is large enough to affect collection efficiency or stack opacity. The same record shows insulator condition notes and control panel firmware version, closing the gap that maintenance teams often leave around TR-set electrical components sitting on top of the ESP housing, out of easy sight and easy to defer during a busy round.
Pillar 3 · CEMS Records
CEMS Calibration and Permit Record Automation
QAL2 calibration certificates, QAL3 drift-check results, and analyser service history are all attached to the specific CEMS asset inside OxMaint, indexed by reporting period so an auditor's request pulls a complete, chronological evidence set instead of a search across three separate systems. Exceedance events, if any occur, generate an automatic work order and link back to the rapper and TR-set records from the same time window, giving the environmental team the full causal picture in one place instead of having to reconstruct the sequence of events from three separate systems after the fact.
Results Nine Months After the Rollout
0
ESP-related findings across the two most recent audit cycles, compared with findings in three consecutive cycles beforehand
2
developing TR-set and rapper issues caught by trend alerts and corrected during planned maintenance instead of as unplanned interventions
Minutes
time to produce a complete, timestamped evidence set for any ESP asset and reporting period when an auditor requests it
14181
BS EN 14181 is the UK monitoring standard behind QAL1, QAL2, and QAL3 requirements for CEMS on regulated plant
99.5%
typical ESP collection efficiency when rapping, electrode alignment, and TR-set performance are all within normal range
OMA
Operator Monitoring Assessment scoring is where incomplete rapper, TR-set, or CEMS evidence most often turns into a formal finding
Zone
rapper verification is tracked field by field rather than as one blanket ESP-wide check, matching how degradation actually develops
Most ESP compliance findings are not equipment failures. They are evidence gaps that show up the moment an auditor asks a specific question about a specific period.
Rapper sequence logs, TR-set trend data, and CEMS calibration records, connected to the same asset register and produced in minutes rather than days, are exactly what closes that gap.
UK ESP Compliance Requirements and Where OxMaint Fits
| Requirement | What It Covers | Typical Interval | OxMaint Coverage |
|---|---|---|---|
| Environment Agency Permit Conditions | Site-specific emission limit values, monitoring frequency, and maintenance obligations for ESP and CEMS assets | Continuous, permit-defined | Asset-linked condition tracking and evidence export |
| BS EN 14181 QAL2 | CEMS calibration after installation or major process change | After installation or change | Calibration certificate stored against the CEMS asset |
| BS EN 14181 QAL3 | Ongoing drift checks confirming the CEMS remains under control | Routine, typically monthly | Scheduled work orders with logged drift-check results |
| Rapper Sequence Verification | Rapping intensity, frequency, and motor current confirmed against baseline by zone | Every shift or defined round | Zone-level checklist with measured value requirement |
| TR-Set Performance Logging | Secondary voltage, current, and spark rate trended per field | Every round | Automatic trend alert on out-of-band readings |
| OMA Evidence Readiness | Complete, traceable maintenance record supporting the operator's self-monitoring score | Ongoing, reviewed periodically | One-export audit package by asset and period |
We were not failing because the ESP was in bad shape. We were failing because we could not prove, on demand, that the rapper sequence had run correctly or that a TR-set reading three weeks ago was within range. Once every check fed into one system tied to the actual asset and the actual date, the findings stopped. We have gone through two audit cycles since with nothing flagged on the ESP side at all.
Environmental Compliance Manager, UK Power Generation Site
Frequently Asked Questions
What does rapper sequence verification actually involve day to day?
A technician confirms each ESP zone's live rapping intensity and frequency against its recorded baseline, checks rapper motor current per group, and logs acoustic horn cycles on gas-side systems. Sign in to OxMaint to see the zone-level checklist structure.
How does TR-set trend tracking prevent a compliance finding before it happens?
Secondary voltage, current, and spark rate are plotted across consecutive readings rather than checked as single points, so a field drifting out of its normal band is flagged weeks before it affects opacity, giving time to correct it during planned maintenance.
Does this replace our CEMS calibration provider or our UK ETS reporting process?
No. OxMaint does not perform QAL2 or QAL3 calibration itself. It stores and organises the certificates, drift-check results, and service records your provider generates, so the evidence behind your permit and UK ETS returns is complete and retrievable in one place.
How long does a rollout like this typically take before findings stop?
This plant took nine months from baseline audit to a fully evidenced, zero-finding cycle, with structured checklists live within the first five months. Book a demo to map a timeline against your own asset count and audit calendar.
Does this work for plants running both ESP and baghouse systems, or mixed coal and gas assets?
Yes. Each ESP field, baghouse compartment, TR-set, and CEMS analyser is tracked as its own asset with its own checklist and threshold set, so mixed particulate control systems and mixed fuel types share one compliance record without forcing every asset into the same template.
ESP Compliance Findings Are Rarely About the Equipment. They Are About What You Can Prove.
Rapper sequence logs, TR-set trend data, and CEMS calibration evidence, connected to the same asset register and ready before your next Environment Agency audit or OMA review.
