EV Charging Station Components and Architecture: A Procurement and RFQ Guide
Map every power, control and evidence boundary before comparing an EV charging station quote.
Direct answer: An EV charging station is not one box. It is a chain from the site service and protection through power conversion, cabinet or dispenser, connector, controls, metering, thermal management and vehicle acceptance. A procurement-ready design defines each boundary, identifies the component that owns each limit, and tests the complete chain at factory and site acceptance. Use the map below to turn a generic charger quote into a comparable architecture.
EV charging station components at a glance
Trace energy, control and evidence through one station
The visible charger is only the delivery point in a larger electrical and digital system. For a commercial DC station, the buyer normally needs to define at least these layers:
| Layer | Main responsibility | Question for the RFQ | Evidence to request |
|---|---|---|---|
| Site and energy | Bring power to the station safely | What service, transformer, switchgear and feeder are available? | Single-line diagram, service data, protection schedule |
| Protection | Disconnect unsafe conditions | Which fault, isolation and emergency-stop paths act locally? | Protection schedule, interlock logic, FAT test record |
| Conversion | Convert grid AC into controlled DC | What voltage/current envelope and power basis apply? | Exact SKU data sheet and test limits |
| Delivery | Route energy to the vehicle | Is the system all-in-one, cabinet-plus-dispenser or shared-power? | Topology drawing, connector/cable schedule |
| Vehicle interface | Establish compatibility and limits | Which inlet, communication and vehicle acceptance are in scope? | Compatibility matrix and witnessed test plan |
| Control and network | Operate sessions and report status | Which local controller, HMI, backend and OCPP version are included? | Interface list, protocol statement, logs |
| Measurement | Record delivered energy | Where is energy measured and for which billing regime? | Meter model, accuracy class and calibration evidence |
| Thermal and civil | Keep the equipment within its design envelope | What cooling, clearances, drainage, access and foundations are required? | Installation drawing and environmental limits |
The table is deliberately written as a buyer tool. The component name alone is not enough; the quote must say what it controls and how the buyer will verify it.
How do EV charging stations work during a session?
An EVSE session is a coordinated sequence rather than a simple switch-on event. Texas Instruments describes the chain as communication and HMI, safety verification, power conversion, metering and backend connectivity; its DC description places the conversion outside the vehicle. TI’s EVSE application brief is a useful primary reference for the sequence.
1. Detect and communicate
The station detects that a vehicle is connected and establishes the applicable low-level and, where required, high-level communication. The vehicle and EVSE exchange information about connection state, charging limits and session control. The exact signaling path depends on the charging mode, connector and market; do not treat one connector or protocol as universal.
2. Verify protection and vehicle limits
Before enabling energy, the station checks the relevant interlocks and electrical safety conditions. A DC design may include insulation monitoring and independent shutdown paths; an AC design has different residual-current and switching requirements. EVerest’s current hardware reference is useful because it separates high-level software from low-level safety functions and shows why a controller failure must not remove the hardware’s protective boundary. See the EVerest hardware architecture reference.
3. Enable regulated power
In AC charging, the vehicle’s onboard charger performs the AC/DC conversion. In DC fast charging, the station performs the conversion and supplies regulated DC according to the vehicle’s requested voltage and current limits. A nameplate kW value is therefore only one part of the operating envelope: voltage range, current capability, vehicle acceptance and any active power-sharing rule still matter.
4. Meter, report and close the session
The station measures delivered energy, reports status to its local or backend system and closes the session with the relevant transaction data. If the project uses billing, roaming or a CPO backend, the quote must identify the meter location, accuracy/regulatory requirement, network path and OCPP responsibility. The Open Charge Alliance OCPP overview describes OCPP as an open protocol family for communication between charge points and a central system; it does not prove that a particular charger includes a particular version.
The seven-boundary architecture check
Every quote needs an owner, a limit and a document
Use these boundaries in design reviews and supplier meetings. Each one should have an owner, a limit and a document.
1. Vehicle boundary
Record the vehicle or fleet mix, inlet/connector, voltage and current acceptance, communication requirements and target dwell. If a project serves several vehicle families, create a compatibility matrix rather than writing “universal.” A charger can be electrically available while a vehicle remains limited by its own acceptance envelope.
2. Energy boundary
Define where the utility or site service ends and the charging project begins. Capture available service capacity, transformer or switchgear assumptions, feeder route, protection, earthing and any load-management constraint. DOE’s soft-costs guidance is a useful reminder that planning, permitting and installation work are part of the project even though they are not charger hardware.
3. Conversion boundary
State where AC is rectified, how the DC link is controlled, and which power modules or converters are included. For a modular system, define the module count, allocation logic and failure behavior. Do not compare two quotes by cabinet kW alone if one quote is a single output path and the other shares modules across multiple dispensers.
4. Delivery boundary
Separate power cabinet, dispenser, cable, connector and output switching. A remote dispenser may change the civil route, service access, cable length and voltage drop. The quote should show which hardware is in the cabinet, which is at the dispenser and where the final output contactors sit.
5. Control boundary
Identify local controls, HMI, authentication, remote commands, offline behavior, firmware responsibility and backend connection. “Network ready” is not a sufficient requirement. Name the interface, protocol version, security responsibility and log access needed for commissioning.
6. Measurement boundary
Define where energy is measured, whether the meter is AC or DC, what accuracy or legal-metrology regime applies and how readings reach the transaction record. Measurement location affects what losses and events are visible to the operator. The exact local requirement is destination-specific.
7. Acceptance boundary
Agree in advance what will be checked at factory acceptance (FAT), site acceptance (SAT) and handover. A cabinet that powers on at the factory has not automatically proven vehicle compatibility, site protection, backend operation, metering or multi-connector allocation.
Core EV charger components and what each one controls
| Component or layer | It controls | What fails when vague | Request this evidence |
|---|---|---|---|
| Service, transformer and switchgear | Available input power and fault-clearing boundary | The charger is ordered before the site can supply it | Site single-line diagram, service capacity and protection assumptions |
| Surge, overcurrent and emergency isolation | Safe disconnection during abnormal conditions | A software fault is expected to perform a hardware safety function | Protection diagram, emergency-stop logic and test record |
| AC/DC conversion | Rectification, power factor and DC-link creation | The input/output power basis is unclear | Exact configuration data sheet and test limits |
| DC/DC conversion or power module | Voltage/current regulation and module allocation | Low-voltage vehicles or shared outputs are silently limited | Output envelope, module topology and allocation logic |
| Power cabinet | Houses conversion and often upstream control/protection | Cabinet rating is mistaken for per-connector delivery | Topology drawing and per-output allocation table |
| Dispenser and output contactors | Physical delivery, switching and user interface | Cable/connector or shutdown responsibility is missing | Dispenser drawing, contactor/interlock schedule |
| Cable and connector | Vehicle interface and mechanical reach | A regional connector is assumed to work everywhere | Destination/vehicle matrix and connector schedule |
| Control pilot/BMS communication | Connection state and charging limits | Station and vehicle cannot complete the handshake | Interface/protocol statement and test cases |
| Safety MCU, IMD or residual-current functions | Fast local fault response | The high-level controller is treated as the only safety layer | Safety architecture, thresholds and FAT evidence |
| HMI, local controller and CSMS/OCPP | Session control, authentication and reporting | “Online” does not define who owns the backend | Network diagram, version statement and log samples |
| Energy meter | Delivered-energy record and billing/diagnostics | Supplier and operator totals disagree | Meter model, location, accuracy and calibration evidence |
| Fans, liquid/air thermal path and sensors | Operating envelope and derating behavior | A nominal output is read as a sustained guarantee | Model-specific thermal limits and alarm/derating logic |
| Foundations, cable route, drainage and clearance | Physical installation and maintainability | Equipment fits the brochure but not the site | Civil drawing, access/clearance and environmental limits |
EV charger architecture choices: all-in-one, split or modular/shared-power
There is no universal best topology. Choose the architecture that makes the site, vehicle and operating boundary easiest to verify.
| Architecture | What it means | Can fit when | Do not choose it without checking |
|---|---|---|---|
| All-in-one | Conversion, controls and delivery are in one enclosure or close assembly | The site values a compact equipment boundary and the power path is straightforward | Service access, heat rejection, cable reach, civil clearance and future expansion |
| Split cabinet/dispenser | Power conversion is separated from one or more user-facing dispensers | Dispensers need flexible placement or a shared power cabinet is useful | Cable length, allocation per connector, voltage drop, communication and emergency isolation |
| Modular/shared-power | Multiple modules are allocated among outputs by a defined controller | A fleet or public site needs concurrent sessions and a rule for priority | Per-output minimum/maximum, failure behavior, vehicle acceptance and what the kW label represents |
The right comparison is not “which box is better?” It is “which topology makes the seven boundaries explicit, testable and maintainable for this site?”
What must be in an EV charging station RFQ?
11 inputs turn a charger label into a comparable scope
Send these inputs before requesting a final configuration or commercial comparison:
- Vehicle and inlet: makes or classes, inlet/connector, voltage/current acceptance and communication.
- Destination: country/region, grid code, electrical standards, metering and certificate requirements.
- Site service: voltage/frequency, available capacity, transformer/switchgear and protection data.
- Target power: required output basis, dwell or mission, and whether the figure is cabinet, system or per-output.
- Connector count: number of dispensers/connectors and cable reach.
- Concurrent sessions: how many vehicles may charge at once.
- Power sharing: fixed, priority-based or dynamic allocation, plus minimum power per session.
- Communications: local network, backend/CSMS, OCPP version, remote commands and offline behavior.
- Metering: meter location, accuracy, billing or legal-metrology requirement.
- Civil/environment: foundation, cable routes, clearance, ambient range, drainage, noise and service access.
- FAT/SAT and handover: test scripts, drawings, manuals, spare parts, training and acceptance records.
If a supplier cannot map its offer to these inputs, the quote is not yet comparable. Ask for a marked-up exception list instead of filling the gaps with assumptions.
FAT/SAT evidence: prove the chain, not just the cabinet
| Stage | Evidence to review or witness | Pass condition |
|---|---|---|
| Configuration review | SKU, connector, topology, software/protocol, drawings and destination document list | The supplied configuration matches the approved RFQ inputs |
| Factory safety test | Interlocks, emergency stop, insulation/residual-current functions and contactor behavior | Faults produce the defined local safe state |
| Factory communication test | Vehicle simulator or agreed test vehicle, HMI, backend and logs | Session states, limits and errors are traceable |
| Factory power test | Output envelope, allocation and derating behavior for the quoted configuration | Results are reported against the exact test setup, not a generic brochure |
| Site readiness | Service, protection, earthing, civil work, network and clearances | Site inputs match the approved drawings and responsibility matrix |
| Site acceptance | Vehicle session, simultaneous sessions, metering, backend, emergency stop and restart | Agreed SAT cases pass and exceptions are recorded |
| Handover | As-built drawings, manuals, software/version record, test reports and training | Operator receives the documents needed to operate and maintain the system |
Reality check: a kW label does not complete an architecture
A 350 kW, 480 kW or any other label does not mean every vehicle receives that output. The active limit may be the vehicle’s requested voltage/current, the power modules available to a connector, the site import ceiling, a sharing rule, a thermal derating condition or a destination-specific requirement. Use the 120/240/480 kW DC charger selection guide, 350 kW DC charger guide and HPC vs DC comparison for those downstream decisions.
HG Power scope and configuration boundary
HG Power’s public DC portfolio is presented in the 40–480 kW range. The reviewed CCS1 manual names 120, 180, 240, 360 and 480 kW models in that specific manual family. That distinction matters: the portfolio range is context, while connector, voltage/current envelope, cooling, communication, certificate package and destination requirements must be confirmed for the exact quoted configuration.
For supplier qualification and evidence matching, use How to Verify a DC Charger Manufacturer in China. For station-level design and commissioning, see the DC fast charger station guide. For connector boundaries, use the CCS charger buyers guide and GB/T EV charger guide.
When this architecture checklist is not enough
- A residential buyer looking for a consumer cable or home wallbox needs a different safety and installation guide.
- A permit-ready public site needs destination-specific electrical, civil, accessibility and utility design by the responsible licensed parties.
- A solar-storage, battery-swapping or V2X project adds generation, storage, export and grid-approval boundaries that need their own evidence.
- A vehicle-compatibility question about one connector or model year belongs in the relevant compatibility guide, not in a generic parts table.
Frequently asked questions
What are the main components of an EV charging station?
The main functional layers are site/service and protection, power conversion, cabinet or dispenser, cable/connector, vehicle communication, local controls and backend, metering, thermal management and civil interfaces. The exact parts and boundaries depend on AC or DC mode, destination and topology.
Is the power cabinet the same as the dispenser?
Not always. An all-in-one unit may combine them, while a split system places conversion in a cabinet and user-facing delivery in a remote dispenser. The RFQ should identify where conversion, switching, metering, controls and connectors are located.
How do EV charging stations communicate with vehicles and the backend?
Vehicle communication establishes connection and charging limits; the backend connection supports authentication, monitoring, transaction handling and remote operations. The connector, vehicle, local controller and OCPP/backend responsibilities must be specified for the project rather than assumed from the word “smart.”
What should an EV charger supplier include in a quote?
At minimum: exact SKU/configuration, topology, connector and output envelope, site input assumptions, allocation rules, communication/backend scope, metering, thermal/environmental limits, civil interfaces, FAT/SAT cases and handover documents. Use the 11-input checklist above to mark omissions.
Does a 350 kW label mean every vehicle receives 350 kW?
No. Delivered power is bounded by the vehicle, connector and communication limits, the charger’s configured voltage/current envelope, active power sharing, site capacity and any thermal or destination constraint. A supplier should state the basis of the rating and the evidence available for the exact configuration.
Sources and technical review
- US DOE Alternative Fuels Data Center — Electric Vehicle Charging Stations
- US DOE — Understanding the Soft Costs of EV Charging
- IEC 61851-23:2023 publication page
- Open Charge Alliance — OCPP
- EVerest — Hardware Architecture
- Texas Instruments — EVSE application brief SBAA819
Technical review: Marvin. Product and configuration statements are limited to the evidence scope described above.
Request a configuration review
Send the 11 inputs—vehicle/inlet, destination, site service, target power, connector count, concurrent sessions, power sharing, communications/backend, metering, civil/environmental conditions and FAT/SAT requirements. HG Power can then return a configuration-specific scope instead of treating a generic kW label as a complete station design.