> 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/energy-efficiency/advanced-hvac/modelling-a-fixed-minimum-air-flow-rate-on-ahus-vavs.md).
# Modelling a fixed minimum air flow rate on AHUs/VAVs
In large buildings with central air handling unit systems, it's common to have an effective minimum air flow rate that exceeds zero. A typical minimum zone air terminal flow rate is 40% of its maximum. It's considered good practice to aim for a 30% turndown, as this significantly reduces central plant energy consumption. This adjustment will have observable effects on annual fan energy consumption and supply airflow rates in the Design Day HVAC Nodes reports.
{% hint style="success" %}
To model a 30% minimum airflow in an air handling unit system for each applicable Space, go to 'Space Sizing', select 'Cooling Supply Air', and adjust the 'Cooling Min. Air Flow Fraction' to 30%. Next, on the 'HVAC Schematic', select each applicable 'VAV Terminal. Go to 'Air Terminal Settings', then 'Sizing', and adjust the 'Constant Min. Air Flow Fraction' to 30%. Lastly, On the 'HVAC Schematic', select each applicable 'AHU Unit'. Go to 'Air Handling Unit Settings', then 'Setpoint Manager Settings', and adjust the 'Min. Turndown Ratio' to 30%.
{% 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/workflows/energy-efficiency/advanced-hvac/modelling-a-fixed-minimum-air-flow-rate-on-ahus-vavs.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.
