A scalable CPMS architecture is the design of a Charge Point Management System (CPMS) that can reliably grow from managing a small number of chargers to managing thousands of EVSEs, high session volumes, many tenants, and multiple integrations—while maintaining strong uptime, security, and billing accuracy.
A CPMS is the “brain” that connects chargers (via OCPP), users and payments, operations workflows, and interoperability (via OCPI). A scalable architecture ensures the platform continues to perform as device count, data volume, and complexity increase.
Why Scalability Matters for a CPMS
As charging networks scale, the CPMS must handle:
– More chargers and concurrent connections (heartbeats, meter values, status notifications)
– Higher session throughput (authorizations, starts/stops, CDR generation)
– More pricing logic (tariffs by site, time-of-day, memberships, roaming)
– More stakeholders (operators, installers, site hosts, finance, support)
– More data (telemetry, logs, billing, reporting, compliance evidence)
If CPMS scalability is weak, the results are operational pain: slow portals, failed session starts, missed CDRs, settlement disputes, and higher revenue leakage.
Core Building Blocks of a Scalable CPMS
A scalable CPMS typically includes these architectural components:
– Device connectivity layer (OCPP gateway)
– Handles charger connections, authentication, message routing, and retries
– Supports OCPP 1.6 and/or 2.0.1 with secure configuration
– Event-driven processing
– Converts charger messages into durable events and processes them asynchronously
– Helps absorb traffic spikes (rush hours, firmware rollouts)
– Session and transaction services
– Authorize users (RFID/app), start/stop sessions, calculate costs, generate CDRs
– Enforces idempotency (avoid double-billing) and consistent state handling
– Tariff and billing engine
– Pricing rules (per kWh, per minute, idle fees, minimum fees, memberships)
– Supports gross vs net accounting definitions for revenue reporting
– Payments and invoicing
– Payment gateway integration, wallets, invoices, refunds, chargebacks
– Strong reconciliation logic (sessions ↔ payments ↔ settlements)
– Roaming and interoperability
– OCPI modules for tokens, locations, tariffs, sessions, and CDR exchange
– Partner monitoring and dispute workflows
– Operations and monitoring
– Fault detection, alarms, ticketing integration, uptime dashboards
– Firmware management, configuration templates, remote commands
– Identity and access
– RBAC with tenant/site scoping (multi-tenant charging)
– Audit trails for sensitive actions (tariff edits, refunds, remote commands)
– Data platform
– Operational database for real-time state + analytics warehouse for reporting
– Time-series storage for telemetry (optional) and log retention policies
Key Scalability Patterns Used in CPMS
– Horizontal scaling of OCPP gateways and API services (stateless services behind load balancers)
– Message queues / streaming for decoupling ingestion from processing (spike resilience)
– Idempotent APIs and unique transaction identifiers to prevent duplicates
– Partitioning/sharding by tenant, region, or charger group for performance isolation
– Caching for frequently accessed data (tariffs, token status, charger metadata)
– Backpressure and rate limiting to protect critical services during storms
– Blue/green or canary deployments to reduce risk during releases
– Observability: metrics, traces, structured logs, alerting, and SLOs
Multi-tenant Scalability (B2B Reality)
For OEMs and platform operators, multi-tenant support is a common requirement:
– Tenants separated by data boundaries (sites, users, tariffs, reports)
– Tenant-level admin roles and scoped access via RBAC
– Per-tenant integrations (payment providers, roaming partners, webhooks)
– Reporting segmented by tenant while supporting operator-level rollups
This prevents one tenant’s volume or misconfiguration from impacting others.
Reliability and Data Integrity Requirements at Scale
A scalable CPMS must prioritize correctness under failure conditions:
– Offline behavior handling (late session sync, delayed meter values)
– Exactly-once billing outcomes (no duplicates, no missing CDRs)
– Strong reconciliation to detect missing sessions, failed payments, and roaming gaps
– Safe remote command handling and secure credential management
– Disaster recovery plans and data backups for financial records
KPIs That Indicate CPMS Scalability
– Authorization success rate and session start success rate at peak times
– Message processing latency (OCPP events to portal visibility)
– CDR generation timeliness and acceptance rate (especially roaming)
– Portal/API response times under load
– Uptime and mean time to recover (MTTR) during incidents
– Billing accuracy (low refunds/chargebacks, low revenue leakage)
Related Glossary Terms
Charge Point Management System (CPMS)
OCPP
OCPI
Role-based access control (RBAC)
Multi-tenant charging
Revenue reporting
Revenue leakage detection
Uptime
Network performance KPIs
Incident response plan