Integrations · OCPI

OB7 and your CPMS:connected via OCPI

Your CPMS keeps running the chargers. OB7 takes care of everything your customers see: ad-hoc charging, the driver app and billing under your brand. Through the ENAPI roaming hub your customers also charge on other networks.

  • OCPI 2.1.1 · 2.2.1 · 2.3.0
  • Live with eRound, chargecloud and EAAZE
  • Roaming via ENAPI
Architecture
OB7OCPIOCPPOB7 · YOUR BRAND
  • Ad-hoc charging
  • Driver app
  • Billing
  • Roaming

Step by step

One charging session,from the charger to the invoice

What happens between charger, CPMS and OB7 when someone charges? Pick a case and walk through the steps.

Step 1 of 6

01

Locations and prices arrive

Your CPMS reports charge points, status and tariffs to OB7 via OCPI. This runs continuously in the background, not only when someone charges.

HARDWAREYour chargersconnected via OCPPCPMSYour CPMSruns the chargersROAMINGOther networksother operatorsROAMING HUBENAPIrouting & clearingEMSP BACKENDOB7under your brandFRONTENDYour customersweb app & driver appLocationsTariffs
  • Toward the customer
  • Toward the charger

Overview

Who talks to whom:charger, CPMS and OB7

Your own network and, through the roaming hub, other networks. The dots show which way the data flows.

Diagram
HARDWAREYour chargersconnected via OCPPCPMSYour CPMSruns the chargersROAMINGOther networksother operatorsROAMING HUBENAPIrouting & clearingEMSP BACKENDOB7under your brandFRONTENDYour customersweb app & driver appOCPPOCPIOCPIOCPI
  • Toward the customer
  • Toward the charger

The OCPI modules

Six modules, each with one job and one direction.

LocationsCPMS → OB7
The CPMS reports locations, charge points and their status. OB7 shows them on the map and in the app, available or occupied, in real time.
TariffsCPMS → OB7
Prices come from the CPMS. Your customers see what a session costs before they start.
SessionsCPMS → OB7
While charging, the CPMS reports energy, duration and status. Your customers follow it live.
CDRsCPMS → OB7
After the session the CPMS sends the Charge Detail Record, the billable data set. The invoice is built on it.
TokensOB7 → CPMS
OB7 tells the CPMS which customers, apps and charging cards are allowed to charge.
CommandsOB7 → CPMS
OB7 starts and stops sessions from the web app or the driver app. The CPMS passes the command on to the charger via OCPP.

Division of roles

What stays,and what OB7 adds

Stays

With you and your CPMS

  • Your CPMS and the contract with its provider
  • Your chargers and their OCPP connection
  • Operation, monitoring and fault handling of the chargers
  • Master data such as locations and charge points
New with OB7

For your customers

  • Ad-hoc charging via QR code, no sign-up needed
  • A driver app under your brand in the App Store and on Google Play
  • Customer accounts, subscriptions and billing in the eMSP backend
  • Roaming: your customers also charge on other networks

Partners

These systemsare already connected

The same standard everywhere: OCPI. Dedicated partner pages will soon cover what differs from system to system.

eRound

CPMS

The CPMS of Hamburger Energienetze. Running together with OB7 at HEnW Mobil in Hamburg.

About the partnership

chargecloud

CPMS

CPMS for charging infrastructure. OB7 connects via OCPI and adds ad-hoc charging, the driver app and billing.

Partner page coming soon

EAAZE

CPMS

CPMS for charging infrastructure. Here too the connection runs over OCPI, with no changes at the chargers.

Partner page coming soon

ENAPI

Roaming hub

Platform for roaming and clearing. One connection is enough to reach many other networks.

Partner page coming soon

Your CPMS is not listed? If it supports OCPI, it can usually be connected. Ask us.

FAQs

Frequently asked questions

About connecting your CPMS and roaming hubs.

Do we have to switch our CPMS?

No. OB7 does not replace a CPMS. Your CPMS keeps running the chargers, and OB7 adds everything your customers see and use.

Which OCPI versions does OB7 support?

OCPI 2.1.1, 2.2.1 and 2.3.0. Both systems negotiate the version when they connect.

What is a CDR?

A Charge Detail Record is the final data set of a charging session: energy, duration, price and charge point. The invoice is based on it.

What does a roaming hub like ENAPI do?

A hub bundles many operators behind one connection. Instead of connecting to every operator one by one, OB7 talks to ENAPI. The hub forwards the data and handles clearing.

Do we need new hardware?

No. The chargers stay connected to your CPMS via OCPP. For ad-hoc charging, QR codes go on the chargers. They work independently of the CPMS and survive a later system change.

Our CPMS is not listed. Can it still work?

If your CPMS supports OCPI, usually yes. Tell us which system you use and we will check the connection.

Who owns the data?

You do. All data is available through open interfaces at no extra cost.

Let's talkabout your CPMS

Tell us which system you use. We will show you what the connection looks like and what your customers see afterwards.