WORLD EV CHARGING

Practical guides

Clearer questions. Better project decisions.

Project planning

Before a site survey

Collect parking counts, electrical drawings, interval demand, planned vehicles, access hours and a responsible project owner. Bring constraints and unknowns to the survey; do not select equipment from a headline rating.

Technology

kW, kWh and the charging curve

kW is a rate; kWh is energy. The simple energy/power calculation assumes constant power. Battery temperature, state of charge, vehicle limits and power sharing can extend real sessions.

Energy

A charger count is not a capacity plan

Total nameplate power can exceed available site power. Establish simultaneous demand and how a controller allocates a shared limit. Decide the fallback when communications fail.

Fleet

Fleet readiness starts with a route

Measure route energy and arrival/departure times. Test seasonal consumption, reserve policy and exceptions. A daily total cannot demonstrate that every vehicle is ready on time.

Operations

Availability needs a definition

Report the denominator, period and exclusions. Separate a powered device from an accessible bay, working payment and completed charging session.

Procurement

Compare offers on lifetime scope

List hardware, civil works, grid connection, installation, software, payment fees, service, spares and replacement. Record what is excluded and who carries the risk.

Economics

Public charging margin is not profit

Subtracting electricity and transaction cost from charging revenue gives a contribution before fixed costs. Tariff peaks, rent, maintenance and financing can materially change the result.

Technology

Open protocols still need acceptance tests

Check version, profiles, certification scope and the required use cases with the chosen hardware and management system. Do not assume a protocol claim proves a complete operating journey.

Energy

Solar is not firm import capacity

Generation changes through the day. Compare hourly or finer profiles and grid limits. Storage requires its own power, energy and loss assumptions.

Operations

Make the handover operable

Require as-built documents, support contacts, access roles, maintenance schedules, safe shutdown procedures and a record of tested recovery scenarios.