Open Charge Point Protocol

Jan Kosta is a FlexiCharge co-founder working across sales, business development, and account management.

Together, they explain how a single OCPP proxy can run a primary, a fallback, and a service backend in parallel.

Why three backends means three different transaction ideas and how a smart mapping layers keeps everyone in sync.

And the industry trends Yann is watching most closely right now.

And how much of that was completely aligned with the briefing or the request we got from Daimler? Or did you convince them to slightly change the requirements because the solution developed was even better than what they asked for?

The solution was designed very much in collaboration with them.

We started off with the same idea, with the same ambitions, and then we realized where the restrictions are, and they're mostly coming from how OCPP and the version 1.6 works.

which is basically that the backend services provide the transaction ID, right? When we realized that, that introduced a lot of different sort of issues.

So even when we're trying to talk about EV charging from more of an automotive perspective, it's often quite jargon heavy terms that can even lock out businesses.

So an example of that might be the term OCPP or some of the pass and standard terminology that we just kind of fling around within this industry.

Tracey, any thoughts?

Couldn't agree more, Belinda.

So nuanced.

Any closing comments before we move on, Belinda?

Yes, I'm just going to say to the industry, please, if we're using words like OCPP and all of this technical information, can we at least break it down for everybody so it's accessible? Thank you.

Wonderful.