EVSE Technology Partner for Charger OEMs

Buy the controller rather than build the stack

If you build enclosures, power paths and cables well but do not want to own an OCPP implementation, the controller is the subsystem to take under an integration programme. Your product stays yours; the maintenance obligation moves.

Or develop the product together

Where the requirement is a product that does not exist yet, development runs from requirements through architecture, prototype, validation and certification to pilot build. Scoped at the depth the commercial objective needs rather than at the deepest available.

Ship it with software

Selling hardware with a platform attached changes the proposition, because the buyer gets one supplier and one place to go when something fails between layers. It also means your product is judged on software behaviour, which is a real exposure to price in.

Design for where production ends up

If a customer may later require local manufacture, designing for that transfer at architecture stage costs little. Retrofitting a design for transfer afterwards is awkward and sometimes impossible without revisiting decisions.

What an end-to-end programme looks like

Where an OEM wants the whole path rather than one piece, the sequence runs: an initial sample batch to validate the platform in your conditions, customisation to make the product yours, technology transfer of the design and production package, then localization support to get it building at your own site.

The software can come with it. The same organisation builds the charging management platform, the operations suite and the charger registry, so a hardware programme does not have to arrive without a way to operate the fleet it produces.

What one OEM programme looked like end to end

A renewables company in Europe entering EV charging, with nothing in the field and no way to forecast volume honestly. Samples first, their own management platform developed alongside, volume once the samples had proved the case, then customisation to their form factor, technology transfer of two AC platforms starting at 3.3 kW, and finally manufacturing set up in their own market.

The hardest part was not engineering. It was qualifying suppliers in a market where we had no relationships, and it took longer than moving the design. Any OEM planning to build locally should budget for that specifically.

They are in production and run their own operational system. This is the shape of an end-to-end programme when it works.

The software half of an OEM programme

A charger without a platform is a product you cannot sell twice. Most OEM conversations start at the hardware and the ones that succeed cover the software in the same breath.

• The charging management platform your customers will actually operate on
• Warranty management, so claims, returns and root cause analysis are a system rather than a mailbox
• The operations suite: monitoring, ticketing, dispatch and the automation around them
• APIs, so your customers can build on what you sold them

We develop the product and the software together and ship them as one thing, which is the only arrangement where a fault gets diagnosed instead of attributed.

What else comes with it

1. 1

   Test setup and certification

   We build the test systems and take products through accredited laboratories. We have done this for our own products and for customers'.

2. 2

   Manufacturing support

   Production setup, line planning, test jigs, vendor qualification and the documentation a factory builds from.

3. 3

   Operations support

   Running the network, or supporting the team that does, after the units are in the ground.

4. 4

   Consulting

   Where the question is which of the above you actually need, which is frequently the first conversation rather than the last.