Guide

Guidance for operators of recharging points

2025

This guidance provides an overview of the data requirements laid down in Regulation (EU) 2023/1804 of the European Parliament and of the Council of 13 September 2023 on the deployment of alternative fuels infrastructure and repealing Directive 2014/94/EU (hereinafter referred to as the AFIR Regulation) and the extent to which these requirements are supported by the widely used market standard for the exchange of data on recharging points, the Open Charge Point Interface (OCPI).

The decision to use the industry standard OCPI for making data available was taken to ensure standardized data sharing. With the implementation of AFIR across the EU, it is expected that industry standards for data exchange will increasingly be aligned with the requirements set out in AFIR. Moreover, the electric vehicle recharging market is constantly evolving. To ensure that data keeps pace with this development, OCPI should always be implemented in the most recent version, or the version immediately preceding it.

This guidance is primarily addressed to the relevant market actors, namely operators and owners of recharging points, who, pursuant to Article 20 of the AFIR Regulation, are obliged to make data available.

The AFIR Regulation, the Implementing Regulation and OCPI

Article 20(2) of the AFIR Regulation specifies which types of data must be made available. In addition, the European Commission has adopted an Implementing Regulation that sets out in detail how the data referred to in Article 20(2) is to be made available. The Implementing Regulation therefore specifies the static and dynamic data to be made available in greater detail than the AFIR Regulation itself.

This guidance considers OCPI version 2.2.1 (document version 2.2.1-d2) and version 2.3.0. Regarding future versions of OCPI, the EV Roaming Foundation is working on version 3.0. A review version of 3.0 has formed the basis for assessing data in future versions. See https://evroaming.org/ocpi/ for an introduction and further information on OCPI.

Compliance with EU requirements via OCPI

There is no complete alignment between OCPI versions 2.2.1/2.3.0 and the specifications of the Implementing Regulation, but the European Commission expects that OCPI and other relevant standards will over time be updated to match the data specifications in the Implementing Regulation.

Operators of publicly accessible recharging points may therefore make data available via OCPI and, by continuously upgrading to new versions of OCPI, provide data in accordance with the data specifications of the Implementing Regulation.

When comparing the data specifications in the Implementing Regulation with the object descriptions in OCPI, several situations may occur:

  • Data exists in data fields in OCPI
    • There may be a one-to-one correspondence between the data specifications and OCPI
    • It may be necessary to fill in non-mandatory data fields in OCPI
    • There may be substantive correspondence (the content of the data covers the same aspects, but e.g. country codes may be expressed in another format or there may be other enumerations)
  • Data can be derived from data fields in OCPI (e.g. a number can be derived as the number of elements in a list)
  • Data does not exist in OCPI
    • Future versions of OCPI may include the required data.

The Implementing Regulation distinguishes between two levels of data relating to recharging stations and recharging points, as well as two types of data (static data and dynamic data). In the AFIR Regulation, a recharging station is defined as a physical installation with at least one recharging point. A recharging point can serve only one vehicle at a time. The number of recharging points at a recharging station determines how many vehicles can be recharged at the station. The illustration below shows the distinction between what constitutes a station (shown in red) and what constitutes a point (shown in blue).

In OCPI v.2.2.1/v.2.3.0, data is referenced in the Location module, i.e. object structures containing Location, EVSE and Connector objects, as well as data on prices in the Tariff module. In OCPI v.2.2.1/v.2.3.0 there is no distinction between static data and dynamic data, but this is expected to be introduced in version 3.0 together with a number of other changes.

Note that all mandatory data fields in the modules Versions, Credentials, Locations and Tariffs must always be exposed.

Stricter data requirements for OCPI

When using OCPI v.2.2.1/v.2.3.0, a number of stricter data requirements apply compared to the OCPI standard, in order to ensure that the data provided complies with the data requirements specified in the Implementing Regulation. The stricter data requirements for completing data fields compared to the descriptions in the OCPI standard are listed in the tables in this section.

 

Download table

Skema over datatyper

The following stricter requirements apply to the Locations-module:

