The future of charging:
autonomous, seamless and secure

Hubject kickstarts a fully automated charging experience.

Figure out how we make the difference.

Up until now, charging stations are usually activated by smartphone or RFID card. With Plug&Charge via ISO 15118 Hubject now provides a market-ready, game-changing technology for intuitive and secure charging. Based on installed IT-certificates in cars and charging stations machines communicate autonomous, seamless and secure: this means a shift towards disruptive charging concepts, such as bi-directional or inductive charging processes.

The reason why we lead the field.

We offer automated and secure data exchange – enabled by the first-of-its-kind fully productive ISO 15118-conform PKI. Get ready for a next level of smart charging infrastructure services.

most secure

Our ISO 15118-compliant PKI is a first-of-its-kind: based on the latest ISO 15118 standard, including the usage of X.509 v3 certificates, TLS and cipher suites.

strong and neutral

Our leading position as a market enabler and industry expert predestines us for the neutral role of operating the V2G Root CA.

truly experienced

As a trusted partner in ISO 15118, we are highly experienced in developing, piloting, testing and implementing full-scale projects with world-leading industry players.

Find out how we get you started

1. we enable

Our ISO 15118-compliant PKI is a first-of-its-kind: based on the latest ISO 15118 standard, including the usage of X.509 v3 certificates, TLS and cipher suites.

2. we connect

Our leading position as a market enabler and industry expert predestines us for the neutral role of operating the V2G Root CA.

3. we implement

As a trusted partner in ISO 15118, we are highly experienced in developing, piloting, testing and implementing full-scale projects with world-leading industry players.

These partners trust our service

Find your fit.
We provide tailored solutions.

The perfect answer to your needs: Depending on your individual market role and intended use case we offer solutions for Charge Point Operators, eMobility Service Providers or Original Equipment Manufacturers in four standardized solutions.

Plug&Charge OEM

  • End to end guide for OEMs to support with the integration of ISO 15118 and Plug&Charge in the car and associated backends​
  • Hubject also provides services for OEMs without an own PKI and provides security as a service​

Plug&Charge CPO​

  • Enable Plug&Charge for charging stations and the CPO backend connection to the PKI and Ecosystem for the exchange of V2G Root and EVSE leaf certificates​
  • Also for CPOs without an own PKI / EVSE leaf certificates and Hubject​

Plug&Charge MO​

  • Enable the generation and provisioning of contract certificates for MO and their customers to securely install this into the EV​
  • Also for MOs without an own PKI / contract certificates​

Plug&Charge​ CHECK CPMS​

  • Validate and test how ready your implementation is for Plug&Charge based on ISO 15118 for your backend solution​
  • Jointly identify next steps to close the gaps, in IT security, interfaces, and potential organisational changes needed to comply with the standard and be implementation ready​

Plug&Charge​ CHECK EVSE​

  • Show that your EVSE-solution is plug and play for the Hubject PnC Ecosystem and for distinct CPMS​
  • Extend your charging product with Plug&Charge functionality​
  • Develop new distribution channels and customer opportunities​
  • Communicate to the entire market that your software and hardware product meets all the prerequisites for Plug&Charge based authentication​​

Plug&Charge ​LAB​

  • This lab enables our partners to validate their Plug&Charge implementation against different backend setups and charging station vendors.​

Frequently Asked Questions

Why does Hubject think ISO 15118 is going to be the new standard?

Up until now, charging EVs has been done with relatively insecure protocols and other technologies, which are vulnerable to hacking. ISO 15118 offers the most advanced internet and device proven technologies for a seamless and secure charging experience and service offering for all participants in the eMobility ecosystem, enabled by digital certificates and a secure TLS connection between EV and EVSE. For the last years, Hubject has invested in projects studying the implications of the standard with various implementations and will continue to do so in projects with our partners and shareholders.
Which charging stations and which EVs are currently offering ISO 15118 based communication?
Several companies have already completed successful testings between ISO 15118 compliant EVCC controllers and EVSE controllers on bi-annual testing Symposia. Currently, the only production model which offers ISO 15118 based charging is the Electric Smart from Daimler. However, with Hubject’s tight connection to the OEMs (Original Equipment Manufacturers), we can say that newer models will come in 2019 and onwards. This raises the urgency for the market to be prepared.

