Skip to main content

Technical requirements

Stadler Sofia
  • Updated

Plugsurfing officially support version 2.1.1-2d of the OCPI protocol (Github link)

These Technical Requirements are subject to change. The CPO shall check these technical requirements regularly for updates. If major updates are done, Plugsurfing will inform the CPOs with one month's notice.

Registration / Credentials Module (Required):

Initiation of registration can be done by any of the parties

Issuing party Commands Status
CPO POST credentials Supported
PUT credentials Supported
DELETE credentials Supported
GET versions Supported
GET endpoints (for a specific version) Supported
EMP POST credentials Supported
PUT credentials Supported
DELETE credentials Supported
GET versions Supported
GET endpoints (for a specific version) Supported

 

Locations Module (Required):

  1. The Charging Infrastructure Data shall contain all information required in accordance with the Protocol.

  2. The Charging Infrastructure Data submitted by the CPO to Plugsurfing must be accurate, valid, complete, unique and consistent.

  3. The Charging Infrastructure must be located within the operating Territories.

  4. The Charging Infrastructure Data for a Charging Station must be submitted prior to any Charging Session at this Charging Station.

Request Issuing party Commands Status
Push CPO PUT locations Supported

PUT EVSE

 Supported

PUT locations

 Supported
PATCH locations (Patch call will only patch properties on the Location, child EVSEs and connectors will not be updated.) Supported
PATCH locations (Patch calls will only patch properties of the EVSE, child connectors will not be updated.) Supported
PATCH locations (connector) Supported
Pull CPO GET locations (i.e., CPO gets location from our platform) Not supported
EMP GET locations (location) (i.e. our platform gets location from CPO) Supported

 

Tokens Module (Required):

CPO shall use Realtime Authentications when their system is online.

Request Issuing party Commands Status
Push EMP PUT Tokens (creation/update) Supported
PATCH Tokens (update) Not supported
Pull CPO Get Tokens (list) Supported

 

Charge Detailed Records (CDR) (Required):

  1. The CDR shall be transmitted immediately, no longer than one hour, after the end of Charging Session.

  2. The CDR shall contain all information required in accordance with the Protocol version.

  3. The CDR submitted by the CPO to Plugsurfing must be unaltered, complete and correct.

  4. The CDR shall be associated with a Customer who was Authorized in Real Time only.

  5. The Charging Infrastructure Data for a Charging Station must be submitted prior to any Charging Session at this Charging Station.

  6. The CDR shall refer to a positive (zero or higher) energy consumption, price and session time.

Request Issuing party Commands Status
Push CPO POST CDRs Supported
Pull EMP GET CDRs Supported (Not preferred)

Component not supported currently : PARKING_TIME

 

Tariffs Module (Optional):

If Tariffs Module is not supported, the standard Fees for charging will apply: https://partnersupport.plugsurfing.com/hc/en-us/articles/360021089838-Fees

Restrictions:

  • Min_power

  • Max_power

  • Start_date

  • End_date

Request Issuing party Commands Status
Push CPO PUT Tariffs Supported
PATCH Tariffs Supported
Pull CPO GET Tariffs Not supported
EMP GET Tariffs Supported

 

Sessions Module (Optional*):

Request Issuing party Commands Status
Push CPO PUT sessions Supported
PATCH sessions Supported
Pull CPO GET sessions Not supported
EMP GET sessions Not supported

* This is required if remote start/stop is to be used.

 

Commands Module (Optional):

Issuing party Commands Status
EMP POST commands (START_SESSION) Supported
POST commands (STOP_SESSION) Supported
POST commands (RESERVE_NOW) Not supported
POST commands (UNLOCK) Not supported

 

Territory

Territory means the geographical area which this Agreement covers, and within which all Charging Stations must be located. The definition of the Territory is subject to changes provided that Plugsurfing will notify per email of any upcoming change one (1) month prior to any change. The geographical area included in the Territory is:

    • Austria
    • Belgium
    • Croatia
    • Czech Republic
    • Denmark
    • Estonia
    • Finland
    • France
    • Germany
    • Hungary
    • Iceland
    • Ireland
    • Italy
    • Latvia
    • Liechtenstein
    • Lithuania
    • Luxembourg
    • Netherlands
    • Norway
    • Poland
    • Romania
    • Slovakia
    • Slovenia
    • Spain
    • Sweden
    • Switzerland
    • United Kingdom

Territory can also be enforced by usage of real-time authorization for local starts initiating a Charging Process, and LocationReferences object in the request body

If the start request is denied, the CPO shall not allow the user to charge. If a session is started by the CPO when Plugsurfing has rejected the session start request, Plugsurfing has the right to reject the CDR.

 

Related articles