OBC and DC/DC Integrated Unit vs Separate Modules

An integrated OBC/DC/DC unit usually reduces package volume, wiring and integration effort, but concentrates thermal, functional-safety and service risks in one assembly. Separate modules provide more flexibility and easier replacement, yet increase interfaces, validation tasks and installation space.

Which architecture fits the vehicle package?

An integrated OBC/DC/DC platform places the AC charger and high-voltage-to-low-voltage converter in one housing. This can reduce duplicated covers, connectors, mounting brackets, busbars and intermediate cabling. It is attractive where the installation envelope is tight or where the vehicle team wants one coordinated power-electronics package.

Separate modules allow the OBC and DC/DC converter to be positioned according to local constraints. The OBC may sit near the charge inlet, while the DC/DC converter can be located closer to the low-voltage distribution system or auxiliary loads. That flexibility can simplify a difficult vehicle layout, especially in commercial vehicles with several body configurations.

The package comparison must include more than enclosure size. Assess high-voltage creepage and clearance, service access, connector orientation, coolant routing, cable bend radius, mounting stiffness and protection from road contamination. A compact integrated unit can still create installation problems if its mass, access direction or coolant connections conflict with the vehicle structure.

Does integration improve thermal management?

Integration can make thermal management more coherent because the supplier can coordinate semiconductor placement, cold plates, coolant paths and temperature sensing within one assembly. Shared cooling hardware may reduce duplicated interfaces and allow the controls to manage OBC and DC/DC operating states together.

However, the two functions do not always have the same load profile. Charging can produce sustained OBC heat, while the DC/DC converter may experience a different duty cycle driven by vehicle auxiliaries. Their combined heat rejection, transient behaviour and derating limits must therefore be evaluated across charging, driving, idle, hot-soak and low-temperature conditions.

Separate modules can be thermally optimised for their individual power stages and installed at locations with better coolant or airflow access. They also prevent a fault or thermal limitation in one function from automatically constraining the other, provided the vehicle controls and cooling system support that independence.

Which option reduces integration work?

An integrated unit can reduce the number of electrical and mechanical interfaces that the vehicle team must define. One housing may provide a common high-voltage input, low-voltage output, communication network, interlock path and cooling connection. This can shorten interface negotiations and reduce opportunities for wiring errors.

The apparent simplification depends on the supplier’s integration scope. The programme still needs clear definitions for CAN messages, wake-up and sleep behaviour, isolation monitoring, pre-charge coordination, charging permissions, low-voltage load management, fault reactions and emergency shutdown. A single connector does not automatically mean a simple control concept.

Separate modules create more interfaces but can make each one easier to understand and reuse. A fleet platform with several battery voltages, charging requirements or auxiliary-load profiles may benefit from combining a common OBC family with different DC/DC variants, or vice versa. This can reduce redesign when the vehicle portfolio changes.

What happens to serviceability and field support?

With separate modules, a confirmed OBC fault can normally be handled without replacing the DC/DC converter, assuming the vehicle service process supports module-level replacement. This can simplify diagnosis, reduce unnecessary part replacement and preserve a functioning converter when only one subsystem has failed.

An integrated unit may reduce workshop operations because there are fewer assemblies and fewer vehicle-level interfaces. It can also simplify removal if the unit is designed with accessible fasteners, clear lifting provisions and a documented isolation procedure. Conversely, a fault in one internal section may require replacement of the complete unit, increasing logistics exposure and the need for controlled remanufacturing or repair capability.

Serviceability should be agreed during sourcing rather than after design freeze. Define whether internal repair is permitted, whether firmware and calibration are shared, how replacement units are commissioned, how diagnostic data is retrieved and which party owns root-cause analysis. For fleet operators, mean time to restore service may matter more than the initial package benefit.

How does validation scope change?

An integrated platform requires validation of each power function and their interactions. Testing must cover power sharing, control arbitration, fault propagation, thermal coupling, communications, isolation, electromagnetic compatibility and behaviour during transitions between charging, driving, standby and shutdown. The vehicle integration team must also validate the combined unit with the battery, charging inlet, thermal system and low-voltage network.

Separate modules require broader interface validation. Each module must be tested independently, then validated in the vehicle for electrical compatibility, communications, timing, thermal interaction and fault response. More connectors and cables introduce additional EMC, sealing, mechanical and assembly checks.

For road vehicles, the safety case must address the complete electrical and electronic system rather than relying on the enclosure arrangement alone. ISO 26262 covers safety-related electrical and electronic systems across their lifecycle, including development, production, operation, service and decommissioning.[2] UNECE Regulation No. 100 addresses safety requirements for electric powertrains and high-voltage components connected to the traction battery bus.[1][8]

The key question is not which architecture has fewer tests. It is which supplier can provide traceable requirements, failure analysis, diagnostic evidence, software configuration control, EMC records and production controls for the chosen vehicle variant.

Where does total programme risk sit?

Integration concentrates responsibility. If the supplier owns the mechanical, thermal, power and control interfaces, the OEM may gain a clearer escalation path. The risk is that an issue in one internal domain can affect the entire assembly, and a late change may require requalification of multiple coupled functions.

Separate modules distribute risk across suppliers and make substitution more feasible, but they increase coordination effort. Interface changes, software version mismatches, different diagnostic assumptions and separate warranty investigations can create schedule risk. The OEM or Tier-1 must retain strong configuration control and define who owns vehicle-level fault reproduction.

Programme maturity also matters. An integrated unit can be efficient for a high-volume platform with stable requirements and a common electrical architecture. Separate modules may be more suitable for low-volume industrial vehicles, mixed fleets or platforms still undergoing battery and auxiliary-load changes. Neither approach removes the need for a frozen requirements baseline.

How should buyers compare the two options?

Use a weighted comparison that reflects the actual vehicle programme. Give package and harness reduction higher weight when installation volume is constrained. Give serviceability, variant reuse and independent sourcing higher weight when the platform will serve multiple bodies or duty cycles. Include the engineering hours required for interface definition, calibration, testing and field support.

Ask suppliers to identify assumptions instead of presenting only headline specifications. The review should cover operating points, simultaneous-function limits, cooling conditions, communication ownership, software update method, diagnostic access, production end-of-line tests and change-notification periods. Require the same evidence structure from integrated and separate-module bidders.

What should be included in the sourcing specification?

Specify the vehicle voltage range, charging modes, low-voltage output requirements, operating duty cycle, ambient and coolant conditions, installation restrictions, communication protocol, diagnostic requirements and expected service model. Avoid accepting a generic statement that the unit is suitable for the vehicle class.

Require interface control documents, preliminary thermal models, EMC test plans, fault-tree or FMEA outputs, software release procedures and a validation matrix. Ask which requirements are verified by analysis, bench testing, hardware-in-the-loop, vehicle testing or production inspection.

Finally, agree change management before nomination. The contract should define notification lead time, sample approval, regression testing, traceability of hardware and software revisions, spare-unit compatibility and responsibility for regulatory or customer revalidation. Check the supplier datasheet and programme-specific compliance evidence before freezing the design.