A permitted facility does not only report what it emits; it reports when it fell outside the lines. When a monitored parameter crosses a limit, or a required monitor goes offline, that event is a deviation, and regulations oblige the facility to disclose it. The excess emissions and deviation report is how that disclosure is made - periodically, in a defined form, signed by a responsible official. This guide explains what counts as a deviation, the recurring reports that carry them, and how a SCADA system's alarm and exceedance history can auto-populate the record rather than leaving staff to reconstruct it.
Excess Emissions & Deviation Report in one line: An excess emissions and deviation report is the periodic filing in which a permitted facility discloses every instance where a monitored parameter exceeded a permit limit or a required monitor was unavailable. Under programs like Title V it takes the form of semiannual monitoring reports and an annual compliance certification, and it draws directly on the facility's exceedance and monitor-downtime records - exactly the history a SCADA system captures.
A deviation is any departure from what the permit requires, and it is broader than most people first assume. The obvious case is an exceedance: a monitored value crossing an emission limit or operating limit. But a deviation also includes failing to monitor when monitoring was required - a period where a continuous monitor was offline and no valid data was collected counts as a deviation from the monitoring obligation even if actual emissions were fine. Missed testing, a lapsed calibration, or a breach of an operating parameter that stands in for emissions can all be deviations. The permit defines the lines; anything outside them, including gaps in the demonstration itself, is a deviation to be reported.
Not every deviation is treated identically. Regulations often distinguish deviations caused by malfunctions, startup, or shutdown from those occurring during normal operation, and the reporting can carry the cause, duration, and any corrective action taken. Some events trigger prompt, standalone reporting on their own timeline rather than waiting for the periodic report. But the common thread is that a deviation is a factual event with a start, an end, and a cause, and the facility is obligated to have recorded it accurately enough to disclose it later. That recording burden is precisely where a continuous monitoring record earns its keep.
Under the Title V operating permit program, deviations are carried in two recurring artifacts. The first is the periodic monitoring report, commonly filed on a semiannual cycle, which lists all deviations from permit requirements identified during the period - each exceedance and each monitoring gap, with the relevant detail. If there were no deviations, the report still gets filed stating that. The second is the annual compliance certification, in which a responsible official certifies the facility's compliance status for the year based on the monitoring and the deviations recorded. These are not optional summaries; they are required submissions with legal weight behind the official's signature.
Because a responsible official is personally certifying the content, the accuracy and completeness of the underlying record is not a clerical concern but a liability one. A certification that overlooks a real exceedance, or a periodic report that misses a monitor-downtime deviation, exposes both the facility and the signer. This raises the bar on how deviations are captured through the period: the record has to be complete and defensible when the reporting date arrives, which is difficult if it is reconstructed at the last minute from scattered logs. The reports reward facilities that maintain a continuous, queryable record of every exceedance and every monitoring gap throughout the period rather than assembling one after the fact.
The two things a deviation report needs - a record of every limit exceedance and a record of every period a monitor was unavailable - are both things a SCADA system already tracks. When a monitored value crosses a configured limit, the system raises an alarm and time-stamps the start and end of the exceedance; when an analyzer drops offline or a data gap opens, the same system logs the loss of valid data. Over a reporting period these events accumulate into exactly the two lists the report requires, already carrying the who, what, and when that the disclosure has to include.
A cloud SCADA platform such as Merobix turns that accumulated history into the raw material for the report rather than a pile of logs someone must comb through. Because exceedances and data gaps are captured as discrete, time-stamped, queryable events, the semiannual report becomes a filtered query over the period, and the data-availability accounting the certification relies on comes straight from the record. Just as importantly, the same alarming that populates the report notifies operators in real time, so an exceedance or a monitor outage can be addressed while it is happening - shortening the deviation itself and, in the case of a downtime event, sometimes preventing it from becoming a reportable gap at all. The report stays a formal compliance filing; the SCADA record is what makes it accurate and painless to produce.
Often, yes. If monitoring was required during a period and no valid data was collected because the monitor was down, that gap is a deviation from the monitoring obligation even if actual emissions were within limits. This is why data availability and monitor uptime are compliance concerns in their own right - a dark monitor can manufacture a deviation, so facilities track and report downtime alongside exceedances.
The semiannual monitoring report lists all deviations identified during the reporting period - each exceedance and each monitoring gap. The annual compliance certification is a yearly statement in which a responsible official certifies the facility's overall compliance status based on that monitoring. The periodic report is a factual list of events; the certification is a signed attestation carrying personal legal weight.
A SCADA system already captures the two things the report needs: time-stamped records of every limit exceedance and every period a monitor was unavailable. Because those are stored as discrete, queryable events, the periodic report becomes a filtered query over the period rather than a manual reconstruction, and the data-availability accounting comes straight from the record. The same alarming also lets operators respond in real time, shortening or preventing the deviation.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.