One EMS, Three Ways to Deploy It

Not every charging site needs the same setup. A single connector in a car park runs fine on cloud-managed control. A multi-asset hub with a battery, solar and a DSO curtailment signal does not.

CPOs that default to one architecture across the whole portfolio end up over-engineering the simple sites and under-serving the complex ones. Ignoring that DSO rules and grid requirements differ by country makes it worse. The fix isn't more hardware everywhere. It's matching the control layer to what the site, and the market it's in, actually needs.

FLEXECHARGE runs load and energy management three ways: in the cloud, on a local GATEWAY, or inside a standardised FLEXBOX that bundles local execution, DSO interfaces and site networking into one unit. One platform, three ways to deploy it, so the architecture fits the site instead of the other way round.

In this masterclass, Nicolas and Jan walk through when each option applies and why, using a decision tree and three real site types, from a simple charging location to a regulated, multi-asset hub.

FLEXECHARGE gives you one platform, built to run the way each site actually needs it to.

What you will learn

• what role Cloud, GATEWAY and FLEXBOX each play in a FLEXECHARGE deployment

• when a site needs local, offline-capable control instead of cloud

• how DSO signals, country rules and site assets change which architecture fits

What this means for your rollout

• You stop guessing site by site and start from a framework that already accounts for DSO and country differences.

• Commissioning takes less back-and-forth because the architecture already matches what the site needs.

• Standardisation happens where it can, without forcing complex sites into a setup they'll outgrow.