Location object
Field name OCPI Cardinality Stricter Cardinality Requirement Notes 
postal_code
 Optional (?) Required (1)   
state
 Optional (?) Required (1)   
parking_type
 Optional (?) Required (1) All elements defined in the OCPI list must be allowed as parking_type. 
parking_places
 List of zero or more objects (*) List of at least one object (+) Required from OCPI v.2.3.0 
operator
 Optional (?) Required (1) Name of the operator as shown on the physical installation is provided here. 
owner
 Optional (?) Required (1) Legal name of the operator or owner, as agreed between the operator and the owner. 
opening_times
 Optional (?) Required (1)   
energy_mix
 Optional (?) Required (1)   
help_phone
 Optional (?) Required (1) Required from OCPI v.2.3.0

 

EVSE object
Field name OCPI Cardinality Stricter Cardinality Requirement Notes 
evse_id
 Optional (?) Required (1)   
capabilities
 List of zero or more objects (*) List of at least one object (+) From OCPI v.2.3.0, the list becomes an OpenEnum, to which the following values must be added:
CONTRACT_BASED
AUTOMATIC_AUTHENTICATION
[OTHER]		 
floor_level
 Optional (?) Required (1)   
coordinates
 Optional (?) Required (1)   
physical_reference
 Optional (?) Required (1)   
parking
 List of zero or more objects (*) List of at least one object (+) Required from OCPI v.2.3.0

 

Connector object
Field name OCPI Cardinality Stricter Cardinality Requirement Notes 
max_electric_power
 Optional (?) Required (1)   
tariff_ids
 List of zero or more objects (*) List of at least one object (+)   
capabilities
 List of zero or more objects (*) List of at least one object (+) Required from OCPI v.2.3.0

 

Parking object (Required from OCPI v.2.3.0)
Field name OCPI Cardinality Stricter Cardinality Requirement Notes 
max_vehicle_weight
 Optional (?) Required (1) Required from OCPI v.2.3.0 
max_vehicle_height
 Optional (?) Required (1) Required from OCPI v.2.3.0 
max_vehicle_length
 Optional (?) Required (1) Required from OCPI v.2.3.0 
max_vehicle_width
 Optional (?) Required (1) Required from OCPI v.2.3.0 
roofed
 Optional (?) Required (1) Required from OCPI v.2.3.0 
lighting
 Optional (?) Required (1) Required from OCPI v.2.3.0

 

The following stricter requirements apply to the Tariffs-module:

Tariff object
Field name OCPI Cardinality Stricter Cardinality Requirement Notes 
type
 Optional (?) Required (1)   
min_price
 Optional (?) Required (1)   
max_price
 Optional (?) Required (1)  

Data Specifications from the Implementing Regulation

The data specifications from the implementing regulation are presented below, with an indication of their correspondence to data in OCPI v.2.2.1 / v.2.3.0. The tables are taken from the implementing regulation, which contains the most detailed data specifications.

The table includes several columns, where the grey columns are copied from the implementing regulation. The blue columns indicate how the data can be made available in OCPI v.2.2.1 / v.2.3.0. The reference to OCPI is given in the column “OCPI-v.2.2.1-ds (OCPI v.2.3.0)” and is structured as [object name].[field name]. The last column may contain notes regarding the correspondence.

Table on data types

Tabel A - Static data for publicly accessible recharging and refuelling infrastructure for alternative fuels

OCPI

Number

Type of  alternative fuels infrastructur

Type of data

Data category

Data type

Data level

Description

Data format

v.2.2.1-d2

v.2.3.0

1

Recharging and refuelling infrastructure of alternative fuels

Static

General information

Legal name of the recharging or refuelling point operator or owner

Station

Legal name of the operator responsible for the management and operation of the publicly accessible recharging and refuelling points for alternative fuels, or, in accordance with the arrangements between them, the owner of those points, which provides a recharging or refuelling service to end users, including in the name and on behalf of a mobility service provider.

Discrete value (string/text)

Data field:

Location.owner

 

Remarks:

Legal name of the operator or owner, as agreed between the operator and the owner.
It is only possible to specify one legal name.

Data field:

-||-

 

 

2

Recharging and refuelling infrastructure of alternative fuels

Static

General information

Commercial name of the recharging or refuelling point operator or owner

Station

Commercial name of the recharging or refuelling point operator or, in accordance with the arrangements between them, the owner of those points as it is presented to the public when offering recharging or refuelling services.

Discrete value (string/text)

Data field:

Location.operator

 

Remarks:

Name of the operator as shown on the physical installation.

Data field:

-||-

3

Recharging and refuelling infrastructure of alternative fuels

Static

General information

Number of recharging or refuelling points

Station

Number of recharging points or refuelling points that can be used at the same time in a recharging or refuelling station. An electric recharging point may have one or more connectors, however only one can be used at the same time

Numeric value (number)

Data field:

Location.evses

 

 

Remarks:

The user can derive the numerical value for the number of objects in the list Location.evses

Data field:

-||-

4

Opladnings- og optankningsinfrastruktur for alternative drivmidler

Static

General information

Service support

Station

Information regarding the presence of physical persons attending the recharging or refuelling station.

Discrete value (string/text)

Data field:

N/A

 

 

Data field:

Location.facilities

[SERVICE_SUPPORT]

 

Remarks:

In this version, Facility is an OpenEnum, to which the following value must be added:
SERVICE_SUPPORT

5

Recharging and refuelling infrastructure of alternative fuels

Static

General information

Helpdesk telephone

Station

Telephone number of the helpdesk, managed by the recharging or refuelling point operator or owner, that is readable in the recharging station

Format based on notation applicable to Union telephone numbers containing at least the following elements: Country code complete number including the regional code (if there is one) in one separate block with the starting zero. Extension numbers shall be added with a dash directly after the complete number. No other dashes, spaces or brackets may be used in the helpdesk telephone number.

Data field:

N/A

Data field:

Location.help_phone

 

Remarks:

It is required that the hotline number consists of [country code]-[8-digit phone number]

 

Example:

0045-72545500

 

 

 

 

 

 

 

code (if there is
one) …

 

 

6

Recharging and refuelling infrastructure of alternative fuels

Static

General information

Facilities offering associated services to the user

Station

The recharging or refuelling station has in its immediate surrounding area facilities offering associated services to customers. The following facilities and services shall be reported (yes/no):

—

Roofed recharging or refuelling parking location.

 

—

Illuminated recharging or refuelling parking location.

 

—

Catering service (e.g. food, beverage)

 

—

Bathrooms.

 

—

Resting facilities

 

—

 Other (expressed as free text).

Discrete value (string/text) in list format

Datafelt:

Location.facilities

[RESTAURANT, CAFE, SUPERMARKET, HOTEL, PARKING_LOT, [OTHER]]

 

Remarks:

The above values must be included in the list of facilities if the facilities are present at the location.

 

In this version, it is not possible to provide information about roofing, lighting, standards, toilets, or rest facilities.

Data field:

-||-

 

As well as

 

Location.parking_places

   .roofed

   .lighting

   .standards

 

 

Remarks:

In this version, Facility is an OpenEnum, to which the following values must be added:

TOILET

[OTHER]

7

Recharging and refuelling infrastructure of alternative fuels

Static

Geographic location

Global Navigation Satellite System (GNSS) geographic location information

Station

Latitude and longitude coordinates of the recharging or refuelling station.

Latitude and Longitude coordinated in WGS84 decimal standard.

Data field:

Location.coordinates

 

As well as

 

Location.evse

   .coordinates

Data field:

-||-

 

 

8

Recharging and refuelling infrastructure of alternative fuels

Static

Geographic location

Additional geographic location information

Station

Additional concrete information that may be relevant to reach the recharging or refuelling station in certain situations, such as parking level, parking lot, etc.

Discrete/numeric value (combination of string/text and numeric)

Data field:

Location.parking_type

 

As well as

 

Location.evse

   .floor_level

 

As well as

 

Location.evse

   .physical_reference

 

