MAHLE's Montblanc Cooling Plates: Why the Drawing Is Only Part of the Specification

What the Montblanc announcement establishes

MAHLE's release dated July 29, 2026 reports the start of battery cooling-plate series production at Montblanc, Spain. It describes a gradual production ramp and emphasizes surface quality, cleanliness, corrosion protection and automated manufacturing. Its stated possible peak of 15,000 units per week is a capacity scenario, not a confirmed continuous shipment rate. The release's dateline is used here; some MAHLE listings show July 30. [Source]

The announcement is a useful reminder that a visually simple thermal component can have demanding interfaces. A flat plate with ports may look straightforward in a catalog, yet its performance depends on how it contacts the heat source, distributes fluid and survives the intended environment.

For a vehicle manufacturer or system integrator, the buying challenge is to convert those dependencies into a specification that can be manufactured and verified. This article sets out a practical review method. It does not provide a battery-pack design or claim that VETHY supplies the component in the announced program.

Begin with the mating system

A cooling plate does not operate alone. It interfaces with the heat-producing assembly, a fluid circuit, mechanical supports and the surrounding environment. The specification should identify those interfaces before the supplier proposes a detailed design.

Provide the available installation envelope and the surfaces that must exchange heat. Explain how the plate is supported and which dimensions are fixed by the vehicle or pack. If interface materials are used, identify the organization responsible for selecting and validating them. The plate supplier cannot reliably infer those conditions from an external outline alone.

The fluid circuit needs its own description. State the approved fluid, expected operating range and connection requirements. Identify the pump and upstream or downstream restrictions where those are already known. If they are not yet selected, mark them as open design inputs instead of inventing a convenient flow condition.

The result should be an interface-control document that both sides can review. It does not need to expose the entire vehicle design. It needs to provide the boundary conditions necessary to evaluate the plate and make clear which assumptions remain provisional.

Specify temperature distribution and heat load together

A total heat load is useful, but it does not describe where that heat enters the plate. Different distributions can produce different local temperatures even when the total watts are the same. The supplier needs the spatial and time-dependent load relevant to the application.

Ask the responsible system designer to define acceptable temperatures and temperature differences. Those limits should come from the assembly being cooled. They should not be copied from a general industry article or another vehicle's specification.

For a changing load, provide the operating sequence. A short peak followed by a long recovery period differs from sustained high demand. Starting temperature and available cooling conditions also influence the response. The test plan should reproduce or reasonably represent the conditions that drive the design.

A useful supplier response explains how the proposed plate addresses the defined distribution and identifies any assumptions in the analysis. The buyer can then decide which cases need physical testing. A single favorable average temperature should not replace evidence for the local conditions that matter to the assembly.

Understand the contact interface

Heat must cross the interface between the source and the plate. Surface geometry, contact arrangement and any interface material can affect that transfer. A plate may perform differently when installed with a different contact condition from the one used in its test fixture.

The drawing should identify the critical contact surfaces and the relevant tolerances. The assembly instructions should define the intended installation method. The responsible engineers need to consider how the interface behaves across production variation and the operating environment, not only in a carefully assembled prototype.

If the customer supplies the mating structure or interface material, state that boundary clearly. A supplier test conducted with its own fixture may demonstrate component capability while leaving the customer's interface unverified. That is a reasonable division if everyone understands it and the vehicle-level validation closes the remaining question.

Avoid solving an interface problem by simply demanding more cooling capacity. Additional downstream capability may not correct a local transfer limitation. The useful review asks where the temperature difference occurs and which part of the design controls it. This keeps the engineering effort focused on the actual constraint.

Pressure loss is part of the thermal decision

Flow helps carry heat away, but creating flow requires a pressure difference. A plate's internal passages contribute to the resistance of the complete circuit. The proposed design should therefore be evaluated with both thermal performance and pressure loss in view.

Ask for data at relevant flow rates and fluid conditions. A pressure-loss value without a stated fluid or temperature may be difficult to compare with another proposal. The customer should also identify the pressure available after accounting for other circuit components.

More flow is not a universal solution. It can change pumping demand and may exceed the intended operating conditions of components. The system designer should evaluate the complete circuit rather than optimizing the plate in isolation.

For purchasing, a clear requirement could specify the relevant operating points and the evidence expected at each one. This allows suppliers to propose different internal designs while being judged against the same application. It also prevents a thermal figure obtained under an unusually favorable flow condition from being mistaken for performance in the customer's circuit.

A worked interface review

Imagine a hypothetical buyer requesting a plate for an assembly with a total heat load of 3 kilowatts. The first drawing gives only the external dimensions and port locations. A supplier could respond with a concept, but it would have to make assumptions about contact, fluid and temperature limits.

