OCPP, OCPI and ISO 15118 for charging site owners
Summary
OCPP is the protocol between a charger and the software that manages it; OCPI connects that management software to other networks and driver apps; ISO 15118 handles communication between the car and the charger. An owner who buys chargers certified for OCPP 2.0.1 and keeps the administrator credentials can move to a different back-end without replacing hardware. New York's Make-Ready Program now requires OCPP 2.0.1 and ISO 15118 for DC fast charging and ties funding to data reporting, so the choice affects incentive eligibility as well as operations.
Three layers of communication
- Car to charger: ISO 15118 and IEC 61851. ISO 15118 enables Plug and Charge, in which the car identifies itself and the session starts without a card or app.
- Charger to back-end: OCPP (Open Charge Point Protocol), published by the Open Charge Alliance (opens an external site). The back-end is the charging station management system, or CSMS, that starts sessions, sets prices, updates firmware and collects data.
- Back-end to other networks and apps: OCPI (Open Charge Point Interface) (opens an external site), which lets a driver's app or card from another network work at your charger.
- Back-end to the utility and incentive programs: demand response signals, such as OpenADR, and the data reporting that programs require.
A charger does not support OCPI. OCPI runs between servers, not in the charger: the charger controller implements OCPP, and the back-end implements OCPI. Charger controllers made for export commonly advertise OCPP 1.6J and, increasingly, OCPP 2.0.1; the claim is checked against the Open Charge Alliance's certified product list for the specific model.
OCPP versions
| Version | Released | What it adds | Note for owners |
|---|---|---|---|
| OCPP 1.6 (1.6J is the JSON variant) | 2015 | Core remote control, metering and basic smart charging | Most widely installed; does not meet the Make-Ready DC fast charging or NEVI requirements |
| OCPP 2.0.1 | 2020 | Device management, stronger security, ISO 15118 support | Not backward compatible with 1.6; approved as IEC 63584 in 2024; required by Make-Ready and NEVI |
| OCPP 2.1 | 2025 | Bidirectional charging (V2X) and ISO 15118-20 features | Builds on 2.0.1 while keeping its application logic compatible |
Some hardware sold as OCPP 1.6J cannot be upgraded to 2.0.1 in the field. Because Make-Ready DC fast charging and NEVI require 2.0.1, ask before buying whether the exact model ships with 2.0.1 or has a confirmed upgrade path.
What lock-in looks like
Lock-in is rarely a single clause. It is a combination of technical and contract terms that together make changing providers expensive. None of the items below is specific to one company.
- Firmware that works only with one cloud service, or a CSMS address the owner cannot change.
- Administrator credentials held only by the vendor.
- A warranty that is void if the charger is connected to a different back-end.
- No right to export session, revenue and uptime data in a standard format.
- Multi-year prepaid software plans without termination assistance.
Checks before buying, terms before signing
Before buying, verify six things about the exact model: OCA certification, rather than a brochure statement that the charger is OCPP compliant, because partial implementations can break smart charging and remote firmware updates; the OCPP version and which certified functions are included, such as smart charging profiles, which allow a site power cap to control demand charges; the security profile supported and how firmware updates are delivered and signed; who holds the administrator login and who can change the CSMS address setting; for DC chargers, ISO 15118 hardware and software conformance, which Make-Ready and NEVI require; and a wired Ethernet option for garages and basements where cellular coverage is weak.
The contract should then state the following.
- Owner-held administrator credentials and the right to change the CSMS address.
- Data export in a standard format, on request and at termination.
- Termination assistance, including a defined period of cooperation when moving to a new back-end.
- A statement that switching back-ends does not void the hardware warranty.
- Uptime and utilization reporting in the format the incentive programs require, since that reporting is now a condition of funding in New York.
New York and federal requirements
The Make-Ready Program (opens an external site) requires DC fast charging stations to use OCPP 2.0.1 or later and to have ISO 15118 hardware and software conformance. Since the 2026 program changes, projects must use a network service provider on the Eligible NSP List, and providers must meet a 90% data-reporting threshold to stay on it. Participants who switch network providers or replace equipment must notify their utility within 30 days. Make-Ready DC fast charging applications have been paused since April 22, 2026 and may reopen once data-reporting compliance plans are approved. NYSERDA's Charge Ready NY 2.0, for Level 2, likewise accepts only chargers and networks on its eligible lists.
For federally funded NEVI sites, 23 CFR 680.108 (opens an external site) requires chargers to conform to OCPP 2.0.1 and ISO 15118, requires networks to communicate with other networks through OCPI 2.2.1, and requires chargers to be able to switch network providers securely without any hardware changes. The federal rule treats the ability to change networks as a basic requirement, and it is a reasonable standard for private sites as well.
We commission chargers on the back-end the owner chooses, record the configuration and hand over the administrator credentials, so the station belongs to the owner rather than to a subscription. Electrical installation is performed by licensed partner electricians, and network cabling comes through our low-voltage service.
Frequently asked questions
What is the difference between OCPP and OCPI?
OCPP connects a charger to the software that manages it. OCPI connects that management software to other networks and apps, so drivers from other networks can use the charger. A charger implements OCPP; OCPI runs on the back-end servers.
Can I switch charging networks without replacing my chargers?
Yes, if the chargers are certified for a current OCPP version, you hold the administrator credentials and the contract allows it without voiding the warranty. If a Make-Ready project is involved, notify the utility within 30 days of the change.
Is OCPP 1.6J still acceptable?
It works for many private uses, but New York's Make-Ready Program, for DC fast charging, and federal NEVI rules require OCPP 2.0.1. Some 1.6J hardware cannot be upgraded in the field, so confirm the version before buying.
How can I tell whether a charger is really OCPP certified?
Look up the exact model on the Open Charge Alliance's certified product list. A brochure statement that a charger is OCPP compatible does not mean it has passed certification testing.
Sources
5 sources
- Open Charge Point Protocol (OCPP) (opens an external site)Open Charge Alliance
- 23 CFR 680.108 - Interoperability of electric vehicle charging infrastructure (opens an external site)Legal Information Institute, Cornell Law School
- 23 CFR 680.114 - Charging network connectivity of electric vehicle charging infrastructure (opens an external site)Legal Information Institute, Cornell Law School
- EV Make-Ready Program Amended Participant Guide (updated July 13, 2026) (opens an external site)Joint Utilities of New York
- EVRoaming Foundation (OCPI) (opens an external site)EVRoaming Foundation
This guide reflects our experience and our interpretation of the rules as of the date it was published or last updated. Regulations, codes, incentives and the way agencies enforce them change often, and our interpretation may be incomplete or wrong. It is general information, not legal, engineering, tax or financial advice. Consult the relevant agency and a licensed professional before you plan, purchase or begin any work. Reading this guide does not make you our client and does not create any contractor, consulting or advisory relationship. Outstanding Construction Inc is not liable for any loss arising from the use of or reliance on this content, and is responsible only for work performed under a written contract signed with us.