ODM EV Charger Development

Requirements definition

Most programmes that run late ran late from here. Requirements that say 22 kW and OCPP compliant are not a specification. They are a heading.

• Power levels, phases and supply configuration for the target markets
• Connector standard and cable configuration, tethered or socketed
• Environmental range, mounting and ingress requirements
• Communications: which bearers, which regions, which carriers
• Backend requirement, including OCPP version and any roaming obligation
• User interface expectations, including display, indication and language
• Target certification schemes and target markets
• Volume forecast, because it changes the design, not just the price

Architecture

The architecture decides most of the cost and nearly all of the risk. Controller topology, protection strategy, metering approach, connectivity and thermal design are settled here, and changing them later is a redesign rather than an adjustment.

We work through the architecture with your team rather than presenting it finished, because the trade-offs are commercial as often as they are technical.

Prototype

Prototypes exist to answer questions, not to impress. Each build has a defined set of unknowns it is meant to resolve: thermal behaviour, protection response, connectivity in real conditions, mechanical fit.

Validation

Electrical, thermal, EMC pre-compliance, environmental and protocol interoperability testing against the intended backend. Pre-compliance before formal testing is not optional. Discovering an EMC problem at the accredited laboratory is the most expensive way to find it.

Certification

We prepare the technical file and take the product through accredited laboratories for the target schemes. Scheme requirements are confirmed with the certification body rather than assumed from a general list.

Pilot build and production

A pilot batch validates that the design is manufacturable at rate, with the test coverage and documentation the line will actually use. Production follows against defined release criteria.

If you intend to localize production later, say so now. Designing for a future transfer is cheap. Retrofitting a design for one is not.

How one ODM programme actually ran

A renewables company in Europe came to us to enter EV charging. No chargers in the field, no way to forecast volume, and a market they had not sold into yet.

1. 1

   Samples first

   We agreed a programme and shipped samples rather than quoting against a forecast neither side could stand behind.

2. 2

   Their platform alongside

   Their charging management system was developed to their own requirements in parallel, so the samples arrived with software that was theirs.

3. 3

   Volume after validation

   Volume followed once the samples had done their work in their market, not before.

4. 4

   Customisation

   The product was reshaped to their form factor and brand, and the feature set adjusted to what their buyers actually asked for.

5. 5

   Transfer and localization

   Two AC platforms starting at 3.3 kW, then manufacturing set up in their own market.

They are in production and run their own operational system. What they said surprised them was the speed of it, and the reason is structural rather than flattering: because the hardware, the firmware and the platform are one team here, a requirement raised on Monday does not have to be negotiated across three suppliers who each own a layer of the answer.