Webasto Cool Top 120-e: What Electric Minibus Buyers Must Resolve Before Installation

News facts: a high-voltage roof system enters the minibus conversation

The Commercial Vehicle Show published a Webasto exhibitor update on March 23, 2026, carrying a manufacturer announcement dated March 2. It introduced the Cool Top 120-e for electric vans, minibuses and related applications. Webasto described a roof-mounted system offering up to 12 kW of cooling, designed around a 400 V DC supply with a stated operating range of 250–460 V DC. The announcement also described CAN integration or an optional dedicated controller. These are manufacturer-reported features, not measurements by VETHY. The report does not approve the unit for every electric chassis or passenger conversion. Read the original announcement.

The useful buying question is how a complete vehicle will support passenger comfort throughout its working day. The analysis below addresses that integration problem. It does not provide installation instructions or claim that another supplier's product can be substituted directly.

Start with the transport duty, not the roof opening

A hotel shuttle, an airport transfer vehicle and a community minibus may use similar body shells while imposing very different cooling demands. A shuttle can have frequent door openings and brief occupied trips. An airport vehicle may stand in direct sun before loading passengers and luggage. A community service may carry passengers who need more consistent conditions and longer boarding times. Those differences affect the operating requirement before anybody chooses equipment.

Write a representative working day in plain language. Include where the vehicle waits, whether it is plugged in, how many passengers board, how often the main door opens and when the driver can request preconditioning. Record whether the rear passenger compartment is separated from the cab. A vendor can then explain what it can support and what information remains missing. A list of vehicle dimensions without these operating details leaves too much to assumption.

High voltage changes the ownership of the decision

A high-voltage HVAC installation requires more than selecting a connector with the right nominal rating. The vehicle manufacturer must define where an auxiliary system may obtain power, under which operating states that power is available and which protection and isolation requirements apply. The bodybuilder must work within those documented boundaries. Qualified high-voltage personnel should carry out the electrical design and validation.

This creates an important purchasing distinction. A roof unit supplier may be responsible for the equipment, but it does not automatically control the chassis power interface. A bodybuilder may understand interior construction without having permission to change traction-system behavior. The fleet may request cooling while parked without knowing that the vehicle changes its available auxiliary power after a shutdown sequence. Put these responsibilities into the project definition instead of discovering them during handover.

Why a 12 V parking AC is a different starting point

Parking air conditioning commonly addresses a limited occupied space during engine-off rest. Passenger HVAC for an electric minibus can address a larger occupied area, repeated door openings and service while driving. The two applications can overlap, but they should not be treated as interchangeable simply because both can use roof-mounted equipment.

Low-voltage and high-voltage designs also impose different electrical integration work. The correct choice follows from the chassis, cooling requirement and operating schedule. There is no universal rule that a higher-voltage system is always the better answer, or that a low-voltage system is always easier to integrate. A buyer comparing alternatives should ask each supplier to identify its supported supply architecture, agreed load case and exclusions in the same format. That makes omissions visible without pretending the systems are identical.

Cooling output and electrical demand belong in separate columns

Cooling capacity describes heat removal under stated conditions. Electrical input describes the energy drawn to provide that service. A headline cooling number therefore cannot be inserted directly into a battery-use calculation. Nor should an efficiency ratio calculated from two unrelated brochure values be presented as a measured result.

For a project comparison, request the relevant capacity and input values together, with ambient conditions, interior conditions and operating mode identified. Ask what happens when the available electrical power is limited. Does the system reduce output, pause, report a warning or depend on an instruction from the vehicle controller? Each behavior can be acceptable in a suitable architecture, but it changes what the driver and passengers experience. The fleet needs that behavior described before accepting a quoted performance target.

Build an operating-state agreement

A parked vehicle is not one electrical state. It may be charging, waiting with a driver present, shut down with no occupants, or preparing for its next trip. A vehicle can also enter a reduced-power condition because of its own energy-management priorities. The HVAC request must be interpreted within those states.

This table is a planning framework, not a claim about any named vehicle. Its purpose is to prevent the sales phrase “works while stationary” from carrying more meaning than the actual integration supports.

CAN capability does not supply the missing control specification

A network interface provides a way to exchange information. It does not by itself define which commands exist, how they are acknowledged, or what the vehicle should do if communications are interrupted. Those details belong in an interface document agreed by the relevant suppliers.

The document should name the owner of temperature demand, on/off authorization, power limitation and fault reporting. It should distinguish a request from confirmation that cooling is available. A dashboard indicator that merely repeats the driver's command can otherwise suggest successful operation when the system has rejected that command. Buyers do not need to publish proprietary network messages; they need evidence that the control responsibilities have been resolved and tested. A dedicated controller can be a valid option, but it still needs an agreed relationship with vehicle power and operating states.

Map the air path through the occupied compartment

The roof unit's location is only the beginning of air distribution. Passengers experience conditions at their seats, not at an equipment outlet. Seat backs, luggage areas, interior partitions and local obstructions can influence where conditioned air reaches. The return-air path matters as much as the visible supply outlets.

