The three names describe different communication boundaries. OCPP connects charging stations to charging-management software; OCPI commonly exchanges information between charging-network businesses; ISO 15118 covers high-level communication between an electric vehicle and charging equipment. A building may need one, several, or none of these interfaces. A standard’s existence does not show that a particular car, charger, network, meter, or payment service will work with another.
The protocols serve different connections
| Protocol | Main communication boundary | What it may help a building do | What the name alone does not prove |
|---|---|---|---|
| OCPP, the Open Charge Point Protocol | Charging station to its charge station management system (CSMS) | Report status and transactions, receive management commands, and use supported smart-charging or security functions. | That the exact charger and CSMS implement the same version, optional features, certificate scope, or building workflow. |
| OCPI, the Open Charge Point Interface | Commonly charge point operators and e-mobility service providers | Exchange roaming-related location, tariff, token, session, and charge-detail information when the parties implement the needed modules. | That a residents-only building needs roaming, or that its billing, payment, or network partners support the desired exchange. |
| ISO 15118 | Vehicle and EV supply equipment communication controllers | Support selected vehicle-to-equipment functions such as digital identification, Plug & Charge, or bidirectional use when the vehicle, charger, and service are designed for them. | That a specific vehicle, station, certificate service, or building system supports those functions or has been approved for power export. |
Think of these as links between parts of a wider system rather than as three competing charger features. For example, Plug & Charge may depend on a vehicle and station exchanging credentials, an authorization service trusting them, and the charging network correctly recording the session. OCPP, OCPI, and ISO 15118 may each play a part, but they do not collapse those parties into one guaranteed connection. A building energy-management system may also have a local interface to an EVSE controller through a resource manager. IEC 63380-3 describes one such interface; it is separate from station-to-CSMS OCPP and does not establish support in a particular product pair. Specify and test that local connection independently when the project needs it.
Ask for an implementation, not a label
Ask the seller to state, in writing:
- the exact protocol version and edition for each station and software service;
- which required profiles and features are implemented, and which are optional or unavailable;
- the firmware and backend versions covered by any certificate or test report;
- whether the exact station-to-CSMS pairing has been tested by an independent lab and again in the proposed configuration;
- for OCPI, the core and module release, each party’s role, the counterparties, fields, and exchanges the system actually supports;
- which party operates each identity, roaming, tariff, session, meter, and payment interface;
- what data moves across the interface and which party can export it.
OCPP versions are not interchangeable by name. The Open Charge Alliance says OCPP 1.6 and 2.0.1 are not compatible, while 2.1 builds on 2.0.1 and retains its application logic. The current downloads include OCPP 2.1 Edition 2 and OCPP 2.0.1 Edition 4. September 2026 errata for both editions were published on 7 October 2026, so ask the vendor to identify the edition and exact errata used in its implementation, specification, and test evidence. A version label alone does not identify the functions or corrections tested.
Review evidence in sequence: the interface specification; the implemented edition, modules, and firmware; the exact product and certificate scope; the protocol-test report and cases run; and finally a composed test of the resident workflow. A result at one level does not prove the next level.
For a CSMS on a current EVCAN listing, read the capability evidence as CSMS-specific. The application process distinguishes required capabilities supported by public or customer-provided evidence from reported capabilities that receive a broader review. That status does not establish EVSE hardware approval, local EMS support, or acceptance of the exact building deployment. Ask for the current listing and evidence, then test the station, local-control interface, and resident workflow you will use.
Certification is useful evidence with a boundary. OCA’s certification page, checked on 9 November 2026, displayed OCPP 1.6 and 2.0.1 as available certification versions; it did not state whether that list was exhaustive for newer editions. Verify the current certified-products directory and the exact certificate, edition, profile, product, firmware, and software. In OCA’s product-family program, one representative product is tested at an official OCA laboratory; other listed family members can be added through a Vendor Declaration of Conformance that the vendor tests using OCTT, without separate lab testing of each member. Confirm whether the proposed model is the representative or a declared family member and request the applicable evidence.
OCA’s current OCTT Suite page lists OCPP 1.6, 2.0.1, and 2.1 for both OCTT Starter and Professional. Starter provides core test cases, while Professional includes all test cases. OCA announced OCPP 2.1 testing in Professional on 12 October 2026. The suite page’s separate 14-day trial description still lists selected OCPP 1.6 and 2.0.1 cases. Ask which tier, test-set version, and specific cases a supplier used. OCTT reports protocol-conformance results but does not issue an OCA certificate by itself, and its predefined scenarios do not simulate the whole charging service. Ask for the dated report, exact test cases, role tested (station or CSMS), product and firmware, failed or skipped cases, and any remaining scenarios or vendor declarations. Then test the composed resident workflow with the proposed EVSE, CSMS, vehicle, identity, roaming, payment, and support services.
Test the whole resident journey
A contract should name the actual system behavior that matters. Ask for a witnessed acceptance test using the selected station model, firmware, CSMS, network connection, and resident access method. Include:
- A resident starts and ends a session and receives the expected status, meter/session record, and receipt.
- A second compatible account or vehicle is authorized using the intended method.
- A station reports its state and an agreed session record to the right building or network system.
- A load limit or scheduled control request reaches the equipment; check the accepted command and configured setpoint separately from observed current, power, or metered energy. Agree who defines safe limits and failure behavior.
- A loss of internet or backend service produces the agreed local behavior, safe stop, or fallback, and the resident can reach the named support channel.
- A software restart or certificate change leaves the approved resident journey usable.
- If roaming or Plug & Charge is required, the test follows authorization through the vehicle, station, backend, service provider, and final session record. For Plug & Charge, include a TLS profile or version mismatch, recovery, and regression after a certificate-library update where the selected products support those cases.
- If a supplier change is likely, a test station connects to the proposed replacement CSMS and returns usable records.
ISO 15118-21:2025 defines conformance tests for communication controllers implementing ISO 15118-20. Those tests cover protocol capabilities and behavior, but not performance, robustness, reliability, physical implementation, or power flow. Confirm the edition, profile, and exact controller tested when reviewing a supplier’s report.
If the proposed service uses Plug & Charge, ask who owns and operates its certificates and trusted-party configuration, how expiry, renewal, and revocation are handled, and what happens after a failed certificate check. Assign an owner for the fallback and test it with the offered vehicle, station, backend, and support path. Include profile/version mismatch and recovery cases only for the selected implementation, then rerun them after relevant certificate-library updates. The National Laboratory of the Rockies and Sandia PKI test-plan workbook can help frame certificate and revocation cases; it is a planning aid, not completed test results or product certification.
Offline access also needs exact-product testing. For example, Bender’s current OCPP implementation notes say its controller uses a fixed local authorization list: it may accept SendLocalList without changing that list, while offline authorization remains available. This is a manufacturer-specific behavior, not an OCPP-wide rule. Before procurement, test adding, removing, and revoking the credentials residents will use, first while connected, then offline, and again after reconnection; record the expected result for the exact model and firmware.
OCPI availability is version- and module-specific too. As checked in November 2026, the steward lists version 2.3 as available and says OCPI 3.0 is awaiting CENELEC review, with H2 2027 only an expected release window. Do not contract against 3.0 as a released interface; confirm the current release, roles, and modules with both parties when procuring.
CharIN’s 2025 Testival reports describe composed EV, charging-station, backend, Plug & Charge, and roaming tests, including session authorization and charge-detail-record reporting. Use these as examples when designing a building’s own test; they are not an apartment-specific requirement, a universal test suite, or product certification.
Choose by the service promise
A building that needs residents to identify themselves and see their session history may not need public roaming. A site that deliberately serves visitors or the public may need additional access, payment, data, and regulatory checks. A project considering managed charging needs a defined control interface and collaboration with its electrical and energy teams. A project considering bidirectional charging needs separate vehicle, EVSE, building, grid-interconnection, and safety review.
Use the network requirements checklist to define the system, and the privacy checklist and vendor exit guide for cross-system duties. If the network’s energy records will support a resident kWh charge, also check the relevant U.S. metering guide or Canadian approval guide. A standard is a starting specification; compatibility is a result to demonstrate.
Checked: 9 November 2026. Published protocol versions, test-tool coverage, certification scopes, and errata change; verify current documents and exact product evidence before procurement.