Skip to main content

Dev Station Technology

Electric vehicle charging

Charging software built for 99 percent reliability

Charge point monitoring, fault tracking and the open data a public network has to publish. Built on the self-hosted IoT platform we delivered to a client who owns every record.

99%Reliability required of rapid charge points, annual average
50 kWCharge point power at which the rapid rule applies
24/7Free helpline requirement
24 Nov 2024Date the requirements applied
What this is

Reliability is a legal number now

The Public Charge Point Regulations set a reliability level for rapid charge points and require contactless payment, a helpline and open data. An operator can only meet them if it measures uptime per connector and can show the figures.

Where we have proof

a self-hosted, multi-tenant IoT platform with role-based access and reporting built in

Where we have not yet

We have no published EV charging case. We say so on the first call and show the closest work.

Services

What we build for charging operators

Charge point monitoring

Status and faults per connector in near real time.

Reliability reporting

Uptime calculated the way the regulations measure it.

Telemetry ingest

Charger data over MQTT, with a broker in front.

Contactless payment integration

Payment flows joined to the session record.

Open data publishing

Location and status published in the format the rules ask for.

Engineer apps

Faults assigned and closed in the field, offline.

Rules

What the Public Charge Point Regulations require

These come from gov.uk guidance on the Public Charge Point Regulations 2023.

99 percent reliabilityRapid charge points of 50 kW and above must average 99 percent reliability over a year. Source: gov.uk, Public Charge Point Regulations guidance.
Contactless paymentRequired on new charge points of 8 kW and above, and on existing ones of 50 kW and above. Source: same guidance.
24/7 helplineOperators must provide a free helpline open at all times. Source: same guidance.
Open dataOperators must share charge point data in the OCPI open data standard. Source: same guidance.
Case study

A platform the client owns outright

IoT Core Engine self hosted platform built by Dev Station
Industrial IoT

IoT Core Engine

The client wanted off third-party IoT SaaS without losing the enterprise features their own customers expected. We built a self-hosted, white-labelled platform on an open-source base, with role-based access, single sign-on and reporting built in.

Self-hostedOn-premise, private cloud or hybrid
Technologies in the build abovePostgreSQLApache KafkaDockerKubernetes
Who we build for

The teams who call us

Charge point operators

Networks that need reliability figures they can defend.

Fleet and depot charging teams

Sites with many chargers and few engineers.

Property owners with charging

Landlords who host chargers and owe the data.

Charging hardware makers

Product teams who need a monitoring platform under their own brand.

Related reading: energy and utilities software, e-scooter software and automotive software.

FAQs

What buyers ask first

Do you have a EV charging case?

Not yet published. We say so on the first call and show the closest work, which is a self-hosted IoT platform with telemetry ingest.

Can you connect to our chargers?

Usually over OCPP, the maker API or MQTT. Send the models and we will say what we can read.

Do you give advice on the regulations?

No. That advice comes from your compliance team and the Office for Zero Emission Vehicles. We build the measurement they specify.

Who owns the code and the cloud accounts?

You do, from the first commit. Repositories and cloud accounts stay in your name.

Send us your charger list

Thirty minutes with the engineers on your hardware, how uptime is measured now and what you report.

Let's Talk