Hanon's Integrated Cooling Module: Packaging Gains and Service Questions for EV Buyers

The announcement and its status

On August 12, 2026, Hanon Systems announced that its Highly Integrated Cooling Entity was a finalist for the Automotive News PACE Awards. The release describes a module combining an electric compressor, expansion control, a water-cooled condenser with internal heat exchanger and a chiller. It identifies a production application in the BMW iX3. Finalist status is the confirmed status in that announcement; it is not a statement that the module won the award. [Source]

The news illustrates a broader design direction: purchasing a coordinated thermal assembly rather than separately sourcing every refrigerant-system element. For an OEM, that can change packaging and assembly work. It also changes where technical responsibility and service boundaries sit.

This article examines those tradeoffs from a buyer's perspective. It does not claim equivalence between Hanon's module and any VETHY product. The purpose is to help a customer evaluate an integrated HVAC or thermal-module proposal with clear questions about what is included, what remains outside and how the installed system will be supported.

Define the module boundary before discussing integration

The word integrated can describe mechanical consolidation, shared controls, combined fluid passages or several of these at once. Buyers should ask the supplier to identify the exact boundary. A photograph of a compact assembly cannot show which functions are included or how they interact.

Request a diagram showing every external connection and the function it serves. Include electrical power, communications, fluid connections, mounting and any external sensors. The diagram should identify which components remain on the vehicle side and which are supplied within the module.

Then ask who controls each function. A module may manage internal operation while relying on vehicle-level requests and constraints. The vehicle integrator must understand that relationship to design the surrounding system and interpret its behavior.

This boundary definition is essential for comparing proposals. One supplier may quote an assembly with substantial internal control, while another quotes hardware requiring more vehicle-side development. Both may use the word module, but they do not necessarily offer equivalent scope or integration effort.

Count interfaces that disappear and interfaces that remain

Consolidation can reduce some external connections, but it does not eliminate the need for interfaces. The remaining connections may carry more functions or become more important to the complete system. Buyers should evaluate their quality and accessibility rather than celebrating a smaller count in isolation.

For every external interface, identify its mechanical definition, operating conditions and verification method. Ask how assembly staff confirm the correct connection and how service staff inspect it. A compact layout can be efficient while still requiring careful access planning.

The vehicle-side routing should be reviewed with the module in its actual position. A connection that is convenient on a bench may be obstructed by structure or another system after installation. Include assembly sequence and service removal in the layout review.

Interface reduction should also be considered in the documentation. Fewer visible components can make a system appear simpler to the operator while concealing more internal functions from the workshop. The service information must explain enough of the boundary behavior to support diagnosis without requiring access to proprietary internal design.

Compare installed space rather than component volume alone

A module's external dimensions are only part of its installed envelope. Connections, supports, clearances and removal paths add space. The buyer should compare complete installations using the same assumptions, including any components that remain outside the module.

Ask the packaging team to model the assembly in the intended vehicle. Show the position of service connections and the path used to remove the unit. Include neighboring systems and the stages at which they are installed. This helps identify whether a compact module creates an assembly advantage or simply moves complexity elsewhere.

Mass should also be compared on a consistent basis. A bare module and a complete distributed system are not equivalent measurement boundaries. Include the relevant mounts, lines and external components when evaluating a vehicle-level change.

The useful procurement result is a package comparison tied to the actual vehicle. It should state what has been included and what remains provisional. A smaller component can be valuable, but the installed benefit should be demonstrated rather than assumed from a catalog dimension.

Match the module to the operating cases

An integrated module still has operating limits. Its internal functions must serve the vehicle's required thermal cases, including combinations of cabin and equipment demands where applicable. The buyer should provide an operating-state matrix rather than a single maximum capacity request.

For each state, identify the thermal loads, available power, relevant temperatures and requested control behavior. Include transitions such as starting, stopping or changing from driving to charging. A module that meets separate steady-state cases may still need evaluation during transitions between them.

Ask for performance information at the boundary conditions that matter to the vehicle. If the supplier uses a reference condition that differs from the application, identify the difference. Avoid comparing nominal figures obtained at different conditions or assuming a module has unlimited flexibility because several functions are combined inside it.

The validation plan should link the important cases to evidence. Some may be supported by supplier testing, while others require system or vehicle tests. Assign those responsibilities explicitly so that integration does not become an area that every party assumes another organization has already verified.

Understand control ownership

The vehicle controller and module controller need an agreed relationship. Define which requests the vehicle sends, which constraints it provides and which status information it receives. Separate normal operating commands from diagnostic and configuration functions.

