> 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/support-and-training/other-support/webinars/speckel-webinar-archive/airflow-networks-j1v5-tm59-and-natural-ventilation.md).

# Airflow Networks: J1V5, TM59 and Natural Ventilation

The [Airflow Network Mode](broken://pages/DApyfnSgy08TkItRs001)l offers a comprehensive approach to simulating the performance of natural and forced air distribution systems within building, with a particular emphasis on multizone mixed mode or natural ventilation outcomes.

Typically, methodologies such as [CIBSE TM59](broken://pages/bTYb2MBDua0ol1XIcbrE) or the incoming J1V5 Verification Method use airflow networks to establish overheating risk or theoretical heating and cooling loads.

On the 16th of May, Darren O'Dea (Director) provided a practical overview of Speckel's new air flow network features that enable projects to understand and model detailed natural ventilation strategies for compliance and beyond.

{% embed url="<https://www.loom.com/share/cd7603ed10ec40ec866f374efee28a0e?sid=febb10fd-4df6-4022-941d-2e21039ffb21?hide_owner=true&hide_share=true&hide_title=true&hideEmbedTopBar=true>" %}


---

# 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/support-and-training/other-support/webinars/speckel-webinar-archive/airflow-networks-j1v5-tm59-and-natural-ventilation.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.