Data field:

-||-

 

9

Recharging and refuelling infrastructure of alternative fuels

Static

Geographic location

Country

Station

Name of the Member States where the recharging or refuelling station is located.

Format according to standard ISO 3166-1 alpha-2 codes

Data fiedt:

Location.country

 

Remarks:

OCPI leverer I ISO 3166-1 alpha-3 code.

 

Data field:

-||-

10

Recharging and refuelling infrastructure of alternative fuels

Static

Geographic location

Region

Station

Name of the Member States region where the recharging or refuelling station is located, expressed in the nomenclature of territorial units for statistics (NUTS) 1 level

Format according to NUTS-1 geocode standard

Data field:

Location.state

 

Remarks:

NUTS 1 koden for Danmark er DK0.

Data field:

-||-

11

Recharging and refuelling infrastructure of alternative fuels

Static

Geographic location

City or town

Station

Name of the Member States city or town where the recharging station is located. It shall include information on the municipality or stop name (e.g. highway, area) if not directly associated with the city or town.

Discrete value (string/text)

Data field:

Location.city

Data field:

-||-

 

12

Recharging and refuelling infrastructure of alternative fuels

Static

Geographic location

Postal Code

Station

Postal code where the recharging or refuelling station is located, including potential additional identification information attending to the concrete characteristics of the postal code in that location.

Discrete/numeric value (combination of string/text and numeric)

Data field:

Location.postal_code

Data field:

-||-

13

Recharging and refuelling infrastructure of alternative fuels

Static

Geographic location

Adress name

Station

Where relevant, name of the street where the recharging or refuelling station is located, including the number.

Discrete/numeric value (combination of string/text and numeric) indicating the street name followed by the street number

Data field:

Location.address

 

Remarks:

The appearance of the cadastral number is a translation error from the EU. It is recommended that the house number be provided instead.

Data field:

-||-

 

14

Recharging and refuelling infrastructure of alternative fuels

Static

Accessibility

Opening time

Station

Information regarding the time periods when a recharging or refuelling station is open and accessible to the public for recharging or refuelling, where applicable taking into account the time schedules of the building/facility that gives physical access to that recharging or refuelling station.

Discrete/numeric value (combination of string/text and numeric) indicating the weekdays followed by the time ranges when a recharging or refuelling station is open and accessible to the public

Data field:

Location.opening_times

Data field:

-||-

15

Recharging and refuelling infrastructure of alternative fuels

Static

Accessibility

Time zone

Station

Time zone where the recharging or refuelling station is located. This data type shall be used in combination with other data types to ensure that the availability of a recharging or refuelling point is shown correctly and to make reservation possible and accurate.

Format according to standard ISO 8601

Data field:

Location.time_zone

 

Remarks:

It is recommended to use the ISO 8601 standard as the time zone standard instead of the IANA TZ values specified in OCPI.

Data field:

-||-

16

Recharging and refuelling infrastructure of alternative fuels.

Static

Accessibility

Vehicle-type compatibility

Station

Type of vehicle that may use a recharging or refuelling station. The type of vehicle shall be specified in accordance with UNECE vehicle categorisation (1). The following vehicle categories shall be reported (yes/no):

—

Two- and three-wheel vehicles and quadricycles (L)

 

—

Passenger cars (M1)

 

—

Buses and coaches (M2 or M3)

 

—

Vans (N1)

 

—

Trucks (N2 or N3)

 

—

Other (expressed as free text)

 

 

 

 

 

Discrete/numeric value (combination of string/text and numeric) in list format

Data field:

N/A

Data field:

Location.parking_places

   .vehicle_types

 

As well as

 

Location.evse.parking

   .parking_id

 

Remarks:

Location.parking_places contains a list of Parking objects, each of which includes a list of vehicle types for the given parking space.

17

Recharging and refuelling infrastructure of alternative fuels

Static

Accessibility

Vehicle specifications permitted

Station

Where relevant, specific limitations to the mass and dimensions of vehicles (including trailers, semi-trailers, etc.) (2), allowed to access the recharging or refuelling station. The following vehicle specifications, including trailers, shall be reported (yes/no):

