Nobody has time to read a report listing every well that is running fine - what operations needs is the short list of what is not. Exception reporting is the reporting philosophy that surfaces only the abnormal: the sites out of limits, the wells behind target, the equipment overdue. It is management by exception applied to operational data, and it is what keeps a large field manageable by one person. This guide explains what exception reporting is and, importantly, how it differs from the telemetry technique with a similar name.
Exception Reporting in one line: Exception reporting is a reporting approach that presents only the items that fall outside expected or acceptable conditions - the exceptions - rather than every value. Instead of a full status list, an exception report shows just what needs attention: readings out of range, targets missed, or conditions requiring action.
An exception report is built by applying a set of rules or thresholds to a body of data and outputting only the records that violate them. Where a full report might list all 300 wells with their production and status, an exception report lists only the 12 wells producing below target, the 3 tanks near high level, and the 2 sites that have not communicated in an hour. Everything performing normally is deliberately omitted, because 'normal' does not require action.
This is the operational expression of management by exception: focus human attention on deviations, not on confirming that most things are fine. A well-designed exception report is ranked or grouped by severity, so the most urgent exceptions rise to the top, and it defines its criteria clearly so the same conditions always appear. The report answers a single question - what needs my attention right now?
These two terms are easily confused and are genuinely different. Report by exception (RBE) is a telemetry transmission technique: a field device sends a value over the wire only when it changes past a deadband, to save bandwidth and power on cellular or radio links. It is about how data moves from device to host. Exception reporting, in contrast, is an information and reporting practice: after data has been collected, a report or view presents only the out-of-limit conditions to a person.
In short, RBE decides what a device transmits; exception reporting decides what a human sees. One is a communications optimization at the edge, the other is an analytics and presentation choice on the host side. A system can use both - devices reporting by exception to save airtime, and dashboards reporting exceptions to save attention.
Exception reporting scales operations. A single foreman may be responsible for hundreds of wells across a basin; reviewing each one daily is impossible, but reviewing an exception report of the two dozen that need attention is routine. Exception views drive morning rounds, dispatch decisions, and management summaries by filtering the field down to actionable items, often layered with severity so the worst problems surface first.
A cloud SCADA like Merobix historizes tags from field devices read over Modbus, DNP3, and OPC UA, and exception reports and dashboards are built on that data by applying limits and rules to surface only the sites and assets that are out of tolerance. The platform provides the contextualized data and the alarm state; the exception report is the lens that shows the operator just the deviations, wherever they are in the field.
It is a reporting approach that shows only the items outside expected conditions - the exceptions - rather than every value. Instead of listing everything, an exception report surfaces just what needs attention: readings out of range, targets missed, or conditions requiring action, so people focus on deviations rather than confirming normal.
Report by exception (RBE) is a telemetry technique where a field device transmits data only when it changes past a threshold, to save bandwidth. Exception reporting is a reporting practice where, after data is collected, a report shows only out-of-limit conditions to a person. RBE decides what a device sends; exception reporting decides what a human sees.
Because it scales operations. A single person responsible for hundreds of wells cannot review each one, but can review an exception report of the two dozen needing attention. By filtering the field down to actionable, out-of-tolerance items - often ranked by severity - exception reports drive rounds, dispatch, and management summaries efficiently.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.