OCPP - laedc.org · About me • The Hague University of Applied Sciences • Technical University...

OCPP From concept to standard

About me

• The Hague University of Applied Sciences

• Technical University Eindhoven, EESI System Architecture

• Working since 1997 in IT consultancy and embedded systems

Logica (ICS), Philips, NXP, ASML

• Involved in Charging Solutions since 2009

Alfen, E-Laad

• 42/20/10/4

© ABB Group March 13, 2013 | Slide 3

Evolving EV Market Segmentation

OCPP

What is OCPP

Terminology: Interoperability or Roaming

• Roaming, for end user • Authorization • Billing

• Interoperability, for network operators • Multi-vendor networks (best equipment for specific situations) • Choice of service (best fit for needs) • Quality of service (switching without replacing hardware)

OCPP: background

• E-Laad Foundation: Founded by the Dutch utilities to • implement national charging network • study effects of charging/driver behavior on the grid • seek international cooperation

• An open interoperable system, no vendor lock-in • increased flexibility • increased innovation • increased competition • decrease total costs

OCPP principles

• The protocol description is published and can be obtained free of charge

• there are no constraints on the re-use of the standard

• the IP rights to the standard are vested in a not-for-profit organisation, which operates a completely free access policy

• Further development done by consensus in a open and transparent process, where anyone can participate in the development process.

OCPP 2.0 • Release date: July 2013? • Technical team:

• Netherlands: E-Laad, Alfen, Logica, Ihomer, Enexis, The New Motion • Ireland: ESB • Germany: Bosch, EBG, Mennekes, Pro Systems, Siemens, Smartlab • USA: Chargepoint (Coulomb), Greenlots • France: GIR, EDF • Spain: Circontrol, IBIL • Denmark: Clever • Portugal: Critical Software, Petrotec, Efacec, Intelli • United Kingdom: Electromotive • Belgium: E-novates, Laborec • Luxemburg: Estonteco

OCPP 2.0

• Additional business requirements input • Netherlands: Alliander, Vattenfal/Nuon, Plugsurfing • Germany: Parkeon, RWE, Ebee Smart Technologies • France: Schneider Electric • Belgium: GE Energy Management • United Kingdom: Charge Your Car, Mindseed • Turkey: Fullcharger • Greece: Public Power Corporation Greece • Malaysia: Malaysia Green Technology Co

Questions

Fragen

Vragen

Preguntas

问题

質問

вопросы Perguntas

?

Sorular

OCPP in context: involved

• EV Driver

• EV Car sales organizations

• EV Car manufacturers

• EV Equipment manufacturers

• EV Consultants

• Back office suppliers

• Navigation system manufacturers

• Utilities

• National politics

• Municipalities

• Ground owners

• Electricity suppliers

• Other (Journalists, Research institutes, …)

OCPP in context: systems

• Authorization service

• Clearing house

• Service Provider

• Helpdesk

• Grid management

• Navigation System

• User apps

• Service apps

Public network example 1: ESB

• One national utility • one network • Multiple charging station vendors

• Roaming: Northern Ireland • Independent choice station • Same back office

Public network example 2: E-Laad

• 8 utilities working together • One national network • Multiple charge point manufacturers

• National roaming • E-Laad network + local/private networks • Authorization • Charge Detail Records

• International roaming: Germany and Belgium

Private network example: The Hague

• 300 stations

• Main contractor: Alfen

• Sub contractors: BAM, The New Motion

• Local network, national roaming

EU Tender rules

• € 125 000 for public sector supply and service contracts as well as design contests of central government authorities

• € 193 000 for public sector supply and service contracts as well as design contests of other authorities

• € 193 000 for service contracts that are more than 50% state-subsidized • € 387 000 for utility supply and service contracts, including service design

contests • € 4 845 000 for public sector and utility works contracts, as well as for

contracts that are more than 50% state-subsidized and involve civil engineering activities or hospital, sports, recreation or education facility construction

