> 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/clt-panels/floor-wood-framing/framing-configuration/opening-framing-general.md).

# Opening Framing – General

**Framing Configuration** may be found in two locations:

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FZWN2FUdrMpndhFbTIoPF%2F0.jpeg?alt=media)

or:

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FMH8qYchuvTKbHXadlako%2F1.jpeg?alt=media)

### Opening Framing

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FPT9VuBMnOHWpRTarmd9n%2F2.jpeg?alt=media)

Opening settings are saved under separate names and can be adjusted for different opening sizes (From – To).

Also, the software will recognize if the opening is inserted into a structural (bearing) or non-structural floor.

**Opening Framing** – settings for framing single openings, which are mostly used for Ducts, Pipes, or other MEP elements.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FagnBoBbV9p8r4CF7FbCj%2F3.jpeg?alt=media)

### Preassembling

**Preassembled –** fills in information for the framing elements (like trimming joists, headers, etc.) from the selected configuration. The configuration can later be scheduled and separately displayed in shop drawings.

**Opening Element Preassembled** – fills in information for the opening, which can be later scheduled and separately displayed in shop drawings.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2F0FiWfd3Bz6sE8o4P7r4v%2F4.jpeg?alt=media)

Fills information into these parameters:

**FM Module Type**

For Openings – writes opening type.

For Connections – writes join configuration name.

**FM Module Mark** – writes **FM Module Type** + **Mark** (from Floor) + **Mark** (from Opening) + unique number.

**FM Module Preassembled –** writes Yes/No if element is (or is not) included in the preassembly.

*Example:*

*Header2 is included in the preassembly so **FM Module Type** parameter has Opening value, **FM Module Mark** parameter contains **FM Module Type** parameter value (Opening) + current floor **Mark** value (F-1, can be seen near **FM HostMemberSortMark**) + current window **Mark** + unique number.*

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2Fpz5F1tgOZNTZL8Ryk9Xf%2F5.jpeg?alt=media)

All these parameters can later be used in the schedules and view filters.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FDsasgdSZUX9UNJZgMywq%2F7.png?alt=media)


---

# 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/clt-panels/floor-wood-framing/framing-configuration/opening-framing-general.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.