> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sensorup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding the Time and Rate Engine

> Learn how the time and rate engine groups observations to calculate methane emission rates and temporal data for accurate volume quantification and reconciliation.

## What is the Time and Rate Engine?

The Time and Rate Engine is an intelligent calculation system that automatically processes your methane detection observations and transforms them into accurate emission events with calculated rates, volumes, and time boundaries. Instead of manually reconciling conflicting data from multiple sources, the engine applies consistent, industry-standard logic to give you reliable emission quantification for regulatory reporting and operational decision-making.

<CardGroup cols={3}>
  <Card title="90% Faster" icon="clock">
    Automated calculation processing
  </Card>

  <Card title="Multi-Source" icon="database">
    Consolidates all observation types
  </Card>

  <Card title="Regulation-Ready" icon="check">
    Industry-compliant calculations
  </Card>
</CardGroup>

## Why Use the Time and Rate Engine?

<CardGroup cols={2}>
  <Card title="The Problem" icon="triangle-exclamation">
    **Without automated processing:**

    * Manual reconciliation of conflicting observation data
    * Inconsistent calculation methods across emission events
    * Time-consuming volume calculations and temporal boundary setting
    * Difficult to maintain audit trails for regulatory compliance
  </Card>

  <Card title="The Solution" icon="lightbulb">
    **With the Time and Rate Engine:**

    * Automatic consolidation using configurable priority rules
    * Consistent, traceable calculations across all emission events
    * Instant rate and volume calculations with confidence bounds
    * Complete audit trail for regulatory reporting
  </Card>
</CardGroup>

## How It Works

The Time and Rate Engine processes your emission observations through three core functions:

### 1. **Smart Data Consolidation**

When you have multiple observations for a single emission event, the engine automatically selects and combines the most reliable data using configurable priority rules. For example, it might use the spatial accuracy from a flyover survey combined with the temporal precision from a continuous monitoring system.

### 2. **Intelligent Rate & Volume Calculation**

The system calculates emission rates and volumes using industry-standard methods, handling different observation types appropriately:

* **Standard detections** (satellite, drone, optical gas imaging): Uses arithmetic mean for multiple observations
* **Time-based observations** (continuous monitoring, operational events): Combines volumes over duration for accurate rates

### 3. **Automatic Time Boundary Setting**

The engine establishes start and end times for emission events using the most reliable temporal data available, including:

* Confirmed times from observations with explicit timestamps
* Estimated times using no-detection data and inference rules
* Default estimation methods for events with unknown start times

## Common Use Cases

**Regulatory Reporting**: Automatically generate compliant emission calculations with complete audit trails for regulatory submissions, eliminating manual reconciliation work.

**Multi-Source Event Analysis**: Process emission events detected by multiple methods (satellite, flyover, ground surveys) into single, coherent records with the best available rate and temporal data.

**Operational Event Tracking**: Handle planned emissions like compressor blowdowns by combining operational data with sensor observations for accurate volume quantification.

## Getting Started

<Info>
  **Ready to use the Time and Rate Engine?** The system automatically processes observations as they're added to emission events. Here's how to work with the results.
</Info>

<Steps>
  <Step title="Review Grouped Observations">
    Navigate to an emission event with multiple observations to see how the engine has consolidated your data sources.
  </Step>

  <Step title="Understand the Calculations">
    Review the calculated emission rate, volume, and time boundaries. The system shows which observations contributed to each calculation.
  </Step>

  <Step title="Verify Results">
    Check the confidence bounds and audit trail to ensure the calculations meet your accuracy requirements for reporting.
  </Step>
</Steps>

## Feature Specifications

<AccordionGroup>
  <Accordion title="Supported Observation Types" icon="list">
    **Site-Level Observations:**

    * Flyover Surveys (aircraft-based detection)
    * Drone Surveys (UAV-based detection)
    * Continuous Monitoring Systems (CMS)
    * Satellite Detection

    **Source-Level Observations:**

    * Venting, Flaring & Blowdown (VFB) events
    * Optical Gas Imaging (OGI)
    * Manual observations
    * Other monitoring systems
  </Accordion>

  <Accordion title="Calculation Methods" icon="calculator">
    **Rate Calculations:**

    * Single observation: Direct rate with confidence bounds
    * Multiple same-type: Arithmetic mean of all rates
    * Time-based observations: Volume-weighted rate calculation

    **Volume Calculations:**

    * Formula: Emission Rate × Duration (hours)
    * Automatic time zone conversion to UTC
    * Confidence bound propagation throughout calculations
  </Accordion>

  <Accordion title="Priority Configuration" icon="sort">
    **Default Site-Level Priority:**

    1. Flyover Surveys
    2. Drone Surveys
    3. Continuous Monitoring Systems
    4. Satellite Detection

    **Default Source-Level Priority:**

    1. Venting, Flaring & Blowdown
    2. Optical Gas Imaging
    3. Flyover Surveys

    *Note: Manual observations always receive highest priority regardless of type.*
  </Accordion>
</AccordionGroup>

## FAQ / Troubleshooting

<AccordionGroup>
  <Accordion title="Why are some time boundaries marked as 'Estimated'?" icon="question">
    Time boundaries are marked as "Estimated" when the system cannot find explicit start or end times in your observations. The engine uses no-detection data and default estimation rules (like 90-day lookback periods) to provide reasonable time boundaries for volume calculations.
  </Accordion>

  <Accordion title="How does the system handle conflicting observation data?" icon="question">
    The Time and Rate Engine uses configurable priority rules to select the most reliable data. Higher-priority observations (like manual entries) override lower-priority ones (like satellite detections). For observations of the same type, the system typically uses arithmetic averaging.
  </Accordion>

  <Accordion title="Can I override the automatic calculations?" icon="question">
    While the engine provides consistent baseline calculations, you can add manual observations with the highest priority to override automatic results when needed. The system maintains an audit trail showing both automatic and manual inputs.
  </Accordion>

  <Accordion title="What happens when an emission event is marked as repaired?" icon="question">
    When linked observations (like OGI leak repairs) are updated, the engine automatically recalculates the emission event's end time and volume to reflect the mitigation action, keeping your active emissions inventory current.
  </Accordion>
</AccordionGroup>

***

## Related Features

<CardGroup cols={2}>
  <Card title="Emission Event Management" icon="calendar" href="/use-sensorup/emission-operations/event-management/getting-started-with-event-management">
    Learn how to create and manage emission events that feed into the Time and Rate Engine.
  </Card>

  <Card title="Automatic Time Bounding" icon="clock" href="/use-sensorup/emission-operations/emission-quantification/understanding-automatic-timebounding">
    Understand how the system automatically sets temporal boundaries for emission events.
  </Card>
</CardGroup>

## Feedback & Support

<Warning>
  **Found an issue with calculation results?** Report calculation discrepancies through the emission event interface, including the specific observations and expected vs. actual results.
</Warning>