OEM EV Charger With CMS

Hardware

AC charging hardware built to your configuration or your design, with metering, protection and connectivity appropriate to the target market. See the AC OEM page for platform scope.

Firmware

Developed in the same organisation as the hardware, which is why a timing problem between the contactor and the pilot state can be diagnosed rather than negotiated between suppliers.

OCPP

OCPP 1.6J and 2.0.1 are released, with the implementation maintained rather than frozen at ship date. Because we also build backends, protocol behaviour is tested from both ends rather than against a specification document alone.

CMS

A charging management system for monitoring, authorisation, tariffs, sessions and reporting, deployable as your own platform. Where you already have a CMS, the hardware connects to it over OCPP instead, and the bundle is not required.

Buying both from one supplier is a support decision, not a lock-in requirement. The hardware speaks standard OCPP and will connect elsewhere.

Provisioning

Units leave production with identity and credentials applied, so commissioning on site does not depend on an engineer typing configuration into a unit in a basement with no signal.

Field support with one owner

When a session fails intermittently, the question is which layer caused it. With one supplier across hardware, firmware, protocol and platform, that question has an owner rather than a meeting.

This is the actual argument for the bundle. Not integration convenience, but the elimination of the gap between suppliers that field problems fall into.

Why the platform question outlives the hardware question

Chargers last around a decade in the field. Platform relationships frequently do not, and the mismatch between those two timescales is where the expensive surprises live.

We used to resell a shared third-party platform to several customers at once. Each of them saw their own brand. Underneath, one system served all of them, so any change one customer asked for either could not be made or landed on everybody. When a change finally became unavoidable, the only way to deploy it was to send people out to every charger and do it physically, in the field, unit by unit.

That is why Charger360 exists and why we treat platform portability as a hardware requirement rather than a software feature. A fleet should be able to move between management platforms remotely. If your OEM cannot tell you how the fleet changes backend without a site visit, you have bought a van route along with the chargers.

How we work with you on this

Buying hardware and platform from one supplier concentrates risk, and we would rather name that than have you notice it later.

Our answer is to make leaving possible. The fleet can be pointed at a different management platform remotely, so the platform relationship has to be re-earned rather than enforced by the cost of exit. We built that capability because we watched the alternative, on chargers we had to visit physically to change.

Your team gets the operational training to run the platform themselves. Continuing support is a monthly arrangement rather than a dependency.