AC EV Charger OEM Manufacturer

Why in-house matters here

When a charger fails intermittently in the field, the cause could be hardware, firmware, protocol handling or the backend. A supplier who owns only one of those layers can prove their layer is fine and leave you with the problem.

Hardware, firmware, OCPP implementation and cloud are built in the same organisation here, which is why root cause analysis can cross the boundaries instead of stopping at them.

Metering and billing

If sessions are billed, metering accuracy determines whether the bills are defensible. The accuracy class required depends on the market and on whether the transaction is a regulated sale of electricity. Establish that early, because it constrains component selection and cannot be retrofitted cheaply.

Protection and safety

Residual current detection, over current, over and under voltage, over temperature and earth continuity are all built into the unit. Additional protection can be designed in where a deployment or scheme requires it. Protection components sit in the safety path, which is why they are also the parts most constrained during any later localization.

Connectivity in real conditions

Basement car parks, metal enclosures and shared Wi-Fi are the normal operating environment, not the exception. Connectivity that works on a bench frequently does not work on site, which is why bearer selection and antenna design are validated in representative conditions.

OCPP and backend

OCPP 1.6J and 2.0.1 are both released in shipping firmware. Compliance with a version is not the same as interoperability with a specific backend, so integration testing against your intended CMS is part of the programme rather than an assumption.

The quality position, with a number attached

Across our deployed AC fleet, field failures run at about 0.5 percent, roughly one unit in two hundred. We publish it because a number you can hold us to is worth more than an adjective.

Two practices sit behind that number, and neither came from a standard.

1. 1

   Every unit tested

   We build our own end-of-line jigs and include a charger simulator, so the charging sequence is exercised without a vehicle present. A line that tests only what can be checked without one will pass units whose charging behaviour was never verified.

2. 2

   Cable treated as a controlled item

   Cable quality and internal routing produce failures that pass end-of-line test and appear months later in the field. We found this by analysing returns, which is the only way it is ever found.

Neither of those is exotic. Both came from analysing returns rather than from a standard, which is the only way they are ever found.

How we work with you on this

We would rather sell you samples than volume you are not ready for, and that is not a sales position, it is what the sequence should be. Sample enough units to see variation and field behaviour in your own market, then commit.

If the standard product does what you need, we will tell you that and you should not pay for customisation. If it does not, we will say what would have to change and what it would cost. Either answer is more useful to you than a quotation against an untested specification.

You are not locked to our platform

This is the part of an OEM decision that matters most in five years and gets the least attention at the point of purchase.

The charger's endpoints are configurable. You set the server it connects to, which means the unit is not tied to a proprietary platform, ours included. If you want to run it on your own management system, or move it to a different one later, that is a configuration change rather than a negotiation with us.

We are explicit about this because we have been on the wrong side of it. We used to resell a shared third-party platform, and when a change finally became unavoidable the only way to deploy it was to send people to every charger in the field. A charger you cannot point somewhere else is a charger your supplier controls.

Protection and metering, as built

All protection is inside the unit rather than assumed from the installation.

• Overvoltage and undervoltage
• Overcurrent
• Earth leakage
• Over temperature
• IP65 enclosure protection
• Load management protection, so an allocation cannot be exceeded

Metering is Class 1 accuracy onboard. Where a deployment needs certified measurement for billing, the unit also reads an external meter over Modbus RS-485, so the transaction record comes from the certified device rather than from us. Which of the two you need is a market question rather than a product one, and both are available.