How to set the right tender conditions when buying software through public procurement
A training material for contracting authorities preparing tender documentation for software supplies. How to reduce the risk of buying illegal software, obtain comparable bids and secure enforceable contractual protection in the event of a legal defect in the licenses.
Introduction
This training material is intended for contracting authorities and for staff who prepare tender documentation for software supplies. Public contracts for licenses are specific in that new software from the manufacturer and secondary software, i.e. software from the open market, exist side by side on the market. With secondary software, the main risk is that the contracting authority cannot reliably verify whether its origin is legal.
The material shows how to set the tender conditions and contractual arrangements so that the contracting authority:
reduces the risk of purchasing illegal software,
obtains comparable bids from all suppliers,
has genuinely enforceable protection in the contract in the event of a legal defect in the licenses.
The explanation is divided into four interconnected parts. The first part describes the risks that arise when conditions are set inadequately. The second part sets out two basic requirements that prevent these risks. The third part offers specific contractual provisions that supplement the basic requirements and make them enforceable. The fourth part recalls the principle of proportionality, which must be observed when preparing tender documentation. The text of the individual parts is taken from the original recommendation without changes.
When preparing a specific contract, the recommended requirements must be adapted to the subject matter of the contract, and the principles of the Public Procurement Act must be observed, in particular proportionality, transparency and equal treatment.
Recommendations on tender conditions
1. Why the tender conditions need to be adjusted
The starting point is the current situation on the software market. The following paragraphs describe the risks faced by a contracting authority that sets the conditions inadequately.
In view of the current developments on the software market in the Czech Republic, where offers of software of non-transparent origin are increasing, presented both as secondary and as new software, and in view of the fact that these offers are also making their way into the tender procedures of public contracting authorities.
Inadequately defined conditions expose the contracting authority to the risk of purchasing pirated copies. Bids with pirated copies harm not only the contracting authority, which suffers damage, but also the other competitors. At the same time, they lead to non-comparable bids and to unfair competitive conduct.
2. Key requirements
The risks described lead to a recommendation on how to adjust the tender conditions. It is based on two requirements that should not be missing from any software contract.
We recommend adjusting the tender conditions so as to exclude bids for which the legal origin of the software has not been demonstrated with a sufficiently high degree of certainty.
The following requirements are particularly important:
For new software, always insist that the license be credited directly to the CUSTOMER's license account on the manufacturer's portal (crediting to the seller's account is not sufficient).
For secondary software, require the handover of documentation proving the legal origin of the copy and have its content reviewed (this right does not apply if an auditor's audit report has already been prepared for the licenses in question).
3. Recommended contractual provisions
The two basic requirements from the previous part should be supplemented by provisions directly in the contract. These provisions cover proof of license origin, verification of documentation, insurance, access to the license portal and compensation for damage, and thus give the contracting authority firm support in the event of a dispute.
We also strongly recommend considering the possibility of setting requirements for liability insurance and other potentially relevant requirements, as set out below:
We recommend including in the contract:
In order to ensure a higher degree of legal certainty and thus also of security, the contracting authority requires that the seller have standardized processes in place at the level of ISO 9001. The supplier shall submit documents proving this as part of its bid.
If secondary software is supplied, these products must meet all statutory requirements and be supplied together with the following documentation (collectively referred to as the ownership documentation), which proves that all statutory conditions have been met:
a) Identification details of the first acquirer of the software and proof that the products were purchased through official distribution. Identification of the products by the number of the agreement under which they were purchased, as well as identification of the original volume licensing agreement (among other things, to make it clear that these are not EDU/Academic licenses).
b) A declaration by the first acquirer that the software was paid for in full.
c) Confirmation that the software product was first placed on the market in the EU, the EEC or Switzerland.
d) Confirmation that the license is perpetual.
e) Complete identification of the previous owners of the software.
f) A signed declaration by the original acquirer of the software (and by all other acquirers in the chain of previous owners) stating that all software products have been uninstalled, are not in use and that their future use has been prevented.
The contracting authority accepts that the ownership documentation under points a) to f) above may be replaced by an independent license audit report. An authorized auditor shall carry out a license audit before the licenses are delivered and confirm the authenticity and originality of this information. The original of the audit report shall be delivered to the contracting authority.
Where secondary licenses are offered, the contracting authority reserves the right to have all documentation and the information contained therein independently verified, in particular the right to provide all submitted documents for assessment to external experts (the software manufacturer, a distributor or another specialist), provided that they are contractually bound to protect their content to the same extent as the contracting authority. This right does not apply if an auditor's audit report has already been prepared for the licenses in question.
Information and documents proving the origin and transfer of the licenses (the "License Provenance Documentation") do not constitute a trade secret or confidential information of either contracting party. This applies notwithstanding any other provisions of this contract or other confidentiality agreements between the parties. License Provenance Documentation includes, in particular:
a) identification of the first and all subsequent acquirers,
b) license agreement numbers (e.g. Enterprise Agreement, Open License, MPSA, CSP, OEM) and authorization numbers,
c) type, edition, version and number of licenses and date of acquisition,
d) proof of acquisition,
e) uninstallation declarations,
f) details of the independent auditor (company name, company ID number, registered office) and its audit report or certificate.
The Seller agrees that the Buyer may disclose the License Provenance Documentation to subsequent acquirers, to the licensor and auditors appointed by it, and to distributors, courts and public authorities. The Buyer may do so for the purpose of demonstrating the exhaustion of the distribution right that occurred upon the first sale of the licenses within the EU/EEA pursuant to Section 14(2) of the Czech Copyright Act.
Proof of professional liability insurance which, where secondary software is supplied, also covers the supply of copies from the open market, with a limit of at least the price of the licenses on the primary market. Suppliers shall prove this by submitting a professional liability insurance certificate or contract. A copy of the insurance contract / certificate of the concluded insurance contract forms Annex No. x to this Contract.
As part of the software delivery, the contracting authority also requires that the licenses be credited to its account on a license portal to which it will have direct access. For new licenses, they must be credited to the software manufacturer's license portal created for the customer; for secondary licenses, this may also be another license portal enabling license management, at least to the extent of recording the licenses, downloading the legal documentation and providing a list of links to installation files, provided that its operator has implemented standards at the level of ISO 27001. The same ISO 27001 requirements as those set for the license portal should also be set for the option of delivery via cloud storage, which may be operated by a third party and thus represents an additional risk.
The supplier shall compensate the contracting authority and the group companies for all damage incurred as a result of a legal defect in the licenses, including penalties imposed by the software manufacturer or by public authorities, the costs of a software audit and the costs of legal representation. The claim for damages is not limited by the amount of the contractual penalty.
The contracting authority reserves the right not to conclude a contract with a bidder in respect of whom an internal risk assessment identifies serious deficiencies.
4. Proportionality and protection of the contracting authority
The proposed measures are intended to give the contracting authority a high level of protection, but they must not restrict competition unnecessarily. The original recommendation therefore ends with a reference to the principle of proportionality.
We believe that the combination of tools described above provides the contracting authority with greater and genuinely enforceable protection. We therefore ask you to consider amending the relevant provision of the tender documentation so that it complies with the principle of proportionality while maintaining full protection of the contracting authority.
Conclusion
The introduction set out three objectives: to reduce the risk of purchasing illegal software, to obtain comparable bids and to have enforceable protection in the contract. The individual parts of the material lead to them as follows:
Risks (part 1). Inadequately set conditions lead to the purchase of pirated copies, harm the contracting authority and the other competitors, and result in non-comparable bids.
Basic requirements (part 2). New software is credited directly to the contracting authority's license account on the manufacturer's portal. For secondary software, the contracting authority requires and reviews documentation proving its legal origin.
Contractual protection (part 3). The contract includes the right to verify the documentation, consent to the disclosure of the documentation to third parties, liability insurance, compensation for damage and the right not to conclude the contract if serious risks are identified.
Proportionality (part 4). Each requirement must correspond to the subject matter and value of the contract and must not unjustifiably restrict competition. It is therefore advisable to consult the setup with an expert in public procurement and copyright law.
In public software procurement, the contracting authority's main objective is to obtain licenses whose legal origin can be documented and which can be defended in the event of a dispute.