Open Protocols: OCPP & OpenADR
Open-protocol requirements exist to protect the buyer: a charger that speaks OCPP can change networks; a charger that speaks OpenADR can participate in utility demand-response programs. Program administrators write these requirements into eligibility rules so public money doesn't buy stranded assets.
Speak To An Expert- Kind
- Standing requirement
- When it applies
- Many utility make-ready and state grant programs require open-protocol, non-proprietary networked chargers as an eligibility condition; NEVI adds its own protocol requirements under 23 CFR 680.108.
- Whose obligation
- The manufacturer and network provider — this is one requirement that is squarely the vendor's to meet.
- ZEF's status
- The ZEFNET platform supports OCPP 1.6, OCPP 2.0.1, ISO 15118, OpenADR 2.0b, and OCPI 2.2.1.
Why programs require open protocols
OCPP (Open Charge Point Protocol, maintained by the Open Charge Alliance) standardizes communication between a charger and its network platform. Its practical value is exit rights: OCPP hardware can be re-pointed to a different network if the vendor relationship, pricing, or service quality changes. Utility make-ready programs and state grants increasingly require OCPP for exactly that reason — public and ratepayer money should not purchase hardware held hostage by a proprietary network.
OpenADR standardizes utility demand-response signaling. A charger platform that supports OpenADR 2.0b can receive utility load-management events — which is what makes chargers grid assets rather than just loads, and what qualifies them for the managed-charging rates and demand-response programs that many utilities now offer.
Where this shows up in requirements
As a standing matter, utility interconnection and make-ready program rules frequently condition rebates on open-protocol, networked equipment — each state page on this site notes utility-specific requirements where they exist. As a funding-attached matter, NEVI projects face the specific protocol stack of 23 CFR 680.108, which goes further than a general OCPP requirement.
ZEF's factual position: ZEFNET supports OCPP 1.6, OCPP 2.0.1, ISO 15118, OpenADR 2.0b, and OCPI 2.2.1, and ZEF has 80+ utility partners running programs on the platform. For NEVI-funded specs, ask ZEF for § 680.108 conformance documentation for your specific project.
Frequently asked questions
Why do grant programs care what protocol a charger uses?
To prevent stranded assets. OCPP-compliant chargers can switch network providers; proprietary-network chargers can become unusable if their vendor fails or raises prices. Program administrators require open protocols so funded hardware outlives any single vendor relationship.
What does OpenADR add beyond OCPP?
OCPP connects the charger to its management network; OpenADR connects the platform to the utility for demand-response signaling. OpenADR support is what enables participation in utility managed-charging and load-management programs — often with better rates.
Not sure what applies? Ask.
ZEF has helped 80+ utility partners and 200+ cities and agencies fund, buy, and deploy compliant EV charging. Bring us your project and funding questions.
Speak To An Expert Or email solutions@zefenergy.com · call 1-888-493-3638