Centralised ETS Project Management via MyKNX with Synchronisation and Access Control
I'd like to share an idea that I believe could be useful for many KNX SIs, especially those working with larger building operators.
I personally manage several larger KNX installations and regularly run into problems with different versions of ETS projects.
Especially in public buildings such as schools, government offices or other state-owned facilities, ETS project files are often not managed particularly well.
Here's an example: I've been maintaining a KNX installation for several years. Due to a public tender, another electrician or system integrator is awarded the contract for a major extension. That's perfectly fine, but things often get complicated afterwards.
Did they use the original ETS project? Were all changes included? And when I return for the next maintenance visit, will I actually receive the latest and complete project file?
A large part of my work now involves modernising existing installations and, unfortunately, reconstructing ETS projects. Especially in installations that have been extended several times over the years, parts of the documentation or even entire project versions are often missing.
With KNX Secure, I don't think this situation will become any easier in the future.
Building operators could store and manage all their ETS projects centrally within their MyKNX account.
For example, a regional government manages 30 buildings equipped with KNX installations. All 30 ETS projects would be stored centrally in the government's MyKNX account.
This way, the project files would always remain under the building operator's control instead of depending on individual contractors.
The building operator could grant individual KNX partners access to specific projects.
The authorised partner would open the project directly in ETS, make the necessary changes and synchronise the updated project back to MyKNX once the work is completed.
If another electrician or system integrator takes over, the building operator simply grants them access. Permissions for previous contractors could be removed whenever necessary.
This would also eliminate the constant exchange of project files via email or other methods.
Direct integration into ETS would be ideal.
Open the project, make your changes and synchronise it back to MyKNX.
Some additional features could include:
-
Version history with the option to restore previous project versions
-
Project locking to prevent multiple partners from creating conflicting project versions
-
An overview showing who last modified a project and when
-
Notifications to the building operator whenever a new project version is uploaded
ETS already allows users to attach additional files to projects.
These might include access credentials, visualisation project files, network documentation or other technical documents.
What I'd like to see here is a better overview. It should already be visible in the project list whether additional documents are available, without having to open the project details first.
Sensitive documents should, of course, only be accessible to authorised users.
I see a particularly strong benefit when it comes to KNX Secure.
If different project versions are circulating or important security keys are lost, maintaining or extending an installation can quickly become very complicated.
Centralised project management could help ensure that the latest project files, including the necessary KNX Secure information, remain available to authorised partners.
Building operators would retain full control over their ETS projects while still being free to choose which KNX partner carries out maintenance or extensions.
For us system integrators, it would also make life much easier because we wouldn't constantly have to search for the latest project version when working on existing installations.
I can certainly imagine larger building operators being willing to pay an annual subscription fee for such a service.
-
I agree Dominik. Your suggestions seem similar to the Project Archive but with more functionality/complexity. Split and Merge ETS App might be useful for adding a major extension to an existing installation.
I think KNX Secure is great in principle to secure the communication in a KNX installation but (as far as I know) devices commissioned using KNX secure are not possible to Reconstruct without the keychain - so in the event that a KNX secure .knxproj file is lost, corrupted or inaccessible this might require manually accessing every device and hope it still has the QR code label on it…
0 -
Hello Stephen,
I use the Split & Merge app myself. However, it does not prevent multiple project versions from circulating. This is especially true when an external company has no experience with the app, as some basic rules regarding the group address structure still need to be followed to keep things manageable.
My request was less about configuring KNX Secure or reconstructing an installation. It was more about preventing data inconsistencies through a central project repository, stored online rather than locally on someone’s PC and managed by the installation owner.
I also do not think an ETS app is the right approach, as it would require the external system integrator to have another tool to access that repository. In my view, it would make sense to integrate this functionality directly into ETS and use MyKNX for user management, since a MyKNX account is already needed for things like installing apps and using cloud licensing.
In my example, the installation owner’s account should cover the costs and administration, so that each invited system integrator does not have to make changes to their own setup.
I currently use a self-hosted project portal to share and request project files. However, this still involves additional steps and relies on external system integrators having the discipline to upload everything again and document what they changed.
With KNX Secure projects, data consistency is extremely important to avoid problems with the Device Key.
1 -
The most delicate aspect of a KNX installation is managing the project files over time as changes are made.
0 -
I don’t know if it’s a fair comparison, but I’m quite happy with the project and user management in Loxone Exosphere. With a 1- to 10-year subscription, you get a platform where you can store the project and additional documents and share them with others through user management.
Once the work is complete, the project is saved again and the external contractor’s access to it is revoked. This would also mean that the project password would not have to be shared with them in plain text. It would help maintain security afterwards by ensuring that they no longer have access to the installation once their permissions have been revoked.
1
Kommentare
4 Kommentare
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.