Flaring Monitor

The Flaring Monitor is a comprehensive flaring compliance service that tracks flare event volumes, validates Form R-32 filings, calculates emissions (CO2e), forecasts authorization exceedances, manages repair obligations, handles operational events with deduplication and submission guards, and provides burn rate projections.

Overview

Texas operators that flare or vent natural gas must comply with RRC Rule 32 (Statewide Rule 32). The flaring monitor provides the data backbone for this compliance workflow:

• Volume tracking — Ingest flaring events, compute cumulative volumes, and assess compliance against authorization limits
• Pre-filing validation — Validate Form R-32 data completeness before submission
• Emissions calculation — Compute CO2, CH4, and CO2-equivalent emissions for flaring and venting, assess EPA OOOOb applicability
• Predictive analysis — Forecast when an authorization will be exceeded using decline curve analysis and model infrastructure delay impacts
• Audit trail — Tag events with applicable regulatory frameworks (RRC, EPA, GHGRP) and write HMAC-signed audit entries
• Flare event CRUD — Full lifecycle management of individual flare events with correlation
• Burn rate projections — Calculate daily burn rates and project authorization exhaustion dates
• Repair obligations — Track repair commitments triggered by flare events
• Operational events — Unified event system for 5+ event types with deduplication rules, custom event types, and submission guards

Port & Language

Key Endpoints

Volume Tracking & Compliance

Emissions & Audit

Predictive Analysis

Flare Events CRUD

Burn Rate & Projections

Repair Obligations

Operational Events (Unified)

Duplication Rules

Custom Event Types

Submission Guard Rules

Dashboard & Seeding

Architecture

Module Breakdown

src/flaring/
├── main.py                      # FastAPI app, core endpoint definitions, background tasks
├── config.py                    # Settings and emission factor constants
├── schemas.py                   # Pydantic request/response models
├── volume_tracker.py            # Flaring volume processing and compliance assessment
├── validation.py                # Form R-32 pre-filing validation
├── prediction.py                # Decline curve forecasting and infra delay modeling
├── audit_tagging.py             # Regulatory framework tagging, Form PR generation, audit writes
├── burn_rate.py                 # Burn rate calculation and alert thresholds
├── burn_rate_routes.py          # Burn rate API routes
├── event_routes.py              # Flare event CRUD routes
├── repair_routes.py             # Repair obligation routes
├── operational_event_routes.py  # Unified operational event CRUD
├── duplication_engine.py        # Event deduplication rule engine
├── duplication_rule_routes.py   # Deduplication rule CRUD routes
├── event_type_service.py        # Custom event type management
├── event_type_routes.py         # Custom event type routes
├── submission_guard_engine.py   # Pre-submission validation guard engine
├── guard_rule_service.py        # Guard rule management service
├── guard_rule_routes.py         # Guard rule routes
├── compliance_triggers.py       # Event-driven compliance trigger logic
├── correlation.py               # Event correlation logic
├── event_number.py              # Sequential event number generation
├── override_capture.py          # Override tracking for guard acknowledgments
├── seed_events.py               # Demo operational event seeder
├── seed_duplication_rules.py    # Demo deduplication rule seeder
└── seed_event_types.py          # Demo custom event type seeder

Emissions Calculation

The /flaring/emissions endpoint computes emissions using EPA-standard factors:

EPA OOOOb applicability: Wells spudded after November 15, 2021 are subject to OOOOb methane emission standards.

Alert Thresholds

Nightly Burn Rate Recalculation

A background task runs every 24 hours (with a 60-second startup delay) that recalculates burn rates for all active authorizations:

1. Query all distinct authorization_id values from flare_events
2. For each authorization, aggregate daily volumes
3. Recalculate the burn rate and update projections

Operational Event Deduplication

When creating an operational event, the DuplicationRulesEngine checks the new event against configurable rules to detect potential duplicates:

• Rules define matching criteria (entity, time window, event type, severity)
• If a potential duplicate is detected, the API returns a warning
• The caller can acknowledge the duplication and proceed by setting duplication_acknowledged: true

Submission Guards

The SubmissionGuardEngine evaluates pre-submission rules before an event can be created:

• Rules define conditions that must be met (e.g., required fields, minimum data quality)
• If a guard rule fails, the API returns the failing conditions
• The caller can acknowledge and override by setting guard_acknowledged: true

Dependencies

Python Packages

Service Dependencies

Configuration

Hardcoded emission factors and thresholds are in config.py. See the Emissions Calculation section above for values.

Running Locally

cd services/flaring-monitor
poetry install
poetry run uvicorn flaring.main:app --reload --port 8007

Seeding Demo Data

# Seed operational events, duplication rules, and custom event types
curl -X POST http://localhost:8007/seed-events