> 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/common-for-several-products/smart-assemblies/special-parameters/build-in-place.md).

# Build in Place

**Build in Place** - by default, the 'Create Assemblies' command will add all hosted details to the Assembly. But if you add the 'Build in Place' parameter to hosted element families, and turn it ON, they will not be added to the Assembly. It's useful when you have a few nested elements and some of them should be installed on site, so you don't want to have them in the Assembly.

Parameter should be created like this:

![](/files/1PIsL1DirDnY51ffjWVv)

It's a 'Yes/No' parameter, and its name should be exactly 'Build in Place', so the software can recognize it.

Here's a family with some nested families inside, some of which have the 'Build in Place' parameter.

![](/files/1ufYn06tBe04kIEDIYWO)

So, in the model space, all hardware is in place:

![](/files/V2fbk1MQ36e92tl7PeFI)

But in the Assembly, loose plates are excluded:

![](/files/KxZcdO2BVMNY7qfXkSCH)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.besmart.software/common-for-several-products/smart-assemblies/special-parameters/build-in-place.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.