120 kW vs 240 kW vs 480 kW DC Charger: A Procurement and Site-Fit Guide
Choose the lowest DC power band that clears energy, vehicle, concurrency, site and acceptance limits—then lock the exact configuration before a purchase order.
Direct answer: Choose 120 kW, 240 kW or 480 kW DC charging only after the project clears five limits: energy needed before departure, usable charging window, vehicle voltage/current acceptance, simultaneous-session allocation and site import capacity. A higher cabinet label does not override any one of those limits. Freeze the exact configuration and prove it through FAT and SAT before approving a purchase order.
This guide helps CPOs, fleet operators, EPCs, distributors and commercial site owners turn a power-band question into a comparable RFQ. It is not a universal charging-speed, infrastructure-cost or compliance promise. Destination rules, site electrical design and the exact charger configuration still require project-specific review.
The 120 / 240 / 480 kW decision at a glance
| Power-band question | 120 kW may be a candidate when… | 240 kW may be a candidate when… | 480 kW may be a candidate when… | Evidence required before deciding |
|---|---|---|---|---|
| Energy and dwell | The required energy fits the usable dwell window after vehicle constraints are applied. | The same site needs more energy within shorter or overlapping windows. | The operating model has documented high-energy, short-window or multi-bay demand. | Vehicle duty ledger: arrival energy, departure target, dwell and overlap. |
| Vehicle acceptance | Representative vehicles can use the requested voltage/current envelope. | The vehicle mix and voltage/current envelope justify a higher usable ceiling. | Representative vehicles and cable/connector options can actually use the proposed configuration. | Vehicle acceptance record and a representative charging test. |
| Concurrent sessions | One or two simultaneous sessions fit the agreed allocation schedule. | Aggregate output and port floors work in the overlap cases. | Multiple sessions/dispenser demand is defined rather than assumed from cabinet kW. | Exact cabinet, connector/dispenser and allocation state table. |
| Site import | Available capacity, protection, transformer/switchgear and operating load have been checked. | The site can support the proposed import or has a staged upgrade path. | Upstream capacity, protection, civil routing and utility process have been assessed before hardware selection. | Site single-line assumptions, load study and utility/AHJ inputs. |
| Acceptance | A configuration and test boundary can be frozen. | The supplier can document configuration, FAT and SAT evidence. | The system architecture, distribution and failure behavior can be witnessed for the ordered build. | Three-record acceptance pack: configuration, FAT and SAT. |
The table is a routing tool, not a universal application map. A long-dwell depot may need less peak power but more ports. A high-throughput public site may need a higher aggregate envelope, but only if vehicles, concurrency and the service connection can use it.
Start with energy and time, not the charger label
The first planning calculation is deliberately simple:
For example, if an illustrative vehicle needs 90 kWh and has a three-hour usable charging window, the baseline is 30 kW. That does not mean a 30 kW charger will necessarily meet the task. The vehicle may reduce power as state of charge rises, another session may overlap, the site may impose a limit, and the charger configuration may have different cabinet and connector boundaries.
Use the equation to expose a gap, not to promise an outcome. Build an operating ledger for each representative vehicle class:
| Input | Why it changes the selection | What to retain |
|---|---|---|
| Arrival state of charge and target departure state of charge | Defines energy to be delivered, not nominal battery capacity. | Route/duty record and planning assumption. |
| Usable charging window | A parked vehicle is not always charging for the entire stop. | Dispatch, driver, access and queue assumptions. |
| Vehicle voltage/current acceptance | Limits instantaneous DC power even at a high-rated station. | OEM information and a project-specific test plan. |
| Overlap window | Determines whether one cabinet serves one or several active sessions. | Arrival/departure distribution or dispatch schedule. |
| Site import and other load | Can restrict the available charging envelope. | Electrical load study and operating controls. |
The U.S. Department of Energy notes that charging time varies with state of charge, battery capacity, vehicle factors, equipment output and electrical-service specifications. A station nameplate is therefore only one variable in a project model.[1]
Use the Five-Ceiling Power-Band Test
Choose the lowest band that clears every active ceiling
Any unknown ceiling pauses the selection. A larger cabinet does not remove it.
A kW band is a candidate only if it clears each active ceiling. The lowest ceiling controls the deliverable result.
Ceiling 1: energy within the usable window
The requirement is the energy the vehicle must receive before departure, divided by the real window available for charging. Include loading, dispatch, access and queue assumptions; do not equate a parking duration with a guaranteed charging duration.
Ceiling 2: vehicle voltage, current and charging curve
At a point in a DC session, electrical power follows:
That identity explains why a charger label does not become vehicle power automatically. At 400 V, 300 A corresponds to 120 kW; at 800 V, the same current corresponds to 240 kW. But a vehicle’s battery-management request, connector/cable ceiling, temperature and state of charge can reduce either voltage, current or both. Chevrolet similarly explains that a vehicle with a lower acceptance rate will charge below a higher-rated DC fast-charging station.[2]
Ceiling 3: cabinet, connector and concurrent allocation
Record all of these separately:
- cabinet rated output;
- maximum output per connector or dispenser;
- aggregate output when sessions overlap; and
- minimum agreed service level for each active session, if the project needs one.
A 240 kW cabinet with two connectors is not automatically two 240 kW sessions. A 480 kW split system is not automatically 480 kW at every dispenser. The allocation rule, module granularity, connector limits, vehicle requests and site cap decide the delivered result. For the detailed two-session state table and witnessed allocation tests, use HG Power’s Dual Gun Charging guide.
Ceiling 4: site import and operating load
The charger’s DC output is not a substitute for an electrical study. The team must establish available service capacity, transformer and switchgear boundary, protection coordination, cable route, metering, other coincident loads, utility requirements and the desired operating limit. The DOE notes that DC fast-charging energization can vary materially with requested site capacity, grid upgrades, location and local processes.[3]
Ceiling 5: evidence and acceptance
The configuration has to be stable enough to test. A chosen rating is not procurement-ready until the order can identify its model, options, cabinet/dispenser relationship, connector/cable arrangement, firmware or backend profile, allocation behavior, documents and acceptance conditions.
What 120 kW, 240 kW and 480 kW actually describe
Those labels commonly describe a DC cabinet or system rating. They do not, by themselves, define every connector’s output, the number of simultaneously active vehicles, the vehicle’s acceptance rate, the site import requirement, or the output that persists at a particular state of charge or ambient condition.
| Label on a quotation | The buyer must ask | Do not assume |
|---|---|---|
| 120 kW | Is this cabinet total, a single output, or an aggregate two-connector limit? | 120 kW to every connector or every vehicle. |
| 240 kW | What happens during equal, unequal, tapering and site-capped concurrent demand? | Automatic equal or dynamic sharing. |
| 480 kW | Is this an integrated cabinet, a power cabinet feeding dispensers, or another architecture? | 480 kW at each bay, all markets or all vehicle classes. |
| Any rating | At which input, voltage/current, temperature and equipment state is it stated? | Continuous output under every condition. |
The distinction becomes particularly important at higher system ratings. More cabinet output may be useful for a larger concurrent demand envelope, but it can also expose a site to a different electrical, civil, controls and acceptance boundary. It is not “future proof” merely because the number is larger.
Route the project by operating pattern
| Operating pattern | First question | Possible direction | What could make that direction wrong |
|---|---|---|---|
| Low-overlap commercial fleet with predictable long dwell | Can required energy be delivered before departure without creating a peak-power problem? | 120 kW may be evaluated alongside port count and overnight scheduling. | Vehicle/window calculation, site load or simultaneous duty may demand another architecture. |
| Mixed public or regional route site | How many sessions overlap, and what service level is needed during the peak? | 240 kW may be evaluated where aggregate demand, connector configuration and site import are documented. | The vehicle mix may not use the envelope; site cap or port allocation may dominate. |
| High-throughput hub, short dwell or suitable heavy-duty duty | Is there demonstrated high-energy, short-window demand and a credible multi-bay/site design? | 480 kW may be evaluated as part of a documented system architecture. | Inadequate upstream capacity, undefined dispenser allocation, unsuitable vehicle/cable envelope or weak utilization evidence. |
| Early-stage site with uncertain demand | Which measurements are missing? | Stage the data collection, electrical route and expansion decision first. | Selecting a large rating solely to avoid future planning. |
This is intentionally not a list of “best applications.” The same duty can resolve differently when the vehicle fleet, country, transformer capacity, parking layout, tariff structure, allowed operating window or service objective changes.
Compare the three bands with verification fields, not marketing labels
| Procurement field | 120 kW selection record | 240 kW selection record | 480 kW selection record |
|---|---|---|---|
| Required energy / window | Representative mission and baseline average power. | Same, including documented overlap windows. | Same, including high-energy or multi-bay demand evidence. |
| Vehicle fit | Voltage/current/charge-curve limits for representative vehicles. | Same for the highest-demand and concurrent vehicle cases. | Same, including the actual connector/cable and vehicle classes expected to use the system. |
| Power architecture | Cabinet vs connector output and number of active sessions. | Aggregate limit, allocation policy and two-session floor. | Cabinet/dispenser relationship, active-position limits and aggregate/site cap behavior. |
| Site fit | Service/load study and protection/interface assumptions. | Utility, transformer/switchgear, cable route and operating cap checked. | Same, plus staged distribution, civil route, protection and expansion/failure-domain review. |
| Acceptance | Configuration record and relevant output/session test. | FAT/SAT state table for concurrency and site limit. | System FAT/SAT including configuration, distribution, concurrent sessions, limits, alarms and recovery. |
No row says “fastest.” A power-band decision is valid only when the configuration record and the test evidence use the same definition of output.
Power band is not a configuration
Trace the kW label until it reaches a witnessed record
Each step changes what the original number can actually prove.
Use this chain when reviewing a quotation:
Rated cabinet/system kW
↓
Exact cabinet + dispenser/connector topology
↓
Per-connector voltage/current/power ceiling
↓
Concurrent allocation and site operating cap
↓
Vehicle request and charging curve
↓
Witnessed delivered-power and acceptance record
Every arrow is a verification point. A brochure may establish a product range. It does not close the arrows for the ordered build.
The Open Charge Alliance describes OCPP smart-charging and load-balancing capabilities, but protocol support alone does not prove a supplier’s internal allocation behavior or a project’s CSMS integration. Require the exact protocol version, enabled functions, local fallback behavior and a message-to-meter test where controls are in scope.[4]
HG Power documentation: use model scope, not portfolio scope
HG Power’s public DC portfolio context spans 40–480 kW. This is a starting point for project configuration; it is not one common specification.
The reviewed CCS1 manual covers named ANSI-DCL120B, DCL180B, DCL240B, DCL360B and DCL480B models. It documents those named ratings within that model family. It must not be used to claim that every 40–480 kW configuration shares its connector, voltage/current, cooling, protocol, protection, certification or concurrent-output behavior.
For a proposal, ask HG Power to provide the exact model code, option list, output basis, connector/cable arrangement, configuration sheet, applicable destination evidence, installation assumptions and test boundary. See the current DC charger specifications as a starting point, then request a configuration-specific response.
Freeze three records before approving a purchase order
| Record | Must identify | Why it matters |
|---|---|---|
| 1. Configuration record | Exact model, options, rating basis, cabinet/dispenser/connector topology, documents, firmware/backend scope and approved changes. | Stops a generic kW label from replacing the ordered build. |
| 2. FAT record | Unit/serial identity, test equipment, conditions, requested/delivered values, concurrent cases, alarms, exceptions and sign-off. | Proves agreed factory-testable behavior before shipment. |
| 3. SAT record | Installed configuration, site input, communications, protection/interface checks, agreed vehicle/session cases, alarms/recovery and open items. | Confirms the integrated system at the real site. |
For a broader factory-evidence method, use the DC charger manufacturer audit and FAT/SAT checklist. For the full site sequence, use the DC fast charger station engineering guide.
Project killers: diagnose the selection before it becomes an order
| Symptom | Likely missing decision | Verify before release | Mitigation |
|---|---|---|---|
| “480 kW” is specified but no vehicle can document comparable acceptance. | Vehicle ceiling. | Vehicle voltage/current request and charging curve. | Recalculate around actual vehicle classes and duty. |
| Two connectors are shown but concurrent output is undefined. | Allocation boundary. | A/B/aggregate state table and FAT case. | Add port floors, allocation behavior and test cases to RFQ. |
| Charger rating is selected before utility discussion. | Site-import ceiling. | Available capacity, upgrade path, protection/interface and operating cap. | Hold final rating or plan a staged electrical route. |
| Cabinet and dispenser terminology are mixed. | Architecture definition. | Single-line concept, topology and output basis. | Freeze terms and drawings before bid comparison. |
| A certificate or protocol logo is offered as the only evidence. | Product/project scope. | Exact model/version, issuer/database route and integration test. | Replace logo claims with configuration-specific evidence. |
| FAT only states “pass.” | Acceptance record. | Test conditions, unit identity, instruments, exceptions and sign-off. | Attach a detailed FAT/SAT protocol to the order. |
When not to choose 480 kW
Do not choose 480 kW merely because a vehicle list includes a high peak acceptance number, a competitor has a higher label, or the site may grow one day. Pause the selection when any of the following is unresolved:
- the required energy fits a lower, properly scheduled configuration;
- the actual vehicle mix cannot use the proposed voltage/current/cable envelope;
- concurrency is assumed rather than measured or contractually defined;
- the utility/site import and protection boundary are not established;
- the cabinet/dispenser/connector allocation rule is unknown;
- site layout, maintenance isolation or failure-domain needs point to another architecture; or
- the project cannot state how the ordered build will be accepted at FAT and SAT.
A lower rating is not automatically lower risk, and a higher rating is not automatically higher throughput. The valid choice is the configuration that closes the operating and evidence gaps.
What this page does not prove
This guide does not prove a universal charging time, exact infrastructure cost, utility approval, certificate applicability, vehicle compatibility, connector availability, power-sharing behavior, session outcome or market compliance for a particular charger. It does not state that every HG Power 40–480 kW unit shares the reviewed CCS1 manual’s characteristics. Those answers require a defined model, destination, vehicle set, site boundary and acceptance plan.
Frequently asked questions
Is a 480 kW DC charger always faster than a 240 kW charger?
No. Delivered power is limited by the vehicle’s present request, connector/cable and charger limits, concurrent allocation and the site operating cap. A higher-rated cabinet may offer a larger available envelope, but it does not override a lower active limit.
How do I calculate the DC charger power I need?
Start with required energy divided by the usable charging window. Then test vehicle acceptance, concurrent sessions, the charger’s exact allocation architecture and available site import. Treat the calculation as a planning baseline, not a guaranteed delivered-power result.
Does a 240 kW dual-connector charger deliver 240 kW to each car?
Not necessarily. The quotation must state cabinet output, per-connector ceiling, aggregate concurrent limit and allocation rule. Request a two-session FAT/SAT test for the exact ordered configuration.
What should I request in a 120/240/480 kW DC charger quotation?
Send destination, vehicle list, required energy and dwell window, concurrent-session requirement, site capacity assumptions, connector/cable needs, cabinet/dispenser topology, backend/OCPP requirements, applicable evidence and FAT/SAT acceptance cases. Request the supplier’s answer against the exact model and options.
Is OCPP enough to prove power sharing?
No. OCPP can support smart-charging controls, but the charger’s internal allocation behavior, enabled implementation, CSMS interoperability and actual meter response must be identified and tested for the project.
Request a configuration review
For a model-specific 120/240/480 kW proposal, send HG Power:
- destination country and responsible project party;
- representative vehicles, connector requirements and voltage/current information;
- energy required by departure and usable charging windows;
- expected concurrent sessions and any minimum service floor per session;
- site service, other-load, transformer/switchgear and operating-cap assumptions;
- preferred cabinet/dispenser/bay arrangement and expansion path;
- CSMS/OCPP, authorization, payment and data requirements; and
- document, FAT and SAT acceptance requirements.
Request a configuration-specific DC charger review. HG Power can then reconcile the requested configuration to the exact model, options and evidence boundary rather than quoting from a generic kW label.
Technical review: Marvin. This guide is procurement planning guidance. Final electrical design, destination conformity, utility engagement and commissioning decisions remain with the responsible project parties.
Sources and related guides
[1]: U.S. Department of Energy Alternative Fuels Data Center — Electric Vehicle Charging Stations
[2]: Chevrolet — DC Fast Charging Station Power Levels
[3]: U.S. Department of Energy — Understanding the Soft Costs of EV Charging