CPO EV Charging Solution Operating Model and Procurement Guide

A CPO EV charging solution has to keep physical infrastructure, digital operations, customer access, energy, payments, and field service working as one commercial service. Buying connected chargers is only the first part. The charge point operator must also decide who owns each system, how failures are recovered, how revenue is reconciled, and how the network can change suppliers without losing control of its assets or data.

This guide helps new and scaling CPOs, utilities, energy companies, infrastructure investors, municipalities, and integration partners design the operating model before selecting vendors. Luxman Energy can supply project-specific charging configurations, while the wider CPO stack and local service relationships should be defined in the procurement scope.

Define the CPO role before selecting systems

In the EU, AFIR defines an operator of a recharging point as the entity responsible for managing and operating the point and providing the charging service to end users, including when acting for a mobility service provider. Other markets use different legal language, but the practical distinction remains useful.

A CPO normally controls the infrastructure service. An e-mobility service provider, or eMSP, manages a contractual relationship with drivers and may sell access across several CPO networks. A roaming platform exchanges data and commercial records between them. One company can perform several roles, but the contracts, identifiers, tariffs, taxes, and support responsibilities should still be separated.

Write a role matrix covering:

Activity	Accountable party to name
Site lease and grid connection	Asset owner, site host, CPO, or project company
Charger operation and availability	CPO or contracted operator
Charger hardware warranty	Manufacturer, distributor, or EPC
CSMS and charger communications	CPO platform team or managed-service provider
Ad hoc payment and merchant account	CPO, payment service, and acquirer
Driver contract and roaming	CPO, eMSP, or roaming provider
Tariffs, tax, invoices, and settlements	Commercial and finance owners
Remote support and field maintenance	Network operations center and service contractor
Regulatory data and reporting	CPO compliance owner and data provider

If two vendors both describe the other as responsible, the gap usually appears during a failed charging session, refund, or overnight outage. Resolve it in the contract before rollout.

Design the CPO EV charging solution as seven operating layers

The complete stack should be approved layer by layer, with an interface owner between each pair.

Layer	Main decision	Evidence required before rollout
Site and electrical system	Connection capacity, protection, metering, bay layout, future expansion	Approved design, grid agreement, inspection and commissioning records
Charging hardware	AC or DC power, outputs, connectors, cables, environmental rating	Exact configuration, test evidence, spare and warranty plan
Charger management	OCPP version, remote control, transactions, firmware, alarms	Function statement, certification scope, interoperability tests
Customer and payment	Access methods, tariff display, acquiring, receipts, refunds	Tested user journeys, merchant setup, financial reconciliation
Roaming and discovery	Locations, status, tariffs, tokens, sessions, charging data records	Partner interfaces, identifier register, roaming test cases
Energy management	Site limits, allocation priorities, schedules, demand response	Power study, control hierarchy, fail-safe behavior
Operations and analytics	Monitoring, incidents, field service, reporting, data retention	SLA, playbooks, dashboards, export and exit plan

Do not procure each layer independently and leave integration for commissioning. Define event and data flows early: authorization, connector start, meter records, payment capture, charger fault, power limit, tariff update, firmware change, and asset replacement.

Segment the network by service promise

One CPO may operate workplace AC charging, retail destination sites, urban hubs, fleet depots, petrol stations, and motorway DC charging. These sites should not share one undifferentiated design standard.

Create service classes using:

• Vehicle type and expected energy per visit

• Arrival pattern and dwell time

• Required departure or turnaround time

• Public, private, fleet, tenant, or mixed access

• Revenue model and acceptable payment friction

• Site staffing and support availability

• Grid capacity, energy tariff, and demand constraints

• Regulatory classification and data obligations

A long-dwell office site may prioritize managed AC capacity and user allocation. A motorway hub may prioritize multiple high-power DC points, payment-terminal redundancy, visible pricing, and rapid cable replacement. A fleet depot may value departure readiness and vehicle scheduling more than public roaming.

Set hardware, uptime, response, payment, and spare-parts standards for each service class. This protects the CPO from paying for high-cost features everywhere while under-specifying the sites where each minute of downtime matters.

Select hardware from demand and operating conditions

Model daily energy and simultaneous power separately. Charger nameplate power answers how fast a point may charge under suitable conditions. The site model answers whether the grid, transformer, switchgear, cables, controls, and vehicles can use that output at the same time.

For each site, document:

1. Vehicle arrivals by hour and day.

2. Energy required per session and before departure.

3. Dwell-time distribution rather than one average.

4. Vehicle inlet, voltage, and charging-curve limitations.

5. Simultaneous-session assumptions.

6. Available site power under peak non-charging load.

7. Planned chargers and expansion stages.

8. Failure capacity when one point or feeder is unavailable.

Use this model to choose AC and DC output, number of ports, cable and connector type, and power-sharing behavior. Require environmental derating curves where high or low temperature, altitude, dust, humidity, or direct sun can affect output.

The hardware specification should also cover screens, authorization readers, payment terminals, meters, accessibility, impact protection, communications, cyber controls, remote updates, consumable parts, and field replacement time.

