Industries

OCPP in charger management — protocol, CPMS and platform selection

Maciej Zaleski · Published · Updated · 7 min read

OCPP enables communication between a charging station and a management system, usually called a CPMS. For an operator, it is not just the protocol version that matters, but compatibility of specific devices, the platform's feature scope, and how failures are handled. The choice between an off-the-shelf solution, a white-label model, and a custom system should follow operational processes and the network development plan.

A compatibility label on a product sheet does not settle whether a particular feature will work across the environment. The station-side implementation, device firmware version, and backend capabilities matter. An implementation plan should therefore include tests of representative configurations, not just a comparison of suppliers' commercial claims.

OCPP — a common language, not a complete platform

The protocol defines messages and behaviors that enable information exchange about stations and charging sessions. A CPMS uses this communication in the operator's processes. Its tasks may include device inventory, monitoring, remote command handling, and making data available to other applications. The scope depends on the product and deployment configuration.

OCPP should not be equated with complete payment, roaming, or invoicing support. Those areas require additional mechanisms and integrations. The ability to start a session remotely does not yet mean the system will correctly serve the customer, settle the transaction, and investigate a complaint. The architecture should separate device communication from commercial processes.

For a CPO, or charge point operator, predictable operations are fundamental. They need to know which device requires intervention, what happened during a session, and who is responsible for solving a problem. The protocol provides some data, but interpreting it and organizing work remain tasks for the system and team.

OCPP 1.6 versus 2.0.1 — differences relevant to the decision

OCPP 1.6 and 2.0.1 are separate protocol versions that should not be treated as interchangeable without compatibility checks. Version 2.0.1 expands, among other things, the device management model, security handling, and features related to advanced charging scenarios. However, the actual scope available to the operator depends on implementation on both sides.

Version 1.6 may be an appropriate part of an existing network if it meets the operational and security requirements of the specific deployment. Do not assume choosing a newer version will itself solve maintenance problems. On the other hand, hardware procurement plans should account for future requirements so development possibilities are not limited to an arbitrarily selected configuration.

Area OCPP 1.6 OCPP 2.0.1
Compatibility Verify the specific implementation Verify device and backend separately
Device management Scope depends on supported features Expanded device model
Security Assess deployment profiles and capabilities Enhanced security mechanisms
Purchasing decision Match current needs Match planned architecture

Prepare a feature matrix rather than just a list of versions. For each charger model, check authentication, meter reporting, diagnostics, updates, and remote commands. Record required firmware and configuration. If a feature depends on an additional module or license, this should be visible before signing the contract.

Monitoring should lead to action

A dashboard listing stations is not enough to manage a network. An operator needs to distinguish lost connectivity, device faults, individual connector problems, and missing expected data. Define a priority and response for each event. Too many alarms without context lead to notifications being ignored.

The freshness of the displayed state matters. Information received before connection loss should not look like current confirmation of availability. The dashboard should show the last communication time and status source. Likewise, the absence of an active session does not prove a device is ready for the next driver.

Retain the history needed for diagnostics, but control its scope and access. Linking device events to sessions and operator actions helps establish the cause of a complaint. Technical data should share identifiers and consistent timestamps so the team does not have to manually join incomparable records from several systems.

Remote management requires safeguards

Commands such as restart or configuration change should be available to appropriate roles, with execution logged. For important operations, include user confirmation and a reason for the action. Not every failure should trigger an automatic restart, especially if this could interrupt service to a driver.

Separate sending a command, the device accepting it, and achieving the expected state. No response requires a different interpretation from an explicit rejection. Retries must account for the risk of repeated execution. The operator interface should clearly show these stages rather than display a generic success message.

Plan firmware updates around the manufacturer's capabilities, file signing, and recovery procedures. Test representative devices first, then expand the rollout. Define certificate and credential management separately. Even a good platform cannot fix a lack of control over station service access.

White-label or your own CPMS

A white-label platform may let you use an existing product under your own brand, but the scope of customization requires confirmation. Changing a logo does not mean processes can be modified arbitrarily. Check APIs, data export, integrations, permission models, and product updates. Also establish how the relationship ends and devices are transferred.

A custom system offers greater control over development but means responsibility for protocol maintenance, security, device tests, and operator processes. This is a product requiring ongoing work, not a one-off integration. Specific processes or business advantages that cannot reasonably be achieved by configuring an available platform may justify it.

Go2ops develops go2ev.com, an OCPP 1.6 charger management platform for CPOs. Feature scope, device fit, and any white-label model must be confirmed in a requirements discussion; they do not automatically follow from the protocol description alone. We present the context of industry projects in our energy and e-mobility area.

Integrations and platform infrastructure

A CPMS can exchange data with CRM, ERP, a driver app, or analytics tools. In every case, establish the source of truth, identifiers, and correction handling. Settlement should not depend solely on a single message without a way to reconcile session history. The article on ERP system integration describes broader principles.

Backend maintenance affects service availability, monitoring, and operating costs. Backups, recovery tests, permission controls, and a plan for increased traffic are needed. Infrastructure criteria appear in our cloud and on-premise comparison. If you need unusual processes, assess their justification before starting custom software development.

Projects involving user data, payments, or infrastructure requirements need a separate compliance analysis. Current regulations and obligations applicable to the business model should be verified with a specialist. Communication protocol compliance does not confirm fulfillment of all the operator's legal or contractual requirements.

How to accept the solution before deployment

Prepare normal-operation and failure scenarios for representative device models. Check connection loss, station restart, delayed messages, and reconnection. Acceptance criteria should include consistent session history and correct operator response, not just establishing a technical connection.

Document configurations, limitations, and escalation responsibility. Establish contacts for the device manufacturer, platform owner, and field team. This prevents tickets circulating between parties without diagnosis. Repeat acceptance tests after significant firmware or backend changes, because compatibility applies to a specific set of versions.

FAQ

Does every OCPP charger work with every CPMS?

Do not assume so. Versions, supported features, and security configurations must be compatible. Testing a specific model and firmware is a more reliable basis for a decision than a protocol label in an offer.

Does OCPP 2.0.1 replace 1.6 without changes?

This is not a simple version-number substitution. Confirm support on both the station and backend sides and plan tests. Migrating an existing network may depend on hardware and manufacturer capabilities.

Does a CPMS solve all billing issues?

Not automatically. The scope depends on the product and integrations. Check how sessions enter commercial processes, how corrections are handled, and who investigates discrepancies. The protocol alone does not define the entire business model.

When is it worth building your own platform?

When specific requirements justify long-term product responsibility. First compare available solutions with actual processes. Custom development also requires a budget for maintenance, compatibility tests, and incident handling.

Summary

Choose a platform based on operator processes, device tests, and maintenance capabilities. Protocol version matters but does not replace complete architecture. Go2ops can help discuss CPMS requirements and assess whether the right direction is an existing platform, integration, or dedicated development.

MZ

Maciej Zaleski

Managing Director, Go2ops

Related articles