Compliance Monitor

The Compliance Monitor tracks regulatory deadlines, detects rule changes, monitors production data for violations, and computes risk scores for wells across an operator’s portfolio. It queries the knowledge graph service for entity data and applies domain-specific compliance logic.

Overview

Oil and gas operators must track dozens of regulatory deadlines, production allowables, and evolving rules. The compliance monitor provides four capabilities:

1. Deadline tracking — Scans permits, flaring authorizations, and filing deadlines for approaching or expired dates, categorizing alerts as critical, warning, or informational
2. Production monitoring — Checks well production data against allowable limits, flags gas-oil ratio (GOR) anomalies, identifies zero-production active wells, and detects unauthorized flaring
3. Rule change detection — Maps recent statewide and field-specific rule changes to affected wells and operations
4. Risk scoring — Computes a 0-100 compliance risk score per well based on deadline proximity, active issues, violation history, and flaring exposure, then ranks the portfolio

The service also provides a portfolio dashboard endpoint that aggregates all four capabilities for a given operator.

Port & Language

Key Endpoints

Architecture

Module Breakdown

src/compliance/
├── main.py           # FastAPI app, endpoint definitions, dashboard aggregation
├── config.py         # Settings from environment variables
├── deadlines.py      # Deadline scanning logic
├── production.py     # Production compliance checking
├── rule_changes.py   # Rule change detection
└── risk_scoring.py   # Risk scoring algorithm

Deadline Tracking (deadlines.py)

The scan_deadlines function processes three types of items:

Alert thresholds (configurable):

Alerts are sorted by days remaining (most urgent first). The response includes aggregate counts of critical and warning alerts.

Production Monitoring (production.py)

The check_production_compliance function evaluates each well against four checks:

Rule Change Detection (rule_changes.py)

The service maintains a registry of recent rule changes (currently hardcoded; in production, this would be scraped from RRC). Each rule change is matched against wells based on:

• Well type match: Does the rule affect this well’s type (oil, gas)?
• Field match: Does the rule target a specific field? (If no field restriction, all wells match.)

Currently tracked rule changes:

Risk Scoring (risk_scoring.py)

The score_well_risk function computes a 0-100 risk score across four weighted factors:

Risk levels:

The score_portfolio function scores all wells, sorts by risk (descending), and returns distribution statistics.

Portfolio Dashboard

The GET /compliance/dashboard/{operator_id} endpoint aggregates all four capabilities:

1. Fetch data from the knowledge graph service via Cypher queries:
   • Wells operated by the operator
   • Permits associated with the operator
   • Flaring authorizations on the operator’s leases
2. Run all checks: deadlines, rule changes, production compliance, risk scoring
3. Return summary with counts, alerts, and risk distribution

{
  "operator_id": "op-permian-01",
  "summary": {
    "total_wells": 12,
    "total_permits": 5,
    "total_flaring_auths": 3,
    "critical_alerts": 2,
    "warning_alerts": 4,
    "average_risk_score": 35.2
  },
  "deadlines": { ... },
  "rule_changes": { ... },
  "production": { ... },
  "risk_scores": { ... }
}

Dependencies

Python Packages

Service Dependencies

Configuration

Hardcoded thresholds (in config.py):

Running Locally

cd services/compliance-monitor
poetry install
poetry run uvicorn compliance.main:app --reload --port 8006