A useful interface describes behavior, not only message names. What does the module report when it cannot satisfy a request? How does the vehicle distinguish waiting, limited operation and a fault? Which information is needed for the driver and which belongs in the service tool?

Version control is particularly important when hardware and software are supplied together. Record the approved combination and the process for updates. A change inside the module can affect external behavior even if the connector and part outline remain unchanged.

The supplier and integrator should test the requested functions together. A shared network technology does not establish compatibility. The acceptance test should use the actual vehicle-side controller or a representative approved test arrangement and document any remaining differences before production release.

A service-boundary thought experiment

Consider a hypothetical vehicle using a consolidated thermal module. A field complaint indicates that one thermal function is not meeting its target. The workshop must determine whether the cause lies inside the module, in an external circuit or in a vehicle request. Replacing the whole module immediately may be costly and may not resolve an external problem.

The service plan should therefore identify the observations available at the module boundary. These may include requested and actual operating states, relevant temperatures, supply conditions and fault information. The exact dataset depends on the design and should be agreed with the supplier.

Next, identify the permitted repair scope. Some assemblies may be exchanged as a complete unit; others may allow specified service operations. The workshop must follow the approved route and have the required capability. Procurement should understand that route before comparing lifecycle costs.

Finally, consider the recovery time. A complete exchange module may simplify a repair if the correct unit is available and commissioning is straightforward. It may be less convenient if the replacement requires long lead time or specialized setup. The right conclusion depends on the actual support arrangement, not an assumption that integrated always means easier or harder to repair.

Evaluate replacement economics with visible assumptions

An integrated assembly can change the balance between production efficiency and service cost. Buyers should examine both without inventing failure rates. Use the supplier's actual replacement scope and the operator's service expectations to create a transparent comparison.

List the cost categories rather than immediately producing a payback number: assembly work, external connections, validation effort, diagnostic capability, replacement parts, commissioning and vehicle downtime. Determine which categories change under the proposed architecture and which remain similar.

Where data is missing, show a range or leave the item unresolved. A precise lifecycle calculation based on an assumed failure frequency can be more misleading than a clear statement that the evidence is not yet available. The procurement team should distinguish a planning scenario from a forecast.

The final comparison should explain the conditions under which each architecture is attractive. A vehicle manufacturer with a strong exchange network may value a different service boundary from a specialist builder supporting small fleets across remote locations. The design and support model should fit together.

Noise needs an installed-system assessment

Thermal modules can contain moving components and paths that transmit vibration or sound. An enclosure or mounting concept may address some of those effects, but the vehicle installation influences what occupants and nearby people experience.

Ask the supplier for acoustic information with test conditions. Identify the operating mode, measurement position and surrounding environment. A number without those details may not be comparable with another proposal or with the customer's vehicle.

The vehicle evaluation should include relevant operating states, especially those in which background noise is low. An acceptable result during driving may not describe a parked vehicle. The test should also consider the locations that matter to the intended occupants or service operation.

If the installation changes, review the effect on vibration paths and sound transmission. Mounts, panels and adjacent structures can influence the result. The buyer should treat module-level acoustic evidence as an input to installed validation, not a guarantee that every vehicle arrangement will sound the same.

Supplier responsibility can become clearer or more concentrated

A module supplier may take responsibility for several internal interfaces that the vehicle builder would otherwise coordinate. That can simplify project management. It can also increase reliance on one supplier's configuration, software and service route.

The buyer should identify which responsibilities are transferred and which remain with the vehicle integrator. The contract and technical specification should agree on that division. A broad promise of system responsibility is not useful if the external boundary conditions are undefined.

Discuss documentation and continuity. What information is available for integration and service? How are revisions communicated? How will replacement support be maintained over the planned vehicle life? These questions are relevant even when the initial module performs well.

The objective is not to avoid integration because it concentrates responsibility. It is to make the concentration deliberate and supportable. A clear boundary can improve accountability when the supplier and customer agree the evidence, change process and service obligations associated with it.

Build a staged evaluation

At the concept stage, review the module boundary, package and operating cases. Identify whether the proposed architecture can meet the vehicle's major constraints. Do not treat that review as final validation; it establishes whether further development is justified.

At the sample stage, check the agreed interfaces and relevant performance conditions. Record the exact hardware and software. If the sample uses temporary fittings or a different control arrangement, identify which results need confirmation in the production-intent installation.

At the vehicle stage, evaluate the complete operating sequence, packaging, controls and service access. Include the cases that depend on surrounding vehicle systems. A module test cannot independently prove behavior that relies on those systems.

Before release, compare the final configuration with the one supported by the evidence. Close remaining issues and provide production and service documentation. This sequence makes the buyer's decision traceable and prevents a promising demonstration from being mistaken for completion of the whole integration task.

