
STARTER PACKS / MOBILITY
EV CHARGING NETWORK
STARTER PACK
60 DAYS - €4,900
OCPI INTEGRATION AND LIVE CHARGING AVAILABILITY - FOR ONE CHARGING NETWORK.

problem
YOU OPERATE A CHARGING NETWORK BUT EVERY ROAMING PARTNER, EVERY DRIVER APP, EVERY MAP REQUIRES A DIFFERENT INTEGRATION. THE ISSUE IS NOT MORE CHARGERS - IT'S PUBLISHING WHAT YOU HAVE IN ONE OPEN STANDARD EVERYBODY CAN CONSUME.
EVERY ROAMING
PARTNER WANTS A
DIFFERENT API
One uses OCPI. Another wants a custom JSON. A third wants OCPP.
DRIVERS CAN'T FIND
YOUR STATIONS IN
THEIR APP
Without OCPI, you're invisible to most navigation and EV-trip-planning apps.
SESSION DATA STAYS IN
YOUR CSMS
Operations sees it. No one else does. Reporting is manual.
CROSS-DOMAIN INSIGHT
IS MISSING
Charging vs traffic vs parking vs grid load - all separate.
CHARGING OPERATORS DON'T NEED MORE INTEGRATIONS. THEY NEED ONE OPEN INTEGRATION THAT REPLACES THEM ALL.
solution
We start with the Starter Pack (one charging network, OCPI 2.2.1 publishing, NGSI-LD bridge) because this gives you 80% of value in 60 days with minimal cost and no risk.
HOW WE APPROACH THIS
(simple and a bit refreshing)
We connect to your charging station management system, expose OCPI 2.2.1 endpoints for roaming partners and apps, and bridge to NGSI-LD for cross-domain integration.
We connect it using:
- OCPI 2.2.1 as the open roaming and data standard.
- ETSI NGSI-LD Smart Data Models for EV charging entities.
- The Vela Context Data Hub.
- Your existing CSMS (Charging Station Management System) - Has·to·be, Driivz, ChargePoint, Greenflux, custom - via OCPP and CSMS-specific APIs.
No replacement of your CSMS. No new charging hardware. No 'enterprise digitalisation committee'.
Once the connection is built → OCPI endpoints serve roaming partners, your stations appear in driver apps, and your data joins the city mobility context.
Then we expand - adding session analytics, demand forecasting, and grid-load correlation.
What You Get (in 60 Days)
- OCPI 2.2.1 endpoints - locations, EVSEs, Connectors, Tariffs, Sessions, CDRs.
- Roaming-partner connectivity - plug-and-play with OCPI-compliant partners - Hubject, Gireve, e-clearing.net.
- NGSI-LD Context Bridge - your network in the Vela Context Data Hub for cross-domain queries.
- Live station availability widget - embeddable on your website, partner sites, city portals.
- Session and CDR analytics - daily session reporting, peak hours, station utilisation.
- Driver-facing data - journey planners and EV-trip apps consume your stations natively.
- Data ownership - your data. Your tariff. Your customer relationships. We're the layer underneath.
THIS IS YOUR CHARGING-NETWORK PUBLISHING LAYER, NOT A PILOT.
Who This Is For
EV charging network operators that:
- Run 20+ public charging stations across one or more locations.
- Use a CSMS that exposes OCPP and basic management APIs.
- Need OCPI publishing for roaming partners or driver apps.
- Want cross-domain integration with traffic, parking, grid load, weather.
Multi-CPO regional aggregators → see Mobility Data Space STARTER pack.
pricing
STARTER PACK
€4,900
one time setup
(20 working hours included for consulting and developing)
-
- Fully managed shared hosted Vela Context Data Hub instance
-
The essentials
Metadata and data viewer / editor
Searchable metadata and data portal
Authentication and authorization
CSMS connector (Has·to·be, Driivz, ChargePoint, Greenflux, custom)
OCPP 1.6 / 2.0.1 ingestion
Database
NGSI-LD Context Broker
Network / location / station / EVSE / connector hierarchy
Semantic model for EV charging (NGSI-LD bridge to OCPI)
OCPI 2.2.1 endpoint generator
Roaming-partner connection setup (Hubject / Gireve / e-clearing.net)
Live station availability widget
Session and CDR dashboards
Data ownership
API for database access and direct Context broker access
Installation
-
Support
Email support (Business hours)
(OPTIONAL) 12 MONTH SUPPORT EXTENSION
€990/month
12-month support extension,
hosting & support, billed monthly after 60 days period
(5 working hours per month included for consulting and developing)
Quarterly review session
New stations / locations / partners onboarded
OCPI version-evolution support
Support
Email support
Want the architecture walkthrough?
We’ll show:
- How your CSMS feeds OCPI automatically.
- How roaming partners and driver apps consume your stations.
- How NGSI-LD bridges charging into the wider city context graph.
VELA CONTEXT DATA HUB · ONE SHARED DATA LANGUAGE FOR MOBILITY · EU OPEN STANDARDS (NGSI-LD) · YOUR INFRASTRUCTURE, YOUR RULES