Contracting for connected infrastructure: what a good agreement covers

General information, as of October 2026. This article is a general checklist, not legal advice. A real agreement must be tailored to the project, the parties, and applicable Albanian law. Have it reviewed by a qualified lawyer.

A connected solar plant, treatment unit, or irrigation system is three things at once: equipment installed on a site, software that runs and monitors it, and data that flows between them. Contracts written for only one of these leave gaps. A good agreement covers all three, in plain language, and gets the hard questions answered before the first delivery.

As our Terms of Service say about our website, nothing published on it is a binding offer. Scope, pricing, specifications, and timelines are confirmed only in a signed agreement — which is why the contents of that agreement matter.

1. Scope and specification

What exactly is delivered: equipment, installation, commissioning, software, training, documentation?
What are the performance targets, and — just as important — how will they be measured? "Reduces water use" means nothing without a baseline, a measurement period, and a method.
What are the site and customer's responsibilities: access, foundations, permits, connection to the grid or water network?

2. Acceptance and handover

Define the commissioning tests (for example, the documentation, inspection, and testing approach in IEC 62446-1 for PV systems) and who witnesses them.
Agree how defects found at handover are listed and fixed.
List the handover package: as-built drawings, equipment data sheets, configuration, manuals, passwords and access under the customer's control, and training.

3. Warranties and defects

Distinguish manufacturer warranties on equipment from the installer's workmanship warranty.
State the defects-liability period and the process for reporting and fixing faults.
Be explicit about exclusions — misuse, unauthorized modification, grid or network failures, and force majeure.

4. Operation, monitoring, and service levels

Who operates the system day to day, and who is responsible for safety and compliance on site?
For a monitoring service: availability targets, support hours, response and resolution times, planned maintenance windows, and what happens when targets are missed.
Manual-override and safety rules: who may override automation, how it is recorded, and which limits can never be overridden.

5. Data

Data deserves its own section:

Ownership and use. Who owns the site's operational data? What may the provider do with it — deliver the service, improve it, create anonymized or aggregated insights?
Confidentiality of customer operating data and commercial information.
Personal data. Where personal data is involved, include the roles of the parties and a data processing agreement — see personal data on an IoT platform.
Retention and export. How long is data kept, and in what format can the customer take it with them when the contract ends?

6. Intellectual property

Equipment is owned by whoever buys it; software is normally licensed, not sold. State the licence's scope, term, and limits.
Protect proprietary technology — including the logic inside a control platform — with clear restrictions on copying and reverse engineering.
Settle who owns customer-specific configurations, dashboards, and reports.

7. Price, payment, and risk of change

Milestone payments tied to defined, verifiable events; retention amounts where appropriate.
Title to the equipment: when it passes, and any retention of title until payment.
Price adjustment for major cost swings and for currency risk.
Regulatory change. In energy and water, rules move — see Albania's energy rules in 2026. Who bears the cost if a law, tariff, or permit condition changes?

8. Liability and insurance

Reasonable caps and exclusions for indirect losses, within what the law allows. Some liabilities cannot be limited under mandatory rules.
Required insurance: construction, product, professional, and cyber cover where relevant.
Indemnities that match who controls the risk.

9. Security and incidents

Security obligations for both sides: access control, device handling, and changes to network settings.
Incident notification — who tells whom, and how fast, if something goes wrong. See securing connected infrastructure.

10. Changes, termination, and exit

A process for variations so that scope changes are priced and agreed before they are built.
Grounds for termination and what survives it.
Exit support: handing over credentials, data, documentation, and — where agreed — transition assistance and spare parts.

11. Compliance and disputes

Compliance with permits, health and safety, anti-corruption, and sanctions rules; subcontractor responsibilities.
Governing law, language, and how disputes are escalated: management discussion, mediation, then courts or arbitration.

The best contract is the one both sides could explain to someone else in five minutes — and still agree on the answer.