Support contract for OpenStack

The commitment is required that a company liability insurance with the following minimum amounts of coverage is available or be completed and presented at the latest within a period of 14 days after surcharge:

• 5 million Euro for personal injury per claim with double annual maximum for all claims and
• 5 million. Euro for property damages per claim for double the maximum annual performance for all claims and
• 2.5 million. Euro for property damages and data protection damages per claim for double the maximum annual performance for all claims. The insurance shall be maintained for the entire duration of the contract.

Proof of ISO 27001 Certification The tenderer shall demonstrate an information security management system in accordance with ISO/IEC 27001:2022 or an equivalent standard for the area providing the tendered support and operational support services. The proof is provided by a valid certificate from an accredited certification body. Equivalent certificates shall be recognised. Other documents about an equivalent system are subject to the provisions of § 49 para. 1 VgV recognized.

References: In order to demonstrate technical and professional capacity, the tenderer must submit at least two appropriate references in his tender. The submitted references must in their entirety meet the following minimum requirements R1 to R3. A reference may cover several minimum requirements. R1 – OpenStack and Yaook: Evidence of at least two relevant references on operational support and support of productive OpenStack environments.

At least one of these references must concern an OpenStack environment based on Yaook. R2 – Ceph: Proof of practical experience with Ceph as a productive storage platform of an OpenStack environment. R3 – Open Source/Upstream Projects: Proof of practical experience with active participation in relevant open source or upstream projects, in particular OpenStack, Yaook or Ceph.

Active participation includes, for example, code contributions, bug fixes, the processing of issues, reviews or contributions to technical documentation. The services used to demonstrate the requirements R1 to R3 must have been provided within the last three years before the expiry of the offer period. Reference contracts still in progress shall be taken into account to the extent that the relevant services have been provided within that period.

For this purpose, the Annex Reference Description for each nominated reference project must be submitted in full with the tender. The tenderer must indicate which of the requirements R1 to R3 are proven by the respective reference. An evaluation of the references by points does not take place.

If at least two appropriate references are not submitted or one of the minimum requirements R1 to R3 is not demonstrated, the tenderer’s technical and professional capacity shall not be established and the tender shall be excluded from the further ranking. The number of references to be submitted shall not be limited upwards. In addition to the minimum required two references, other appropriate references may be submitted. There is no improvement solely on the basis of the number of references submitted.

The contracting entity reserves the right to verify the information relating to the references. For this purpose, the bidder has to name a contact person with the respective reference customer with official telephone number and e-mail address on request within a time limit set by the customer. In the case of open source or upstream activities, additional suitable evidence, in particular references to publicly accessible repositories, issues, reviews or documentation, may be required. For groupings of tenderers and in the case of a qualifying loan, the submitted references shall be considered as a whole.