[OASIS Issue Tracker] (OCPP-72) CR: Car Sharing

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OCPP-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64493#comment-64493 ] 

Robert de Leeuw commented on OCPP-72:
-------------------------------------

Based on the input received from different sources (including the OCA Car Sharing Call)
There seems to be no need to write a CR for Car Sharing.

There are 3 scenarios identified:
1: Closed community car sharing (Family, Neighborhood, etc) 
2: Car Rental
3: Company Car (is this different from 1?)

For scenario 1 & 3 the current OCPP 1.6 ParentId (will be GroupId in 2.0) will work.
We shortly discussed if we needed to allow multiple ParentIds per IdToken (RFID Token).
Seems useful, but in the real world a driver that uses both a Closed Community and a Company Car will receive an RFID Card from each service, because it is much easier to handle for the companies and also helps with branding.

For scenario 2 we discussed if we need a way to allow a different driver to stop a transaction then the person that started the transaction.
Most cars now unlock the connector (car-side) when you unlock the car. This enables the driver to stop the transaction by unplugging the cable car side. No need to stop the transaction another way.
When a rental car is returned, it needs to be returned to the rental company. An employee does a quick check of the EV and parks it, the employee can plug the car in (use his RFID card to start charging.)
The rental company wants to have as much charge available as possible, for this reason we think a rental company never will allow a non-rental car to charge at one of there own charge points.

bigger car sharing programs (like GreenWheels in the Netherlands) have there own parking-spaces. You have to return the car to this parking spot.
If such a car is an EV, they you don't want another car to be charging at such a parking-space. Such an EV could be recognized via 15118 Plug-n-Charge. If 15118 is not available, the user could use his own RFID to start the charging session. Stopping could be the same as in scenario 2.


> CR: Car Sharing
> ---------------
>
>                 Key: OCPP-72
>                 URL: https://issues.oasis-open.org/browse/OCPP-72
>             Project: OASIS OCPP Electric Vehicle Charging Equipment Data Exchange TC
>          Issue Type: Task
>         Environment: New ideas (OCA list)	
>            Reporter: Jonel Timbergen
>            Assignee: Jonel Timbergen
>            Priority: Trivial
>
> Organize a call about Car sharing, how can we solve this?	



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)