Skip to main content

OOOOa Fugitives Found

Published: 2026-06-24      Revised: 2026-06-24

What this report does​

Produces the data needed to populate the Fugitives Found sheet of the EPA CEDRI (Compliance and Emissions Data Reporting Interface) annual reporting template for NSPS (New Source Performance Standards) OOOOa (40 CFR Part 60, Subpart OOOOa — Standards of Performance for Crude Oil and Natural Gas Facilities). Each row represents one component type within a survey visit to a location unit, showing:

  • How many fugitives (leaks) were found for that component type
  • How many remain unrepaired
  • How many are on a Delay of Repair (DOR)
  • The reason for any delays

The report is formatted for Excel and sized for direct copy-paste into the CEDRI template. This report is in the OGI folder on the Reports tab.

This report reads from a pre-calculated data cache. The underlying data must be refreshed before running the report. Contact your system administrator if the report appears to show stale or missing data.

When to use it​

  • Generating the annual OOOOa CEDRI submission's Fugitives Found sheet.
  • Reviewing counts of fugitives found, unrepaired, and on DOR across location units for a reporting period.
  • Producing regulatory documentation of fugitive emission repair status.

Parameters​

ParameterDescriptionRequiredHow it filters
Start DateBeginning of date windowYesSurvey visits on or after this date are included
End DateEnd of the date windowYesSurvey visits on or before this date are included
LUnitsOne or more location units to includeYesOnly data for the selected units appears
RegulationsOne or more regulationsYesOnly fugitives under the selected regulations are counted

Columns​

ColumnWhat it shows
Fug SurveySurvey identifier — location unit name plus survey date (e.g., "OGI Site 1 04/16/18")
Fugitive TypeComponent type of the fugitive emission (e.g., "Valve", "Connector")
Fug Other TypeAlternative type description; blank — included to match CEDRI template layout
Fugitive NumCount of fugitives (leaks) found for this component type in this survey
Not Repaired NumCount of fugitives that have not yet been repaired
Delay Repaired NumCount of fugitives on a Delay of Repair (DOR)
Delay Repair ExplanationReason(s) for the delay; blank if no DORs

What's included and excluded​

Included:

  • OGI survey visits within the date range for the selected location units and regulations.
  • One row per component type per survey visit.
  • Only surveys where at least one leak was found (Fugitive Num > 0).

Excluded:

  • Survey visits outside the selected date range.
  • Components in units not selected.
  • Leaks under regulations not selected.

How key values are calculated​

Fug Survey

The survey identifier combines the location unit name with the survey date, formatted as "UnitName MM/DD/YY". This identifier matches the CEDRI template's row key format.

Fugitive Num

Count of distinct leaks found for the given component type during the survey visit, scoped to the selected location unit and regulation.

Not Repaired Num

Count of those leaks that do not yet have a closed repair date at the time the cache was last refreshed.

Delay Repaired Num

Count of leaks with an active DOR (Delay of Repair).

Delay Repair Explanation

Comma-separated DOR reason text for the leaks in this row. Blank when no DORs exist.

Tips and common questions​

  • "The report shows no data." This report reads from a pre-calculated cache. If the cache has not been refreshed recently, data for recent surveys will not appear. Ask your system administrator to refresh the cache before running the report.
  • "How do I refresh the report data?" The OOOOa Fugitives Found report reads from a pre-built data cache. To update the cache with the latest data, run the Refresh OOOOa Fugitives Found Cache utility in Chateau before generating this report. The refresh can be triggered from the Reports tab. Allow the refresh to complete before running the report — the report will continue to return the previous data set until the refresh finishes.
  • "Fug Other Type is always blank." This column exists to match the CEDRI template format; it is not populated by the system.
  • "The Fug Other Type column is always blank — is that correct?" Yes. Chateau does not currently populate the Fug Other Type field. If your CEDRI submission requires a value in this column, you will need to enter it manually in Excel after exporting the report.
  • "How do I know if the cache is out of date?" The report does not display the date the cache was last refreshed. If you are unsure whether the data is current, run the cache refresh before generating the report. It is best practice to always refresh the cache immediately before generating this report for a CEDRI submission.
  • "How is this different from OOOOa Fugitives Survey?" The OOOOa Fugitives Survey report provides survey-level rows with a Yes/No fugitive flag (for the CEDRI Fugitives Survey sheet). This report provides component-type-level detail with fugitive counts (for the CEDRI Fugitives Found sheet). Both are needed to complete the full CEDRI annual submission.
  • "This report is formatted for Excel." Column widths are set for CEDRI template copy-paste (margins exceed 11 inches). Export to Excel for best results; on-screen or PDF preview may appear cut off.

Sample output​

Report run for Example Facility, Start Date: 12/7/2025, End Date: 5/20/2026, LUnits: All, Regulations: OOOOa.

(No data rows — no matching fugitives found for the selected date range and regulation.)

Columns present:

Fug SurveyFugitive TypeFug Other TypeFugitive NumNot Repaired NumDelay Repaired NumDelay Repair Explanation
(empty)

Output format​

One row per component type per survey visit, ordered by survey date. Formatted for Excel export and sized for copy-paste into the CEDRI annual reporting template.

  • OOOOa Fugitives Survey — survey-level data (one row per survey per unit, with Yes/No fugitive flag) for the CEDRI Fugitives Survey sheet.
  • OGI Report — full OGI survey documentation with survey conditions, leak summary, and DOR records.