Cal. Code Regs. tit. 20, § 3125
Additional Requirements for Networked Publicly or Ratepayer Funded Chargers.
Effective Apr 1, 2026Register 2026, No. 11Authority cited: Sections 25210, 25213, 25216.5, 25218(e), 25231.5, 25301, 25302, 25303, 25304, 25305, 25400, 25401, 25601, 25602 and 25618, Public Resources Code. Reference: Sections 25210, 25216.5, 25229, 25231.5, 25300, 25301, 25302, 25303, 25304, 25305, 25324, 25400, 25401, 25601, 25602 and 25618, Public Resources Code.State of California
(a) For networked publicly or ratepayer funded chargers installed on or after September 28, 2026, the recordkeeping and reporting agent as designated pursuant to section 3122, shall ensure the charger meets the following requirements:
- (1) The charger has Subset Certification in the Open Charge Alliance OCPP Certification Program for OCPP version 2.0.1, edition 3, published May 06, 2024, for Core and Advanced Security functionalities.
(2) The charger and Central Management System transmit the following protocol data units as specified in OCPP:
- (A) AuthorizeRequest shall be transmitted to the Central Management System by the charger as specified in OCPP.
- (B) AuthorizeResponse shall be transmitted by the Central Management System to the charger as specified in OCPP 2.0.1.
- (C) HeartbeatRequest shall be transmitted to the Central Management System by the charger on a set interval.
- (D) HeartbeatResponse shall be transmitted to the charger by the Central Management System in response to any received HeartbeatResponse.
- (E) StatusNotificationRequest shall be transmitted by the charger to the Central Management System as specified in OCPP 2.0.1.
- (F) BootNotificationRequest shall be transmitted by the charger to the Central Management System any time the charger is powered on.
- (G) BootNotificationResponse shall be transmitted by the Central Management System to the charger in response to any received BootNotificationRequest.
- (H) RequestStartTransactionRequest shall be transmitted by the Central Management System to the charger as specified in OCPP 2.0.1.
- (I) NotifyEventRequest shall be transmitted by the Central Management System to the charger as specified in OCPP 2.0.1.
(J) TransactionEventRequest shall be transmitted to the Central Management System by the charger as specified in OCPP 2.0.1.
- 1. The optional field meterValue must be populated when the eventType field is set to either “Started” or “Ended.”
- 2. When populated, the sub-subfield Value of the subfield SampledValue of the field meterValue shall be transmitted in Watt-hours (Wh).
- 3. When populated, the sub-sub-subfield unit of the sub-subfield unitOfMeasure of the subfield SampledValue of the field meterValue shall be set to the default string, “Wh.”
- 4. When populated, the sub-sub-subfield multiplier of the sub-subfield unitOfMeasure of the subfield SampledValue of the field meterValue shall be set to the default integer, 0 (zero).
- 5. When the meterValue field is populated, the measurand sub-subfield of the SampledValueType subfield, of the field meterValue shall be populated as specified in OCPP 2.0.1.
(b) For networked publicly or ratepayer funded chargers installed on or after September 28, 2026, the recordkeeping and reporting agent of a networked publicly or ratepayer funded charger shall automatically transmit to the CEC or the CEC's designee the data specified in the following subdivisions (1) through (6) via API. If the record is generated by the central system and sent to the charger, the recordkeeping and reporting agent shall transmit the record to the CEC or the CEC's designee within 60 minutes after the record's generation. If the record is generated by the charger and sent to the central system, the recordkeeping and reporting agent shall transmit the record to the CEC or the CEC's designee within 60 minutes after the record's receipt by the Central Management System:
- (1) Charger serial number.
- (2) Charger ID -- the unique identifier for the charger within the network provided by the charging network provider. This shall be identical to the charger ID reported pursuant to section 3123(b)(2)(M)(1).
- (3) Charging Port ID -- the unique identifier for the charging port within the network provided by the charging network provider. This shall be identical to the charger ID reported pursuant to section 3123(b)(2)(M)(2).
- (4) System time -- The date and time that the record was first recorded by the central system. For records generated by the charger and sent to the central system, system time shall be the time the record was received by the central system. For messages generated by the central system and sent to the charger, system time shall be the time the record was generated.
- (5) All instances of HeartbeatResponse, BootNotificationRequest, and BootNotificationResponse for each charger.
- (6) All instances of AuthorizeRequest, AuthorizeResponse, NotifyEventRequest, RequestStartTransactionRequest, StatusNotificationRequest, and TransactionEventRequest for each charging port.
- (c) For networked publicly or ratepayer funded chargers installed from January 1, 2024 through September 27, 2026, the recordkeeping and reporting agent of a networked publicly or ratepayer funded charger shall comply with subdivisions (a) and (b) of this section, or shall record, and retain for six years from the date of recording, the operative status of each charging port for each publicly or ratepayer funded charger on a fifteen-minute interval. In the event the recordkeeping and reporting agent elects to comply with subdivisions (a) and (b) of this section and the CEC or the CEC's designee is not yet set up to receive the data via API, the recordkeeping and reporting agent shall transmit the data to the CEC or the CEC's designee with the semiannual reporting required in section 3123 in an electronic format of the Executive Director's choosing until the CEC or the CEC's designee is set up to receive the data via API.
- (d) For publicly or ratepayer funded chargers installed on or after January 1, 2024, the charging station operator shall record and retain for six years from the date of recording, the documentation required by section 3124(d) for any excluded downtime claimed as part of the uptime report specified in subdivision 3124(a).
- (e) The Executive Director may electronically request (sent to the most recent email address filed pursuant to section 3123(b)(1)(C)) that a recordkeeping and reporting agent provide the CEC with copies of the records retained pursuant to subdivision (c) and (d) of this section in an electronic format of the Executive Director's choosing. The recordkeeping and reporting agent shall submit the requested records to the CEC within 21 days after the date of the request in the electronic format specified by the Executive Director.
- (f) In the event of a technological malfunction other than the situation described in subdivision (c)(1) of this section that prevents recordkeeping and reporting agents from transmitting the records specified in subdivisions (a) and (b) of this section within 60 minutes of the records generation via API, the recordkeeping and reporting agent shall transmit data that was unable to be transmitted to the CEC or CEC's designee promptly upon the resolution of the technological malfunction.
- (g) Any charger that meets the definition of an AC level 2 charger, fleet charger, off-grid charger, private residential charger, research charger, or temporary charger, as those terms are defined in section 3121 is not required to meet the requirements of subdivisions (a) through (f) of this section.
(h) Data submitted pursuant to this section shall be submitted in a format consistent with the Hourly Charger Data Reporting Specification (July 29, 2025) of the Data Dictionary.
The following documents are incorporated by reference into section 3125.
Data Dictionary
Hourly Charger Data Reporting Specification (July 29, 2025)
energy.ca.gov/inventory-reliability
Copies available from:
Fuels and Transportation Division
California Energy Commission
715 P Street, MS-6
Sacramento, CA 95814
phone # 800-555-7794
Open Charge Point Protocol
Open Charge Point Protocol version 2.0.1 Edition 3 (May 06, 2024).
https://www.openchargealliance.org/downloads/
Copies available from:
Superintendent of Documents
U.S. Government Printing Office Washington, DC 20402 www.ecfr.gov
Note: Authority cited: Sections 25210, 25213, 25216.5, 25218(e), 25231.5, 25301, 25302, 25303, 25304, 25305, 25400, 25401, 25601, 25602 and 25618, Public Resources Code. Reference: Sections 25210, 25216.5, 25229, 25231.5, 25300, 25301, 25302, 25303, 25304, 25305, 25324, 25400, 25401, 25601, 25602 and 25618, Public Resources Code.
History
1. New section filed 3-10-2026; operative 4-1-2026 pursuant to Government Code section 11343.4(b)(3) (Register 2026, No. 11).