A fast charger warranty is not an uptime plan

A warranty can leave diagnosis and field repair unassigned

A prospective charging-site owner in a saved Reddit discussion asked which network would give customers the best experience. Other operators warned about parts availability and recurring fees. The practical question is what happens when a driver cannot start or complete a session. Product warranty, network support, and on-site repair are separate services. A station can have an active warranty while remaining unavailable because diagnosis, labor, shipping, or replacement parts are outside the agreed coverage.

Source: Business owner considering EV charging network providers - INPUT REQUEST

Name the owner of each service dependency

DOE's infrastructure guidance includes operations and maintenance in project planning. Procurement should identify the owner of each dependency: electrical supply, charger hardware, payment terminal, communications, software backend, and customer support. Avoid a single vague promise of support. Ask who receives the first fault report, who determines responsibility, and who coordinates when the symptom could belong to several vendors.

Source: Alternative Fuels Data Center: Procurement and Installation for Electric Vehicle Charging Infrastructure

When payment fails but the hardware appears healthy

Illustrative scenario: a dual-port station remains connected to the network but neither port accepts payment. The hardware vendor sees no power-conversion fault; the network vendor says the payment terminal is a third-party component. Without a coordination agreement, the owner becomes the integration manager while customers leave. A defined incident process would specify remote diagnosis, escalation timing, customer notices, field dispatch, and evidence required to close the incident.

Separate response, dispatch and restoration commitments

Request separate commitments for response, diagnosis, repair dispatch, and restoration. A response-time promise may mean only that an email is acknowledged. Clarify business hours, weekend coverage, geographic service availability, spare parts, travel charges, and exclusions. Ask how recurring failures are handled and whether software updates can be scheduled or rolled back through supported procedures. Maintain secure owner access to account and performance data.

Separate inventory reporting from funded-charger reliability duties

The CEC’s EV Charger Data and Reliability Standards took effect April 1, 2026. A privately funded commercial DC fast charger can still require the semiannual inventory report under sections 3120 and 3123. For these privately funded chargers, section 3122(b) makes the network provider the reporting agent; without a network provider, the station operator takes that role. Section 3123 excludes defined private residential, research, temporary and off-grid chargers, and provides an exception for chargers previously reported uninstalled that have not resumed dispensing energy. Private funding alone is not an exemption.

The separate 97% annual per-port uptime standard generally covers DC fast chargers installed on or after January 1, 2024 with state or ratepayer funding, including qualifying federal funds passed through a state agency. It applies for the first six years, with defined exemptions including fleet-only chargers. Funding, installation date and use therefore determine the additional duties; they do not determine whether every reporting obligation disappears. Before assigning only inventory-reporting duties, have the provider document whether the actual project contribution meets the incentive and funded-charger definitions in §3121(a)(25) and (42).

For networked publicly or ratepayer-funded chargers installed on or after September 28, 2026, section 3125 requires OCPP 2.0.1 edition 3 Subset Certification for Core and Advanced Security and prescribed data transmission. Section 3125(g) exempts defined AC level 2, fleet, off-grid, private residential, research and temporary chargers from subdivisions (a) through (f) of that section. Section 3122(c)(2) generally requires a CEC-enrolled network provider as reporting agent. An enrolled site host can fill that role itself; a host may also report itself during a period without energy dispensing other than testing or maintenance. Confirm any exemption, obtain certification where required and identify the applicable reporting arrangement before contracting.

Source: CEC: July 2026 implementation workshop; April 1, 2026 effective date · CEC: Charger performance standards and uptime reporting · CEC: adopted EV Charger Data and Reliability Standards, sections 3120–3131

Define what counts as restoration from the customer’s perspective

A repair ticket should close on an agreed usable outcome, not merely on the return of network connectivity. For a payment-related failure, that may require a representative customer authorization followed by successful energy delivery. For an interrupted-session fault, the test should address the reported failure condition through the provider's approved procedure. The owner does not need to perform internal diagnostics, but should understand what evidence demonstrates that the service has been restored. A remote dashboard turning green can be one observation without being the whole acceptance test.

Walk through an after-hours incident with the proposed support team before signing. Identify the first contact, the information needed, the party authorized to dispatch a technician, and responsibility for costs that fall outside warranty. Ask how a parts delay is communicated and what the operator should tell customers while a port remains unavailable. The answer should also cover updating station listings and removing misleading availability information. Preserve escalation contacts and name an owner to review recurring failures against the agreement.

Verify the support path at handoff

At handoff, test a support case using the actual station identifier and confirm that the owner receives a ticket and escalation path. Preserve maintenance instructions and a safe isolation procedure for qualified personnel. Site staff can report visible damage and keep unsafe equipment out of service through the approved process; they should not improvise internal repairs. Review incidents and recurring charges periodically so the operating agreement evolves with real failure patterns.

Give the reporting work a named owner

The first semiannual reporting period is July through December 2026, with submission due January 31, 2027. Assign collection, validation and filing of the inventory, including charger and port details, payment options, prices and support contacts. Add the applicable uptime and hourly-data duties for qualifying funded chargers. Preserve owner access to records when a network contract ends. For DCFC covered by section 3127, provide a way to report faults and make the instructions available at the station; the reporting channel itself can be remote.

For the uptime calculation, section 3124(d)(6) permits exclusion of a cellular or internet provider outage only when the charger defaults to operational charging that is free to any customer during the communication loss. Do not classify every disconnected port as excluded downtime. Have the vendor document the fallback configuration, test it and retain event records supporting the claimed exclusion. Separately track failed starts, payment problems and derating that need repair even if the reported uptime meets the standard.

Source: CEC: adopted EV Charger Data and Reliability Standards, sections 3120–3131 · CEC: Charger performance standards and uptime reporting

Put it into practice

A decision table to keep handy