> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/user-guide/2d-building/building/hvac/hvac-templates/managed/water-cooled-package-unit.md).

# Water-cooled Package Unit

A water-cooled package unit is a type of HVAC system that utilises water for cooling purposes. It typically consists of a cooling coil, water loop, pump, and controls. The cooling coil removes heat from the air by exchanging it with water circulating through the system. The water loop circulates water between the cooling coil and external heat rejection equipment, such as a cooling tower or chiller. The pump ensures proper water flow, while controls regulate the system's operation based on building cooling demands.

It is composed of:

* Condenser Water Loop
* Air Handling Unit
* Hot Water Loop
* Auxiliary Condenser Water Loop
* Water to Air Heat Pump

The 'Select HVAC Template' form enables you to configure the system to:

* Connect Hot Water Loop to Plant
* Connect Central Air Handing Unit to Zone/s
* Connect single or multiple Air Handing Units
* Choice of Spaces

{% hint style="info" %}
Only available on Premium Plan.  Please reach out for further [support.](https://docs.betterbuilding.io/support-and-training/contact-us.md)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.betterbuilding.io/user-guide/2d-building/building/hvac/hvac-templates/managed/water-cooled-package-unit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
