OCPP (Open Charge Point Protocol) is an open communication standard that allows EV chargers to talk to a Central Management System (CMS) — regardless of who manufactured the charger or who built the software. If you're setting up public or commercial EV charging in India, understanding OCPP is important because it determines how much control you have over your chargers, how easily you can scale, and whether you're locked into a single vendor or free to choose.
What Does OCPP Actually Do?
Think of OCPP as a common language. Just as HTTP lets any web browser talk to any web server, OCPP lets any compliant EV charger communicate with any compliant management platform. The charger sends data (session details, energy consumed, fault codes, connector status) to the CMS, and the CMS sends commands back (start/stop charging, update firmware, adjust power levels).
Without OCPP, each charger manufacturer uses its own proprietary protocol. Your chargers only work with that manufacturer's software, their app, their billing system. If you want to switch software or add chargers from a different brand, you can't — or it requires expensive custom integration. OCPP removes that lock-in.
How Does OCPP Work in a Charging Session?
Here's a simplified flow of what happens behind the scenes when someone charges at an OCPP-connected station:
- Boot notification — when the charger powers on, it sends its model, serial number, and firmware version to the CMS. The CMS confirms the charger is registered and authorised to operate.
- Heartbeat — the charger sends periodic signals (every 30-60 seconds) to confirm it's online and operational. If the CMS stops receiving heartbeats, it knows the charger has gone offline.
- Authorise — when a driver taps their RFID card, scans a QR code, or starts a session via app, the charger sends an authorisation request to the CMS. The CMS checks the user's credentials and balance, then approves or denies.
- Start transaction — once authorised, the charger begins delivering power and reports meter values (energy consumed, power output, voltage) at regular intervals to the CMS.
- Stop transaction — when charging ends (user stops it, car is full, or session times out), the charger sends final meter values. The CMS calculates the bill and processes payment.
- Status notification — throughout, the charger reports connector status (available, charging, faulted, preparing) so the CMS can update apps and maps in real time.
All of this happens automatically. The CPO (Charge Point Operator) sees it on a dashboard — live charger status, session data, revenue, faults — without being physically present at the site.
Which OCPP Version Should You Use?
There are three versions you'll encounter. Here's what each brings:
OCPP 1.6 (released 2015) — the most widely deployed version globally and in India. Supports the essentials: remote start/stop, smart charging profiles, firmware updates over-the-air, basic diagnostics, and RFID/app-based authorisation. If you're starting a small to medium charging network, OCPP 1.6 covers what you need. Most chargers and CMS platforms in India today run on 1.6.
OCPP 2.0.1 (released 2020) — a significant upgrade with enhanced security (TLS encryption, mutual authentication), a new hierarchical device model (better for managing multi-connector chargers), improved smart charging with energy management system integration, consolidated transaction handling, and support for ISO 15118 (Plug and Charge). It was accepted as IEC standard 63584 in late 2024, giving it international standards body backing. New large-scale deployments are increasingly adopting 2.0.1.
OCPP 2.1 (released January 2025) — the latest version. Adds Vehicle-to-Grid (V2G) support, distributed energy resource control, and backward compatibility with 2.0.1. This is forward-looking — V2G isn't commercially active in India yet, but when it arrives, 2.1-ready infrastructure will be able to support it without hardware changes.
One important note: OCPP 2.0.1 is not backward compatible with 1.6 — it uses a completely different data structure and device model. Moving from 1.6 to 2.0.1 requires firmware upgrades on the charger and backend changes on the CMS. Most CMS platforms today support both versions to handle mixed fleets of older and newer chargers.
Why Are India's 2024 Guidelines Pushing for OCPP?
The Ministry of Power's 2024 Guidelines for Installation and Operation of EV Charging Infrastructure explicitly advise CPOs to adopt open communication protocols. The guidelines reference OCPP (for charger-to-CMS communication), OCPI (for roaming between networks), UEI (Unified Energy Interface), and OpenADR (for demand response with DISCOMs).
The key requirements from the 2024 guidelines that relate to OCPP:
- Open protocols — public charging stations are advised to adopt OCPP, OCPI, and related open standards for interoperability
- Unified payments — all public chargers must support UPI-based payments, which requires a CMS with payment gateway integration
- Real-time data sharing — chargers must share live availability data for national databases, apps, and maps. This requires the CMS to receive and publish real-time status via OCPP
- Cyber security compliance — open protocols must comply with existing cyber security provisions, which is where OCPP 2.0.1's TLS security becomes relevant
The guidelines use the word "advised" rather than "mandated" — but the direction is clear. Government subsidies under PM E-DRIVE increasingly favour CPOs who demonstrate open protocol compliance. And practically, if your chargers can't share data with the national database or support roaming, you're at a disadvantage in utilisation and discoverability.
What Problems Does OCPP Solve for Charge Point Operators?
If you're building or operating a charging network in India, OCPP addresses five specific operational problems:
Vendor lock-in. Without OCPP, your chargers only work with one manufacturer's software. If their service deteriorates, pricing increases, or the company shuts down, you're stuck — your entire network depends on one vendor. With OCPP, you can run chargers from different manufacturers on a single CMS. You can switch your CMS provider without replacing hardware. Your investment in ZEVpoint chargers isn't tied to any one software platform.
Remote monitoring and control. OCPP lets you manage your entire charger fleet from a single dashboard, without visiting sites physically. Monitor charger status and uptime, start/stop sessions remotely, push firmware updates over-the-air, set dynamic pricing, and receive instant alerts for faults and downtime. For a CPO with chargers spread across multiple locations — which is the reality for most Indian operators — this is essential.
Smart charging and load management. OCPP's smart charging profiles allow you to dynamically manage power distribution across multiple chargers at a site. This is critical in India where grid capacity at many locations is limited. You can set power limits per charger, implement time-based pricing, and balance loads to avoid transformer overload — all through OCPP commands from the CMS.
Roaming and network visibility. OCPP works together with OCPI (Open Charge Point Interface) to enable roaming — drivers from one network can charge on another network's chargers. This dramatically increases your charger visibility and utilisation. An EV driver using any OCPI-connected app (Google Maps, PlugShare, ZEVpoint, and others) can discover and use your chargers without needing your specific app or RFID card.
Scalability. Adding new chargers to an OCPP-based network is straightforward — configure the charger with your CMS endpoint, and it connects automatically via OCPP. No custom integration per charger model, no proprietary API work. This matters when you're growing from 5 chargers to 50 or 500.
What Should You Look for in an OCPP-Compliant CMS?
Not all CMS platforms are equal. When evaluating one for an Indian charging network, look for:
- OCPP 1.6 and 2.0.1 support — you'll have a mix of charger generations, and the CMS needs to handle both
- Indian payment integration — UPI is non-negotiable for public charging. Support for Razorpay, PhonePe, Google Pay, and major wallets
- Multi-location management — manage chargers across different sites, cities, and even different partners from one dashboard
- Real-time monitoring — live charger status, session tracking, energy consumption, and revenue reporting
- Smart charging profiles — dynamic load management and power scheduling to work within your site's grid capacity
- OCPI roaming — connection to national roaming networks so drivers from other apps can use your chargers
- Reliable support — a CMS provider with responsive technical support matters when a charger goes offline at a highway location at 11 PM
When Might You Not Need OCPP?
OCPP is essential for public and commercial charging networks. But there are specific situations where it may not be necessary — or where a simpler setup works fine.
Home charging. If you're installing a charger at home for your personal car, OCPP is irrelevant. Your home charger doesn't need to connect to a centralised management system, process payments from third parties, or share status with public apps. A smart charger with app control and energy monitoring gives you everything you need at home without OCPP.
Remote locations with poor connectivity. OCPP requires a reliable internet connection between the charger and CMS. In hilly regions, remote highways, or areas with inconsistent mobile data, an OCPP connection may be unreliable. In such cases, chargers that can operate in offline mode — accepting payment at a nearby reception desk (common in hotels and resorts in hill stations) or via local RFID — work better than a system that depends on constant cloud connectivity.
Very small setups. If you have one or two chargers at a single location (a small shop, a restaurant), and you're managing them yourself, the overhead of a CMS may not be justified yet. As you grow beyond a handful of chargers, the operational benefits of OCPP start outweighing the setup effort.
That said, even for these cases, buying OCPP-compliant hardware is a good practice. The charger has the capability built in — you can always connect it to a CMS later when it makes sense, without replacing the hardware.
How Does OCPP Relate to OCPI?
These two get confused often, so it's worth clarifying. OCPP is charger-to-CMS communication — how your charger talks to your management software. OCPI is CMS-to-CMS communication — how your network talks to other networks to enable roaming.
You need OCPP first (to manage your chargers), and then OCPI on top (to connect your network with others for roaming). Together, they form the backbone of an interoperable, scalable charging network. The 2024 Ministry of Power guidelines advise adoption of both.
The Bottom Line
OCPP is the open standard that ensures your EV chargers aren't locked to one vendor's software. It gives you remote management, smart charging, interoperability, and the ability to scale your network without being dependent on a single manufacturer. India's 2024 guidelines strongly push CPOs toward OCPP and OCPI adoption, and the direction is only getting firmer with PM E-DRIVE subsidy requirements and national database integration.
For CPOs building public or commercial networks, OCPP compliance is practically a baseline requirement in 2026. For home users, it's not necessary — but buying OCPP-capable hardware means you're future-proofed. Either way, the protocol itself isn't complicated. It's just the common language that makes the Indian EV charging ecosystem work together instead of in silos.
