Skip to content
acharge by acemo
← Who it's for

Car parks & charging hubs

Many charge points, one connection, mostly other people's drivers

Operating a charging hub means selling electricity to people you do not know. aCharge handles the three things that make that viable: metrology-compliant billing, ad-hoc payment without registration, and roaming so customers of other providers charge with you — and you get paid for it.

What you get

Plan, install, monitor, bill

The four steps between “we would like charge points” and a running installation — from one source, with one point of contact.

01

Concept

Technical feasibility, on-site survey, documentation and, where needed, a load profile measurement.

02

Planning

Detailed and, on request, tender planning, matched to connection capacity and expansion stages.

03

Installation

Built by POSID or your own contractor — the controller is vendor-independent.

04

Operation

Monitoring, user management and metrology-compliant billing then run on automatically.

Capabilities

What the system takes off your hands

Vendor-independent

Wallboxes and charging stations from many vendors over OCPP and Modbus TCP — mixed if need be.

Scalable

Start with a few charge points and grow. Up to 1,000 per site.

Reliable

The local controller keeps regulating even if the internet connection drops.

Always current

Automatic software updates protect your investment over its lifetime.

Load management

Dynamic and multi-stage, integrable even into complicated existing installations.

User management

Manage users and charge cards; users can register themselves.

Billing

Automatic metrology-compliant billing, optionally with SEPA collection.

Monitoring

Remote monitoring of the charging infrastructure with alerting on faults.

Recommendation

For this kind of site: aCharge Cloud

One connection, a manageable number of charge points, one meter: the entry-level tier covers that — and costs less.

aCharge CLOUD auf einer Hutschiene montiert

FAQ

Common questions

How does revenue from other providers' drivers reach us?
Through the roaming network. aCharge connects to Hubject via OICP and supports OCPI; sessions from other providers are recorded, priced and paid out via the settlement overview.
Does this scale across multiple sites?
Yes. aCharge Cloud is designed to scale from a single site to hundreds of thousands of charge points in one installation, with roles and permissions per site.
Do all charge points have to come from the same vendor?
No. aCharge DYLAMO connects charge points over OCPP and Modbus TCP — mixed within the same installation if need be. You can start with whatever is available and add more later without committing to one vendor.
What happens during an internet outage?
The controller keeps regulating on site and enforces the site capacity unchanged, so charging continues. Once the connection returns it re-synchronises with the cloud automatically; sessions and meter readings are not lost.

Other kinds of site