> 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.md). # List of MEP Features


Split	Splits the selected duct/pipe into segments of a specified length	Split
Renumber	Renumbers all devices and ducts in the selected branch from a given number.	Renumber
Delete Pipes / Ducts	Deletes selected part of the pipes	Delete Pipes/Ducts
Split Elbows	Split pipe or duct elbows in two equal-sized elbows.	Split Elbows
Join Systems	Automatically connects all elements that their connectors touch.	Join Systems
Move & Join	Move MEP elements together and join into one system	Move & Join
Duct Insulation	Creates the insulation on ducts or pipes	Duct Insulation
Insulation Area of Fittings	Calculates insulation area on pipe / tube fittings	Insulation Area of Fittings
Duct Description	Enables you to automatically insert duct tags on the connectors	Duct Description
Pipes / Ducts Symbols	Adds direction symbols to selected pipes or ducts	Pipe / Duct Symbols
System Direction	Adds to the floor plan flow direction of vertical pipes	System Direction
Route Length	Displays the total length of selected route elements	Route Length
Units	Assign units to parameters and create schedules with proper units for listed values	Units
Leveler	Change the associated level of selected elements	Leveler

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