PVT Heat Pump System Design Documentation Guide

1. Why PVT System Documentation Matters

A PVT heat pump system involves multiple disciplines:

• photovoltaic engineering;
• thermal engineering;
• refrigeration engineering;
• hydraulic engineering;
• building energy design.

Without structured documentation, important design assumptions may be lost.

A professional documentation system allows engineers to answer:

System Question

Why was this architecture selected?

Performance Question

How was the system expected to operate?

Reliability Question

How was long-term operation considered?

2. Recommended PVT Engineering Documentation Structure

A complete system package can be organized into seven layers.

Layer 1: Project Requirement Document

Defines:

• application type;
• climate conditions;
• heating demand;
• DHW requirement;
• installation constraints.

Example:

Building Type

↓

Energy Demand

↓

Climate Profile

↓

System Objective

Layer 2: System Architecture Document

Defines:

• DX or Brine configuration;
• single-source or dual-source strategy;
• energy flow path.

Brine 450W Architecture

PVT Collector

↓

Brine Loop

↓

Heat Exchanger

↓

Heat Pump

↓

Building

DX 450W Architecture

PVT Collector

↓

Refrigerant Circuit

↓

Heat Pump

↓

Building

Layer 3: Component Selection Document

Defines why each component is selected.

PVT Collector

Document:

• electrical characteristics;
• thermal characteristics;
• mechanical design;
• operating conditions.

Heat Pump

Document:

• source requirements;
• operating range;
• capacity matching.

Supporting Components

Document:

• pump;
• heat exchanger;
• valves;
• controls.

Layer 4: Engineering Calculation Package

The calculation package provides technical justification.

Thermal Calculation

Evaluate:

• available solar heat;
• heat extraction capability;
• heating demand matching.

Hydraulic Calculation

For Brine systems:

Evaluate:

• flow rate;
• pressure loss;
• pump selection.

Refrigeration Calculation

For DX systems:

Evaluate:

• refrigerant behavior;
• evaporation conditions;
• system matching.

Layer 5: Performance Evaluation Document

Defines how system performance is assessed.

Include:

Energy Flow

Solar Input

↓

PV + Thermal Output

↓

Heat Pump Conversion

↓

Building Energy Service

Performance Indicators

Examples:

• thermal output;
• electrical generation;
• heat pump efficiency;
• seasonal contribution.

Layer 6: Verification and Validation Records

Documents:

Verification

Design correctness.

Examples:

• calculation review;
• component compatibility;
• engineering checks.

Validation

Real-world performance.

Examples:

• prototype testing;
• monitoring data;
• field operation.

Layer 7: Operation and Maintenance Documentation

A complete engineering package should also support long-term operation.

Include:

• operating principles;
• inspection points;
• troubleshooting guidance;
• maintenance requirements.

3. Brine 450W Documentation Framework

Engineering Focus:

Hydraulic and thermal integration.

Recommended documentation:

3.1 Hydraulic Diagram

Shows:

• collector arrangement;
• piping;
• pump;
• heat exchanger.

3.2 Flow Design Record

Includes:

• design flow;
• pressure loss;
• pump selection.

3.3 Thermal Transfer Record

Includes:

• source temperature;
• heat extraction conditions;
• heat pump interface.

3.4 Fluid Management Record

Includes:

• fluid characteristics;
• freeze protection;
• expansion management.

4. DX 450W Documentation Framework

Engineering Focus:

Refrigeration integration.

Recommended documentation:

4.1 Refrigeration Circuit Diagram

Shows:

• collector;
• refrigerant path;
• compressor;
• expansion components.

4.2 Refrigerant Matching Record

Includes:

• refrigerant compatibility;
• operating conditions;
• evaporation strategy.

4.3 Control Logic Document

Includes:

• operating conditions;
• protection strategy;
• response to solar variation.

5. Evidence Management Framework

Professional engineering content requires separating evidence types.

Evidence Level 1: Standards and Testing Evidence

Supports:

• verified characteristics;
• standardized evaluation.

Evidence Level 2: Product Engineering Evidence

Supports:

• material choices;
• structural design;
• component decisions.

Evidence Level 3: System Engineering Evidence

Supports:

• system behavior;
• application performance.

Important Principle

A collector test validates collector performance.

It does not automatically validate:

• complete heat pump COP;
• annual energy savings;
• building performance.

System conclusions require system-level evidence.

6. Solis Engineering Content Application

For the Solis PVT Engineering Design Series, each reference design should eventually connect:

Design Knowledge

↓

Engineering Rules

↓

Reference Architecture

↓

Project Application

Example:

Brine 450W Knowledge Chain

Brine Technology

↓

Hydraulic Rules

↓

Reference Design

↓

Heat Pump Project

DX 450W Knowledge Chain

DX Technology

↓

Refrigeration Rules

↓

Reference Design

↓

Integrated System

7. Engineering Document Package Example

A complete project package:

01 Project Requirement

02 System Architecture

03 PVT Collector Selection

04 Heat Pump Selection

05 Hydraulic/Refrigeration Design

06 Control Strategy

07 Performance Evaluation

08 Verification Report

09 Validation Data

10 Operation Manual

8. Common Documentation Mistakes

Mistake 1: Only Providing Product Datasheets

A datasheet does not explain system engineering.

Mistake 2: Missing Design Assumptions

Engineering decisions require traceability.

Mistake 3: Mixing Verified Data With Recommendations

Evidence boundaries must remain clear.

Mistake 4: Ignoring Application Conditions

The same system may behave differently under different climates and loads.

9. Solis PVT Engineering Design Series Documentation Model

The website content structure should evolve from:

Product Information

toward:

Engineering Design Knowledge

Recommended hierarchy:

Technology Knowledge

↓

System Architecture

↓

Design Method

↓

Reference Design

↓

Project Solution