> 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/t4r/list-of-mep-features/renumber.md).

# Renumber

Renumbers all devices and ducts in the selected branch from a given number

**Icon:** <img src="https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/JIiC9eJKxpIbUbycC1ru/image" alt="" data-size="line">

**Location:** ribbon Be.Smart T4R MEP, panel Modify

**Packages:** Be.Smart T4R Silver

{% hint style="info" %}

#### Main functionalities and benefits:

* Create better and more accurate documentation
* Easier access to all MEP elements in a branch
  {% endhint %}

### Overview

The function Renumber ducts renumbers all devices and ducts in the selected branch from a given number. Just select the first element of the duct branch.

If you renumber only a part of the duct, select the start point and the direction of renumbering. In case the branch contains element of the same type and size, it will be assigned the same number.

<figure><img src="https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2F4l2jF3YrLktCozpCOlvC%2F3.gif?alt=media&amp;token=1d66432a-a651-41cc-991f-4c2e21bdf7a3" alt=""><figcaption></figcaption></figure>

### Tutorial

{% file src="/files/hJEUmK54bczkjy6fpHMQ" %}


---

# 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/t4r/list-of-mep-features/renumber.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.