Review the interior plan with the HVAC supplier and bodybuilder together. Identify the front and rear occupied zones and the boarding area. Ask how the system will be evaluated with the normal seat arrangement and representative passenger loading. An empty-shell demonstration may be useful early in development, but it cannot settle every question about the finished vehicle. The evaluation should include airflow direction and local discomfort, not just one centrally located temperature reading.

Fresh air and cooling are related but separate requirements

A comfortable temperature does not establish that a passenger compartment has the intended ventilation strategy. Conversely, bringing in more outside air can add a thermal load that the cooling system must handle. The project therefore needs both a comfort requirement and a documented approach to outside-air management.

Avoid treating a feature label as a complete ventilation specification. Ask when outside air is admitted, how the driver knows the selected mode and whether the overall vehicle has other ventilation paths that affect performance. If a public transport or special-purpose application has formal requirements, the responsible vehicle integrator must identify and verify them for the destination market. This article does not assign a universal ventilation rate or claim that an air-conditioning product alone satisfies passenger transport rules.

Roof integration includes more than static dimensions

A drawing should show equipment position, surrounding roof furniture, interior interfaces and areas needed for service. It should also reflect the vehicle manufacturer's structural guidance. An acceptable external footprint does not establish an acceptable roof load, approved opening or mounting method.

The project review should include how maintenance staff will reach the unit and which surrounding components must remain accessible. Consider whether a replacement part can be removed after interior trim, lighting and other roof equipment are fitted. Weather sealing and condensate routing also need clear ownership. A clean-looking installation can still create a difficult service task if the repair process was never reviewed. Resolve these matters in the body design, when changes are still relatively straightforward, rather than expecting an installer to improvise at the end.

A worked energy example without a runtime promise

Consider a hypothetical passenger vehicle whose measured HVAC electrical input averages 2.4 kW during a particular four-hour operating segment. Its energy use for that segment would be 2.4 × 4 = 9.6 kWh. If a separate thirty-minute preconditioning period averaged 3 kW, that period would add 1.5 kWh. The combined illustrative total would be 11.1 kWh.

These assumed values are not specifications for the announced product or any VETHY system. They demonstrate why the operating schedule matters. A fleet must then consider other vehicle energy use and the reserve its vehicle manufacturer requires. It cannot translate this example directly into a promised number of kilometers. The useful next step is to measure a representative duty cycle and identify which parts of the day dominate auxiliary consumption.

Design the acceptance test around passenger service

Before a prototype is evaluated, agree the questions the test should answer. Can the vehicle prepare the compartment before boarding under the chosen conditions? Are front and rear occupied zones within the agreed comfort criteria? Does the system recover acceptably after the representative door-opening sequence? Are warnings understandable to the driver?

Record the conditions alongside the results. Weather, sun exposure, initial interior temperature, occupancy assumptions and power availability all affect interpretation. If a condition falls outside the agreed test envelope, describe that limitation. Do not convert a successful mild-weather test into an all-climate claim. The same discipline applies to failures: a blocked return path or unavailable chassis power should be identified as an integration issue, rather than immediately described as inadequate refrigeration capacity.

Separate development tests from delivery checks

A development program explores the limits and behavior of the design. A delivery inspection confirms that a particular vehicle matches the approved configuration and functions as intended. These activities overlap, but one cannot replace the other. Repeating a short handover check on every vehicle does not prove that the underlying design has been validated for its intended duty.

Use a configuration record to connect the two. It should identify the approved equipment version, control configuration, interior arrangement and relevant installation documents. When a supplier changes a component or the bodybuilder changes a duct, assess whether earlier evidence still applies. The need for reassessment depends on the change; it should not be answered automatically by either “everything must be retested” or “the part number is almost the same.”

Three project situations that change the answer

A hotel shuttle that returns regularly to a charging location may prioritize predictable preconditioning before departure. Its development effort can focus on the transition between charging, waiting and driving, together with repeated boarding events. The chosen operating procedure may be as important as a small change in rated cooling capacity.

A rural minibus with a long route and limited charging opportunities may prioritize energy availability across the complete shift. It needs a realistic reserve policy and a clear response when the vehicle limits auxiliary power. A cooling demonstration at full battery does not resolve the end-of-route question.

A specialist passenger conversion may have separate environmental requirements for different areas of the vehicle. In that case, the first question is whether one air-distribution arrangement can serve them appropriately. The project may need zoning or a different system architecture. None of these scenarios establishes product suitability without the chassis and application review.

Make the commercial scope match the engineering scope

A quotation should say which items and services are included. Equipment supply, interior air distribution, vehicle-interface engineering, installation, commissioning and validation are distinct responsibilities. They can be combined under one contract, but leaving them unnamed makes disputes more likely.

Define the deliverables that accompany each responsibility. For example, an interface document is different from a statement that a product supports a communication protocol. A commissioned prototype is different from an approved series-production configuration. A training session is different from an ongoing service commitment. The buyer should also identify who coordinates questions spanning two suppliers. Without a named owner, a fault can remain unresolved while each party demonstrates that its own component works separately.

