SCADA Data for Emissions Reporting in Oil and Gas

Consider a compressor station closing its April emissions inventory. The April fuel-gas export arrives on the second working day of May. It is one tag, hourly values for April. The emissions workbook still contains the figures from the March reporting close. March’s fuel row holds a replacement total an analyst entered during that close, after the series went flat, and a note that points to an email. April’s engine calculation will use the new export, or a treated version of the hours in it that are missing or invalid. In the close meeting, nobody can explain March’s reported volume without retrieving the earlier correction and its supporting email. April’s flat hours are another unresolved question.

What has to be true before a SCADA tag is an emissions input

A SCADA tag becomes an input to emissions reporting when the people running the calculation can say which value they used, and why. At this station, “the fuel gas tag” is not specific enough. The reporting lead needs the tag for the actual compressor-engine meter, the period pulled from the historian, and the unit and time basis of that series. The tag originates in the site’s SCADA (supervisory control and data acquisition) environment. Buying or replacing that operational system is a different decision from whether its data is ready for an emissions calculation.

Halfway through April the series goes flat. A flat trace can be real zero flow, such as a shutdown, or an invalid reading from a frozen tag. Fuel the engine did not burn during a real shutdown belongs in the total as zero for those hours. An invalid reading still needs a treatment, and the applicable method, including any missing-data procedure it requires, decides whether those hours stay, drop out, or take an approved substitute. Until someone can say which case these hours are, there is no April fuel volume worth calculating from.

The close still has to settle that for this meter before April’s total is safe to use. A software evaluation asks a reporting platform the same thing: who owns a missing value, and what happens when another file disagrees with the extract. That test sits in emissions reporting software.

How a historian extract fails the calculation

The export can look complete and still be the wrong fuel volume. More than one of these problems can show up in the same month. The historian may have stored exactly what the tag sent. The engine calculation still needs a fuel volume someone can explain.

The tag and the meter

The tag can be mapped to the wrong meter. Years ago, someone pointed this historian point at a row called “Station 4 fuel gas.” The station has two fuel meters, one on the engine and one on a heater on the same pad. The workbook has a single fuel row for the engine calculation. If the tag is the heater, or a blend of both, the combustion estimate is using the wrong gas. The export does not say which meter it is. The row name does, and the row name is what the close meeting is trusting.

A meter replacement creates another risk. If operations changes the engine fuel meter but the reporting workbook still queries the retired tag, the export may continue producing a file even though it no longer represents the active meter.

Missing readings, bad values, and units

Missing hours get a value they were never given. Fourteen hours in April’s export are empty because the tag dropped offline. If the engine was running during those hours but the workbook treats the missing readings as zero, the calculated monthly fuel volume will be understated. Carrying the last good reading forward can overstate or understate the volume, depending on what the missing hours really were and which earlier reading is used. Excluding those hours without an approved substitute can also understate the monthly total. Each treatment produces a different monthly volume. The applicable method decides which treatment is allowed. None of them is visible once the only number on the table is a monthly total that has already been summed.

A bad interval can fail in a different way. For a run of hours the value does not move, down to the decimal. In the historian those hours may be marked bad or questionable. Whether that status travels with the number depends on the export. The file can keep the numeric reading and drop the quality status. The workbook then has a full-looking cell, and a sum can include that reading with no sign that a bad or questionable status should have prompted a review. A frozen number is not the same thing as fuel the engine burned at that rate.

A unit mismatch can go unnoticed because the workbook still produces a numerical result. This tag is stored as a rate, and the calculation wants a volume for the month. Converting a flow rate into monthly volume requires the correct units and time basis. If the calculation averages readings without accounting for missing or invalid periods, the resulting volume may be wrong even though the spreadsheet completes the arithmetic. A similar error occurs when a fuel volume recorded in cubic meters is used with an emissions factor that expects thousand cubic feet, without converting the units first.

The time window and the allocated volume

The clock on the export is a separate mismatch. The historian stamps are in UTC. The reporting month is local time, and this station’s gas day does not close at midnight. An export labeled April can include hours from the next gas day, or drop the last hours of this one, depending on who set the start and the end. If the workbook retains only the month label and the total, the reporting lead may not see the window that was actually pulled.

