Voltage window and current duty
State minimum, nominal, maximum, continuous, peak, duration, duty cycle, and transient conditions.
PDU RFQ checklist
PDU RFQ requirements · RFQ checklist and buyer-enablement resource
PDU RFQ Requirements for EV and ESS Projects
A meaningful PDU engineering review starts with the system diagram, duty, protection, interfaces, packaging, environment, and project context. This public checklist helps buyers organize safe, relevant inputs without exposing internal commercial fields.
Minimum information for an initial engineering review
Send the available SLD, voltage/current duty, load or branch list, protection intent, control interfaces, mechanical envelope, environment, project stage, and quantity context. Preliminary information can be labeled as such.
Electrical system data
Load/branch list and single-line diagram
Identify each output, branch owner, load type, connector, protection, switching, sensing, and service relationship.
Fault data and protection requirements
Provide prospective fault current, battery resistance, time constant, bus capacitance, coordination assumptions, pre-charge, fuse, breaker, contactor, and HVIL needs.
Control, sensing, and communication data
- BMS/VCU/PCS/EMS control ownership and sequencing
- CAN/LIN, CAN/RS485, discrete I/O, diagnostics, and frame/interface expectations
- Current/voltage sensing, insulation-monitoring, HVIL, and fault reporting
Mechanical, connector, cooling, and environment data
- Envelope, mounting, busbar route, connector family, service access
- Cooling path, temperature/environment, vibration, altitude where relevant
- Sealing/IP target, enclosure responsibility, harness and installation constraints
Compliance and validation requirements
Identify applicable project standards and acceptance criteria. DVP&R, EOL, insulation, switching, thermal, enclosure, and communication tests should be planned against the approved configuration; no completed test or certification is implied by this checklist.
Project and quantity information
State project stage, prototype/sample context, target production context, expected quantities if available, drawing maturity, and requested engineering deliverables. Commercial terms are reviewed separately and are not promised here.
EV-specific additions
- Vehicle battery and load architecture, BMS/VCU logic, traction/charging/conversion/thermal branches
- Pre-charge, HVIL, service disconnect, vehicle packaging, cooling, and connector requirements
ESS-specific additions
- Rack/cluster arrangement, PCS/DC-bus interface, branch list, fault current/time constant
- Protection coordination, cabinet/enclosure, cooling, service, BMS/EMS/PCS communication and installation
What happens after submission
Engineering can review completeness, clarify the architecture, identify open inputs, align interfaces and protection assumptions, and define a project-specific proposal and validation plan. No fixed quotation timing, MOQ, lead time, or response promise is made.
Buyer checklist
Prepare the review package
Start with the SLD
Show battery, PDU/HVJB, loads or branches, protection, control ownership, and interfaces.
State duty and faults
Provide voltage window, current duty, duration, prospective fault current, resistance, time constant, and coordination assumptions.
Attach integration context
Include mechanical envelope, connectors, cooling, environment/IP, project stage, quantity, and validation expectations.
Evidence context
Real TRHT engineering and testing context
These visuals support a conservative engineering and workmanship context. They do not identify an exact model or prove a universal rating, certification, customer case, or completed validation result.
Buyer questions
Frequently asked questions
What information is required for a custom PDU quotation?
Provide the SLD, voltage/current duty, load or branch list, fault/protection data, controls, interfaces, mechanical envelope, environment, project stage, and quantity context.
Is a single-line diagram required?
It is strongly preferred because it shows power paths, branch ownership, protection, and interfaces that a product name cannot define.
How should peak current and duration be specified?
State peak value, operating voltage, duration, repetition/duty cycle, thermal assumptions, and whether it is normal, transient, or fault-related.
Can TRHT quote before interfaces are frozen?
An early engineering review can identify gaps, but a final technical/commercial proposal depends on sufficiently defined architecture, interfaces, protection, and scope.
Continue your review
Related TRHT resources
Move from category understanding to architecture review, factory context, or an RFQ conversation.