The revised brief adds a heat-distribution map, the approved fluid, operating temperature range, available flow and allowable pressure loss. It identifies the contact surface and states who supplies the interface material. It also distinguishes a continuous operating case from a short peak case.

Now the supplier can explain whether the proposed design meets the specified boundary conditions and where evidence is still needed. The buyer can compare responses on the same basis. If one proposal needs more flow or a different interface condition, that difference becomes visible before a sample is ordered.

The sample test should preserve those conditions or clearly document any departure. If the test fixture uses a more favorable contact arrangement than the vehicle, the result must be interpreted accordingly. A passing component test cannot silently stand in for a different installed interface.

This example uses hypothetical values and does not describe a MAHLE or VETHY product. Its point is procedural: better inputs reduce hidden assumptions. The most useful specification is not necessarily the longest one, but the one that makes the important boundaries and acceptance conditions explicit.

Cleanliness should have a measurable definition

The word clean can mean different things to different organizations. A thermal circuit may need control of particles, residues or other contamination relevant to its materials and functions. The specification should define what is being controlled and how compliance is checked.

Ask the system designer and supplier to agree the relevant cleanliness requirement, sampling method and acceptance evidence. The requirement should be justified by the application. An arbitrary demanding number can add cost without addressing the actual failure mechanism, while a vague instruction may be impossible to verify consistently.

Packaging and handling belong in the same discussion. A component can leave production in an acceptable condition and lose that condition before assembly. Define how ports are protected, how packages are opened and what happens if the protection is damaged or the component is stored for an extended period.

Incoming inspection should verify the agreed evidence and identify obvious handling problems. It should not create a conflicting process that contaminates the part during examination. The supplier and customer should align their methods so that the acceptance activity preserves the condition it is intended to confirm.

Corrosion protection needs an application context

Corrosion performance depends on materials, coatings, fluid and environmental exposure. A buyer should identify which surfaces see which conditions. Internal fluid exposure and external vehicle exposure may require different evidence and should not be merged into a single unqualified durability claim.

The supplier should explain the proposed protection system and the tests supporting its intended use. Ask whether the test samples represent the production process and whether assembly operations can affect the protected surfaces. A coating specification alone does not describe the completed component's condition.

Changes in material source, surface preparation or coating process may require review. The change-control plan should identify which characteristics are critical and what evidence is needed before a change is accepted. This is especially important when the product moves from a pilot process to a higher-volume line.

Service considerations also matter. The vehicle documentation should identify approved fluids and any relevant inspection or replacement requirements. A component qualification based on one fluid and environment should not be presented as permission for unrestricted substitution throughout the vehicle's life.

Leak testing and pressure requirements need clear boundaries

The component specification should identify its permitted operating conditions and the required verification of fluid containment. The responsible engineers should select the appropriate test methods and acceptance criteria for the design. Procurement's role is to ensure those requirements are explicit and supported by records.

Distinguish development testing from routine production checks. A development test may explore a design's capability, while a production check verifies a defined characteristic on manufactured units or samples. One does not automatically replace the other.

Ask how the result is linked to the component identity and how nonconforming units are managed. A pass indication without traceability may be insufficient for investigating a later issue. Conversely, collecting records that cannot be retrieved efficiently offers little practical value.

The customer should also define the installed-system verification. Connections added during vehicle assembly create boundaries that were not present in the supplier's component test. Responsibility for those checks belongs in the project plan so that each organization understands what its own acceptance evidence covers.

Production ramp-up should preserve the approved process

Increasing output can involve new shifts, additional equipment or revised material flow. The buyer should understand how the supplier maintains the approved characteristics during that change. A capacity ramp is not only a scheduling event; it can also be a quality-control event.

Agree which process changes require notification and which evidence must accompany them. The supplier should identify how operators are trained and how inspection consistency is maintained. The customer should avoid demanding more volume while ignoring the time needed to establish a stable process.

For a new program, use production-intent samples to check the intended manufacturing route. Record any temporary processes or special handling used for the sample batch. If those differ from series production, determine which results remain applicable and which need confirmation later.

The delivery plan should include a realistic ramp and a route for managing deviations. A public peak-capacity figure does not define the customer's allocation or the maturity of a particular variant. Program planning should use the supplier's written commitment for the actual configuration being purchased.

Build a drawing package that different teams can use

Engineering, purchasing, quality and service need related but different information. A strong drawing package connects them without forcing each team to interpret an incomplete technical sketch. The part number and revision should be consistent across the drawing, quotation and validation record.

Identify critical interfaces clearly. Include the external envelope, connection definitions, mounting features and relevant surface requirements. Put performance conditions in a controlled specification rather than burying them in an email that may not reach production staff.

