Settlement Engine

The engine ingests raw meter data and applies statistical methodologies to calculate the Customer Baseline Load (CBL). It compares actual consumption against this counterfactual baseline to determine the precise load reduction delivered. Key M&V adjustments include:

• Weather normalization: Correcting for temperature deviations from the baseline period
• Opt-out subtraction: Removing non-participating assets from the portfolio calculation
• Symmetrical additive adjustment: Aligning the baseline magnitude with the event-day morning load

A settlement engine must encode the specific tariff structures and market products governing the transaction. This includes Real-Time Pricing (RTP) signals, Critical Peak Pricing (CPP) overlays, and Ancillary Service Market clearing prices. The engine dynamically applies:

• Performance thresholds: Minimum load reduction required to qualify for payment
• Curtailment windows: The exact start and end times of the dispatch event
• Locational Marginal Price (LMP) multipliers for nodal-specific settlements

Beyond simple payment for performance, the engine enforces contractual obligations. It calculates non-performance penalties when a resource fails to meet its committed capacity during a dispatch event. Conversely, it computes over-performance bonuses for exceeding contracted load reduction. The logic handles:

• Consecutive failure triggers: Escalating penalties for repeated underperformance
• Make-whole payments: Compensating resources dispatched out of economic merit order
• Capacity deficiency charges: Applied when a resource's availability drops below its nominated volume

The engine performs rigorous data quality checks before financial calculation. It flags and quarantines intervals with missing telemetry, time-drift anomalies, or unrealistic consumption spikes. For Virtual Power Plant (VPP) aggregations, it reconciles sub-meter data against the master revenue meter. The system generates an immutable audit trail detailing every calculation step, enabling participants to trace exactly how a settlement amount was derived and file formal disputes.

In a Demand Response Aggregator model, the engine disaggregates a single wholesale market payment across a portfolio of retail customers. It allocates revenue based on individual contribution percentages, subtracting the aggregator's contracted fee structure. The engine manages complex hierarchies:

• Utility-to-aggregator bulk settlement
• Aggregator-to-customer pass-through credits
• Dual participation logic preventing a single asset from being compensated in two concurrent programs

The engine must interface with the Independent System Operator (ISO) or Regional Transmission Organization (RTO) financial systems. It formats settlement statements according to strict regulatory timelines (e.g., FERC Order 745 compliance). The engine handles resettlement cycles, automatically recalculating historical periods when meter data is corrected or market prices are republished, ensuring financial positions remain accurate across billing cycles.

The rigorous analytical process that quantifies actual load reduction against a Customer Baseline Load (CBL). M&V is the primary data source for the settlement engine, using statistical models to filter out noise and confirm that a demand response event resulted in a genuine deviation from expected consumption. Without robust M&V, financial settlement is arbitrary.

• IPMVP provides standard protocols for determining savings
• Utilizes interval meter data at 15-minute or hourly granularity
• Adjusts for weather, occupancy, and production variables

A statistical calculation of what a customer's energy consumption would have been in the absence of a demand response event. The settlement engine uses the CBL as the counterfactual reference point to calculate the delta between actual and expected load. Common methods include High X of Y averaging, which selects the highest usage days from a recent window to prevent baseline inflation.

• Directly determines the financial credit or penalty for a participant
• Requires recalibration to account for load growth and seasonality
• A flawed baseline leads to overpayment or underpayment disputes

The competitive marketplace where grid operators procure specialized services like frequency regulation and spinning reserves. The settlement engine calculates payments based on whether a resource delivered its committed capacity with the required speed and accuracy. Performance scores in these markets directly impact the settlement multiplier applied to a resource's base payment.

• Fast-responding assets like batteries earn premium pricing
• Penalties apply for failing to meet ramp rate obligations
• Settlement often occurs on a sub-hourly basis for regulation services

A real-time or time-varying electricity rate transmitted to consumers to incentivize load reduction. The settlement engine ingests these price signals to calculate the financial baseline against which savings are measured. In Real-Time Pricing (RTP) environments, settlement is the difference between the actual price and a pre-agreed strike price, multiplied by the curtailed volume.

• Critical Peak Pricing (CPP) triggers high settlement values for rare events
• Requires precise time synchronization between meter and pricing engine
• Price volatility increases settlement risk for aggregators

A third-party entity that enrolls multiple retail customers into a single portfolio to bid aggregated load reduction capacity into wholesale markets. The settlement engine treats the aggregator as the single counterparty, distributing payments to individual assets based on a secondary, private settlement logic. The aggregator absorbs performance risk if one asset underperforms.

• Manages the complexity of behind-the-meter assets
• Must reconcile utility settlement statements with internal sub-meter data
• Subject to credit requirements from the market operator

The marginal cost of supplying the next increment of electricity at a specific node on the grid, accounting for generation costs and physical transmission congestion. The settlement engine uses LMP to value demand response at the exact location where it occurs, meaning a load reduction in a congested area receives a higher payment than one in an unconstrained zone.

• Reflects the true economic value of local load reduction
• Nodal pricing creates granular settlement differentials
• Requires integration with the market clearing engine