OASIS members & interested parties,
A new OASIS technical committee is being formed. The OASIS Charge Point Protocol (OCPP) Technical Committee (TC) has been proposed by the members of OASIS listed in the charter below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode and language specified in this proposal will constitute the TC's official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's first meeting.
The eligibility requirements for becoming a participant in the TC at the first meeting are:
(a) you must be an employee or designee of an OASIS member organization or an individual member of OASIS, and
(b) you must join the Technical Committee, which members may do by using the Roster "join group: link on the TC's web page at [a].
To be considered a voting member at the first meeting:
(a) you must join the Technical Committee at least 7 days prior to the first meeting (on or before 31 August 2016); and
(b) you must attend the first meeting of the TC, at the time and date fixed below (07 September 2016).
Participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties.
Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC's public home page at [c].
Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation.
CALL FOR PARTICIPATION
OASIS Open Charge Point Protocol (OCPP) Technical Committee Charter
The charter for this TC is as follows.
Section 1: TC Charter
(1)(a) TC Name
OASIS Open Charge Point Protocol (OCPP) Technical Committee (TC)
(1)(b) Statement of Purpose
The OCPP TC will strengthen the electric vehicle (EV) charging infrastructure by bringing the industry together to advance an international standard that will make it possible to connect any OCPP "Central System" (including intermediate or virtual emulators) with any electric vehicle (EV) charging station ("charge point" or "EVSE"), including intermediate or other emulators, regardless of vendor, to assure the uniform, application-level interoperable exchange of EVSE and EV data and control information.
With OCPP, true interoperability and standardized secure interoperation with and connection to charge points will be possible. OCPP standardization will promote innovation and benefit the entire range of stakeholders in the electric vehicle (EV) eco-system:
1) Charge point Owners: Municipalities, businesses, residences, and other charge point owners will have more freedom to choose their Central Management System Suppliers with OCPP. Owners will be able to change and add different suppliers to their network whilst keeping their existing charging stations operational (avoiding stranded assets and vendor lock-ins). Owners will have the flexibility to select suppliers and services based on the best price, quality of service, innovative features, and other criteria of their choosing.
2) Central System Providers and Integrators: With OCPP, providers of central systems can easily integrate charge points from different vendors into their system. This gives Providers the freedom to pick and choose from a pool of vendors and to operate in different countries with different vendors if necessary. Providers can acquire new customers by incorporating the customer's existing charge points into their systems.
3) Charge point vendors: Providers of standard-compliant charge points will be able to easily integrate their charge points with different Central Systems. This enables Providers to sell more products to more customers and gives them the option to join existing charging networks.
4) Electricity Service Providers and System Operators: charge points are an important element in the smart grid. OCPP will allow Electricity Service Providers and/or System Operators to interact with the charging infrastructure and indirectly with aggregated EV loads or supplies by optionally applying transactive energy technologies to address temporary surplus and shortage due to abundance of renewables or other factors.
5) Demand Response (DR) Service Providers and Aggregators: OCPP enables dynamic management of the EV charging station infrastructure as a Demand Response or Distributed Energy Resource for a containing grids or microgrids, giving DR service providers significant value gains. Both transactive and request mechanisms should be supported.
Bringing together representatives of the entire stakeholder community - people with different backgrounds, different needs, different approaches, from different locations around the world - to collaborate on an open protocol is the most reliable way to produce solutions that are cost-effective, diverse, comprehensive, innovative, and scaled to meet the aggressive EV growth strategies.
The OCPP TC will produce specifications that define the functional standards needed for data interoperation between a charge point and central system providers and Integrators. The interoperation includes but is not limited to authorizations, identification, metering, management, resource and consumption availability and needs. The scope is limited to communication between Central System Providers/Integrators and charge points and related necessary information definition.
The starting point will be the contributed OCPP Version 1.6. Other contributions may be made at or after the first meeting of the TC. Such contributions shall be considered by the TC Members on an equal basis to improve the original starting point contribution.
The specifications will address application layer information exchange requirements for alternating current (AC) and direct current (DC) charge points as well as wired and wireless networked charging solutions.
The work product will consist of one or more specifications for information exchange and patterns expressed using XML, a binding to JSON over web sockets, and one or more security profiles. The TC may choose to address other transport bindings as it sees the need. However, the TC will not mandate a specific communication technology beyond requiring TCP/IP connectivity.
The OCPP v2.0 specification shall align, interoperate with, and reuse components, as the TC deems appropriate, with and from relevant IEC, ISO, OASIS, and other standards.
The TC may establish liaisons with relevant standards organizations and committees including IEC TC 57 (power systems), IEC TC 69 (electric road vehicles and electric industrial trucks) and ISO TC 22/SC 31 (data communication) in order to pursue alignment, interoperation with, and adoption of OCPP V2.0 with other related work.
Out of Scope
A non-exhaustive list is provided below for the sake of clarity. If some function, mechanism or feature is not described as Out of Scope, and it is not listed as In Scope in the Scope of Work section, then it will also be considered as Out of Scope.
- The TC will not produce reference implementations of the protocol
- Transports not using TCP/IP connectivity
- Communication details between a charge point and a vehicle
Once the TC has completed work on a deliverable and it has become an OASIS Standard, the TC will enter "maintenance mode" for that deliverable. The purpose of maintenance mode is to provide minor revisions to previously adopted deliverables to clarify ambiguities, inconsistencies and obvious errors. The maintenance mode will not functionally enhance a previously adopted deliverable or extend its functionality. The TC will collect issues raised against the deliverables and periodically process those issues. Issues that result in the clarification or non-substantive correction of the deliverables shall be processed. The TC shall maintain a list of these adopted clarifications and may periodically create a new minor revision of the deliverables including these updates
Using OCPP Version 1.6 as one input, the TC plans to produce specifications for OCPP Version 2.0 within 12 months of its first meeting. Other contributions to the TC will also be considered for incorporation into the specification based on their merits.
The TC will accept as additional input issues and recommended changes from the TC Members and others. Changes to the input document or other contributions will be accepted for consideration without any prejudice or restrictions and evaluated based on technical merit in so far as they conform to this charter.
The work product will consist of one or more specifications for information exchange and patterns expressed using XML, a binding to JSON over web sockets. The TC may choose to address other transport bindings as it sees the need.
Follow-on versions of the specification may be developed to address additional in-scope capabilities identified by the TC on a schedule to be defined by the TC.
Following approval as an OASIS Standard, the TC intends to forward OCPP V2.0 to the IEC.
The TC may produce other non-standards track deliverables within the scope outlined above, such as tutorials or white papers to support the specification.
(1)(e) IPR Mode
The TC will operate under the Non-Assertion IPR mode.
All parties involved in the EV charging infrastructure are strongly encouraged to participate in the OCPP TC:
- EV and EV charge point owners
- Central system providers or system integrators
- E-mobility Service providers and charge point operators
- Charge point vendors
- EV OEMs
- Facility Energy Management Systems and integrators
- Utilities: Electricity service providers and/or distribution network operators
- Microgrid operators
- DR service providers and/or aggregators
- Research institutes and consultancy firms
- Government agencies and regulatory agencies
The OCPP TC will use United States (U.S.) English as the language for conducting its operations.
Section 2: Additional Information
(2)(a) Identification of Similar Work
OCPP in its various deployed versions is a widely used and open specification for this technology area. This effort will formally standardize and building on this de facto standard.
At this time, there is no ongoing or completed work within the International Electro Technical Commission (IEC) on a similar standard. At the appropriate time, the TC will consider forwarding OCPP V2.0 to the IEC for consideration as part of its framework. In support of this, the TC will consider establishing liaisons with relevant standards projects including IEC TC 57 (power systems), IEC TC 69 (electric road vehicles and electric industrial trucks) and ISO TC 22/SC 31 (data communication). The purpose of these liaisons is to support activities such as sharing and discussing with IEC drafts of the OASIS OCPP specification; alignment and interoperation between OCPP 2.0 and the relevant IEC and ISO standards (IEC CIM, IEC 61850 and ISO 15118); and integrating findings into the OASIS OCPP specification.
A working group within the National Electrical Manufacturers Association (NEMA) has planned to develop a standard for EV charging station to Central System communication that may overlap in scope with OCPP. NEMA is a U.S. organization and appears to be focused on the U.S. Market. The OCPP project seeks to create a specification available and suitable for global use.
The IEEE has recently created a new working group with partially overlapping scope with OCPP. Efforts are under way to understand the goals and how that group may leverage the de facto global standard, OCPP. There is no completed work in IEEE.
(2)(b) First TC Meeting
The first TC Meeting will be a teleconference on 07 September 2016 at 15:00 UTC. The Open Charge Alliance will sponsor the teleconference.
(2)(c) Ongoing Meeting Schedule
Online meetings will he held every two weeks. Face-to-Face meetings will be held approximately every six months, alternating between Europe and North America.
(2)(d) TC Proposers
5) Pierre Sacre, Schneider, Pierre.Sacre@Schneider-electric.com
(2)(e) Primary Representatives' Support
I, Lonneke Driessen, Lonneke.Driessen@openchargealliance.org
, as OCA's Primary Representative to OASIS, confirm our support for the OASIS Open Charge Point Protocol (OCPP) Technical Committee charter and the participation of our co-proposers named above.
I, Arjan Wargers, email@example.com
, as Elaad's Primary Representative to OASIS, confirm our support for the OASIS Open Charge Point Protocol (OCPP) Technical Committee charter and the participation of our co-proposers named above.
I, Harmeet Singh, firstname.lastname@example.org
, as Greenlots' Primary Representative to OASIS, confirm our support for the OASIS Open Charge Point Protocol (OCPP) Technical Committee charter and the participation of our co-proposers named above.
I, Brendan McMahon, Brendan.McMahon@ESB.ie, as ESB's Primary Representative to OASIS, confirm our support for the OASIS Open Charge Point Protocol (OCPP) Technical Committee charter and the participation of our co-proposers named above.
I, Pierre Sacre, Pierre.Sacre@Schneider-electric.com , as Schneider's Primary Representative to OASIS, confirm our support for the OASIS Open Charge Point Protocol (OCPP) Technical Committee charter and the participation of our co-proposers named above.
I, Bram van de Leur, Bram@ev-box.com
, as EV-Box's Primary Representative to OASIS, confirm our support for the OASIS Open Charge Point Protocol (OCPP) Technical Committee charter and the participation of our co-proposers named above.
I, Lionel Causse, email@example.com
, as G2Mobility's Primary Representative to OASIS, confirm our support for the OASIS Open Charge Point Protocol (OCPP) Technical Committee charter and the participation of our co-proposers named above.
I, Sibo Li, firstname.lastname@example.org
, as ChargerLink's Primary Representative to OASIS, confirm our support for the OASIS Open Charge Point Protocol (OCPP) Technical Committee charter and the participation of our co-proposers named above.
(2)(f) TC Convener
(2)(g) OASIS Member Section
None at this time.
(2)(h) Anticipated Contributions
- All OCPP Requests for Change to date; by OCA Technical Working Group
- Tooling inputs used to generate schemas, JSON encodings and other artifacts for OCPP 1.6.
- Security enhancements; by ELAAD/ENCS
(2)(i) FAQ Document
(2)(j) Work Product Titles and Acronyms
The primary work product title is "OASIS OCPP - Open Charge Point Protocol" Acronym for the TC and its work product is "OCPP."
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information societyhttp://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393