Skip to main content

Technical requirements

Stadler Sofia
  • Updated

The 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.

OCPI

Plugsurfing is currently supporting OCPI 2.1.1-d2.

General

Plugsurfing

Requirements

OCPI version

2.1.1-d2

 

 

 

 

Registration / Credentials Module

Initiation of registration can be done by any of the parties

 

Get FromEMP versions

Supported

 

Get FromEMP endpoints (for a specific version)

Supported

 

Get ToEMP versions

Supported

 

Get ToEMP endpoints (for a specific version)

Supported

 

POST FromEMP credentials

Supported

 

POST ToEMP credentials

Supported

 

PUT FromEMP credentials

Supported

 

PUT ToEMP credentials

Supported

 

DELETE FromEMP credentials

Supported

 

DELETE ToEMP credentials

Supported

 

 

 

 

Locations Module

 
  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 Territory.
  4. The Charging Infrastructure Data for a Charging Station must be submitted prior to any Charging Session at this Charging Station.

PUT ToEMP locations (location)

Supported

  

PUT ToEMP locations (evse)

Supported

  

PUT ToEMP locations (connector)

Supported

  

PATCH ToEMP locations (location)

Supported

  

PATCH ToEMP locations (evse)

Supported

  

PATCH ToEMP locations (connector)

Supported

  

Get FromEMP locations (i.e., EMP gets location from our platform)

Not supported

Can be supported if necessary

Get ToEMP locations (location) (i.e., our platform gets location from EMP)

Not supported

 

Get ToEMP locations (evse)

Not supported

 

Get ToEMP locations (connector)

Not supported

 

 

 

 

Tokens Module

 

 

Get ToEMP Tokens (list)

Supported

 

PUT FromEMP Tokens (creation/update)

Supported

 

PATCH FromEMP Tokens (update)

Not supported

 

POST ToEMP Tokens (real time auth)

Supported

 

 

 

 

Sessions Module

 

 

PUT ToEMP sessions

Not supported

 

PATCH ToEMP sessions

Not supported

 

GET ToEMP sessions

Not supported

 

 

 

 

Commands Module

 

 

POST FromEMP commands (START_SESSION)

Not supported

 

POST FromEMP commands (STOP_SESSION)

Not supported

 

POST FromEMP commands (RESERVE_NOW)

Not supported

 

POST FromEMP commands (UNLOCK)

Not supported

 

 

 

 

CDRs Module

 
  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 is white-listed at the time of initiating the Charging Session, regardless if the authorization was real-time or not.
  5. The CDR shall be associated with any Charging Station.
  6. The CDR shall refer to Charging Infrastructure Data.
  7. The Charging Infrastructure Data for a Charging Station must be submitted prior to any Charging Session at this Charging Station.
  8. The CDR shall refer to a positive (zero or higher) energy consumption, price and session time;

POST ToEMP CDRs

Supported

 

GET ToEMP CDRs

Not supported

 

 

 

 

Tariffs Module

Currently not supported:

Component:

●       PARKING_TIME

Restrictions:

●       Min_power

●       Max_power

●       Start_date

●       End_date

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

PUT ToEMP Tariffs 

Supported

 

PATCH ToEMP Tariffs

Supported

 

GET FromEMP Tariffs

Not supported

 

 

OIOI

Plugsurfing is currently supporting OIOI. New integrations are only done through OCPI.

Specifications:

https://docs.plugsurfing.com/

Create a ticket to request credentials.

 

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
  • Czechia
  • Denmark
  • Finland
  • France
  • Germany
  • Hungary
  • Iceland
  • Ireland
  • Italy
  • Latvia
  • Liechtenstein
  • Luxembourg
  • Netherlands
  • Norway
  • Poland
  • Romania
  • Slovakia
  • Slovenia
  • Spain
  • Sweden
  • Switzerland
  • UK

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. Plugsurfing can then validate if the Token is allowed to be used at the specified location. 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