On the EVSE side, we are in close collaboration with Ebee technologies (Bender) offering an ISO 15118 compliant controller, with which we have successfully completed projects.

To what extend does Plug & Charge based charging cover ad-hoc charging and payment?
ISO 15118 based authentication authorization of a user and charging has the underlying assumption of a contract between MO or MSP and an EV driver, and assures automatic recognition and therefore authentication and authorization to start the charging process. In contrast, ad-hoc charging and payment is not backed with an underlying contract. We however belief that these services will be offered next to each other.
Can I use the Plug & Charge products from Hubject, without being a partner of the intercharge Network?
One can become a participant of the Plug & Charge Ecosystem, using Hubject services for support with the ISO 15118 implementation. We however recommend, to also connect to our roaming platform for the ability to connect to other eMobility ecosystem participants in one go.
How does it work when an EV driver has multiple contracts from various MOs with whom he likes to enable Plug & Charge functionalities?
In the permanent memory of the car, there is theoretically space for 5 contract (certificates). Without taking the process of installation of new certificates in the EV into consideration, charging sessions based on a different contract, e.g. a private and a business contract, should be triggered by either the HMI (Human Machine Interface) in the EV or via the app of the MO, by which the new applicable contract certificate will be activated.
How can certificates be installed in an Electric Vehicle?
The process to install certificates in the EV looks as follows:

  1. With production of the EV, the OEM installs the OEM provisioning certificate and the V2G Root certificate from Hubject in the permanent memory of the EV.
  2. The EV driver concludes a contract with the Mobility Operator.
  3. Within a first Plug & Charge based charging session, the OEM provisioning certificate is forwarded to the charging station, which checks it with the Clearing House (Hubject).
  4. After which the contract is connected to the EV, with a contract certificate, this contract certificate, via the CPO backend is also installed in the EV.
  5. The Plug & Charge based charging session can start, within a matter of 5 seconds.
What is the DKE/VDE Anwendunsgregel and why is it important for my ISO 15118 implementation?
The Application Rule is a guidance document specifying recommended practices for the ISO specifications with regards to a specific technology, thereby filling specification gaps. Additionally, it defines the roles of e.g. CPO,OEM, MO, CPS within the ISO 15118 PKI as well as their processes need to be set up. The Plug & Charge Ecosystem by Hubject is fully based on the DKE/VDE Anwendungsregel.

The specification can be found here

What changes in my backend do I need to consider in order to become a part of the Plug & Charge Ecosystem?
This differs from the perspective in the market that you would have. The OEM has to make other considerations than the MO. With the connection to the Hubject Ecosystem and our V2G Root CA, and the provisioning of Sub CA by connection to the webservices, there are not many changes needed: you can just can get started.
What supporting documents to regarding the PKI can Hubject provide me with?
On our PKI website, we have placed the Certificate Policy (CP). In this document you will find a description of the business, legal, and technical requirements for approving, issuing, managing, using, revoking, and renewing, digital certificates within the PKI and providing associated trust services for all participants within the PKI. In short, the Certificate Policy sets requirements that participants of the Hubject Plug&Charge PKI must meet.
Why is Hubject taking the role of V2G Root Certificate Authority?
The V2G Root CA (Certificate Authority) is an authority that issues and manages certificates. As it verifies the Contract EMAID, PCID of the EV and signs certificates to prevent certificate forgery and manipulation. As we already have a neutral and strong central position in the eMobility market for the last 6 years, and while we believe in this new standard, we also see an opportunity in supporting the market in their needs of implementing ISO 15118 as the provider of certificates as V2G Root CA.

Hubject Plug&Charge services are certified in information security 
according to ISO 27001 by TÜV Süd. For further information regarding the Hubject V2G PKI and security audit please click here.

Be sure that we meet your needs.

Oval 4

Jonel Timbergen

Senior Business Manager

Hubject has got all you need to kickstart your ISO 15118 solution: Interested in a workshop or even a full-scale MVP project with Hubject?
Get in contact