Key takeaways
- The ETS project file constitutes a contractual deliverable owed to the client.
- Withholding the parameterisation blocks maintenance and severely harms the installer's reputation.
- A concise user memo prevents unnecessary call-outs and ensures the autonomy of end users.
- A documented group architecture enables the takeover of the installation by another telematics technician.
Transmitting the ETS project file and clarifying intellectual property
Some integrators wrongly consider the ETS database to be a trade secret or a tool for commercial lock-in to force the operator to commission future interventions. This practice is counterproductive. Under Swiss construction law, pursuant to art. 363 CO, which defines the contract for work, the contractor undertakes to deliver a completed and usable work. On a building management or residential home automation installation, the work does not merely include DIN rail-mounted modules and line couplers: it inextricably encompasses the intelligence injected into these devices, embodied by the parameterisation of logic functions, group addresses and communication object links.
Withholding the software archive exposes the enterprise to formal complaints and destroys the relationship of trust with the client or the construction management. If a third party must intervene to troubleshoot a defective micromodule or reconfigure a lighting control without the source file, reverse engineering by monitoring frames on the bus or by manual reconstruction generates massive additional costs that the client will legitimately seek to pass on to the original installer. Upon acceptance of the work, the as-built documentation (DOE) must therefore include the export of the ETS project, ideally in the standard archive format (.knxproj), sealed and cleaned.
| Documentation element | Expected format | Purpose for the operator and incoming technician |
|---|---|---|
| ETS project archive | Unprotected .knxproj file | Reprogramming, device replacement, functional upgrades. |
| ETS project report | Concise PDF document | Inventory of physical addresses, line topologies and couplers. |
| Group address table | CSV export or spreadsheet document | Understanding of the 3-level structure (function / room / action). |
| KNX Secure security keys | Keyring certificate file | Access to secure devices in the event of subsequent extensions. |
Contractual mention of the ownership of the parameterisation must be clarified from the initial quote. The text of the contract for work must specify that the client acquires full enjoyment of the parameterisation injected into their building once the final invoice is settled, whilst the integrator retains their generic know-how or preconfigured logic blocks in the form of a non-exclusive licence of use. This clause prevents any intellectual property dispute whilst confirming the transfer of the operational data of the work.
Organising operator training and preparing takeover by a third party
A home automation installation handed over without human guidance systematically generates unwarranted call-outs and user frustration. Handing over the bus keys requires a dedicated training session, of a duration suited to the site's complexity: around one hour for a detached house, half a day for a commercial or administrative building. This familiarisation takes place on site, under real operating conditions, in the presence of key users, building caretakers or the technical facility manager.
- Demonstration of local controlsPresent the operation of wall push-buttons, short and long presses for dimming, recalling living scenes and the operation of integrated room thermostats.
- Explanation of automations and safety systemsDetail the autonomous behaviours of the system: automatic blind retraction in strong winds via the weather station, emergency lighting override, manual overrides and timers.
- Familiarisation with supervision interfacesGuide the operator through the central touch screen or dedicated mobile applications: management of time profiles, modification of setpoint temperatures and acknowledgement of technical faults.
- Handover of the concise user memoDeliver a laminated document of two to four pages, kept close to the control panel or local server, summarising common operations and the procedure to follow in the event of a fault.
The user memo does not replace the complete operating manual, but it condenses vital information. It must record the IP addressing plan of gateways and visualisation servers, administrator and user access credentials, as well as the procedure for a clean restart of an interface in the event of a network lockup. It explicitly specifies the division of responsibilities between KNX control and terminal devices.
The warranty for defects applies according to the rules of the Code of Obligations (CO). Art. 368 CO reserves the client's rights in the event of defects affecting the agreed work. However, as soon as a third party intervenes on the bus and downloads new programming without prior agreement, the original integrator's liability ceases for the modified components. To prevent conflicting claims, the enterprise delivers the ETS archive on sealed physical media (USB flash drive) upon signature of the acceptance report, whilst retaining a time-stamped mirror copy in its enterprise technical archives.
Withholding the knxproj project: commercial illusion and technical risks
Some integrators still consider the project file in the standardised export format to be their private preserve, supposed to guarantee a monopoly on subsequent maintenance or troubleshooting operations. In French-speaking Swiss finishing work practice, this retention of information is a systematically losing calculation. It damages the relationship of trust with the client, blocks emergency interventions and exposes the installer to disputes during the acceptance of the work in accordance with standard SIA 118.
On a technical level, a bus whose database is sequestered becomes an opaque system for the operator. Unlike industrial programmable logic controllers whose source code can sometimes be protected under proprietary licence, the infrastructure of a major commercial or residential building must remain durable, regardless of the commercial survival of the initial installation enterprise. Withholding the file forces a third-party contractor to reconstruct the topology through reverse engineering during hardware failure, leading to disproportionate engineering costs.
| Document or deliverable | Technical format | Purpose for the operator or incoming technician |
|---|---|---|
| Complete project archive | Software archive file (.knxproj) | Full takeover of parameterisation, addition of devices and group address diagnostics. |
| Project report and topology | Printable document or PDF | Visualisation of the line tree, couplers and individual addresses without programming tools. |
| Group address list | Structured table or spreadsheet | Unambiguous correspondence between control functions, status feedbacks and communication objects. |
| Security keyring | Security keys file (.knxkeys) | Essential access to devices using the KNX Data Secure or KNX IP Secure protocol. |
| Gateway backups | Image files or system configurations | Rapid restoration of supervision modules, display servers and gateways to third-party protocols. |
Contractual safeguarding, user memo and technical handover
The transmission of the parameterisation must be clarified as early as order placement. Within the framework of a contract for work within the meaning of art. 363 CO, the intellectual work of addressing, linking communication objects and parameterising devices forms an integral part of the work ordered and remunerated by the client. Art. 364 CO binds the contractor to faithful and diligent performance, which implies providing the operator with the real means to maintain their installation.
To avoid any dispute, the special conditions of the quote or tender must explicitly stipulate the status of the data. Rigorous wording specifies that the integrator transfers exclusive use of the parameterisation applied to the site upon full payment of the work, whilst handing over an unlocked archive on removable media left in the main patching or distribution cabinet.
The handover is not limited to handing over raw files. The installer dedicates a formal session to training the site's technical manager or the owner. This session is based on a concise user memo: procedure for disconnecting and reconnecting the bus power supply with choke, interpretation of line coupler status LEDs, location of hardware backups and method for local access to administration interfaces without relying on a remote portal.
By handing over an impeccable file, the enterprise showcases its professional rigour. Experience shows that a client who holds all of their access credentials and databases voluntarily calls back the original technician for future extensions, whereas illegitimate withholding invariably leads to contract terminations and claims for defects in the work.
Dispute management, lockouts and forced takeover of an orphaned installation
When an integrator refuses to hand over the `.knxproj` archive or the technical documentation disappears after a contractor's bankruptcy, the operator finds themselves captive to a locked system. Under Swiss contract law, the parameterised database constitutes an indivisible component of the delivered work, on the same footing as electrical schematics or inspection reports. In the absence of this native file containing the associations and application parameters, any modification of a group address or replacement of an actuator becomes impossible without overwriting the existing programming. The client then suffers direct operational loss. Under art. 368 CO, the client may assert their rights in the event of defects in the work, demanding rectification or damages where contractual deliverables are missing.
- Passive audit and bus monitoringConnect an IP or USB communication interface to the bus, activate the ETS group monitor for several hours of operation to map the telegrams exchanged and record active group addresses.
- Physical scan and panel reconciliationRun a line scan to identify each individual physical address present, then cross-reference these addresses with the low-current single-line diagram found in the cabinet.
- Reconstruction in a new ETS projectReimport the manufacturers' certified application programs, recreate the room structure and overwrite the parameterisation device by device in order to rehabilitate the installation.
Prior to any legal action, a formal written notice based on contractual rules and standard SIA 118 is generally sufficient to unblock the export of the project file against payment of the agreed balance. If the amicable handover definitively fails, the new integrator records a formal joint status report before injecting any command line into the bus, thereby strictly delimiting their warranty relative to the original programming. This baseline document records the verified functionalities, observed defects and inaccessible devices, ensuring legal certainty for the incoming contractor.
Frequently asked questions
What should be done if the password for the ETS project or KNX Secure access has been misplaced?
Without the KNX Secure security keys (FDSK or project certificate), secure devices can no longer be modified via the bus. The integrator must reset each device to factory settings using its programming button or a manufacturer-specific hardware procedure. This erases the resident parameterisation, requiring the entire application to be redownloaded from a reconstructed ETS project, which causes a substantial loss of time on the construction site.
Can the operator demand the ETS file if the total amount of the work has not been settled in full?
Refusing to transmit technical documentation is frequently a means of retention used by an installer faced with non-payment. However, CO provides that the price of the work is payable at the time of delivery. If the client withholds a disproportionate amount for a minor dispute, both parties reach an impasse. The usual solution consists of depositing the disputed balance into an escrow account to discharge the obligation to hand over the .knxproj file.
Which physical or digital media should be preferred for archiving the project file on site?
It is recommended to store an industrial USB flash drive containing the exported .knxproj file, wiring diagrams and user memo directly in a technical document wallet fixed inside the home automation panel. In addition, an encrypted export must be sent via secure messaging or placed on the building's local server. This redundancy ensures that an emergency repair technician has access to the data without having to chase the initial installation enterprise.
What contractual precautions should be taken before taking over the maintenance of a third-party site?
The incoming integrator must have a takeover protocol signed releasing them from liability for any pre-existing defects. They begin by requesting the original ETS project and check its strict conformity with the installation using the ETS comparison tool. In the event of discrepancy or lack of a project file, hours spent mapping or reprogramming the bus do not fall under the maintenance flat rate, but must be subject to a prior quote on a technical daywork basis.
Texts and standards cited
- SIA 118general conditions for construction work
- CO art. 368client's rights in the event of defects in the work: repudiation, price reduction, rectification, damages
- COthe price of the work is payable at the time of delivery
