EV charger asset registers: connect the physical unit to the right operating record

1. Agree what each identifier means

Keep the manufacturer's equipment identity separate from names chosen by the site owner or software provider. A friendly dashboard name can be useful, but the handover should also retain the exact identifier used to match the supplied unit to its documents. Ask who assigns each field, who may change it and which record is authoritative.

The Open Charge Alliance describes OCPP as communication between charging stations and charging management systems. A protocol connection does not by itself define the buyer's complete inventory or document-filing process. Confirm the actual identifier model for the agreed charger, firmware, protocol version and backend; this checklist does not prescribe protocol field names or assume that different versions number outputs identically.

• Physical identity: supplier, selected model/variant and serial number as documented for the delivered equipment.
• Site identity: the owner's asset code, site and position or bay reference.
• Software identity: the management system and its configured station/output references.
• Evidence identity: the purchase line, delivery record, configuration record and accepted test-report references.

Record these as separate fields even when some values happen to match. Do not substitute a shipping-carton number for the equipment serial number without supplier confirmation.

2. Use a station record and a linked output list

Choose a stable internal record key for the register and agree how it is maintained. Then keep a child list for the outputs associated with that station. The purpose is to describe the actual delivered arrangement, not to infer simultaneous power, connector compatibility or software capabilities from the number of rows.

Allow “not applicable” and “awaiting confirmation” with a named owner. An empty cell should not silently mean “passed”. Agree a format that the buyer can export, read and maintain after handover. Keep dates and identifier formatting consistent, including meaningful leading zeros.

3. Validate the mapping before operational acceptance

Ask the supplier to provide a sample register before the pilot, using synthetic information if actual serial numbers are not yet assigned. At delivery, the receiving team reconciles the supplied identity evidence with the purchase and packing records. At commissioning, authorised personnel reconcile the installed location and visible labels with the operator's approved system records.

Use the project's approved commissioning plan for any functional demonstration. For each relevant output, record which physical label corresponds to which backend record and who witnessed the check. Do not perform ad hoc remote commands on an operating site to guess the mapping. Missing or contradictory evidence should enter the agreed defect-resolution process, not be hidden by renaming an entry.

The register should point to the FAT/SAT evidence; it does not replace testing. A document link should identify its revision and applicable unit or configuration, not just open a generic folder.

4. Work through a two-site example

Illustrative administrative example, not customer data: two depots both call their first station “Charger 1”. The buyer creates register keys SITE-A-01 and SITE-B-01 while retaining the suppliers' original serial numbers. Each station has a separate list linking its visible output labels to its confirmed backend records. The names are examples, not required protocol identifiers.

If a service report arrives for SITE-B-01, the reviewer should be able to locate the correct model, installed location, accepted configuration and document package without searching the other depot's files. If a dashboard nickname changes, the change record preserves the earlier value and date. The physical serial number is not rewritten merely to make the names look consistent.

Ask bidders to demonstrate this lookup with a sample delivery pack. A successful lookup is a useful administrative acceptance check; it does not prove equipment safety or charging performance.

5. Keep replacement and relocation history

Before a controller, output assembly or complete unit is replaced, ask the responsible teams which recorded identities and references must change. Do not assume that a replacement keeps every software identifier or that all identifiers must be replaced. Capture the agreed before-and-after mapping, work-order reference, effective date and required acceptance evidence.

Retain the earlier record with an appropriate lifecycle status rather than deleting it. A replacement cabinet should not inherit an old serial number just because it occupies the same bay. Likewise, moving a unit to another site should update its location history without obscuring its origin. Record unresolved mappings and obtain approval before treating the handover as complete.

Link approved spare-part references to the exact supported configuration; the local service and spare-parts checklist covers the separate compatibility review. Use the configuration change-control guide for changes that affect the accepted technical baseline.

6. Make the register useful without exposing secrets

Agree who can read the inventory, approve changes and export records. Keep credentials, private keys, payment details and customer or driver records out of the handover spreadsheet. Where access provisioning is required, reference the organisation's controlled process and responsible role rather than copying authentication material into the register.

Share only the fields needed for a support request and use an approved private channel for sensitive equipment inventories. Keep public photographs and case studies separate from internal evidence. Before an operator transition, confirm that the receiving authorised team can access the agreed records and that obsolete access is handled through the approved process.

7. Put register ownership in the quotation

Specify the first sample delivery, final handover format, required fields, acceptance reviewer and responsibility for correcting discrepancies. Ask who updates the register after firmware changes, repairs, relocations or backend migration, and whether the quoted support includes that work. Do not assume that software exports automatically include supplier manuals or historic maintenance evidence.

Add the requested deliverable to your RFQ planning brief. Ask for one sample station record, one output mapping and one replacement-history example. Agree the document language and access arrangements before a repeat order. A buyer tool helps structure questions; it is not engineering, cybersecurity, regulatory or contract approval.

AC and DC SKD: identify both the kit and the accepted assembled unit

For AC EV charger SKD kits and technical documentation, agree how the supplied component/BOM records connect to the selected assembled unit, its configuration and assembly evidence.

For DC EV charger SKD kits and technical documentation, separately define the component, control/interface and output-mapping records required for the agreed model and qualified testing process. Do not infer approved substitutions from matching names alone.

Xiaochong recruits businesses interested in local charger production and assembly, with project-scoped SKD components, assembly technical support and repair/maintenance technical support. Available AC or DC technical documentation is free on request. Confirm exact models, document revisions, languages, testing, training, support and licensing in the project agreement. Free documents do not mean free hardware, repair labour, all training, certification or unrestricted software and intellectual-property rights.

Buyer FAQ

Is a charger serial number the same as its backend identity?

Do not assume they are the same. Record the physical serial number and the configured backend identifier separately, then have the supplier and operator verify the mapping for the selected system.

What should happen to the register after a controller replacement?

Keep the old record and add a dated change entry linking the replacement, approved configuration, updated software mapping and relevant acceptance evidence. Confirm which identifiers remain valid before returning the equipment to service.

Should passwords or private keys be included in the asset register?

No. Keep secrets in the organisation's approved credential-management process. The register should identify the responsible role and controlled reference, not expose authentication material.

Request a model-specific handover scope

Send Xiaochong Energy Technology (Zhongshan) Co., Ltd., China your country, AC or DC track, pilot quantity, site count, intended management platform and required register/document language. Request the available free AC or DC technical documents and a proposed project-specific handover list.

Review the official partner programme, AC/DC SKD technical-output page and procurement guide. Any document samples or drawings must be approved for sharing; this article contains no private factory files.

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