EV charger uptime: agree what the percentage measures before accepting it

1. Separate the technical evidence from the commercial promise

The Open Charge Alliance white paper on uptime monitoring explains that successful charging involves the station, management system and other participants. It distinguishes reporting per site, charging station and EVSE, and notes that a working WebSocket connection does not by itself demonstrate a fully functioning charging application. These distinctions are useful when evaluating an online indicator. They do not establish a particular model's uptime, supported feature set or a legally required percentage.

As a buyer, request two separate deliverables: a description of the monitoring evidence the chosen system can provide, and a written commercial reporting agreement. Ask the supplier and operator to identify gaps between them before signing. A screenshot or marketing statement should not silently become the acceptance method.

2. Ask for a one-page reporting specification

Use the following questions as an original procurement worksheet. Ask each bidder to answer against the same proposed site, equipment list and service schedule so that comparisons are meaningful.

• Scope: Which equipment identifiers are covered, from what acceptance date, and under which configuration revision?
• Period: Which dates, time zone and service hours appear in the report? Who approves changes to opening hours?
• Evidence: Which records support each reported interval, and who can export them for review?
• Exceptions: What is excluded, who approves each exclusion, and where can the buyer see the reason?
• Uncertainty: How are missing, delayed or contradictory observations displayed?
• Ownership: Who prepares, checks, signs off and corrects the monthly report?

Keep the worksheet revision with the purchase and service records. If the operator changes its reporting method, require a dated explanation rather than silently comparing the new result with an older, differently defined percentage.

3. Keep uncertainty visible instead of calling it success

Request a worked sample containing a normal period, an incident and an interval where information was unavailable. The sample should show how the report reaches its conclusion without exposing another customer's private data. Synthetic demonstration data is acceptable when clearly labelled; it is not evidence of field performance.

In the buyer's brief, require a separate explanation for unknown intervals. Ask who reconciles delayed records and how an amended report is versioned. Do not assume missing records mean either confirmed service or confirmed downtime. The chosen reporting method should explain its limitations in plain language.

For the communications responsibilities behind those records, use the site network and SIM checklist. Confirm the actual monitoring and export capabilities for the selected charger, firmware and backend; this guide does not imply that every model implements every diagnostic feature.

4. Agree how an incident becomes a reviewed record

Propose a simple record with an incident reference, affected equipment, first observation, reporting party, evidence references, assigned owner, current status and closure evidence. Keep the original observations alongside later conclusions. A ticket being closed and the agreed service being verified are separate milestones in the proposed workflow.

Require the responsible teams to agree how duplicate reports and overlapping incidents are handled. Otherwise, the buyer may receive several tickets for one event or lose visibility when a ticket is transferred between organisations. Ask for a named coordinator and a review date for disputed classifications.

This is a record-management proposal, not a diagnostic instruction. Follow the model-specific support process; do not reset equipment repeatedly, change safety settings or open an enclosure to make a report look healthy. Use the fault-reporting guide to prepare an appropriate support request.

5. Make the reporting service part of the quotation

Request a separately identifiable scope for dashboard access, report preparation, retention, export, incident review and after-hours support. Ask whether the buyer retains access when the support contract ends. Compare the work and access rights included, not just the headline subscription.

Agree who can receive reports and which information must be restricted. Public marketing material should not contain customer identities, payment information, credentials or raw operational logs. A monthly management summary and a controlled technical evidence bundle can serve different audiences.

The warranty and service-SLA guide covers the wider response and restoration agreement. Any service credit, uptime target or exclusion requires explicit commercial review; none is promised by this article.

6. Use the first reporting cycle as a handover check

Before expanding an installation, ask the buyer, operator and supplier to review one agreed reporting cycle together. Confirm that the equipment list is correct, the designated people can access the agreed records and an example incident can be followed from observation to closure. Record unresolved items, their owners and the next review date.

Separate this evidence review from revenue forecasting. Customer demand, operating costs and service interruptions deserve distinct assumptions in a business case. Do not use a high availability percentage as a guarantee of sessions, sales or payback. Add the reporting requirements to the free RFQ brief builder; it is a planning aid, not financial or regulatory approval.

AC and DC local-production partners

For AC EV charger SKD kits and technical documentation, confirm the supplied controller/component scope, documentation revisions, qualified assembly/testing responsibilities and reporting features of the selected configuration.

For DC EV charger SKD kits and technical documentation, separately agree the power/control integration boundary, technical evidence and qualified service responsibilities. Do not carry an AC configuration's acceptance assumptions into a DC project without review.

Xiaochong welcomes local production and assembly partners and can discuss SKD components, assembly technical support, professional repair and maintenance skills, available training videos and requested document languages. Available technical documentation can be requested free. Exact models, revisions, licences, languages and training/support deliverables require agreement; hardware, all training, repair labour, certification and unrestricted intellectual property are not automatically free.

Buyer FAQ

Does an online charger prove that customers can charge?

No. A communications indicator is only one piece of evidence. Agree the customer workflow and the checks needed for the selected charger, authorization method and backend.

Should a buyer accept an uptime percentage without an event log?

Ask for the reporting period, included equipment, exclusions, unknown intervals and supporting event records. A percentage without a defined scope is difficult to compare.

Can a charger availability promise guarantee project profit?

No. Availability, customer demand, tariffs and operating costs are different inputs. Treat downtime assumptions separately in your commercial scenarios; no guide guarantees revenue or payback.

Request a project-specific reporting brief

Xiaochong Energy Technology (Zhongshan) Co., Ltd., China welcomes overseas operators and distributors. Send your country, AC or DC track, proposed equipment quantity, backend, operating hours and reporting needs. Request free available AC or DC technical documents and tell us which languages your qualified team requires.

Review the official partner programme, AC/DC SKD scope and procurement guide. The quotation must confirm model-specific capabilities and responsibilities.

xc0225888@163.com · Sales 1: +86 137 1772 6888 · Sales 2: +86 134 2580 6997