OCPP HUB / CONNECTIVITY & CONTROL
One charger connection. More possibilities.
Connect your chargers to your own platform and partner CSMS. Keep clear ownership, control permissions and the evidence to understand every session.
Product screenshot with demonstration data
MULTI-CSMS
A clear role for every connected platform
- 01
Record owner: official charger records
- 02
Controller: permitted commands
- 03
Observer: session data
01 / Built around your operations
Connect more platforms. Keep control clear.
A single endpoint at the charger opens up multiple upstream connections. Each platform gets the role and actions you permit.
- One record owner per charger; separate controller and observer permissions.
- One configuration owner for charger-wide commands such as reset or firmware updates.
- Default-deny command allowlists per charger–CSMS pair.
- Change routing and permissions from the console after the initial charger setup.
02 / Built around your operations
Keep the session connected across systems.
Configured failover helps the network continue when an upstream platform is unavailable, while transaction mapping keeps records aligned.
- Promote a configured backup CSMS when the record owner is down.
- Map the HUB session to each CSMS’s own transaction number.
- Replay a missed stop to the owner after failback.
- Handle duplicate starts and apply reconnect back-off.
Failover requires a configured backup. Behaviour also depends on the charger and connected CSMS.
03 / Built around your operations
Bring new chargers into your existing network.
Support mixed hardware and OCPP versions without making every system move at once.
- OCPP 1.6J and 2.0.1 configured per charger and upstream CSMS.
- Enable 2.0.1 → 1.6 translation per backend.
- Review the compatibility matrix for supported messages and fields.
- Route RFID cards by prefix and schedule CSMS attachment windows.
Translation has message and field limits; it does not make every 2.0.1 capability available in 1.6.
04 / Built around your operations
Know which platform owns each session.
Make partner reporting and energy reconciliation easier with ownership attached to the underlying session.
- Energy reports by charger, site or tenant, split by owning CSMS.
- Session records with energy, RFID tag, owner and ending reason; CSV exports.
- Read-only Partner API for overview, locations, health, sessions and energy.
- Partner keys with scoped permissions, optional IP allowlists and access logs.
05 / Built around your operations
Answer “what happened?” with evidence.
Bring sessions, OCPP frames, connection attempts and health events into one investigation window.
- Live frame monitoring and a connection log, including unknown chargers.
- Health events, vendor alarm codes and charger timelines.
- Rules flag missing starts, clock drift and contradictory evidence.
- Optional AI helps plan an investigation and explain the evidence it cites.
AI investigation is Preview, controlled by tenant policy and quota. Evidence remains available when AI is disabled.
Screens show demonstration data. Siam EV Demo is a fictional operator. Capabilities depend on charger support and configuration. We can review your hardware and workflow during a demo.
Let’s map the platform to your network.
Tell us about your chargers, existing systems and the experience you want to offer. We’ll walk through the right setup together.
Book a demo