•In the topology (an individual Area/Line)
•In the building structure (an individual building/building part)
•In the trade structure (an individual trade)
If the mouse is located over a split-able element, the split can be performed from the context menu accessed with a right mouse click. The master project will be closed while the split is being performed.
The Result of Splitting
After splitting, there will be a split project in addition to the master project.
1.The split project contains all elements of the master project, not just the part which is of interest for editing the split project. With respect to the content, it is a complete copy of the master project (which means that every editor sees the entire original master project).
2.The split project name corresponds to the master project name, but has a consecutive number appended in parentheses. The name can be changed later, but it is important that the logical relationship to the master project not be lost.
3.Care must be taken to prevent the changing of something in the split project which may not be changed/edited due to the split (because it lies outside of the split area in the master project, even though it’s still visible - see 1). In both the split and master projects, the split areas in which editing is not allowed are locked for this reason. The fact that the split project and the master project can both be edited is referred to as split information and is shown using additional icons respectively in the structure element.
Icons and Their Meaning
•Splits can only be performed in the master project. Consequently, a split project cannot itself be subdivided or split again, even if the split would be performed on editable elements.
•Further splits can only be performed for new structures or levels in the master project which have not already been split at a lower level (a split at the area level is not possible if a line present in it at a lower level is already split). This is also indicated by the status B.
Buildings and trades have a name, but no additional, unique identifier such as the PA/IA for a device. Rooms on the same floor that have the same name do not represent a problem in a project, for example. Splitting and later merging projects with rooms and the same names on the same level (e.g. floor) would, however, not make unique assignment of the devices to a room possible.
ETS checks for this situation before a split and issues a warning, however, after the split, there is no more warning before a subsequent name change (responsibility of the user).
•Because a split project is also a complete, independent project (a copy of the master project), splits can be undone in the Project Area, both for a split project and a master project. The function is only active when there is actually a split in the project. When this is done, all split information relating to the split is reset in the selected (and only in the selected) project. A merge is also still possible after this, but only with increased effort.
•Possible project files in the master project are also integrated into the split project.
•Any possible project password in the master project (mandatory when KNX Secure is enabled) is also applied to the split project.
•A project split is also logged in the Project Tracking function if this option is enabled in the master project.
•When a master or a split project is copied normally, all split information is copied as well.
▪They have, at the most, a logical relationship (based on the name) to each other. There is no technical link between parts. The only (indirect) information about the master and the split consists of the Availability of the elements in the different projects.
They contain elements with status A () and status B ().
•All nodes of the split area (A) can be edited; all other areas comprise status (B).
•The part of the project was, consequently, split out of "something" (the master) and therefore this project is correctly called a split project.
They contain only elements with status B ().
•All nodes of the split area (B) cannot be edited; all other areas, which are not also split, comprise status (C).
•The part of the project was, consequently, split into "something" (the split) and therefore this project is correctly called a master project.
▪They exist fully autonomously from each other, which is why a reset of the split is possible.
▪The node, or the root element on which the split was performed, cannot be edited in the split projects after a split.
▪Correct management of the master/split project interconnection by an administrator is a prerequisite.