EV Charging Infrastructure · Lesson 1 of 5
Begin with vehicles, energy and dwell time
Charging infrastructure exists to support mobility. The design should therefore begin with vehicles: battery capacity, energy consumed per route, arrival state of charge, required departure state, dwell time, connector and maximum acceptance rate. Selecting charger power before understanding this duty can produce unnecessary cost or missed departures.
After this lesson, you should be able to:
- Translate vehicle operations into charging energy and power needs
- Distinguish charger nameplate from vehicle acceptance
- Explain operator and driver value
What is physically and operationally happening?
Charging infrastructure exists to support mobility. The design should therefore begin with vehicles: battery capacity, energy consumed per route, arrival state of charge, required departure state, dwell time, connector and maximum acceptance rate. Selecting charger power before understanding this duty can produce unnecessary cost or missed departures.
For drivers, value is reliable access and enough energy at the required time. For site operators, value may include fleet readiness, managed demand, uptime and clear support. A high-power charger that vehicles cannot accept or schedules cannot use does not improve the service.
Route energy
Estimate energy consumed between charging opportunities.
Dwell window
Measure time available between arrival and required departure.
Acceptance
Confirm the vehicle’s AC or DC charging limit and compatibility.
Schedule
Allocate charger power so every priority vehicle meets departure need.
Fleet energy window
Required average power is fleet energy divided by the usable charging window, before losses and operational constraints.
Mobility demand evidence profile
Illustrative vehicle arrivals and departure deadline. Values are educational, not Metro Power project-performance claims.
OPTIONAL ENGINEERING DEPTHMobility demandTranslate vehicle mix, daily energy, dwell time and route windows into charging requirements.+
- Separate connected load from controlled demand
- Include existing site peak and reserve margin
- Respect vehicle acceptance, arrival and departure
- 01Build the one-line from utility service to connector
- 02Run vehicle-energy and managed-allocation scenarios
- 03Test controller fallback when communications or site metering fails
Site peak exceeds the enforced cap
Control latency, stale data or unmanaged charger
Compare meter, controller and charger timestamps
Vehicles miss departure targets
Allocation ignores energy deadline
Replay arrivals, initial SOC and priorities
- Vehicle schedule and session traces
- Site interval load and capacity study
- Controller logic and fallback test
Overnight fleet requirement
Twenty vehicles each need 60 kWh before departure and have a six-hour common window.
- Average fleet power = 1,200 / 6 = 200 kW
- Add charging losses and operational margin
- Test individual vehicle and charger constraints
- Schedule priority vehicles and late arrivals
“A 60 kW charger always charges a vehicle at 60 kW.”
Actual power is limited by the vehicle, charger, battery condition, temperature, state of charge and site controls.
Check what you can explain without looking back.
Choose an answer and report your confidence. The confidence signal is stored only until you submit this page.
What is the first design input?
600 kWh must be delivered in 5 hours. Average power before losses is:
A vehicle accepts 11 kW AC on a 22 kW charger. Likely power is limited to:
Continue with the controlling references.
01Electric Vehicles for FleetsUS Department of Energy Alternative Fuels Data CenterFleet planning, equipment, operations and training considerations.
Open source ↗02State and Local Planning for EV Charging InfrastructureUS Department of Energy Alternative Fuels Data CenterCharging infrastructure planning framework.
Open source ↗Read the complete technical paper →