> 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/workflows/design-day.md).
# Design Day
### Set up a Design Day Model
A Design Day in HVAC pertains to using extreme climatic conditions to size and effectively design heating, ventilation, and air conditioning systems. They are crucial in HVAC for several reasons. They represent extreme weather conditions, ensuring systems are sized to handle peak loads effectively. By focusing on the hottest and coldest days, design days provide a reliable basis for dimensioning heating and cooling systems, preventing underperformance during temperature extremes and in real-world conditions.
Design Days are established automatically through EPW (EnergyPlus Weather) files, encompassing location-specific weather data. A DesignDay object is employed to create these days, specifying parameters such as dry-bulb temperature, humidity, solar radiation, etc. Alternatively, you can create your Design Day to produce multiple Design Days based on project-specific parameters.
More information can be found on Design Day Weather Overview and EnergyPlus Sizing Calculations.
---
# 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/workflows/design-day.md?ask=&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.