> 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/customise-fan-performance-curves.md).
# Customise fan performance curves
The EnergyPlus Fan performance curve is a table that describes how electric power consumption varies with air flow rate. For more details, we recommend reviewing the [EnergyPlus documentation](https://bigladdersoftware.com/epx/docs/22-2/input-output-reference/group-fans.html#fanvariablevolume). The observable effect of a custom fan performance curve will be in the annual energy consumption for the air-conditioning fans.
Advanced HVAC allows for custom fan performance curves to be modelled on all HVAC fans. In this example, we model a typical static pressure reset fan curve on an Air Handling Unit fan, per the following coefficients.
$$
P
fan
\=0.0012−0.0579⋅PLR
fan
+0.5864⋅PLR
fan
2
+0.41712⋅PLR
fan
3
$$
{% hint style="success" %}
Customise fan performance curves on an Air Handling Unit fan by selecting a ‘Air Handling Unit’, then the 'Supply Air Fan', and then 'Customise Curves'. Next, select 'Electric Power Function of Flow Fraction' and 'Quartic Curve'. Lastly, enter the coefficients of the fan performance curve. Hit 'Update, then 'Save'.
{% 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/customise-fan-performance-curves.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.
