Start with the network you need to operate

A charge point management system (CPMS) can monitor chargers, manage users, apply tariffs and connect charging data to the rest of an operator’s business. Choosing one should begin with the operating model, not the longest feature list.

Define the charger types, markets, users, payment methods, support hours, reporting duties and energy constraints. Separate functions required at launch from possible future services. A platform built for public rapid charging may be a poor fit for home reimbursement or shared residential sites, even if both products call themselves a CPMS.

Test the exact charger and OCPP implementation

Confirm the live OCPP version and functions supported by the CPMS and by each charger and firmware version. Check formal certificates in the Open Charge Alliance certification programme, then test the actual pairing. Certification reduces integration uncertainty, but a pilot must still cover the functions your network will use.

Map the connection path too. Does the charger connect directly to your CPMS, or through a manufacturer cloud? Who controls the OCPP credentials, SIM, certificates and firmware? Check what continues locally when the connection fails, including authorisation, active sessions and stored transaction data.

Make the operations team use it

Give support staff realistic tasks during the trial: locate an intermittent charger, inspect its message history, restart it, change a setting and collect evidence for a customer case. A polished dashboard matters less than whether an operator can identify the fault and decide what to do next.

Follow a session from access to settlement

Test RFID, app and other required authorisation methods from start to finish. Check meter records, tariff rules, VAT, payment failures, refunds, reimbursement and charge detail exports. Establish which system creates invoices and which party reconciles missing or disputed sessions. Legal metrology requirements must be checked for every market where energy is billed.

Decide where energy control belongs

A CPMS may send schedules or charging limits, but site control can also sit in the charger, a local controller, an energy-management system or a specialist service. Define which component makes each decision and what must keep working without internet access. “Smart charging included” is not an architecture.

Inspect integrations and data access

List the systems needed now and later, such as payment services, roaming, accounting, CRM, fleet tools, energy services and data warehouses. Review API documentation, permissions, webhooks, rate limits, test environments and data retention. Confirm that raw operational and transaction data can be exported in a usable format.

Plan the exit before signing

Ask how chargers would be pointed to another backend and how credentials, users, tariffs, session records and audit logs would move. The Open Charge Alliance recommends testing every charger model and firmware before a CSMS migration. A credible supplier should be able to explain the process, responsibilities and fees before the contract is signed.

Price the whole operating model

Compare licence and transaction charges alongside onboarding, payment, roaming, support, data retention and migration costs. Add the labour needed to resolve faults and reconcile sessions. Low software fees do not help if routine cases require manual work or site visits.

Run a representative pilot

Use production firmware, real connectivity and the integrations intended for launch. Test successful sessions, failures, offline behaviour, updates and recovery. Record acceptance criteria and assign ownership for fixes. The result should be evidence that the charger, CPMS and operating process work together.

How amina fits

amina supplies focused charging hardware and works with specialist software partners. amina C/C2 and amina M/M2 use local OCPP 1.6J for CPMS connections; C2 and M2 are described as hardware-ready for OCPP 2.0.1. Hardware readiness is not the same as every OCPP 2.0.1 function being active in a particular firmware and backend pairing, so buyers should evaluate the version available for deployment.

This approach keeps software choice with the operator while recognising that compatibility still needs proving. See the current integration partners and test the intended combination before roll-out.