Asset Management meets CPMS – without manual handoffs.
How Stackbox automatically transfers new and updated charge points from your Asset Management System to the CPMS – including full mapping to the OCPI data structure. Set it up once. Let it run.
01 · Challenge
Asset data sits in the system. It never reaches the CPMS.
CPOs managing their charging infrastructure via a dedicated Asset Management System know the fundamental integration problem: the operational basis – which charge point is where, what hardware is installed, what configuration applies – is maintained in the asset system but never automatically available in the CPMS. This isn't a niche problem. It's day-to-day reality.
Manual Double Entry
New charge points or changes to existing assets have to be manually transferred to the CPMS. This is time-consuming, error-prone, and does not scale with growing charging networks.
Inconsistent Data States
Changes in the Asset Management – new locations, hardware replacements, configuration adjustments – are mirrored asynchronously or not at all into the CPMS. The systems drift apart.
Missing OCPI Mapping
Asset data does not follow a standardised structure. The transfer into the OCPI data model (Location, EVSE, Connector) must be solved anew for each integration – cumbersome and inconsistent.
Blocked Downstream Processing
Roaming, clearing, and external integrations require OCPI-compliant data. Until this is cleanly in place, every downstream use is blocked or requires repeated additional effort.
Asset Management
CPMS / OCPI
Asset Management and CPMS speak different languages. Without a dedicated integration layer that automatically synchronises, validates, and maps data to OCPI, every integration remains a manual, error-prone one-off process. We know how to fix this – and we do it right.
02 · Solution
One connector that keeps both systems permanently in sync.
Stackbox built an Asset Connector that automatically connects your Asset Management System and CPMS, maps all data to the OCPI structure, and makes it available for downstream processing. You configure it once – then it just runs.
Connecting your Asset Management System
The connector integrates with your existing Asset Management System via API, webhook, or scheduled data pull. New assets and changes to existing entries are automatically detected – without manual trigger.
Validation and Data Enrichment
Incoming asset data is checked, validated for completeness, and enriched with default values or reference data where needed. Inconsistencies are logged before they reach the CPMS.
Automatic OCPI Mapping
Each asset record is mapped to the OCPI hierarchy: Location → EVSE → Connector. The mapping is configurable, versioned, and accounts for your specific field names and data types.
Automatic Transfer to CPMS
New and updated assets are fully and structurally pushed into the CPMS – as new Locations, EVSEs, or Connectors, or as updates to existing records. Delta-sync prevents unnecessary overwrites.
OCPI-ready for downstream use
Since all data is available in OCPI format, it is immediately usable for roaming, clearing via eMSPs, direct payments, and external platform connections – without further mapping.
OCPI Hierarchy
| Asset Field | OCPI | |
|---|---|---|
| site / location | → | Location |
| charge point / evse | → | EVSE |
| connector / plug | → | Connector |
| status / state | → | status (EVSE) |
| power / type | → | max_electric_power |
| coordinates | → | GeoLocation |
System Architecture
Sync · Validation · OCPI Mapping
Compatibility
03 · Impact
What changes for you.
From manual double entry to fully automated synchronisation – with measurable results from day one. That's not a promise. That's what we deliver.
manual steps when transferring new or changed assets
OCPI-compliant data structure for all charge points – out of the box
scalable – even with large charging infrastructure networks without growing maintenance effort
real-time sync – changes in the asset system are instantly active in the CPMS
integrable into existing system landscapes without rebuilding
foundation for roaming, MSP connection, and external platforms without rework
Every time a new charge point went live, it was a manual process – create the asset, update the CPMS, fill in the OCPI fields. With the Stackbox integration it runs completely automatically. The charge point is created in the asset system and is in the CPMS shortly after – OCPI-compliant and ready for operation.
Stackbox · Asset Connector
Ready for automatic asset sync without manual handoffs?
We'll show you how the Stackbox Asset Connector integrates into your existing system landscape – API-first, OCPI-compliant, production-ready.
Let's talk →