This function makes it possible to split a project into project parts which several editors can then edit individually. They can each work independently in different places and at different times. When editing is complete, the project can be merged so that the download to the installation can be performed (for different procedures, see Notes).
The license is only required for the project editor, for example, who splits a project and later merges it once again. The editors of a split project do not each require their own license to edit the split project.
In order to split a project, it must first, of course, be created (centrally), and this forms the basis for any subsequent splitting. This project is then the master project and is managed by the project administrator.
Several basic structures which can be split must be created within the master project. These are used later for the actual splitting. This is relatively self evident as structures must be spatially and topologically separated in order for editors to be able to work in them without influencing their "neighbor’s" data. This makes it apparent which structures in an ETS project even come into question for splitting (e.g. lines in the topology).
The result of splitting is the generation of a split project in addition to the master project* . To make it possible to distribute editing tasks, the split project must still be exported and transferred to the respective editors. At the end of the procedure, they must then be merged with the master project.
|*||Several independent split projects can be created based on one master project.|
1.Create Master Project
This step is the same as for a normal project with topology and a building structure set up by the Administrator. This step serves to create project structures which can be split.
2.Split a Project
The administrator performs a splitin the master project which results on one or several split projects being created. For details, see here.
3.Distribute Split Project
The split projects must be exported by the administrator and transferred to the editors.
After completion of editing, the administrator must merge the split projects with the master project. For details, see here.
Split projects need not consist only of the individual split projects, but can also include the master project itself. The master project is also subject to certain editing limitations after being split.
Copy in split projects
Structures in split projects can be copied or duplicated (e.g. reproducing a line), but several points must be taken into consideration when doing so.
•If split structures (those with icons) are copied within the project, the split information is not stored in the target copy; reasons:
•Copy is Generated in Split Project
•Copy is Generated in Master Project
Edit in split projects
When editing structures in split projects, a few points must be observed (r = read - read-only; w = write - editable and deletable).
KNX Secure in split projects
Structures in split projects can also influence the handling of KNX Secure, so several points must be taken into consideration for this.
•If a KNXnet/ IP device is blocked for editing by a project split, then KNX IP Secure devices in the associated part of the topology are also inserted as KNXnet/ IP devices (without KNX IP Secure being enabled), meaning without a query in accordance with the actual security rules in the topology.
•Another approach that could be used as a working procedure for a line that has already been projected (while the others are still being edited) would be to split it and transfer it to the on-site editor for the purpose of fine-tuning the parameters and for downloading. Subsequently, at the end, this final subproject would then be merged with the master.