The package should also explain the boundary of supply. Are fittings, seals, protective caps or sensors included? Which items are installed by the customer? Ambiguity here can create assembly delays even when the core plate meets its thermal requirements.

For service, provide an identification route and the approved replacement scope. A technician should not have to infer whether a visually similar part is interchangeable. Configuration control established during development should remain useful after the vehicle enters service.

Questions to resolve before ordering samples

Ask what heat load and distribution the design assumes, which fluid conditions apply and what temperatures must be maintained. Confirm the contact arrangement and identify any assumptions that differ from the intended vehicle. These are the inputs needed to interpret the proposed thermal result.

Then ask how pressure loss, containment, cleanliness and corrosion-related requirements will be verified. Request the distinction between development evidence and routine production controls. Confirm which records will accompany the sample and which will support series production approval.

Finally, review packaging, assembly and change control. Agree how the accepted configuration will be identified and what happens if a material or process changes. This closes the gap between a successful technical sample and a repeatable production component.

The discussion should end with a short list of confirmed requirements and open items. A sample order can then state its purpose precisely. That makes it easier to judge the result and prevents an exploratory prototype from being treated as a fully approved production part.

Review the pressure budget before increasing flow

An illustrative pressure-budget worksheet can show why a plate should not be evaluated alone. Suppose a system designer has established a particular available pressure difference at a required flow. The complete path includes supply lines, connections, the cooling plate, return lines and other circuit elements. Each consumes part of that pressure difference.

The buyer should ask the responsible engineer to assign a justified allowance to each element at the same fluid and operating condition. The allowances are not universal design values. They depend on the actual circuit and should be supported by data or appropriate analysis.

If a proposed plate uses more of the budget than expected, the system may not achieve the intended flow with the selected pump. The response could involve a different plate design, another circuit change or a revised pump selection, but the decision belongs to the complete-system review. Simply requesting more flow from the supplier does not resolve the underlying constraint.

Temperature changes can affect the fluid properties used in the calculation. The worksheet should therefore identify the condition for every value and examine the operating cases that matter. A room-temperature comparison may not describe the most demanding state of the actual vehicle.

The test plan should verify the relevant pressure and flow relationship at agreed points. Measurement locations need to be defined so that the supplier and customer do not include different lengths of line or different fittings in their reported result. A small boundary difference can make two valid measurements appear inconsistent.

This exercise also helps compare competing proposals. One plate may achieve a thermal target at a higher flow than another. If the surrounding system cannot provide that flow within its electrical and pressure constraints, the nominal thermal result may not be usable. The buyer should compare the installed operating point, not select the most favorable isolated number.

For a sample report, retain the fluid identity, temperature, flow, pressure-measurement locations and heat-input condition. Include the configuration of the test fixture where it affects the result. These details allow later engineers to understand whether the test represents the intended vehicle circuit.

The worksheet should remain linked to change control. A revised connector, hose route or filter can alter the circuit even when the cooling plate is unchanged. The customer should review the complete pressure budget after relevant changes rather than treating the plate's original approval as proof that every later circuit arrangement will work.

The practical outcome is a more precise supplier conversation. Instead of asking whether the plate has enough cooling, the buyer can ask whether the proposed thermal performance is available at the flow and pressure conditions the vehicle can actually provide. That question connects component capability to system feasibility.

Frequently asked questions

Is a cooling plate a complete battery thermal management system?

No. It is one element in a wider heat-transfer and control arrangement. The complete system may include fluid circulation, heat rejection, sensors, controls and other equipment. The exact architecture depends on the vehicle and battery requirements.

Does a larger plate always cool better?

Not by itself. Contact, internal flow distribution, available flow and the surrounding circuit matter. The useful comparison is performance under the same application conditions, including the temperature distribution and pressure-loss requirements.

Can a manufacturer's plant announcement prove a supplier's readiness for another project?

It can provide context about manufacturing activity, but it does not qualify a different part or supplier. Buyers need evidence for their own configuration, production process and delivery plan.

How does this relate to VETHY's HVAC work?

It illustrates the system-level questions that should accompany a thermal project inquiry. VETHY can discuss the proposed vehicle HVAC scope and interfaces. Battery cooling-plate design, materials qualification and high-voltage application evidence must be confirmed for the specific project rather than inferred from general HVAC experience.

From component shape to a controlled thermal interface

The most useful lesson from cooling-plate manufacturing news is that performance depends on details that may be invisible in a product photograph. The drawing, operating conditions, manufacturing controls and installed interface must describe the same component in the same application.

For the next inquiry, send the supplier a defined heat path and acceptance plan alongside the geometry. This creates a stronger basis for design, quotation and sample review, and it helps the customer evaluate thermal engineering capability through evidence rather than appearance alone.