> For the complete documentation index, see [llms.txt](https://docs.dietrichs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/design-program/modellbereiche/allgemeines/elemente/gleiche-elementnummern.md). # Identical Element Numbers ## Multiple elements with the same element number For sortable and fixed element numbers, multiple elements can now receive the same number. Until now, an element number was uniquely assigned to a single element. This must be taken into account in many parts of the system: * The same element number cannot exist across different types. When a new element number is assigned, the numbers of the other types are also taken into account. If an element number is forced, the element numbers of the other types are adjusted if necessary. * Example: A fixed element number is set to **E\_14** There already exists a unique element number **E\_14**; this one now receives the next free number, e.g. **E\_15**. * Example: A unique element number is set to **E\_14** There are already multiple elements with the sortable element number **E\_14**; all of these elements now receive the next free number, e.g. **E\_15**. * In DICAM, function 6-5 lists the element MOS, i.e. the element numbers for all elements. * Even with the same element number, there is an entry in the list for each element. * Following the element number in parentheses is a counter and the total number of that element number. So if the element **SE\_12** occurs a total of 5 times, the entries read: **SE\_12 (1/5)** **SE\_12 (2/5) SE\_12 (3/5)** ... The counter has no further meaning; it is assigned arbitrarily. The preview can be used to identify the element. * In the sorting of components, the element, i.e. the element number, can be taken into account. * If two identical components belong to different elements with the same element number, they therefore receive the same sequence number. * To sort elements, their components must be sorted. At the same time, conversely, the element number may need to be considered when sorting the components. The system ensures a unique and technically correct numbering of components and elements even in this situation (circular dependency). ## Effects on results for elements * Element drawings are generated for each element, even if the elements have the same element number. * Even if the elements themselves are identical, they are located in different places in the building. Adjacent walls, components or drawing elements can differ. These differences are also shown on the drawing, which makes them distinct. * If drawings are saved in multiple steps (e.g. by floors) and only one drawing would be created for identical elements, the drawing could be missing in the next step and the element could be overlooked. * As a note, the total number of elements with that number is displayed in the text field of the element drawings after the element number. * Typically the element number is used in the drawing name. Since it is now used for multiple drawings, a counter should definitely be used; otherwise the question of overwriting will repeatedly arise. * The building element list should be used as an overview of the elements. It shows their distribution across building elements (walls, ceilings, roof surfaces) and floors. * In the building element list, identical element numbers within a building element (wall, ceiling, roof surface) are grouped together. For example, if there are 3 identical elements in a ceiling, only one row is created with the quantity 3. Identical elements in different ceilings receive their own rows, since the listing is divided by building element. --- # 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.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/design-program/modellbereiche/allgemeines/elemente/gleiche-elementnummern.md?ask=&goal= ``` `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.