EV Charging Management Software Review: Evaluating Charge Point Management Systems

The charge point management system (CPMS) — the software that manages EV chargers — is as important as the charger hardware itself. A CPMS provides the intelligence that transforms a simple power outlet into a managed charging asset: smart scheduling, load balancing, user authentication, billing, reporting, and integration with fleet management and energy management systems.

The CPMS market has grown rapidly alongside EV adoption, and the quality and focus of available platforms varies significantly. This review provides a structured evaluation framework for CPMS selection, covering the technical capabilities and operational features that differentiate platforms for parking facility and fleet applications.

Evaluation Framework: What Matters for Parking Applications

OCPP Compliance Depth

OCPP (Open Charge Point Protocol) compliance is the interoperability standard that allows hardware and software from different vendors to work together. But “OCPP compliant” doesn’t mean the same thing for every platform:

OCPP 1.6 compliance covers basic charging operations: start/stop sessions, meter readings, status notifications, firmware updates. Most platforms claiming OCPP compliance support 1.6.

OCPP 2.0.1 compliance adds security (mandatory TLS), enhanced smart charging profiles, ISO 15118 integration (Plug & Charge), and improved transaction management. OCPP 2.0.1 is the current-generation specification and the appropriate requirement for new deployments.

Compliance depth: Which OCPP feature profiles are implemented? The Core profile is mandatory; Smart Charging, Firmware Management, Local Auth List Management, and Remote Trigger profiles vary by platform. A platform that implements only the Core profile is OCPP 1.6 compliant but lacks the smart charging capabilities that deliver the primary operational value.

Verify OCPP compliance through the OCA (Open Charge Alliance) certification list, not vendor marketing materials.

Smart Charging Capabilities

Smart charging — adjusting charging rate and schedule to optimize for cost, grid impact, or vehicle readiness — is the primary value differentiator among CPMS platforms for parking applications.

Load management evaluation:

• Can the CPMS impose a total power limit across all charge points at a facility and automatically distribute available power?
• Does load management respond in real time to facility electrical demand (not just a static schedule)?
• Can individual chargers be assigned different priority levels (fleet vehicles prioritized over employee personal vehicles)?
• What happens during a communications outage between the CPMS and charge points — do chargers fall back to a safe default, or do they stop charging?

Scheduling and charging profiles:

• Can charging schedules be configured at the facility level? The charger level? The individual vehicle/account level?
• How granular is the scheduling resolution (hourly? 15-minute intervals?)
• Are TOU (time-of-use) rate inputs supported for cost-optimized charging?
• Does the platform support demand charge management (tracking the facility’s demand curve and constraining charging to avoid demand spikes)?

User Authentication and Access Control

CPMS user authentication determines who can charge and how costs are attributed:

RFID card authentication: The most widely deployed authentication method — drivers tap an RFID card to authorize charging. Evaluate whether the CPMS supports card management (issuing, deactivating, reporting by card) or requires a separate card management system.

Mobile app authentication: Many CPMS platforms include or integrate with consumer-facing apps for charging authorization and session management.

Autocharge / Plug & Charge: ISO 15118-based automatic authentication upon plug connection (no user action required). Requires ISO 15118 support in both vehicle and charger; CPMS must support ISO 15118 PKI certificate management.

Open access: Some facilities provide open charging (no authentication required), particularly for visitor or public charging. The CPMS should support configurable access control per charger, not a global policy.

Billing and Payment Integration

For facilities charging for electricity use:

Revenue-grade metering: Verify that the CPMS reports energy delivery from revenue-grade meters (ANSI C12.20 accuracy or equivalent) if you bill by kWh. Informational-grade metering (±5%) is not appropriate for commercial billing.

Payment processing integration: Does the CPMS integrate with your existing payment processing infrastructure, or does it require a proprietary payment platform? Proprietary payment requirements may conflict with your existing accounting workflows.

