CPO · fleet · OEM

Plug & Charge / ISO 15118-20 Demo login

Vehicle recognition, contract certificates and ISO 15118-20 flows — publicly through Hubject, at home with capable wallboxes.

Open CPMS demo → Got questions? Get in touch

Best reviewed together: Plug & Charge touches the CPMS, Hubject, charger firmware, contract certificates and home-charging flows.

Vehicle Contract identity eMAID · PCID · Cert

ISO 15118-20

EVSE Capable wallbox OCPP 2.0.1 · Session

authorize

Pipelet CPMS Identity tenant · tariff · driver

Hubject Plug & Charge

Home charging Driver Portal

Back office Billing & reporting

Plug & Charge in Pipelet is not an isolated certificate feature. The integration spans the CPMS, Hubject and the Driver Portal: contract certificates, eMAID/PCID mapping, authorization, session attribution and billing run through the same suite.

For public charging infrastructure, Pipelet supports a full Plug & Charge integration through Hubject. The CPMS can bring ISO-15118-capable charge points, contract data and OCPP sessions together so drivers can start charging without RFID or an app.

For company cars and home charging, ISO 15118-20 is also used in the home-charging portal: at an ISO-15118-20-capable wallbox, Pipelet recognizes the vehicle at home, assigns the charging session to the right company car and prepares reimbursement or reporting tenant by tenant.

What to expect

✓

Hubject Plug & Charge

Integration with Hubject PnC processes including contract certificates, eMAID/PCID mapping, certificate validation and clean session attribution.

✓

ISO 15118-20 in the CPMS

ISO-15118-20-capable wallboxes and OCPP sessions become visible in the CPMS: vehicle identity, charge point, tenant and authorization remain traceable.

✓

Vehicle recognition at home

The home-charging portal recognizes company cars automatically at capable wallboxes and cleanly attributes private, business and reimbursable sessions.

✓

One identity stack

RFID, app, eMAID, PCID and vehicle data converge in the same tenant and billing models instead of separate point solutions.

Common scenarios

Public CPO with Hubject PnC

Drivers plug in, the vehicle provides its contract identity, Pipelet validates via Hubject and starts the session without an RFID card or app interaction.

Company car charging at home

At an ISO-15118-20-capable home wallbox, Pipelet recognizes the company car automatically and creates a reimbursable home-charging session for fleet and HR.

OEM or wallbox validation

Simulator, CPMS and protocol logs help test ISO 15118/OCPP flows reproducibly and narrow field issues between vehicle, wallbox and backend.

How Plug & Charge / ISO 15118-20 fits into the suite

Integrates with

Plug & Charge / ISO 15118-20 https://cpms.pipelet.com

Driver Portal Home charging, charging history, CarData integra Fleet Portal Fleet management, driver management, RFID and bi CPMS Core The new operator UI: sites, charger commands, vo

Frequently asked questions

Is Pipelet available as source code?

Yes. Every module is available as a source-access package — complete with Docker Compose, documentation and an SLA support channel. You can audit, customize and self-host.

Which OCPP versions are supported?

Full OCPP 1.6 and 2.0.1 including Security Profiles, Smart Charging, and ISO 15118 Plug & Charge.

Can I use individual modules only?

Yes. Every module is standalone — you can deploy e.g. just the OCPP Broker as infrastructure and build your own CPMS on top.

What does onboarding look like?

We start with a 30-minute call to scope requirements. After that you get a concrete proposal with modules, timeline and price. Pilot typically live in 4–8 weeks.