The organisation needed one charging network platform for drivers, site hosts, and charging network operators. The existing journey divided charger discovery, connector status, reservations, sessions, tariffs, payments, host reporting, maintenance, and network health between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete charging network platform shaped around drivers, site hosts, and charging network operators
The organisation needed one charging network platform for drivers, site hosts, and charging network operators. The existing journey divided charger discovery, connector status, reservations, sessions, tariffs, payments, host reporting, maintenance, and network health between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between charging network, driver sessions, and site operations, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole charging network platform.
- Separate firm electric mobility rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined charging network, driver sessions, and site operations without blurring roles
Keep charger telemetry and session accounting authoritative while presenting drivers with clear availability, pricing, and recovery when a charger fails.
In the charging network platform, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Flutter, Angular, IoT APIs formed one supportable charging network platform
The architecture follows business ownership rather than the navigation menu. Flutter, Angular, IoT APIs share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind driver sessions.
In the charging network platform, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Flutter supports the primary product surface.
- Angular owns a bounded part of the product journey.
- IoT APIs keeps operational data and handoffs reviewable.
The release had to prove the whole charging network platform, not one polished screen
Drivers can understand a charging session while operators manage sites, revenue, and service issues centrally. The release plan therefore followed representative work across every audience and the complete path through charging network, driver sessions, and site operations.
Acceptance for the charging network platform included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Drivers can understand a charging session while operators manage sites, revenue, and service issues centrally.
- 01
The charging network platform now gives drivers, site hosts, and charging network operators one shared operating record.
- 02
Charging network, driver sessions, and site operations follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.