What information should a first inquiry contain?

Send the chassis identification and available bodybuilder guidance, the intended passenger layout, the destination market and a representative daily schedule. Include the cooling objective, expected parked operation and any restrictions on roof equipment. State whether the request concerns a prototype, a conversion series or an established fleet modification.

If some information is unavailable, mark it as unknown. An honest gap allows the engineering team to request the right evidence. An estimated roof opening presented as an approved dimension can create expensive rework. For an initial discussion of passenger applications, use the vehicle application overview and the engineering project route. A module-level request should explain how that module fits the larger system; the HVAC integration overview can help structure that conversation.

Plan maintenance around the vehicle's actual availability

Passenger fleets often have short gaps between services. A maintenance plan that assumes an entire free working day may not fit a vehicle that returns late and leaves early. Ask the operator when inspections can realistically happen, where the vehicle can be safely parked for roof access and whether a substitute vehicle is available. These practical constraints shape how faults should be triaged and which parts should be available locally.

A support record should distinguish three levels of action: an operator observation, a workshop diagnosis and a repair requiring specialist involvement. Drivers can report symptoms and warnings without being expected to identify a refrigerant fault. Workshops need the correct equipment documentation and an escalation route. Specialist technicians need a record of what was observed before the vehicle was reset or modified. This division avoids turning every comfort complaint into an improvised electrical investigation.

The fleet should also decide how repeated complaints are reviewed. Several reports from one seating position may point to air distribution or a usage pattern rather than repeated equipment failures. Several vehicles showing the same warning after a software update may require a configuration review. Good records make those patterns visible while preserving the distinction between a suspected cause and a confirmed diagnosis.

Use a staged purchase decision when evidence is incomplete

An unfamiliar chassis conversion does not always justify a full fleet commitment at the first quotation. A staged program can separate feasibility, prototype evaluation and series release. The initial stage resolves whether the required power and mounting interfaces are available. The prototype stage evaluates the occupied vehicle and its controls. The series stage establishes repeatable installation, acceptance and support arrangements.

Each stage needs a clear decision criterion. A prototype that operates successfully for a brief demonstration should not automatically authorize a large order if the intended hot-weather route has not been evaluated. Equally, a minor trim issue should not obscure evidence that the core architecture is suitable. Record open items by importance, owner and deadline so that the commercial decision reflects the remaining work.

This approach is especially useful when several companies share responsibility. It gives the chassis supplier, bodybuilder, HVAC provider and fleet a common set of review points. Buyers can then distinguish a known limitation they accept from an unresolved question they still need answered. The outcome is a defensible specification rather than a collection of optimistic assumptions.

Agree the information that moves from prototype to production

The final prototype report should identify the configuration that produced the accepted result. Include the relevant equipment version, control settings, interior layout and operating conditions. Photographs can support the record, but they should not replace drawings or approved specifications. A later production vehicle must be traceable to that configuration if the earlier evidence is to remain useful.

Also identify what the report does not establish. A test on one route may support that route's use case without proving performance in a different climate or with a changed passenger layout. The procurement team should retain these boundaries when writing marketing or tender responses. Doing so allows the fleet to expand the application deliberately, with additional review where needed, rather than discovering that a sales promise has grown beyond the evidence.

For series supply, assign an owner to review proposed changes before they reach delivered vehicles. A revised air outlet, software configuration or power interface may be minor or significant depending on its effect. The value of the record is that the decision can be made from evidence instead of memory.

Frequently asked questions

Does a higher cooling rating guarantee a better minibus installation?

No. Capacity must be suitable for the actual load, but passenger results also depend on air distribution, available electrical power, control behavior and the completed body. Compare ratings under matching conditions and evaluate the vehicle rather than selecting solely by the largest headline number.

Can a high-voltage roof air conditioner run whenever the vehicle is parked?

That depends on the vehicle's approved power architecture and operating-state rules. A product may support stationary cooling while the finished vehicle imposes additional conditions. Obtain a written answer for the exact chassis and intended parked-use scenario, including how the driver is informed when cooling is unavailable.

Is CAN integration enough to make the system compatible?

No. The project still needs an agreed interface, supported commands, status feedback and fault handling. Compatibility is a conclusion from the complete integration and validation process. A shared communication medium is only one part of that process.

Should fleets ask for a single guaranteed runtime?

A runtime commitment needs defined conditions, usable energy, other electrical loads and a clear end point. Without those details, a single number can hide more than it explains. Request a representative duty-cycle assessment and state which reserve and comfort criteria must remain satisfied.

What is the most useful next decision?

Choose the person or organization responsible for the completed vehicle's HVAC integration. Then agree the operating states and passenger-service requirements before narrowing the equipment selection. This connects the procurement process to an outcome the fleet can inspect: a vehicle that provides the agreed cooling service, with understood limits and a workable support route.