> 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.md).

# Cut Opening

{% hint style="info" %}
This document describes the functionality of the paid version of **Cut Opening**. If you are using **Cut Opening Free**, it only allows you to place openings when all elements are in the active model (unless the opening file was created in the paid version).

To unlock the full functionality, you can start a free trial of the full version or obtain a license. To do this, look for **Cut Opening** (instead of **Cut Opening Free**) in the **ARKANCE Dock**.
{% endhint %}

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>Getting Started</strong></td><td><a href="/3d-modeling-and-design/cut-opening/getting-started.md">Getting Started</a></td></tr><tr><td align="center"><strong>Opening Configurations</strong></td><td><a href="/3d-modeling-and-design/cut-opening/opening-configurations.md">Opening Configurations</a></td></tr><tr><td align="center"><strong>Opening Updates/Modifications</strong></td><td><a href="/3d-modeling-and-design/cut-opening/opening-updates-modifications.md">Opening Updates/Modifications</a></td></tr><tr><td align="center"><strong>Export/Import MEP Openings</strong></td><td><a href="/3d-modeling-and-design/cut-opening/export-import-mep-openings.md">Export/Import MEP Openings</a></td></tr><tr><td align="center"><strong>Insert Door/Window Openings</strong></td><td><a href="/3d-modeling-and-design/cut-opening/insert-door-window-openings.md">Insert Door/Window Openings</a></td></tr><tr><td align="center"><strong>Insert Fire Dampers</strong></td><td><a href="/3d-modeling-and-design/cut-opening/insert-fire-dampers.md">Insert Fire Dampers</a></td></tr></tbody></table>

Cut Opening defines and reserves spaces in Revit® models for ducts, pipes, cable trays and conduits. Structural engineers and architects can then review, revise, and create the approved holes with just one click. Suitable openings are designed automatically based on the location and types of clashes detected in MEP elements in current, linked, or IFC files.

{% embed url="<https://youtu.be/0zAiZI_Id6w?si=wimlYzOh23DFsZ7k>" %}

• Cut Opening utilizes Revit® „Interference Check“ results for adding openings.

•  Automatically creates openings where **ducts, pipes, cable trays, conduits, fittings, and beams** intersect **walls, floors, roofs, ceilings, structural framing, and structural columns.**

•  Inserts openings with predefined opening shapes.

•  Inserts openings with predefined opening sizes.

•  Joins openings with a predefined auto-join offset.

•  Updates openings if changes with MEP or structural elements were made.

•  Ability to change/delete existing openings if needed.

•  Works with linked files.&#x20;

•  Adds structural openings to structural walls according to architectural windows and doors.


---

# 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.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.
