Starting point
WALL-E builds and operates charging and energy solutions for companies, real estate and fleets – from hardware rollout to day-to-day operations in its own charging portal. For the software layer, WALL-E needed more than an off-the-shelf SaaS CPMS: a platform on which to build and run its own multi-tenant CPMS for different customer instances.
Typical tenants are banks, premium OEMs and logistics companies: cases that demand not only features but scale and migration safety – up to 8,000 charge points per customer, incumbent backend operators, and operations that must not stop during the switch.
Solution: OCPP Broker and OCPP Server as the platform foundation
WALL-E uses the NeLeSo OCPP Server and OCPP Broker as the foundation. The server is the OCPP backend on which WALL-E builds its CPMS logic and service portal. The broker decouples charge points from individual backend instances: routing, parallel operation and stepwise cutover become controlled operations instead of a big-bang go-live.
The architecture is multi-tenant: WALL-E can run different customers and operating models on the same platform base – without starting a new OCPP stack for every project. Open APIs connect the WALL-E service portal and other systems to the platform.
Migrate through the broker, not with a big bang
For large fleet customers – banks, premium OEMs and logistics companies – the stack runs at high scale on Azure, with up to 8,000 charge points per customer. Before a switch, two or more incumbent backend operators are often in play. Instead of moving every charger on a single cutover day, the OCPP Broker is inserted first: all charge points are moved onto the broker and still routed to the respective legacy backends.
Only once that intermediate state is stable – connections, sessions, operational flows – does the stepwise migration to WALL-E’s own CPMS server begin. Groups or sites can be switched, observed and rolled back if needed. Charge points never notice the backend change; the broker remains their constant peer.
This path greatly reduces typical migration risk: the critical step “move all chargers” is decoupled from “make the new backend productive”. Stability can be proven before the operational cutover.
Service portal connected in a few days
Via the broker API, WALL-E connected its service portal and gained an operational overview of the estate within a few days – status, sessions and the events that matter for operations, without first building a full custom integration against every legacy backend.
That is the value of a decoupled platform: operations tools and CPMS UIs hang off the broker and clear APIs, not off the internals of whichever legacy system is still running.
Outcome
WALL-E has a platform to run its own multi-tenant CPMS and scale it for banks, premium OEMs and logistics companies – with up to 8,000 charge points per customer. The migration path in practice: broker first, prove stability, then move stepwise to the own server on Azure.
Portal and operations screenshots will follow on this page shortly.