Published： May 15, 2026
Last Modified：August 17, 2026
Hotels are one of the most interesting building applications for photovoltaic-thermal systems because they can have a substantial and relatively persistent demand for both hot water and electricity.
Unlike many residential buildings, a hotel may require domestic hot water throughout the day, while also consuming electricity for:
This creates an important PVT opportunity:
The hotel may be able to use both outputs of a PVT collector—electricity and useful heat—within the same building.
But a hotel is not automatically a good PVT project.
The engineering question is whether the solar resource, DHW demand, heating/cooling demand, temperature requirements, storage and heat-pump architecture can be matched effectively.
The design approach in this article uses two Solis reference architectures:
The defining characteristic of a hotel is not simply its size.
It is the combination of:
A simplified hotel energy system can be represented as:
This creates several possible pathways for PVT energy.
For many hotels, DHW is not a minor secondary load.
It can be associated with:
The designer therefore needs a time-dependent DHW profile.
At minimum, determine:
A useful design principle is:
Do not size the PVT array from the hotel’s annual DHW consumption alone.
The hourly and seasonal relationship between solar production and DHW demand matters.
Hotels can have thermal demand during periods when solar energy is available.
For example:
Later in the day:
This does not mean solar production and hotel demand will always coincide.
Instead, it means that hotel operation can provide useful opportunities for load matching and storage.
The correct design sequence is:
This prevents a common design error:
selecting the collector field first and attempting to make the building load fit the available PVT output.
A hotel should not be modeled as having one generic “heat demand.”
At minimum, separate:
High-temperature water demand.
Potentially lower-temperature hydronic or air-based heating.
Potentially substantial seasonal demand.
Depending on the property:
Each load may have a different temperature requirement.
Consider two hotels with identical annual thermal demand.
Hotel A uses low-temperature heating.
Hotel B requires substantially higher-temperature water.
Their PVT systems may need very different operating conditions.
The design chain is:
Higher delivery temperatures generally increase the heat-pump temperature lift and therefore affect system performance.
DHW is particularly important because the required temperature can be significantly higher than typical low-temperature space heating.
The reviewed PVT literature identifies:
These values should not be treated as a universal regulatory requirement for every country.
Actual hotel DHW temperature requirements must be established according to the applicable local health, plumbing and building regulations.
The engineering implication is universal:
DHW can impose a substantially higher temperature requirement than low-temperature space heating.
A typical architecture is:
The PVT collector provides a low-temperature renewable heat source.
The heat pump provides temperature lift.
The storage tank provides temporal separation between:
For the Brine 450W reference architecture:
The PVT and refrigerant circuits remain separated.
This provides several identifiable engineering layers:
This architecture is particularly useful for explaining a modular indirect-expansion design.
The DX architecture is fundamentally different.
The PVT collector functions as the heat-pump evaporator.
There is no intermediate thermal-fluid heat exchanger between the PVT collector and refrigerant circuit.
This creates a more direct relationship between:
| Engineering factor | Brine 450W | DX 450W |
|---|---|---|
| PVT thermal-fluid loop | Yes | No |
| Intermediate heat exchanger | Yes | No |
| Refrigerant inside PVT collector | No | Yes |
| PVT/refrigerant coupling | Indirect | Direct |
| Source circuit separation | High | Low |
| Refrigerant distribution through collector | Not applicable | Critical |
| Control requirement | Significant | Particularly demanding |
| Hotel reference role | Indirect-expansion | Direct-expansion |
Neither architecture should be declared universally superior.
The correct selection depends on the complete hotel system.
The review identifies real-time compressor-frequency control as fundamental in DX-PVT-SAHP systems.
The reason is straightforward.
Solar irradiance can change rapidly.
Therefore:
A hotel system may also experience rapidly changing DHW demand.
The control system therefore has to respond to both:
The PVT array is a solar-energy source.
The heat pump is the controllable thermal-capacity component.
Therefore, the two sizing decisions should remain separate.
The reviewed literature explicitly recommends that:
PVT area and heat-pump capacity should not be determined by the same criterion.
In particular, the source recommends defining heat-pump size according to the building’s peak thermal load without relying on PVT contribution.
This ensures that the building remains functional during periods of scarce solar radiation.
The PVT collector field should be evaluated against the hotel’s useful thermal load.
The reviewed literature gives a specific sizing heuristic:
the PVT area should be defined to cover the thermal load in the month with the highest solar radiation, helping avoid excessive hot-water production.
This is a general sizing heuristic from the reviewed literature, not a substitute for project-specific simulation.
The reason is important.
If the PVT field is oversized:
Therefore:
PVT oversizing can reduce useful solar-energy utilization.
Storage should not be treated as an accessory added after collector sizing.
It is part of the system architecture.
Storage can:
There is no universal “hotel PVT storage ratio.”
The reviewed literature states that storage technology and size should be selected according to the design objectives.
Those objectives may include:
The storage system should therefore be modeled together with the collector and heat pump.
Some hotels include:
These can introduce a lower-temperature thermal load.
The source material identifies swimming-pool/spa applications around approximately 27–35 °C, with other cited data extending to 50 °C depending on application context.
This can create an important system-design opportunity:
The system can potentially prioritize different thermal loads according to:
The exact priority strategy must be established project by project.
This is one of the more interesting configurations.
The building may simultaneously require:
The system can therefore operate at different temperature levels.
A conceptual hierarchy is:
The designer should avoid forcing every thermal load to the highest required temperature.
Doing so can increase unnecessary heat-pump temperature lift.
The PVT collector also produces electricity.
Hotels may have substantial electricity consumption from:
Therefore:
This creates a potentially valuable degree of electrical self-consumption.
The electricity and thermal outputs should nevertheless be evaluated separately.
A conventional PV system and solar-thermal system installed separately occupy additional area.
PVT combines electrical and thermal generation on the same collector surface.
For a hotel with limited roof area and simultaneous electricity and hot-water demand, this can be particularly relevant.
But the trade-off remains:
There is no universal PVT configuration that maximizes every output simultaneously.
The reviewed literature identifies an important design trade-off:
This is highly relevant to hotel design.
If the hotel has:
an uncovered architecture may be attractive.
If the hotel has:
a covered architecture may deserve evaluation.
This should be decided from the actual temperature and energy-use profile, not from collector appearance.
A full hotel energy system may require both heating and cooling.
The source review distinguishes between single-source and dual-source PVT-SAHP architectures.
Its system-level conclusion identifies dual-source indirect-expansion systems as particularly promising for covering broader building thermal needs, including:
This is an important distinction from a simple single-source PVT heat-pump system.
Solar-only systems depend strongly on solar availability.
A hotel, however, needs reliable operation regardless of weather.
But:
A second source can improve operational flexibility.
The reviewed literature identifies air and ground as the principal secondary-source options.
A conceptual dual-source Brine/IDX system is:
The second source can provide thermal energy when PVT is insufficient.
This is particularly relevant for hotels where service continuity is more important than maximizing solar contribution at every moment.
The reviewed literature indicates:
Therefore:
| Hotel condition | Secondary-source direction to evaluate |
|---|---|
| Hot/temperate climate | Air source |
| Retrofit project | Air source often practical |
| Cold climate | Ground source may be attractive |
| Existing borehole infrastructure | Ground source deserves evaluation |
| Need for maximum flexibility | Dual-source system |
These are selection directions, not universal rules.
Determine:
Determine:
Separate each load.
Determine daytime and seasonal electricity consumption.
Identify each load’s required supply temperature.
Evaluate:
Based on required peak building thermal load.
Use solar/load analysis and avoid excessive thermal production.
Based on the intended operating strategy.
Coordinate:
Evaluate the complete annual operating profile.
This architecture allows the thermal source, refrigeration system and building circuits to be treated as distinct engineering layers.
The DX architecture requires particularly careful control because the PVT collector is directly coupled to the refrigerant cycle.
A hotel system should be able to answer:
Is useful PVT energy available?
Is there an immediate thermal load?
Can storage accept the available energy?
Should the heat pump operate?
Should an auxiliary source operate?
A conceptual hierarchy is:
Occupancy changes.
Guest behavior changes.
Kitchen demand changes.
Laundry demand changes.
Therefore:
This is why a hotel PVT system should ideally be evaluated using an hourly or otherwise sufficiently time-resolved model rather than only annual totals.
Potentially:
This can make DHW and cooling-related operation important.
Potentially:
This creates the classic solar/load mismatch.
Potentially:
The system may operate with different PVT and heat-pump priorities.
A reliable hotel system must continue to serve guests when:
Possible solutions include:
Therefore:
The solar system should improve the hotel’s energy system—not become a single point of failure for essential hot-water service.
Annual demand hides daily and seasonal mismatch.
Better: develop a time-dependent DHW profile.
A large roof does not mean the entire roof should be covered with PVT.
Better: determine useful collector area from load and solar analysis.
DHW can require substantially higher temperatures than space heating.
Better: model each temperature level separately.
Solar availability is variable.
Better: establish heat-pump capacity from building peak thermal demand.
Excess solar heat can create storage and control problems.
Better: optimize useful thermal utilization.
Storage can determine how much PVT energy is actually useful.
Better: design PVT, heat pump and storage as one system.
The literature reports higher point-in-time COP values in some DX studies but also highlights the lack of long-term DX experimental data and the sensitivity to unstable environmental conditions.
Better: compare architectures using comparable operating conditions and representative time periods.
The available literature provides useful evidence that hotel applications are commercially relevant.
The broader PVT market review identifies hotel applications among real-world PVT deployments.
For example, the reviewed market material documents a hotel installation in the Netherlands using PVT for DHW and electricity, with reported electrical and thermal production figures. These figures are manufacturer/project-source data and should be treated as case-specific rather than universal performance benchmarks.
This distinction matters.
A project example demonstrates:
technical/application feasibility
It does not prove:
universal performance for all hotels.
The strongest engineering reason to investigate PVT for hotels is not simply that hotels have large roofs.
It is the potential convergence of:
This creates a potentially favorable system architecture.
But the project should still be rejected or redesigned if:
| Design question | Engineering implication |
|---|---|
| High DHW demand? | Strong reason to evaluate PVT |
| Significant daytime electricity demand? | Good opportunity for electrical self-consumption |
| Low-temperature heating? | Potentially favorable heat-pump source condition |
| High DHW temperature? | Greater heat-pump temperature lift |
| Swimming pool? | Potential additional lower-temperature thermal load |
| Large roof? | More potential PVT area, but not automatically optimal |
| Strong solar resource? | Higher potential solar contribution |
| Poor winter solar resource? | Dual-source/auxiliary strategy becomes more important |
| Need reliable year-round DHW? | Avoid solar-only dependence |
| Hot/temperate climate? | Air-source dual-source architecture may be attractive |
| Cold climate with favorable ground conditions? | Ground-source coupling may deserve evaluation |
This article provides a hotel-specific PVT system-design framework.
It does not prescribe a universal:
Those values require project-specific engineering.
The Solis Brine 450W and DX 450W configurations are used as reference designs for system architecture and engineering analysis.
They should not be interpreted as proof that either architecture is suitable for every hotel.
Hotels can be strong candidates for PVT where significant DHW and electricity demand coincide with adequate solar resource and suitable roof area.
Hotels can have substantial and relatively persistent DHW demand while also consuming electricity for HVAC, lighting, kitchens, laundry and other services.
Yes. PVT can provide thermal energy directly or act as a heat source for a heat pump producing DHW.
Yes. This is one of the central characteristics of PVT: the same collector area generates both electrical and thermal output.
Start with the hotel’s time-dependent thermal load, solar resource, required temperatures and operating strategy. Do not size the array simply according to roof area.
No. Heat-pump capacity should be established from the building’s required peak thermal load rather than relying on instantaneous PVT output.
Storage is not universally mandatory, but it is often an important part of matching variable solar production with variable DHW and heating demand.
Neither is universally better. Brine separates the PVT thermal circuit from the refrigerant circuit, while DX directly integrates the PVT collector into the refrigerant circuit.
Some PVT heat-pump architectures can support cooling, particularly dual-source configurations. Cooling capability depends on the complete heat-pump architecture and controls.
Yes. Where a pool or spa is present, its relatively low-temperature thermal demand can become another potential thermal sink for the system.
The principal scientific basis for the PVT heat-pump architecture in this article is the peer-reviewed review by Alessandro Miglioli, Niccolò Aste, Claudio Del Pero and Fabrizio Leonforte, from the Architecture, Built Environment and Construction Engineering Department, Politecnico di Milano. The paper reviews PVT solar-assisted heat-pump integration, including DX/IDX, single-/dual-source configurations, component design, sizing and control.
The source specifically supports the following design principles used here:
The separate PVT market/application source documents real hotel applications, including a hotel installation using PVT for DHW and electricity. Those project figures are treated as case-specific evidence, not generalized Solis performance claims.
No certificate number, test-report number, original supplier filename or supply-chain information is exposed.
42. Internal Linking Architecture
Parent
P4 Mother Pillar — PVT Applications for Buildings and Heat Pump Systems: An Engineering Design Guide
Recommended anchor:
PVT applications for buildings
Upstream
P1
What Is a PVT Collector? The Complete Beginner’s Guide
Anchor:
how PVT collectors work
P2
How to Choose the Right PVT Collector
Anchor:
choosing the right PVT collector
P3
PVT System Design & Integration
Anchor:
PVT system design and integration
Lateral P4
Published:
P4-I01 — PVT for Residential Buildings
P4-I02 — PVT for Commercial Buildings
To publish:
P4-I04 — PVT for Hospitals
P4-I05 — PVT for Schools
P4-I06 — PVT for Swimming Pools
P4-I07 — PVT for Multi-Family Buildings
P4-I08 — PVT for Industrial Process Heat
P4-I09 — PVT for Agriculture and Greenhouses
P4-I10 — PVT for District Heating
Contextual links
Particularly relevant links from this article:
P4-I06 — Swimming Pools when discussing pool/spa loads;
P4-I07 — Multi-Family Buildings when discussing centralized DHW;
P4-I08 — Industrial Process Heat when discussing hotel laundry/kitchen service loads.
Only link to those URLs after publication.
Downstream P5
Recommended future links:
PVT collector sizing
PVT heat-pump sizing
Thermal-storage sizing
PVT flow-rate design
PVT seasonal performance
COP vs SPF
PVT system controls
The correct architecture depends on:
Hotel Load + Occupancy + DHW + Temperature + Solar Resource + Heat Pump + Storage + Controls
For a project evaluation, establish:
