yashovardhan

Charge City

Charge City: moving an EV charging network off spreadsheets

Product
Charge City
Year
2023
Industry
Automotive
Contributors
Tarandeep R., Vineet M.
Charge City case study cover

Results

Faster maintenance response
50%
More charger uptime
25%
Saved per employee each month
30+ hrs

Context

An EV network run on spreadsheets

Charge City ran EV chargers across Delhi NCR, and a fault only surfaced when someone noticed and reported it. Interviews with 15+ operators showed the problem wasn't data entry: 80% of maintenance delays came from not knowing a charger was down. I designed the internal platform that replaced the sheets, with Tarandeep R. and Vineet M.

01Dashboard

First thing in the morning: is anything broken?

The control centre puts faults first, then sessions, revenue and energy, with a station view and inline controls to fix things.

Why: A fault should be something you click into, so every chart is paired with a list you can act on.

Charge City: Control centre. Faults sit up top with sessions, revenue and energy.
1.1Control centre. Faults sit up top with sessions, revenue and energy.
Charge City: Station view: sessions, charger status and user actions, with inline controls to fix things.
1.2Station view: sessions, charger status and user actions, with inline controls to fix things.

02Usage

Usage and energy

Sessions next to live energy and revenue, plus heatmaps for consumption, cost and peak usage across locations.

Why: Session data is huge, so operators start from a summary and drill in with filters and grouping.

Charge City: Sessions next to live energy and revenue, with filters and grouping.
2.1Sessions next to live energy and revenue, with filters and grouping.
Charge City: Heatmaps and graphs for consumption, cost and peak usage across locations.
2.2Heatmaps and graphs for consumption, cost and peak usage across locations.

03Payouts

Payouts and reports

Reports and payouts on one screen, with a live invoice preview before export.

Why: Revenue leakage was one of the starting problems, so finance sees exactly what they sign off without going back to a spreadsheet.

Charge City: Reports on one side, payouts on the other, and a live invoice preview before export.
3.1Reports on one side, payouts on the other, and a live invoice preview before export.

04Setup

The setup screens

Vehicles, locations, credentials and permissions, given the same care as the dashboards.

Why: Configuration is where mistakes get expensive, and different people run different parts of the network.

Charge City: Vehicles grouped by brand, with charging-compatibility tags and quick edits. Multi-OEM lists get long.
4.1Vehicles grouped by brand, with charging-compatibility tags and quick edits. Multi-OEM lists get long.
Charge City: Location settings and metadata side by side, live charger health underneath.
4.2Location settings and metadata side by side, live charger health underneath.
Charge City: Credentials and permissions on one screen, grouped by area.
4.3Credentials and permissions on one screen, grouped by area.

Outcome

What changed

“Thanks again, the designs look amazing and the process had been smooth”
TarandeepCharge City

Hiring for product design, or building something new? Send the context and we can talk it through.

Book a 30-min call (opens in new tab)