60 kW DC Charger: Vehicle Fit, Site Input and RFQ Guide
A configuration-first way to turn a 60 kW label into a vehicle, site and acceptance decision.
Quick answer
A 60 kW DC charger is a commercial DC charging configuration, not a guaranteed 60 kW result at every vehicle or connector. The useful buying question is whether the selected charger can deliver the required energy to the intended vehicles, in the available dwell window, while the site can supply it and the ordered two-port behaviour is written down. For the reviewed HG Power Genesis CCS2 configuration, the sheet lists 60 kW maximum output, two CCS2 outputs, a 200–1000 Vdc output range and 200 A maximum per connector. Vehicle acceptance, concurrent-session allocation, site limits and optional software functions still need project confirmation.
What does “60 kW DC charger” mean?
The label describes a maximum DC output class. It does not reveal the charging curve of the vehicle, the output split when two cars are connected, the site’s available capacity, cable reach, required connector family, payment scope, software integration or destination-market evidence.
The basic electrical identity is P = V × I. A vehicle can only receive the power allowed by the lowest active limit: its requested current and voltage, the charger output envelope, connector/cable limits, any concurrent-session rule, thermal conditions, site controls and the battery charge curve. That is why a cabinet label alone cannot be converted into a session promise.
For first-pass planning, divide the energy you want to add by the available charging window. The result is an average energy-delivery requirement, not a charger selection or a guaranteed session outcome. Losses, battery temperature, starting state of charge, tapering, vehicle software and simultaneous demand must be separately considered.
The reviewed Genesis 60 kW CCS2 configuration: facts and boundaries
The supplied one-page specification is useful because it identifies a configuration rather than leaving “60 kW charger” undefined. It lists CCS2+CCS2 output interfaces, a maximum output of 60 kW, 200–1000 Vdc output voltage, 200 A maximum per connector and two outputs. It also lists a 5 m charging cable, IP54, forced-air cooling and ground mounting.
These are configuration-specific facts. They do not prove that every 60 kW charger has the same architecture, that both connectors can each receive a named share, or that an installed project will achieve a particular charging time. The quotation must retain the model/configuration identifier and any deviations from the reviewed sheet.
| Decision field | Reviewed sheet value | What the project still needs to freeze |
|---|---|---|
| DC output class | 60 kW maximum | Required power at the relevant vehicle voltage and duty point |
| Output envelope | 200–1000 Vdc; 200 A max/connector | Target vehicle voltage/current range and the requested test points |
| Connector arrangement | CCS2+CCS2; two outputs | Connector-market fit, cable routing and simultaneous-session allocation |
| Site-side datum | 380 Vac ±15%, 50/60 Hz, L1+L2+L3+N+PE; 97 A rated input current | Local service, earthing, protection, fault level, cable route and utility approval |
| Product conditions | PF ≥0.99 at 50% load and above; 95% efficiency at nominal output power | Project load profile, metering boundary and any local electrical calculation |
| Environment | −25°C to 55°C; 5–95% non-condensing; ≤2000 m | Actual ambient, solar exposure, airflow, corrosion and installation validation |
A 60 kW delivery ledger prevents the common quote mistake
Six decisions before a 60 kW number becomes a project answer
configurationVehicle
envelopeOutput
envelopeConcurrent
ruleSite
boundaryWitness
rule
The delivered result is governed by the lowest active boundary—not the largest number in a quotation.
Before comparing suppliers, create one line for each boundary below. Every quote should either confirm the line or declare a deviation. The ledger is deliberately more useful than a catalogue comparison because it records the constraints that change delivered energy.
- Named configuration: manufacturer, model, connector count and option list.
- Vehicle envelope: target models, battery voltage range, maximum accepted power/current and planned state-of-charge window.
- Output envelope: voltage/current range, maximum output and conditions for the stated figures.
- Concurrent rule: what happens with one session, two equal requests, unequal requests, vehicle disconnect and restart.
- Site boundary: incoming supply, permitted demand, earthing, protection assumptions, cable route and utility constraints.
- Witness rule: FAT/SAT instruments, test cases, records, tolerances, participants and sign-off.
The active result is set by the tightest line. A 60 kW label cannot overcome a vehicle that asks for less power, a restricted site, or a two-session allocation that has not been defined.
Can two cars charge at 60 kW at the same time?
Two connectors are not a published power split
→
+
→
Witness single, equal-demand, unequal-demand, transition and recovery cases using the ordered configuration.
Not from the information “two outputs” alone. Two outputs show that two connector paths exist. They do not state whether the 60 kW pool is shared, how it is shared, whether it is prioritised, or what happens when two vehicles request different voltage/current combinations.
Ask for an allocation matrix that covers at least these four cases:
| Witness case | Record before and during test | Acceptance question |
|---|---|---|
| One vehicle | Vehicle request, DC voltage/current, charger output and elapsed time | Does the delivered result match the declared single-session boundary? |
| Two equal requests | Both vehicles’ request and output, plus total output | What allocation rule is actually applied? |
| Two unequal requests | Higher/lower vehicle request and both outputs | Does the behaviour follow the written priority or dynamic rule? |
| Transition and recovery | Start second session; end one session; observe remaining session | Does allocation change and recover as the agreed logic says? |
Do not replace this matrix with a generic phrase such as “dynamic sharing”. A dual-output 60 kW tender may specify one full-power output or two shared outputs, but that is an order-specific requirement—not a property that transfers automatically to the reviewed Genesis configuration or to every competitor model.
How vehicle voltage and current change the result
Voltage and current create the output envelope. At a given moment, power is the product of the actual DC voltage and current. A charger may have a wide rated voltage range while a vehicle’s battery-management system asks for less current or begins to taper as state of charge rises. A charger also cannot use a current value above its configured boundary.
Use vehicle data to define the required test points instead of assuming that a higher-voltage vehicle or a lower-voltage vehicle will always receive the same result. For the reviewed configuration, record whether the intended fleet is within the declared 200–1000 Vdc range and whether the expected current is within the stated 200 A maximum per connector. This is an RFQ screen, not vehicle compatibility approval.
For session planning, document the target usable energy, starting and ending state of charge, expected dwell window and the vehicle’s known charging behaviour. Then validate the actual result during commissioning with the agreed vehicle and conditions.
Site input: use the published datum without turning it into a site design
The reviewed sheet lists 380 Vac ±15%, 50/60 Hz, L1+L2+L3+N+PE and 97 A rated input current. It is a valuable starting datum for the named configuration. It is not a universal incoming-supply design, a breaker selection, a transformer recommendation or approval to install at any site.
The responsible local electrical team still needs to assess the incoming service, fault level, protection coordination, earthing arrangement, conductor routing, voltage drop, demand diversity, utility conditions, civil interface and local code route. US Department of Energy guidance likewise treats utility, grid and site processes as linked to charging deployment rather than a simple equipment purchase. Read the DOE overview.
The practical rule is simple: the supplier confirms the ordered equipment boundary; the project team confirms the site boundary; the acceptance plan connects the two. Do not make a site engineer infer these fields from a marketing image or another model’s manual.
Optional OCPP, network and payment functions need an option register
The reviewed Genesis sheet marks OCPP 1.6/2.0.1, Ethernet, 3G/4G, Wi‑Fi and payment functions as optional. Optional is not a weakness—it is a signal to select the functions deliberately. A project can avoid expensive late changes by putting the required software and network behaviour into the RFQ before a quote is compared.
| Option register field | Specify it in writing | Witness it before handover |
|---|---|---|
| CSMS/protocol | Required OCPP version, profiles, backend, security and remote actions | Connection, required messages, session records and recovery behaviour |
| Network | Ethernet/cellular/Wi‑Fi option, SIM/APN responsibility, signal and cybersecurity constraints | Connectivity at the installed location and a documented fault/recovery workflow |
| Access/payment | RFID, app, password and/or payment option; tariff and receipt scope where relevant | Each approved start method, failed authorisation and transaction record |
| User interface | Language, accessibility, display messages and support contact path | End-to-end user flow with the ordered configuration |
Open Charge Alliance documentation distinguishes protocol versions and certification profiles. It does not make an unselected option work, prove that every profile is included or replace a project-specific integration test. Review the protocol context and keep the selected functions in the acceptance checklist.
Where a 60 kW DC charger can be evaluated—and where it should not be assumed
Sixty kilowatts is often evaluated where the operator wants more energy transfer per visit than AC charging but does not automatically need a higher-power DC class. That may include destination, commercial property, light-fleet or public-access situations. These are duty hypotheses, not default application claims.
| Duty question | A 60 kW candidate is worth studying when… | Escalate or reconsider when… |
|---|---|---|
| Dwell window | The average energy need can be met within the realistic stop pattern after vehicle taper is considered. | The operation depends on very short turnarounds or a high daily energy throughput. |
| Concurrent use | The written allocation rule fits the probability of two active sessions. | Two simultaneous sessions each require a defined higher output. |
| Site headroom | The local study supports the equipment and demand-management plan. | Utility capacity, civil route or demand limits make the project infeasible. |
| Vehicle mix | Connector and output envelope are screened against the actual vehicles. | The vehicle fleet, connector direction or voltage needs are unknown. |
| Operations | The selected authentication, CSMS and support process suit the operating model. | Required payment/network behaviours are merely assumed. |
This approach avoids both over-sizing by headline power and under-sizing because the buyer only looked at price. If the duty evidence points higher, compare the next power band with the 120 kW DC charger guide. If the core question is station design, use the DC fast charger station guide.
Make 60 kW quotations comparable
Do not ask several suppliers for “a 60 kW charger” and compare their totals. Ask them to reply against the same scope sheet. A lower price can describe a different connector, no selected communications option, a different cable, different documentation, a different allocation rule or an exclusion that will surface during installation.
| Quote block | Must be explicit | Red flag if absent |
|---|---|---|
| Equipment identity | Model, connector configuration, output envelope, cable length, cooling and enclosure fields | A family brochure is used instead of a configuration sheet. |
| Site interface | Declared AC datum, earthing assumptions, physical interface and exclusions | Supplier implies a site design without project data. |
| Options | OCPP/CSMS, network, payment, authentication, language and accessories | “Included” is stated without a part number or test scope. |
| Evidence route | Destination documents, manuals, drawings and deviation list | Certificate names appear without model, revision or destination scope. |
| Delivery/acceptance | FAT, packing list, commissioning support, SAT steps and record ownership | No written way to prove the ordered performance. |
For supplier due diligence and document control, pair this page with the DC charger manufacturer audit checklist.
FAT and SAT: turn the quote into a witnessed result
Factory acceptance testing (FAT) confirms the agreed configuration before shipment. Site acceptance testing (SAT) confirms the installed result under the defined site and vehicle conditions. Neither is a substitute for the other.
For this 60 kW class, the test plan should name the serialised configuration, connector set, selected optional functions, test instruments, DC voltage/current/power readings, one-session and two-session test cases, communications checks, safety/protection checks, unresolved items and sign-off roles. Record conditions alongside numbers: vehicle, battery state, ambient conditions and site constraints can change the interpretation.
The goal is not to force a generic number into every test. It is to produce an audit trail that shows whether the ordered unit behaves as the purchaser specified. Destination-specific conformity and electrical commissioning remain the responsibility of the appropriate project parties.
The 12-input RFQ for a 60 kW DC charger
Make every 60 kW proposal comparable
Require an assumptions-and-exclusions register with each technical and commercial reply.
Send these fields together. They make a technical reply possible and give every bidder the same boundary.
- Destination country/region and intended installation setting.
- Project role: owner, CPO, fleet, EPC, distributor or installer.
- Target vehicle models, connector direction and voltage/current information available.
- Usable energy to add and real dwell window.
- Expected simultaneous sessions and operating hours.
- Required connector count, cable reach and parking geometry.
- Required allocation behaviour for one and two sessions.
- Available site supply and any utility/load-management constraints.
- Ambient, altitude, enclosure exposure and civil-installation constraints.
- Required OCPP/CSMS, network, authentication and payment scope.
- Documentation, destination evidence and language requirements.
- FAT/SAT test cases, witnesses, sign-off rule and desired commercial scope split.
Ask every reply to include an assumptions-and-exclusions register. That one request makes “60 kW DC charger price” comparable because the buyer can see what the number includes—and what it does not.
Frequently asked questions
Is a 60 kW DC charger enough for my site?
It may be a candidate when the real dwell pattern, vehicle acceptance, expected concurrency and local site capacity fit the required energy delivery. Screen those four constraints before selecting by nameplate or price.
Does two CCS2 outputs mean 30 kW per car?
No. The reviewed sheet identifies two outputs, not a universal split. Require the ordered configuration’s allocation matrix and witness one- and two-session tests.
What AC supply does the reviewed Genesis configuration list?
The reviewed sheet lists 380 Vac ±15%, 50/60 Hz, L1+L2+L3+N+PE and 97 A rated input current. A local electrical professional must still validate the actual service and protection design.
Are OCPP and payment included?
The reviewed sheet labels OCPP 1.6/2.0.1 and payment functions optional. Specify the exact selected option and the integration test in the RFQ.
What should be proven before shipment and handover?
Freeze the named configuration, output envelope, allocation rule, selected options, documents and FAT/SAT witness cases. The record should show the conditions as well as the results.
Request a defined 60 kW CCS2 configuration
HG Power’s public DC portfolio context spans 40–480 kW. Share the 12 RFQ inputs above, and request a configuration-specific response with the selected options, declared boundaries, documents and acceptance plan. If a requirement cannot be confirmed in writing for the ordered configuration, keep it open rather than assuming it is included.