> 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/ashrae-90.1-ecbm/system-no.-10-packaged-terminal-air-conditioner.md).

# System No. 10 Packaged Terminal Air Conditioner

A Packaged Terminal Air Conditioner (PTAC), as defined in EnergyPlus HVACTemplate, is a self-contained climate control system commonly used in buildings such as hotels, apartments, and hospitals. It consists of an integrated unit that combines heating and cooling components in a single package, typically installed through an exterior wall.&#x20;

The system uses a direct expansion (DX) cooling coil and may include electric resistance heating or gas boilers for heating. The PTAC draws outdoor air for ventilation and condenser heat rejection, while fans circulate conditioned air directly into the space, providing independent zone control. This configuration is particularly suitable for applications where decentralised, room-by-room temperature control is preferred.

<figure><img src="https://2129322768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKJnzF2TwHA3APPbiCpF%2Fuploads%2FLi8AFvuFkTbVlbplh5Ob%2Fimage.png?alt=media&amp;token=e5cc39b2-1546-4deb-be4c-705ca84f4a6a" alt=""><figcaption></figcaption></figure>

A PTAC comprises:

* Plant HVAC component  - Hot Water Loop
* Space HVAC component - Packaged Terminal Air Conditioner

The 'Select HVAC Template' form allows for multiple Spaces to be served. Clicking into the 'Spaces' field shows a list of available Spaces. Each selected Space will have one Packaged Terminal Air Conditioner Space HVAC component, providing independent climate control for that zone.


---

# 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/ashrae-90.1-ecbm/system-no.-10-packaged-terminal-air-conditioner.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.