Questions for an integrated-module RFQ

Ask the supplier to define the included functions and every external interface. Request performance data at the application's relevant conditions and identify the operating limits. State whether the customer expects a hardware assembly, a controlled subsystem or a broader integration service.

Include the available package, power architecture and vehicle control requirements. Describe simultaneous thermal loads and the intended operating sequence. Give the planned quantities and the stages of the vehicle program so that sample and production needs can be separated.

For lifecycle support, ask about diagnostics, replacement scope, commissioning and change control. Request the information required by the customer's production and service teams. A complete RFQ should make the supplier's scope understandable across the vehicle lifecycle, not only at the point of purchase.

Evaluate responses against the same boundaries. A proposal that leaves more work to the customer may still be suitable, but the remaining work must be visible and resourced. Comparable scope is the foundation of a fair technical and commercial comparison.

Compare an exchange module with a component-repair route

An integrated design changes the practical meaning of a repair. A buyer should compare the approved exchange route with any permitted component-level route using the same operating assumptions. This is a support-planning exercise, not a recommendation to open a module or perform work outside its service instructions.

Start with the event the operator is trying to recover from. The complaint must first be identified and the cause assessed. Both repair routes may require the same initial diagnostic work. A comparison that starts only after the failed item is known can understate the time needed to restore a real vehicle.

For an exchange route, list the steps: confirm the correct replacement, obtain it, prepare the vehicle, replace the assembly through the approved process, commission it and verify the result. The elapsed time depends on stock, access and specialist availability. A complete module can be quick to fit while still creating a long wait if the correct configuration is not available.

For a permitted component route, identify the additional diagnosis, parts, tools and checks required. The component may be less expensive while the repair demands more workshop time or specialist capability. The operator needs to compare the complete supported process, not only the price of the item removed.

Use hypothetical timelines only as planning scenarios. For example, a stocked exchange assembly might be available the same day, while an unstocked one might follow a supplier lead time. Those are conditions to confirm in the actual agreement, not universal advantages of integrated products. Do not invent failure frequency to make one route appear financially superior.

The fleet can then evaluate the value of stock at the appropriate level. Holding one exchange module may support several vehicles if the approved configurations are interchangeable. If they are not, the apparent commonality may disappear. Ask the supplier for the actual supported replacement matrix before planning inventory.

Consider the handling of the removed assembly as well. The agreed process may involve inspection, return or another disposition. The operator should understand packaging, identification and the information required for investigation. A damaged or unidentified returned unit can reduce the value of later technical analysis.

Finally, separate repair success from root-cause closure. Replacing an assembly may restore operation without proving why the original symptom occurred. The supplier and operator should retain the relevant observations so that repeated events can be investigated. Otherwise, an external installation issue could lead to repeated exchanges without a durable resolution.

This comparison gives purchasing, engineering and service a common view of the module boundary. It can reveal that an integrated solution is attractive when supported by the right exchange network, or that another architecture better suits a particular operator. The conclusion follows the actual repair process and evidence rather than a general preference for more or fewer components.

Record the chosen strategy in the vehicle's service plan before production. The plan should identify the responsible organizations, required records and acceptance checks after repair. That turns a packaging decision into a supportable lifecycle decision.

Frequently asked questions

Does PACE finalist status mean the technology won the award?

No. The cited announcement confirms finalist status. Award outcomes require a separate source. The technical evaluation should also remain independent of award language and focus on the evidence relevant to the customer's application.

Is an integrated module always a complete vehicle thermal system?

No. It has a defined boundary and may rely on external circuits, heat exchangers, controls or sensors. Buyers should obtain the boundary diagram and identify the responsibilities that remain outside the module.

Does fewer external connections mean maintenance is automatically cheaper?

Not necessarily. The repair boundary, diagnostic information, replacement availability and commissioning process determine the service outcome. Compare the complete support arrangement rather than connection count alone.

How can VETHY use this approach for customer projects?

VETHY can discuss HVAC module scope and vehicle interfaces around a defined application brief. The proposed assembly, controls and evidence must be confirmed project by project. The Hanon announcement is an industry reference, not proof of a VETHY relationship with Hanon or BMW.

Evaluate the system that the module creates

The most useful question is not how many components have been combined. It is what the resulting boundary allows the vehicle manufacturer to design, assemble, operate and maintain. A well-defined module can make those tasks clearer, provided the surrounding responsibilities remain explicit.

Bring the package drawing, operating-state matrix and service expectations into the first supplier review. Those inputs make it possible to assess an integrated thermal proposal as a complete project decision rather than an attractive compact object on a product sheet.