Require proven charger and CSMS interoperability

The Open Charge Alliance defines OCPP as the open communication protocol between charging stations and charging management systems. OCPP 1.6 remains widely implemented, while OCPP 2.0.1 and 2.1 add more advanced transaction, device, security, smart-charging, and other functions.

Procure supported functions rather than the word OCPP. List required remote commands, status behavior, meter values, transaction records, authorization, charging profiles, security settings, diagnostics, firmware controls, display messages, and offline recovery. Then identify the protocol version and profiles that deliver them.

OCPP certification is valuable conformance evidence for the exact product and software version. It does not prove interoperability with the CPO’s complete configuration, payment service, site controller, or custom extensions. Run factory tests against the chosen CSMS and repeat critical journeys on the production network.

Maintain a tested-combination register containing charger model, hardware revision, firmware, OCPP version, CSMS release, configuration package, optional devices, and test date. Treat a firmware update as a controlled change, not routine maintenance with no commercial risk.

Build payments around the complete session lifecycle

The CPO must control the relationship between tariff, authorization, charging, payment capture, receipt, settlement, and refund. A successful card authorization is not a successful paid charging session.

Define the normal path and exceptions:

• The driver selects an available connector.

• The system shows the applicable tariff and any authorization hold.

• The payment method or contract authorizes the session.

• The correct charger starts once.

• Meter values and status remain linked to the authorization.

• The stop event produces a final billable record.

• The correct amount is captured, invoiced, or allocated.

• A receipt is available and settlement is reconciled.

Test declines, repeated taps, start failures, network timeouts, zero-energy sessions, charger reboots, missing stop records, partial captures, refunds, and chargebacks. Every uncertain state needs an owner and a safe retry rule that does not duplicate the charge or session.

Separate bank-card payment data from charging data. The charger and CSMS should normally use non-sensitive tokens and references for session control and reconciliation. Define the PCI DSS responsibility split with the merchant, payment provider, acquirer, terminal manager, and any support supplier that can access connected systems.

Use roaming without losing identifier control

Roaming allows a driver with an eMSP contract to use another CPO’s infrastructure. The CPO still needs reliable location, tariff, token, session, and charging data record exchange.

The EVRoaming Foundation’s OCPI release page lists OCPI 2.3.0 as an available release with AFIR-related data support and a Direct Payment module. It also documents the widely implemented 2.2.1 family, which covers locations, tariffs, tokens, sessions, charging data records, and remote tools.

OCPP and OCPI solve different interfaces. OCPP commonly connects the charger to the CSMS. OCPI commonly connects CPO, eMSP, and roaming systems. Buying an OCPP charger does not make roaming automatic.

Create one identifier policy for country code, party ID, location, EVSE, connector, tariff, token, session, and charging data record. Map identifiers through the charger, CSMS, payment system, roaming partner, public data interface, finance platform, and support tools. Asset replacement should not silently create a new commercial identity or reuse an old merchant mapping.

Make field operations part of the solution

Remote monitoring reduces visits only when alerts lead to a clear action. Build an operating playbook for each failure class:

Failure	First action	Evidence for escalation
Charger unreachable	Check power and primary or backup network	Last heartbeat, local power, modem and router status
Connector unavailable	Check active session, lock, cable and fault code	OCPP events, photos, local diagnostic log
Payment unavailable	Compare terminal, PSP, acquirer and merchant health	Terminal ID, non-sensitive transaction reference, network status
Session will not start	Validate authorization, vehicle state and connector mapping	Timeline across terminal, CSMS and charger
Incorrect tariff	Freeze affected version and compare source systems	Display evidence, tariff version, transaction record
Slow charging	Compare vehicle request, charger limit, site limit and temperature	Requested and delivered power, profile, derating state

Define 24-hour coverage only where the service model and contract fund it. Distinguish monitoring hours, help-desk hours, remote-response time, field-response time, restore target, and permanent repair target.

Stock spares based on failure impact and lead time. Payment terminals, screens, communication devices, contactors, modules, cables, connectors, filters, and cooling components may need different stocking policies.

Manage energy at site and portfolio level

Energy management should preserve site limits and meet the charging service promise. Decide where control runs: charger, local site controller, CSMS, building management system, or an energy platform. Name the authoritative limit and define behavior when two controllers send different instructions.

Allocation rules can prioritize fleet departure, emergency or service vehicles, public fast charging, subscribed users, or fair sharing. The customer interface should not promise a fixed rate when the site is designed to vary power. Tariff and refund rules should account for reductions caused by site control rather than vehicle choice.

Track total energy as well as peak power. Load management can reduce simultaneous demand but cannot compensate for insufficient hours to deliver the daily energy requirement. Include expansion scenarios, transformer lead time, storage or solar interfaces where relevant, and safe local limits during network loss.

Control data security and supplier access

A CPO network combines internet-connected industrial equipment, payment services, customer accounts, and critical operating data. Require role-based access, multifactor authentication where appropriate, unique credentials, certificate management, encrypted communications, audit logs, vulnerability handling, patch support, backup, recovery, and controlled remote access.

