1 Innovations in Electric Vehicle Charging EV Infrastructure Project: Open Charge Point Protocol (OCPP) Prepared for: Project Knowledge Dissemination Workshop February 22, 2018 Presented by: Kelly Carmichael, Smart Microgrid Applied Research Team
2 OCPP: What Is It? It is an Open Protocol that runs between charging stations and the Network Operator Greenlots Driivz SemaConnect (End of March) Chargepoint (stated they would be OCPP 2.0) AddEnergie Protocol designed and maintained by the Open Charge Alliance Free to Implement Royalty Free use To provide a common framework to allow multiple vendors equipment to be used with a single backend solution.
3 OCPP: Why Should I Care? Problems Addressed: No single EVSE Vendor has a solution that fits for all purposes Vendor selection criteria changes over time What if your preferred vendor goes out of business What if your preferred vendor is now doing a poor job What if your vendor s business objectives don t match your needs Benefits: Enables moving to a new Network Provider Potential integration with Building Management Systems and Utility Demand Response Establishes a common platform enabling larger integration in the future
4 OCPP 1.5 vs OCPP 1.6J OCPP 1.5 SOAP (Simple Object Access Protocol) Disconnected operation 2 way connections required OCPP 1.6J JSON over Websockets (JavaScript Object Notation) Fully Connected (TCP/IP) 1 way connections (firewall friendly) Faster detection of outage
5 1.5 Messages versus 1.6J Messages OCPP 1.5 Message (1300 bytes): <S:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"> <S:Header> <chargeboxidentity xmlns="urn://ocpp/cs/2012/06/">uid=1013,o=solardev</chargeboxidentity> <To xmlns="http://www.w3.org/2005/08/addressing" OCPP 1.6J Message (109 bytes): [3,"130",{ "chargepointvendor": "BCIT", "chargepointmodel": "OpenOCPP1.0", "chargepointserialnumber": "1" }] >http://localhost:9000/steve/services/centralsystemservice</to> <Action xmlns="http://www.w3.org/2005/08/addressing">/bootnotification</action> <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://www.w3.org/2005/08/addressing/anonymous</Address> </ReplyTo> <MessageID xmlns="http://www.w3.org/2005/08/addressing" >uuid:f86a3b23-5db3-4260-ab21-d72348da5ecc</messageid> <From xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://192.168.1.44:8680/ocpp/v15</Address> </From> </S:Header> <S:Body> <bootnotificationrequest xmlns="urn://ocpp/cs/2012/06/"> <chargepointvendor>solarnetwork</chargepointvendor> <chargepointmodel>solarnode</chargepointmodel> <chargepointserialnumber>155</chargepointserialnumber> <firmwareversion>0.1.0</firmwareversion> </bootnotificationrequest> </S:Body> </S:Envelope>
6 OCPP Profiles Core Firmware Management Local Auth List Management Reservation Smart Charging Remote Trigger
7 OCPP: What Has BCIT Done? Developed an OCPP 1.6J Ecosystem: Backend Server Client code to help vendors implement OCPP on their charging stations User Portal Administration Panel Plugshare integration for Sending Live Station Status PCI Compliant Payment Processing Check-In Terminal Bring Your Own RFID demonstration Making it available to all for use for FREE, with no restrictions Not everybody wants charging stations with a lifetime of SaaS fees. Private fleets still want analytics of charging data Stratas may only want to apportion utility costs to the residents and SaaS is overkill for them. Available for download shortly after project completion
8 OCPP: Customer Portal Features: View Charge History Manage Preferences Associate Vehicle to RFID Map of Charging locations Start Charge from the App Reserve a charging station PCI Payment integration (Stripe.com) Written in PHP to allow web developers to reskin the portal
9 OCPP: Admin Panel Features: Reporting Manage Charging Stations Manage Customers Map of Charging locations Live Charging Data / Status of Stations Send Commands to OCPP charging stations
10 OCPP: Client Features: Written in C for portability and deployment on small hardware Small footprint Physical device integration separate from OCPP code Deployed Hardware using client code: 6 Clipper Creek CS40 EVSE 1 Schneider V0.9 DCFC
11 OCPP: Server Code Features: Written in C for speed and scalability Business logic is all handled via SQL stored procedures Integrators only need SQL expertise if the current business logic needs to be adjusted Current Clients: 6 Clipper Creek CS40 1 Schneider DCFC 1 Efacec DCFC Pending Clients: 1 Efacec L2 EVSE 1 BTC Power DCFC
12 OCPP: Payment PCI Compliance Current Network Providers: Many are not familiar with payment card industry compliance Think that the credit card data is only on their server for a second or two is fine BCIT Solution: Integrated Stripe.com payments We never see any credit card information
13 Payment for Charging Q: If in future there was a fee associated with the EV parking, what do you think is a fair price for the public to pay for use of a charging station ($/per hour)? Less than $1h/hr $2/hr $3/hr $4/hr $5/hr More than $5/hr I don't know 105 90 23 4 1 3 82 0 20 40 60 80 100 120
Q&A 14