—

Maximum vehicle mass.

 

—

Maximum vehicle height.

 

—

Maximum vehicle length.

 

—

Maximum vehicle width.

Discrete/numeric value (combination of string/text and numeric) indicating maximum vehicle mass in tonnes and maximum vehicle height, length and width in metres, including trailer.

Data field:

N/A

Data field:

Location.parking_places

   .max_vehicle_weight

   .max_vehicle_height

   .max_vehicle_length

   .max_vehicle_width

 

Remarks:

Capable of converting from centimeters and kilograms to meters and metric tons

18

Recharging and refuelling infrastructure of alternative fuels

Static

Accessibility

Number of parking spaces

Station

Number of parking spaces that may be used at a recharging or refuelling station to conduct a recharging or refuelling session. It may be different to the number of recharging or refuelling points of that station.

Numeric value (integer number

Data field:

N/A

Data field:

Location.evse.parking

 

Remarks:

The implementation can derive the number of parking spaces for charging from the number of Parking objects in Location.evse.parking

19

Recharging and refuelling infrastructure of alternative fuels

Static

Accessibility

Number of parking spaces for people with disabilities

Station

Number of parking spaces with accessible recharging or refuelling points for people with disabilities in compliance with relevant accessibility requirements defined in existing standards, guidelines or national legislation.

Numeric value (integer number

Data field:

Locations.evse

   .parking_restrictions

    [DISABLED]

 

Remarks:

The number is not directly available in OCPI, but it can be derived from the number of EVSEs where the parking_restriction is 'DISABLED'.

Data field:

-||-

 

As well as

 

Location.parking_places

   .vechicle_type

    [DISABLED]

&

   Standards

 

Remarks:

In OCPI v.2.3.0, the number can also be derived from the number of Parking objects in Location.parking_places with the vehicle type 'DISABLED' and standards indicating accessibility for persons with disabilities.

20

Recharging and refuelling infrastructure of alternative fuels

Static

Payment options

Payment device with bank card reader

Station

Indication on the existence (yes/no) of a payment terminal with the ability to enable the bank card (debit/credit) to be physically inserted in the terminal for the Europay, Mastercard and Visa (EMV) chip to be read.

Discrete value (string/text)

Datafelt:

Locations.evse

   .capabilities

 

Remarks:

The following OCPI options must be able to be included in the list:

-          CHIP_CARD_SUPPORT

-          CREDIT_CARD_PAYABLE

-          DEBIT_CARD_PAYABLE

-          PED_TERMINAL

Data field:

-||-

 

infrastructure of alternative fuels

 

 

 

 

in the terminal for the Europay, Mastercard and Visa (EMV) chip to be read.

 

 

 

21

Recharging and refuelling infrastructure of alternative fuels

Static

Payment options

Payment device with a contactless functionality that is at least able to read payment cards

Station

Indication on the existence (yes/no) of a payment terminal that is at least able to read bank cards (debit/credit) with a contactless functionality (e.g. Near Field Communication – NFC).

Discrete value (string/text)

Data field:

Locations.evse

   .capabilities

 

Remarks:

The following OCPI options must be able to be included in the list:

-          CONTACTLESS_CARD_SUPPORT

-          CREDIT_CARD_PAYABLE

-          DEBIT_CARD_PAYABLE

Data field:

-||-

22

Recharging and refuelling infrastructure of alternative fuels

Static

Payment options

Other ad hoc payment option

Station

Indication on the existence (yes/no) of the following ad hoc payment options:

—       Specific (i.e. dynamically generated) QR code

—       Payment through a website (e.g. static QR code)

—       Cash

—       Other (expressed as free text)

Discrete value (string/text)

Data field:

N/A

Data field:

-||-

 

23

Recharging and refuelling infrastructure of alternative fuels

Static

Payment options

Additional information about payment providers accepted

Station

Additional information indicating the payment service providers that accept electronic payments in the ad hoc payment option.

Discrete value (string/text) in list format

Data field:

N/A

Data field:

-||-

 

24

Recharging and refuelling infrastructure of alternative fuels

Static

Payment options

Contract-based (subscription) payment option

Station

Possibility to pay for a recharging or refuelling service on the basis of a contract-based payment (yes/no) between the end user and the mobility service provider.

Discrete value (string/text)

Data field:

N/A

Data field:

Location.evse

  .accepted_service_providers

 

As well as

 

Location.evse.capabilities

 

Remarks:

The implementation can derive payment options from lists of service providers with contract-based payment options on EVSE objects – the lists may be empty.

In this version, Capability is an OpenEnum, to which the following value must be

added:
CONTRACT_BASED

 

 

Tabel B - Further static data for publicly accessible recharging infrastructure

OCPI

Number

Type of alternative fuels infrastructure

Type of data

Data category

Data type

Data level

Description

Data format

v.2.2.1-d2

v.2.3.0

1

Electric recharging infrastructure

Static

General information

Recharging Point ID code (Connector)

Point

Unique ID of the recharging point, which includes the unique ID code of the recharging point operator issued by the IDRO (ID Registration Organisation). It supports the identification, including for billing and booking purposes, of the recharging point within a recharging station.

Discrete/numeric value (combination of string/text and numeric)

Data field:

Location.evse

   .evse_id

Data field:

-||-

2

Electric recharging infrastructure

Static

General information

Number of connectors

Punkt

Number of connectors in a recharging point. An electric recharging point may have one or more connectors, however only one can be used at the same time.

Numeric value (integer number)

Data field:

Location.evse

   .connectors

 

Remarks:

The implementation can derive the numerical value of the number of objects in the list of Connector objects.

 

Data field:

-||-

3

Electric recharging infrastructure

Static

General information

Type of connector (plug)

Point

Identification of connectors available in each recharging point within a recharging station:

—

Type 2 (AC)

 

—

Combo 2/CCS (DC)

 

—

Megawatt Charging System (MCS)

 

—

CHAdeMO (DC)

 

—

Other (expressed as free text)

Discrete value (string/text) in list format

Data field:

Location.evse.connectors

   .standard

 

Remarks:

Note that the types do not exist directly in OCPI as noted in AFIR. ConnectorType must at a minimum consist of

- CHADEMO

- TYPE_2

- COMBO2_CCS

- MCS

 

Data field:

-||-

 

Remarks:

ConnectorType is an OpenEnum in this version, to which the following value must be added:
OTHER

4

Electric recharging infrastructure

Static

Type of current

Type of current

Point

Type of electric current flow delivered at the recharging point, differentiating between alternating current (AC) or direct current (DC)

Discrete value (string/text) differentiating between AC and DC

Data field:

Location.evse.connectors

   .power_type

 

Data field:

-||-

 

5

Electric recharging infrastructure

Static

Power output

Recharging station maximum power

Station

Total maximum power that the recharging points of the station can provide at the same time.

Numeric value (number) expressed in kW

Data field:

N/A

 

Data field:

-||-

 

 

 

 

 

 

 

 

 

 

I OCPI 3.0 forventes Location.max_power tilføjet.

6

Electric recharging
infrastructure

Static

Power output

Recharging point maximum
power

Point

Maximum power that can be provided by the recharging point to the electric vehicle at a given time.

Numeric value (number)
expressed in kW

Data field:

Connector.max_electr ic_power

Data field:

-||-

7

Electric recharging infrastructure

Static

Payment options

Mobility service providers offering contract-based
recharging

Station

Information indicating the name of those mobility service providers that are offering contract-based payment options and are accepted in a recharging station.

Discrete value (string/text) in list format

Data field:

N/A

Data field:

Location.evse

   .accepted_service_providers

 

As well as

 

Location.evse.capabilities

 

Remarks:

Capability is an OpenEnum in this version, to which the following value must be added:
CONTRACT_BASED

8

Electric recharging infrastructure

Static

Automatic authentication

Plug-and-charge

Point

Possibility of conducting automatic authentication and authorisation of the recharging session on the basis of a contract-based payment concluded between the end user and the mobility service provider (yes/no) in a recharging point.

Discrete value (string/text)

Data field:

N/A

Data field:

Location.evse.capabilities

 

Remarks:

Capability is an OpenEnum in this version, to which the following value must be added:
AUTOMATIC_AUTHENTICATION

 

 

9

Electric recharging infrastructure

Static

Smart recharging functionalities

Smart recharging services

Point

Possibility of using smart recharging services in a recharging point. The possibility of using the following smart recharging services must be indicated (yes/no):

 

—       Remote monitoring and control recharging.

—       User preference configuration for recharging power optimisation.

—       Bidirectional recharging.

—       Other (expressed as free text)

 

 

Discrete value (string/text)

Data field:

N/A

Data field:

-||-

10

Electric recharging infrastructure

Static

Renewable electricity

Electricity supplied is 100 % renewable

Station

The recharging station exclusively supplies 100 % renewable electricity (yes/no) (EU Guarantee of Origin (GO) scheme).

Discrete value (string/text)

Data field:

Location.energy_mix

   .is_green_energy

 

Data field:

-||-

 

 

Tabel F - Dynamic data for publicly accessible recharging and refuelling infrastructure for alternative fuels

OCPI

Number

Type infrastruktur for alternative drivmidler

Type of data

Data category

Data type

Data level

Description

Data format

v.2.2.1-d2

v.2.3.0

1

Recharging and refuelling infrastructure of alternative fuels

Dynamic

Functionality

Operational status

Point

Capability of the recharging or refuelling point to perform its function. The operational status of a recharging or refuelling point expressed as operational or non-operational:

—       Operational: it can be used in normal conditions during the opening time that is accessible to the public.

—       Non-operational: it cannot be used due to a technical problem or maintenance works.

Discrete value (string/text) expressed as operational or non-operational

Datafelt:

Location.evse.status

 

Remarks:

Values defined in OCPI do not directly reflect the description in AFIR.

 

All values defined in OCPI for status shall be used as possible values.

 

Data field:

-||-

 

 

2

Recharging and refuelling infrastructure of alternative fuels

Dynamic

Functionality

Availability

Point

Possibility to use a recharging or refuelling point at present time and, when technically possible, at a specific future time, The availability of a recharging or refuelling point expressed as in use, reserved or not in use:

 

 

 

—       In use: it is occupied

—       Reserved: it is booked by an end user

—      Not in use: it is non-occupied, thus available for use

Discrete value (string/text) expressed as in use, reserved or not in use

Data field:

Location.evse.status

 

Remarks:

Values defined in OCPI do not directly correspond to the description in AFIR.

 

 

3

Recharging and refuelling infrastructure of alternative fuels

Dynamic

Price

Ad hoc-price

Station

For recharging infrastructure, indication of the end user price for recharging on an ad hoc basis, including all applicable price components. These must be indicated and expressed in national currency per kWh, national currency/min, or national currency/session. Any other price component that may apply in addition must be equally indicated.

 

For refuelling infrastructure, indication of the end user price for refuelling on an ad hoc basis, expressed in national currency per kg of fuel.

Discrete/numeric value (combination of string/text and numeric) in list format expressed for recharging infrastructure in national currency per kWh, national currency/min, or national currency/session and for refuelling infrastructure in national currency per kg of fuel.

 

National currencies shall be expressed according to ISO 4217, which establishes internationally recognised codes for the representation of currencies.

Data field:

Tariff

   .type

   .min_price

   .max_price

 

Tariff.elements

   .price_components

   .restrictions

   

 

Location.evse.connectors

   .tariff_ids

 

Remarks:

Information on the connector about tariffs (Connector.tariff_ids) refers to Tariff objects from the Tariff module, which can have the tariff type "AD_HOC_PAYMENT" in Tariff.type.

 

If Tariff.type is not specified, the tariff applies to all sessions.

Data field:

-||-

 

Remarks:

Note: In OCPI 3.0, Tariff Associations are expected to be introduced as an object.