480 kW DC Charger: Cabinet, Bay Allocation, Site Fit and RFQ Guide
Turn a 480 kW headline into a defined cabinet-to-bay configuration, a site interface schedule and witnessed acceptance evidence.
Technical review: Marvin
HG Power public DC portfolio: 40–480 kW
Scope: international projects; the ordered configuration and destination requirements control
Quick answer
A 480 kW DC charger should be bought as a defined power pool and bay plan, not as a promise that each connector, vehicle or session will receive 480 kW. The delivered result is limited by the ordered cabinet/dispenser topology, connector voltage-current envelope, vehicle request, simultaneous-use rule, thermal condition and site import limit. Put those limits into the RFQ, then witness them through configuration records, FAT and site acceptance testing.
480 kW at a glance
| Decision item | What the buyer must establish before comparing proposals |
|---|---|
| 480 kW boundary | Is the number the cabinet/system total, a single-output ceiling, or a shared pool? |
| Physical architecture | All-in-one cabinet at the bay, or a central cabinet serving remote dispensers? |
| Bay plan | Number of active bays, connector standard/count, cable reach and traffic layout |
| Allocation | Single-session maximum, simultaneous-session rule, priority, minimum allocation and recovery behavior |
| Vehicle fit | Voltage/current envelope, real charging curve and required energy before departure |
| Site fit | Supply, transformer/service capacity, feeder/protection study, coincident loads and demand-control policy |
| Digital scope | Exact OCPP version/profiles, CSMS, connectivity, payment and offline behavior |
| Acceptance | Order-specific drawings, matched conformity evidence, FAT and SAT cases |
| Quote boundary | Hardware, options, shipping, electrical/civil works, commissioning, warranty, spares and support |
What does “480 kW” mean on a DC charging proposal?
It is a capacity label. It is not enough information to predict a vehicle’s charging power, the output at every bay, or the utility work required for the project.
On the market, a 480 kW label can appear on an integrated cabinet, a central conversion cabinet that distributes power to dispensers, or a system with multiple outlets sharing one conversion pool. Those architectures create different civil layouts, cable routes, maintenance access, utilization patterns and concurrent-output rules. A supplier’s headline kW does not make them equivalent.
The first procurement question is therefore: where does the 480 kW apply, and what has to be true for that capacity to reach a vehicle? Require the bid to state the answer on the ordered SKU—not merely on a product-family brochure.
In simplified DC arithmetic:
power (kW) = voltage (V) × current (A) ÷ 1,000
That relationship is useful for checking a proposed operating point, but it is not a performance guarantee. A real session also depends on the charger’s configured voltage/current envelope, cable and connector limits, the vehicle’s battery-management request, state of charge, battery temperature, allocation logic and site control. The lowest active ceiling sets the result.
For a first decision between power bands, use our 120 kW vs 240 kW vs 480 kW DC charger guide. This page starts after the buyer has a credible reason to investigate the 480 kW class.
The 480 kW Capacity Map
Trace the headline to the actual vehicle-side result
→
→
→
→
→
The active delivery limit is the lowest applicable boundary—not the largest number in the quotation.
Treat the system as six linked limits. The map prevents a project from buying a large cabinet but commissioning an underspecified set of bays.
- Conversion capacity: what the ordered cabinet/system can convert under its documented conditions.
- Topology and bay boundary: which dispensers or integrated outlets are connected to that capacity pool.
- Connector ceiling: the ordered connector, cable and thermal envelope at each bay.
- Vehicle request: the voltage, current and charging curve accepted by each target vehicle.
- Concurrency and site ceiling: the allocation rule when more than one session is active, plus any upstream or energy-management cap.
- Witnessed delivery: the agreed FAT/SAT test result for a defined vehicle or load condition.
This is the important distinction between a nameplate and a project outcome. A 480 kW system can be the right choice while one active vehicle receives less than 480 kW because the vehicle, bay, software setting or site is the controlling limit. That is normal when it is disclosed, designed and tested. It becomes a procurement failure when it was never stated.
Cabinet at the bay or cabinet feeding dispensers?
Two common layouts; one order-specific proof chain
at bayVehicle
All-in-one at the bay
Lock the footprint, cable reach, service access and simultaneous-use rule.
cabinetBay ABay BBay …
Central cabinet + dispensers
Lock the cable route, bay assignment, allocation matrix and fault boundary.
Do not assume a topology from the word “480.” These are common high-power DC architectures; the exact offering must be confirmed in the supplier’s order-specific technical schedule.
| Architecture | Useful when | Buyer must lock down | Typical failure if it is left open |
|---|---|---|---|
| All-in-one cabinet at the bay | The site wants a self-contained charger at each parking position and can accommodate the equipment footprint there. | Cabinet location, connector count, cable management, service clearances, foundations and one/two-session allocation. | The parking layout works on paper but access, cable reach or concurrent behavior does not. |
| Central cabinet with remote dispensers | Multiple bays need a shared conversion pool, while the project can support a separate equipment area and DC distribution layout. | Number/location of dispensers, cabinet-to-dispenser cable route, bay assignment, service access, allocation matrix and fault isolation. | The cabinet is quoted but the required bays, cabling, civil scope or service boundary are missing. |
| Multi-unit site | Demand is distributed across several areas or operating windows. | Whether capacity is pooled, separated or governed by a site energy-management policy. | A site total is mistaken for a guarantee at every bay. |
Ask the supplier to draw the system from utility interface to vehicle connector. The drawing should label every cabinet, dispenser, cable interface, communication path, protective boundary and bay. If the bid cannot show that path, it cannot yet prove the operational result.
For generic questions about allocation at two connectors, see dual-gun charging. A 480 kW project requires the same discipline, but the bay map and upstream interfaces usually make the consequences larger.
Which operations justify a 480 kW system?
The answer starts with duty, not prestige. A 480 kW class project can be relevant where a site needs substantial energy transfer across short or overlapping dwell windows—for example, a high-turnover public hub, a fleet/depot with constrained departure windows, or a corridor/charging operator planning several simultaneous sessions. It can also be a poor fit when grid reinforcement, vehicle acceptance or actual concurrent demand does not support it.
Build a vehicle-and-duty matrix before selecting hardware:
| Vehicle/duty input | Why it matters |
|---|---|
| Vehicle model and DC inlet standard | Confirms physical/protocol compatibility for the destination. |
| Battery voltage architecture and accepted current | Determines whether the vehicle can request the charger’s usable operating envelope. |
| Charging curve over the practical state-of-charge window | Peak acceptance does not describe average energy delivered before departure. |
| Arrival energy, required departure energy and dwell time | Converts operation into kWh and time requirements. |
| Number of overlapping sessions | Determines the allocation schedule the system must demonstrate. |
| Seasonal/ambient conditions and duty sequence | Defines thermal and derating evidence that may be needed. |
| Dispatch priority | Makes it possible to specify whether a departure-critical vehicle receives priority. |
The transparent first-pass calculation is:
ideal charging time (hours) = energy added (kWh) ÷ accepted power (kW)
Use it only to form a question. For example, if a vehicle needs a defined amount of energy before a defined departure, the actual average accepted power—not the largest cabinet number—must satisfy the window. The vehicle charging curve, sharing rule and site cap can all reduce the average. Validate the final schedule with target-vehicle evidence or agreed test loads.
Write the concurrent-bay schedule before choosing the equipment
A high-power project needs a short operating schedule that suppliers can quote against. It should cover every meaningful state, including what happens when a second vehicle arrives and when a session ends.
| Operating state | Required declaration from the bidder | Evidence to request |
|---|---|---|
| One priority bay active | Available minimum/maximum at that bay; cabinet/system total; governing conditions | Configuration record and single-session FAT curve |
| Two or more bays active | Allocation rule, minimum/maximum per active bay, priority behavior and total cap | Concurrent-load FAT case and event record |
| A vehicle finishes or disconnects | Reallocation behavior, response time and operator-visible status | Event log and witnessed reallocation test |
| Site demand cap becomes active | Command source, fallback behavior and evidence of the applied limit | Energy-management/CSMS test case and site record |
| Communications interruption | Local/offline behavior, authorization policy and recovery | Written configuration and resilience test |
Terms such as “dynamic power sharing” are not enough. The buyer needs the actual logic for the offered configuration: which bays can share, which are prioritized, whether allocation changes in fixed or configurable steps, and how the system behaves at the project’s specified site cap. Do not borrow those values from another supplier’s 480 kW brochure.
Site fit: a 480 kW order is also an electrical and civil project
The charger is only one interface in the station. The responsible project engineer must size the upstream system from the ordered equipment data and local requirements—not by copying transformer, breaker or cable numbers from another 480 kW installation.
Prepare a site interface schedule containing:
- supply voltage, frequency, earthing arrangement and available fault information;
- existing and planned service/transformer capacity, plus other coincident loads;
- the exact equipment’s rated input data, efficiency information and demand-control behavior;
- feeder route, installation method, protection coordination, isolation and earthing design;
- equipment/foundation locations, service clearances, dispenser bays, vehicle circulation and cable reach;
- ambient temperature, altitude, rain, dust, salt, drainage, ventilation and flood-risk conditions;
- communications path, signal quality, CSMS ownership and cybersecurity responsibilities;
- accessibility, fire, parking, utility and inspection requirements that apply at the destination;
- civil and electrical division of responsibility, shutdown windows and commissioning sequence.
The supplied HG Power manual advises professional installation and adequate heat dissipation. That is a project boundary, not a generic site design. Electrical, civil, fire-safety and utility requirements must be checked locally against the exact order.
For the wider build sequence from survey through handover, use our DC fast charger station guide.
What is documented for HG Power at the 480 kW class?
HG Power’s public DC portfolio spans 40–480 kW. The reviewed CCS1 120kW ~ 480kW DC charger user manual（起源二代） names a DCL480B model within a CCS1 family, alongside 120, 180, 240 and 360 kW family models.
That is useful product-family evidence, but it is not a universal project specification. It does not by itself establish the available topology, number of bays, connector count, per-bay current, power-sharing rule, cable selection, cooling configuration, sustained duty, destination certificates or price for a proposed shipment. Those points must be verified in the ordered configuration sheet, drawings and matched evidence package.
This distinction matters especially at 480 kW: a sales drawing can look like a complete station while leaving the actual bay behavior and installation interfaces unpriced or untested. Make the configuration schedule part of the commercial offer.
OCPP, CSMS and payments: specify the operating outcome
The Open Charge Alliance defines OCPP as a protocol between a charging station and a charging-station management system. “OCPP supported” does not describe the project outcome.
Write the exact version, edition and required profiles/features into the technical schedule, then test them with the selected CSMS. Depending on the project, the acceptance plan may cover:
- remote start/stop, authorization and transaction records;
- status, fault, diagnostics and availability reporting;
- meter values, tariff handling and time synchronization;
- reservations, local authorization and the offline policy;
- site-power limit commands and the behavior of active bays;
- firmware/configuration control, logs and recovery procedures;
- security and certificate responsibilities;
- payment terminal, acquirer, fiscal and roaming boundaries.
OCPP interoperability, smart charging and payment integration are related but separate acceptance tracks. None should be assumed from the other. Reference the exact protocol requirement and prove the requested workflow on the ordered configuration.
The Cabinet-to-Bay Acceptance Pack
Before approving a purchase order, require five connected records. Together they convert a 480 kW headline into something the project team can test.
- Configuration record: order-specific datasheet, topology drawing, bay/connector schedule, voltage-current envelope, environmental assumptions and software options.
- Site interface record: input requirements, utility/service boundary, cable/protection responsibilities, foundation and bay layout, communications and civil scope.
- Conformity record: destination-required certificates/test reports matched to the ordered model and relevant options—not a generic family logo.
- FAT record: agreed power/allocation conditions, protections, HMI, communications, fault recovery and the configuration actually tested.
- SAT and handover record: installation checks, site communications, target-vehicle or agreed-load sessions, demand-control behavior, training, settings backup, warranty contacts and escalation path.
IEC 61851-23 addresses DC EV supply equipment requirements, including conformity-test and thermal-management topics. A reference to the standard is not proof that a particular configuration is certified or accepted for a specific destination. The proof has to match the ordered equipment and local requirement.
The 14-input RFQ for a comparable 480 kW proposal
Fourteen inputs turn “480 kW” into an answerable project request
Return an assumptions-and-exclusions register with every bid.
Send each supplier the same written inputs. It makes commercial differences visible before they become site variations.
- destination country, codes and installation environment;
- operator type and daily duty model;
- vehicle list, inlet standards, voltage architecture and acceptance data;
- arrival/departure energy, dwell windows and planned session overlap;
- required cabinet/dispenser topology and number of active bays;
- connector type/count, cable reach, cable management and parking geometry;
- required single- and concurrent-session allocation schedule;
- grid voltage/frequency, available capacity, transformer/service data and demand-control policy;
- ambient/altitude/weather exposure and required thermal-duty evidence;
- civil, electrical, utility and communications scope boundaries;
- OCPP edition/profiles, CSMS, connectivity, cybersecurity and offline requirements;
- payment, authorization, metering, fiscal and roaming requirements;
- destination conformity documents plus FAT/SAT cases and acceptance thresholds;
- price boundary: equipment/options, Incoterm, freight, taxes, site works, commissioning, warranty, spares and service.
Ask each bidder to return an assumptions-and-exclusions register. The best proposal is not the one with the largest unqualified number; it is the one that makes the most project interfaces testable.
Four ways a 480 kW project can fail before energization
| Failure mode | Early warning | Corrective action |
|---|---|---|
| Correct cabinet, wrong bay plan | Quote has a cabinet picture but no bay drawing or allocation table. | Freeze the topology, bay count, cable routes and concurrent behavior in the order. |
| Vehicle-side bottleneck | Peak-kW statement has no vehicle voltage/current or curve evidence. | Build and validate a target-vehicle matrix. |
| Upstream boundary hidden | Grid/service work is excluded or site cap behavior is undefined. | Obtain the utility/electrical interface schedule and test demand-control behavior. |
| Evidence pack incomplete | A certificate/logo or “OCPP” line is offered without scope/version/test case. | Match documents to the ordered SKU and witness FAT/SAT cases. |
When should you not choose 480 kW?
Do not choose a 480 kW class system solely because it looks future-ready. Reassess when target vehicles cannot request the usable envelope, operating overlap is low, grid reinforcement dominates the project, a site cap will control most sessions, or a lower-power/multi-unit strategy meets the departure schedule with less complexity.
Likewise, do not reject it only because one vehicle may never receive 480 kW. The relevant question is whether the complete cabinet-to-bay plan delivers the required energy, to the required vehicles, during the actual operating window, within the site boundary. Compare this with our 350 kW DC EV charger guide and HPC vs DC charging guide before assigning a label.
Reality check before issuing an RFQ
- 480 kW at the cabinet is not automatically 480 kW at every connector.
- A shared-power headline is not a concurrent-bay schedule.
- A vehicle peak is not its average energy-delivery rate.
- A system drawing is not an electrical/civil site design.
- A standard reference is not matched destination conformity evidence.
- OCPP support is not completed CSMS, smart-charging or payment integration.
- A hardware price is not the installed, landed and commissioned project price.
Frequently asked questions
Is a 480 kW DC charger 480 kW per connector?
Not necessarily. The number may apply to a cabinet, a system total or a shared pool. The ordered configuration must state the maximum and minimum available at every active bay under the agreed concurrent operating states.
How many vehicles can a 480 kW charger serve at once?
There is no universal answer. It depends on the system topology, ordered outlet count, allocation logic, vehicle requests and site limit. Ask for a bay allocation schedule and a concurrent-load FAT case.
Does 480 kW always mean a split cabinet-and-dispenser system?
No. High-power DC products can use different architectures. Confirm the exact ordered topology, locations, cable interfaces and maintenance boundary from the proposal drawings.
Can a 400 V or 800 V vehicle use a 480 kW system?
Only where the ordered charger’s voltage/current envelope, connector/protocol standard and the vehicle request are compatible. The vehicle will also control its own accepted power through the charging curve.
What electrical supply does a 480 kW charger need?
Use the rated input data for the exact order and have the responsible engineer design the service, transformer, feeder, protection and earthing system for the destination. Do not extrapolate from another project or a cabinet headline.
Does OCPP prove that power sharing will work with the backend?
No. OCPP scope and site power-management behavior must be stated and tested. A protocol line alone does not prove allocation behavior, CSMS interoperability or payment readiness.
Can a user manual prove destination certification?
No. Manuals, certificates and test reports have different roles. Destination requirements must be matched to the ordered model/configuration and verified by the responsible project parties.
Start a 480 kW configuration review
Send HG Power the destination, vehicle matrix, energy/dwell schedule, proposed number of bays, connector requirement, grid information, site environment, backend/payment requirements and requested FAT/SAT evidence. We can map the enquiry to the appropriate configuration within the 40–480 kW DC portfolio, identify open project interfaces and prepare a comparable RFQ basis.
Technical review: Marvin
Primary references
- IEC 61851-23:2023, DC EV supply equipment: https://webstore.iec.ch/en/publication/32973
- Open Charge Alliance, OCPP overview: https://openchargealliance.org/protocols/open-charge-point-protocol/
- Open Charge Alliance, current OCPP downloads: https://openchargealliance.org/my-oca/ocpp/
- HG Power supplied
CCS1 120kW ~ 480kW DC charger user manual（起源二代）.pdf