Production accounting may already have a different fuel quantity for the same engine. The meter records measured flow. Production accounting may use an allocated or adjusted quantity, moving gas between the engine and the heater, or between this station and another, under the measurement group’s rules. Where a reporting method specifies which quantity to use, that method controls. A company rule can choose between the meter and the allocated quantity only when the method allows the choice. The workbook contains both values on different tabs. The reporting lead still needs to establish which one the applicable method requires, and to record that choice and the reason the other value was not used. Disagreement does not, by itself, make the measured flow the right reporting input.

When the spreadsheet becomes the real system

March’s series contained an invalid interval. During the March reporting close, an analyst entered a replacement fuel value in the workbook and wrote the reason in an email. The note in the column says the tag was bad.

When April’s export arrives, the workbook contains March’s corrected total, but the historian does not. The next analyst can retrieve the original March readings without seeing why the reported value differed. Unless the workbook note and supporting email are preserved, the team cannot reconstruct the decision from the source data alone. The value that enters the calculation is the cell, not the tag. That is how the workbook becomes the system of record for the fuel value that gets reported.

The same volume is then typed again. It moves from the historian export into the workbook, from the workbook into the reporting tool, and sometimes into a second template because another program wants the fuel on a different layout. That re-key is one of the places environmental compliance work breaks. The same pattern shows up across other industrial compliance workflow bottlenecks: a value gets moved between systems without carrying the context that explains it.

What has to stay with the value the calculation used

The fuel value needs a record of where it came from and how it was changed. That means the tag and the physical meter it represents, the time range that was pulled, and whether that range matches the reporting period or only overlaps the station’s gas day. It also means the unit stored in the historian, any conversion, and which intervals were left out, replaced, or given a substitute, along with the reason.

It also needs the value that was actually selected. If an allocated quantity was used instead of measured flow, the record should show which review chose it and that the applicable method allowed the choice. The review or approval behind the value can be a named person, a defined review step, or both. What matters is that a later reader can see the decision without reconstructing it from memory.

That record is what lets the next person reproduce the fuel volume without searching an inbox, and it is what an emissions assurance and verification review will ask to see. The close meeting’s job is to keep these facts with the number.

What operations keeps

Operations keeps the control system and the historian. The environmental team does not need to own either one. A live connection from the historian into a reporting tool can end the monthly paste. The applicable reporting method still decides which fuel quantity to use and how missing or invalid hours are treated. The filings that use this fuel volume are regulatory air and GHG reporting.

Frequently asked questions

Can a SCADA or historian export go straight into an emissions calculation?

Only when the tag, the units, the time basis, and the gaps are known, and the value that will be used has been accepted under the applicable procedure. A file with a row for every interval can still be the wrong meter, a rate treated as a volume without accounting for missing periods, or a month that includes readings whose quality status never left the historian.

What should you do with missing or bad intervals?

Follow the treatment the applicable method requires, including any missing-data procedure. Do not treat a blank as zero, and do not leave a frozen value in the total, unless that method allows it. An internal habit does not override the method. A zero, a value carried forward, and an approved substitute can each produce a different volume, and carrying a previous reading forward can overstate or understate the result. The interval, the treatment, and the review behind the value have to stay with the number. A month total that has already summed the gaps has hidden that decision.

Why do the historian and production accounting disagree?

They often are not the same quantity. A historian total is measured flow at the meter. Production accounting may already have allocated or adjusted that fuel between equipment or between stations, and the day boundaries may not match. Where a reporting method specifies the quantity, that method controls. A company rule can choose between the two only when the method allows the choice. Write down which value was used. Disagreement alone is not a reason to prefer the historian.

Does connecting the historian replace the spreadsheet?

A connection can stop the monthly re-key from the export into the workbook. It does not decide which tag is the right meter, what treatment an invalid interval requires, or which total wins when measured flow and an allocated quantity differ. If those decisions and corrections exist only in the workbook, the workbook has effectively become the system of record for the value that gets reported. The historian is still where the series was stored.

Is this the same project as buying or replacing a SCADA system?

No. Operations already runs that system, and the historian already stores the tag. The reporting question is what happens to the export after it leaves that store: which value is used, how missing or invalid hours were treated, and whether the next person can see the choice. A new control system does not answer that.

From historian data to a reporting input

Validere supports regulatory air and GHG reporting from operational inputs through calculation, review, and filing, while operators keep the control systems and historians they already run. Connecting a historian does not, by itself, settle which data is valid or which quantity the reporting method requires. For teams still moving data through monthly exports and workbooks, Validere connects existing operational systems to that reporting work.