• € 4 845 000 for public works concession contracts

Source: http://en.wikipedia.org/wiki/Government_procurement_in_the_European_Union

OCPP in context: Interfaces

E-Laad

• Organization type: Foundation

• Founders: Tennet, Enexis, Liander, Delta, Rendo, Westland Infra, Endinet, Cogas

• Mission: Implement charging network of 10.000 by end 2013

• Current network: +/- 2000 charge points

Organization

Steering group: • Vision and roadmap • Define work group packages • Consists of main stakeholders • Budget holder • Approve the standard/releases • Handles possible issues

Work group: • Execute work package • Define changes/additions in

detail • Advise steering group • Consist of OCPP specialists

Executive organisation (facilitator): • Organizer of steering group meetings (and prepare meetings) • Independently leading the work group • Writing down the standard and changes (made by the work group) • Executing the helpdesk function • Making a small annual plan • 2 part-time persons from a independent,- or branch organisation

Development process • Steering group (SG) makes inventory of change requests

• SG groups change requests into topics/work group (WG) assignments

• SG publishes topics, time and location for workshop • Interested parties register for active participation, preferably with topic(s) of interest • During workshop final WG’s are formed and assignments carried out, resulting in:

• Concrete solutions for items where consensus has been reached • Hand-back of non-consensus items to SG

• SG evaluates and creates new assignment/WG for non-consensus items

Guidelines for the development process

• Evolutionary: keep it pragmatic: start simple, grow as needed

• Interoperable: Only generic functionality, nothing vendor-specific

• Up-to-date: Keeping track of technological improvements and incorporate them in the protocol

• Transparent: Everything we do, decide and create should be visible and understandable to all

History • October 2009: Start E-Laad foundation • Initial charging stations with proprietary protocol • Definition of open protocol (OCPP) • October 2010: Release OCPP 1.2 • August 2011: First international workshop to define OCPP organisation • June 2012: Release OCPP 1.5 • September 2012: Kick-Off OCPP 2.0 - • April 2013: 2.0 Release candidate 1 • July 2013: 2.0 Final?

OCPPforum.net • Started September 2011 as OCPP.nl • Goals:

• Central point of information • Central location for tools • Forum to ask questions/find anwers

• Membership • 200 members by januari 2012 (kick-off workshop 1.5) • 500 members by September 2012 (kick-off workshop 2.0) • Currently 800+ • Members: See “OCPP in Context: involved”

OCPP 1.2

• Release date: October 2010

• Team: E-Laad, Alfen, Logica (ICS)

• Functionality: next slide

OCPP: 1.2 Functionality

GPRS

Authorize

Boot Notification

Diagnostics Status Notification

Firmware Status Notification

Heartbeat

Meter Values

Start Transaction

Status Notification

Stop Transaction

Change Availability

Change Configuration

Clear Cache

Get Diagnostics

RemoteStartTransaction

RemoteStopTransaction

Reset

Unlock Connector

Update Firmware

OCPP 1.5

• Release date: June 2012

• Team: • Netherlands: E-Laad, Alfen, Logica, IHomer, ABB, The New Motion • Ireland: ESB • United Kingdom: Pod Point • Belgium: BeCharged, E-novates • Germany: Ladenetz Aachen, Smartlab, Siemens, Reewoud, EBG • France: GIR

OCPP: 1.5 Functionality • Authentication/Authorization (white-/grey-/blacklist, delta updates) • Interval meter readings • Reservation & Release • Generic data transfer • Detailed status notification • Get configuration item • Timestamp mandatory in bootnotification • Rejecting StartTransaction • Size firmwareVersion

OCPP 2.0 Functionality

• Smart charging (schedule based charging)

• Pricing (Different tariff plans)

• Transport Mechanisms (Investigate alternatives to SOAP)

• Diagnostics (differentiate between logging and diagnostics)

• Compliancy (Restructure specification for testing, define function groups for functional comparison charging stations)

• Miscellaneous (all other change requests)