Intro Restricted Access
As a charger operator, you must publish your roaming Locations. But when there are restrictions, you want to inform drivers on forehand.
E.g. as a Hotel you want to indicate that Charge Stations can be used by Hotel guests, but not by the rest of the public, a Charge Station can be located behind a barrier at an office side.
Portal
Permission Levels needed: only users with permissions to update or create location will be able to edit/create these fields
Roaming protocols
Although in both OCPI and OICP roaming protocol there are options to define Restricted Access it really depends on the implementation of EMSPs what they do with the provided information.
OCPI
In OCPI, there are so called 'Parking Restrictions'.
GreenFlux maps the Location property 'Restricted Access' to the 'CUSTOMERS' restriction on Evse level. This is agreed within e-Violin (eViolin – Solid foundation for public accessibility of charging infrastructure for electric driving).
OICP
In OICP protocol we use top 2 options. Second one in case Restricted Access is enabled.
Charge Assist
This is how Charge Assists shows Restricted access:
*Charge Assist is the Mobile Application and API by Greenflux.
Platform API
LocationsV1
Works similar as OCPI.
LocationsV2
Via 'acces_type' you can choose 'PUBLIC' when no Restricted Access is applicable and 'RESTRICTED' when it is.
The parking_restriction 'CUSTOMER' is assigned to Evses when Location has access_type 'RESTRICTED'
Portal Published | Portal Restricted Access | API publish | API access_type |
Yes | No | true | PUBLIC |
Yes | Yes | true | RESTRICTED |
No | N/A | false | PRIVATE |