METRO POWERMetro Power Academy lessonPlan a project ↗

EV Charging InfrastructureLesson 1 of 5SYSTEM ORIENTATION

Begin with vehicles, energy and dwell time

Charging infrastructure exists to support mobility.

READING TIME
12 minutes
OBJECTIVES
3 learning objectives
SELF-CHECK
3 check questions
INTENDED FOR
Fleet, property, utility, engineering and charging-operations teams

Educational lesson. Confirm project-specific requirements before application.

Integrated DC fast charger with a pedestal unit (product render)
Manufacturer renderIntegrated DC fast charger

01LEARNING OBJECTIVES

After this lesson, you should be able to:

  1. 01Translate vehicle operations into charging energy and power needs
  2. 02Distinguish charger nameplate from vehicle acceptance
  3. 03Explain operator and driver value

02EXPLANATION

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.

  1. 01

    Route energy

    Estimate energy consumed between charging opportunities.

    kWh/vehicle/day
  2. 02

    Dwell window

    Measure time available between arrival and required departure.

    Hours
  3. 03

    Acceptance

    Confirm the vehicle’s AC or DC charging limit and compatibility.

    kW/vehicle
  4. 04

    Schedule

    Allocate charger power so every priority vehicle meets its departure need.

    Fleet readiness
READING NOTEIllustrative schedule. Use real telematics, routes, vehicle acceptance and operational reserve.
TECHNICAL VISUAL · SYSTEM-SPECIFIC MODEL

Fleet energy window

Required average power is fleet energy divided by the usable charging window, before losses and operational constraints.

Three vehicles connected. The earliest departure keeps full power and the others share what remains, so the site holds at its limit instead of reaching 150 percent.

  • AC power
  • Control and data
  • Power flowing, arrow shows direction
Illustrative arrangement, not a Metro Power project. Supplied equipment appears as Bescore renders and studio photographs of the equipment class; the grid, generation, buildings, vehicles and control equipment are drawn.
ENGINEERING VIEW · ILLUSTRATIVE

Mobility demand: illustrative profile

normalized
Illustrative vehicle arrivals and departure deadline

Illustrative vehicle arrivals and departure deadline. Values are educational, not Metro Power project-performance claims.

04OPTIONAL ENGINEERING DEPTHEngineering reasoning for this learning pathThe same design relationship, checks and evidence apply across every lesson in this path.
DESIGN RELATIONSHIPAllocated charging demand ≤ verified site charging cap while each priority vehicle meets its energy deadline
  • Separate connected load from controlled demand
  • Include existing site peak and reserve margin
  • Respect vehicle acceptance, arrival and departure
ENGINEERING CHECKS FOR THIS PATH
  1. 01Build the single-line diagram from utility service to connector
  2. 02Run vehicle-energy and managed-allocation scenarios
  3. 03Test controller fallback when communications or site metering fails
FAILURE ANALYSIS
Observed signalPossible causeDiscriminating test

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 state of charge (SOC) and priorities

PROJECT EVIDENCE TO COLLECT
  • Vehicle schedule and session traces
  • Site interval load and capacity study
  • Controller logic and fallback test

05WORKED EXAMPLE

Overnight fleet requirement

Twenty vehicles each need 60 kWh before departure and have a six-hour common window.

STEP BY STEP
  1. Average fleet power = 1,200 / 6 = 200 kW
  2. Add charging losses and operational margin
  3. Test individual vehicle and charger constraints
  4. Schedule priority vehicles and late arrivals
INTERPRETATION

The fleet needs at least 200 kW average delivered charging before allowances, not necessarily twenty chargers operating at full nameplate.

06COMMON FAILURE OR MISCONCEPTION

“A 60 kW charger always charges a vehicle at 60 kW.”

CORRECTION

Actual power is limited by the vehicle, charger, battery condition, temperature, state of charge and site controls.

RETRIEVAL PRACTICE · 3 QUESTIONS

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.

OBJECTIVE · Start with operations

What is the first design input?

How confident are you?
OBJECTIVE · Calculate average power

600 kWh must be delivered in 5 hours. Average power before losses is:

How confident are you?
OBJECTIVE · Interpret nameplate

A vehicle accepts 11 kW AC on a 22 kW charger. Likely power is limited to:

How confident are you?
Answer every question and confidence prompt.

08SOURCE NOTES

Sources for further study.

International references support further study. They do not replace Philippine laws, regulations, utility requirements or project specifications.

  1. 01Electric Vehicles for FleetsUS Department of Energy Alternative Fuels Data Center

    Fleet planning, equipment, operations and training considerations.

    Open source ↗
  2. 02State and Local Planning for EV Charging InfrastructureUS Department of Energy Alternative Fuels Data Center

    Charging infrastructure planning framework.

    Open source ↗
Read the complete technical paper

NEXT IN THIS COURSELesson 2 of 514 minutes

The complete grid-to-vehicle power path