Maintain separate production, test, and support environments. Vendors should not share administrator credentials or retain unrestricted permanent access. The CPO needs an offboarding process for staff, installers, service partners, terminal managers, and software suppliers.

Contracts should define data ownership, storage location, retention, export format, deletion, breach notification, subcontractors, and exit assistance. Export a representative site, asset, user, tariff, session, meter, payment-reference, incident, and audit dataset before signing a long contract. A promise of API access is not a tested exit plan.

Measure service and commercial performance

Use metrics that follow the complete customer and revenue journey:

• Connector availability by service class

• Successful charge starts per valid attempt

• Payment authorization and completion rate

• Sessions with energy but no billable record

• Paid attempts with no energy delivered

• Energy delivered per connector and occupied hour

• Revenue, electricity, demand, roaming, and payment cost per session

• Fault recurrence and mean time to remote or field restore

• Data freshness for status, availability, and price

• Refunds, chargebacks, receipt requests, and support contacts

Agree calculation rules with suppliers. Exclusions, maintenance windows, low-power states, blocked bays, communication faults, and third-party failures can change an uptime figure substantially. Keep both technical availability and successful-service metrics.

Stage rollout with measurable gates

Use a controlled sequence:

1. Lab integration with charger, CSMS, payment, and roaming test environments.

2. Factory acceptance for the ordered hardware and software combination.

3. A small production pilot with real grid, telecom, merchant, and service partners.

4. Stabilization based on start success, payment, energy, incidents, and field repairs.

5. Regional deployment with standard configurations and trained service coverage.

6. Portfolio expansion only after update, spare, reporting, and reconciliation processes work at scale.

Do not define a pilot only by elapsed weeks. Set numerical or binary exit criteria for the journeys that matter, including failure recovery and financial close.

Review the Luxman public charging solution

Luxman’s public charging solution describes charging facilities, customer services, smart energy management, white-label options, and the ability to support an operator’s own network or services for other charger operators. The page also lists selected split DC equipment with POS payment, ISO 15118, Modbus TCP, and optional 4G, Wi-Fi, or Ethernet.

Use these published capabilities as a starting point for configuration discussions. Ask Luxman to confirm the exact charger models, power, connectors, outputs, firmware, OCPP functions, payment interfaces, communications, environmental requirements, standards evidence, and service scope for the target country. CSMS, payment acquiring, roaming, energy controls, local installation, regulatory reporting, and field-service responsibilities may require separate project partners or confirmation.

CPO procurement checklist

Before contract award, confirm:

• Network service classes and user promises

• Site demand, electrical capacity, charger quantity, and expansion

• Exact hardware and software configuration baseline

• OCPP and CSMS interoperability evidence

• Payment, tariff, merchant, settlement, receipt, and refund flows

• Roaming protocol, partners, identifiers, and commercial records

• Energy-management hierarchy, priorities, and safe fallback

• Monitoring, support, field response, spares, and warranty

• Cybersecurity, data ownership, API, backup, and exit rights

• Regulatory duties, technical evidence, and acceptance tests by country

• Pilot scope, success criteria, rollout governance, and change control

Frequently asked questions

What is included in a CPO EV charging solution?

It normally combines sites, electrical infrastructure, chargers, a CSMS, customer access, payment, roaming, energy management, monitoring, field service, finance, data, and compliance processes. The exact ownership model should be written into the contract.

Is a CPO the same as an eMSP?

No. A CPO operates charging infrastructure, while an eMSP usually manages a contractual service for drivers. One company may perform both roles, but the data and commercial responsibilities remain distinct.

Does OCPP provide roaming?

No. OCPP connects charging stations and charging management systems. Roaming usually requires a separate CPO-to-eMSP or hub interface such as OCPI, plus commercial agreements and identifier management.

Should a new CPO build or buy its CSMS?

The answer depends on scale, product differentiation, engineering capacity, regulatory needs, and control requirements. Buyers should compare total lifecycle cost, integration risk, data portability, and time to operate rather than license price alone.

Which CPO metric matters most?

No single metric covers the service. Successful paid charging sessions, connector availability, energy delivery, incident recovery, and reconciliation together show whether the network works technically and commercially.

How should a CPO reduce vendor lock in?

Specify open interfaces, exact protocol functions, stable identifiers, configuration access, regular data exports, documentation, transition support, credential transfer, and contract exit tests before rollout.

CPO EV charging solution conclusion

A CPO EV charging solution should be designed from the operating model outward. Clear service classes, system boundaries, identifiers, acceptance tests, field processes, and exit rights give the CPO more control than a long feature list.

To discuss a deployment, provide Luxman Energy with the countries, site types, vehicle groups, expected sessions and energy, AC and DC power, number of charging points, grid capacity, connectors, CSMS and OCPP requirements, payment and roaming model, energy-management rules, installation environment, rollout schedule, and service expectations. Luxman Energy can then confirm suitable equipment configurations and the interfaces that require project-specific integration.