Skip to main content

OCPI 2.2.1 Tariff Calculation Engine

Project description

OCPI Tariffs

CI Python Version License

A production-ready Python implementation of the OCPI 2.2.1 Tariff module. This package provides a robust calculation engine to compute the cost of Charging Data Records (CDRs) against complex OCPI Tariffs.

It is designed to handle real-world complexities such as:

  • Tariff Dimensions: Exact calculation for Time, Energy, Parking Time, and Flat Fees.
  • Restrictions: Validation of Start/End time, Day of week, and Min/Max duration restrictions.
  • Timezones: Automatic handling of "Local Time" restrictions using Country Code mapping (e.g., NLD -> Europe/Amsterdam).
  • Step Size: Precise implementation of OCPI "step size" rounding rules (e.g., 5-minute increments).

Methodology

The calculation engine follows a strict interpretation of the OCPI 2.2.1 specification, processing a CDR and a Tariff to produce a final Cost.

1. Chronological Processing

The engine processes the CDR's charging_periods chronologically. For each period:

  1. Duration Calculation: The duration is derived from the gap between the current period's start_date_time and the next period's start.
  2. Local Time Resolution: The period's start time is converted to the Charging Location's local time (derived from cdr_location.country) to accurately evaluate time-based restrictions (e.g., "08:00 - 18:00").

2. Tariff Element Selection

For each period, the engine searches for an Active Tariff Element:

  • It iterates through the Tariff's elements.
  • It checks the restrictions of each element against the session state (Current Local Time, Session Duration, Day of Week).
  • The first matching Element is selected.

3. Price Component Application

Once an element is active, its price_components are applied to the period's dimensions:

  • FLAT: Applied once per session (the first time a matching Flat component is encountered).
  • ENERGY: period.volume (kWh) × price.
  • TIME: period.duration (hours) × price.
  • PARKING_TIME: Applied if the CDR explicitly logs parking time or if logic determines the session is in a parking state.

4. Step Size Smoothing

To ensure billing accuracy according to tariff rules:

  • Raw usage (seconds or Wh) is aggregated per dimension.
  • Step Size Logic: At the end of the calculation (or where specified), the total duration/energy is rounded up to the nearest step_size multiple.
  • Note: As per OCPI rules, if both TIME and PARKING_TIME are present, step size logic usually prioritizes the total parking duration for the parking component.

Installation

pip install ocpi-tariffs

(Note: Once published to PyPI. For now, install via git)

pip install git+ssh://git@github.com/Hamza-nabil/ocpi-tariffs-py.git

Usage

Basic Calculation

from decimal import Decimal
from datetime import datetime
from ocpi_tariffs.v2_2_1.models import Cdr, Tariff
from ocpi_tariffs.v2_2_1.tariff_calculator import calculate_cdr_cost

# 1. Define a Tariff
tariff_data = {
    "id": "tariff-1",
    "currency": "EUR",
    "elements": [
        {
            "price_components": [
                {"type": "ENERGY", "price": "0.50", "step_size": 1}
            ]
        }
    ],
    "last_updated": "2024-01-01T00:00:00Z"
}
tariff = Tariff(**tariff_data)

# 2. Define a CDR (Charging Session)
cdr_data = {
    "id": "cdr-1",
    "start_date_time": "2024-01-01T12:00:00Z",
    "end_date_time": "2024-01-01T13:00:00Z",
    "currency": "EUR",
    "cdr_location": {
        "id": "loc-1",
        "country": "NLD", # Essential for correct Timezone calculation
        "coordinates": {"latitude": "52.3", "longitude": "4.9"}
    },
    "charging_periods": [
        {
            "start_date_time": "2024-01-01T12:00:00Z",
            "dimensions": [
                {"type": "ENERGY", "volume": "10.0"} # 10 kWh
            ]
        }
    ],
    "total_energy": "10.0",
    "total_time": "1.0",
    "last_updated": "2024-01-01T13:00:00Z"
}
cdr = Cdr(**cdr_data)

# 3. Calculate Cost
price = calculate_cdr_cost(cdr, tariff)

print(f"Total Cost: {price.excl_vat} {tariff.currency}")
# Output: Total Cost: 5.00 EUR

Development

This project uses ruff for linting and mypy for strong typing.

  1. Install dependencies:

    pip install -e .
    pip install ruff mypy pytest types-python-dateutil
    
  2. Run Tests:

    pytest
    
  3. Code Check:

    ruff check .
    mypy .
    

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

ocpi_tariffs-0.1.0.tar.gz (4.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

ocpi_tariffs-0.1.0-py3-none-any.whl (4.8 kB view details)

Uploaded Python 3

File details

Details for the file ocpi_tariffs-0.1.0.tar.gz.

File metadata

  • Download URL: ocpi_tariffs-0.1.0.tar.gz
  • Upload date:
  • Size: 4.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for ocpi_tariffs-0.1.0.tar.gz
Algorithm Hash digest
SHA256 92c88eb18d1a4b4a330a3e8cd0f2b18b107e80789ca4214ce5b13c9dcd84ceb5
MD5 ff38457d48c4438aa3e0f676fb8f8046
BLAKE2b-256 548225eb3a95c03b4f86825f6dd6dc95ad3b6e0d9f446b43479df019dd26c261

See more details on using hashes here.

File details

Details for the file ocpi_tariffs-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: ocpi_tariffs-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 4.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for ocpi_tariffs-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 97a7fdd26d1c1b988b85f81fded94946b5b3f679f268ab7baee7c8e00fbcc97c
MD5 dbba272a84e7cd2a0e4181fcc7cc14df
BLAKE2b-256 75d643d44143074bf1d10a86c26a30db8fe4de9b27315b13106af1357f62631a

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page