> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/cut-opening/insert-fire-dampers.md).
# Insert Fire Dampers
{% hint style="info" %}
Temporarily, functionality is accessible through ARKANCE DOCK Cut Opening page:
{% endhint %}
Fire Dampter creation process:
1. **Set up the** [**configuration (mapping)**](/3d-modeling-and-design/cut-opening/opening-configurations/fire-damper-insertion-configuration.md)
2. **Run the Revit "Interference Check"** function for ducts and any structure types that might require fire dampers.
Save the interference check file by exporting the results.
3. **Click on the "Insert/Update Fire Dampers"** in Cut Opening to open the insertion menu.
4. In the newly opened window, **select the recently exported interference check file**. This will lead to the next step of fire damper insertion. 
5. **Click "Next" to launch the insertion table**.
6. **Select the Clashes for which Fire Dampers should be inserted**. Filtering is available via the selection tree on the left side of the window or by filtering the table via filtering options
7. After selecting, click on "OK" to start the fire damper insertion process. Fire dampers will be inserted only for the clashes actively visible in the table.
---
# 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.besmart.software/3d-modeling-and-design/cut-opening/insert-fire-dampers.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.