Billing model flexibility: Per-kWh, per-minute, flat session fee, and free charging are the primary billing models. Verify that the CPMS supports the billing model you want, particularly per-kWh billing if you plan to charge for energy delivered.

Tenant and fleet cost allocation: For facilities with multiple cost centers (fleet department, HR employee benefit, visitor parking), does the CPMS support cost allocation by user group, account, or RFID card pool?

Reporting and Analytics

Operational reporting: Session volume, energy delivered, uptime, utilization rate, and fault reporting are minimum operational reports. Evaluate whether these are available on demand or only as scheduled batch reports.

Energy and cost reporting: kWh delivered by charger, session, time period, and user/account. Cost tracking if TOU rates are configured. These reports are necessary for cost allocation and ROI tracking.

Grid and demand charge visibility: For facilities managing demand charges, reports that show the charging contribution to facility demand peaks are necessary for understanding the financial impact of the CPMS’s demand management performance.

Integration with Parking Management Systems

For parking facilities deploying EV charging alongside parking access control and revenue management, CPMS integration with the PARCS is a significant operational simplification:

• Can EV charging sessions be linked to parking sessions (same payment method, single transaction)?
• Does the PARCS know which permit holders have EV charging entitlements?
• Can charging access be controlled through the same credential (RFID, mobile app, LPR) as parking access?

Platforms with native PARCS-CPMS integration eliminate the need for separate accounts and payment methods for parking and charging.

Fleet Management Integration

For fleet charging applications, evaluate:

• API integration with fleet management systems (Geotab, Samsara, Fleet Complete)
• Vehicle-level state of charge reporting
• Charging event notifications to fleet management
• Pre-condition scheduling (pre-heating/cooling the vehicle before departure)

Vendor Assessment Criteria

Network and Platform Availability

CPMS downtime means charging management is unavailable — chargers may continue operating in offline mode, but smart charging, authentication, and reporting stop. Evaluate:

• Published uptime SLA (99.9%? 99.95%?)
• Historical uptime data (request actual incident history, not just the SLA)
• Multi-region redundancy architecture
• Offline operation behavior of charge points during CPMS outage

Certification and Compliance

• OCPP certification by Open Charge Alliance
• For payment-enabled deployments: PCI DSS compliance for payment data handling
• Utility demand response: OpenADR 2.0 compliance for grid integration programs

FAQ

What is the difference between a CPMS and an EMSP? A Charge Point Management System (CPMS) manages the operational back-end of charge points — smart charging, load management, hardware monitoring, and local billing. An e-Mobility Service Provider (EMSP) manages the driver-facing service — account management, payment processing, roaming across multiple charging networks. In simple deployments, a single platform may serve both functions. In complex deployments (public charging networks, multi-operator roaming), CPMS and EMSP roles may be served by different platforms using the OCPI (Open Charge Point Interface) protocol for roaming interoperability.

Can a CPMS support both AC Level 2 and DC Fast Charge equipment? Yes — most enterprise CPMS platforms support both EVSE types through OCPP. The smart charging profiles for DC fast chargers are more complex (higher power levels, different power management dynamics), so verify that DC fast charge smart charging is specifically tested, not just theoretically supported.

How should parking operators handle the situation where a vehicle is plugged in but not actively charging (blocking a charge point)? Most CPMS platforms support idle fees — additional charges that begin after the charging session completes and the vehicle remains plugged in. This discourages session hogging that reduces charger utilization. Configure idle fees in the CPMS rate settings; display the idle fee policy clearly on charger signage and in the app to manage driver expectations.

What customer support quality is critical for CPMS vendors in commercial parking applications? EV charger faults that prevent charging generate immediate driver complaints and, for fleet applications, may prevent vehicle deployment. CPMS vendors supporting commercial applications should offer 24/7 critical issue support with response time SLAs for hardware fault alerts. Ask specifically: “What is your process when a charger goes offline at 2 AM on a Sunday before a fleet dispatch at 6 AM Monday?” The answer reveals support quality more than any SLA document.